DOCUMENTATION

Transfer Pricing

Treaty and cross-border operations

Transfer pricing starts with the real transaction, the people who control it, and the evidence that supports the pricing outcome. For most groups, the difficult work is not selecting a method in the abstract, but aligning contracts, conduct, value creation, and documentation before an audit forces that alignment.

Overview

A defensible transfer pricing position usually turns on accurate delineation first. That means identifying the actual conduct of the parties, the economically significant risks, and which entity has the capability and authority to control those risks. Once that foundation is sound, method selection, benchmarking, and policy implementation become far more reliable.

For platform users, transfer pricing is rarely a standalone memo. It intersects with IP ownership, treasury flows, service centers, commissionaire or limited-risk distribution models, and Pillar Two data. The operational question is whether the fact pattern, contracts, and local files tell one coherent story across jurisdictions.

How Uncle Louis helps

Use the platform to consolidate contracts, correspondence, organizational evidence, and prior memoranda into one audit-ready narrative. That makes it easier to move from transfer pricing theory to a documented position that tax authorities can actually test.

Useful outputs for platform users

A scoped memorandum on intercompany pricing, DEMPE, or financial transactions.
A fact map that reconciles contracts, emails, meeting records, and entity functions.
A practical documentation plan covering master file, local file, and supporting evidence packages.

When this topic matters

A group is migrating IP, centralizing procurement, or redesigning supply chain functions.
Intercompany services, cost allocations, or management charges have grown faster than headcount and substance.
Treasury entities are making loans, guarantees, cash pooling arrangements, or hedging decisions for the group.
Local file and master file narratives do not clearly match board minutes, budgets, and functional reality.

Common risk flags

Cash-box entities receive residual return without control over funding or strategic decisions.
DEMPE activity sits in one jurisdiction while legal ownership and returns sit in another with limited personnel.
Routine entities report volatile margins that do not fit the stated functional profile.
Year-end true-ups solve accounting targets but are not supported by contemporaneous operational evidence.

How the analysis should be structured

Delineate the controlled transaction

Map the actual transaction, tested parties, contractual terms, and commercial context before choosing a pricing method.

Test functions, assets, and risk control

Confirm who performs DEMPE functions, who funds and controls risk, and whether legal ownership matches operational decision-making.

Select and defend the pricing method

Choose the method that best fits the transaction, document comparability adjustments, and explain why alternatives are weaker.

Connect policy to implementation

Tie the pricing policy to invoices, year-end adjustments, local files, intercompany agreements, and audit-ready evidence.

Questions users typically ask

Does this IP owner really earn residual return, or should value shift to the operating entity performing DEMPE?

What is the strongest defense for a limited-risk distributor with declining margins?

How should we document intercompany loans and guarantees so the pricing logic survives scrutiny?