A group-company decision framework separating third-party common input-service distribution from internally generated services between distinct GST registrations.
ISD distributes third-party input-service credit. Cross charge taxes an internal supply between distinct persons. Using one mechanism for both creates either duplication or missing tax.
Separate GST registrations of the same legal entity are distinct persons under the Act.
Cross charge concerns an actual supply made by one registration to another, including certain internally generated support services.
The ISD mechanism distributes credit of qualifying input services received by one office for or on behalf of distinct persons.
From 1 April 2025, the amended ISD framework applies mandatorily to its covered common input-service scope.
| Check | What to examine |
|---|---|
| Cost source | External vendor service or internal employee/asset activity. |
| Benefit | One GSTIN, several GSTINs or entity-wide. |
| Mechanism | Direct vendor invoice, ISD distribution or cross-charge invoice. |
| Value | Actual cost, allocation key and rule 28 implications. |
| Credit | Recipient eligibility and blocked/exempt usage. |
Head office receives a single group audit invoice and also employs a central finance team serving all States. The audit invoice belongs in the common third-party service/ISD analysis; the employee-driven support belongs in the cross-charge supply analysis. One combined debit note cannot safely perform both jobs.
Create a central-cost taxonomy before posting. Route third-party common input services to ISD; identify direct services for direct billing; analyse internally generated branch support for cross charge.
Prevent double taxation by reconciling vendor value, distributed credit and internal service value. A markup or allocation key should be supported by the valuation framework and facts.
Identify the GSTIN, tax period, transaction, document and exact statutory question. Review cost source, benefit and mechanism together. Freeze the source data so that later ERP edits do not destroy the evidence used for the decision.
Start with the contract or commercial event. Move through the invoice, receipt or movement evidence, e-invoice or e-way bill, accounting entry, return and electronic ledger. Classify each difference as timing, error, ineligible amount, statutory exception, disputed position or completed correction. Avoid a plug entry whose only purpose is to make two reports equal.
Prepare a concise position note with facts, authority, amount, alternative view and approval. Preserve the filing acknowledgement and update the responsible master data, vendor rule, invoice workflow or monthly checklist. The objective is not only to survive one review but to prevent the same issue in the next period.
GST positions are strongest when the transaction, legal provision, invoice, physical or service evidence, books, return and electronic ledger agree. A portal match without commercial evidence is not a complete control.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.