This is a composite, illustrative scenario built from how a GSTR-2B mismatch typically resolves in practice, not an account of a named client. A client had claimed input tax credit on an invoice that did not appear in GSTR-2B for the relevant return period. The client's explanation — that the vendor had filed late and the credit would appear in a later period's 2B — was the correct explanation, but accepting it without verification would have meant taking the client's word for a fact that was independently checkable. Pulling the vendor's GSTR-1 filing history confirmed the invoice had in fact been filed, one return period late, which converted "probably a timing thing" from a plausible story into a documented fact the file could rely on.
Where it showed up
A routine reconciliation of the purchase register's claimed ITC against GSTR-2B for the year turned up one invoice, roughly thirty-one thousand rupees of credit, present in the client's books and claimed in the relevant GSTR-3B, but absent from the 2B statement for that period. Everything else on the vendor's account reconciled cleanly — this was the one line that didn't.
| Possible cause | What confirms it |
|---|---|
| Vendor filed late — credit appears in a later 2B | Vendor's GSTR-1 for a later period shows the invoice; the client's own later-period 2B carries it forward |
| Vendor never filed the invoice at all | No appearance in any subsequent period's 2B; a real risk of a disallowed claim under Section 16 |
| Wrong GSTIN or invoice number on either side | A near-match appears in 2B — same amount, different reference — once searched for directly |
| Credit note or amendment the client's books don't reflect | Vendor's filing shows a corresponding amendment or credit note that the client never booked |
"The vendor probably filed late" is a hypothesis, not a finding, until one of these is actually checked. Recording the client's explanation without checking it against the vendor's own filing history is the single most common way an ITC mismatch exception gets closed on the wrong basis.
How it was actually confirmed
- 01Checked the next two periods' GSTR-2B for the same invoiceFound it in the 2B issued one return period later — same invoice number, same amount, same vendor GSTIN. The vendor had filed, just not on time.
- 02Checked whether the client had claimed it again in that later periodThey had not — the credit had been claimed once, in the earlier period, based on the invoice date rather than the 2B appearance date. That is itself a timing question under Section 16, not a resolved one just because the invoice eventually showed up.
- 03Checked whether the claim period was still open to a noticeThe credit had been claimed before the relevant 2B reflected it, which is the specific fact pattern Section 16(2)(aa) addresses. Whether that claim stands depends on when the department's own matching caught up, not on whether the vendor eventually filed — a question for the client's tax advisor, flagged rather than resolved in the audit file.
What went into the working paper
- The original mismatch, the amount, and the period in which the credit was claimed.
- The vendor's GSTR-1 filing history extract, showing the late filing and the period it actually landed in.
- A note that the credit was claimed before 2B reflected it, with a reference to Section 16(2)(aa) rather than an audit conclusion on its validity.
- The matter referred to the client's tax advisor for a view on exposure, rather than the audit team forming its own tax position.
- A note on materiality: thirty-one thousand rupees, immaterial to the financial statements on its own, but worth checking whether it was one of several similar late-filing vendors rather than an isolated case.
Checking "was it one of several" mattered more than the single item. A second pass across the full ITC population, matched by vendor against their filing pattern over the year rather than by individual invoice, found two more vendors with the same late-filing habit — not large enough in aggregate to be material, but a pattern worth naming in the management letter as a vendor-compliance risk the client should monitor rather than discover again next year.
How we think about this
A single mismatch is a data point. Whether it is isolated or a pattern is the question that actually determines what belongs in the file — and answering it means reconciling the full ITC population against GSTR-2B, not following up individually on the one line a sample happened to surface. This is the specific thing Lekhya's GSTR-2B reconciliation is built to do by default.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- GST & GSTR-2BInvestigating ITC mismatches during auditA decision path for an ITC mismatch: available, eligible, still claimable. What the client can do about each outcome, and how to quantify credit at risk.
- GST & GSTR-2BGSTR-2B reconciliation: a practical guide for auditorsWhat GSTR-2B is, how the Invoice Management System changed it, the statutory conditions that govern input credit, and how to run and conclude the reconciliation.
- GST & GSTR-2BTwelve GST reconciliation mistakes that show up in audit filesPooling registrations, reconciling against 2A, stopping at March, netting categories and eight more errors, with what each causes and how to correct it.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.