A functional analysis is the foundation of a transfer pricing report. It explains what the parties do, which assets they use, and which risks they assume and connects those facts to the pricing of their intercompany transactions.
But how should that analysis be documented? Should a report contain one general functional analysis, a separate analysis for each legal entity, or an analysis for each transaction?
The answer depends on the business, the transactions, and the applicable documentation requirements. For multinational groups preparing reports across several countries, the most effective approach often combines a consistent factual foundation with flexibility in how the analysis is presented.
That flexibility matters when documentation must serve several purposes: explaining the business, meeting local reporting requirements, and answering detailed questions during a tax audit.
Three perspectives commonly appear in transfer pricing reports:
- A general overview explains the business model, value chain, and allocation of major responsibilities across the group.
- An entity-level functional analysis describes a particular company’s economically significant activities, assets, capabilities, and risks.
- A transaction-level functional analysis examines what each relevant party contributes to a specific intercompany transaction or category of transactions.
These perspectives overlap. “Top-level” describes the position or depth of an analysis, while “entity-level” describes its subject. A report’s main functional-analysis chapter may already be a detailed entity-level analysis.
For example, consider a distributor whose only significant activity is purchasing products from a related manufacturer and reselling them to customers. Its entity profile and the functional analysis supporting those purchases may cover substantially the same facts. One well-developed analysis, including the supplier’s relevant responsibilities, can provide the foundation for the transaction section.
The position changes when the same company also provides engineering services or licenses technology. Its responsibilities, assets, and risks may differ across those activities. A single description of the company as a “distributor” would leave important questions unanswered.
The practical question is whether the report explains the facts relevant to each pricing conclusion. The number of functional-analysis chapters is secondary.
U.S. documentation provides one reason why reports can look different.
The U.S. documentation rules associated with transfer pricing penalty protection call for both a business and organizational overview and descriptions of controlled transactions, methods, and economic analysis. This structure supports a report that begins with a substantial common business narrative before addressing individual dealings. Treas. Reg. §1.6662-6(d)(2)(iii)(B).
The United States also does not generally require domestic transfer pricing documentation to follow the OECD master-file and local-file format. Group context and entity information may therefore appear together within a U.S. report. These features help explain why some U.S. reports appear more entity-oriented. They do not establish that U.S. reports are generally less transaction-specific. OECD U.S. country profile, questions 29–31.
The selected pricing method can also influence the presentation. The U.S. Comparable Profits Method, or CPM, examines the profitability of a relevant business activity. Where that activity encompasses an entire entity, an entity-oriented narrative can be appropriate. However, the regulation directs the analysis toward the most narrowly identifiable relevant business activity supported by available data. Entity-wide testing is therefore a conclusion to support, rather than an automatic starting point. Treas. Reg. §1.482-5(b)(1).
The IRS is explicit about the quality of the underlying analysis. Its documentation guidance criticizes functional checklists that describe who does what without connecting those facts to the transactions, method selection, and intercompany pricing. A general narrative must still explain why the business facts matter economically. IRS transfer pricing documentation FAQs, Q4.
The OECD framework makes the different perspectives more visible through its documentation structure. The master file provides group context, including entities’ principal contributions to value creation. The local file includes information about the local entity and a detailed functional and comparability analysis for each material category of controlled transactions. That analysis covers the taxpayer and its relevant associated enterprises. OECD Transfer Pricing Guidelines, Chapter V, Annexes I and II.
This does not require repeating the same facts throughout the documentation. The OECD expressly allows a cross-reference where the local-file functional analysis duplicates information in the master file. Shared information can be documented once, with additional analysis explaining its application to the relevant transaction category. Domestic implementation still determines the requirements in each country. OECD Action 13 Final Report, Annex II, note 1.
For a multinational enterprise, this raises a practical question: should every entity follow the same documentation strategy?
We recommend one group-wide framework that allows different local report structures. The framework should establish how facts are collected, verified, attributed to entities, and reviewed. Each report should then reflect the relevant entity’s activities, transaction categories, and local requirements.
In practice, this means:
- Maintaining a consistent account of the group’s business and the parties’ responsibilities.
- Reusing functional descriptions where the underlying facts are genuinely shared.
- Adding local and transaction-specific detail wherever responsibilities, risks, assets, or legal requirements differ.
A group might therefore use a common functional-analysis chapter for a straightforward U.S. distributor and more extensive transaction sections for an entity combining manufacturing, services, and licensing. Different formats can be appropriate within the same multinational. The descriptions of shared arrangements should remain consistent across the reports.
Even companies described as performing the same role need verification. Two distributors may differ in their authority over pricing, marketing activities, inventory exposure, or customer relationships. A standard group profile is a useful starting point, but those differences may affect the analysis.
HMRC’s guidance illustrates this principle: centrally prepared functional analysis can be appropriate where it sufficiently reflects the local entity, with supplementary investigation and information where needed. HMRC Guidelines for Compliance, Part 2, §2.2.2.
TPGenie supports both entity-level and transaction-level approaches to documenting functional analysis. Teams can choose a structure that fits their business and reporting requirements, using the relevant narratives and tables to explain responsibilities and differences clearly.
Financial data offers a smaller example of the same flexibility: TPGenie allows it to be entered by legal entity or by transaction. The appropriate scope of the financial analysis still follows from the activities and transactions being evaluated.
A well-documented functional analysis allows a reader to follow the reasoning from business activities to transfer pricing conclusions. TPGenie gives teams the flexibility to present that reasoning at the level their documentation requires.
Contact Us for a DEMO
Recent Comments