GSTR-2B reconciliation is a small job at fifty purchase invoices a month and a serious one at four thousand. A mid-sized manufacturer buying raw material, consumables, packing, transport, job work and power from several hundred vendors is matching thousands of lines against a statement that only lands on the 14th, against a GSTR-3B due on the 20th.
That is the real constraint. Not the matching logic, the calendar. This post sets out how matching at volume actually works, where fuzzy matching earns its place and where it must not be trusted, how to run an exception queue, how to chase suppliers, and what the audit trail has to show for the GST rules as they stand in July 2026.
The monthly problem at volume
Form GSTR-2B is the auto-drafted statement of input tax credit built from what your suppliers filed. Under the Invoice Management System, a draft GSTR-2B is generated on the 14th of the following month, and you can act on records from the time a supplier saves them in GSTR-1, IFF or GSTR-1A right up to the moment you file your GSTR-3B. Any action taken or changed after the 14th means GSTR-2B has to be recomputed.
Monthly GSTR-3B is due on the 20th of the following month. Quarterly filers under QRMP file on the 22nd or the 24th, depending on the state or union territory. So for a monthly filer the working window between a usable 2B and the return is about six days, and in those six days a purchase team has to explain every difference between the books and the portal.
At a few hundred invoices, a clerk with a spreadsheet gets through it. At a few thousand, the spreadsheet stops being a tool and becomes the risk.
GSTR-2B reconciliation: matching rules that do most of the work
Run matching in passes, strictest first, and only let later passes see what earlier passes could not settle.
- Exact match. Supplier GSTIN, document number, document date, taxable value and each tax head equal. On a clean vendor base this clears the large majority of lines and should never need a human.
- Exact match with rounding tolerance. Same keys, with a small value difference from rounding in your ERP or theirs. Set the tolerance in rupees, keep it small, and log every line cleared this way.
- Normalised document number. Same GSTIN and date and value, document number matching after case, spacing, slashes and leading zeros are normalised.
- Near date. Same GSTIN, number and value, invoice date differing by a day or two, which usually means the document was booked on a different day at one end.
- Everything else goes to the exception queue with a reason attached.
Where fuzzy matching earns its place
Fuzzy matching is for suggesting a candidate, never for deciding one. These are the cases where it pays.
| In your books | In GSTR-2B | What the system should do | Who decides |
|---|---|---|---|
| INV/2026-27/0148, 5 June, ₹2,45,000 | INV-2026-27-148, 5 June, ₹2,45,000 | Normalise the number and match automatically | No one |
| Doc 4471, 30 June, ₹88,500 | Doc 4471, 1 July, ₹88,500 | Match with a date-variance flag | No one, but reported |
| Taxable ₹1,00,000, IGST ₹18,000 | Taxable ₹1,00,000, IGST ₹18,000.40 | Clear within rounding tolerance | No one, logged |
| Taxable ₹1,00,000 | Taxable ₹90,000 | Propose as a value mismatch, do not clear | Purchase, against the GRN |
| CGST and SGST charged | IGST reported | Flag as a place of supply issue | Accounts, with the supplier |
| Invoice present | Not present | Park it, chase the supplier | Purchase, then finance |
| Not in books | Invoice present | Check for an unbooked bill before rejecting | Stores and accounts |
Two rules keep fuzzy matching safe. It may only propose within the same GSTIN, never across suppliers. And every automatic clearance outside an exact match is written to the log with the rule that cleared it, so a reviewer can see later why a line was passed.
Running the exception queue
A queue only works if every item has an owner and an age. Sort by tax value at risk, not by date, so the ₹4 lakh mismatch is not sitting behind forty small ones.
- In books, not in 2B. The credit is not available this period. Chase the supplier, and keep the record pending in IMS rather than rejecting it outright.
- In 2B, not in books. Usually a bill in transit, a document sent to a branch, or a wrong GSTIN at the supplier’s end. Find it before you act.
- Value or tax mismatch. Check the purchase order and the goods receipt note before you accept the supplier’s figure.
- Wrong tax head or place of supply. The supplier has to amend. Note the tax value at risk and the period.
- Credit notes. From the October 2025 tax period, IMS allows credit notes and certain amendments to be kept pending, with a defined limit of one tax period for monthly filers and one quarter for quarterly filers, after which an unacted record is deemed accepted. Watch that clock.
- Partial reversal. IMS now asks whether input tax credit needs to be reduced for a selected record and lets you declare the amount, with remarks mandatory where you reverse nothing or only part.
Supplier follow-up that works
Chasing is a monthly campaign, not a series of phone calls. Group by supplier rather than by invoice, send one statement per supplier listing exactly which documents are missing, in what period and for what tax value, and repeat it on a fixed day each month so suppliers learn the rhythm.
Escalate on money, not on age. A supplier holding up ₹6 lakh of credit gets a call from finance; one holding up ₹3,000 gets another email. Where a supplier has filed GSTR-1 but not GSTR-3B, tell them plainly what Rule 37A means for both of you.
The rules that make the audit trail matter
Three provisions decide how much a clean trail is worth.
Section 16(2)(aa) allows input tax credit only where the supplier has furnished the details of the invoice or debit note in their statement of outward supplies and communicated it to you. A bill in your books that never reached the portal is not a credit.
Section 16(4) sets the outer limit: credit for an invoice or debit note cannot be taken after the thirtieth day of November following the end of the financial year to which it relates, or the date of furnishing the annual return, whichever is earlier. Records kept pending in IMS can be availed later, but not past this limit.
Rule 37A covers the supplier who reported the invoice in GSTR-1 but did not file GSTR-3B for that period by the 30th of September following the financial year. You must reverse that credit in a GSTR-3B filed on or before the 30th of November following the end of that financial year, failing which it is payable with interest under section 50. If the supplier later files, you can re-avail it.
For each of those you need, per invoice: which pass matched it, what tolerance was applied, what action you took in IMS and when, who approved an exception, what the supplier was told, and in which return the credit was claimed, reversed or re-availed. That record is the difference between answering a notice in an afternoon and rebuilding a year of workings.
If you want the underlying return mechanics first, we set them out in how GSTR-1, GSTR-2B and GSTR-3B fit together.
Frequently asked questions
Can we simply claim what GSTR-2B shows?
No. GSTR-2B tells you what your suppliers reported. Your books tell you what you actually bought and received. Credit depends on both, plus the other conditions in section 16, including receipt of the goods or services.
Should we reject records in IMS that we cannot find?
Pending is usually the safer action while you investigate, because a record kept pending can be acted on later within the section 16(4) limit. Rejecting is a decision, so make it deliberately and record the reason.
How far can we push automatic clearance?
As far as exact and normalised matches take you, which on a stable vendor base is most of the volume. Everything with a value, tax head or place of supply difference belongs with a person, because those are the ones that turn into notices.
What about credits from earlier years?
Time limits under section 16 have changed more than once in recent years, including a special dispensation for early financial years. Check the current provision and the relevant notification for anything not belonging to the current year rather than relying on a rule of thumb.
Where to start
Take last month’s closed reconciliation, run it through an automated pass, and compare what cleared automatically against what your team cleared by hand. That number tells you the size of the prize. AI Solutions by AIMatric reconciles vendor invoices against GSTR-2B at volume, pushes exceptions to your team and keeps the audit trail, beginning with a free 30-minute process audit.
