Group Restructuring TP: Exit Charges, Location Savings and ThinCap

A group restructuring — migrating an IP owner, moving the manufacturing base, consolidating the treasury, shifting the service centre — is not a pricing event in the ordinary sense. It is a reallocation of functions, assets and risk across jurisdictions, and the transfer pricing questions are the questions about what moves, what stays, and what each side is owed for the change. The OECD’s position (the 2015 guidance on business restructurings) is the reference: the restructuring is respected where it has a valid business or economic reason, the reallocation follows the restructured functions, and the compensation for what is given up is priced arm’s length.

The business rationale first

Before any pricing, the file must establish why the restructuring happened — the valid commercial or economic reason, documented contemporaneously:

• The genuine reasons: operational efficiency (consolidating the service centre where the skills are), market access (moving the regional sales entity to the market it serves), regulatory response, the group’s portfolio rationalization, the cost structure.
• The document that carries it: the board materials, the restructuring business case, the management presentation — the records that show the decision was made for the stated reason, before the tax analysis was final.
• The test the authorities apply: whether the restructuring has a real commercial rationale beyond the tax outcome. A restructuring whose records show the tax outcome was the driver is a restructuring the examination unwinds — the functions, assets and risk are treated as never having moved, and the pricing is re-examined on the pre-restructuring basis.

The rationale is not a disclaimer in the Local File; it is the business record, attached and referenced.

Exit charges: what the exiting party is owed

Where a participant exits an arrangement — leaves a cost sharing arrangement, stops performing a function another party continues, surrenders an intangible it developed or co-developed — the question is the exit charge: what the continuing arrangement owes the exiting party for the value it surrenders.

• The OECD position: where the exiting party contributed to the value that continues (the development it performed, the intangibles it brings to the arrangement), the continuation is compensated — the exit payment prices the value the exiting party gives up, on the same valuation discipline as a CSA entry payment (the value at the exit date, the prospective analysis).
• The practical positions: a pure service provider exiting (it performed a routine function, it owns nothing that continues) owes and is owed nothing beyond the service fees through the exit date — no exit charge. A development participant exiting a CSA with a live benefit ratio is owed the value of its share of the intangible at the exit date. The line between the two is the DEMPE record of what the exiting party actually contributed and controlled.
• The Indian position: India has no codified exit-charge regime — the question is approached under the s.92 arm’s length standard, and the practice is thin and case-specific. The file’s job is the analysis either way: what the exiting party contributed, what continues, and the valuation of the value surrendered — because the absence of a codified regime is not the absence of the question, and the counter-jurisdiction (where the continuing value sits) may price it.

Location savings: the cost reduction from the move

A restructuring that moves a function to a lower-cost location generates a location saving — the ongoing cost reduction from performing the function where it now sits. The OECD’s apportionment rule:

• The saving is not the relocating entity’s to keep, nor the commissioning entity’s to claim in full — it is apportioned between the parties in proportion to the economic value of the functions they perform and the assets/risk they bear.
• The typical split in practice: the saving is shared (the benchmark is the negotiation, informed by the functional comparison) — the commissioning party that would otherwise pay the higher-cost location gets a price reduction; the performing entity that moved gets a return that reflects its function at the new cost base.
• The documentation: the pre- and post-restructuring cost bases, the saving quantified, the apportionment with the functional reasoning, and the ongoing pricing that reflects the new cost structure — the post-restructuring study (the new tested party position, the new pool where the function’s economics changed) run from the first post-move year.

Thin capitalization: the debt that follows the restructuring

Restructurings routinely move the group’s debt — the treasury consolidation, the acquisition funding, the intercompany loan stack — and the thin capitalization question is whether the debt loaded onto an entity exceeds what an independent lender would have provided it.

• The independent-lender test (the general standard): the entity’s debt level is arm’s length where an independent lender would have lent it that much, on that security, at that rate — the entity’s standalone leverage, the security package, and the group-support analysis (see intercompany finance).
• The Indian statutory cap: under section 92(3), the interest deductible for a borrowing (domestic or external) is capped — the computation runs on the debt-to-equity ratio of 3:1 as the base, with interest beyond the cap at the prescribed deemed rate (the lower of the statutory deemed rate or the actual rate, on the excess). The cap is a deduction limit in the Indian computation, and it operates alongside the arm’s length rate benchmark, not instead of it.
• The restructuring interaction: where the restructuring moved debt onto an entity that did not previously carry it, the thin-cap analysis is on the post-restructuring capital structure — and the file that loads the relocated entity with debt its standalone profile does not support has priced the debt the way the lender would not have lent it.

The documentation sequence

The restructuring file is a sequence, and the sequence is the defence:

1. The business case — the valid commercial reason, the board record, dated before the implementation.
2. The functional map, before and after — the FAR of each entity pre- and post-restructuring: what functions, assets and risk moved, what stayed.
3. The valuations — the intangibles that transferred (the valuation at the transfer date), the exit payments (the value surrendered, per the DEMPE record), the entry payments into continuing arrangements.
4. The ongoing pricing — the post-restructuring agreements (the new service fees, the new royalty, the new loan terms) with the benchmarks — the post-move study, not the pre-move study re-labelled.
5. The tax positions, per jurisdiction — the Indian position (the s.92 analysis, the thin-cap computation, the exit-charge analysis) and the counter-jurisdiction positions, consistent with each other — because the restructuring that is priced correctly in one jurisdiction and incorrectly in the other is the double-taxation case, and the file that anticipated the inconsistency (the mapping agreement, the APA where available) is the file that survived it.

See also

• Intangibles TP
• Intercompany finance
• Intercompany agreements
• DEMPE