Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Enterprises with 3 to 15+ GSTINs across Indian states face per-GSTIN IMS dashboards with no portal-side consolidation. State teams operating in isolation produce inconsistent decision discipline, miss inter-entity stock-transfer reconciliations, and create audit-trail gaps under Rule 36(4) compliance.
A consolidated workflow pulls each GSTIN's IMS dashboard, normalises the data into a single decision queue keyed on supplier GSTIN plus invoice number plus buyer GSTIN, applies a common decision engine against a shared purchase master with state-to-GSTIN mapping, identifies inter-entity stock transfers as paired entries, and routes exceptions to the appropriate state or central authority before posting back to the relevant GSTIN dashboard.
Per-GSTIN portal credentials, state-to-GSTIN mapping in purchase master, intercompany invoice identification rules, role-based authority split (central versus state), and per-GSTIN audit-trail capture aligned to Rule 36(4).
Consolidated cross-GSTIN IMS decision queue, per-GSTIN exception report, intercompany stock-transfer reconciliation report, per-GSTIN post-decision GSTR-2B, and group-level audit pack with per-GSTIN breakdown for Rule 36(4) compliance.
A pharmaceutical manufacturer with eight GSTINs across Maharashtra, Karnataka, Tamil Nadu, Telangana, Gujarat, Madhya Pradesh, West Bengal, and Uttar Pradesh maintains eight separate IMS dashboards on the GST portal. Each dashboard has its own decision queue, its own monthly GSTR-2B, its own GSTR-3B filing, and its own Rule 36(4) audit-trail. The group has 3,200 monthly inward invoices spread across these eight entities. Without a consolidated workflow, eight state finance teams operate in parallel, intercompany stock-transfer invoices reconcile inconsistently, and the group has no visibility into total ITC discipline. This article maps the consolidated workflow design.
Why the GST Portal Forces Per-GSTIN Operation
The GST portal is structurally organised by GSTIN. Each registered GSTIN has its own login (or sub-login), its own filings, its own GSTR-2B, and its own IMS dashboard. There is no portal-side consolidation across GSTINs even within the same PAN.
This is intentional. Each GSTIN is a separate registration under the CGST Act with separate compliance obligations. The portal enforces this through per-GSTIN data segregation.
The operational consequence: any consolidation must happen outside the portal in a reconciliation tool that pulls each GSTIN’s data, applies a unified decision engine, and posts decisions back to each dashboard.
The Three Operating Models for Multi-GSTIN IMS
Model 1 — Shared Service Centre (centralised). A central AP team handles IMS for all GSTINs. The team runs the decision engine against a consolidated purchase master, posts decisions to each GSTIN dashboard, and prepares each GSTR-3B. State finance owners are informed but do not act.
Best for: groups with standardised supplier base, central procurement, uniform decision rules. Risk: state-specific tax treatment differences (e.g., compounded levies, specific exemptions) may be missed by central operators.
Model 2 — Decentralised State Operation. Each state finance team owns its GSTIN’s IMS dashboard, applies local decision rules, and prepares its own GSTR-3B. Group-level reporting consolidates after-the-fact.
Best for: groups with state-distinct operations, local supplier bases, and state-level finance autonomy. Risk: inconsistent decision discipline across states; intercompany transfers reconcile poorly.
Model 3 — Hybrid (most common). Central operations runs the automated decision engine and posts Accepts on clean matches. State teams own Pending and Reject decisions for their GSTIN. Central also handles intercompany stock-transfer reconciliation.
Best for: groups with 5+ GSTINs. Combines central efficiency with state-level expertise on local exceptions.
Consolidated Purchase Master with State-to-GSTIN Mapping
The shared purchase master is the spine of the consolidated workflow. Each purchase register entry carries:
- Supplier GSTIN.
- Buyer GSTIN (which state entity received this purchase).
- Invoice number, date, tax period.
- Taxable amount, CGST, SGST, IGST.
- State of supply (for intra-state vs inter-state classification).
- Internal cost-centre and warehouse code.
The state-to-GSTIN mapping ensures that each inward invoice is evaluated against the correct entity’s IMS dashboard. A supplier filing under Maharashtra-GSTIN must match against the buyer’s Maharashtra-GSTIN, not the Karnataka-GSTIN.
For groups with central procurement and state-level delivery, the mapping logic is: where was the invoice raised against? That GSTIN owns the IMS decision.
Inter-State Stock Transfer IMS Impact
Inter-state stock transfers within the same legal entity attract IGST. The dispatching GSTIN raises an invoice on the receiving GSTIN, filing it in GSTR-1. The receiving GSTIN sees this in its IMS dashboard as an inward invoice with IGST.
These should always Accept — the dispatching side has already filed; the goods have been transferred internally; the IGST is recoverable. The internal control is to confirm pairing: every IGST-bearing inward invoice from an internal GSTIN should have a matched outward entry on the dispatching side.
Mismatches typically indicate one of three issues:
- Dispatching side filed but receiving side hasn’t recorded the goods receipt yet (timing).
- Receiving side recorded but dispatching side filed under a different invoice number (entry error).
- One side recorded internally but the other treated it as a third-party transaction (classification error).
The intercompany reconciliation discipline that applies to traditional financial flows applies equally to IMS. See intercompany reconciliation for the broader framework.
Worked Example: Manufacturer With 8 GSTINs, 3,200 Monthly Invoices
A diversified manufacturer with operations in 8 states runs a hybrid IMS model:
- Total monthly inward invoices: 3,200, distributed roughly proportional to operational scale.
- Maharashtra (largest plant): 1,100 invoices.
- Karnataka: 600 invoices.
- Tamil Nadu: 500 invoices.
- Telangana: 320 invoices.
- Gujarat: 280 invoices.
- MP, WB, UP: 100, 180, 120 invoices respectively.
Central operations (shared service centre) handles:
- All Tier 1 strategic supplier auto-Accept (60 percent of total volume, ~1,920 invoices). Decisions posted to each GSTIN dashboard.
- All intercompany stock-transfer reconciliation. Roughly 180 paired entries per month (90 outward, 90 inward) across the 8 GSTINs.
- Group-level Rule 36(4) audit-pack consolidation.
State finance teams handle:
- Tier 2 mid-tier supplier review (25 percent of volume, ~800 invoices). State team reviews auto-recommendation and overrides exceptions.
- Tier 3 tail supplier Reject decisions (15 percent of volume, ~480 invoices). State team posts Reject directly.
- State-specific exemption claims (e.g., specific input categories with state-level treatment).
Distribution of touchpoints across the month:
- Central touchpoints: 60 (intercompany pairing exceptions plus group-level reviews).
- State touchpoints (combined across 8 states): 240 (mid-tier reviews and tail Rejects).
- Total: 300 manual decisions, with 70 percent of volume flowing through auto-Accept.
This is the operating shape that makes multi-GSTIN IMS sustainable. A purely decentralised model would force each state to recreate the decision engine. A purely centralised model would lose state-level supplier expertise.
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 →Audit-Trail Compliance Per GSTIN Under Rule 36(4)
Rule 36(4) compliance is per-GSTIN. Each GSTIN’s monthly audit pack must independently contain:
- Purchase register entries for that GSTIN.
- IMS Accept timestamps for that GSTIN’s decisions.
- Post-decision GSTR-2B for that GSTIN.
- GSTR-3B Table 4 figures for that GSTIN.
- Actor identity for each Accept (authorised user under that GSTIN).
The group-level audit pack stitches these into a single document, but the underlying evidence is per-GSTIN. Centralised execution does not collapse the audit trail; each GSTIN’s evidence chain stands alone.
Cross-Process Integration
For multi-GSTIN enterprises, IMS rarely sits in isolation. The same group typically runs TDS reconciliation under the new tax-year regime, NACH bounce handling for vendor payments, bank reconciliation across 20+ accounts, and platform-settlement reconciliation if any e-commerce channel is involved.
A unified reconciliation software India approach handles these in a single compliance workflow, with shared master data (vendor master, GSTIN master, bank account master) reducing duplicate maintenance across the processes. The GST reconciliation software component handles IMS specifically within this broader architecture.
For the underlying IMS-versus-GSTR-2B mechanics, see IMS vs GSTR-2B reconciliation. For the downstream GSTR-2B-to-GSTR-3B check, see the GSTR-2B reconciliation guide.