Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A mid-market finance team opens the September month-end review and discovers the GSTR-2B input tax credit reconciliation has not been run since April. Six months of GSTR-2B pulls sit archived but unreconciled against a purchase register that has grown by an illustrative 2,400 invoices at an average of Rs 18,000 each — an illustrative Rs 4.32 crore of unclaimed input tax credit sitting in the ERP with no matched status. Section 16(4) of the CGST Act will permanently forfeit any of this credit not claimed in GSTR-3B by the 30th of November following the end of the financial year — with no rectification, no condonation, and no refund mechanism. The finance team has exactly 90 days from 1 September to 30 November to recover, provision, or accept the loss on the backlog, and the recovery cannot begin without a structured 12-week sprint sequenced against the deadline.
Sequence the 90-day catch-up as four phases with named weekly deliverables. Weeks 1-2 freeze all new work, extract six months of GSTR-2B, IMS action logs, purchase register, and prior GSTR-3B filings, and size the backlog as an exposure map with a preliminary bucket estimate per month. Weeks 3-6 execute the retrospective three-way match one month at a time, oldest first — April in Week 3, May in Week 4, June in Week 5, July in Week 6 — categorising every invoice into the five buckets and computing net recoverable ITC after Rule 42 and 43 common credit, Rule 37 180-day non-payment, Rule 37A supplier-non-filing cascading reversal, and Section 17(5) block-class exclusion. Weeks 7-10 chase the at-risk queue produced at end of Week 6 through the Vendor GSTR-1 Follow-Up Letter Pack with three tiers of escalation. Weeks 11-12 return to the monthly cadence — the current month runs on the five-day runbook and the November 2026 GSTR-3B carries the recovered backlog ITC before the 30 November foreclosure.
Named owners for each phase — tax executive as the running owner, tax manager as the reviewer, controller as the sign-off gate and the CFO briefing point. A written freeze note from the controller on Day 1 of Week 1 that formalises the diversion of finance-team capacity from the current-month cadence. A sprint folder with the six-month GSTR-2B PDFs, IMS action logs, purchase register, and GSTR-3B filings archived under timestamps and hashes. A five-bucket categorisation table maintained per invoice across Weeks 3-6. An at-risk queue keyed to supplier GSTIN, invoice date, rupee value, and days remaining to 30 November, refreshed at end of each retrospective week. A tiered chase cadence in Weeks 7-10 — Tier 1 supplier reminder in Week 7, Tier 2 controller escalation in Week 8, Tier 3 pre-foreclosure notice signed by the CFO in Week 9. An Ind AS 37 provisioning framework for the residual that will not recover by 30 November.
By end of Week 12, the illustrative Rs 4.32 crore six-month backlog is resolved into three components — the recovered ITC (illustrative Rs 3.72 crore after chase) claimed in the November 2026 GSTR-3B before the Section 16(4) foreclosure; the DRC-03 reversal batch for Rule 37 and Rule 37A ITC availed against defaulting suppliers; and the Ind AS 37 provision for the residual unrecoverable amount. The at-risk queue for the current month (October 2026) is fresh against the FY 2026-27 Section 16(4) clock. The five-day GSTR-2B runbook is back on cadence from Week 11. The failure mode that produced the six-month backlog is logged in the reconciliation process design register so the failure class is caught before it accumulates again. The exposure is closed on the balance sheet and the working paper is defensible for a Section 143(3)(i) statutory audit.
The CFO opens the September month-end review and asks the question every finance manager dreads: when did we last run the GSTR-2B reconciliation? The tax executive checks the folder. The last signed-off working paper is dated 15 April 2026. Six months of GSTR-2B pulls have been extracted and archived but never reconciled. The purchase register has grown by an illustrative 2,400 invoices at an average of Rs 18,000 each — an illustrative Rs 4.32 crore of unclaimed input tax credit sitting in the ERP with no matched status against GSTR-2B. And Section 16(4) of the CGST Act will permanently forfeit any of this credit that is not claimed in GSTR-3B by 30 November 2026 — with no rectification, no condonation, and no refund mechanism.
This article is the 90-day catch-up plan — the 12-week sprint the tax analyst, tax manager, and controller run together to close the backlog before the Section 16(4) clock forecloses it. The specific week-by-week sequence, the illustrative rupee figures the working paper produces, the statutory anchor each week discharges, and the escalation trigger when a week cannot close.
The reconciliation playbook monthly close guide is the preventive discipline that stops a six-month backlog from forming in the first place. The GSTR-2B five-day runbook is the monthly cadence that closes the window inside five days. This sprint is the recovery discipline when both slipped.
Why 30 November is unforgiving
Section 16(4) is the only Severity 10 anchor in the GST reconciliation stack. Every other statute carries some correction pathway — Section 39(9) allows GSTR-3B amendments in a subsequent month, Section 168 allows the CBIC to extend deadlines by notification, Section 200A demand notices can be replied to and litigated. Section 16(4) has none of these. A March 2026 invoice whose ITC is not claimed in the GSTR-3B filed on or before 30 November 2026 becomes a permanent statutory loss, non-recoverable in any subsequent period, non-adjustable against any other credit, and non-eligible for refund.
From 1 September 2026, the tax team has exactly 90 days to Section 16(4) — 12 weeks of five working days each. The plan below allocates those 12 weeks against the six-month backlog with the illustrative Rs 4.32 crore exposure, and the exit condition is a signed-off ITC claim in the November 2026 GSTR-3B filed on or before 20 November 2026 to leave a 10-day buffer before the Section 16(4) foreclosure.
The sprint has four phases: Weeks 1-2 freeze and assess; Weeks 3-6 retrospective three-way match, oldest month first, using the three-way ITC recipe; Weeks 7-10 at-risk queue chase through the Vendor GSTR-1 Follow-Up Letter Pack; Weeks 11-12 return to cycle with a refresh of the GSTR-2B failure modes design layer so the failure that produced the backlog is caught next cycle.
Weeks 1-2 — Freeze and assess
The first two weeks are the freeze. No new AP booking touches the closed months. No new IMS actions are taken except for the current month. The controller signs a written freeze note on Day 1 of Week 1 explaining the diversion to the CFO and the business heads. Without the written freeze note, the sprint silently defaults to a part-time job around the current cadence and slides past 30 November.
Once frozen, the tax executive extracts everything.
- Six months of GSTR-2B PDFs and JSONs from the GST portal, April 2026 through September 2026, archived per month with a timestamp and a hash.
- Six months of IMS action logs from the IMS dashboard, exporting the action taken per invoice (Accept, Reject, Pending, or auto-defaulted to Accept).
- Six months of purchase register from the ERP with invoice number, invoice date, supplier GSTIN, taxable value, IGST, CGST, SGST, cess, HSN code, and AP booking date.
- Six months of GSTR-3B filings — the recipient’s own returns to establish what ITC has already been claimed. This is the baseline the retrospective walks against.
The assess step sizes the backlog by month. Illustrative April 2026 = 380 invoices at Rs 20,000 average = Rs 76 lakh; May = 410 invoices at Rs 19,000 = Rs 78 lakh; June through August similar; September = 430 invoices at Rs 17,000 = Rs 73 lakh. Total = an illustrative 2,400 invoices at Rs 18,000 average = Rs 4.32 crore of ITC exposure to be walked through the three-way match.
The Week 2 deliverable is the exposure map — every month with a rupee figure, an invoice count, and a preliminary bucket estimate (matched, at-risk, ghost or missed-AP, IMS-rejected, IMS-pending) derived from a coarse first-pass match. The controller formally approves the plan at end of Week 2. Escalation trigger: if the exposure map cannot be built by end of Week 2, the CFO is briefed that the November deadline will not be met without an additional resource or a scope reduction — typically dropping to a 4-month rather than 6-month recovery to buy time.
Weeks 3-6 — Retrospective three-way match, oldest first
Weeks 3, 4, 5, and 6 execute the three-way match on one month each, oldest first. Week 3 = April 2026; Week 4 = May; Week 5 = June; Week 6 = July. August and September fold into the current-cycle work in Weeks 11-12.
The method is the three-way ITC recipe — purchase register versus GSTR-2B versus IMS action log — categorised into five mutually exclusive buckets. The downloadable Three-Way ITC Workbook provides the working paper skeleton.
- Bucket 1 — matched. Invoice is in the purchase register, in GSTR-2B, and IMS-Accept was taken (or auto-defaulted to Accept). Illustrative April 2026 match rate is 65 per cent by value — Rs 49 lakh of the Rs 76 lakh April exposure lands in Bucket 1 and becomes claimable ITC. After Rule 42 and 43 common credit reversal, Rule 37 180-day non-payment reversal, and Section 17(5) block-class exclusion, the illustrative net April recovery is Rs 42 lakh — added to the November 2026 GSTR-3B Table 4 as prior-period ITC.
- Bucket 2 — at-risk. Invoice is in the purchase register but not in GSTR-2B — the supplier has not filed GSTR-1. Illustrative April at-risk = Rs 21 lakh. These invoices flow into the at-risk queue for the Weeks 7-10 chase.
- Bucket 3 — ghost or missed-AP. Investigated the same day. Illustrative April = Rs 3 lakh.
- Bucket 4 — IMS-rejected. Already rejected, no claim. Illustrative April = Rs 2 lakh.
- Bucket 5 — IMS-defaulted-to-Accept without verification. The most common failure mode in a six-month backlog — the IMS action window closed without any action taken by the tax team, so the invoice auto-flowed into GSTR-2B on the 14th. Every one of these needs a retrospective sanity check against the AP booking. Illustrative April = Rs 1 lakh, largely benign but each line is tested against the source invoice.
Weeks 3-6 also layer in the Rule 37A cascading reversal — for any supplier whose GSTR-3B for the closed month is unfiled by 30 September 2026, the ITC availed against their invoices has to be reversed with interest under Section 50. A supplier who missed the April 2026 GSTR-3B and continued to miss May, June, and July requires four months of cumulative reversal, surfaced together at end of Week 6.
Escalation trigger: any month that cannot close in its week. If Week 3 does not close April by end of the week, the sprint is compressed — either the tax executive works overtime through Week 4, or a second analyst is assigned, or the exposure map is revised down to the four newest months with the two oldest provisioned as accepted loss. The CFO is briefed at the trigger, not at Week 10 when Section 16(4) has already foreclosed the option.
Weeks 7-10 — At-risk queue chase against 30 November
By end of Week 6, the at-risk queue is finalised. Illustrative total = Rs 68 lakh across the six closed months, distributed as roughly Rs 21 lakh April, Rs 15 lakh May, Rs 12 lakh June, Rs 8 lakh July, Rs 7 lakh August, and Rs 5 lakh September. Weeks 7-10 are the chase.
The chase runs on the Vendor GSTR-1 Follow-Up Letter Pack established in the vendor GSTR-1 follow-up letter templates article. The pack provides three tiered letters — supplier reminder, controller escalation, and pre-Section 16(4) foreclosure notice — each carrying the invoice number, invoice date, taxable value, and days remaining to the 30 November deadline. The pack also carries the Rule 37A trigger warning as a supplier-facing motivator — the letter states that the supplier’s continued non-filing will force the recipient to reverse the ITC with interest under Section 50 and to record the cascading loss in the Section 143(3)(i) audit working papers.
The chase cadence is prioritised by rupee value multiplied by days remaining. Week 7 dispatches Tier 1 letters on every Rs 68 lakh at-risk invoice under the tax executive’s name. Week 8 dispatches Tier 2 letters on any invoice that has not received a filed GSTR-1 by end of Week 7 — Tier 2 is signed by the controller. Week 9 dispatches Tier 3 pre-foreclosure notices on any invoice above Rs 1 lakh that is still not filed by end of Week 8 — Tier 3 is signed by the CFO and copied to the vendor’s key account owner in procurement.
Week 10 closes the chase and finalises the recovered versus unrecovered split. Illustrative recovery — Rs 51 lakh of the Rs 68 lakh at-risk queue lands in Bucket 1 as suppliers file the missing GSTR-1s under chase pressure. The remaining Rs 17 lakh is the unrecovered residual — the tax executive prepares the DRC-03 batch for Rule 37A ITC reversals on the unrecovered suppliers, and a DRC-01C ITC mismatch response draft in case the portal fires a Rule 88D auto-notice on the current-period claim.
Escalation trigger: unrecovered above Rs 20 lakh or Rule 37A cascading exposure above Rs 15 lakh triggers a CFO briefing and an Ind AS 37 provision against the November close.
Weeks 11-12 — Back on cycle
The catch-up sprint ends at end of Week 10. Weeks 11-12 return the finance team to the monthly cadence.
Week 11 picks up the current month (October 2026) on the five-day GSTR-2B runbook — IMS actions on Day 11, GSTR-2B pull on Day 12, three-way match on Day 13, reversals and blocks on Day 14, controller sign-off on Day 15. The at-risk queue for October is a fresh queue against the FY 2026-27 Section 16(4) clock — 30 November 2027 is the foreclosure date for FY 2026-27 invoices, and the queue starts clean.
Week 12 files the November 2026 GSTR-3B on 20 November — carrying the recovered ITC from Weeks 3-10 (illustrative Rs 3.72 crore of the Rs 4.32 crore backlog after chase recovery, net of Rule 42/43, Rule 37/37A, and Section 17(5) exclusion) as prior-period ITC, and the November current-month ITC on top. The November 2026 GSTR-3B is the last window for the backlog to appear before the 30 November Section 16(4) foreclosure.
The final Week 12 deliverable is the failure-mode update against the GSTR-2B ITC reconciliation failure modes design layer — the failure that produced the six-month backlog is logged in the reconciliation process design register so the five-day runbook catches the class before it accumulates again. Without this closing step, the sprint fixes the symptom and leaves the underlying failure in place — and the same six-month backlog re-forms next year.
The exception — if the sprint cannot close by 30 November
The plan above assumes the sprint executes on schedule. Real teams miss dates. If, by end of Week 10, the at-risk queue is materially larger than Rs 68 lakh or the retrospective match has not closed all six months, the exception protocol activates. The controller and CFO make one of three decisions.
- Provision the unrecovered residual as an accepted loss. Under Ind AS 37, an ITC that will not be recovered before the Section 16(4) foreclosure is provisioned in the current period as an expense. The provision closes the exposure on the balance sheet and moves the residual out of the ITC ledger. This is the default option and is used for the illustrative Rs 17 lakh residual in the plan above.
- Extend the November 2026 GSTR-3B filing to 30 November. The statutory GSTR-3B due date is the 20th of the following month, but Section 16(4) permits ITC claim in any GSTR-3B filed on or before 30 November. Filing on 30 November rather than 20 November buys 10 more days of chase — for a large residual, this may recover a further Rs 5-10 lakh from suppliers who file at the last minute. The trade-off is late-filing interest under Section 50 and the opportunity cost of the finance team’s continued diversion.
- Recast the plan to a 4-month recovery. For a backlog too large to recover the two oldest months, the plan is revised to recover months 3-6 fully and to provision months 1-2 as accepted loss. This limits the recovery scope to what is achievable and produces a defensible working paper for the statutory audit.
None of the three options avoids the Section 16(4) foreclosure. All three are exit protocols that manage the residual under statutory constraints — the decision is which residual the CFO chooses to absorb.
When the manual sprint outgrows itself
The 12-week catch-up sprint is a recovery discipline for a mid-market finance team with roughly 200 or fewer active vendors on a single GSTIN, a six-month backlog of manageable volume, and a controller willing to divert two months of finance-team capacity to close it. Three thresholds break the sprint.
- Backlog longer than six months. A 9-month gap crosses into a prior financial year for its oldest invoices, and the Section 16(4) foreclosure has already permanently closed the credit on those months — the sprint becomes a provisioning exercise rather than a recovery, and the residual runs into the crore range rather than the tens of lakhs.
- Vendor count above 500 or multi-GSTIN complexity. The retrospective three-way match across 500-plus vendors on a single GSTIN cannot fit into 4 weeks; the cross-GSTIN reconciliation across two or three related entities cannot fit into 12 weeks at all.
- Recurring backlog. A six-month gap that appears once is a bad quarter. A six-month gap that appears every year is a broken process — and the sprint is a symptom, not the cure.
At all three thresholds, the value of a continuously refreshed reconciliation surface is that the backlog is prevented rather than recovered — the at-risk queue becomes a first-class continuously refreshed output against the Section 16(4) clock, the IMS action monitoring runs daily rather than monthly, and the vendor GSTR-1 follow-up cadence runs on a rolling calendar rather than a monthly batch. The reconciliation playbook pillar documents the operational cadence the sprint returns the team to, and TransactIG GST reconciliation software is what the pattern moves to when a six-month backlog is no longer an acceptable outcome.
The companion TDS backlog correction sprint walks the equivalent 7-week protocol for the March 31 correction deadline on FY 2018-19 to FY 2022-23 TDS statements — the two sprints share the freeze-and-assess opening, the retrospective work in the middle, and the provisioning exit, applied to different statutes.
Where this fits
- Reconciliation software India — pillar guide
- GST reconciliation software India
- TDS reconciliation software India
Related reading
- The reconciliation playbook — monthly close pillar
- GSTR-2B five-day runbook — the monthly cadence this sprint returns to
- GSTR-2B ITC reconciliation failure modes — the design layer the sprint refreshes
- Section 16(4) ITC time bar
- Rule 37 and Rule 37A ITC reversal
- Invoice Management System reconciliation
- Vendor GSTR-1 follow-up letter templates — the chase-list activator for Weeks 7-10
- Three-way ITC reconciliation Excel recipe — the working paper the retrospective runs on
- DRC-01C ITC mismatch reply
- TDS backlog correction sprint — companion catch-up manual for the March 31 TDS deadline
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 — Time limit for availing input tax credit. A registered person cannot claim ITC in respect of any invoice or debit note pertaining to a financial year after the thirtieth day of November following the end of that financial year, or the furnishing of the relevant annual return, whichever is earlier. Where a supplier's GSTR-1 is filed late and no matched entry is picked up before the deadline, the credit is permanently forfeited with no rectification, condonation, or refund mechanism. This is the anchor that turns a six-month GSTR-2B backlog surfaced in September into a hard 90-day sprint terminating on 30 November.
- ▸ Rule 36(4), Central Goods and Services Tax Rules 2017 — Input tax credit ceiling on GSTR-2B. Input tax credit availed by a registered person in respect of invoices or debit notes shall not exceed the credit available in FORM GSTR-2B, being the auto-generated statement of ITC based on supplier GSTR-1 filings. Rule 36(4) is the operational ceiling that turns every unmatched purchase-register invoice into an at-risk item — the recipient cannot claim ITC that has not landed in GSTR-2B, and the catch-up sprint's retrospective three-way match is the working paper that validates the ceiling for each of the six closed months.
- ▸ Rule 37A, Central Goods and Services Tax Rules 2017 — Reversal of input tax credit in case of non-payment of tax by the supplier. Where the supplier of goods or services has not filed GSTR-3B for the tax period in which the invoice was reported by the thirtieth day of September following the end of the financial year, the recipient shall reverse the ITC availed against the said invoice. The reversal cascades where the supplier defaults across multiple months. The catch-up sprint reveals the cascade for the first time — a supplier who missed the April 2026 GSTR-3B and continued to miss May, June, and July requires four months of cumulative reversal with interest under Section 50, discovered together at Week 6.
- ▸ Rule 37, Central Goods and Services Tax Rules 2017 — Reversal of input tax credit in case of non-payment of consideration. A registered person who has availed input tax credit but has failed to pay the supplier of the goods or services the amount towards value of supply along with tax within 180 days from the date of issue of invoice shall pay an amount equal to the input tax credit availed along with interest thereon under Section 50. The Week 3 to Week 6 retrospective match layers Rule 37 alongside the Bucket 1 matched population — AP invoices booked more than 180 days ago that have not been paid trigger a reversal that must be netted against the recoverable ITC in the same working paper.
- ▸ Invoice Management System, GST Council notification effective October 2024 — Invoice Management System introduction. From October 2024, every inbound invoice and debit or credit note filed by a supplier in GSTR-1 or through the Invoice Furnishing Facility appears in the recipient's IMS dashboard for an Accept, Reject, or Pending action before the invoice locks into the recipient's GSTR-2B on the 14th of the following month. Where the recipient takes no action, the invoice defaults to Accept. In a six-month backlog scenario, the entire IMS action log for the closed months has already auto-defaulted to Accept, and the retrospective match must sanity-check each auto-Accept line against the AP booking to catch ghost invoices, duplicates, and block-class supplies that were never rejected in real time.
- ▸ Rule 88D, Central Goods and Services Tax Rules 2017 — DRC-01C intimation — Manner of dealing with difference in input tax credit available in auto-generated statement containing details of input tax credit and that availed in return. Where the input tax credit availed by a registered person in FORM GSTR-3B exceeds the input tax credit available in FORM GSTR-2B beyond the prescribed threshold, the system shall issue an intimation in FORM GST DRC-01C to the registered person, who shall respond within thirty days either by paying the differential with interest through FORM GST DRC-03 or by furnishing a reply explaining the reasons. A backlog recovery that claims prior-period ITC in the November GSTR-3B may trigger DRC-01C if the claim exceeds the current-month GSTR-2B ceiling — the sprint's working paper is the primary evidentiary defence.