Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian recipients of B2B supplies face structural ITC leakage under Rule 36(4) of the CGST Rules because Input Tax Credit availability depends on supplier-side GSTR-1 filing flowing through the recipient's GSTR-2B. Suppliers who file late create lagged leakage with working-capital cost and Section 50 interest exposure; suppliers who never file create permanent leakage. Without a supplier-ageing workflow tied to the GSTR-1 filing calendar and the IMS dashboard, the recipient's GSTR-3B Table 4(A)(5) claim runs systematically below the procurement-side tax position, and the gap shows up as either an interest charge or a structurally written-off credit.
Maintain a procurement ITC ledger keyed by supplier GSTIN, invoice number, taxable value, GST split, supplier filing cycle (monthly or quarterly), and expected GSTR-1 filing window. Daily-pull IMS data and weekly-pull GSTR-2B reflection per recipient GSTIN. Match every books-side ITC entry to its 2B counterpart. Age every unreconciled invoice in 5 / 20 / 45 / annual-return buckets keyed to the supplier's GSTR-1 deadline. Route each bucket to a specific recovery action. Track permanent vs lagged classification and feed the Discovered Money register on the tax-deduction class.
Procurement ITC ledger with supplier GSTIN, invoice number, taxable value, IGST / CGST / SGST split, supplier filing cycle, expected GSTR-1 window. IMS dashboard sync per recipient GSTIN. GSTR-2B reflection match-engine with primary keys on supplier GSTIN, invoice number, period and amount. Ageing buckets day-5, day-20, day-45, annual-return-deadline. Escalation playbook by bucket. Section 50 interest calculator keyed to original credit-availment date. Permanent vs lagged classifier. Audit trail for every reclassification.
A daily ITC-at-risk dashboard by supplier with rupee credit, days outside 2B reflection, and recovery probability. A weekly supplier-side escalation pack with GSTIN, period, and invoice-level detail. A monthly Section 50 interest-exposure projection. A quarterly permanent-vs-lagged leakage trend that feeds the audit committee. A standing recovery register tracking rupees in claim, rupees recovered, rupees structurally lost.
A CFO at a Pune-based B2B SaaS reseller running ₹85 crore of annual GST-bearing procurement audits the FY26 ITC position. The books show ₹12.8 crore of input GST paid to suppliers. The aggregated GSTR-2B reflection across all twelve months shows ₹11.7 crore. The gap — ₹1.1 crore, or 8.6% of procurement-side ITC — sits in two pools: ₹74 lakh of lagged ITC waiting on supplier late-filings, ₹36 lakh of permanent leakage from suppliers whose annual return cutoff has now passed.
This is what Rule 36(4) leakage looks like in practice: not a single failure, but the cumulative drag of 47 suppliers across 211 invoices, each individually small, each individually below the threshold a manual ITC team would chase, but together representing more than 8% of a real, paid, tax-rupee asset that the recipient is statutorily entitled to.
Quick reference: ITC leakage detection map under Rule 36(4)
| Leakage signal | Source artefact | Operative reference | Recovery action |
|---|---|---|---|
| Books ITC exceeds GSTR-2B reflection | Procurement ledger vs GSTR-2B | Rule 36(4), CGST Rules | Supplier-side GSTR-1 follow-up |
| Supplier filed GSTR-1 late | TRACES / GSTN public filing index | Supplier filing cycle calendar | Lagged-ITC claim in subsequent 3B |
| Supplier never filed | Multi-period 2B absence | Section 73/74, CGST Act | Permanent classification, recovery escalation |
| Invoice rejected in IMS by error | IMS dashboard log | IMS architecture | Reverse rejection within recipient’s window |
| ITC claimed without 2B support | GSTR-3B Table 4(A)(5) vs 2B | Section 50, CGST Act | Reverse with Section 50 interest |
| Rule 37 risk on unpaid supplier | Payables ledger day-180 ageing | Rule 37(1), CGST Rules | Proportionate reversal, Table 4(B)(2) |
| Supplier GSTIN cancelled retrospectively | GSTIN status check | Section 29 cancellation rules | Document for permanent leakage |
| Annual return cutoff approaching | Recipient annual ITC calendar | 30 November of next FY, GSTR-9 | Pre-cutoff sweep, force claim or reverse |
The Rule 36(4) ITC architecture in one paragraph
Section 16(2) of the CGST Act sets four conditions for ITC: possession of a tax invoice, receipt of the supply, payment of the tax to the government, and filing of the return. Rule 36(4) operationalises the third and fourth: ITC can be availed only on invoices reflected in the recipient’s GSTR-2B, which is auto-populated from supplier-filed GSTR-1. The IMS dashboard layer added in 2024 lets the recipient accept, reject, or mark pending each invoice flowing in, giving the recipient a daily working surface rather than a once-a-month 2B reconciliation. The combination of Rule 36(4) and IMS means the recipient’s claim is mechanically capped at what the supplier ecosystem files — leakage equals the gap.
The permanent vs lagged distinction
The biggest analytical mistake in ITC leakage reporting is treating “missing from 2B this month” as a single class. It is two:
Lagged ITC. The supplier will file GSTR-1, just late. The invoice flows into 2B in a subsequent period. The recipient’s claim is delayed by one or more periods, but the rupee is recoverable. Working-capital cost: the time-value of the deferred credit. Interest cost: only triggered if the recipient incorrectly claimed in the original period and now must reverse with Section 50 interest.
Permanent ITC leakage. The supplier will not file GSTR-1 within the window where the recipient can still claim. This happens when: the supplier has wound up the business (closure or liquidation), the supplier’s GSTIN was cancelled retrospectively, the invoice date is so old that the supplier’s GSTR-9 annual return cutoff (30 November of the next FY) has passed without the invoice being included, or the invoice carries a structural defect (invalid GSTIN, wrong supplier name) that cannot be rectified.
The split in a healthy mid-market supplier base is typically 65-75% lagged, 25-35% permanent. The classification has to be done early because the recovery actions differ entirely.
Worked example — a ₹85 crore B2B procurement spend
Setup. A B2B SaaS reseller in Pune with ₹85 crore of annual GST-bearing procurement spend. Average input GST rate weighted across services and goods: roughly 15.1% on taxable value of ₹85 crore = ₹12.83 crore of input GST per year.
Pre-workflow baseline at FY-end. Aggregated GSTR-2B reflection: ₹11.72 crore. Standing gap: ₹1.11 crore — 8.6% of procurement-side ITC.
Decomposition. Supplier audit at month-13 reveals 47 suppliers and 211 invoices in the gap. ₹74 lakh is lagged across 168 invoices from 38 suppliers who file GSTR-1 quarterly and are running 1-2 months late through the recipient’s monthly filing cadence. ₹36 lakh is permanent across 43 invoices from 9 suppliers (3 wound up, 4 with retrospectively cancelled GSTINs, 2 with invoices past the GSTR-9 cutoff).
After four-bucket workflow for two quarters. Lagged recovery: 78% of ₹74 lakh = ₹57.7 lakh claimed across subsequent 3B periods. Section 50 interest exposure avoided by not pre-claiming: roughly ₹3.2 lakh on the recovered base. Permanent recovery: ₹4.1 lakh recovered through targeted supplier follow-up on two of the nine suppliers (the others remain structurally lost).
Net annual leakage reduction: ₹61.8 lakh. Net annual permanent loss reduced to: ₹31.9 lakh — 2.5% of procurement-side ITC (down from 8.6%), which is the structurally-typical floor for a recipient operating in the B2B SaaS supplier mix.
Model ITC leakage on your B2B procurement
Enter procurement spend, supplier mix, and current 2B reflection rate to project lagged vs permanent leakage and recovery upside.
Open the ITC Leakage Calculator →The four-bucket supplier ageing playbook
Bucket 1 — day 0 to day 5 from the supplier’s GSTR-1 filing deadline. The recipient’s IMS dashboard either shows the invoice accepted, the invoice rejected, or no record. If no record at day 5, send a soft AP-AR prompt to the supplier with invoice number, period, and value. Resolution at this stage is usually fast: the supplier confirms either “filed late by 2 days, will reflect next 2B” or “we missed, adding to next return.”
Bucket 2 — day 5 to day 20. The IMS dashboard should show the invoice or the supplier’s draft 2B contribution. If still absent, send a formal escalation citing the supplier’s filing cycle (monthly or quarterly), the missing invoice number, the recipient’s filing deadline, and the implied Section 50 interest exposure if the recipient were to claim without 2B support.
Bucket 3 — day 20 to day 45. Escalate to the supplier’s CFO office or controllership. By this stage, more than 80% of resolutions happen via the supplier filing a GSTR-1A correction or including the invoice in the next regular GSTR-1. The recipient’s claim shifts to the period of 2B reflection.
Bucket 4 — day 45 to annual return cutoff. This is the high-stakes window. If the supplier has not filed by 30 November of the next FY, the invoice falls permanently outside the recipient’s claim window under the recipient’s own GSTR-9 deadline. The action by this stage is either commercial leverage (withhold next payment, escalate to legal) or formal acceptance of permanent leakage.
The IMS adoption gap
The IMS dashboard’s value is in the early-warning advantage. A recipient who consults IMS daily catches missing invoices in bucket 1; a recipient who consults at month-end catches in bucket 3 or 4. Industry adoption surveys (CBIC consultative bodies, ICAI working group) put active daily IMS use at 35-45% of mid-market recipients today, with the balance still working off month-end GSTR-2B downloads. The leakage band correlates: daily-IMS recipients run at 1.5-3% leakage, month-end-2B recipients run at 5-9%.
Section 50 interest exposure — the hidden cost
Section 50 runs 18% per annum on ITC wrongly availed. Two scenarios trigger it in a Rule 36(4) context.
Scenario A — pre-claim. The recipient claimed ITC in the original period anticipating the supplier’s filing. The filing did not materialise. The recipient must reverse the claim with Section 50 interest running from the original GSTR-3B Table 4(A)(5) date.
Scenario B — Rule 37 cascade. The recipient claimed valid ITC, then failed to pay the supplier within 180 days. Rule 37(1) requires proportionate reversal under Table 4(B)(2). Section 50 interest runs from the original credit-availment date. Even if the recipient pays the supplier later and re-avails under Rule 37(4) via Table 4(A)(5), the interest paid between reversal and re-availment is permanent leakage. See the Rule 37 ITC reversal article for the OEM short-pay cascade case.
The hidden cost in Scenario A is the most under-counted: a recipient who chronically pre-claims to keep filing-period cash flow clean is permanently paying Section 50 interest on the catch-up reversals. The corrective is a hard rule: claim only what is in 2B; defer the rest.
Putting Rule 36(4) leakage on the audit committee agenda
The standard quarterly pack for ITC leakage contains: procurement spend with input GST, GSTR-2B reflection coverage rate, lagged-vs-permanent decomposition, supplier ageing pack with rupees and counterparty, Section 50 interest exposure projection, and the recovery pipeline by bucket. The single most important chart is the permanent-leakage trendline: it tells the audit committee whether supplier-quality discipline is improving and whether the leakage class is structural or controllable.
Continue reading on the leakage backbone
For the umbrella framing, return to Revenue leakage and the Seven Classes framework. The TDS-side companion is TDS credit leakage and Form 26AS / Form 168. For the cross-class operating model, see the Revenue leakage recovery playbook. The Stop Revenue Leakage pillar page anchors the full umbrella story.