GSTR-2B reconciliation in 2026: what changed, what breaks, and how to automate it
A practical guide to GSTR-2B vs purchase-register reconciliation under IMS, hard-locked GSTR-3B and Rule 37A, with a workflow CA firms can automate end to end.
By DotZero Research
If you run a CA practice or an SME finance team, GSTR-2B reconciliation is probably the single largest block of recurring hours in your month. ICAI’s own AI use-case library puts it at 2 to 3 hours per client per month for a client with 200 to 300 purchase invoices. A 30-client practice spends 60 to 90 hours a month matching invoices that, in most cases, match perfectly.
Three changes in 2025 and 2026 turned this from a chore into a risk.
What changed
GSTR-3B liability is hard-locked. From the July 2025 tax period, the auto-populated liability in Tables 3.1 and 3.2 of GSTR-3B can no longer be edited. Corrections go through GSTR-1A before 3B is filed. ITC in Table 4 is still editable as of October 2026, but GSTN has signalled that locking is the direction of travel, and any claim above 2B is now a visible anomaly.
The Invoice Management System (IMS) is live and has teeth. Every invoice a supplier reports in GSTR-1 appears on your IMS dashboard, where you accept, reject or keep it pending. From the October 2025 tax period, credit notes can be kept pending and you must declare the ITC reduction. Do nothing and the invoice is deemed accepted when 2B is generated on the 14th. Deemed acceptance of a wrong invoice is your problem, not the supplier’s.
The three-year filing bar is enforced. Since November 2025, returns whose due date is more than three years old are permanently blocked on the portal. Old reconciliation gaps can no longer be fixed “later”.
Add Rule 37A, which requires you to reverse ITC by 30 November of the following year if the supplier never filed GSTR-3B, and Rule 37, which reverses ITC on invoices unpaid for 180 days, and you have a monthly process with real money attached.
The five outcomes of a match
Every row in a reconciliation lands in one of five buckets. Naming them precisely is what makes automation possible.
| Outcome | What it means | Action |
|---|---|---|
| Matched | GSTIN, invoice number and taxable value agree | Accept in IMS, claim |
| Amount difference | Same invoice, different value | Usually a credit note or rate change. Keep pending in IMS until traced |
| In 2B, not in books | Supplier reported an invoice you have not booked | Verify goods receipt. Book it, or reject in IMS |
| In books, not in 2B | You booked it, supplier has not filed | Hold ITC (Rule 37A risk). Remind the supplier |
| Reference mismatch | Same invoice, number formatted differently (INV/0781 vs INV-0781) | Normalise and match. Fix the books |
The last bucket is where most “manual” reconciliation time goes. A human sees that DF/0781 and DF-0781 are the same invoice instantly. Excel does not. Software that normalises references before matching removes most false mismatches on day one.
A workflow that can run without you
Here is the pipeline we build for CA firms. Each step runs automatically; humans see only exceptions.
- Pull. GSTR-2B and IMS data come in through a GSTN-authorised GST Suvidha Provider (GSP), with OTP consent from the taxpayer. No portal passwords, no scraping.
- Extract the purchase register. From TallyPrime via its XML interface, from Zoho Books via API, or from the client’s Excel. Including the ones that arrive as WhatsApp photos.
- Match. Exact match first, then normalised references, then fuzzy match on GSTIN plus date plus value within tolerance.
- Classify and explain. Each mismatch gets a bucket and a one-line reason in plain English. “Books show ₹2,85,000 vs 2B ₹2,58,000. Likely credit note. Keep pending.”
- Propose IMS actions. Accept the matched set, keep amount differences pending, flag the in-2B-not-in-books set for a goods-receipt check.
- Chase suppliers. For every invoice in books but not in 2B, a WhatsApp or email message goes to the supplier naming the invoice, with escalation after three days.
- Compute the safe claim. ITC available in 2B, ITC per books, the amount safe to claim this month, and the amount on hold under Rule 37A.
- Hand over. The CA reviews a one-page summary and the exception list, not 300 rows.
You can see this running on sample data in our accounting demo.
What this is worth
For a 30-client practice at 2.5 hours per client, automation that leaves 20 minutes of review per client recovers roughly 65 hours a month. At a loaded cost of ₹350 an hour that is about ₹2.7 lakh a year in staff time, before counting the ITC that stops leaking because suppliers are chased on the 15th instead of the 19th.
The larger benefit is the one firms mention after three months: deadline week stops being a crisis. When reconciliation is done by the 15th, GSTR-3B on the 20th is a review, not a scramble.
Where to start
Pick the one client with the messiest purchase register. If the automation works there, it works everywhere. Bring that client’s September purchase register and 2B to a working session and we will reconcile it live. Book a session.
Frequently asked
Is GSTR-2B reconciliation mandatory every month?
What is the difference between GSTR-2A and GSTR-2B?
Can reconciliation be fully automated?
DotZero Research
We build and run AI automations for CA firms, finance teams and tender bidders in India, and write about the rules we automate. Corrections: hello@dotzero.in.