GSTR-2B ITC Reconciliation Failure Modes: How to Prevent Section 16(4) Permanent Losses

Section 16(4) of the CGST Act is the only provision in Indian indirect tax that permanently forfeits a legitimate credit with no rectification, no condonation, and no recovery mechanism. Every year on 30 November — the statutory deadline for claiming Input Tax Credit against an invoice from the preceding financial year — a slice of otherwise-valid ITC turns to ash on the balance sheet of enterprises that failed to reconcile GSTR-2B against their purchase register at invoice level. This is why GSTR-2B reconciliation carries the single highest severity of any reconciliation function on the Indian finance calendar, and why the ITC failure modes India finance teams face on this stream deserve a first-principles process design rather than a monthly spreadsheet walkthrough.

This article catalogues the fourteen failure modes that conspire to produce a Section 16(4) permanent loss, groups them into the twelve failure classes of the reconciliation process design framework, and rates each on the Action Priority table. It closes at the point where a manual detection layer stops being economically viable — the at-risk ITC queue as the canonical High-AP control that manual processes outgrow above roughly 200 vendors.

Function definition — what GSTR-2B ITC reconciliation is

GSTR-2B ITC reconciliation is a monthly, PAN-and-GSTIN-level match between three inputs — the enterprise’s own purchase register for the tax period, the auto-generated GSTR-2B statement published on the GST portal, and the ITC availed in Table 4 of the current GSTR-3B — with a fourth annual reconciliation into Table 8 of the GSTR-9 annual return. The output is a claimable ITC register that satisfies every precondition in Section 16 of the CGST Act, respects the Rule 36(4) ceiling, applies every Section 17(5) exclusion, and reserves the ITC on invoices that have not yet appeared in GSTR-2B until they do — or until the Section 16(4) deadline runs out.

The function operates on a monthly cadence — GSTR-2B is published for a tax period between the 14th and the 16th of the following month, GSTR-3B is filed by the 20th (for monthly filers), and the ITC availed in each month’s GSTR-3B is cumulative for the financial year. The function operates at the GSTIN level — a multi-GSTIN entity runs this reconciliation independently for each registration, because the electronic credit ledger, the GSTR-2B, and the GSTR-3B are all GSTIN-scoped. The function operates at the PAN level for the annual return, because GSTR-9 aggregates across all GSTINs under a single PAN.

The Severity-10 anchor — Section 16(4) permanent loss on November 30

The reconciliation process design framework anchors its Severity scale to real Indian consequences rather than a generic 1-to-10 rubric, and the anchor at the top of the scale on the GSTR-2B stream is Section 16(4).

The text of the provision is unambiguous: a registered person shall not be entitled to take ITC in respect of any invoice or debit note for a supply of goods or services or both after the 30th 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. The Finance Act 2022 shifted the original 30 September deadline to 30 November and applied the extension retrospectively from 1 July 2017. There is no rectification path under Section 39 for an updated return. There is no condonation of delay. There is no revival mechanism. The credit, once time-barred, is permanently lost — and the enterprise’s only remaining recourse is a commercial claim against the supplier under the contractual indemnity, which is neither guaranteed nor timely.

An invoice dated 15 March 2026 (falling in FY 2025-26) must have its ITC claimed in a GSTR-3B filed on or before 30 November 2026, or the date of the FY 2025-26 GSTR-9 filing, whichever is earlier. If the GSTR-9 is filed on 15 October 2026, the effective Section 16(4) cutoff is pulled forward to 15 October 2026. Every day between the invoice date and that cutoff is an ageing day the reconciliation process must track. This is the Severity-10 anchor — and the Section 16(4) ITC time-bar guide covers the mechanics in detail.

The failure surface — IMS-era, Rule 37A-era, DRC-01C-era

The GSTR-2B failure surface has widened over the last three regulatory cycles, and every widening step has added failure modes without removing any of the existing ones.

January 2022 — Section 16(2)(aa) and Rule 36(4). From this point, the invoice must appear in GSTR-2B as a precondition for ITC and the ITC claimed in GSTR-3B cannot exceed the GSTR-2B amount. The zero-tolerance Rule 36(4) removed the last provisional ITC mechanism, and the reconciliation stream became a portal-driven rather than purchase-register-driven exercise.

January 2023 — Rule 37A introduced. A supplier’s failure to file GSTR-3B by 30 September of the following financial year forces the recipient to reverse the ITC by 30 November of that year. This introduced a Partner-class failure mode where the recipient’s ITC turns on the supplier’s tax-payment behaviour, not just the supplier’s return-filing behaviour. Re-availment is permitted once the supplier files, and is not subject to the Section 16(4) time bar.

August 2023 — Rule 88D and DRC-01C. Where the ITC availed in GSTR-3B for a period exceeds the ITC available in GSTR-2B by more than the prescribed threshold, an auto-generated intimation under Form GST DRC-01C flags the mismatch and demands either payment (through DRC-03) or a reasoned reply within the prescribed period. This is a Severity-8 anchor on the reconciliation process design severity scale — same tier as a DRC-01B GSTR-1-vs-3B mismatch and a CARO 2020 material weakness finding. See the DRC-01C reply guide for the response mechanics.

October 2024 — Invoice Management System (IMS) live. From this point every inward document (invoice, credit note, debit note) lands in the recipient’s IMS dashboard as Pending until the recipient actions it as Accept, Reject, or Keep Pending. Only Accepted documents flow into GSTR-2B. The default at cycle-close is Accept. Two new failure modes were born in October 2024 — a wrong Default-Accept that pulls a fraudulent invoice into GSTR-2B, and a wrong Reject that permanently excludes a legitimate invoice. See the Invoice Management System reconciliation guide and the IMS vs GSTR-2B three-way reconciliation for the underlying workflow.

The framework — twelve failure classes, six causes, Severity-first Action Priority

The reconciliation process design framework Terra Insight applies across every stream — invoice-to-bank, TDS, GSTR-1 vs 3B, and this stream — uses three intersecting taxonomies to name what can go wrong and how urgently it needs a control.

Twelve failure classes. Data extraction / Classification / Completeness / Matching / Timing / Partner / Precision / Policy / Aging / Cutoff / Evidence / Portal. On the GSTR-2B stream, Timing, Partner, Policy, Classification, and Completeness carry the highest concentration of High Action Priority failure modes.

Six causes — the 6P taxonomy. Every failure traces to People (a preparer or reviewer action), Policy (a rule the enterprise has or lacks), Process (a step in the reconciliation walkthrough), Portal (a behaviour or gap on the GST portal, IMS, or ICEGATE), Period (a cross-tax-period timing issue), or Partner (a supplier, buyer, or intermediary action). The 6P replaces the manufacturing 4M/6M cause categories that do not map to Indian reconciliation.

Severity-first Action Priority. The framework does not multiply Severity × Occurrence × Detection into an RPN because a Severity-10 row with Low Occurrence and Low Detection can still cause a permanent loss and must be a High Action Priority. Severity is the dominant axis. A Severity-10 row is always High Action Priority regardless of Occurrence and Detection. A Severity-8 or 9 row is High if Occurrence is Medium or higher, or if Detection is Low. A Severity-6 or 7 row is Medium unless Occurrence is High and Detection is Low, at which point it escalates to High. Below Severity 6, the rating rarely exceeds Medium unless the failure clusters into a systemic pattern.

The fourteen failure modes

Each of the fourteen rows below carries a failure mode name, its class from the twelve-class taxonomy, its 6P cause, the effect (with the specific Indian statute triggered), Severity/Occurrence/Detection ratings on a 1-to-10 scale, and the Action Priority. The Severity anchor for each rating is called out — S10 for Section 16(4) permanent loss, S9 for Section 200A demand analogue on GST-side interest, S8 for DRC-01C intimation and CARO 2020 material weakness.

The failure mode descriptions and their prevention and detection controls follow.

Failure mode 1 — Supplier’s GSTR-1 not filed by the 30 November cutoff

Class. Partner. 6P. Partner. Effect. The invoice never appears in the recipient’s GSTR-2B, and the Section 16(2)(aa) precondition is not met. On 30 November of the following financial year, the ITC is time-barred under Section 16(4) with no recovery mechanism. Severity 10 — the anchor row on this stream and the reason GSTR-2B carries the highest reconciliation severity of any function on the calendar. Occurrence 6 — moderate, because most GSTR-1 non-filings are cured within one or two months but a persistent supplier can carry through to the cutoff. Detection 5 — the supplier’s filing status is visible on the portal, but only if the recipient runs the check. Prevention control. A vendor onboarding gate that requires the supplier’s GSTIN, filing frequency, and last-filed GSTR-1 date at PO issue time; a contractual clause tying payment to timely GSTR-1 filing; and a quarterly supplier tax-compliance review with a top-quartile-exposure vendor list. Detection control. A weekly supplier GSTR-1 filing watch keyed to every purchase register invoice from the recipient’s own supplier master, with an ageing band of 30 / 60 / 90 / 120 days-to-cutoff, and a supplier follow-up cadence that escalates at 90 days. This is one of the failure modes the at-risk ITC queue was designed for.

Failure mode 2 — IMS action defaulted to Accept on a wrongly-issued invoice

Class. Portal. 6P. Portal / Process. Effect. A wrongly-issued invoice — a duplicate, an invoice against a cancelled PO, or a fraudulent invoice from a compromised supplier — lands in the recipient’s IMS dashboard as Pending. The recipient’s finance team fails to action it. At cycle-close IMS applies the default action of Accept, the document flows into GSTR-2B, and the ITC becomes claimable in GSTR-3B. When the fraud or the duplication is later detected, the recovery under Section 74 carries interest plus penalty of the tax amount plus, at CBIC’s discretion, an equivalent penalty. Severity 9 — Section 74 recovery is not permanent loss but the interest-plus-penalty stack is materially heavier than a routine reversal. Occurrence 5 — the IMS default has been operational only since October 2024 and finance teams are still building the muscle for a daily IMS review. Detection 6 — the finance team can catch it in the IMS dashboard review if the cadence is daily. Prevention control. A daily IMS dashboard review as an ERP-adjacent standing agenda item, an IMS action policy that requires an explicit Accept / Reject / Keep Pending on every document with an owner and a timestamp, and a two-eyes review on Accept actions above a threshold PO value. Detection control. A monthly IMS action log audit against the purchase register — every document Accepted in IMS must reconcile to a valid open PO or a valid open contract with the same supplier.

Failure mode 3 — IMS action taken as Reject on a legitimate invoice

Class. Portal. 6P. People. Effect. A legitimate invoice from a recently-onboarded supplier is wrongly Rejected in IMS — either the reviewer did not recognise the supplier or the invoice details did not match the reviewer’s expectation. The document is excluded from GSTR-2B and never enters the recipient’s ITC surface. Because the Section 16(2)(aa) precondition is not met, and because the IMS Reject action is not automatically reversible after the cycle closes, the ITC is time-barred under Section 16(4) on 30 November of the following financial year. Severity 10 — Section 16(4) permanent loss. Occurrence 4 — less frequent than a Default-Accept, because a Reject is a deliberate action. Detection 6 — the reviewer can catch it in the IMS action log if the two-eyes review is set up. Prevention control. A vendor whitelist gating IMS Reject actions — an IMS Reject on any document from a whitelisted supplier requires a second reviewer’s approval and a supplier-side confirmation before the action fires. Detection control. A monthly IMS Reject audit against the vendor master and the purchase register, with a supplier-side confirmation that the invoice was in fact revoked.

Failure mode 4 — Inbound invoice booked to a sibling entity in the group

Class. Completeness. 6P. Policy / Process. Effect. A multi-GSTIN group with a shared procurement function books an inbound invoice against the wrong entity’s books — the invoice is billed to Entity A but posted to Entity B’s purchase register. Entity A never sees the invoice in its purchase register and never reconciles it against its GSTR-2B. Entity B posted the invoice but the supplier’s GSTR-1 has it billed to Entity A’s GSTIN, so it never lands in Entity B’s GSTR-2B either. Both entities miss the ITC. On 30 November of the following financial year, the ITC is permanently lost. Severity 9 — the loss is functionally identical to Section 16(4) though the underlying cause is a booking error rather than a portal failure. Occurrence 6 — common on multi-GSTIN structures with a shared services centre or a group-level procurement policy. Detection 4 — the failure is invisible until the two-way GSTR-2B reconciliation surfaces the orphan. Prevention control. An entity master keyed to the shipping address and the billing GSTIN with a hard validation at PO creation, an ERP-level check that routes an invoice’s posting entity to the same entity as the billing GSTIN on the tax invoice, and a shared services centre policy that requires the GSTIN as a mandatory field on every purchase invoice booking. Detection control. A monthly cross-entity GSTR-2B walk — for each GSTIN, list the invoices in GSTR-2B that do not appear in that GSTIN’s purchase register, and route each orphan to the correct entity’s finance team for booking.

Failure mode 5 — Rule 37 180-day non-payment reversal missed

Class. Timing. 6P. Process. Effect. The recipient claimed ITC on an inward supply but has not paid the supplier the value of the supply (with tax) within 180 days from the invoice date. Rule 37 requires the ITC to be reversed proportionately in the GSTR-3B for the tax period immediately following the 180-day expiry. If the reversal is missed, Section 50 interest at 18% per annum applies from the date of ITC utilisation to the date of eventual reversal, and DRC-01C exposure builds up on the aggregate ITC differential. Severity 8 — the reversal is recoverable once payment is made (Rule 37 permits re-availment with no Section 16(4) time bar), but the interest and DRC-01C exposure are material. Occurrence 7 — common in enterprises with a long-tail supplier base or a stretched working-capital policy. Detection 5 — the ageing is derivable from the accounts payable ledger. Prevention control. A vendor payment policy tied to Rule 37 with a 150-day-to-Rule-37 alert at the accounts payable clock, a Section 43B(h) MSME payment discipline that shortens the working-capital window on MSME suppliers to 45 days (or 15 days if there is no written agreement), and a Rule 37 education pass for the purchase and accounts payable teams. Detection control. A weekly Rule 37 ageing walk on the accounts payable ledger keyed to invoice date, with a 150 / 170 / 180-day escalation band and a monthly Rule 37 reversal computation for any invoice that crosses. See the Rule 37 and 37A ITC reversal guide for the reversal computation mechanics.

Failure mode 6 — Rule 37A supplier-non-filing reversal missed

Class. Partner. 6P. Partner / Process. Effect. The recipient claimed ITC in the current financial year on an invoice from a supplier who has not filed GSTR-3B by the 30 September of the following financial year. Rule 37A requires the ITC to be reversed by 30 November of the same year. Missing the reversal exposes the recipient to a DRC-01C intimation (because the GSTR-3B ITC will now exceed the GSTR-2B ITC on a comparable basis) and to Section 50 interest at 18% per annum from the ITC utilisation date. Severity 8 — the reversal is recoverable once the supplier files, and re-availment is not subject to the Section 16(4) time bar, but the intervening DRC-01C and interest exposure is material. Occurrence 6 — moderate, because the supplier universe filing GSTR-1 but skipping GSTR-3B is a defined subset of the compliance-defaulting supplier base. Detection 5 — the supplier’s GSTR-3B filing status is visible on the portal. Prevention control. A supplier watchlist that keys every purchase register supplier from GSTR-2B to their GSTR-3B filing status, with a quarterly refresh, and a contractual clause tying payment retention or a small holdback to the supplier’s GSTR-3B filing behaviour. Detection control. An annual Rule 37A walk in September of every year — for each supplier appearing in the recipient’s GSTR-2B for the closing financial year, verify GSTR-3B filing status and compute the reversal amount for any supplier who has not filed. The Rule 37A reversal is then filed in the November GSTR-3B.

Failure mode 7 — Section 17(5) blocked ITC claimed on motor vehicle repair

Class. Policy. 6P. Policy / People. Effect. The recipient wrongly claims ITC on a category listed in Section 17(5) — the working example is repair and maintenance of a motor vehicle that is not used for the specified onward taxable outward supplies (transportation of goods, passenger transportation service, driving school). When the claim is caught at internal audit or a Section 65 GST audit, the ITC is disallowed under Section 73/74 with interest at 18% per annum and, at CBIC’s discretion, a penalty. Other common Section 17(5) rows in an Indian purchase register are food and beverages, outdoor catering, health services, health and life insurance where not mandatory, membership of clubs and fitness centres, and works contract on immovable property (other than plant and machinery). Severity 8 — Section 73/74 recovery is material and interest under Section 50 applies from utilisation. Occurrence 6 — moderate, because the blocked-credit category surfaces routinely in office administration, sales team travel, and works contract lines. Detection 4 — low, because a preparer without a Section 17(5) checklist rarely catches it. Prevention control. A blocked-credit master keyed to HSN/SAC and payment description that gates ITC availment at posting time, a Section 17(5) checklist embedded in the monthly close pack, and a preparer training refresh on the blocked-credit list at the start of every financial year. Detection control. A monthly Section 17(5) sweep of the ITC availed against the HSN/SAC master, with a two-eyes review on any newly-availed category. See the Section 17(5) blocked ITC reference for the full category list and the specified-outward-supply exclusions.

Failure mode 8 — GSTR-2B pulled before supplier’s late GSTR-1 filing lands

Class. Timing. 6P. Period / Portal. Effect. The recipient pulls GSTR-2B on the 15th of a month, files GSTR-3B on the 18th, and later the supplier files a delayed GSTR-1 that would have added invoices to the recipient’s GSTR-2B for the tax period the recipient just closed. The ITC on those invoices is not lost — under the current framework it flows into the next tax period’s GSTR-2B — but the ITC availment is deferred by one month, and if the delay compounds across the March close it can push into the Section 16(4) time-bar zone. Severity 7 — the loss is a timing loss, not a permanent loss, unless it compounds to the November 30 cutoff. Occurrence 8 — high, because supplier late-filing is a routine feature of the Indian tax portal. Detection 4 — low, because the recipient does not naturally re-pull GSTR-2B after the initial close. Prevention control. A GSTR-2B pull cadence that includes a re-pull on the 20th and the 25th of the same month before GSTR-3B filing, and a supplier follow-up on high-value missing invoices between the 15th and the 20th. Detection control. A monthly reconciliation of the previous period’s purchase register against the current period’s GSTR-2B with a “late-arriving invoice” bucket, and a Section 16(4) ageing walk on every late-arriving invoice against the invoice date.

Failure mode 9 — Import IGST credit missed (Bill of Entry not reconciled)

Class. Completeness. 6P. Portal / Process. Effect. IGST paid on the import of goods is claimable as ITC once the Bill of Entry appears in the recipient’s GSTR-2B — the ICEGATE-GST portal integration populates the Bill of Entry ITC into GSTR-2B Table 5 (Amendments) and Table 4 (Original) depending on the port and the filing timeline. Where the Bill of Entry does not populate — because of a port-code mismatch, an ICEGATE-side filing delay, or an integration lag — the recipient’s finance team does not see the import IGST in GSTR-2B and does not claim it. If the miss carries to the November 30 cutoff, the import IGST is time-barred under Section 16(4). Severity 9 — near the Section 16(4) anchor because the amounts on a single import Bill of Entry can run into lakhs of IGST. Occurrence 5 — moderate, because ICEGATE integration is generally reliable but the port-code and port-timing edge cases surface routinely. Detection 5 — the Bill of Entry is visible in the recipient’s ICEGATE-side dashboard even if it has not landed in GSTR-2B. Prevention control. An import ITC master keyed to Bill of Entry number, port code, IGST amount, and ICEGATE filing status, with a monthly cross-check between the recipient’s ICEGATE ledger and GSTR-2B Table 5. Detection control. A monthly Bill of Entry reconciliation walk — every Bill of Entry filed by the recipient’s CHA must appear either in GSTR-2B or on the ICEGATE portal within the same or next tax period. The at-risk queue includes every Bill of Entry not yet in GSTR-2B with an ageing band.

Failure mode 10 — Credit note from supplier not tracked into ITC reversal

Class. Aging. 6P. Process / Partner. Effect. The supplier issues a credit note against an earlier invoice — for a quality claim, a return, a rate revision, or a rebate. The credit note appears in the supplier’s GSTR-1 and flows into the recipient’s GSTR-2B as a negative ITC line. The recipient’s finance team, tracking positive invoices only, misses the credit note and continues to hold the original ITC in the electronic credit ledger. On the annual reconciliation into GSTR-9 Table 8, the mismatch surfaces and the excess ITC must be reversed with interest under Section 50. In the interim, the DRC-01C mismatch simulation flags the differential and can trigger the intimation. Severity 7 — reversible but interest-bearing. Occurrence 6 — moderate. Detection 5 — the credit note is visible in GSTR-2B and in IMS. Prevention control. A credit note tracker on the supplier master, with a reconciliation to the goods return note and the debit note register at the recipient’s end. Detection control. A monthly walk of GSTR-2B credit notes against the recipient’s own credit note register, with a variance investigation on any mismatch.

Failure mode 11 — Multi-GSTIN entity: ITC claimed in the wrong GSTIN

Class. Classification. 6P. Policy / Process. Effect. A multi-GSTIN entity claims ITC in the wrong GSTIN — the invoice was billed to GSTIN A but the recipient’s finance team, working from a shared purchase register, posts the ITC to GSTIN B’s GSTR-3B. GSTIN A’s GSTR-2B shows the invoice as an unavailed ITC (because it was never claimed there) and GSTIN B’s GSTR-3B shows the ITC as a wrong-availment (because the invoice never appeared in GSTIN B’s GSTR-2B). The wrong-availment attracts recovery under Section 73/74 in GSTIN B and the missed availment carries a Section 16(4) exposure in GSTIN A. Severity 8 — the two-legged failure creates recovery in one entity and permanent loss in the other. Occurrence 5 — moderate on multi-GSTIN structures. Detection 5 — visible on cross-GSTIN reconciliation. Prevention control. GSTIN as a mandatory field at purchase invoice booking, with an ERP-level validation that the billing GSTIN on the tax invoice matches the posting GSTIN in the ledger. Detection control. A monthly cross-GSTIN reconciliation of GSTR-2B invoices against GSTR-3B availment, per GSTIN.

Failure mode 12 — Rounding-difference reject on paise-level GSTR-2B match

Class. Precision. 6P. Policy. Effect. The recipient’s reconciliation policy applies a zero-paise tolerance on the GSTR-2B versus purchase register match, and a routine paise-level rounding difference — GSTR-2B rounds to the paise, the recipient’s ERP rounds to the rupee, the arithmetic sums to a one-or-two-paise gap — flags a legitimate invoice as a mismatch. The invoice is excluded from the current period’s ITC availment. Severity 4 — the ITC is not lost, only deferred by one month, but the operational noise consumes reviewer capacity. Occurrence 8 — high. Detection 3 — the false positives are visible at every close. Prevention control. A reconciliation tolerance policy that permits a one-rupee-per-invoice variance on invoice value and a one-rupee variance on the tax amount, per CBIC clarifications on rounding. Detection control. A weekly exception review with a tolerance filter, so paise-level mismatches auto-clear without occupying reviewer attention.

Failure mode 13 — B2C invoice reclassified as B2B by supplier — mismatch surfaces late

Class. Classification. 6P. Partner / Period. Effect. The supplier originally treated a supply as a B2C sale (no invoice-level GSTR-1 population) and only later, on a supplier-side amendment, reclassified it as a B2B sale keyed to the recipient’s GSTIN. The invoice lands in GSTR-2B in a period much later than the original invoice date. The ITC is claimable in that later period, subject to the Section 16(4) deadline against the original invoice date. If the reclassification lands after the November 30 cutoff on the original invoice’s financial year, the ITC is permanently lost. Severity 6 — moderate, tending to Severity 10 if the reclassification lands after the cutoff. Occurrence 5 — moderate. Detection 6 — visible in GSTR-2B if the recipient monitors amendments. Prevention control. A supplier engagement protocol that requires the B2B classification at PO issue time, with the recipient’s GSTIN captured on every purchase order and communicated to the supplier’s billing team. Detection control. A monthly GSTR-2B amendment walk, with every reclassified invoice keyed to its original invoice date and its Section 16(4) exposure.

Failure mode 14 — Table 4 vs Table 6 GSTR-3B reconciliation not run

Class. Matching. 6P. Process. Effect. GSTR-3B Table 4 reports the total ITC availed for the period. Table 6 auto-populates the ITC available from GSTR-2B. A well-designed monthly close pack reconciles the two — the Table 4 availed number against the Table 6 available number, with the difference split between (a) ITC available but not yet availed (a timing item to carry to the next period) and (b) ITC availed above Table 6 (a DRC-01C exposure). Enterprises that skip the Table 4 vs Table 6 walk carry an undetected DRC-01C exposure into the annual GSTR-9 reconciliation, where the Table 8 auto-population makes the differential visible only at year-end. Severity 6 — the exposure is a DRC-01C tier rather than a Section 16(4) tier, but it carries interest and reviewer time. Occurrence 7 — high, because the Table 4 vs Table 6 walk is not part of the default monthly close template in most enterprises. Detection 5 — visible in the GSTR-3B if the walk is set up. Prevention control. The Table 4 vs Table 6 walk as a standing item in the monthly close pack with the difference explained in the reconciliation memo. Detection control. A monthly DRC-01C mismatch simulation that runs the Rule 88D threshold against the actual Table 4 vs Table 6 differential, so any period where the intimation would fire is flagged before the GSTR-3B is filed.

Summary — the Action Priority ranking

Ranked by Action Priority and Severity, the fourteen failure modes stack as follows.

High Action Priority — top of stack. #1 supplier GSTR-1 non-filing (S10), #3 IMS wrong Reject (S10), #9 import IGST Bill of Entry not reconciled (S9), #2 IMS Default-Accept on wrong invoice (S9), #4 inbound invoice booked to sibling entity (S9), #11 wrong-GSTIN availment on multi-GSTIN (S8), #7 Section 17(5) blocked ITC wrongly claimed (S8), #5 Rule 37 reversal missed (S8), #6 Rule 37A reversal missed (S8), #8 GSTR-2B pulled before late GSTR-1 lands (S7 with escalation to S10 near cutoff).

Medium Action Priority — middle of stack. #10 credit note not tracked (S7), #13 B2C-to-B2B late reclassification (S6 with escalation to S10 near cutoff), #14 Table 4 vs Table 6 walk not run (S6).

Low Action Priority — bottom of stack. #12 paise-level rounding reject (S4, high Occurrence, cheap to fix with policy change).

The at-risk ITC queue — the canonical High-AP detection control

The single detection control that catches the highest concentration of High Action Priority failure modes on the GSTR-2B stream — failure modes 1, 3, 5, 6, 8, 9, and 13 simultaneously — is the at-risk ITC queue. The queue is a rolling list of purchase register invoices where at least one applicable deadline is within the ageing window, sorted by earliest deadline and severity, with an escalation state per row and a closure path.

The applicable deadlines feeding the queue are the Section 16(4) November 30 cutoff (for every invoice whose supplier’s GSTR-1 has not landed in GSTR-2B), the Rule 37 180-day payment clock (for every invoice not yet paid to the supplier), the Rule 37A September 30 supplier-filing clock (for every supplier who has filed GSTR-1 but not GSTR-3B for the closing financial year), the IMS action deadline (for every document in Pending status approaching cycle-close default), the Bill of Entry ICEGATE-to-GSTR-2B lag window, and the amendment-window ageing on any reclassified invoice. Each row carries a days-to-deadline value, an ageing band (0-30 / 30-60 / 60-90 / 90-120 / 120+), and an escalation state (Reviewer Assigned / Supplier Follow-up Sent / Portal Action Pending / Escalated to CFO / Closed).

For an enterprise with fewer than 200 active suppliers and fewer than 3,000 purchase invoices per month, a manual detection layer — the queue rebuilt weekly in Excel or Google Sheets from a GSTR-2B extract and a purchase register export, filtered by days-to-deadline, walked by the assistant manager on a weekly cadence — is economically viable. The reviewer can walk every High-AP row in three to four hours a week, follow up with suppliers, log the escalation state on a shared sheet, and close the loop before the deadlines fire. This is where a manual reconciliation process holds up under audit-committee scrutiny.

Above roughly 200 active suppliers, or above roughly 3,000 purchase invoices per month, or on a multi-GSTIN structure with more than three GSTINs, the manual detection layer stops being economically viable. The queue length exceeds what a single finance team member can walk in a working week. The Rule 37 ageing walk, the Rule 37A annual walk, and the Section 16(4) November lockdown walk all compress into the same September-October-November window, and the queue is longest exactly when the review capacity is most constrained. At that threshold, the at-risk ITC queue must become a continuously-refreshed detection layer — populated automatically from a live purchase register, a scheduled GSTR-2B extract, and an IMS action log — with escalation triggers, an assigned owner per row, and a closed-loop supplier follow-up path. The queue then stops being a spreadsheet reviewed on a weekly cadence and becomes a first-class output of the reconciliation surface. Every High Action Priority row is worked to closure by its deadline rather than by the reviewer’s next scheduled walkthrough.

This is the point at which the reconciliation process design framework’s High Action Priority discipline outgrows a manual detection layer on the GSTR-2B stream — and it is why the GST reconciliation software surface exists as the layer that carries the queue continuously, and the reconciliation software India surface exists as the layer that carries every other stream’s High-AP queue on the same cadence discipline.

Closing note — why this stream deserves the process design treatment

Every reconciliation stream in an Indian finance function benefits from a formal failure-mode-and-cause discipline, but the GSTR-2B stream is the one where the discipline is not optional. The Severity-10 anchor is real, permanent, and unrecoverable. The IMS regime has added failure modes without removing any. Rule 37A has extended the reversal clock to the supplier’s tax-payment behaviour. DRC-01C has moved the mismatch surface from the annual return to the monthly close. And the fourteen failure modes catalogued here are not exhaustive — they are the fourteen that appear routinely in a well-run enterprise’s monthly close pack. A less well-run function will produce twenty, twenty-five, or thirty. The framework is the same; the row count is a function of the enterprise’s own operating maturity.

The reconciliation process design framework’s Action Priority table exists precisely to force the correct prioritisation on a stream where the materiality threshold is not the right heuristic — a Section 16(4) loss can start below the materiality threshold and compound. The 6P cause taxonomy exists to force the correct root-cause discipline on a stream where the cause is rarely the reviewer’s arithmetic and almost always the supplier, the portal, or the process. And the twelve-class failure mode taxonomy exists to name what can go wrong in a language that both the finance team and the audit committee can hold onto.

The at-risk ITC queue is the layer where all three come together — the framework’s severity discipline, its cause discipline, and its detection discipline, on a single sheet, on a rolling cadence, closed to zero by every deadline.

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 13 July 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024