GST ITC Reconciliation 2026

The Input Tax Credit (ITC) under GST is meant to be simple — pay GST on inputs, claim it back against output GST, net the difference. In practice, since the introduction of GSTR-2B as the static, auto-generated ITC statement and the tightening of matching rules under Section 16(2)(aa) and Rule 36(4), monthly ITC reconciliation has become the single biggest source of working-capital leakage and notice exposure for Indian businesses.

This is a working CA's walkthrough of how the matching actually works in 2026, what to do when a vendor files late or wrongly, why ITC gets auto-reversed, and the exact step-by-step reconciliation workflow we run for our clients each month. If you file GSTR-3B for a company doing more than ₹5 Cr of turnover, the rest of this is your monthly close playbook.

Why ITC reconciliation is no longer optional

Until 2021, businesses could claim provisional ITC against their books — pay vendor invoices, claim the GST in 3B, and reconcile later. That window is closed. The current regime, codified through successive amendments to Section 16 and Rule 36(4), has three hard gates that ITC must pass before it lands in your electronic credit ledger:

1. Tax invoice test (Sec 16(2)(a)): You must hold a tax-compliant invoice from a registered supplier.
2. Receipt of goods or services test (Sec 16(2)(b)): The goods or services must have actually been received.
3. Vendor reporting test (Sec 16(2)(aa) read with Rule 36(4)): The invoice must appear in your GSTR-2B — meaning the vendor must have filed his GSTR-1 / IFF and reported the invoice before your GSTR-3B due date.

It's the third gate that has changed the game. Before 2022, a 5–10% buffer was allowed for vendor non-reporting. Today the buffer is zero. If your vendor hasn't filed, you can't claim — even if you've paid him in full and have the invoice in hand.

How GSTR-2B actually gets generated

GSTR-2B is a static auto-drafted ITC statement that the GSTN system generates on the 14th of each month for the immediately preceding tax period. It pulls data from:

• GSTR-1 / IFF filings by your vendors (B2B invoices)
• GSTR-5 filings by non-resident taxable persons
• GSTR-6 filings from Input Service Distributors
• ICEGATE imports for Bill of Entry-based credits

The cut-off matters. If your vendor files his April GSTR-1 on 11th May (the standard due date), it shows up in your May GSTR-2B (generated 14th May) — which means you can claim that ITC in your May GSTR-3B (filed by 20th May). Easy.

But if the same vendor files his April GSTR-1 on, say, 16th May — three days late — the invoice will skip your May 2B entirely and only appear in your June 2B. Result: you wait an extra month for credit you've already paid for.

The four ITC sub-categories in your 2B

When you open your monthly 2B, the credits break out into four buckets. The CFO/Finance Controller must read each separately:

The four mismatches that bite you every month

In a clean month, your purchase register equals your 2B equals your 3B claim. In real life, the four common mismatches show up reliably:

1. Invoice in books, not in 2B (vendor late filer)

Your AP team has booked the invoice; you've paid the vendor; but the invoice doesn't show up in 2B. The vendor either hasn't filed his GSTR-1, or filed it after the cut-off, or filed under the wrong GSTIN.

Workflow: Don't claim. Park the ITC in a "deferred credit" reconciliation tracker. Email the vendor with a copy of the invoice and your GSTIN. Most legitimate suppliers respond within 7 days. If silence persists, follow your vendor escalation matrix and consider freezing future PO releases against that vendor.

2. Invoice in 2B, not in books (ghost invoice)

The 2B shows ITC against an invoice your AP team has no record of. Possible causes: the invoice is genuine but mis-routed (sent to a different GSTIN within your group), or someone has fraudulently filed against your GSTIN, or it's a duplicate from the vendor.

Workflow: Investigate before claiming. Reach out to the vendor for the underlying invoice copy, lorry receipt, and proof of delivery. If the invoice is genuinely yours, book it. If not, do not claim — you'll be liable to reverse plus interest plus penalty if assessment officers later disallow it.

3. Tax-amount mismatch

The invoice appears in 2B but the tax amount is different from your books. Usually a vendor entry error — wrong rate, wrong tax head (CGST/SGST vs IGST), or rounding.

Workflow: Claim the lower of the two amounts. Notify the vendor to file a credit note or amendment. The deferred portion stays in the reconciliation tracker until the vendor's amended GSTR-1 flows through.

4. POS / place-of-supply mismatch

The vendor has reported your supply as inter-state when it should be intra-state, or vice versa. This is more common than people realise — especially when the invoice billing address and the actual delivery address differ.

Workflow: Don't claim until corrected. Wrong tax head means your books and the vendor's books will never reconcile, and the credit will not appear in the right ledger (CGST/SGST vs IGST) when the assessment officer cross-checks.

The 180-day rule: Rule 37 and what triggers it

Even if you've crossed all three Section 16(2) gates and the credit is sitting in your electronic credit ledger, GST law has a 180-day payment condition. Under Rule 37, if the invoice value (including tax) is not paid to the vendor within 180 days of the invoice date, you must reverse the ITC already claimed, with interest under Section 50 from the date the credit was originally claimed.

The 180 days are calendar days, not working days, counted from the invoice date — not the due date, not the booking date. Once you make the payment, you can re-claim the credit, but the interest already accrued is final.

What "payment" means under Rule 37

A few practical clarifications:

• TDS/TCS deducted from vendor: Counts as payment to the extent deducted, since it's deemed paid to the vendor.
• Setoff against debit note / credit note: Allowed, treated as payment.
• Related-party transactions: Mere journal-entry settlement against intercompany loans is not "payment" for Rule 37 purposes — actual transfer of consideration is required.
• Disputed invoices: If you've raised a debit note disputing the supply, the disputed portion is excluded from the 180-day calculation.

The monthly reconciliation workflow that we actually run

Here is the closing workflow we run every month for clients between the 14th (when 2B drops) and the 20th (3B due date):

Step 1 — Day 14: Pull and reconcile

The moment the 2B drops, finance ops pulls it as JSON from the GST portal. We use a Tally / Zoho / SAP add-on (or a custom Python reconciler for larger clients) to do an invoice-level VLOOKUP against the purchase register. The tool produces five buckets:

• ✓ Matched — invoice and tax both reconcile
• ⚠ Books only — vendor late filer (Mismatch 1)
• ⚠ 2B only — ghost invoice or mis-routing (Mismatch 2)
• ⚠ Tax mismatch — same invoice, different tax (Mismatch 3)
• ⚠ POS mismatch — wrong place of supply (Mismatch 4)

Step 2 — Days 14–17: Vendor follow-up

Books-only items get an automated email to the vendor with the invoice copy attached. Most respond within 48 hours and either confirm they'll amend the next GSTR-1 or send proof that they've already filed correctly. Repeat offenders (vendors with >2 mismatches in a quarter) get flagged for procurement review.

Step 3 — Day 18: Provisional 3B draft

We draft 3B with only the matched ITC plus any 2B-only items confirmed legitimate. Books-only items are parked. The draft goes to the CFO with a one-page reconciliation summary showing total ITC available, total claimed, and total deferred.

Step 4 — Day 19: 180-day reversal scan

Before filing, we scan the AP ledger for any invoices older than 180 days that remain unpaid. Those ITC amounts go into the 3B "Reversal" line under Rule 37. Interest is computed and self-paid in the same return.

Step 5 — Day 20: File 3B

3B filed. Reconciliation tracker archived with vendor follow-ups carried forward to the next month's tracker.

What the FY 2026 amendments changed

Three regulatory changes have hit ITC reconciliation in the last 18 months:

1. Sequential filing of returns: You can no longer file GSTR-3B if your previous month's 3B is unfiled. This forces clean reconciliation discipline.
2. Mandatory e-invoicing threshold: Lowered to ₹5 Cr aggregate turnover. Most B2B vendors are now under e-invoicing, which means fewer manual GSTR-1 errors and faster 2B population.
3. ITC blocking under Rule 86A: Officers can now block your electronic credit ledger if vendor verification fails. Practical effect: you can't even claim matched ITC if the vendor's registration is suspended or under investigation.

The audit-defence playbook

When the GST officer issues an ASMT-10 notice or scrutiny, the file you'll need is the monthly reconciliation tracker for the period under question. Specifically:

• Month-by-month reconciliation showing the four buckets
• Vendor email correspondence for any deferred credits
• Rule 37 reversal calculations with interest workings
• Bank statements / payment proofs for any invoices older than 180 days
• POS / addressing documentation for any mismatch corrections

If the reconciliation file is well-maintained, an ASMT-10 typically closes within 30–60 days. Without it, expect a Show Cause Notice under Section 73 with interest plus penalty plus a defence cycle of 6–18 months.

Where most companies trip up

Across the engagements we've handled in the last two years, four patterns explain almost every ITC notice we've defended:

1. No reconciliation tracker. AP team pays vendors, claims ITC against books, and assumes it'll match. It rarely does.
2. 180-day rule ignored. Disputed invoices, retentions, and intercompany payables sit on the books beyond 180 days; ITC continues to be claimed; interest accrues quietly.
3. Vendor master not cleaned. Wrong GSTINs, suspended vendors, and inactive registrations stay in the system. ITC against any of these is automatically wrong.
4. POS errors in services. Especially for pan-India software / subscription services — the wrong state is captured as place of supply, ITC lands in the wrong ledger, and the matching fails silently.

Bottom line

ITC reconciliation in 2026 is a closing-cycle activity, not a year-end project. The companies that get it right run a five-day cycle every month between 2B drop and 3B filing, maintain a vendor-mismatch follow-up tracker, and treat Rule 37 as a hard cash-flow gate. The companies that don't pay for it twice — once in working capital tied up in deferred credits, and once in interest plus penalty when the assessment officer comes knocking.

If your monthly close runs without a structured reconciliation file, this is the workflow that needs to be in place before the next 3B due date.

Disclaimer: This article reflects the regulatory position as of May 2026 and is intended as general advisory commentary. It is not a substitute for tailored professional advice. For specific situations, please consult a qualified Chartered Accountant or your GST advisor.