Commercial expansion creates GST registrations before finance teams often realise it.
Quick View
Review every new state presence before signing a lease, moving stock or accepting orders.
Create state-expansion checklist.
Lease or logistics contract.
Using head-office GSTIN everywhere.
Why It Matters
GST registration is state-specific. A place of business, warehouse, branch or fixed establishment can create registration and invoicing implications.
Registrations under the same PAN are distinct persons, making inter-branch supplies and common-cost allocation taxable or reportable under the GST framework.
Registration thresholds differ between goods and services and across specified states, while compulsory-registration rules and e-commerce conditions can override them.
Control Framework
| Area | What to establish | Operating rule |
|---|---|---|
| Presence | Office, warehouse, employee or fixed establishment. | Document facts. |
| Supply | Goods movement or service delivery. | Identify state. |
| Registration | Threshold or compulsory trigger. | Check before launch. |
| Inter-branch | Stock, services and common credit. | Design invoicing. |
Action Checklist
- Create state-expansion checklist.
- Review lease and warehouse model.
- Map supply routes.
- Assess registration trigger.
- Configure GSTIN and invoice series.
- Design branch and ISD controls.
Practical Example
Evidence to Keep
- Lease or logistics contract.
- Warehouse records.
- Employee and establishment evidence.
- Registration working.
- Stock-transfer invoices.
- State-wise return reconciliation.
Warning Signs
- Using head-office GSTIN everywhere.
- Ignoring third-party warehouse.
- Applying one threshold nationally.
- No branch transfer invoices.
- Late marketplace review.
Detailed Review
A defensible GST position must connect the commercial transaction, statutory rule, notification or circular, invoice, books, portal return and electronic ledger. A conclusion supported by only one layer is fragile.
Prepare an issue sheet that records GSTIN, period, tax head, amount, legal provision, effective date, evidence owner and approval. This is especially important where rates, thresholds or portal advisories changed during the year.
Reconcile by CGST, SGST, IGST and cess instead of only by total. An equal total can conceal tax paid to the wrong jurisdiction or credit recorded under the wrong registration.
Maintain original downloads and signed documents. Portal screenshots are useful context but should not replace JSON, returns, bills of entry, e-way bills, IRNs, ledgers, contracts and acknowledgements.
For judgemental matters, document competing interpretations and why one was selected. A short approval note created before filing is more credible than a justification written after a notice.
Run a monthly exception report and assign each difference to business, vendor, customer, tax or system owner. Close only when the corrected document or acknowledgement is retained.
Test one high-value transaction from contract to return every month. Sampling identifies master-data and evidence failures before annual reconciliation.
Transaction Test
Before filing, restate the transaction in one sentence using the legal parties, GST registrations, product or service, value, place, date and consideration. This often exposes hidden assumptions.
Test the result under an alternative fact: different customer GSTIN, delayed invoice, changed vehicle, partial vendor payment, exempt recipient or later cancellation. The control should explain why the tax outcome changes.
Create a gross-to-net bridge from commercial value to taxable value, tax, credit, payment and ledger effect. Avoid unexplained balancing figures.
Reconcile the counterparty’s likely records. Customer ITC, vendor GSTR-1, operator settlement, customs bill of entry and transport documents can contradict internal accounting.
Record the correction route before an error occurs: cancellation, credit note, amendment, reversal, re-availment, refund, DRC-03, representation or appeal.
Registration decisions should use separate goods and services thresholds, relevant state variation and compulsory-registration provisions. A single national threshold is not sufficient.
Review new warehouses, branches, marketplace arrangements and fixed establishments before commercial launch.
Escalation Route
Start with the commercial record, GST portal data and statutory working. Correct system or document errors through the prescribed process and retain the acknowledgement.
Where the matter is judgemental, disputed or enforcement-related, obtain a reasoned GST and legal review before payment, reply, refund, statement, appeal or restructuring.
Final Control
Management should record the financial exposure, cash-flow consequence, counterparty impact and statutory deadline for every unresolved GST issue. A tax difference can affect customer ITC, pricing, bank limits or business continuity even before an order is issued.
The control is complete only when the corrected invoice, portal filing, ledger entry, payment, refund, ruling, registration or authority communication is received and stored. An internal email saying that the issue is resolved is not closure evidence.
Common Questions
Does every employee create registration?
No. Facts must establish a place or fixed establishment.
Does a warehouse matter?
It can create a place-of-business and registration issue.
Are branches separate persons?
Different GST registrations under one PAN are distinct persons.
Can one state’s threshold be used everywhere?
No. Supply type, state and compulsory-registration rules must be checked.
Official Sources
- GST Common Portal
- CBIC — GST Acts, Rules, Forms, Notifications, Circulars
- GST Council — GST flyers and topic explainers
Use current Acts, Rules, notifications, circulars, advisories and transaction evidence. GST treatment can change by effective date, state, registration and facts.