Input service distributor positive boost to GST — a compliance checklist on ISD registration, ITC distribution rules across CGST, SGST, IGST, and form filings.
A multi-location business with units across several states typically routes shared input services — corporate marketing, professional consultancy, IT support, audit, common procurement — through its head office or a central administrative unit. The tax invoices for these common services carry the head office GSTIN, but the actual consumption of the service sits across several branch units that have their own GST registrations. Left as is, the input tax credit on these common services accumulates at the head office while the branches that actually use the service have no way to claim it against their own output tax liability. The Input Service Distributor mechanism under GST resolves this by allowing the head office to receive the invoice, register separately as an ISD, and distribute the credit to the eligible branches in a defined manner.
The Input Service Distributor as a positive boost to GST sits in this specific operational reality — common input services consumed across multiple registered units within the same PAN should not produce stranded input tax credit at the head office. The mechanism is conceptually clean but procedurally exacting: separate ISD registration is mandatory, the distribution rules differ between intra-state and inter-state allocation, and the dedicated return form (GSTR-6) carries its own filing cadence. Missing any of these pieces produces GST filing errors and input tax credit mismatches at both the ISD and recipient end. The broader ERP subject area discussion for compliance-led businesses treats the ISD framework as one of the more under-utilised credit hygiene practices in operations with significant common-service spend.
When and why to use this ISD checklist
This compliance checklist applies to operations that have a head office, regional office, depot, or central administrative unit receiving tax invoices for common input services consumed across multiple registered units under the same PAN. Each item below names a specific statutory requirement along with the documentary or filing step that supports it. The work runs each month — at the receipt of the common-service invoice, at the distribution to the recipient units, and at the filing of GSTR-6 by the 13th of the following month. The accountant maintains the ISD register; the finance head signs off the monthly distribution before submission. Distribution ERP software that holds the multi-GSTIN configuration supports the ISD discipline by carrying the recipient mapping and the distribution proportions as configured masters rather than as monthly manual computations.
The compliance checklist for ISD setup, distribution, and filing
The items below are grouped under three stages — qualifying as an ISD and obtaining the dedicated registration, applying the distribution rules across intra-state and inter-state recipient units, and meeting the monthly return filing obligations.
Qualifying and registering as an Input Service Distributor
Confirm the ISD qualification — common input services received for distribution to multiple units.
The ISD is the office of the supplier of goods or services (typically the head office, central corporate office, regional office, administrative office, or depot) that receives input services under cover of a tax invoice and is allowed to distribute that input tax credit to units of the supplier registered under the same PAN. The qualification turns on the office receiving the invoice for common services consumed by multiple registered units. A unit consuming all of its input services itself, with no distribution to other branches, would not need ISD registration. The finance head confirms the qualification against the entity's actual common-service receipts.
Apply for separate ISD registration — there is no threshold limit.
ISD registration is mandatory and separate from the regular GST registration of the same entity. There is no threshold limit for ISD registration — once the qualification applies, registration follows regardless of turnover. The application is filed through the GST portal in the form prescribed for ISD registrations, with details of the recipient units across the same PAN. The accountant captures each recipient GSTIN against the ISD registration to ensure the distribution mapping is complete at the time of registration.
Re-register afresh — legacy ISD registrations do not carry over.
Operations that were registered as an ISD under the erstwhile CENVAT Rules in the previous tax regime cannot carry that registration forward into GST. A fresh ISD registration under GST is mandatory; the earlier registration does not migrate automatically. The finance head signs off the fresh ISD registration before any common-service invoice is booked at the ISD office under GST.
Applying the distribution rules
Identify the common input services received against each ISD invoice.
At the point of receiving the tax invoice for a common service, the accountant identifies which recipient unit (or units) actually consumed the service and the proportion of consumption. Where the service is consumed by a single specific unit, the credit is distributed in full to that unit. Where the service is consumed by multiple units, the distribution is made in the proportion of turnover of each recipient unit during the relevant period under the prescribed rules. The finance head signs off the consumption identification before distribution.
Apply the intra-state distribution rule — same-state recipient units.
Where the ISD and the recipient unit are located in the same state or union territory, the distribution preserves the original tax head — CGST is distributed as CGST, SGST is distributed as SGST, UTGST is distributed as UTGST, and IGST is distributed as IGST. For a Mumbai-based ISD distributing credit to a Pune-based recipient against an invoice carrying ₹45,000 CGST and ₹45,000 SGST, the recipient receives ₹45,000 as CGST credit and ₹45,000 as SGST credit. The accountant records the distribution against the recipient GSTIN.
Apply the inter-state distribution rule — different-state recipient units.
Where the ISD and the recipient unit are located in different states or union territories, the distribution converts the original tax heads into IGST in the hands of the recipient. CGST, SGST, UTGST, and IGST in the original ISD invoice are all distributed as IGST to the inter-state recipient. For the same Mumbai-based ISD distributing to a Bangalore-based recipient against an invoice carrying ₹45,000 CGST and ₹45,000 SGST, the recipient receives ₹90,000 as IGST credit (cumulative of the CGST and SGST in the original invoice). The accountant records the head-conversion in the distribution register.
Issue the ISD invoice or challan to the recipient unit.
The distribution of credit is effected through an ISD invoice or challan issued by the ISD to each recipient unit. The invoice or challan carries the ISD GSTIN, the recipient GSTIN, the reference to the original supplier invoice, the credit amounts being distributed under each head (CGST, SGST/UTGST, or IGST as applicable after the inter-state conversion rule), and the period to which the distribution relates. The recipient unit takes the credit into its electronic credit ledger based on this ISD invoice.
Restrict distribution to recipients who have actually used the service.
Credit distribution can only be made to recipient units that have actually used the input service. Distributing credit to a unit that did not consume the service is non-compliant and the credit becomes ineligible at the recipient end. Where a common service is used by some but not all units under the same PAN, distribution is restricted to the using units in the relevant proportion. The accountant maintains a record of the consumption mapping; the finance head signs off where the mapping involves multiple recipient units.
Meeting the filing obligations
Reconcile the auto-drafted ISD inward supply details — Form GSTR-6A.
Form GSTR-6A is the auto-drafted statement of inward supplies available to the ISD, generated from the GSTR-1 filings by the suppliers and made available by the 11th of the following month. The accountant reviews GSTR-6A against the internal record of common-service invoices received during the period. Mismatches between GSTR-6A and the internal record signal supplier-side filing gaps or invoice booking errors and are flagged for investigation before the GSTR-6 is filed.
File Form GSTR-6 by the 13th of the following month.
Form GSTR-6 is the monthly return filed by an ISD containing details of input tax credit received and distributed to recipient units. The form is filed by the 13th of the month following the relevant period. The return captures the ISD invoices issued during the period, the recipient unit GSTINs, the credit amounts distributed under each head, and the reconciliation against GSTR-6A. The finance head signs off the GSTR-6 draft before submission; delay in filing triggers late filing fees and may delay the recipient units' credit availability.
Reconcile the distributed credit at the recipient unit's electronic credit ledger.
The credit distributed through GSTR-6 flows to the recipient unit's electronic credit ledger and becomes available for utilisation in the recipient unit's GSTR-3B set-off. The accountant at each recipient unit reconciles the credit flowing in against the ISD invoices and against the recipient unit's own GSTR-2B. Mismatches typically trace back to ISD distribution errors or to recipient mapping issues; they are escalated to the ISD office for correction in the subsequent period. Where deeper period-over-period reporting matters, BI for ERP reporting holds the multi-period view of ISD distributions against recipient consumption.
Maintain the ISD audit trail for annual reconciliation and statutory audit.
The ISD audit trail — original supplier invoice, consumption identification at the ISD, distribution computation, ISD invoice or challan issued, GSTR-6 filing, recipient unit credit posting — is maintained as a consolidated register at the ISD office. The annual reconciliation under GSTR-9 and the statutory audit each draw from this register. The finance head reviews the register monthly to flag persistent gaps before they compound into annual reconciliation issues. Where statutory payroll also forms part of the operational picture across multiple registered units, HRMS for payroll and HR integration maintains the same kind of audit trail discipline across unit-level statutory deductions.
Facing similar operational challenges?
See how exactllyERP manages inventory management, financial operations, and operational reporting — built for operational businesses.
See how exactllyERP handles operational complexity →How exactllyERP handles this automatically
The ISD mechanism is operationally compact but procedurally exacting because each step depends on clean configuration — the ISD GSTIN, the recipient GSTIN list under the same PAN, the consumption mapping per common service, the distribution proportion logic, and the GSTR-6A reconciliation against the supplier filings. exactllyERP eliminates GST filing errors and input tax credit mismatches by carrying each of these as configured masters and pulling the ISD distribution computation from the same transaction layer that holds the supplier invoice booking. The ISD invoice or challan issued to each recipient unit, the GSTR-6 draft for monthly filing, and the audit trail per common service all flow from one configured source.
How exactllyERP handles this automatically: items 5 (intra-state distribution preserving original heads), 6 (inter-state distribution converting heads to IGST), and 10 (Form GSTR-6 draft preparation by the 13th of the following month) are the three places where ISD distribution errors most commonly surface — and exactllyERP carries the recipient GSTIN-by-state mapping and the head-conversion logic as configured rules rather than as monthly manual computations. The GSTR-6A reconciliation against the internal common-service invoice register runs as a configured monthly process. Supplier-side filing gaps surface as flagged exceptions before the GSTR-6 is filed, with vendor follow-up triggered against the supplier's GSTIN. exactllyERP handles incorrect GSTR filing and HSN code mapping errors automatically through statutory updates absorbed inside the standard release cycle. See it live in a free demo against your ISD registration data and a sample previous-month common-service invoice register.
