Transfer Pricing Policy: Building a Defensible Company-Wide Framework

A transfer pricing policy is the company-wide framework that fixes, in advance and in one document, how the company’s controlled transactions are characterized, priced, documented and reviewed. It is the layer above the Local File: the Local File is the year’s application, the policy is the standing rule the application follows. Groups without a policy price each transaction, each year, from scratch — and the file that is assembled transaction-by-transaction is the file with the gaps, the inconsistencies and the after-the-fabricated decisions that the examination finds. The policy is how those decisions are made once, deliberately, and kept consistent.

The components

A defensible policy contains, at minimum:

Component	The content	The standard it implements
Scope and governance	The entities and transactions in scope; who owns the policy (the TP function, the finance leadership); the approval chain; the escalation for deviations	The accountability structure — the policy is owned, not floating
The functional inventory	Per entity: the functions performed, the assets employed, the risks borne — the group’s FAR map, the Master File’s structure and business description in operational form	The OECD FAR standard, applied to the whole group
The pricing principles	Per transaction type: the method, the PLI, the cost-base definition, the benchmarking approach, the safe harbour elections — the group’s method register	The best-method rule, applied consistently; the PLI reference discipline
The documentation standard	The three-tier requirements (Local File, Master File, CbCR), the contemporaneity deadline (the 31 May preparation window), the retention (8 years), the consistency reconciliation step	The Rule 10D/10DA and CbCR obligations, with the internal deadlines that make them meetable
The intercompany agreement standard	The required clauses (scope, IP, pricing mechanic, decision rights, term), the consistency-with-conduct rule, the amendment and renewal discipline	The substance-over-form standard — the agreement guide in policy form
The monitoring and review	The annual review cycle (the benchmark refresh, the position check, the trend analysis), the deviation log, the self-audit	The ongoing-compliance discipline, not the year-end scramble
The dispute and escalation	The notice-response procedure (the 282BC production), the expert-report decision, the appeal route, the AAR strategy	The audit defense prepared as a standing procedure

The pattern: every examined choice has its standing rule in the policy — the method, the PLI, the cost base, the tested party, the documentation standard, the agreement standard, the response procedure. The Local File then applies the policy to the year, and the application is checkable against the rule.

The governance

The policy is a governance instrument before it is a technical one:

• Ownership. The policy is owned by a named function (the TP function, or the finance leadership where there is no dedicated team), with a named approver. A policy with no owner is a document; a policy with an owner is a control.
• Approval and change control. The policy is approved (the finance leadership, the audit committee where the group has one), and changes to it are controlled — a change to the method register or the documentation standard is a policy amendment, dated and reasoned, not a quiet edit. The change trail is part of the defence: the policy’s evolution is as examinable as its content.
• The deviation log. Where a transaction departs from the policy’s standing rule (the one-off fact pattern, the acquired business, the new market), the deviation is logged with the reason and the approval — the deviation is legitimate and documented, not an inconsistency discovered in the examination.

The refresh triggers

The policy is not written once. The standing triggers that force the review:

Trigger	The review
Annual cycle	The benchmark refresh (the pool, the range, the tested party’s position), the documentation cycle completion, the year-on-year trend check — the policy’s monitoring section run on the year
Structural change	The restructuring, the acquisition, the new entity, the function migration — the restructuring review: the FAR map updated, the pricing principles for the new/changed transactions set, the documentation for the transition years
Threshold crossings	The CbCR/Master File threshold crossed (the group’s revenue over ₹1,000 cr / €750 mn), the Local File threshold crossed (the ₹30 cr revenue), the safe harbour threshold crossed — the new tier’s obligations added to the policy’s documentation standard
Market or data change	The industry’s economics moved (the margin compression, the new competitor structure), the database definitions changed, the safe harbour circumstances amended — the pricing principles re-examined against the new reality
Exposure event	The notice received, the adjustment proposed, the appeal filed — the dispute procedure run, and the policy updated with what the event showed (the weak spot fixed for the next year)

The trigger discipline is what keeps the policy alive: a policy reviewed on triggers is a current control; a policy reviewed “when someone remembers” is a shelf document, and the shelf document is the one the examination compares the files against and finds the files do not follow.

The board reporting

The TP position is a board-level risk item, and the reporting is the policy’s top layer:

• The annual TP report — the group’s TP position: the controlled transactions, the methods applied, the benchmark positions (inside/outside the range), the safe harbour elections, the exposures (the open examinations, the pending appeals, the quantified risk), the policy changes and deviations.
• The risk framing — the TP risk stated in the board’s language: the quantified exposure (the adjustment range, the penalty exposure, the interest), the likelihood (the examination history, the industry scrutiny, the CbCR flag profile), and the mitigation (the policy controls, the AAR positions, the documentation readiness).
• The decision items — where the TP position requires a board decision: the restructuring’s pricing, the AAR application, the appeal settlement range, the policy’s material changes.

The board report is the evidence of the governance in action — the policy that is reported, decided and minuted is the policy the examination finds a company running, which is a different fact from the policy it finds a company filed.

How it survives an audit

The examination’s question, applied to the policy: does this company price its transactions by a standing rule, or by the year’s convenience? The answers that pass:

• The Local Files apply the policy’s method register — the method, the PLI, the cost base, per the standing rule, with the deviations logged.
• The documentation standard is met on the dates — the 31 May preparation, the production readiness, the 8-year retention — because the standard is the policy’s, and the year’s cycle ran to it.
• The agreements match the policy’s agreement standard — the clauses, the consistency, the renewals — because the standard is enforced on every intercompany paper.
• The trend is explained — the year-on-year movement in the positions is the policy’s monitoring output, not a discovery.

The policy does not prevent the adjustment — the price is still examined, and the market still moves. What the policy does is make the company’s position the application of a known, current, governed rule — and a position that is the application of a rule is defended as a rule was applied, not reconstructed as a year was spent. That is the difference the examination finds, and the difference the outcome turns on.

See also

• The documentation pillar guide
• Master File
• TP audit defense
• 10 documentation weaknesses