GSTR-2A Reconciliation

What is GSTR-2A reconciliation?

GSTR-2A reconciliation is the systematic matching of every purchase invoice in the company's books against GSTR-2A (a dynamic, view-only return populated from suppliers' GSTR-1 filings) or its monthly-static cousin GSTR-2B. The reconciliation determines whether the buyer can legally claim Input Tax Credit (ITC) on the GSTR-3B return for that period.

The math is brutal: ITC is only claimable on invoices that also appear in 2A/2B. An invoice in your books but missing from 2A is a credit at risk; an invoice in 2A but not in your books is a phantom credit you cannot legally take.

Why GSTR-2A reconciliation matters in Indian procurement

Three reasons it sits at the centre of the procurement-finance overlap:

• Cash impact — for a mid-size manufacturer, ITC mismatches of even 5% of monthly purchase value mean ~₹5–10 lakh/month of credit at risk. Annualised, that is real working capital.
• Legal risk under Rule 36(4) — ITC can only be claimed on invoices reflected in GSTR-2B (post Sep 2021). Mismatches reversed under audit attract interest at 18% per annum and penalty.
• Supplier accountability — repeated non-filers should be flagged, downgraded, or replaced. Reconciliation turns "GST compliance" into a measurable supplier-evaluation metric.

What goes wrong in practice

The mismatches that consume finance teams during the 1st-to-20th window each month:

1. GSTIN typo on the PO — supplier files correctly, you can\'t find it in your 2A because you\'ve recorded their GSTIN slightly wrong
2. Invoice number variance — leading zeros, hyphens, slashes, or spaces. "INV/2026/0042" vs "INV-2026-42" looks like the same invoice to humans but to a reconciliation engine it\'s two records
3. Multi-state mix-up — supplier files against your Maharashtra GSTIN; the invoice was actually for a Karnataka delivery
4. Supplier hasn\'t filed — most common in Q1 of every fiscal year; the invoice is real, the credit is delayed
5. Reverse-charge invoices — flagged differently and frequently mis-categorised on either side
6. Credit / debit notes — appear separately in 2A but are recorded against the original invoice in your books

How ProcurePulse handles GSTR-2A reconciliation

• Direct GSTN API integration pulls 2A and 2B for every registered GSTIN of the company
• Three-way match (PO + GRN + Invoice) is the upstream control — invoices not three-way-matched cannot be claimed
• Reconciliation engine matches on GSTIN + invoice number (with fuzzy match for known formatting variants) + invoice date + value
• Supplier-side gaps (filed by us, not in their 2A) trigger an automated email to the supplier with the missing line items, escalating to procurement on day-7
• Buyer-side gaps (in 2A, not in our books) are rare but routed to AP for reverse investigation
• Reconciliation reports feed into the GSTR-3B working file and are signed off before filing

Best practices for clean reconciliation

• Validate vendor GSTIN at onboarding via the GSTN API — never rely on a supplier-typed PDF
• Use a single invoice-number format in your system; force suppliers to use it on the invoice (some invoicing tools allow custom formatting)
• Run reconciliation by the 10th, not the 19th — gives a week to chase mismatches before 3B
• Track supplier ITC compliance score as a vendor-rating dimension — chronic non-filers cost the company real money
• Reconcile credit and debit notes separately and link them to the original invoice in the audit trail

Last updated: 2026-04-29