Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian finance teams routinely carry crores of provisional ITC at risk every month because suppliers under-file or mis-file GSTR-1, invoices mismatch on amount or place-of-supply, and the Rule 37 180-day payment clock trips quietly on slow-paid vendors. The recovery happens ad-hoc — someone chases suppliers when a number looks wrong, write-offs get taken at year-end, and DRC-01C notices land without supporting evidence. A structured monthly cycle with named owners, calendar-driven SLAs, and an at-risk register turns ITC recovery from a quarterly scramble into a standing tax-desk capability.
Run a monthly cadence anchored to the GSTR-2B drop on T+13. Reconcile books ITC against 2B ITC and decompose the gap into four categories — missing invoice, amount mismatch, GSTIN mismatch, place-of-supply mismatch. Maintain a GSTIN-wise supplier filing dashboard with a defaulter list. Adopt the Invoice Management System for accept / reject / pending discipline. Operate a parallel Rule 37 watchlist that flags every ITC-claimed invoice unpaid at day 165. For provisional ITC unrecovered by T+45, post the reversal with Section 50 interest and track the reclaim entry. Maintain an at-risk register that holds every disputed line until it is recovered, reclaimed, or structurally lost.
T+0 to T+45 calendar with named owners (tax controller, AP controller, supplier-relations lead). GSTIN-wise supplier filing dashboard with on-time / delayed / defaulter status. IMS daily review queue. Four-category mismatch resolution playbook. Rule 37 day-165 watchlist with weekly tax-desk review. DRC-01B and DRC-01C response templates. ITC at-risk register with status field (chased, accepted, rejected, reversed, reclaimed, structurally lost). Monthly tax-committee pack and quarterly audit-committee feed.
A monthly ITC at-risk register decomposing the provisional ITC pool by category and supplier. A weekly defaulter list driving supplier escalation. A Rule 37 watchlist driving on-time vendor settlements. A monthly reversal-and-reclaim journal posted with regulator-aligned narration. A quarterly tax-committee pack showing ITC recovered, ITC in pipeline, ITC structurally lost, and Section 50 interest avoided.
A tax controller at a Pune-based manufacturer with ₹68 crore of annual B2B procurement opens the books on the 14th of the month and sees the gap. Books ITC for the period: ₹4.2 Cr. GSTR-2B ITC reflected: ₹3.6 Cr. The ₹60 lakh gap is what Rule 36(4) calls provisional ITC at risk — it cannot be claimed in GSTR-3B until it lands in GSTR-2B. Somewhere upstream, suppliers have not filed GSTR-1 yet, or have filed it with the wrong GSTIN, or have under-reported the invoice value. Until that is fixed, the working capital is out of the door and the credit is not.
Sitting next to that file is a second report from the AP system: 47 vendor invoices on which ITC was claimed in earlier GSTR-3Bs but which remain unpaid in books beyond 165 days. Rule 37 says: pay them in the next 15 days, or reverse the ITC with interest under Section 50, then reclaim only when the payment is made. The combined exposure across the two problems — Rule 36(4) provisional ITC and Rule 37 ageing — is the standing leakage that the monthly chase cycle in this article is built to recover.
Quick reference: the monthly ITC chase cycle
| Phase | Action | Owner | SLA |
|---|---|---|---|
| T+0 | Books posted with vendor invoices and ITC mapped | AP controller | Day-zero close |
| T+11 | GSTR-1 deadline for suppliers — track filing | Tax desk | End of T+11 |
| T+13 | GSTR-2B drops, auto-populated ITC available | Tax controller | Same day pull |
| T+14 | Reconciliation: books ITC vs 2B ITC, gap decomposed | Tax controller | T+14 close |
| T+20 | Supplier chase begins with defaulter list | Supplier-relations | Rolling |
| T+30 | Escalation: payment hold, written notice, account-manager review | Tax controller plus AP | T+30 close |
| T+45 | Final reversal of unrecovered provisional ITC; Rule 37 reclaim entries | Tax controller | T+45 close |
How does the monthly ITC chase cycle work end-to-end?
The cycle is anchored to two calendar events. The first is the supplier-side GSTR-1 deadline on T+11. The second is the auto-population of GSTR-2B on T+13. Everything before T+13 is about discipline at posting and at supplier onboarding. Everything from T+13 to T+45 is about recovery.
T+0 to T+11 is the books-clean window. Every vendor invoice gets posted with the supplier GSTIN, the invoice-level taxable value, the rate, the IGST or CGST+SGST split, and the place-of-supply code. Three-way match against PO and GRN is closed. The ITC claim per invoice is computed but is provisional until 2B confirms it.
T+13 the 2B drops. The tax desk pulls 2B by 11 AM and runs the reconciliation routine. The output is a four-bucket decomposition: matched (claim-eligible), missing-invoice (not in 2B at all), amount-mismatch (in 2B with a different taxable value or tax), GSTIN-mismatch (in 2B against a different GSTIN), place-of-supply mismatch (in 2B with a different POS code which changes the IGST/CGST split).
T+14 reconciliation closes. The matched bucket is the ITC eligible for the current GSTR-3B. The mismatch buckets feed the chase pipeline. The provisional ITC at risk is sized.
T+20 supplier chase begins. Every supplier on the defaulter list (no GSTR-1 filed) and every supplier with a mismatched invoice receives a structured request: file GSTR-1 with the missing invoice, amend the incorrect invoice, or confirm the correction will be made in the next return. The request is paired with the buyer’s invoice copy and the 2B extract showing the gap.
T+30 escalation. Suppliers who have not responded by T+30 get the next-payment hold treatment — outgoing payments are paused until the GSTR-1 mismatch is resolved. A written notice goes from the AP controller. For top-revenue suppliers a key-account meeting is scheduled.
T+45 final disposition. Provisional ITC still unrecovered by T+45 gets reversed in the next GSTR-3B with the regulator-aligned narration. Any prior reversal that has since been resolved (the supplier filed; 2B now reflects the invoice) gets reclaimed in the same return. The at-risk register is updated.
How is supplier filing tracked in practice?
A GSTIN-wise supplier filing dashboard is the operational backbone. For every active supplier, the dashboard holds: GSTIN, supplier name, average monthly procurement value, last three months’ GSTR-1 filing status, average filing lag in days, and a risk band (low / medium / high). Suppliers in the high-risk band — those who chronically file late or default — are flagged for either contractual remediation or replacement.
The dashboard refreshes daily from a public GSTIN status check. The defaulter list — suppliers who have not filed by T+11 — gets generated automatically at T+12 morning. That list, sorted by rupee exposure descending, is the chase queue for the supplier-relations team.
For a manufacturer with 240 active GSTIN suppliers, the typical distribution is: 70-80% always-on-time, 15-20% occasional-late, 5-10% chronic defaulters. The chronic 5-10% drive a disproportionate share of the provisional ITC at risk — usually 40-55% of the at-risk pool comes from this tail. Reducing that tail through procurement-side remediation is the single highest-leverage move in the cycle.
What does the Invoice Management System (IMS) workflow look like?
IMS sits between GSTR-2B and GSTR-3B. Every invoice surfacing in 2B gets an explicit action by the buyer: accept (the invoice is genuine and will flow into 3B), reject (the invoice is defective and should be amended by the supplier), or pending (the buyer is still verifying).
Day-by-day operation. The tax desk runs the IMS review queue daily. Invoices matching the books and matching the 2B amount get accepted in bulk. Invoices missing from books (the supplier reported an invoice the buyer did not receive) get rejected or marked pending pending investigation. Invoices in books but mismatched on amount or GSTIN get marked pending and added to the chase queue.
The discipline IMS forces is upstream. Rejected invoices push the supplier to amend rather than carrying a silent mismatch month after month. Pending invoices act as a real-time defaulter signal — the buyer no longer has to wait for the next 2B drop. Accepted invoices become the clean ITC pool with a clear audit trail for any future scrutiny including DRC-01C response.
Adoption requires three upstream gates: clean supplier master data with verified GSTINs, three-way PO-GRN-invoice match at posting, and a named owner for the daily IMS queue. Without those gates, IMS becomes another inbox.
How are GSTR-1 vs GSTR-2B mismatches resolved?
The four mismatch categories each have a different resolution playbook.
Missing invoice. The invoice is in books but absent from 2B entirely. Root cause is almost always supplier non-filing or supplier filing the invoice in the wrong return period. Resolution: send the invoice copy plus the buyer’s books extract to the supplier with a request to file or amend the relevant GSTR-1. Follow-up cadence is T+20, T+30, T+45.
Amount mismatch. The invoice is in 2B but the taxable value or tax amount differs from the books. Root cause is usually a typo on the supplier side, or an amendment the supplier made without informing the buyer. Resolution: reconcile the invoice with the supplier; if the books are correct, request the supplier to amend the GSTR-1; if the supplier’s amendment is correct, post the books correction with a credit note or debit note entry.
GSTIN mismatch. The invoice is in 2B against a GSTIN different from the one the buyer claimed against. Common cause is a buyer with multiple registrations where the supplier billed to a different state. Resolution: re-map the ITC claim to the correct registration, or, if the supplier billed wrongly, request an amendment.
Place-of-supply mismatch. The invoice is in 2B but the POS code differs, which flips IGST to CGST+SGST or vice versa. The tax amount may be unchanged but the head of credit differs. Resolution: reconcile against the original PO and shipping document; if the buyer’s POS is correct, request supplier amendment; if the supplier’s POS is correct, re-post the ITC under the correct head.
What are the Rule 36(4) and Rule 37 mechanics?
Rule 36(4) is a buyer-side restriction. ITC can only be claimed to the extent it is reflected in GSTR-2B for the period. Provisional ITC — credit on invoices posted in books but not yet reflected in 2B — cannot be claimed in that month’s GSTR-3B. If it reflects in a subsequent month’s 2B (the supplier filed late), it becomes claimable in that subsequent month’s 3B. If it never reflects, it is permanently lost.
Rule 37 is a different mechanism. It deals with ITC that was validly claimed in an earlier GSTR-3B but where the buyer has not paid the supplier within 180 days of the invoice date. The buyer must reverse that ITC in the GSTR-3B for the period in which the 180 days complete, with interest under Section 50. Once the payment is subsequently made, the ITC can be reclaimed in the GSTR-3B for the period of payment.
Operationally the two run as parallel watchlists. Rule 36(4) is the monthly cycle anchored to the 2B drop. Rule 37 is the day-165 vendor-ageing flag from the AP system, reviewed weekly at the tax desk. Both feed the at-risk register but with different status fields and different recovery actions.
How is DRC-01B and DRC-01C handled?
DRC-01B is the demand notice issued on a supplier-side mismatch between GSTR-1 outward supplies and GSTR-3B tax paid. It hits the supplier, not the buyer directly. For the buyer, a supplier under DRC-01B is a high-risk filing-discipline supplier and should be flagged on the dashboard.
DRC-01C is the buyer-side notice on a mismatch between ITC claimed in GSTR-3B and ITC available in GSTR-2B. Response window is short — typically 7 to 30 days from issue. The required evidence is an invoice-level mapping between books, 2B, and the chased / not-chased status, plus the corresponding supplier correspondence. A buyer who runs the monthly chase cycle has that evidence ready and can file a contested response. A buyer who does not pays the demand with interest, often unnecessarily.
The template response covers: the books position with the invoice listing, the 2B reconciliation showing matched and mismatched invoices, the chase log per mismatched invoice (request date, supplier reply, current status), and the regulator-aligned narration for any reversal already posted under Rule 36(4).
Worked example — Pune manufacturer, ₹68 Cr annual procurement
A manufacturer with ₹68 crore of annual B2B procurement runs an average monthly ITC claim pool of ₹5.6 crore on roughly 18% effective GST. Books ITC for the full year totals ₹67.2 crore. ITC at risk under Rule 36(4) and Rule 37 combined: ₹2.8 crore.
Decomposition of the at-risk pool. ₹1.6 crore from supplier-not-filed (the chronic defaulter tail — about 12 high-volume suppliers chronically filing late or missing returns). ₹0.7 crore from amount and GSTIN mismatches across roughly 180 mismatched invoices in the year. ₹0.5 crore from Rule 37 reversal on aged vendor payables — about 30 invoices crossing 180 days unpaid in the year.
Year-one recovery program. The tax desk deploys the monthly chase cycle. Supplier-relations runs the defaulter list weekly. The IMS daily queue is operationalised by the second quarter. The Rule 37 day-165 watchlist is integrated into the AP weekly cycle.
Year-one outcome. ₹1.05 crore recovered on supplier-not-filed (about 65% of the bucket — chronic defaulters either reformed under payment-hold pressure or got replaced). ₹0.55 crore recovered on mismatches (about 79% — amount mismatches resolve faster than supplier defaults). ₹0.35 crore recovered on Rule 37 by paying vendors before day 180 or by accelerated reclaim. Total year-one recovery: ₹1.95 crore. Residual ₹0.85 crore moves into the year-two pipeline or gets accepted as structural loss for non-viable suppliers.
The Section 50 interest avoided on Rule 37 alone is roughly ₹6-8 lakh in the year — small as a line item but material as a board-track indicator of operating discipline.
Size the ITC at risk before you deploy
Before standing up the cycle, size the at-risk pool with a baseline calculation. The ITC Leakage Calculator takes annual procurement, effective GST rate, and a rough mix of supplier-filing risk and vendor-payment ageing to project the recoverable upside in year one. The broader Revenue Leakage Calculator places the ITC leakage line alongside the other six classes so the board sees the relative size before committing the program budget.
Common pitfalls in ITC recovery
Skipping the daily IMS queue. Without daily IMS review, accept / reject / pending decisions pile up and the upstream amendment pressure on suppliers disappears.
Treating Rule 36(4) and Rule 37 as the same workflow. They run on different cadences, with different owners, and against different counterparties. Conflating them leaves the Rule 37 day-165 flag perpetually under-staffed.
Letting the supplier defaulter tail persist. The chronic 5-10% of suppliers drive 40-55% of the at-risk pool. Procurement-side replacement of that tail compounds the recovery rate faster than any in-cycle improvement.
Filing DRC-01C responses without the chase log. The response is only defensible if the invoice-level chase history is on file. A buyer who responds with a generic position pays the demand.
Posting Rule 37 reversals without the reclaim entry tracked. The reclaim has a defined window and a defined GSTR-3B period. Missing the reclaim makes the reversal permanent.
Not reporting ITC leakage to the audit committee. Without quarterly external review the program drifts within two to three quarters. The committee discipline is what sustains the cadence.
Tying back to the Seven Classes framework
ITC leakage is one slice of the broader Class 2 (tax-deduction) line in the Seven Classes framework. It sits next to TDS credit leakage on the same balance-sheet head — tax receivable. The operating disciplines rhyme: regulator-anchored deadlines, counterparty filing dependency, monthly chase cycle, at-risk register, audit-committee reporting. A finance function that runs the ITC cycle described in this article can layer the TDS credit cycle on the same operating template with marginal effort, and the combined recovery on the tax-receivable head typically lands in the 60-80% range within two to three quarters of disciplined operation.
For the umbrella operating model, the Revenue leakage recovery playbook shows how this article’s ITC cycle plugs into the broader seven-class program. For the board-approval companion, see Building the board case for revenue leakage recovery. The Stop Revenue Leakage pillar page anchors the broader story.