GSTR-2B Reconciliation: A Working Method for Matching Input Tax Credit

Input credit is only claimable once it appears in GSTR-2B. Here is a repeatable monthly method for matching the purchase register against it, and what to do with each category of mismatch.

Why This Reconciliation Exists

Input tax credit is no longer something you claim from your own records. It is claimable when the supplier has filed and the invoice appears in your auto-drafted GSTR-2B. That single change moved the risk from your bookkeeping to your suppliers' filing discipline. Your purchase register says you are owed credit; GSTR-2B says what the system will actually allow. The gap between the two is real money, and it is invisible until somebody sits down and matches the two lists line by line.

What You Are Actually Matching

Both sides are transaction lists keyed on the same few fields: supplier GSTIN, invoice number, invoice date, taxable value, and the tax split across CGST, SGST and IGST. A match requires all of them to agree closely enough. In practice the identifier that breaks most often is the invoice number, because suppliers format them inconsistently across months and your data-entry may have normalised them differently. Match on the combination rather than on any single field, and treat near-matches as a category to review rather than as failures.

The Four Buckets

Every reconciliation resolves into four outcomes, and each needs a different action. Matched: credit is safe, claim it. In your books but not in 2B: the supplier has not filed, or filed with a wrong GSTIN — chase them, because until they file this credit does not exist. In 2B but not in your books: you have missed recording a purchase, or the supplier has filed against your GSTIN in error — investigate before claiming. Matched but with a value difference: usually a tax-split error on one side, and usually the smaller of the two amounts is what you can safely claim.

Timing Differences Are Not Errors

A large share of first-pass mismatches are timing, not error. An invoice dated on the last day of the month may be filed by the supplier in the following period and appear in the next GSTR-2B. If you treat every unmatched line as a supplier problem you will spend the month chasing people who have done nothing wrong. Carry unmatched items forward into a running list and only escalate when a line has been outstanding across two or three periods. That list, not the monthly count, is what tells you which suppliers are genuinely unreliable.

Do It Monthly, Not Annually

The strongest argument for monthly reconciliation is not tidiness, it is recoverability. A supplier who has not filed can be chased in the same month while the relationship is live and the invoice is fresh. Chase the same person eleven months later and you are asking them to amend an old return for someone else's benefit. There is also a statutory outer limit on how late credit can be claimed for a financial year — check the current provision, because it has been amended more than once — and an annual reconciliation routinely discovers problems after that window has closed.

Common Causes of Mismatch

A handful of causes explain most differences. The supplier filed under the wrong GSTIN, which happens constantly for groups with multiple registrations. The invoice was recorded in your books under a slightly different number, often because a prefix or a leading zero was dropped. The tax was entered as a single total rather than split, so the individual heads do not match. The purchase was a reverse-charge or import transaction that follows a different path entirely. And ordinary duplicates on either side, which inflate both totals and make the summary look worse than it is.

Building the Working Paper

The output should be a working paper, not a verdict. It needs the two source rows side by side for every matched pair, the unmatched entries on each side listed separately, suspected duplicates called out, and a short reason recorded against every exception. That document is what you show a client to explain why their claimed credit differs from their expectation, and what your reviewer reads instead of re-performing the match. Export it, attach it to the file, and keep the prior month so the carry-forward list is traceable.

Automating the Mechanical Part

The matching itself is mechanical and should not consume a person. Download the 2B data, export the purchase register, map the columns once, and let software produce the four buckets. What cannot be automated is the judgement: deciding whether an unmatched line is timing or failure, whether a value difference is a rounding artefact or a real error, and which suppliers need a conversation. Automating the first part is what makes the second part affordable to do every month instead of once a year.