Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
The vendor has emailed the GSTR-1 acknowledgement — ARN in hand, return marked filed for the tax period. The purchase register in your ERP shows a Rs 2.4 lakh invoice from the same vendor for the same period. But the GSTR-2B for that period shows zero against the vendor's GSTIN, and the controller wants an answer before the Day 15 ITC sign-off. Escalating to the vendor before checking the six common causes wastes a day and produces a defensive email chain; skipping the check altogether and claiming the ITC anyway breaches Rule 36(4) and exposes the return to a DRC-01C mismatch notice.
The gap between purchase register and GSTR-2B almost always falls into one of six buckets. First — the vendor filed but for the wrong tax period (quarter drift, invoice-date miscategorisation, or filing-cycle timing). Second — the vendor filed against the wrong recipient GSTIN (multi-GSTIN mix-up, group entity substitution). Third — an IMS Reject action was taken mid-cycle by someone on your own team and the invoice dropped from the current period's GSTR-2B. Fourth — the vendor is under the QRMP scheme and third-month invoices legitimately appear only in the quarterly GSTR-1 the following month. Fifth — the specific invoice was not uploaded inside the return (the return was filed for other invoices but this one was missed at the sub-form level). Sixth — the vendor's own supplier defaulted on GSTR-3B and Rule 37A is cascading a reversal down the chain.
Three checks before escalation, in order of speed. Check the invoice date against the vendor's filing period. Verify the GSTIN on the invoice against the vendor's actual registered GSTIN. Pull the IMS action log for the invoice. Only after all three checks pass, send the vendor the follow-up letter with the exact ask — a screenshot of the invoice line inside the filed GSTR-1 dashboard, not just the return-level ARN. Track every at-risk invoice against the November 30 Section 16(4) deadline with a 30/60/90-day escalation ladder that terminates in August rather than October so there is genuine recovery time.
Every missing invoice carries a category tag from the six-bucket taxonomy, an owner, an age, and a next-escalation date. The 6-bucket categorisation completes within an hour of the Day 12 GSTR-2B pull. The at-risk queue against the November 30 deadline is refreshed weekly rather than surfaced in November when it is too late. The vendor follow-up cycle runs from a standard letter pack rather than a bespoke email per case. The Day 15 controller sign-off knows exactly how many rupees of at-risk ITC are exposed and against which vendors, and Rule 37A cascading reversals are caught before they become a return-side surprise.
Your vendor emailed the acknowledgement at 4pm. ARN in hand. GSTR-1 marked filed for July. You pull the GSTR-2B on the 15th and search for the vendor’s GSTIN. Nothing. The purchase register in the ERP shows a Rs 2.4 lakh invoice from the same vendor dated July 22, IGST at 18 per cent, GSTIN captured correctly at the invoice entry. But the GSTR-2B for July shows zero against that GSTIN. The controller wants an answer before the Day 15 sign-off, and the sales team just forwarded a chase email from the vendor asking why you have not released his payment.
The gap between what your vendor swears he filed and what actually lands in your GSTR-2B is the single most common reconciliation dispute in the Indian GST regime. It rarely means the vendor is lying. It almost always falls into one of six buckets — and only one of them is a genuine vendor lapse. Working through the buckets in the right order takes under an hour and closes 90 per cent of cases without a shouting match.
The quick answer
Before you escalate, run three sixty-second checks: (a) does the invoice date actually fall inside the tax period your vendor filed for; (b) does the GSTIN on the invoice match the vendor’s actual registered GSTIN; (c) has anyone on your own team hit Reject on the invoice inside the Invoice Management System. If any of those three fails, the vendor is not the problem — the fix is on your side or a calendar drift, and the invoice will land in the next GSTR-2B once corrected. Only if all three pass do you send the follow-up letter and ask for the specific invoice-line screenshot from inside the vendor’s filed GSTR-1 dashboard.
Bucket 1 — Vendor filed, but for the wrong tax period
This is the most common cause and the easiest to miss. The vendor filed GSTR-1 for July with 47 invoices — but the specific Rs 2.4 lakh invoice was uploaded against the August tax period because it was dated July 31 and got picked up in the following month’s cycle. The ARN and the return-filed status the vendor sent you are both correct. The invoice is genuinely in a filed GSTR-1 — just not the one you are reconciling.
Where to look: ask the vendor for a screenshot of the invoice line inside the GSTR-1 dashboard, showing the tax period the invoice was uploaded against. If the screenshot shows August rather than July, the invoice will appear in your August GSTR-2B on the September 14 generation cycle. What to do: tag the invoice as “GSTR-2B expected next month” in the at-risk queue and hold the ITC claim to the correct month. Do not claim the ITC in July without visibility — that breaches Rule 36(4).
Bucket 2 — Vendor filed against the wrong recipient GSTIN
A frequent cause in groups with multiple GSTINs across states. The vendor’s accounts executive picked the wrong GSTIN from a saved-payee list — usually the group parent GSTIN when the supply was actually to a state-level operating subsidiary, or the old GSTIN from before a restructure. The return is filed, the ARN is genuine, the invoice is in GSTR-1 — just against a GSTIN that is not yours.
Where to look: verify the GSTIN on the invoice PDF against your actual registered GSTIN using the CBIC GST portal search or a bulk GSTIN validator if the volume is high enough. If the GSTIN on the invoice differs from your registered GSTIN, or if the vendor’s screenshot shows a different GSTIN in the recipient column of the filed return, this is Bucket 2. What to do: request a credit note against the wrong-GSTIN invoice and a fresh correctly-addressed invoice. Do not attempt to claim ITC against an invoice that names a different GSTIN — the mismatch is caught at the DRC-01C stage.
Bucket 3 — Someone on your team hit Reject in IMS
Since October 2024, every inbound invoice must be actioned as Accept, Reject, or Pending in the Invoice Management System before the recipient’s GSTR-2B is generated on the 14th of the following month. A Reject action removes the invoice from the current month’s GSTR-2B. Re-Accepting in the same tax period does not always restore it to the same period’s GSTR-2B — the invoice may only reappear in the subsequent month.
The failure mode is usually a junior executive experimenting with the IMS dashboard, or a Reject taken against a genuinely disputed invoice that was later resolved without reversing the IMS action. Where to look: pull the IMS action log for the invoice and check whether Reject was ever recorded. What to do: if the Reject was accidental, document the reason on the IMS working paper, request the vendor to re-upload or amend via the amendment cycle, and defer the ITC to next month. The IMS vs GSTR-2B three-way match logic documents the specific action-reversal mechanics.
Bucket 4 — The vendor is under the QRMP scheme
The Quarterly Return Monthly Payment scheme is available to suppliers with aggregate turnover up to Rs 5 crore in the preceding financial year. A QRMP-scheme supplier files GSTR-1 quarterly, not monthly. He can upload invoices for the first two months of the quarter via the Invoice Furnishing Facility by the 13th of the following month — so a July invoice from a QRMP supplier can still appear in your July GSTR-2B on the August 14 generation if the vendor used IFF. But there is no IFF in the third month of the quarter (September, December, March, June). A September invoice from a QRMP supplier can only appear via the quarterly GSTR-1 filed by October 13, which means the invoice lands in your October GSTR-2B on November 14 — roughly 45 days after the invoice date.
This is not a lapse; it is how the scheme works. Where to look: track vendor QRMP status in your master data. Any third-month invoice from a QRMP vendor is expected-late. What to do: flag the invoice as “QRMP third-month, expected in Q+1 GSTR-2B” and hold the ITC claim. Do not chase the vendor — the return is not yet due.
Bucket 5 — The return was filed but this specific invoice was missed
The vendor filed GSTR-1 on time. He uploaded 46 out of 47 invoices for the month. The Rs 2.4 lakh invoice you are looking for was the one that got missed at the sub-form level — a data-entry oversight, a validation failure that the vendor’s team never came back to fix, an ERP-to-portal integration that dropped the row. The ARN and return-filed status are both real; the specific invoice inside the return is not.
Where to look: ask the vendor for the specific invoice-line screenshot from inside the filed GSTR-1 dashboard. If the invoice is not visible in his own dashboard for that period, this is Bucket 5. What to do: request an amendment via GSTR-1A or Table 9A in the following month’s GSTR-1 to add the missing invoice. This is a genuine vendor lapse — pull the vendor GSTR-1 follow-up letter templates and send the standard structured request rather than a bespoke email. The follow-up letter pack has the exact ask that gets action rather than defensiveness.
Bucket 6 — Rule 37A cascade from the vendor’s own supplier default
The rarest bucket, but the most damaging when it fires. Rule 37A cascades a reversal down the supply chain when a supplier who reported an invoice in GSTR-1 fails to file GSTR-3B for the same period by September 30 of the following financial year. Your ITC is reversed on November 30 for a default that happened two tiers away — your vendor filed his GSTR-1 correctly, but his supplier’s GSTR-3B lapse cascades into your books.
Where to look: this is not visible on your GSTR-2B directly, but shows up as a Rule 37A reversal notification or as an unexplained ITC adjustment in the September–November window. The Rule 37/37A cascading reversal treatment walks through the exact mechanics and the working-paper trail. What to do: escalate to the vendor’s tax head with a request that they chase their own supplier before September 30, and provision for the reversal in your ITC forecast if the chain does not close.
The one to escalate first — the Section 16(4) permanent-loss risk
If the missing invoice is dated in the current financial year and the tax period has not yet passed the November 30 following-year deadline, you have runway. If the missing invoice is dated in the previous financial year and November 30 is inside 30 days, this is the escalation that jumps every other queue. Section 16(4) is a permanent-loss deadline — an invoice not visible in GSTR-2B by November 30 that is claimed anyway breaches Rule 36(4) and the DRC-01C notice that follows disallows the credit and adds interest and penalty. For a Rs 2.4 lakh invoice at 18 per cent IGST, the exposure is a Rs 43,200 credit permanently lost, plus interest under Section 50 at 18 per cent per annum from the date of original wrong claim, plus penalty of 10 per cent under Section 122.
The ladder that keeps the deadline from ambushing you: Tier 1 at 30 days after the missing invoice is first noticed — analyst-level vendor follow-up with the standard letter. Tier 2 at 60 days — finance-manager escalation to the vendor’s tax head. Tier 3 at 90 days or by August 30 for a March invoice, whichever is earlier — controller-level provisioning entry and a written note to the CFO with the exposure quantified.
When your manual checking outgrows itself
Six buckets, three sixty-second checks, a vendor follow-up letter, an escalation ladder — the manual discipline works cleanly up to about 100 to 150 vendors under GSTR-2B. Above that threshold, the at-risk queue against the November 30 deadline needs to be refreshed continuously rather than pulled once a month, the IMS action log needs to be monitored for accidental Reject actions in near-real-time, and the QRMP-vendor watchlist needs to update automatically as vendors’ turnover crosses the Rs 5 crore threshold. Terra Insight’s GST reconciliation software treats the bucket-categorisation and the at-risk-ITC queue as first-class continuously-refreshed outputs rather than a spreadsheet the analyst maintains by hand — the manual discipline in this article keeps its role as the training the system runs against.
Go deeper
- Rule 37 and Rule 37A cascading reversal — the technical treatment of Bucket 6
- Invoice Management System reconciliation — the IMS action layer above Bucket 3
- IMS vs GSTR-2B three-way match logic — the three-way match method
- Vendor GSTR-1 follow-up letter templates — the exact letters for Buckets 1, 2, and 5
- Section 16(4) ITC time bar — the November 30 permanent-loss anchor
- Vendor GSTR-1 follow-up letter pack — the downloadable pack
- Vendor GSTIN bulk validator — the tool for Bucket 2
Frequently Asked Questions
My vendor sent me the GSTR-1 acknowledgement (ARN) and the invoice still is not in GSTR-2B — is he lying?
Almost never. The far more common explanation is that the vendor filed the return but the specific invoice inside the return was uploaded against the wrong month or the wrong GSTIN. Ask the vendor to send a screenshot of the invoice line inside the GSTR-1 dashboard — not just the ARN. If the screenshot shows the invoice against a different tax period than yours, the vendor filed but for the wrong month, and the invoice will land in your GSTR-2B for that other month rather than the one you are reconciling. If the screenshot shows the invoice against a different GSTIN in the recipient column, the vendor filed against the wrong GSTIN and you will need a credit note plus a fresh correctly-addressed invoice.
If my vendor is under QRMP, when will his July invoice show in my GSTR-2B?
It depends on which month of the quarter the invoice is dated. Under the QRMP scheme (turnover up to Rs 5 crore), the supplier has the Invoice Furnishing Facility for the first two months of the quarter — invoices for July and August can be uploaded to IFF by the 13th of the following month and appear in your GSTR-2B on the 14th, exactly like a monthly filer. But invoices dated in the third month of the quarter (September, December, March, June) can only appear via the quarterly GSTR-1 filed by the 13th of the month after the quarter ends. A September invoice may not appear in your GSTR-2B until the October 14 generation cycle after the September quarter GSTR-1 is filed, and the delay is legal. Track vendor QRMP status in your master data and flag any third-month invoice from a QRMP supplier as expected-late.
Someone on my team rejected an invoice in IMS by mistake — can I still claim the ITC this month?
Usually not in the same tax period. A Reject action under the Invoice Management System removes the invoice from the current month’s GSTR-2B. Re-Accepting the same invoice within the same tax period does not always reinstate it to the same period’s GSTR-2B — the invoice may only reappear in the subsequent month’s GSTR-2B after the supplier re-uploads or amends via the amendment cycle. The immediate mitigation is a documented reason for the Reject on the IMS working paper and an amendment request to the vendor; the ITC will typically reappear in the next month’s GSTR-2B, but a stray Reject at the end of the November tax period against a March-financial-year invoice can push the visibility past the November 30 Section 16(4) deadline and cost you the credit permanently.
My purchase register shows Rs 2.4 lakh from this vendor but GSTR-2B shows Rs 0 — what should I actually do first?
Three sixty-second checks before any escalation. First, confirm the invoice date against your vendor’s filing period — if the invoice was dated July 31 and the vendor filed August GSTR-1, the invoice belongs to August GSTR-2B, not July. Second, verify the GSTIN on the invoice against the vendor’s actual registered GSTIN using the CBIC GST portal search or a bulk validator — the invoice may list your old GSTIN from before a multi-GSTIN restructure or list a group entity’s GSTIN by mistake. Third, check the IMS action log for the invoice — if anyone actioned Reject on it, that alone explains the zero. If all three checks pass, then send the vendor the follow-up letter and ask for the specific invoice line screenshot inside their filed GSTR-1.
How urgent is a March invoice that is missing from GSTR-2B — do I have time?
You have until November 30 of the following financial year and no longer. Section 16(4) of the CGST Act is a permanent-loss deadline — if the invoice is not visible in your GSTR-2B by November 30, and you claim the ITC without it being visible, the claim is disallowed under Rule 36(4) and the invoice becomes an expense in your books rather than a recoverable credit. For a March 15 invoice, you have roughly eight months to run the vendor follow-up cycle, escalate through the vendor’s tax head, and secure a corrected filing before the deadline closes. Working backwards from November 30 with a 30/60/90-day escalation ladder puts your Tier 3 CFO-level escalation at September, which is why the reconciliation playbook flags every at-risk March invoice by August 30 at the latest.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 16(4), Central Goods and Services Tax Act 2017 — A registered person shall not be entitled to take input tax credit in respect of any invoice or debit note for supply of goods or services or both after the thirtieth day of November following the end of the financial year to which such invoice or debit note pertains or furnishing of the relevant annual return, whichever is earlier. Where the supplier's GSTR-1 for the July supply lands in the recipient's GSTR-2B only after the November 30 cutoff, the ITC is permanently lost — the invoice becomes an expense in the recipient's books rather than a recoverable credit, and no vendor apology or subsequent portal correction reopens the entitlement.
- ▸ Rule 36(4), Central Goods and Services Tax Rules 2017 — Input tax credit availed by a registered person in respect of invoices or debit notes the details of which have not been furnished by the suppliers under Section 37 shall not exceed the amount of input tax credit available in respect of invoices or debit notes the details of which have been furnished by the suppliers under FORM GSTR-1 or through the Invoice Furnishing Facility. GSTR-2B is therefore a hard ceiling on the ITC that can be claimed in GSTR-3B Table 4, and any invoice not landing in GSTR-2B for the tax period cannot be included in the current month's claim regardless of what the vendor's acknowledgement email says.
- ▸ Rule 37A, Central Goods and Services Tax Rules 2017 — Where input tax credit has been availed by a registered person in the return in FORM GSTR-3B for a tax period in respect of such invoice the details of which have been furnished by the supplier under Section 37(1) in FORM GSTR-1, but the return in FORM GSTR-3B for such tax period has not been furnished by such supplier till the thirtieth day of September following the end of the financial year, the said amount of input tax credit shall be reversed by the said registered person while furnishing the return in FORM GSTR-3B on or before the thirtieth day of November following the end of the financial year. The cascade fires when the vendor filed GSTR-1 (invoice appears in GSTR-2B) but failed to file GSTR-3B by September 30, and the recipient is compelled to reverse the ITC despite having done nothing wrong.
- ▸ Notification No. 84/2020-Central Tax and Notification No. 85/2020-Central Tax — QRMP scheme — A registered person whose aggregate turnover in the preceding financial year is up to Rs 5 crore may opt to furnish FORM GSTR-1 quarterly with monthly Invoice Furnishing Facility for the first two months of the quarter. Under the QRMP scheme, an invoice raised in the third month of a quarter that the supplier does not upload via the Invoice Furnishing Facility (there is no IFF in the third month) only appears in the recipient's GSTR-2B when the quarterly GSTR-1 is filed by the 13th of the month following the quarter — a legitimate delay of up to 45 days between invoice date and the recipient's GSTR-2B visibility.
- ▸ Circular No. 170/02/2022-GST and related IMS notifications — Under the Invoice Management System live from October 2024, every inbound invoice must be actioned as Accept, Reject, or Pending before the recipient's GSTR-2B is generated on the 14th of the following month. A Reject action taken by any authorised user of the recipient GSTIN — including a junior accounts executive experimenting mid-cycle — removes the invoice from the current month's GSTR-2B, and re-Accepting it in the same tax period does not always restore it to the same period's GSTR-2B; the invoice may only reappear in the subsequent month's GSTR-2B after the supplier re-uploads or amends.