Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Section 16 of the CGST Act has five conditions for ITC claim, each with its own evidence requirement. The IMS regime adds explicit Acceptance as a Rule 36(4) compliance step. The audit defence package is now a five-artefact chain per invoice that spreadsheet workflows cannot reliably maintain at scale, leaving listed entities and high-volume buyers exposed to ITC reversal in statutory GST audit.
The compliant ITC workflow links five evidence artefacts per invoice: tax invoice, goods or services receipt evidence, supplier GSTR-1 filing proof, IMS Accept timestamp, and 180-day payment evidence. Each artefact is captured at the appropriate workflow stage and bound to the GSTR-3B Table 4 line where the ITC was claimed. Rule 37 reversal at day 181 is triggered automatically for unpaid invoices, with re-claim on subsequent payment.
Tax invoice repository linked to purchase register, GRN or service-acceptance system integration, IMS Accept timestamp capture at decision time, supplier payment tracking with 180-day alert, and Rule 37 reversal automation tied to GSTR-3B Table 4(B).
Per-invoice five-artefact audit pack, Rule 36(4) compliance dashboard, Rule 37 reversal report per period, and GSTR-3B Table 4 ITC line reconciled to the underlying evidence chain ready for statutory audit defence.
A statutory GST audit of a listed manufacturer in 2026 will examine ITC claims under Section 16 of the CGST Act with a level of evidence detail that did not apply to claims pre-IMS. The conditions in Section 16 are unchanged — possession of invoice, receipt of goods, supplier tax payment, return filing, and 180-day payment. What changed is that Rule 36(4) compliance now requires the buyer’s explicit IMS Accept as an evidentiary step. The audit defence package has grown from a four-artefact chain to a five-artefact chain. This article maps the chain and the workflow that produces it at scale.
Section 16 Conditions in Detail
Section 16 of the CGST Act sets five cumulative conditions for ITC claim. All must be satisfied; failure of any one disqualifies the ITC.
Condition 1 — Possession of a tax invoice or debit note. The buyer must hold a valid tax invoice complying with Rule 46 of the CGST Rules (or a debit note where applicable). The invoice must contain the supplier’s GSTIN, invoice number, date, taxable value, tax rates, and tax amounts.
Condition 2 — Receipt of goods or services (or both). The buyer must actually receive the goods or services. Evidence: goods receipt note (GRN), delivery challan, service acceptance report, or equivalent. Without receipt evidence, ITC is not claimable even if the invoice is in possession.
Condition 3 — Tax has been actually paid to the government. The supplier must have paid the tax charged on the invoice. The buyer’s evidence is the supplier’s GSTR-1 filing (which appears in the buyer’s GSTR-2A and IMS dashboard). If the supplier defaults on GSTR-3B filing, this condition may fail under Section 41 of the CGST Act, triggering ITC reversal.
Condition 4 — Filing of GSTR-3B by the recipient. The buyer must file the relevant GSTR-3B return claiming the ITC. ITC cannot be claimed if GSTR-3B is not filed.
Condition 5 — Payment to supplier within 180 days from invoice date. Under the second proviso to Section 16(2) and Rule 37 of the CGST Rules, the buyer must pay the supplier (taxable value plus tax) within 180 days of invoice date. Failure triggers ITC reversal in GSTR-3B Table 4(B), with re-claim available on subsequent payment.
The Sixth Implicit Condition: IMS Acceptance
Since October 2024, an additional compliance step sits between the five Section 16 conditions and the actual ITC claim: the buyer’s explicit IMS Accept on the GST portal.
The IMS Accept is not a Section 16 condition per se — Section 16 was not amended. But Rule 36(4) of the CGST Rules requires that ITC be claimed only against invoices appearing in GSTR-2B, and GSTR-2B now reflects IMS decisions. The mechanical chain is:
- Supplier files GSTR-1.
- Invoice appears in buyer’s IMS dashboard.
- Buyer Accepts in IMS (explicit or by 30-day default).
- Invoice flows into GSTR-2B.
- ITC claimed in GSTR-3B Table 4 against GSTR-2B.
Without step 3, step 4 doesn’t happen, and step 5 fails Rule 36(4). The IMS Accept has become the de-facto sixth condition for an ITC claim, even though the CGST Act itself remains unchanged.
The Five-Artefact Audit Defence Chain
A defensible Section 16 ITC claim under the IMS regime requires five evidence artefacts per invoice:
| Artefact | Section 16 Condition | Source |
|---|---|---|
| Tax invoice (PDF or digital) | Condition 1: possession | Supplier provides; buyer files |
| GRN or service-acceptance evidence | Condition 2: receipt | Buyer’s internal system |
| GSTR-1 filing evidence + IMS Accept timestamp | Condition 3: tax paid + Rule 36(4) | GST portal IMS dashboard |
| GSTR-3B Table 4 line | Condition 4: return filing | Buyer’s filing |
| Bank remittance proof within 180 days | Condition 5: payment | Bank statement |
The audit pack assembles these five artefacts per invoice into a single evidence chain. For a buyer with 1,500 monthly inward invoices, that is 7,500 evidence artefacts per month. Manual maintenance at this scale is infeasible — the audit pack must be system-generated.
What is your ITC leakage actually costing?
The ITC Leakage Calculator quantifies the annual rupee cost of ITC blocked by supplier non-filing under the IMS regime. Five inputs return permanent leakage, working-capital lock, and analyst hours.
Run the ITC Leakage Calculator →Rule 37 Reversal Mechanics
Rule 37 of the CGST Rules operationalises the 180-day payment condition under Section 16. The mechanic:
- Day 1: Invoice issued by supplier.
- Day 1-180: Buyer has time to pay (taxable value plus tax).
- Day 181: If unpaid, ITC must be reversed in GSTR-3B Table 4(B) of the current month, with interest from the date of claim.
- Day 181 onwards: If subsequently paid, ITC can be re-claimed in the GSTR-3B of the month of payment.
The interaction with IMS: an invoice can be Accepted in IMS in month 1, ITC claimed in month 1’s GSTR-3B Table 4(A). If unpaid by month 7 (day 181), the same ITC is reversed in month 7’s GSTR-3B Table 4(B). The IMS decision is unaffected — the invoice is still Accepted in IMS — but the ITC has been reversed.
The audit pack must capture both: the original Accept timestamp (month 1) and the Rule 37 reversal (month 7). If re-claim happens later (e.g., month 9 after payment), that is a third event in the same evidence chain.
For the full Rule 37 mechanics, see Rule 37 ITC reversal at 180 days.
Audit Defence Workflow
When the GST auditor examines an ITC claim, the question is: can the buyer produce all five evidence artefacts in a coherent chain, dated correctly, linked to the GSTR-3B line where the ITC was claimed?
A defensible workflow has five capture points:
Capture point 1 — Invoice intake. Tax invoice is logged in the purchase register with a digital copy attached.
Capture point 2 — Goods or service receipt. GRN posted in the ERP, linked to the purchase register entry by purchase order number.
Capture point 3 — IMS Accept. Buyer posts Accept on the GST portal. The IMS Accept timestamp is captured automatically by the reconciliation tool and bound to the purchase register entry.
Capture point 4 — GSTR-3B filing. Table 4(A) ITC value is reconciled to the accepted-set in GSTR-2B. Each line in Table 4(A) ties back to one or more invoices.
Capture point 5 — Payment. Bank remittance posted, with payment date captured. Section 16 day-180 alert triggers Rule 37 reversal if unpaid past day 180.
The five capture points are sequential workflow events. A reconciliation tool that links them produces the audit pack as a by-product of the workflow, not as a separate quarterly assembly exercise.
What Audit Defence Looks Like in Practice
A typical statutory GST audit query: “Show me the audit trail for ITC of ₹4.2 lakh claimed on invoice INV/2026-04-1547 from supplier GSTIN 29AAACX0123A1Z5 in your April 2026 GSTR-3B.”
The defensible response is a five-artefact pack:
- Tax invoice INV/2026-04-1547 dated April 8, 2026, supplier GSTIN 29AAACX0123A1Z5, taxable value ₹23.3 lakh, IGST ₹4.2 lakh — attached as PDF.
- GRN GRN/2026-04-892 dated April 12, 2026, received at warehouse Bangalore-North, against purchase order PO/2026-03-4421 — attached.
- IMS Accept timestamp April 15, 2026 14:32 IST, actor: AP Manager Ravi Sharma, captured from GST portal — log attached.
- GSTR-3B Table 4(A) line item from April 2026 return, IGST ₹4.2 lakh contribution — return attached.
- Bank remittance dated June 22, 2026 to supplier account, amount ₹27.5 lakh (taxable + tax), within 180-day window — bank statement attached.
The audit chain is complete. The auditor closes the query.
Without the IMS Accept timestamp (artefact 3), the chain is broken. The auditor moves to a deeper review of the ITC claim. This is the operational reason the IMS Accept has become a critical evidence artefact.
Multi-Process Integration
Section 16 ITC compliance does not sit in isolation. It interacts with TDS compliance (supplier payment requires TDS deduction where applicable), bank reconciliation (the 180-day payment evidence comes from bank statements), and vendor management (the supplier GSTR-1 filing track record influences future decisions).
A purpose-built GST reconciliation software handles the Section 16 audit chain natively for the IMS-era workflow. For enterprises managing GST alongside TDS, NACH bounce, and bank reconciliation, a unified reconciliation software India approach links the underlying evidence across processes that share supplier and bank master data.
For the foundational IMS-versus-GSTR-2B mechanics that the Section 16 chain sits on top of, see IMS vs GSTR-2B reconciliation and the broader ITC reconciliation under CGST Act framework.