ISD stopped being optional on 1 April 2025. Here's what SAP's own KBAs say about the config
From 1 April 2025, ISD registration became mandatory under Section 20 of the CGST Act for distributing ITC on common input services billed to a head office on behalf of other GSTINs — the earlier option to cross-charge that specific credit instead is gone. Credit only becomes due for distribution once the ISD, on receiving the GSTR-6A entry, treats it as prima facie eligible — not merely on receipt. In SAP ERP or S/4HANA, this runs through transaction J1IG_ISDN, configured per the steps SAP's public KBAs document (in full for S/4HANA Cloud Public Edition, KBA 3553657) — business-place mapping and turnover maintenance among them — completed before that credit is due for GSTR-6 distribution, by the 13th of the following month.
If your head office still books common-service invoices — audit, group software, a national ad campaign — and claims the credit there, or cross-charges it to branches, that stopped being a compliant option for third-party-procured services on 1 April 2025. Section 20 of the CGST Act now requires that credit to move through an Input Service Distributor registration instead. In SAP, that's a configuration project with a hard deadline attached to it, not a settings toggle.
What changed on 1 April 2025, and what didn't
Section 20 of the CGST Act was substituted in full by the Finance Act 2024 (Act 8 of 2024), s.12, and commenced on 1 April 2025 by Notification 16/2024-Central Tax dated 6 August 2024 — an Act made the change; the notification only fixed the date it took effect. The substituted section is self-executing: an office that receives third-party tax invoices for input services "for or on behalf of" its distinct persons under Section 25 shall register as an ISD and shall distribute that credit. It fixes no threshold or figure and delegates no number to the Council — Section 20(2) delegates the manner, time, restrictions and conditions of distribution to the Rules, and Section 20(3) separately delegates the manner of the distribution document, but there's no configurable number to watch for here the way there is elsewhere on this site.
Three limits matter before you assume this touches you at all. First, it bites only where invoices are addressed to a head office or branch on behalf of other GSTINs under the same PAN — a single-registration business, or one whose branches are invoiced directly by the vendor, has nothing to distribute. Second, it covers input services only: ITC on goods and capital goods cannot be routed through ISD at all, mandatorily or otherwise. Third, the mandate displaces cross-charge only for third-party-procured common input services. It does not touch internally generated services — head-office management time or employee cost cross-charged to branches remains governed by Rule 28(1) valuation (Circular 199/11/2023-GST, Issue 2, scoped to branches eligible for full ITC), which has never been withdrawn (as of 11 November 2026). Cross-charge is not abolished; it has a narrower lane than before. (Circular 260/06/2026-GST S.No.1 adds that where a business holds separate registrations for verticals or places of business within a State, each such registrant that itself receives input-service invoices for or on behalf of distinct persons must obtain its own ISD registration — there is no bar on more than one ISD registration in a State.)
What SAP's own public KBAs say you need to do
SAP's knowledge base article on this change (KBA 3573453, "GST IN: Changes in ISD solution applicable from 1 April, 2025 — SAP ERP & SAP S/4HANA") states plainly that the ISD mechanism "will be mandatory" from that date for distributing ITC on common input services, and ties it to two legal changes — the amended ISD definition in Section 2(61) and the distribution rules in Section 20. Its stated environment is SAP ERP, SAP S/4HANA On-premise, and SAP S/4HANA Cloud Private Edition — it does not cover S/4HANA Cloud Public Edition; that product has its own counterpart KBA (below). The KBA's business guidance is two concrete actions: identify which procured services have to move through ISD and in which States you therefore need an ISD registration, and tell vendors in time so invoices for shared services get issued to the ISD GSTIN. A FAQ covering all editions (KBA 3585077) and a note on reverse-charge handling specifically (KBA 3586380) restate the same two actions. (As of 11 November 2026 — SAP's KBAs are retunable without notice, like any vendor knowledge base.)
The authoritative configuration detail sits in SAP's own knowledge base and Help Portal. Three of the KBAs cited below — 3553657, 3554523 and 3578355, all S/4HANA Cloud Public Edition — are published in full; the others (2536753, 3526869, 3573453, 3585077, 3586380) show only a public preview, with the full resolution behind an SAP for Me login. What's quoted here is only what SAP shows publicly.
The SAP mechanics: transaction J1IG_ISDN
SAP's own knowledge base treats J1IG_ISDN as the ISD distribution transaction, not a function group. KBA 2536753 (SAP ERP and S/4HANA) reports an error "thrown in transaction J1IG_ISDN", and KBA 3526869 is titled "…error in J1IG_ISDN tcode". In S/4HANA Cloud Public Edition the same identifier is the app "Re-distribute and Create ISD Invoices" (KBA 3553657, KBA 3554523). No public SAP preview states whether it replaced an older J1IG_ISD transaction, so confirm against your own system's transaction list before planning around either (as of 11 November 2026).
What SAP's public KBAs actually document, rather than a practitioner blog's step-by-step: KBA 3553657 (S/4HANA Cloud Public Edition) states the original posting must carry the ISD business place — "Ensure that ISD Business place is entered while posting original document i.e. MIRO/FB60" — and that FB65 credit memos additionally need "Invoice Reference and Fiscal Year fields in the Payment tab" filled in. The same KBA adds a note on turnover maintenance (SSCUI 101912): "Even though if you follow April–March(V3) financial year, this functionality is built based on the Year." Whatever year key SAP uses, the figure you maintain has to be each recipient's turnover for Rule 39's relevant period — ordinarily the preceding April–March financial year (Rule 39 Explanation (i)) — so check which year value your system reads before trusting the ratios. The KBA also names the Customizing views as SSCUIs: 101911 (map the ISD business place to receiving business places), 101912 (maintain turnover for receiving business places), 101927 (map tax G/L accounts to receiving business places), and 101934 (classify the GST condition types against tax procedure 0TXIN). KBA 3554523 separately documents a missing-configuration error in the same app, resolved by maintaining a dummy tax code in SSCUI 101927 and ensuring the FTXP tax code in SSCUI 101016 carries a 0% rate for conditions JIIG, JICG and JISG.
None of this is a worked example SAP publishes, but Rule 39(1) gives the mechanic worth sanity-checking your SAP turnover maintenance against. Credit is distributed pro rata on the relevant-period turnover of only the recipients to which the input service is attributable and which are operational in the current year (clauses (d)–(e)), by the clause (f) formula C1 = (t1 ÷ T) × C. Clause (f) counts in T every such recipient, "including the recipients who are engaged in making exempt supply, or are otherwise not registered for any reason". Say an audit fee of ₹1,00,000 plus IGST of ₹18,000 is attributable to three registered branches with relevant-period turnovers of ₹6 crore, ₹3 crore and ₹1 crore, the third making mostly exempt supplies. The ₹18,000 goes out as ₹10,800, ₹5,400 and ₹1,800, shown here as IGST to each — clause (i), as amended by Notification 05/2026-Central Tax from 1 November 2026, distributes IGST credit "as input tax credit of integrated tax or central tax". The third branch is not dropped: Circular 260/06/2026-GST S.No.4(b) says the ISD "should distribute the entire input tax credit available to it for distribution" to the recipients to which it is attributable, and that any Section 17(2) reversal under Rules 42/43 is made by those recipients, not by the ISD. Leave that branch out of SAP's turnover table and the other two receive ₹12,000 and ₹6,000 — excess distribution, recoverable from them under Section 21 (Circular 260 S.No.2(b)). Credit that is itself ineligible — blocked under Section 17(5) or otherwise — goes out on its own line under clause (g), never netted into the eligible line. Getting SAP's turnover-maintenance views and that eligible/ineligible split right for every invoice is the configuration work that sits behind this rule.
Where configuration stops and GSTR-6 starts
Getting the Customizing right doesn't finish the job — Rule 39 attaches a timing rule to it that configuration alone can't satisfy. Rule 39(1) was substituted, and sub-rule (1A) and an Explanation inserted, by Notification 12/2024-Central Tax dated 10 July 2024 — commenced separately, on the same 1 April 2025 date, by Notification 09/2025-Central Tax dated 11 February 2025: credit available for distribution in a month must be distributed in that same month, through FORM GSTR-6, due by the 13th of the following month. "Available for distribution" has its own trigger: per CBIC Circular 260/06/2026-GST S.No.3 (26 October 2026), credit becomes available only once the ISD, on receiving the GSTR-6A entry, ascertains it to be prima facie eligible — not merely in the month of receipt. Distribution runs pro rata on the aggregate turnover of the relevant period — ordinarily the preceding financial year, or the last quarter for which all recipients' turnover figures are available if any recipient had none in the preceding FY (Rule 39 Explanation (i)) — of only the recipients to which the service is attributable and which are operational in the current year (Rule 39(1)(d)–(f)). Eligible and ineligible (Section 17(5) or otherwise, per Rule 39(1)(g)) credit must be distributed separately, not netted together.
This is where it bites in practice. If a head office's purchase register still books a common-service invoice and claims the credit directly instead of routing it through the now-mandatory ISD step, that is taking credit in contravention of Section 20 — Section 20 "shall distribute" leaves no alternative for third-party-procured common services — and attracts penalty under Section 122(1)(ix) (restated at Circular 260 S.No.2(c)); demands for periods from April 2025 run under Section 74A, not Sections 73/74. The branch GSTIN that was supposed to receive its share doesn't get a silent correction later; it simply sees nothing from the ISD GSTIN in its own GSTR-2B for that period, because GSTR-2B is built in part from GSTR-6 filings (Rule 60(7)). A missing ISD distribution looks, from the branch's side, exactly like a vendor who hasn't filed — except the branch finance team has no vendor to chase; the fix sits inside their own group's SAP configuration.
The reconciliation this SAP gap forces by hand
Confirming the two sides actually agree — that what the ISD business place distributed in SAP, invoice by invoice, equals what each receiving GSTIN's own GSTR-2B shows as ISD-sourced credit for that period — is painful to do manually once you're running this across more than one or two branches. It means pulling the GSTR-6 filing, matching every distributed line against the originating invoice and the turnover ratio that produced it, and then separately checking each receiving GSTIN's 2B to confirm the credit actually landed where SAP said it should — every month, against a due date that doesn't move.
How Recoup fits
Recoup doesn't configure ISD in SAP and doesn't file GSTR-6 — that configuration and that filing stay inside SAP and whoever owns your India localization. What Recoup reconciles is the result on the receiving side: it matches your books against IMS and GSTR-2B for every GSTIN, invoice by invoice — and because ISD credit reaches each recipient's GSTR-2B from GSTR-6 (Rule 60(7)), credit your books expect from the ISD but a branch's 2B doesn't show surfaces as a gap, the same way an unfiled vendor invoice would.
An ISD distribution that didn't land is invisible until someone checks every branch's 2B
Recoup reconciles each GSTIN's books against its own GSTR-2B — where ISD credit distributed through GSTR-6 appears — so a distribution that never landed shows up before that branch files its GSTR-3B, not at annual return or audit.
Book a demo →Related guides
GSTR-2B reconciliation in SAP
What SAP's own documentation says is automated on the inward side, and what still needs a person.
Setting up e-invoicing (IRN) in SAP
The adjacent SAP India-localization configuration project, and the certificate step most implementations skip.
GST reconciliation: the 2026 guide for finance teams
Why your credit is what your GSTR-2B contains, not what your books say — and the four reconciliations that decide it.
Input Service Distributor (ISD)
What an ISD registration is, and why credit received centrally but not fully passed on is a common audit finding.