GSTR-2B vs Purchase Register Reconciliation: A Monthly Workflow That Survives Scrutiny

Input tax credit is now settled by one document: GSTR-2B. If your monthly claim doesn't reconcile to it, you are either losing credit you paid for, or claiming credit the department will ask back with interest. Here is the month-end workflow we run.

Why 2B, not 2A

GSTR-2A is a dynamic statement — it keeps changing as suppliers file or amend. GSTR-2B is static: generated once for each tax period, and it is the statement your ITC claim is tested against. Reconcile to 2B; use 2A only to investigate why something is missing from 2B.

The five-bucket reconciliation

Export your purchase register and the 2B for the period, match on GSTIN + invoice number (normalise formats first — prefixes, leading zeros and slashes cause most false mismatches). Every line lands in one of five buckets:

1. Matched — in books and in 2B, values agree. Claim.
2. In books, not in 2B — supplier hasn't filed or filed late. Credit is parked, not lost: hold the claim, chase the supplier, and track it to the 2B period in which it eventually appears.
3. In 2B, not in books — usually an unrecorded invoice (booked next month, or an expense bill sitting with a department). Record it or map it; never claim blind.
4. Value or tax mismatch — data-entry error on either side, or a supplier amendment. Resolve to the document.
5. Ineligible — appears in 2B but blocked (vehicle hire, food, construction and the rest of the Section 17(5) list, or credit belonging to another branch's GSTIN). Mark and exclude with a reason code.

The vendor follow-up tracker

Bucket 2 is where money leaks. Keep a running tracker per supplier: invoices pending in 2B, ageing, and follow-up dates. Two practical rules:

• Chase before the supplier's filing due date, not after — a reminder on the 8th of the month changes behaviour; one on the 25th doesn't.
• For repeat offenders, move to payment terms that release the tax portion only after the invoice reflects in 2B. Contracts can say this; most don't.

Documentation for the day a notice arrives

Officers increasingly issue ITC-mismatch notices generated from system data. What closes them quickly is a period-wise file: the 2B download, the purchase register, the reconciliation with bucket tags, and proof of subsequent-period claims for late-reflected invoices. Preserve these monthly — reconstructing three years later is painful and unconvincing.

Automating the mechanics

The matching itself is mechanical and automates well — spreadsheet lookups at low volume, purpose-built reconciliation tools or GSP-based utilities as volume grows. What should never be automated away is the review of exceptions: a person must own buckets 2 to 5 every month.

Educational content only, not professional advice. GST provisions, timelines and portal behaviour change frequently — verify the current legal position before acting. Last reviewed: August 2026.