Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Finance teams continue to operate GSTR-2B reconciliation under pre-October-2024 assumptions, where GSTR-2B was auto-populated and passive. The October 2024 IMS rules made GSTR-2B the output of an active decision pipeline. Without updating the workflow, ITC claims in GSTR-3B will be systematically misaligned with the IMS-decided GSTR-2B, triggering Rule 36(4) compliance gaps and DRC-01C notices.
The new GSTR-2B compliance loop has five stages: supplier GSTR-1 filing, IMS dashboard population by the 12th, buyer Accept/Reject/Pending action before the 14th cut-off, GSTR-2B generation on the 14th reflecting IMS state, and continued IMS action until the 20th deadline updating GSTR-2B. Compliance requires automated participation in all five stages with audit-trail capture at each step.
IMS dashboard pull schedule aligned to the 12th-14th window, decision engine fed by purchase-register match logic, 30-day Pending aging threshold with deemed-accept alert, post-decision GSTR-2B re-pull, and reconciliation against accepted-set ITC before GSTR-3B preparation.
Post-decision GSTR-2B aligned with the purchase register, Pending queue with aging timestamps, GSTR-3B Table 4 ITC reconciled to the accepted set, and Rule 36(4) audit pack capturing the decision timestamp for every invoice.
GSTR-2B was a passive statement for the first five years of GST in India. The buyer downloaded it on the 14th, reconciled it against the purchase register, claimed ITC up to that amount on GSTR-3B by the 20th, and the cycle closed. Since October 2024, GSTR-2B has been the output of an active decision pipeline — the Invoice Management System. The compliance workflow that worked in 2023 produces structurally incomplete results in 2026. This article maps the change and the automation that closes the gap.
Pre-IMS GSTR-2B Mechanics (Before October 2024)
The pre-IMS workflow had three actors and a clean handoff:
- Supplier filed GSTR-1 by the 11th of the month.
- GST portal aggregated GSTR-1 entries and generated buyer-side GSTR-2B on the 14th.
- Buyer downloaded GSTR-2B, reconciled against purchase register, claimed ITC on GSTR-3B by the 20th.
The buyer had no input into what appeared in GSTR-2B. Errors — wrong-GSTIN filings by suppliers, amount mismatches, fictitious invoices — had to be resolved through the supplier filing an amendment in a later cycle. There was no preventive control.
Post-IMS GSTR-2B Mechanics (October 2024 Onwards)
The IMS layer inserts a buyer-side decision stage between supplier filing and GSTR-2B generation:
- Supplier files GSTR-1 (rolling, with the 11th deadline).
- GSTR-1 entries populate the buyer’s IMS dashboard by the 12th.
- Buyer reviews each invoice and posts Accept, Reject, or Pending decision before the 14th cut-off.
- GSTR-2B is generated on the 14th, reflecting only invoices currently in Accepted state (explicitly Accepted, or aged into deemed-accept).
- Buyer can continue to act on IMS between the 14th and the 20th, updating GSTR-2B before GSTR-3B filing.
The static lock falls on the 20th (GSTR-3B filing). After GSTR-3B is filed for the period, the IMS state for that period is closed. Any further change requires a supplier-side GSTR-1 amendment in a later cycle.
For the canonical specification, the GST portal hosts the live IMS dashboard under the GSTR-2B services menu.
Side-By-Side Comparison
| Element | Pre-IMS (Before Oct 2024) | Post-IMS (Oct 2024 Onwards) |
|---|---|---|
| GSTR-2B source | Auto-populated from supplier GSTR-1 | IMS-decided subset of supplier GSTR-1 |
| Buyer action | None (read-only) | Accept / Reject / Pending per invoice |
| Mismatch handling | Reconcile after the fact | Preventive — Reject before GSTR-2B locks |
| Time window for action | None | 12th to 20th (≈ 9 days) |
| Audit trail | Purchase register + GSTR-2B | Purchase register + IMS decision timestamp + GSTR-2B |
| Section 16(4) time limit interaction | Static | Pending aging counts toward time limit |
The compliance work has moved from after-the-fact reconciliation to in-cycle decision-making.
The IMS Feed-In Pipeline, Stage By Stage
Stage 1 — Supplier files GSTR-1. Filing happens between the 1st and the 11th of the month for the previous tax period. Larger suppliers file on the 11th; smaller suppliers file earlier.
Stage 2 — IMS dashboard populated. By the 12th, the GST portal has aggregated all GSTR-1 entries where the buyer’s GSTIN is recipient. The IMS dashboard exposes these as actionable lines.
Stage 3 — Buyer action window opens. From the moment an invoice appears in IMS, the buyer can post Accept, Reject, or Pending. The 30-day deemed-accept clock starts here.
Stage 4 — Pre-generation cut-off (14th). GSTR-2B is generated on the 14th. Whatever IMS state each invoice holds at this moment determines whether it appears in GSTR-2B.
Stage 5 — Continued action window (14th to 20th). Buyer can change IMS decisions during this window. GSTR-2B updates in real time. Final ITC is locked when GSTR-3B is filed by the 20th.
The 9-day total window from the 12th to the 20th is the entire IMS work cycle. For high-volume buyers, daily pulls starting from the 1st of the month spread the work across 20 working days.
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 →The 30-Day Buffer Mechanic
The 30-day buffer applies to Pending status. An invoice marked Pending in IMS retains that state for 30 days from first appearance. If the buyer takes no further action, the invoice is treated as Accepted on day 31 and flows into the next applicable GSTR-2B.
This buffer is the safety net for invoices that need supplier follow-up. It is also the trap for unwatched Pending queues — an invoice the buyer would have rejected gets quietly Accepted on day 31 if the team doesn’t review.
A disciplined operating workflow surfaces Pending items at day 25 for final review before deemed-accept. The cost of missing this review is the loss of the Reject option — the buyer can no longer claim the invoice was incorrect, because the system has already deemed-Accepted it.
Timing Risk: Pending vs Explicit Reject
The semantic difference between Pending and Reject has real timing consequences:
- Reject: Invoice excluded from current and future GSTR-2B. Decision is final unless supplier files an amendment. ITC permanently unavailable on this invoice line.
- Pending: Invoice deferred for up to 30 days. After 30 days, deemed-Accepted. ITC available in the next GSTR-2B cycle. If the buyer takes explicit Accept earlier, ITC available immediately in next GSTR-2B; if buyer takes explicit Reject before day 31, same outcome as direct Reject.
For invoices the buyer is confident are wrong (other-GSTIN filings, fictitious amounts), explicit Reject is the cleaner action. Pending is for cases where the buyer needs to investigate or check with the supplier — and the investigation has a hard 30-day deadline.
Cross-Linking to the Three-Way Reconciliation
The post-IMS GSTR-2B sits in a three-way reconciliation between purchase register, IMS dashboard, and the post-decision GSTR-2B itself. See IMS vs GSTR-2B reconciliation for the full three-source compare. The downstream check between GSTR-2B and GSTR-3B is covered in the GSTR-2B reconciliation guide, and the outward-supply cross-check in GSTR-1 vs GSTR-3B reconciliation.
What Automation Covers in the New GSTR-2B Compliance Loop
For buyers with more than 500 inward invoices per month, manual operation of the 9-day window is unsustainable. Automated workflows in a purpose-built GST reconciliation software cover:
- Daily IMS dashboard pull starting from the 1st of each month.
- Purchase-register match per invoice with decision recommendation.
- 30-day Pending aging tracker with day-25 alert.
- Post-decision GSTR-2B re-pull and three-way reconciliation.
- Rule 36(4) audit-trail capture for every Accept timestamp.
- GSTR-3B Table 4 ITC values produced from the accepted set.
For integrated multi-process reconciliation environments — GST plus TDS plus bank plus settlement — a unified reconciliation software India approach is the equivalent layer for the broader compliance stack. The single point: GSTR-2B is no longer a passive feed, and the compliance workflow must reflect that.