What Pillar Two Means for TP Teams: Workflow and Data Checklist

Pillar Two does not replace transfer pricing — it hangs a new set of questions on top of it. The group still prices every controlled transaction at arm’s length under s.92 (or the local equivalent), still prepares the documentation, and still defends the margins in an audit. What changes is that the outcome of that pricing work now feeds a second computation — the jurisdictional ETR — and the tax team can no longer treat the pricing file and the Pillar Two file as two separate exercises. This guide is the working view: what the TP team now owes, where it touches existing processes, and the checklist to take into the planning cycle.

Why the pricing decision moved up the stack

The chain of dependency runs one way:

Intercompany price (the TP decision, inside the arm's length range)
  → jurisdictional profit split (the PBT per entity, per jurisdiction)
    → adjusted covered income (the GloBE denominator)
      → jurisdictional ETR (covered taxes ÷ ACI)
        → top-up tax allocation (IIR / UTPR / QDMTT)

Each link is documented in its own guide — the GloBE rules, the ETR and SBIE, the charging mechanisms — but the practical consequence is new: a pricing decision that is perfectly arm’s length can still move top-up tax between jurisdictions, and a Pillar Two position that looks optimal on the tax return can pull on the defensible pricing position. The TP team’s range of arm’s length outcomes is now a tax-planning input, not just a compliance output.

Three concrete effects:

Effect	What changes for the TP team
Range choice has a second consequence	Any point inside the arm’s length range is defensible; where in the range the group prices now also determines the jurisdictional split and the resulting ETRs. The selection within the range (mid-point, median, a specific comparable) should be documented with the Pillar Two effect in view
Safe harbour positions interact	India’s safe harbours (Rule 10AA/10AB) fix the price at the safe level; that fixed price is a known quantity in the ETR computation, which makes those entities’ jurisdictional contributions stable inputs to the GloBE model
Restructurings price twice	A group restructuring now has an arm’s length dimension (exit charges, location savings) and a GloBE dimension (the jurisdictional ACI and ETR move with the migration of profit). The sequencing of the two analyses is a planning decision

The new data duties (and where they live)

The Pillar Two computation consumes data the TP function already produces or sits next to. The mapping that matters for workflow:

Data item	Source today	Pillar Two use
Jurisdictional PBT per entity	Consolidation / local statutory accounts	The ACI starting point
Intercompany balances and margin positions	The TP study / benchmarking file	The consistency adjustment (the intercompany effects must be computed consistently across the group)
Payroll per entity (the SBIE payroll credit)	HR / statutory payroll	The SBIE exclusion in the ETR computation
Tangible asset costs (the SBIE PP&E credit)	Fixed asset registers	The SBIE exclusion
Covered taxes (current + deferred, per the model rules)	Tax provision schedule	The ETR numerator
Loss carryforwards and their utilisation	Tax provision schedule	The numerator and the loss-year mechanics
Entity scope (the €750m consolidated revenue test, the in-scope entities)	Consolidation	The scope determination
CbCR data (revenue, PBT, tax paid, employees, assets per jurisdiction)	The CbCR return	The transitional safe harbour and the data backbone for the steady-state computation

The workflow implication: the CbCR data-quality work is now Pillar Two work. The CbCR and Pillar Two guide covers the shared scope and the reconciliation; the point for the team is that a CbCR number that was “close enough” for exchange purposes is not close enough when it drives a top-up tax allocation across the group.

Where it touches the existing processes

The benchmarking / pricing process

• The arm’s length range is now a two-objective input. Defensibility (the audit) and the jurisdictional outcome (the ETR) are both real objectives; the documented selection within the range should state the pricing rationale first — the Pillar Two effect is a consequence to be aware of, not the stated reason for a price. A price chosen because of the ETR effect, documented as a pricing decision, is the position the transfer pricing audit will challenge.
• Safe harbour elections become model inputs. Where the group relies on Rule 10AA/10AB for services or KPO, the safe margin is a fixed, known input to the jurisdictional split — use it in the model rather than re-benchmarking that line every year (the benchmark still stands as the fallback if the safe harbour conditions fail).
• Multi-year and roll-forward studies get a consumer. The three-year benchmark history (multi-year averaging) is now also the history of the jurisdictional split the ETR runs on — keeping the study data and the consolidation consistent year over year is part of the defensibility of both.

The documentation process

• The Local File / Master File gain a cross-reference, not a new chapter. The Master File group-structure and intangibles narrative and the Local File benchmarking annex remain as they are; the addition is a short note where the pricing position feeds the jurisdictional computation (the price, the range, the selection, and that the jurisdictional split is used in the group’s minimum tax computation).
• Intercompany agreements now carry a second reader. The agreements that fix the pricing policy (intercompany agreements) are read by the GloBE function for the consistency rules — the documented pricing policy is what the computation must follow for the intercompany adjustments.
• Contemporaneity applies to the new data too. The penalty protection logic in India (and the contemporaneity expectations elsewhere) is built on the documentation being prepared as the transactions happen; the Pillar Two data pack that supports the pricing positions should be built on the same annual cycle, not assembled after the ETR is in dispute.

The audit / dispute process

• The TP adjustment and the top-up are now sequenced events. A transfer pricing adjustment (the TPO or the foreign authority) changes the jurisdictional profit — which changes the ACI — which changes the ETR — which changes the top-up allocation. The audit defense work now includes tracking the GloBE effect of any proposed adjustment before the position is settled, because the tax cost of the adjustment is no longer just the income tax.
• MAP becomes a two-sided negotiation. The MAP / DTA procedure resolves the double taxation of the adjustment; the correlative relief must now also be reflected in the top-up computation of both jurisdictions.

The team action checklist

The practical cycle, in order:

1. Scope. Confirm the consolidated revenue (the €750m test), the in-scope entities, and the jurisdictions with a mechanism (the IIR/UTPR/QDMTT map) — once a year, and on any structural change.
2. Data. Lock the jurisdictional PBT, payroll and PP&E per entity from the same consolidation the ETR runs on; reconcile the CbCR figures to it. The CbCR guide has the data-quality risks.
3. Pricing. Run the benchmarking as usual; document the selection within the arm’s length range with the pricing rationale; note the jurisdictional effect as a consequence. Use safe harbour positions as fixed inputs where elected.
4. Model. Feed the split into the GloBE computation (the GloBE rules for the mechanics); check the transitional safe harbour eligibility for the applicable years.
5. Document. Cross-reference the pricing positions into the Master File / Local File; keep the intercompany agreements consistent with the computed positions.
6. Dispute. Track the GloBE effect of any proposed TP adjustment before settlement; run the MAP consequences for the top-up in both jurisdictions.
7. Refresh. Annual: repeat 1–5. On change: re-scope (1) and re-model (4) for restructurings, new entities, new jurisdictions, or mechanism changes (a QDMTT coming into force in a group jurisdiction is the common one).

FAQ

Does Pillar Two change what an arm’s length price is? No. The method, the range and the tested party logic are unchanged — the arm’s length principle still governs the price. What changes is that the price’s consequence extends into the minimum tax computation, so the team holds two views of the same number.

Does the SBIE reward low pricing in substance jurisdictions? It rewards substance (payroll and tangible assets) — the exclusion is a credit against the top-up base for the real economy in the jurisdiction. It is not a pricing lever: moving payroll or assets to change the SBIE is a business decision with its own transfer pricing and commercial consequences, not a tax optimisation of the price.

What should the TP team do first if the group is in scope? The data reconciliation (item 2 of the checklist): the ETR is only as good as the jurisdictional split and the payroll/PP&E inputs, and the CbCR-to-consolidation reconciliation is where most in-scope groups find their first gaps. The CbCR and Pillar Two guide has the reconciliation view.

Do the existing TP studies need to be reworked? No rework — a cross-reference and a consistent data pack. The studies keep their structure and their defensibility; the addition is the note that the pricing position feeds the jurisdictional computation, and the annual data lock that keeps the two consistent.