GST Registration Across States: Separate the Applications and Records
A practical guide to gst registration across states, with a worked example, evidence checklist, common mistakes and steps to prepare a defensible working.
AI Summary
A business opens offices in three states; compare its common information with state-specific documents. The useful result is a working that explains the facts, the calculation or classification, and the evidence behind the conclusion. This guide shows how to prepare that working and where a reviewer should investigate before accepting the result.
Scope and applicable period
Indian GST; apply the law, notification and return version for the transaction’s own period. The worked figures are illustrative, not a declaration of a newly notified rate.
Verification date: 11 October 2026. Figures and rates identified as assumptions are teaching examples; apply the stated conditions and the actual facts to a real assignment.
The key principle
GST registrations are state/UT-specific. Common business information can support several applications, but premises, authorised persons and local evidence must be mapped to the correct registration. First establish whether a registration is legally required; a branch address alone should not replace that assessment. A common application workflow does not mean that different GSTINs have become one registration or one set of returns.
Worked example
| Item | Value or fact | What it means |
|---|---|---|
| State A | Head office | Common PAN; local premises proof |
| State B | Branch | State-specific business and signatory records |
| State C | Warehouse | Assess facts and local documentation |
| Control | One application tracker | Separate GSTIN, status and obligations |
Use one common master for legal name, PAN and constitution, then attach state-specific evidence to each application row. If a portal offers a multi-state initiation facility, confirm its current eligibility and screens from the official advisory before using it. Keep notices and approval dates separately. After approval, create a GSTIN-wise filing and ledger structure; shared ownership does not make inter-registration movements invisible for GST.
A practical sequence
Determine the business locations and the registration requirements first. Prepare one application file per relevant state with common PAN/entity evidence and the location-specific documents.
Track the application reference, queries and resulting GSTIN separately. Once registrations are active, assign invoicing, return and inter-branch records to the correct GSTIN.
A common ownership file helps preparation, but it does not merge separate state registrations or their compliance records into one return.
Keep transaction facts and return treatment separate
GST work involves several linked questions: what was supplied, which registration is involved, when liability arises, how it is valued and whether credit is available. A correct accounting entry does not answer all of them. Build the working at invoice level wherever practical, with transaction dates and document references. Reconcile values and tax separately, including amendments and reversals. When a rule or rate changes, use the notified effective date and conditions for the actual transaction; a Council recommendation or a software master update is not, by itself, the legal commencement of the change.
Evidence checklist
Keep the following records linked to the same entity, period and working version. Identify missing items explicitly; a checked box should mean the document was examined and supports the stated conclusion.
- PAN, constitution and legal-name records
- State-specific premises evidence
- Authorisation and signatory documents
- Business activity and registration-requirement assessment
- Application references, queries and approvals
Common mistakes and how to avoid them
- Uploading one state's premises proof to another. Compare the conclusion with the pan, constitution and legal-name records and resolve any conflicting facts.
- Assuming common initiation creates a single GSTIN. Trace the affected item to the authorisation and signatory documents before finalising the working.
- Forgetting the post-registration compliance setup. Use the application references, queries and approvals to make the final position and remaining exceptions clear.
Before you finalise
Recheck the example’s assumptions against the actual assignment, resolve the identified exceptions and make the final figure or conclusion traceable to its source. Preserve the reviewed version and the reason for material changes. For this task, the application references, queries and approvals should agree with the conclusion presented to the client, reviewer or authority.
Frequently asked question
Can all branches share one GST return because the PAN is common? Separate registrations require their own applicable compliance; the PAN is only a common identity input.
Sources and further reading
Related guide: Gst ims accept reject pending guide.