GCC-to-GBS Conversion: The Compliance Debt Nobody Prices In

August 7, 2026

Every GCC-to-GBS pitch deck looks the same. A slide showing the captive centre’s cost curve flattening out, followed by a slide showing the GBS entity’s revenue curve climbing up and to the right. Somewhere between those two slides, a whole category of risk gets waved away with a bullet point that says, “transfer pricing and tax structuring to be finalised.”

That bullet point is where the real work and the real exposure lives.

Converting a Global Capability Centre from a captive cost centre into a Global Business Services entity that sells services externally, cross-charges at scale, or takes on outcome-based contracts isn’t an org-chart change. It’s a change in the legal and economic character of the entity, and every tax authority that touches it will treat it that way. The compliance debt this creates rarely shows up in year one. It shows up in year three or four, as an audit notice, a TP adjustment, or a PE assessment in a jurisdiction the parent didn’t think it was exposed in.

Why the shift matters more than it looks like it does

A captive GCC is structurally simple from a tax perspective. It performs services for its parent or group affiliates, gets reimbursed on a cost-plus basis, and its transfer pricing position is built around a low-risk, limited-function characterisation a routine service provider bearing minimal entrepreneurial risk. Revenue authorities generally accept this at modest margins because the fact pattern is clean: one type of counterparty, one pricing model, one risk profile.

A GBS entity breaks that fact pattern deliberately. It exists to serve multiple business units, external clients, or both; to price on value rather than cost-plus; to hold P&L accountability; and often to make decisions pursuing new mandates, negotiating SLAs, owning delivery risk that a captive was never designed to make. That’s the point of the conversion. But every one of those capabilities is also a fact that a tax examiner will use to argue the entity’s functional profile has changed, and that its transfer pricing and tax treatment should change with it.

The three areas where this bites hardest are permanent establishment risk, GST on export of services, and transfer pricing posture. They’re related, but each has its own failure mode.

Permanent establishment risk: when capability becomes exposure

PE risk is usually framed as something that happens to the parent the foreign entity gets deemed to have a taxable presence in India because of what the GCC-turned-GBS entity does on its behalf. That framing is correct, and it’s the one most legal team already have on their checklist. What gets missed is how directly the GBS conversion itself creates the fact pattern that triggers it.

A few specific triggers worth naming:

Dependent Agent PE: If GBS staff in India start negotiating terms, closing deals, or habitually concluding contracts on behalf of overseas group entities even informally, even as part of “supporting” a sales process that can constitute a Dependent Agent PE for the counterparty entity, regardless of what the intercompany agreement says on paper.
Fixed Place PE: As the GBS entity takes on decision rights (vendor selection, service design, pricing authorship) rather than just execution, the argument that the Indian entity is merely providing “auxiliary or preparatory” services the traditional shield against Fixed Place PE gets harder to sustain.
Service PE: Many tax treaties (India’s DTAAs with the US, UK, and several others) contain service PE clauses triggered by employees of one entity providing services in another jurisdiction beyond a threshold number of days. A GBS model that rotates delivery leads or subject-matter experts to client sites, or seconds of staff to group entities abroad, can trip this without anyone noticing until the day-count is reviewed years later.

The debt accumulates because PE analysis is rarely a one-time exercise for a GCC, but becomes a continuous, multi-jurisdiction exercise for a GBS entity serving several group companies across geographies. A model built for one parent-subsidiary relationship needs to be re-run for every jurisdiction the GBS entity now touches and most conversions don’t budget for that recurring cost.

GST on export of services: the paperwork is the exposure

For a captive GCC, GST treatment is usually settled: services to the foreign parent qualify as “export of services” under Section 2(6) of the IGST Act, are zero-rated, and the entity either exports under a Letter of Undertaking (LUT) without payment of tax or claims a refund of accumulated input tax credit. It’s mechanical once set up correctly.

The GBS conversion disturbs this in three specific ways:

1. “Establishment of a distinct person” risk: Export status requires that the supplier and recipient are not merely establishments of the same legal entity. If the GBS entity is structured such that the overseas recipient and the Indian GBS unit could be read as establishments of a single legal person common in branch or fixed-establishment structures rather than clean subsidiary structures the export characterisation itself can be challenged, converting a zero-rated supply into a domestic one attracting GST.

2. Intermediary services recharacterisation: This is the single most litigated issue in Indian GST for shared services and GBS structures. If the GBS entity is seen as arranging or facilitating a supply between two other parties rather than supplying the service on its own account, GST authorities can classify it as an “intermediary.” Intermediary services are deemed to be supplied where the intermediary is located, i.e., in India, which kills the export/zero-rating claim entirely and creates a GST liability on the full value of the transaction, not just a margin. GBS models that coordinate vendor delivery, manage multi-party service chains, or sit between group entities and external clients are structurally closer to this line than captives ever were.

3. Place supply disputes on composite, multi-service contracts: A captive typically delivers one or two well-defined service lines. A GBS entity bundling finance, HR, procurement, analytics, and platform services into a single client contract creates place-of-supply and valuation questions for each component, multiplying the surface area for disputes and slowing down refund processing on the input tax credit side.

None of these are exotic laws. It’s well-trodden territory in Indian GST jurisprudence. What’s underpriced is the operational cost: intercompany agreements, invoicing flows, and even org design (who signs off on what, and where) all need to be built to keep the entity clearly on the “principal supplier” side of the intermediary line not retrofitted after a notice arrives.

Transfer pricing: from cost-plus to a defensible commercial posture

This is where the conversion forces the most fundamental rethink, because it isn’t a compliance filing problem, it’s a characterisation problem.

A captive TP position rests on a simple, defensible story: limited risk, limited functions, cost-plus margin, benchmarked against comparable low-risk service providers. Indian TP practice has a well-established (if periodically revised) safe harbor framework for exactly this fact pattern. As of the 2026 reforms, India’s safe harbor rules were substantially recast: <cite index=”1-1″>software development, IT-enabled services, knowledge process outsourcing and contract R&D were consolidated into a unified “Information Technology Services” category with a common safe harbor margin of 15.5%, and the eligibility threshold was expanded from INR 300 crore to INR 2,000 crore</cite>, alongside <cite index=”6-1″>a new safe harbor for data center services and an extended five-year validity period</cite>. That’s a meaningful widening of the safe harbor’s reach, and its genuinely good news for GCCs that stay within a captive-like functional profile.

The problem is that a converted GBS entity often doesn’t stay within that profile and the moment it doesn’t, safe harbor protection stops being available, because safe harbors are built for routine, low-risk service providers, not entities that price on value, hold delivery risk, or earn a share of client outcomes. A few specific shifts to track:

Functional and risk profile drift: Once the GBS entity negotiates its own contracts, owns SLAs and penalties, and prices based on value delivered rather than cost incurred, the “limited risk” characterisation that justified a modest cost-plus margin no longer matches the facts. Tax authorities will benchmark against a different, and typically more profitable, set of comparables and will argue for a higher arm-length margin than the group’s existing intercompany agreements provide for.
Broader Associated Enterprise (AE) definitions: The transfer pricing framework under India’s new Income-tax Act, 2025 and the Income-tax Rules, 2026 (effective from April 2026) <cite index=”4-1″>consolidated the general and specific categories of Associated Enterprise, broadening the definition</cite> which means intercompany relationships that a GBS entity builds as it takes on new group counterparties need fresh review to determine whether they now fall within scope, even where the earlier captive structure was clean.
Intangibles and DEMPE risk: A GBS entity that develops proprietary tools, platforms, or methodologies as part of “productising” its services starts to own intangibles or at least the DEMPE (Development, Enhancement, Maintenance, Protection, Exploitation) functions around them. If ownership isn’t cleanly documented and priced, both the source of jurisdiction and the parent’s home jurisdiction will have a claim on where that value and the tax on it should sit.
APA and safe harbour strategy need re-deciding, not defaulting: With safe harbour thresholds now far more generous and APA processing being streamlined under the new rules, groups have a real choice to make elect to safe harbour for parts of the business that remain routine, pursue an APA for the parts that don’t, or run traditional benchmarking. Defaulting into whichever approach the captive used before conversion without re-testing it against the new functional profile is exactly the kind of “we’ll finalise it later” decision that turns into a multi-year TP audit.

The pattern behind all three

PE risk, GST export status, and transfer pricing exposure are three different regimes, three different filing calendars, and often three different advisory teams. But they share a root cause: the GBS conversion changes what the entity actually does who it contracts with, how it prices, what risk it bears, what decisions it makes faster than the legal and tax structure around it gets updated to match. The commercial team ships the new operating model on a transformation timeline; the compliance structure catches up on a very different, much slower one, if it catches proactively at all.

That gap is the compliance of debt. It doesn’t show up in the transition budget because nobody’s cutting a cheque for it in year one the LUT still works; the cost-plus margin still clears a safe harbour test; the old intercompany agreements are still technically in force. It shows up later, as interest and penalties on a GST demand, as a TP adjustment with a multi-year lookback, or as a PE assessment that questions whether the group had a taxable presence in India all along.

What underpricing it actually costs

The organisations that get this right treat the conversion as a re-architecture exercise, not a re-labelling one:

Sequence the legal, tax, and commercial changes together, not commercial-first with tax playing catch-up. If the GBS entity is going to start negotiating deals or owning SLAs, that decision-rights change needs a PE and TP review *before* it goes live, not after the first audit cycle.
Re-paper intercompany agreements to reflect actual functions and risks, not the functions and risks the captive used to have. Agreements that still describe a cost-plus, limited-risk service provider while the entity operates as a value-priced, risk-bearing one are a standing invitation to a TP adjustment.
Actively decide the TP defence strategy safe harbour where the fact pattern genuinely stays routine, APA where it doesn’t rather than inheriting whatever the captive used by default.
Build GST invoicing and contracting flows to preserve export status, particularly around anything that could be read as intermediary activity multi-party delivery chains, vendor coordination, or facilitation between group entities and external clients.
Track PE exposure per jurisdiction on an ongoing basis, not as a one-off study, especially where staff travel, second, or take on negotiation authority across the group’s footprint.

None of this shows up on the slide with the two crossing curves. But it’s the difference between a GBS conversion that compounds value and one that compounds liability quietly, for a few years, until it doesn’t.