Key Takeaways
- The OECD three-tiered structure requires a master file, a local file, a country-by-country report, and supporting intercompany agreements for groups exceeding the EUR 750M consolidated revenue threshold.
- Missing or incomplete documentation shifts the burden of proof to the taxpayer in most EU tax jurisdictions, exposing the group to penalties and double taxation.
- Auditors test TP documentation under ISA 540 because the arm's length price is an accounting estimate with inherent measurement uncertainty.
- Tax authorities in Germany, the Netherlands, France, and Italy impose specific documentation deadlines (often within 60 to 90 days of a request).
What is transfer pricing documentation?
We see this pattern on about half the mid-market group audits we review: the client hands over a benchmarking study that is three years old, and nobody on the engagement team checks whether the comparables still hold. The file should tell a story of how each intercompany price was set and tested, but too often it reads like a compliance afterthought assembled the week before filing.
Transfer pricing documentation (TP documentation) is the set of records a multinational group prepares to show that its intercompany prices satisfy the arm's length principle. The OECD Transfer Pricing Guidelines Chapter V organises this into four components: the master file (group-wide overview of the multinational's business and TP policies), the local file (detailed analysis of each entity's intercompany transactions with comparability data), the country-by-country report (CbCR) filed when consolidated revenue exceeds EUR 750M, and the intercompany agreements that underpin each transaction category.
Most EU member states have transposed these requirements into domestic legislation with local variations. The Netherlands requires TP documentation to be available at the time of filing the corporate tax return. Germany's Gewinnabgrenzungsaufzeichnungsverordnung (GAufzV) obliges taxpayers to present documentation within 60 days of a tax authority request (30 days for extraordinary transactions). ISA 540.13 (a) requires the auditor to evaluate management's method for determining arm's length prices, and ISA 550.11 requires identifying related party transactions that fall outside normal business terms. In practice, the audit team reviews the benchmarking studies and functional analyses that form the local file, then assesses whether the entity's transfer pricing policy has been applied consistently across the group.
Worked example: Schafer Elektrotechnik AG (TP documentation review)
Client: German electronics manufacturer, FY2025, revenue EUR 310M, IFRS reporter. Schafer has subsidiaries in Poland (assembly), the Netherlands (distribution), Portugal (shared services), and a Japanese parent. Consolidated group revenue exceeds EUR 750M. The engagement team must evaluate the TP documentation package.
Step 1 — Assess the documentation structure
Schafer prepares a master file at group level describing the organisational structure, intangible ownership (patents held by the Japanese parent, licensed to Schafer at a 4% royalty on net sales), intercompany financing arrangements, and the group's TP policy. Each subsidiary maintains a local file. The Japanese ultimate parent files the CbCR.
Documentation note: obtain the master file and each local file. Confirm that the master file covers all five categories required by OECD Chapter V, Section B (organisational structure, business description, intangibles, intercompany financial activities, and financial and tax positions). Record the date each document was last updated.
Step 2 — Evaluate the local file for Schafer AG
The German local file documents three categories of intercompany transactions. First, product sales from the Polish assembly subsidiary to Schafer AG at EUR 48M (cost-plus 8% method). Second, distribution commissions paid to the Dutch subsidiary at EUR 6.2M (transactional net margin method, operating margin benchmark of 2.5% to 4.1%). Third, shared services fees received from Portugal at EUR 1.8M (cost-plus 5%). This is where the real work starts: each category needs its own method justification, its own comparable set, and its own position-in-range analysis.
Documentation note: for each transaction category, record the TP method selected, the comparable set used in the benchmarking study, the interquartile range, and where the actual result falls within that range. Reference ISA 540.13 (b) on evaluating the data and assumptions underlying the estimate.
Step 3 — Test the benchmarking study currency
The Dutch subsidiary's benchmarking study was prepared in 2022 using a search for comparable distributors with data from 2019 to 2021. Three fiscal years have passed without an update. Stale comparables are common. GAufzV requires documentation to reflect current conditions, so the engagement team flags the outdated range as a risk that the arm's length benchmark may no longer hold.
Documentation note: record the date of the benchmarking study, the financial years of the comparable data, and the auditor's conclusion on whether the study remains reliable. If the study is outdated, document the discussion with management and whether an updated search has been commissioned. Reference ISA 540.18 on evaluating the reasonableness of management's assumptions.
Step 4 — Evaluate the royalty arrangement
Schafer pays a 4% royalty to the Japanese parent on net sales (EUR 310M x 4% = EUR 12.4M), documented in the master file. A comparability analysis in the local file uses the comparable uncontrolled price method, referencing licence agreements in public databases. Comparable royalties produce an interquartile range of 3.0% to 5.5%. At 4%, the actual rate falls within range.
Documentation note: record the royalty rate, the CUP method applied, the comparable agreements identified (number, source database, date range), the interquartile range, and the position of the actual rate within it. Cross-reference to IAS 24.18 disclosure of the royalty as a related party transaction.
Conclusion: three of four transaction categories are documented with current benchmarking data and fall within arm's length ranges. The Dutch distribution commission requires an updated comparability study before the file can be considered complete. For the three current categories, the approach appears reasonable. Waive further pursuit. Flag the Dutch category for remediation before sign-off.
Why it matters in practice
Audit teams frequently accept TP documentation prepared by the client's tax adviser without evaluating whether the benchmarking studies are current. ISA 540.13 (b) requires the auditor to assess the data and significant assumptions underlying the estimate. A comparability study based on data that is four or five years old may no longer reflect market conditions, and the arm's length range it produces may be unreliable. The auditor cannot outsource this evaluation to the tax adviser. This is the finding that generates the most review notes on group audit files we see.
We've seen engagement teams test only the largest intercompany transaction and overlook smaller flows (management fees and intercompany loans) that in aggregate exceed materiality. ISA 550.11 requires identification of all related party transactions outside normal business terms. Four individually immaterial transactions at non-arm's length prices can produce a combined misstatement that is material to the tax provision.
Transfer pricing documentation vs. related party disclosures ( IAS 24 )
| Dimension | Transfer pricing documentation | Related party disclosures ( IAS 24 ) |
|---|---|---|
| Purpose | Demonstrates to tax authorities that intercompany prices are at arm's length | Informs users of financial statements about related party relationships and transactions |
| Audience | Tax authorities, transfer pricing auditors | Investors, creditors, financial statement users |
| Content | Functional analysis, comparability studies, benchmarking data, intercompany agreements | Nature of relationship, transaction amounts, outstanding balances, terms and conditions |
| Governing framework | OECD Guidelines Chapter V, local tax legislation | IAS 24.18 , IAS 24.19 |
| Timing | Must be available at or before the tax filing date (varies by jurisdiction) | Published with the annual financial statements |
In practice, the same intercompany transactions appear in both sets of documentation. Auditors test the IAS 24 disclosures against the TP local file to confirm consistency. When a transfer price that the local file defends as arm's length is missing from the IAS 24.19 note (or disclosed inconsistently), that gap is exactly what an engagement quality reviewer will question.
Related terms
Related tools
Related reading
Frequently asked questions
What happens if transfer pricing documentation is missing during a tax audit?
In most European jurisdictions, the absence of contemporaneous documentation shifts the burden of proof from the tax authority to the taxpayer. The tax authority may then estimate the arm's length price using its own comparables, which typically produces a higher taxable income. Under German law (Section 162(3) AO), the authority may also apply a penalty surcharge of 5% to 10% of the adjusted income. ISA 250.A6 requires the auditor to consider the implications of non-compliance with laws and regulations on the financial statements.
Does transfer pricing documentation need to be updated every year?
The OECD Transfer Pricing Guidelines Chapter V, paragraph 5.22 recommend that the local file be reviewed and updated annually. The benchmarking study itself does not need to be refreshed every year if the functional analysis has not changed, but the OECD recommends updating the comparable financial data at least every three years. Most European tax administrations follow this approach. ISA 540.18 requires the auditor to evaluate whether the assumptions in the documentation remain valid at the reporting date.
Do small groups below the EUR 750M CbCR threshold still need transfer pricing documentation?
Yes. The CbCR threshold applies only to country-by-country reporting. The master file and local file obligations exist independently under domestic legislation in most EU member states, regardless of group size. A German subsidiary of a EUR 50M group must still maintain transfer pricing documentation under GAufzV if it enters into intercompany transactions. The documentation scope may be simplified for smaller entities, but the obligation itself is not waived.