ISD and cross charge solve different problems. Using one invoice type for every head-office cost can distort tax and credit.
Classify each shared cost by who supplied it, who received it and whether the head office itself provided a service.
Map all common services.
Vendor invoices.
Calling every cost cross charge.
From 1 April 2025, the amended ISD framework applies to common input-service invoices received by one office for or on behalf of distinct persons, subject to the statutory design.
Cross charge concerns taxable supplies by one distinct person to another, including internally generated services where applicable.
Allocation should reflect recipient use and prescribed distribution rules, not a year-end plug.
| Area | What to establish | Operating rule |
|---|---|---|
| Source | Third-party invoice or internal activity. | Choose mechanism. |
| Recipient | Which GSTIN used the service. | Document benefit. |
| Value | ISD distribution or cross-charge valuation. | Use lawful basis. |
| Timing | Monthly distribution and invoicing. | Avoid annual backlog. |
GST control should connect five records: commercial contract, tax invoice, movement or service evidence, accounting entry and portal return. A filing that cannot be traced back to all five records is difficult to defend.
Every reconciliation should have a clear opening balance, current-period additions, corrections, reversals, payments and closing balance. Avoid unexplained plugs that make the total match but do not identify the invoice or legal reason.
Portal data is important but not conclusive by itself. GSTR-2B, e-invoice, e-way bill and ledger data should be read with the statute, rules, notifications, contracts and actual supply evidence.
Keep original source files and final filed versions. Screenshots help explain a portal event but should not replace downloaded returns, JSON, signed invoices, acknowledgements or bank records.
For material exposure, prepare a written position memo stating facts, issue, law, alternatives, conclusion, amount and approval. The memo should record uncertainty rather than hide it.
Expense-side GST controls should scan vendor master, general ledger and foreign payments before return filing. These liabilities may never appear in outward-supply systems.
Allocation across GST registrations should be supported by recipient use, legal mechanism, valuation and consistent accounting.
Start with the GST portal record, responsible business owner and tax working. Where the issue is operational, correct the source system and retain the acknowledgement. Where it is legal or disputed, obtain a reasoned professional position before payment, reply, refund or appeal.
Track the statutory or portal deadline separately from internal approval. Preserve helpdesk tickets, ARN, hearing requests, orders and payment records so a later reviewer can reproduce the entire path.
Before filing or replying, prepare a one-page issue sheet showing GSTIN, tax period, transaction type, amount, applicable provision, portal form, evidence owner and due date. This prevents different teams from solving different versions of the same problem.
Reconcile tax by CGST, SGST, IGST and cess rather than only by total. A total can match even when the wrong tax head, state or period has been used, which can still create interest, cash-flow and customer-credit consequences.
Build an exception register with five statuses: identified, evidence pending, vendor or customer action, tax treatment approved and closed. Every exception should retain its original amount even after correction so the audit trail remains visible.
Test the position against the counterparty’s records. Customer ITC, vendor GSTR-1, transporter data, marketplace statements and bank receipts can expose differences that are invisible in the taxpayer’s own ledger.
The final approval should record who reviewed the legal position and who approved the return, reply, payment, refund or appeal. Material GST decisions should not remain buried in informal email chains.
Create a recurring expense-code scan for legal fees, director services, freight, security, import services and other notified categories. Update the matrix whenever a notification or business model changes.
For group allocations, document the recipient GSTIN, benefit received, allocation basis and invoice or ISD document before credit is distributed.