GST for Multiple Branches: Multi-GSTIN Filing Checklist
- Each regular GSTIN files its applicable returns separately. There is no single statutory return for all registrations under one PAN.
- PAN-level turnover may decide eligibility or applicability, but return preparation, tax payment, and reconciliation happen GSTIN by GSTIN.
- Common input-service credit covered by the ISD provisions must be distributed through an Input Service Distributor.
- Match outward supplies, input tax credit and inter-branch transfers before filing each return.
- Use a PAN-level dashboard for review, but retain separate books, ledgers and supporting records for every registration.
Managing GST for multiple branches is mainly a coordination challenge. A PAN-level threshold can affect several registrations, but an error must usually be corrected in the GSTIN where it occurred. A clear monthly process helps prevent missed invoices, wrong-branch ITC, unmatched stock transfers and late returns.
This guide is for finance heads, accountants and multi-branch businesses managing two or more GST registrations under the same PAN.
See Every GSTIN in One View
Compare liabilities, ITC, pending returns, and branch-level exceptions without combining multiple spreadsheets.
How Multi-GSTIN Filing Works
Under Section 25 (4) and 25(5) of the CGST Act, separate registrations covered by these provisions are treated as distinct persons. A business with four regular GSTINs may therefore need four GSTR-1 returns and four GSTR-3B returns for the same period.
Accounting software may combine data for management review, but consolidated filing does not mean that the GST portal accepts one combined GSTR-1 or GSTR-3B. Each registration retains its own return history, electronic ledgers and supporting records.
PAN-Level Tests and GSTIN-Level Actions
Section 2 (6) defines aggregate turnover on an all-India basis for persons having the same PAN. This PAN-level figure can affect e-invoicing, QRMP eligibility, and annual-return requirements. The related compliance is then handled for each applicable GSTIN .
| Compliance Area | Main Test | Action Required |
|---|---|---|
| E-invoicing | PAN-level aggregate turnover against the notified threshold | Each covered GSTIN reports its applicable documents |
| QRMP eligibility | PAN-level aggregate turnover up to ₹5 crore | Filing frequency is managed for each eligible GSTIN |
| GSTR-1 and GSTR-3B | Applicable to the registration | Filed separately for each GSTIN |
| GSTR-9 | Section 44 and any exemption notified for the relevant financial year | Filed by each applicable regular GSTIN |
| GSTR-9C | Aggregate turnover above ₹5 crore under Rule 80(3) | Filed GSTIN-wise by each applicable regular registration |
| GSTR-6 | ISD registration | Filed separately by the Input Service Distributor |
Compliance Area
Main Test
Action Required
Compliance Area
Main Test
Action Required
Compliance Area
Main Test
Action Required
Compliance Area
Main Test
Action Required
Compliance Area
Main Test
Action Required
Compliance Area
Main Test
Action Required
Do not assume that a small branch is outside a PAN-level rule. For example, Notification 10/2023-Central Tax applies the ₹5 crore e-invoicing threshold where aggregate turnover exceeded ₹5 crore in any relevant preceding financial year from 2017-18 onwards, subject to the notified exclusions.
Set Up Multi-GSTIN Filing Controls
Maintain a GSTIN Control Register
Keep one register containing each GSTIN, state, registration type, filing frequency, responsible preparer, reviewer, authorised signatory, pending periods and current status. Include inactive branches until their registrations are formally cancelled.
This register should also identify which registration acts as the ISD and which branches operate under QRMP. It gives the finance head one reliable view without mixing the underlying return records.
Standardise Masters and Invoice Series
Use a controlled process for HSN and SAC codes, tax rates, units, place-of-supply rules and customer GSTINs across all branches. When a tax rate or master changes, update every affected registration rather than correcting only one branch.
Rule 46 requires a consecutive invoice serial number , not exceeding 16 characters, in one or multiple series and unique for the financial year. A branch or state code is not compulsory, but it can make invoice tracing easier. Unexplained gaps should be investigated and documented.
Assign Clear Ownership
For every GSTIN, name the person who prepares the return, the person who reviews it, and the authorised signatory who files it. Also assign ownership for purchase reconciliation, inter-branch matching, and ISD distribution.
A branch should never assume that head office completed a task unless the filing tracker shows the return status and acknowledgement reference number.
Multi-GSTIN Filing Checklist
| Stage | Checkpoint | Evidence to Retain |
|---|---|---|
| 1 | Close sales, purchases, credit notes, debit notes and branch transfers for each GSTIN | Period-close report |
| 2 | Match the sales register with GSTR-1 or IFF | Invoice-level reconciliation |
| 3 | Correct current-period outward-supply errors through GSTR-1A before GSTR-3B | Amendment working |
| 4 | Match the purchase register with GSTR-2B and review IMS records | ITC reconciliation |
| 5 | Check whether invoices belong to the correct recipient GSTIN | Supplier correction tracker |
| 6 | Match inter-branch transfers at the sending and receiving GSTINs | Transfer-wise reconciliation |
| 7 | Review output tax, RCM, ITC reversals, interest and cash requirements | GSTR-3B working |
| 8 | Review ISD invoices and common-service allocation | GSTR-6 and distribution working |
| 9 | Check cash and credit ledger balances for each GSTIN | Ledger download |
| 10 | File, save the ARN and update the central compliance tracker | Filed return and ARN |
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Stage
Checkpoint
Evidence to Retain
Reconcile Returns and Ledgers Before Filing
Match Books With GSTR-1
For each GSTIN, compare the sales register with GSTR-1 or IFF before filing. Review missing invoices, duplicate document numbers, wrong customer GSTINs, incorrect place of supply , tax-rate errors, credit notes, debit notes, and branch transfers.
GSTN made auto-populated outward liability in GSTR-3B non-editable from the July 2025 tax period. If the current period’s GSTR-1 or IFF contains an error, use GSTR-1A before filing the corresponding GSTR-3B. Do not depend on correcting the liability directly in GSTR-3B.
Review ITC for the Correct GSTIN
Match each registration’s purchase register with GSTR-2B and review the related Invoice Management System records. Separate eligible credit from blocked credit, reverse-charge transactions, disputed invoices, credit notes and invoices that belong to another branch.
An invoice appearing in GSTR-2B does not by itself make the credit eligible . Section 16 and the applicable rules still have to be satisfied. Where a supplier has used the wrong recipient GSTIN, ask the supplier to correct the invoice and return data instead of claiming the credit in another registration.
Match Inter-Branch Transfers on Both Sides
Schedule I covers supplies between distinct persons in the course or furtherance of business even when made without consideration. A taxable stock transfer between different GSTINs should therefore be checked at both registrations.
The sending GSTIN should record the outward supply and tax. The receiving GSTIN should confirm receipt, verify the document in GSTR-2B and test ITC eligibility . A mismatch can leave output tax reported at one branch while the other branch cannot support its credit claim.
Review Cash and Credit Separately
Electronic credit cannot be freely shifted from one GSTIN to another. The cash ledger has a limited transfer facility.
Section 49 (10)(b) and Rule 87 (14) allow eligible amounts under the CGST or IGST heads to be transferred through FORM GST PMT-09 to a distinct person under the same PAN, provided the transferor has no unpaid liability. Use this only after checking the ledger heads and the receiving GSTIN.
Prepare Each Branch Before Filing
Standardise records, match transactions and close branch books faster before GSTR-1 and GSTR-3B filing.
Handle ISD and Cross-Charge Correctly
Distribute Common Input-Service Credit Through ISD
From 1 April 2025, Section 20 requires an office that receives input-service invoices for or on behalf of distinct persons to register as an Input Service Distributor and distribute the related credit.
This generally covers third-party services purchased centrally for one or more GSTINs, such as common software subscriptions, advertising, audit or legal services. Under Rule 39 :
- Credit attributable only to one recipient must be distributed only to that recipient.
- Credit shared by more than one recipient must be distributed among the relevant recipients using the prescribed turnover ratio.
- Eligible and ineligible credit must be distributed separately.
- Credit available for distribution in a month must be distributed in the same month and reported in GSTR-6.
ISD applies only to input services. It cannot be used to distribute credit on goods or capital goods.
Document the Cross-Charge Position
Cross-charge concerns an actual supply made by one GST registration to another distinct GST registration. It commonly applies to internally generated services, such as central management, finance, IT or administrative support provided by head office to branches.
Cross-charge should not be used merely to distribute input tax credit from third-party common-service invoices. Such credit must be handled through ISD where Section 20 applies.
CBIC Circular 199/11/2023-GST explains that where the receiving branch is eligible for full ITC, the value declared in the invoice is treated as the open-market value. For internally generated services, where full ITC is available and no invoice is issued, the value may be deemed to have been declared as nil. The salary cost of head-office employees is not mandatorily required to be included in the taxable value.
This treatment is not a blanket exemption. The business should document the nature of the service, the recipient GSTIN, ITC eligibility, valuation method and treatment adopted.
| Point | ISD | Cross-Charge |
|---|---|---|
| Main purpose | Distribute ITC on third-party input-service invoices received for or on behalf of distinct persons | Account for an actual supply between distinct GST registrations |
| Common example | Software, advertising, audit or legal services purchased centrally | Management, finance, IT or administrative support provided internally |
| Main references | Section 20 and Rule 39 | Schedule I, Rule 28 and Circular 199/11/2023-GST |
| Turnover ratio | Used where the service benefits more than one relevant recipient | Not an automatic valuation method |
| Document or return | ISD invoice or credit note and GSTR-6 | Tax invoice where required, subject to Circular 199 |
| Goods covered | No | Supplies of goods between distinct persons may separately be taxable |
Point
ISD
Cross-Charge
Point
ISD
Cross-Charge
Point
ISD
Cross-Charge
Point
ISD
Cross-Charge
Point
ISD
Cross-Charge
Point
ISD
Cross-Charge
Complete Annual and Long-Term Checks
Confirm GSTR-9 and GSTR-9C Applicability
Do not treat ₹2 crore as a permanent GSTR-9 exemption for every year. Section 44 permits the Commissioner to exempt specified classes through a notification. Check the exemption issued for the relevant financial year before finalising the filing list.
Rule 80(3) requires GSTR-9C where aggregate turnover during the financial year exceeds ₹5 crore, subject to the exclusions in the rule. An ISD does not file GSTR-9 or GSTR-9C.
Clear Returns Before the Three-Year Limit
The Finance Act, 2023 inserted a three-year filing restriction into Sections 37, 39, 44 and 52. The restriction came into force on 1 October 2023 through Notification 28/2023-Central Tax. GSTN implemented portal-level barring from 1 October 2025 for covered returns whose due dates had crossed the three-year limit.
Run a quarterly review of old periods across every GSTIN. Pay particular attention to dormant branches, acquired registrations and nil returns that were never filed. Do not assume that a future relaxation will be available.
Close Cancelled Registrations Properly
When a regular branch closes, complete the cancellation process, reconcile stock and liabilities, and check whether GSTR-10 is required. Simply stopping branch GST filings does not close the registration.
Section 45 requires a registered person covered by Section 39(1), whose registration has been cancelled, to furnish a final return within three months of the cancellation date or the cancellation order, whichever is later. Rule 81 prescribes FORM GSTR-10.
Worked Multi-GSTIN Example
A company has regular GST registrations in Maharashtra, Karnataka and Delhi, along with a separate ISD registration.
| Transaction | Correct Review |
|---|---|
| A software invoice received by the ISD carries ₹1,80,000 of GST and benefits all three branches | Allocate the common credit among the relevant recipients using the Rule 39 turnover ratio |
| A legal-services invoice received by the ISD carries ₹18,000 of GST and relates only to Karnataka | Distribute the full credit only to the Karnataka GSTIN through ISD |
| Maharashtra transfers taxable stock to Delhi | Match the outward supply, tax invoice, GSTR-1 reporting, receipt and Delhi’s ITC eligibility |
| Delhi needs cash while Maharashtra has eligible surplus CGST cash and no unpaid liability | Consider a PMT-09 transfer after checking the statutory conditions |
Transaction
Correct Review
Transaction
Correct Review
Transaction
Correct Review
Transaction
Correct Review
This example shows why GST for multiple branches needs both PAN-level review and GSTIN-level evidence. The figures are illustrative, and the actual treatment depends on the documents, valuation, place of supply and ITC eligibility.
Use GSTIN-Wise Reports for Management Review
GSTIN-wise reports should show turnover, output tax, ITC claimed, ITC under review, cash paid, pending returns and unmatched inter-branch entries for each registration.
The finance head can combine these reports into a PAN-level dashboard without confusing management reporting with consolidated filing. The dashboard should highlight exceptions, but the supporting reconciliation must remain available at GSTIN level. Useful monthly exceptions include:
- a branch whose GSTR-1 turnover does not match its books
- credit claimed against an invoice addressed to another GSTIN
- a transfer reported by the sending branch but missing at the receiving branch
- common-service invoices retained at head office instead of routed through ISD
- an old return approaching the three-year limit
How BUSY Supports Multi-GSTIN Compliance
BUSY supports multi-GSTIN and multi-branch operations, separate branch records, GST return workflows, reconciliation and branch-specific or consolidated reports. Its Enterprise edition also supports GSTIN-level compliance and PAN-wise turnover visibility.
Use BUSY to organise branch data and branch-level reports, while keeping the review and filing responsibility with the authorised finance and tax team. Explore BUSY accounting software for multi-branch compliance management
Conclusion
A reliable GST process for multiple branches begins with one control register and ends with separate, supported filings for every registration. The group should review PAN-level thresholds, but each branch must reconcile its own sales, purchases, ITC, transfers and ledgers.
Keep the monthly checklist focused on exceptions. Match both sides of inter-branch transactions, route common-service credit through ISD, document the cross-charge position and clear old periods before the filing restriction applies. This creates a consolidated management view without weakening the GSTIN-level audit trail .
