Multi-GSTIN Consolidation Playbook for Pan-India Businesses

Quick answer. Operating across multiple states means each state needs its own GSTIN under the same PAN. Each GSTIN is a distinct person under GST, they file their own returns, hold their own ITC, and supplies between them are taxable. The operational discipline is: (1) decide your registration footprint deliberately (where to register, where to skip), (2) flow inter-state branch transfers through proper invoicing with IGST, (3) use ISD for centrally-procured services, (4) cross-charge for centrally-rendered services, (5) maintain consolidated books at the legal entity level even though filings are per-GSTIN, (6) reconcile at year-end into a consolidated GSTR-9 and 9C. Done by hand across 10 states = 120 monthly returns and a permanent audit fire drill. Done with a unified system = the consolidation is automatic.

The “distinct persons” problem

Section 25(4) of the CGST Act treats each registered GSTIN under the same PAN as a distinct person. That sounds harmless until you look at the consequences:

A movement of stock from your Karnataka GSTIN to your Maharashtra GSTIN is a supply under GST. IGST applies. Your Maharashtra GSTIN claims ITC. The consolidated revenue is unchanged but the supply event is real.
Common services rendered by HQ to all branches are also supplies. Either ISD (Input Service Distributor) machinery applies, or HQ cross-charges with IGST.
A purchase by HQ used by the whole group needs its ITC distributed to the right consuming GSTINs.
An audit at year-end consolidates books across GSTINs but compares to per-GSTIN portal data.

For a business with 1 GSTIN, none of this matters. For 5+ GSTINs, every one of these mechanics is a recurring operational concern.

Decide your registration footprint deliberately

A finance team should know why each GSTIN exists. The four legitimate reasons:

Mandatory, you have an establishment in that state (warehouse, office, employees, fixed place of business). GST registration is mandatory under Section 22 read with Schedule II.
Voluntary for ITC capture, you have an installation that procures locally and you don’t want IGST-only accumulation in another state.
Customer-driven, a major buyer requires you to invoice from a specific state for their own ITC mechanics.
Operational efficiency, a centralised dispatch hub simplifying logistics.

GSTINs you should avoid taking on:

“Just in case” registrations for states you might enter later, adds compliance burden with no revenue benefit
“Sales office” with no inventory or fixed place, usually doesn’t trigger mandatory registration if it’s just a marketing presence
Pop-up exhibition stalls for < 30 days, use a casual taxable person registration instead, which is time-bounded

Each new GSTIN = one more set of monthly GSTR-1 + 3B + reconciliation. Don’t add lightly.

Branch transfers, moving stock between GSTINs

When stock moves from one of your GSTINs to another (same PAN, different state):

Issue a tax invoice from the sending GSTIN to the receiving GSTIN. IGST applies (it’s an inter-state supply).
Generate an e-way bill if the consignment value ≥ ₹50,000. The EWB references the tax invoice.
E-invoice if you’re in scope (₹5 cr+ aggregate turnover). The IRN flows the same way as a customer invoice, it’s a supply, just an internal one.
Receiving GSTIN posts the inward supply in its books. Claims ITC of the IGST charged.
Reconcile in the next 2B, the sending GSTIN’s GSTR-1 will show this supply; the receiving GSTIN’s 2B will show it as inward.

The trap: teams treat branch transfers as “internal movements” and skip the invoicing. That fails GST, leaves the e-way bill missing (interception risk during transit), and creates ITC leakage.

Valuation for branch transfers

Section 15 + Rule 28 of CGST: the value of supply between distinct persons is the open market value. Two practical implementations:

Cost + reasonable margin, straightforward for finished goods.
MRP, abatement, for FMCG / regulated-MRP categories.
Open market value where receiving GSTIN claims full ITC, under the second proviso to Rule 28, if the receiving GSTIN is going to claim full ITC anyway, the value declared by the sender is deemed to be the open market value. This is a cleaner approach for material transfers between fully-eligible GSTINs.

Document your valuation policy once; apply it consistently. Auditors care about the policy more than the specific number.

ISD, Input Service Distributor

When services are billed to the head office but consumed across multiple branches (e.g., a software licence for the whole group, audit services, security services), ISD machinery distributes the ITC.

The mechanic:

HQ obtains a separate ISD registration (different from its regular GSTIN; explicit ISD registration under Section 24).
Vendors invoice the ISD GSTIN.
ISD GSTIN claims the ITC.
ISD distributes the ITC to operating GSTINs by issuing an ISD invoice under Rule 39.
Distribution ratio is based on the recipients’ turnover in the relevant period.

Filings:

ISD files a monthly GSTR-6 (different from regular GSTR-1/3B). Due 13th of next month.
The receiving GSTINs see the distributed ITC in their GSTR-6A / 2B.

ISD is only for services. Not goods. For goods, use branch transfers with IGST.

When ISD is mandatory (post Apr 2025)

The Finance Act 2024 made ISD machinery mandatory for distributing ITC of common input services across distinct persons, with effect from 1 April 2025. Before this, companies could (and many did) cross-charge for services in lieu of ISD. Post April 2025, the cross-charge route for centrally-procured services is no longer available, you must use ISD.

This single change has reshaped multi-GSTIN architectures across India. Every group with central procurement of services should have an ISD registration in place.

Cross-charging, for services rendered, not procured

ISD distributes ITC of services procured centrally. Cross-charging is the mechanism for services rendered by one GSTIN to another (same PAN, different state).

Common cases:

HQ in Karnataka providing accounting services to operating GSTINs in 5 other states.
A central IT team in Maharashtra providing infra to the whole group.
A regional office in Delhi providing legal/regulatory services to nearby branches.

The mechanic:

Issuing GSTIN charges the receiving GSTIN with IGST under a regular tax invoice.
E-invoice if applicable.
Receiving GSTIN claims ITC.
Valuation: cost + reasonable margin (Schedule I supplies between distinct persons; Rule 28 applies same as for goods).

The risk if you skip cross-charging: in audit, the IT department may treat the centrally-rendered services as a supply that should have been invoiced. Demand + interest on unbilled supplies, plus disallowance of any related expense.

The conservative practice for multi-GSTIN groups: codify a cross-charge schedule (which GSTIN charges which, for what categories, at what frequency) and run it monthly.

Place of Supply, the rules that bite

For a multi-GSTIN business, place of supply determines which GSTIN should issue the invoice. The default rules (CGST Sections 10, 11, 12, 13):

Category	Place of supply
Goods, B2B with movement	Where the goods are delivered (buyer’s location)
Goods, B2C with movement	Where the goods are delivered
Goods, no movement (e.g., installation)	Where installation happens
Services to a registered person	Buyer’s location
Services to unregistered person	Seller’s location (mostly)
Real-estate-related services	Where the property is located
Restaurant / catering / personal grooming	Where services are performed
Training / event-related services	Where the event is held
Telecom services	Per specific rules in Section 12(11)
Banking, financial, insurance	Buyer’s location

For multi-GSTIN sellers: which of your GSTINs issues the invoice? The answer is the GSTIN that’s in the same state as the place of supply if you have one; otherwise IGST from your closest registered GSTIN. Most companies route per the buyer’s state.

The consolidation problem at year-end

Your books are kept at the legal entity (PAN) level. Your filings are at the GSTIN (state) level. At year-end, you need:

GSTR-9 per GSTIN, the annual return
GSTR-9C per GSTIN above ₹5 cr aggregate turnover, the reconciliation between books and GSTR-9
Income tax return at the PAN level

The reconciliation gap:

GSTR-9 shows turnover and tax for the GSTIN in that state.
The legal entity’s P&L shows total revenue across states.
The two should reconcile minus the inter-GSTIN supplies (which inflate state-level turnovers but are eliminated at consolidation).

A robust system maintains a “consolidated view” that:

Sums GSTR-1 / 3B turnover across GSTINs
Subtracts inter-GSTIN supplies (which appear as both outward in the sending GSTIN and inward in the receiving GSTIN)
Reconciles to the audited financials

If this can’t be done by mid-October, GSTR-9 is filed late.

The operational architecture

For a 10-state group, the recommended architecture:

LEGAL ENTITY (PAN)
  │
  ├─ HQ + ISD GSTIN (centrally-procured services)
  │     ↓ ISD invoices distribute ITC
  │
  ├─ Operating GSTIN, Karnataka
  │     ↓ books, GSTR-1/3B, reconciliation
  │
  ├─ Operating GSTIN, Maharashtra
  │     ↓
  │
  ├─ Operating GSTIN, Tamil Nadu
  │     ↓
  │
  └─ Operating GSTIN, ... (other states)
        ↓
  ALL FEED INTO →
        ↓
  CONSOLIDATED LEDGER (legal entity level)
        ↓
  Audited financials
        ↓
  GSTR-9 per GSTIN + GSTR-9C reconciliation
        ↓
  Consolidated income tax return at PAN

The cleanest implementation:

One system holds books for every GSTIN in one tenant
Each transaction tagged to the right GSTIN automatically (place of supply derives the GSTIN)
Inter-GSTIN supplies (branch transfers, cross-charges) are first-class entities, not ad-hoc journal entries
ISD GSTIN’s distributions auto-post to receiving GSTINs
Period locks per GSTIN (one GSTIN can be closed for the month while another is still open)
Consolidated reports run on demand at legal entity level

Common operational pitfalls

Pitfall	Frequency	Impact
Branch transfers without invoices	High	E-way bill missing → interception; ITC leakage
Cross-charges done irregularly or skipped	High	Audit risk; possible demand + interest
ISD not registered for centrally-procured services	High (post Apr 2025 rule change)	ITC stranding; non-compliance
Different invoice number sequences per GSTIN colliding	Medium	E-invoicing rejection (DocNo uniqueness)
GSTR-9 filed without inter-GSTIN reconciliation	Medium	Mismatch with audited financials → 9C qualifications
Place of supply determined manually per invoice	Medium	Errors, especially for inter-state services
Vendor master not GSTIN-aware	Medium	Wrong GSTIN on bills; ITC blocked
Period locks not consistent across GSTINs	Low	Backdated entries in already-filed periods

CFO dashboard, multi-GSTIN view

Beyond the standard GSTR-3B view per GSTIN, a multi-GSTIN finance leader watches:

Aggregate turnover at PAN level (drives e-invoicing applicability, audit thresholds)
Inter-GSTIN supply volume, total branch transfers + cross-charges, MoM trend
ISD distribution health, % of common-input ITC successfully distributed
State-by-state ITC accumulation, states with persistent ITC stranding
GSTR-9 readiness per GSTIN, at any month, what’s the gap between books and filed
At-risk vendors per GSTIN, vendor non-filers driving stranded ITC
Compliance calendar, every state’s deadlines on one view

Without this view, multi-GSTIN compliance is reactive, discovered at year-end audit, by which time fixing is expensive.

The 90-day setup plan

For a business expanding from 1 to 5+ GSTINs:

Weeks	Milestone
1–2	Decide registration footprint deliberately (which states, why). File registrations.
3	Set up ISD registration if HQ procures services centrally.
4	Configure invoice number sequences per GSTIN to avoid collisions.
5–6	Codify cross-charge schedule. Document valuation policy for inter-GSTIN supplies.
7	Books platform configured for multi-GSTIN tagging. Place of supply derivation rules.
8	First inter-GSTIN supply run (branch transfer + cross-charge) end-to-end. Verify e-invoice + EWB.
9	Vendor master GSTIN tagging. Each vendor mapped to which GSTIN should receive its bill.
10–11	First monthly GSTR-1 + 3B per GSTIN, reconciled against consolidated books.
12	First MOM GSTR-2B reconciliation per GSTIN, with stranded ITC tracker.
13	Compliance calendar for the year. ISD GSTR-6 cadence locked.

Most groups stabilise by month 6, anything unstable beyond that points to upstream ERP or master-data issues.

Tooling: what to look for

Multi-GSTIN tenancy, one tenant, many GSTINs, one user identity
Place-of-supply derivation at the line level, not the invoice level
Inter-GSTIN supply as a first-class entity with linked sender/receiver invoices
ISD module that posts GSTR-6 and auto-distributes ITC
Per-GSTIN period locks, one state can close while others stay open
Consolidated reports at legal entity level on demand
State-by-state compliance calendar
GSTR-9 / 9C automation with books-vs-portal reconciliation per GSTIN
Vendor / customer master with GSTIN-level alternate-name handling

OneFinOps is built for multi-GSTIN, multi-entity, multi-country businesses out of the box. Branch transfers, ISD distribution, cross-charging, and consolidated GSTR-9 reconciliation are native, not bolt-on. Start a free trial or book a 30-min walkthrough.

Frequently asked questions

Do I need a GSTIN in every state where I have customers?

No. You need a GSTIN in every state where you have a fixed place of business (warehouse, office, employees, manufacturing). Pure customer presence (selling B2B from another state) doesn’t trigger registration, your existing GSTIN charges IGST.

What’s the difference between a “branch” and a “casual taxable person”?

A branch is a permanent establishment requiring full GST registration. A casual taxable person (CTP) is for short-term presence (< 90 days), e.g., an exhibition stall, a project site. CTP files monthly GSTR-1/3B for the period it’s active and de-registers. Use CTP for genuinely temporary, < 90-day operations.

Can multiple business verticals under one PAN have separate GSTINs in the same state?

Yes, Section 25(2) allows separate registration for “different business verticals” in the same state. Useful if (e.g.) you run a manufacturing operation and a wholly different trading line. Each vertical operates as a distinct person, with all the inter-vertical supply consequences. Most companies don’t do this, it doubles compliance burden for limited operational benefit.

What changed about ISD in April 2025?

Before April 2025, distributing ITC of common input services could be done either via ISD or via cross-charge. Post April 2025, ISD is the only valid mechanism for distributing ITC of centrally-procured services to distinct persons. Cross-charging now applies only to services rendered by one GSTIN to another, not for redistributing input ITC.

How does GSTR-9 reconcile with consolidated books?

GSTR-9 is per GSTIN. Sum across GSTINs = aggregate turnover including inter-GSTIN supplies. The consolidated books exclude inter-GSTIN supplies (they’re eliminations). The reconciliation note in your GSTR-9C should explicitly call out inter-GSTIN amounts and the elimination.

Should every GSTIN have its own bank account?

Operationally, yes, keeps audit trail clean and simplifies state-specific cash management. From a compliance perspective, GST doesn’t require it (the bank account is a PAN-level entity). Most listed groups maintain one account per GSTIN; smaller groups consolidate to one or two.

What if our HQ GSTIN itself is also an operating GSTIN?

Common pattern. The HQ GSTIN is dual-role, it’s an ISD for distributing service ITC (with a separate ISD registration) AND an operating GSTIN with its own customers and books. Two separate GSTINs (regular + ISD) under the same PAN, in the same state. Filings are independent.

Can the same employee work across multiple GSTINs?

Yes, as long as the legal entity is one PAN. From a payroll perspective, the employee is on one PF/ESI/PT register tied to the state where they’re physically based. From an internal cost-allocation perspective, that employee’s cost can be cross-charged from their home GSTIN to the GSTINs that benefit from their work.

Sources

CGST Act, 2017, Sections 22, 24, 25, 10–13, registration, distinct persons, place of supply.
CGST Rules, 2017, Rules 28, 39, valuation between distinct persons; ISD distribution.
Finance Act, 2024, ISD mandatory for common input services from 1 Apr 2025, change in distribution mechanism.
GSTR-2B Reconciliation Playbook, E-Invoicing Implementation Playbook, adjacent OneFinOps guides.

This guide is operational, not legal advice. Specific cases, particularly ISD vs cross-charge classification edge cases, valuation policies for inter-GSTIN supplies, and consolidation under Ind AS, should be reviewed with your tax counsel.

Multi-GSTIN Consolidation: The Operational Guide for Pan-India Businesses