Introduction
If a head office buys a common service and passes the credit on to its branches through an Input Service Distributor (ISD), who has to prove that the credit is eligible? According to the CBIC, the answer is the branch that receives the credit, not the ISD.
ISD distribution should not be confused with cross-charge, because the two cover different situations. In ISD distribution, the third-party supplier actually renders the service to one or more branches, and the head office only receives the invoice for them or on their behalf. The credit belongs to the branches, and the ISD simply passes it on. In a cross-charge, the head office receives the inputs or input services itself and uses them to provide its own services, such as management, accounting or IT support, to the branches. That is a supply between distinct persons under section 25(4) read with Schedule I, paragraph 2, valued under rule 28. Since 1 April 2025, credit on third-party services attributable to branches must be routed through an ISD.
This question matters more today than it did a couple of years ago. Since 1 April 2025, the ISD route is no longer optional. The Finance Act, 2024 amended section 2(61) and section 20 of the CGST Act, and those amendments came into force on 1 April 2025 through Notification No. 16/2024-Central Tax dated 6 August 2024.
Once the system became compulsory, practical questions followed. Trade and industry asked the Board several of them, and the Board has answered them in Circular No. 260/06/2026-GST dated 26 October 2026, issued under section 168(1) of the CGST Act. This article explains what the Circular says, what it means for businesses, and how the position compares with the old Service Tax regime.
What the Circular clarifies;
The Circular answers seven questions. In brief:
| # | Question raised | Board's answer |
| 1 | Is a separate ISD registration needed for each business vertical or place of business in the same State? | Yes. Every registrant that receives input service invoices on behalf of distinct persons needs its own ISD registration. Credit goes only to the distinct person it is attributable to (rule 39(1)). |
| 2 | Who must meet the section 16 conditions, the ISD or the recipient? | The recipient. The ISD only distributes the credit under section 20. |
| 3 | What does "credit available for distribution in a month" mean? | Credit becomes available when the ISD has checked that it is prima facie eligible. It is distributed in that month, with eligible and ineligible credit shown separately (rule 39(1)(g)). |
| 4 | The recipient, under rules 38, 42 and 43. The ISD distributes the full amount. | |
| 5 | Is an invoice raised under rule 54(1A) part of "turnover in State"? | No. It is only a way of transferring credit, so it does not count as turnover for ISD distribution or for refunds. |
| 6 | Is credit transferred under rule 54(1A) part of "Net ITC" for refunds? | No. It is not the transferring unit's own credit. |
| 7 | Does the unit that transfers credit under rule 54(1A) reverse under section 17? | No. It passes on the full credit, and the final recipients reverse. |
The second answer is the one that changes the most in practice, so the rest of this article concentrates on it.
The core shift: the recipient carries the burden
The Circular states plainly that the recipients of credit must comply with the eligibility conditions, including those in sections 16 and 17 of the CGST Act and the related rules. This is consistent with section 155, which puts the burden of proving eligibility for credit on the person who claims it.
The practical difficulty is that the recipient never deals with the supplier. The paperwork travels along a chain:
- The supplier raises its invoice on the ISD and reports it in GSTR-1.
- The invoice appears in the ISD's GSTR-6A.
- The ISD issues its own ISD invoice under rule 54(1) and reports the distribution in GSTR-6.
- The recipient sees the ISD invoice in its GSTR-2B and avails the credit.
So the recipient is responsible for conditions that depend partly on people it has never dealt with. The table below shows how each condition works in this chain.
| Condition | What the law requires | What it means for the recipient |
| Section 16(2)(a): tax invoice | A valid document under rule 36(1) | The ISD invoice is a valid document (rule 36(1)(d)). Still, keep a copy of the supplier's original invoice to support your claim. |
| Section 16(2)(aa): reflected in returns | Supplier's GSTR-1 flowing through to the recipient | Check your GSTR-2B. You cannot see the ISD's GSTR-6A, so ask the ISD for it. |
| Section 16(2)(b): services received | Actual receipt, including services received on your direction and on your account | Be able to show that the service was actually used by your unit. |
| Section 16(2)(c): tax paid to Government | Supplier has paid the tax | You cannot see the supplier's GSTR-3B. You depend on the ISD. This is the weakest link. |
| Section 16(2)(d): own return filed | Your GSTR-3B filed | Fully in your control. |
| Second proviso to section 16(2) and rule 37: payment within 180 days | Value plus tax paid to the supplier | Payment is usually made by the head office. Get confirmation; if payment is not made, reverse your share with interest. |
| Section 16(4): time limit | Credit taken by 30 November of the next year, or the annual return date if earlier | You can claim only after the ISD distributes, so delays at the ISD eat into your time. |
| Section 17(5): blocked credits | Depends on how the service is used | The ISD's eligible/ineligible tag is only a first screen. Test it against your own use. |
| Sections 17(1), 17(2), 17(4): reversals | You compute and make these reversals yourself. |
One invoice, many recipients
A typical case is one audit fee or software subscription that serves several branches. Under rule 39(1)(d) and (e), the ISD splits that credit among the branches in proportion to their turnover in the relevant period.
Does each branch then have to meet sections 16 and 17 for its share? Yes. Each registration is a separate "distinct person" under section 25. Each branch takes the credit into its own electronic credit ledger and files its own return. The Circular makes no exception for shared invoices.
It helps to sort the conditions into two groups:
| Type | Conditions | What happens if one fails |
| Invoice-level | Supplier reports the invoice, supplier pays the tax, payment within 180 days, genuineness of the supply | Every branch loses credit in proportion to its share. |
| Recipient-level | Use for business, own return filed, time limit, section 17 reversals, blocked credits that depend on use | Only the branch concerned is affected. |
A simple example
The head office receives an invoice for Rs. 10,00,000 plus IGST at 18% (Rs. 1,80,000), a total of Rs. 11,80,000. The credit is shared by three branches. Only Rs. 7,08,000 is paid to the supplier within 180 days, so Rs. 4,72,000 (40% of the invoice) remains unpaid.
| Branch | Turnover in relevant period (Rs. ) | Share | Credit received (Rs. ) | Reversal at 40% (Rs. ) |
| A | 50,00,000 | 50% | 90,000 | 36,000 |
| B | 30,00,000 | 30% | 54,000 | 21,600 |
| C | 20,00,000 | 20% | 36,000 | 14,400 |
| Total | 1,00,00,000 | 100% | 1,80,000 | 72,000 |
All three branches reverse their share even though the payment was the head office's responsibility, and each also owes interest under section 50 from the date it took the credit.
How a recipient can protect itself
The GST portal does not let a recipient check the supplier's side of an ISD transaction. Protection therefore has to come from internal arrangements between the ISD and its branches. A practical checklist:
- Put the ISD process in writing. An internal policy should set out timelines, the basis of attribution, and the ISD's duty to share data with branches.
- Get a monthly pack from the ISD. For each ISD invoice, the pack should contain a copy of the supplier's invoice, the GSTR-6A extract and the turnover working used for the split.
- Track whether suppliers have filed their returns. The ISD should check each supplier's GSTR-3B filing status and confirm it to the branches.
- Track the 180-day payments. The head office should confirm each month which invoices have been paid, with payment references.
- Reconcile GSTR-2B every month. Match the ISD credit in GSTR-2B with the books before availing it.
- Run your own blocked-credit check. Do not rely only on the ISD's eligible/ineligible tag; test section 17(5) against how your unit uses the service.
- Compute your own reversals. Rule 42 and 43 workings for exempt or non-business use belong at branch level.
- Watch the time limit. Keep an ageing report of ISD distributions against the section 16(4) deadline.
- Keep evidence of use. Contracts, deliverables and cost-allocation records show the service was actually received.
- Preserve records for the period required by sections 35 and 36 and rule 56.
Open issues to watch
The Circular settles who is responsible. It does not resolve every practical question.
- A tension in the reasoning. The Circular itself says the ISD is 'best placed' to judge eligibility, because it receives the invoices. Yet it puts the liability on the recipient.
- Binding effect. A circular under section 168 binds departmental officers. It does not bind the taxpayer or the courts where it goes beyond the statute; see COMMISSIONER OF CENTRAL EXCISE, BOLPUR Versus M/s RATAN MELTING & WIRE INDUSTRIES - 2008 (10) TMI 5 - Supreme Court.
- Rule 37A. The rule is designed around a supplier invoice that the recipient sees in GSTR-2B. How it applies when the credit comes through an ISD is not spelt out.
- Which invoice starts the clock under section 16(4)? The law does not say whether it is the ISD invoice or the supplier's invoice. If the ISD takes time to "ascertain" eligibility, recipients may face a time-bar risk.
- Section 21 is narrow. It covers only excess distribution in breach of section 20. A recipient's own failure under section 16 or 17 will be pursued directly against the recipient under sections 73, 74 or 74A.
Conclusion
The message of the Circular is simple. The ISD distributes the credit, and the branch that receives it must stand behind it. Where one invoice is shared, every branch answers for its own share. A failure on the supplier's side hits all of them, while a failure in how a branch uses the service hits only that branch. Multi-location businesses should now treat the ISD as more than a back-office function. Clear internal rules, regular data sharing and branch-level checks are the best protection against demands, interest and penalties.
-------
By: CA. Chitresh Gupta
TaxTMI