What’s new

e-Invoicing compliance Timeline

Know More →

UAE e-Invoicing: The Complete Guide to Compliance and Future Readiness

Read More →

Types of Vendor Verification and When to Use Them

Read More →

Safeguard Your Business with Vendor Validation before Onboarding

Read More →

Modernizing Dealer/Distributor & Customer Onboarding with BridgeFlow

Read More →

Accelerate Vendor Onboarding with BridgeFlow

Read More →

GST Filing 360°: GST, E-Invoicing, E-Way Bills & Annual Returns Made Simple

Read More →

Why Manual Tax Determination Fails for High-Volume, Multi-Country Transactions

Read More →

GST Filing 360°: GST, E-Invoicing, E-Way Bills & Annual Returns Made Simple

Read More →

Key Features of an Invoice Management System Every Business Should Know

Read More →

Automating the Shipping Bill & Bill of Entry Invoice Operations for a Leading Construction Company

Read More →

From Manual to Massive: How Enterprises Are Automating Invoice Signing at Scale

Know More →

What’s new

AI-Powered Voice Assistant for Smarter Search Experiences

Explore More →

Cygnet.One’s GenAI Ideation Workshop

Know More →

Our Journey to CMMI Level 5 Appraisal for Development and Service Model

Read More →

Extend your team with vetted talent for cloud, data, and product work

Explore More →

Enterprise Application Testing Services: What to Expect

Read More →

Future-Proof Your Enterprise with AI-First Quality Engineering

Read More →

Cloud Modernization Enabled HDFC to Cut Storage Costs & Recovery Time

Know More →

Cloud-Native Scalability & Release Agility for a Leading AMC

Know More →

AWS workload optimization & cost management for sustainable growth

Know More →

Cloud Cost Optimization Strategies for 2026: Best Practices to Follow

Read More →

Cygnet.One’s GenAI Ideation Workshop

Explore More →

Practical Approaches to Migration with AWS: A Cygnet.One Guide

Know More →

Tax Governance Frameworks for Enterprises

Read More →

Cygnet Launches TaxAssurance: A Step Towards Certainty in Tax Management

Read More →

How to Manage Multi-State ISD and Allocate ITC Accurately Under GST
Input Service Distributor in GST

How to Manage Multi-State ISD and Allocate ITC Accurately Under GST

Manage multi-state ISD efficiently, allocate ITC accurately, ensure compliance, reduce errors, and streamline GST credit distribution across branches with automated workflows and clear visibility.

By Sayali Bagul ISD Operations May 7, 2026 15 minutes read

Introduction

When your head office procures common services – software licences, audit fees, legal advisory – on behalf of branches in different states, each branch needs its rightful share of the input tax credit. The Input Service Distributor (ISD) mechanism exists precisely for this: a registered office receives the vendor invoices, avails the credit, and distributes it to the consuming branches under the same PAN.

Now, ISD registration is no longer optional. Section 20 of the CGST Act now uses the word ‘shall’, making it mandatory for any office that receives input service invoices on behalf of distinct persons under the same PAN. This blog explains how to get multi-state ISD right – from the allocation formula to tax head conversion, reconciliation, and filing.

What Are Multi-State ISD Operations?

A multi-state ISD operation exists when a single legal entity holds GST registrations in two or more states or union territories, and one of those registrations acts as the ISD. The ISD office typically sits where invoices are received – usually the head office or a shared services centre. The branches consuming those services sit in other states.

Centralized procurement is common across industries. A manufacturing company may buy software licences, security services, and professional advisory services through its Mumbai head office, while its plants in Gujarat, Tamil Nadu, and Haryana use those services. An IT company may route all vendor contracts through Bengaluru, while its delivery centers in Hyderabad, Pune, and Delhi do the actual work. A bank may centralise audit and legal spending in one city while its branches operate across every state.

In every one of these structures, the ISD Support must register separately, receive the vendor invoices at its own GSTIN, avail the credit, and then distribute that credit to the branches before the end of the month in which the invoice was received.

Why Accurate Credit Apportionment Matters

Apportioning credits correctly is not a back-office task. It has direct consequences for your working capital, your tax liability, and your exposure to penalties. Here is why getting it right matters.

Compliance with GST Law

Rule 39 of the CGST Rules prescribe the exact formula for distribution. The amount distributed to any recipient cannot exceed the amount available with the ISD. Credit must be distributed in the same month it is received. Eligible and ineligible ITC must be distributed separately. Each tax head – CGST, SGST, IGST – must be distributed separately. Any deviation from these rules is a violation, not a procedural lapse.

Recovery of Excess Credit

Section 21 of the CGST Act is clear. If the ISD distributes credit in contravention of Section 20, the excess distributed to any recipient will be recovered from that recipient along with interest. The recipient bears the cost of a mistake made by the ISD. Under Section 122(1)(ix), wrongly availing or distributing credit can attract a penalty equal to the tax evaded, or the amount of credit wrongly distributed, whichever is higher.

Short distribution is equally problematic. If a branch does not receive its rightful share of credit, it is effectively overpaying tax. Across multiple branches and multiple months, even a small calculation error compounds into a significant working capital drain.

Audit and Scrutiny Risk

The GST portal matching mechanism compares ISD invoices filed in GSTR-6 with what the recipient branch claims in its GSTR-3B. A mismatch triggers a discrepancy of notice. Regular mismatches invite scrutiny. This is especially relevant for multi-state operations where the volume of invoices and branches multiplies to the surface area for error.

Working Capital Impact

ITC trapped at the ISD level because of incorrect distribution or missed deadlines cannot be set off against output tax liability at the branch level. Branches may then have to discharge output tax liability from their cash balance while credit sits unused at the ISD. In a business with twenty state-level GSTINs and hundreds of vendors invoices each month, the cumulative cash impact of poor ISD management is substantial.

Key Rules for Interstate ITC Allocation

The legal framework for ISD distribution sits in Section 20 of the CGST Act read with Rule 39 of the CGST Rules. The rule was amended by Notification No. 12/2024-Central Tax dated July 10, 2024, and made effective from April 1, 2025, by Notification No. 09/2025-Central Tax.

Foundational Conditions Under Section 20

  1. The amount of ITC distributed cannot exceed the total ITC available with the ISD in that month.
  2. Credit attributable to a specific recipient must be distributed only to that recipient.
  3. Credit attributable to more than one recipient must be distributed on a pro-rata turnover basis.
  4. All distribution must happen within the same calendar month.
  5. Eligible ITC and ineligible ITC must be distributed separately.
  6. Each tax head (CGST, SGST, IGST) must be distributed separately.

The Turnover Formula Under Rule 39

Where a common input service is attributable to more than one recipient, Rule 39 prescribes the following formula:

C1 = (t1 / T) x C   C  = Total ITC to be distributed t1 = Turnover of the specific recipient (R1) during the relevant period T  = Aggregate turnover of ALL recipients to whom the service is attributable,      during the same relevant period C1 = ITC to be distributed to recipient R1

This formula is applied separately for eligible and ineligible ITC, and again separately for each tax head. A business with four state-level GSTINs receiving a common invoice will run this formula up to eight times for a single invoice – four recipient ratios, each calculated for eligible and ineligible credit.

What Is the Relevant Period?

The term ‘relevant period’ in the formula is defined precisely by Rule 39:

SituationRelevant Period to Use
All recipients had turnover in the preceding financial yearThe preceding financial year
Some or all recipients had no turnover in the preceding financial yearThe last quarter (before the current distribution month) for which turnover data is available
New unit with no historical turnover at allTurnover of the current financial year up to the period preceding the distribution month

Tax Head Conversion Rules

This is where multi-state operations get technically complex. How the credit is distributed depends on the location of the recipient relative to the ISD.

Same State or Union Territory (ISD and recipient in same state) Distribute CGST as CGST and SGST as SGST – no conversion needed. Different State or Union Territory (ISD and recipient in different states) CGST and SGST of the ISD state must be combined and distributed as IGST to the out-of-state recipient. IGST credit must always be distributed as IGST to every recipient regardless of location.

In practice, this means an ISD in Maharashtra distributing credit from a CGST + SGST invoice to a branch in Karnataka must convert those two credit heads into a single IGST distribution. This conversion is not optional. Distributing CGST or SGST to a recipient in another state would be non-compliant.

Handling IGST Credit

IGST credit received at the ISD level must be distributed as IGST only, to every recipient – whether they are in the same state or a different state. There is no conversion of IGST to CGST plus SGST at the distribution stage.

Rule 39(1A) – RCM Services

Effective April 1, 2025, a new sub-rule 39(1A) allows a regular GSTIN with the same PAN and state code as the ISD to issue an invoice or credit/debit note to transfer RCM credit to the ISD. The ISD then distributes this credit in the same manner as other ITC. This closes to a gap that existed in the earlier framework where RCM credit could not flow through the ISD mechanism.

Challenges in Multi-State ISD Operations

The rules are clear in theory. In practice, businesses face a range of structural, data, and process challenges that make compliance harder than it looks.

Identifying Which Services Are Attributable to Which Branches

Not every service received at the ISD GSTIN benefits every branch. Some services benefit only at specific locations. Some benefit all of them. And some benefit the head office exclusively and should not be distributed at all. Mapping each vendor’s invoice to its beneficiary branches is a task that requires detailed review of contracts, cost-centre data, and business records. Without this mapping, you either over-distribute (risking recovery) or under-distribute (losing credit).

Managing Multiple GSTINs and Diverse Turnover Ratios

Every state-level GSTIN contributes a different turnover number to the denominator in the Rule 39 formula. A business with fifteen state-level GSTINs must track turnover for each of them every month. Turnover ratios shift month to month as business volumes change across regions. Using a stale or incorrect ratio produces a wrong allocation. This is not a trivial problem – even a 5% error in ratio across a high-value invoice can result in a material credit misallocation.

Data Fragmentation Across ERP Systems

Large organisations often have different ERP instances for different regions, or different accounting systems for different business units. Turnover data for the ratio calculation may sit in five different systems. Vendor invoice data arrives at the ISD GSTIN from dozens of suppliers, each with their own billing cycles. Pulling together all this data into a single, reconciled distribution run every month is operationally intensive.

Manual Errors in Allocation and Reporting

When distribution calculations are done in spreadsheets, errors creep in. Applying the formula manually for twenty branches across thirty invoices with six tax head variants is error prone. A mis-keyed figure in one cell affects the entire distribution for that month. These errors are only discovered at reconciliation time – often after GSTR-6 has already been filed.

Tight Filing Deadline

GSTR-6 must be filed by the 13th of the following month. There is only one day between GSTR-1 filing (due by the 11th) and the GSTR-6 deadline. This leaves very little time for corrections. Any delay in receiving vendor invoices, updating turnover data, or running allocation calculations can push the filing past the deadline, attracting a late fee of Rs. 25 per day under CGST (plus an equal amount under SGST).

New Units and Zero-Turnover Branches

New branches – especially those set up mid-year – may have no preceding-year turnover to use as the basis for allocation. Rule 39 provides for using the last available quarter turnover in such cases but identifying and applying that rule manually requires vigilance. Similarly, branches that make only exempt supplies or are unregistered still receive a share of the distributed credit in the denominator calculation, which can be counterintuitive but is required by law.

How to Apportion Credits Correctly

There is a standard approach provided in the act to credit apportionment under the ISD framework.

Turnover-Based Allocation (Standard Method)

This is the method prescribed by Rule 39. It uses each branch’s turnover as a proxy for how much of the common service it consumes. It is simple to apply, legally defensible, and works well when services are genuinely used by all branches roughly in proportion to their size.

The calculation follows these steps:

  1. Identify the relevant period for each recipient – preceding financial year, or last available quarter for new units.
  2. Collect the turnover of each recipient for that period.
  3. Calculate the allocation ratio: t1 divided by T for each recipient.
  4. Apply the ratio to the eligible ITC and ineligible ITC separately.
  5. Apply the formula again for each tax head: CGST, SGST, IGST.
  6. Convert CGST + SGST to IGST for all out-of-state recipients.
  7. Issue separate ISD invoices to each recipient of GSTIN.

Key rule: The total IGST distributed to out-of-state recipients equals the sum of CGST and SGST that would have been distributed to them. The ISD does not create additional tax – it converts the tax head to match the interstate nature of the transaction.

Role of Automation in Multi-State ISD

Doing multi-state ISD operations manually is possible for a business with two or three GSTINs and a handful of common invoices. For any business at scale, it is not. The combination of monthly distribution, tax head conversion, formula application across multiple recipients, and tight filing deadlines makes automation a practical necessity rather than a luxury.

Automated Allocation Engines

A purpose-built allocation engine handles the Rule 39 formula automatically. You configure which services are attributable to which branches. The engine fetches the turnover data for the relevant period, computes the ratio for each recipient, applies the formula, handles tax head conversion, and generates ISD invoices – all without manual intervention.

Benefits of Automation

Manual ProcessAutomated Process
Formula applied in spreadsheets, prone to errorsFormula executed by system with validation checks at each step
Tax head conversion done manuallySystem detects same-state vs interstate and applies correct conversion
ISD invoices typed or copy-pastedISD invoices generated in bulk with correct format and data
GSTR-6 prepared by compiling multiple sourcesGSTR-6 populated directly from distribution engine output
Errors discovered post-filingValidation flags errors before filing

Reconciliation and Compliance Management

Distribution is only half the job. The other half is reconciliation – making sure what the ISD distributed matches what the branches received, and that both match what is reflected in the GST portal.

Matching ISD Credits with Vendor Invoices

Before distributing credit, the ISD must confirm that the input credit available in its electronic credit ledger matches the vendor’s invoices received. Any vendor who has not filed their GSTR-1, the invoice will not appear in GSTR6A at the ISD level. Distributing credit that is not yet confirmed in GSTR-6A creates a mismatch at the recipient level.

Matching ISD Invoices with Branch Claims

Each ISD invoice becomes a line item in GSTR-6. The credit distributed via that invoice must appear in the recipient branch’s GSTR-2B and be claimed in its GSTR-3B. If the branch does not claim the credit reflected in GSTR-2B, it loses that credit for the period. If it claims more than the ISD distributed, there will be a mismatch.

Handling Mismatches and Corrections

Corrections to ISD distributions are handled via ISD credit notes (for reduction) and ISD debit notes or fresh ISD invoices (for increases). A credit note reduces the credit previously distributed. The reduction applies in the same month as the credit note, or – if the net result is negative – is added to the recipient’s output tax liability.

The key rule: corrections must be made in the month they are identified. You cannot carry forward a correction to a future month or apply it to a prior month’s return once that return has been filed. This puts a premium on catching errors quickly, before the filing deadline.

Audit Trail for ITC Distribution

Every ISD invoice, every distribution calculation, every credit note or debit note adjustment must be logged with timestamps and user details. An auditor examining your ISD compliance will want to trace every rupee of distributed credit from the original vendor invoice through the formula calculation to the final ISD invoice and the branch’s GSTR-3B claim. Gaps in this trail are red flags.

Timely GSTR-6 Filing

GSTR-6 is due by the 13th of each month. This return captures all invoices received by the ISD, all credit distributed, and all ISD invoices and credit notes issued. Once filed, corrections can only be made in the next month’s return. The 13th deadline is non-negotiable and applies regardless of how many branches are being serviced.

Future Outlook

The shift from optional to mandatory ISD is part of a broader GST maturation process. The government is moving toward a system where credits are tracked in real time, matched at source, and less susceptible to fraudulent or erroneous claims. Several trends are shaping the future of ISD compliance.

Real-Time Credit Matching

The GSTN system is progressively moving toward real-time credit availability. Vendor-uploaded GSTR-1 data feeds into recipient GSTR-2A and IMS dynamically. For ISD operations, this means credit availability at the ISD level will increasingly be determinable within days of the invoice date, not weeks. Businesses with live integrations to the GST portal will be able to initiate distribution faster and avoid the last-minute rush before the 13th.

ERP Integration

Leading ERP platform are building native ISD modules following the April 2025 mandate. These modules handle master data (ISD GSTIN, branch GSTIN mapping, attribution rules), automate the formula calculation, and generate compliant ISD invoices directly within the ERP. For finance teams, this means one less reconciliation layer between the accounting system and the GST compliance system.

AI-Assisted Attribution

Identifying which services benefit which branches currently requires manual review of contracts and cost-centre data. AI-assisted attribution tools are beginning to automate this step – reading invoice descriptions and contract terms, comparing them with branch activity data, and recommending attribution rules. This is still early-stage but is likely to reduce the attribution burden significantly for large multi-state operations.

Greater Regulatory Scrutiny

As ISD becomes mandatory, the GST department is likely to increase scrutiny of GSTR-6 filings. Mismatches between ISD distributions and branch claims will be flagged more systematically. The best protection is a clean, automated, and well-documented ISD process – one that can withstand detailed examination without requiring manual reconstruction.

Conclusion

Multi-state ISD operations are now a mandatory compliance function for every organization that procures common input services centrally and operates across more than one state. The framework is clear: Rule 39’s turnover formula, same-month distribution, separate treatment of eligible and ineligible ITC, and correct tax head conversion for interstate recipients.

The complexity lies not in understanding the rules but in applying them reliably at scale. Fifteen branches, thirty vendors, a tight filing window, and a zero-tolerance policy on over-distribution – these are the real challenges. Manual processes can handle them only up to a point. Beyond that point, automation is the only way to achieve both accuracy and efficiency.

The organisations that manage their ISD operations well will see real business benefits: credit flowing to the right branches without delays, working capital freed up, audit risk reduced, and no unnecessary penalties eroding margins. Efficient ISD is not just compliance with hygiene – it is tax efficiency and financial discipline working together.