1. What Section 20 does
Section 20 answers a practical question: when a central office receives input-service invoices for multiple GST registrations, how should eligible ITC be passed to the correct registrations?
Under GST, registrations held by the same legal entity in different States or Union territories are treated as distinct persons for specified purposes. A head office may receive software, audit, professional consultancy, advertising, insurance, common subscriptions and other centrally procured services benefiting one or several registrations. The ISD mechanism creates a controlled route for distributing the corresponding input-service credit.
2. What is an Input Service Distributor?
An ISD is an office of the supplier of goods or services or both that receives tax invoices for input services on behalf of distinct persons and is required to distribute eligible ITC to the appropriate recipients.
Receives eligible input-service invoices.
Operates the prescribed credit-distribution mechanism.
Receive credit based on attribution and the statutory formula.
Reports the ISD distribution.
Section 24(viii) is the linked registration provision, while Section 20 governs distribution. The current text expressly requires the relevant office to be registered as an ISD. citeturn0search1
3. Current statutory structure
| Provision | Subject | Practical meaning |
|---|---|---|
| 20(1) | ISD registration and distribution | Office receiving input-service invoices for distinct persons must be registered as ISD and distribute the ITC. |
| 20(2) | Credit to be distributed | Covers CGST/IGST charged on invoices, including specified reverse-charge input-service credit, subject to prescribed manner, time, restrictions and conditions. |
| 20(3) | Tax character | CGST may be distributed as CGST or IGST; IGST may be distributed as IGST or CGST, through the prescribed document. |
Finance (No. 8) Act, 2024 substituted Section 20(1) with effect from 1 April 2025; Finance (No. 7) Act, 2025 inserted the corresponding reference to specified IGST reverse-charge services with effect from the same date. citeturn0search1
4. Mandatory ISD from 1 April 2025
The GST Council had considered whether ISD should be mandatory for common input services received by a head office and attributable to branches. The 50th Council recommended making the ISD procedure mandatory prospectively; the 53rd Council agenda records the proposed Section 20 and Rule 39 framework. citeturn0search3turn0search20
| Period | Broad position |
|---|---|
| 1 July 2017–31 March 2025 | Historical ISD framework; the exact legal position must be tested for the relevant period and facts. |
| From 1 April 2025 | Current Section 20 requires the relevant office to register as ISD and distribute covered input-service credit through the ISD mechanism. |
The Council's records describe the prospective policy for third-party input services attributable to multiple or particular branches and specified reverse-charge input services. citeturn0search23
5. Reverse-charge input services
The expanded regime specifically addresses input services on which tax is payable under reverse charge. Section 20 now refers to reverse charge under Section 9(3) and 9(4) of the CGST Act and, through the 2025 amendment, specified reverse-charge services under Section 5(3) and 5(4) of the IGST Act.
The 55th GST Council recommended the amendment expressly including inter-State RCM references in Section 20 with effect from 1 April 2025. citeturn0search19
6. Recipient GST registrations
The recipient is the GST registration entitled to receive the distributed credit. Correct recipient identification is therefore the first allocation control.
| Service | Analysis |
|---|---|
| Exclusively benefits Maharashtra GSTIN | Analyse distribution to Maharashtra only. |
| Exclusively benefits Telangana GSTIN | Analyse distribution to Telangana only. |
| Benefits several registrations | Use the prescribed common-credit allocation mechanism. |
| No identifiable eligible recipient | Do not mechanically distribute merely because several GSTINs share a PAN. |
The principle is attribution first, allocation second.
7. Attributable vs common input services
Single-recipient services
If an input service can be directly attributed to one recipient registration, the credit should be analysed for distribution to that recipient rather than spread across all registrations.
Multi-recipient services
Where the service benefits multiple registrations, the prescribed proportionate distribution mechanism applies.
Common services
Central audit, enterprise software, group-level consultancy, common advertising and certain insurance arrangements can be common services depending on the facts.
8. Distribution mechanics
Section 20 provides the statutory framework while Rule 39 supplies the detailed operational methodology.
- Identify the eligible input-service invoice.
- Determine whether it is attributable to one recipient or multiple recipients.
- Determine the credit legally available for distribution.
- Apply the prescribed allocation formula where common.
- Issue the prescribed ISD document.
- Report through the ISD return.
- Reconcile the distribution with recipient GSTIN records.
The Council material records the principle that credit attributable to one recipient should go only to that recipient and common credit should be distributed pro rata using the prescribed methodology. citeturn0search3
9. CGST and IGST treatment
Section 20(3) establishes the tax-character rule for distributed credit.
| Credit received by ISD | Current statutory possibility |
|---|---|
| CGST credit | CGST or IGST, as prescribed. |
| IGST credit | IGST or CGST, as prescribed. |
The actual allocation must follow current Rule 39. An ERP should therefore not hard-code a simplistic “CGST always stays CGST” rule.
10. Turnover-based allocation for common services
Where credit is attributable to more than one recipient, the prescribed Rule 39 methodology uses a turnover-based proportion in the situations specified by the Rules.
GST Council drafting material expressly described pro-rata distribution based on turnover in the State or Union territory for common credit. citeturn0search7
Because Rule 39 has changed over time, historical allocations should be tested against the rule applicable to the relevant month.
11. Detailed practical examples
Example 1 — software used by one GSTIN
A centrally received software licence is exclusively used by Karnataka. Analyse it as attributable to Karnataka rather than distributing it to every registration.
Example 2 — common professional service
A centrally received professional service benefits Maharashtra, Telangana and Karnataka. After eligibility is established, distribute the common credit under the applicable Rule 39 methodology.
Example 3 — national advertising
A national campaign benefits several registrations. Retain campaign documents and establish the recipient population before applying the common-credit formula.
Example 4 — RCM service from 1 April 2025
A covered centrally received input service is subject to reverse charge. The current ISD framework must be considered; RCM status does not by itself remove it from Section 20.
Example 5 — over-distribution
An ISD cannot distribute more credit than is actually available. Invoice-level reconciliation should prevent over-distribution.
Example 6 — tax-head error
Even where total distributed credit is arithmetically correct, incorrect CGST/IGST reporting can create a compliance mismatch.
Example 7 — construction group
A central office incurs common software, audit and legal-service costs for multiple project GSTINs. The ISD master should identify which registrations benefit from each service and retain the allocation working.
Example 8 — recipient changes
If the group's GST registrations or business structure changes, update the recipient master before distributing recurring monthly services.
12. GSTR-6 and reconciliation
GSTR-6 is the return associated with the ISD mechanism. The ISD should reconcile books, source invoices, distributed credit and return data before filing.
| Reconciliation | Check |
|---|---|
| Supplier invoice → books | Invoice received and eligible ITC recorded. |
| Books → allocation | Recipient and common-credit basis supported. |
| Allocation → ISD document | Amount and tax heads agree. |
| ISD document → GSTR-6 | Reported distribution agrees with books. |
| GSTR-6 → recipient records | Recipient has accounted for the distributed credit. |
13. Legislative development
14. GST Council background
The Council's records explain the policy development behind the present ISD framework.
| Development | Relevance |
|---|---|
| 12th meeting / original design | Initial ISD distribution framework. |
| 28th meeting | Turnover-definition wording relevant to common-credit distribution. |
| 50th meeting | Prospective mandatory ISD recommendation. |
| 53rd meeting | Detailed Section 20 and Rule 39 amendment framework. |
| 55th meeting | Inter-State RCM references in ISD provisions. |
The Council records provide legislative background; the operative position must be determined from the enacted Act, commencement provisions and Rules applicable to the relevant date. citeturn0search19turn0search3
15. Professional controls
Maintain recipient GSTINs.
Map recurring services to recipients.
Track centrally received input services.
Single vs multi-recipient.
Apply current Rule 39.
Validate CGST/IGST.
Match books and return.
Confirm credit reached intended GSTIN.
16. Common mistakes
- Continuing an old head-office invoice model after 1 April 2025 without checking the mandatory ISD framework.
- Distributing every central invoice equally to every GSTIN.
- Ignoring actual service attribution.
- Using management-accounting allocation instead of the prescribed statutory method.
- Ignoring covered RCM input services.
- Distributing more credit than available.
- Using the wrong tax head.
- Failing to reconcile GSTR-6 with recipient records.
- Applying today's Rule 39 formula to a historical period without checking the applicable rule.
- Assuming a common PAN alone proves that every GSTIN is a recipient of the service.
17. Audit documentation
| Document | Purpose |
|---|---|
| Supplier tax invoice | Source of input service and credit. |
| Agreement/SOW | Supports recipient attribution. |
| Cost-centre/user mapping | Supports business-use analysis. |
| Allocation working | Supports common-credit formula. |
| Turnover data | Supports prescribed pro-rata distribution where applicable. |
| ISD document | Evidence of distribution. |
| GSTR-6 | Return evidence. |
| Recipient reconciliation | Confirms credit reached intended GSTIN. |
| RCM payment evidence | Important for covered reverse-charge services. |
18. Practical workflow
- Identify centrally received input services.
- Check ITC eligibility.
- Check whether Section 20 covers the service.
- From 1 April 2025, apply the mandatory ISD framework where applicable.
- Classify the invoice as recipient-specific or common.
- Identify recipient GSTINs.
- Calculate distribution under current Rule 39.
- Validate tax heads.
- Issue the prescribed ISD document.
- Report in GSTR-6.
- Reconcile recipient ITC.
- Archive the supporting working.
20. Key takeaways
- Section 20 is the core statutory provision for ISD credit distribution.
- From 1 April 2025, the expanded ISD framework is mandatory for covered input-service credit.
- Specified reverse-charge input services are expressly included.
- Attribution comes before allocation.
- Common credit must follow the prescribed Rule 39 methodology.
- Tax-head distribution matters.
- Historical periods must be tested under the law applicable to those periods.
- GSTR-6 should be reconciled with source invoices and recipient ITC.
- A strong ISD system creates a source-invoice → allocation → ISD document → GSTR-6 → recipient trail.
Disclaimer: This guide is for practical educational and working purposes. GST Acts, Rules, notifications and procedural requirements can change. For historical transactions, apply the law and procedures applicable to the relevant period.