When a French subsidiary invoices a software licence to its Dutch parent, or a shared service centre bills accounting services to eight group entities across six countries, two questions inevitably arise: at what price? And can you justify it?
Tax administrations in more than 100 jurisdictions have been asking the same questions since the BEPS action plan was finalised in October 2015 — and they now have automatic information-exchange tools that let them cross-reference the same entity’s filings across multiple countries in seconds. Transfer pricing documentation, long treated as an annual exercise delegated to a specialist firm, has become a permanent traceability obligation that your ERP must be able to support.
This guide is aimed at CIOs, CFOs and tax directors of multi-entity groups who need to align their information systems with master file and local file requirements, understand the materiality thresholds that apply in their jurisdictions, and identify what their ERP can realistically document — and what requires additional tools.
BEPS Action 13: The Three-Tier Framework Behind All TP Documentation
The OECD’s Base Erosion and Profit Shifting action plan, finalised in October 2015 with the publication of 15 final reports, introduced a three-tier documentation architecture for transactions between entities within the same multinational group. More than 100 jurisdictions have transposed these rules into domestic law, making this architecture unavoidable for any group operating internationally.
The Master File
The master file provides a group-level overview. It covers five broad dimensions:
- Organisational structure: legal entity diagram, details of shareholdings and voting rights.
- Business description: the group’s main sources of value creation, the supply chain for the five main product and service categories, significant intercompany agreements.
- Intangible assets: list of material intangible assets (brands, patents, know-how), intragroup licensing agreements, R&D and intangibles management policy.
- Intercompany financial activities: description of intragroup financing, interest rate policy, cash pooling arrangements.
- Group tax positions: existing rulings, advance pricing agreements (APAs), significant tax positions.
The master file is a governance document, not a transaction-by-transaction analytical document. It answers the question: how does the group operate and how is value distributed across entities?
The Local File
The local file is the most operationally demanding component. Produced at the level of each legal entity, it documents material controlled transactions — those between group entities that exceed the applicable materiality thresholds.
For each transaction category (goods purchases, services, royalties, intercompany loans, asset transfers), the local file must present:
- A description of the transaction, the parties involved, volumes and amounts.
- The functional analysis: who does what, who bears which risks, who uses which assets in the transaction.
- The transfer pricing method selected (comparable uncontrolled price, resale price method, cost-plus method, transactional net margin method, profit-split method) and the rationale for the choice.
- The benchmark: a comparison with transactions between independent companies demonstrating compliance with the arm’s length principle.
The Country-by-Country Report (CbCR)
The third tier applies to groups whose consolidated revenue exceeds €750 million (BEPS Action 13 threshold, confirmed through implementation under the GloBE rules). It summarises for each jurisdiction: revenues, profit before tax, taxes paid, headcount, capital and reserves, and tangible assets. This document allows tax administrations to detect mismatches between declared profits and real economic activity in each country — a potential indicator of aggressive tax optimisation.
National Transpositions: Key Thresholds Across Jurisdictions
Most OECD member states and G20 countries have implemented BEPS Action 13 with differentiated obligations based on entity size, following the OECD’s recommended tiered approach.
Common Threshold Patterns
Full documentation (master file + local file): Most jurisdictions require complete TP documentation for entities whose annual turnover or balance sheet total exceeds a defined threshold — typically in the €150–250 million range. This obligation generally extends to entities holding controlling stakes in subsidiaries that meet the same threshold.
Simplified annual declaration: Entities above a lower materiality threshold (commonly around €50 million) are typically subject to a simplified annual reporting obligation, requiring disclosure of aggregated intercompany transaction amounts by category and the primary transfer pricing method used for each transaction type.
Penalties for Non-Compliance
The consequences of inadequate TP documentation are significant across jurisdictions. Common penalty structures include:
- A percentage of the taxable profits deemed transferred abroad through inadequate transfer prices (typically 5%), or
- A percentage of the undocumented transaction amounts (typically 0.5%), subject to a minimum floor per fiscal year
Taxpayers are generally given a tight deadline — often 30 days from formal notice — to provide complete documentation. This timeframe makes any “on-demand” documentation approach built on manual ERP extractions operationally unworkable.
The EU Regulatory Layer: DAC4 and DAC6
At the European level, Directive DAC4 (2016) transposed BEPS Action 13 obligations into EU law, imposing automatic exchange of country-by-country reports between member states’ tax administrations. Directive DAC6 (2018/822/EU) added a mandatory reporting layer for potentially aggressive cross-border tax arrangements. These two directives create growing pressure on the consistency of TP documentation across a group’s various European jurisdictions.
What the Master File Requires of Your Group Information Systems
Producing the master file depends on data that, for the most part, must be extracted from multiple group systems. The central ERP plays a key role for several sections.
Organisational structure. Your multi-entity ERP must maintain a legal entity register covering group participations. In SAP S/4HANA, this register is the company hierarchy. In Microsoft Dynamics 365, it is the legal entity structure. In Oracle Fusion Cloud ERP, the Business Unit and Legal Entity concepts structure this information. This register is the starting point for the master file.
Intercompany financial arrangements. Cash pooling agreements, intercompany loans and guarantees must be documented with their applicable rates. The ERP must be able to report the average outstanding intercompany receivables and payables per entity, as well as the net interest booked. Our dedicated guide on group cash pooling and ERP details how these flows are tracked in the leading ERP platforms.
Supply chain. The description of the five main product and service categories requires the ability to extract physical and financial flows between entities from the ERP. An intercompany sales management module, with associated incoterms, is essential.
What the Local File Requires Transaction by Transaction
The local file is the most data-intensive exercise for ERP teams. For each category of material controlled transactions, several structured elements must be extracted.
Aggregated amounts by transaction type and entity. The ERP must enable extraction of intercompany flows broken down by nature (goods, services, royalties, financing) and by counterparty entity. In a well-configured ERP, accounting journals systematically record the related-party entity on each intercompany entry. Without this configuration, manual reconstruction represents weeks of work for the tax team.
Agreement documentation. Intercompany service agreements (CSA, staff secondment agreements, brand licences) must be registered and versioned in the document management system linked to the ERP, or in a connected CLM (Contract Lifecycle Management) tool. Each price revision must be traceable with its effective date.
Method and benchmark. This component lies outside the ERP — it sits in the economic analysis performed by the tax department or the TP firm. It uses ERP data as inputs (gross margins by entity, intercompany service costs) but processes them through comparable databases (Bureau van Dijk Orbis, S&P CapIQ) and specialist tools (Thomson Reuters TP Catalyst, ONESOURCE TP). The ERP is the data source, not the analytical tool.
Why the ERP Is the Natural Starting Point for TP Documentation
Centralising Transactional Data
A multi-entity ERP natively captures three of the five major TP data sources:
- Intercompany financial flows (intercompany invoices, payments, outstanding balances)
- Gross margins and cost of goods sold by entity and product line
- Headcount and payroll costs by entity (useful for functional analyses)
In an SAP S/4HANA deployment with a central instance, an intercompany document is automatically generated for each transaction between group companies. This document carries the same group document identifier (document group) on both the seller and buyer side, making intercompany elimination in consolidation and TP traceability immediately available. The SAP Intercompany Reconciliation (ICR) module automatically reconciles reciprocal balances and identifies discrepancies before close — data that proves directly useful in the local file.
The Audit Trail as Your Best Defence in a TP Audit
The ERP’s audit trail is a decisive advantage when facing a transfer pricing audit. Unlike a retrospectively assembled Excel spreadsheet, the ERP records each transaction with its timestamp, the user who entered or approved it, and the pricing parameters active at the time of the transaction (price list, framework agreement, price version). This traceability directly addresses the requirements of a detailed audit.
ERP data retention obligations are distinct from TP documentation obligations but interlock: in most EU jurisdictions, accounting data must be retained for ten years. Retention rules and ERP archiving are covered in our guide on ERP data archiving and retention obligations.
Key ERP Capabilities for TP Compliance
Intercompany Module and Group Chart of Accounts
The primary prerequisite is a group chart of accounts that explicitly distinguishes intercompany transactions from third-party transactions. Intercompany receivable accounts, intercompany payable accounts, intercompany financial income and intercompany financial charges must be used consistently across all entities. Without this coding, segmenting data for the local file becomes a laborious reconstruction exercise.
The intercompany management module (or intercompany netting) compensates reciprocal payables and receivables between entities, simplifying treasury flows while maintaining the transaction-by-transaction traceability required by the local file. Our article on multi-site and multi-entity ERP management with intercompany consolidation details the architectures available.
Consolidated Reporting and Intercompany Eliminations
Financial consolidation within the ERP — or in a connected consolidation tool (SAP Group Reporting, Oracle Financial Consolidation and Close, IBM Cognos Controller, Tagetik) — produces consolidated financial statements by eliminating intercompany transactions. These same elimination data form the basis for the amounts to be documented in the local file.
Careful consolidation configuration, with automatic elimination rules by intercompany transaction category and entity pair, significantly reduces the effort required to produce the local file. Each automatic elimination is a documented, quantified flow.
Exports to Specialist TP Tools
Leading ERPs offer connectors or standard exports to specialist TP documentation tools. SAP provides extractors to tools such as TP DataHub. Oracle has APIs to ONESOURCE solutions. These connectors automatically export intercompany flows aggregated by category, ready to import into master file or local file templates.
Where your ERP lacks a native connector, a structured extraction via the reporting module (SAP BW/Analytics Cloud, Oracle Analytics Cloud, Dynamics 365 Analytics) in a normalised CSV format is functionally equivalent — provided you maintain an audit trail on the extraction itself.
Automating Simplified Annual Reporting
Most jurisdictions’ simplified annual TP reporting forms require a breakdown of intercompany transactions by category and counterparty entity for amounts exceeding the applicable materiality floor. This extraction is directly available from any well-configured ERP: a query on intercompany sales and purchase journals, filtered by fiscal year and materiality threshold, produces the raw data. ERP vendors such as Sage, Epicor, and Unit4 include regulatory reporting modules that incorporate these declarations into their fiscal close dashboards.
What the ERP Cannot Do Alone
TP documentation is not a simple data extraction exercise. The ERP provides factual data, but documentation also requires capabilities the system cannot produce.
Economic analysis and benchmarking. Justifying that an intercompany services price complies with the arm’s length principle requires comparison with transactions between independent third parties. This comparison relies on comparable databases (Bureau van Dijk Orbis, Compustat, Amadeus) and an economic methodology that only a trained tax analyst can apply.
Narrative drafting. The master file and local file are written documents, not just numerical tables. Describing the functions, risks and assets of each entity (the FAR analysis: Functions, Assets, Risks) requires an understanding of the group’s business models that the ERP cannot synthesise.
Defence in dispute. When a tax administration challenges transfer prices, the taxpayer’s defence involves substantive arguments about methods and comparables — territory where specialist TP firms are indispensable.
For mid-market groups (€150 million to €1 billion in revenue), the most effective approach combines automated ERP data extraction — which dramatically reduces collection time — with a TP firm for economic analysis and narrative drafting. The ERP does not replace fiscal expertise; it makes that expertise accessible at a reasonable cost.
A 90-Day Action Plan to Align Your ERP with TP Requirements
Days 0–30: Diagnostic
- Map material intercompany flows (above the applicable threshold) for the prior fiscal year, using ERP data.
- Identify coding gaps: are intercompany accounts used consistently? Is the counterparty entity recorded on all intercompany journal entries?
- Inventory existing intercompany agreements (service contracts, licences, loans) and verify their registration in the ERP or document management system.
Days 30–60: Configuration
- Complete the group chart of accounts with intercompany sub-accounts where necessary.
- Configure intercompany elimination rules in the consolidation module.
- Create dedicated reporting statements: extraction for simplified TP declarations, intercompany flows by category and entity.
Days 60–90: Documentation and Testing
- Produce a preliminary local file draft for the prior fiscal year, using ERP extractions.
- Identify data gaps requiring additional analytical work (benchmark, FAR narrative).
- Test the response procedure for a formal tax notice: can you produce complete documentation in less than 30 days?
For further reading on multi-entity group management in ERP systems, see our guides on group cash pooling in SAP, Oracle, Sage and NetSuite ERPs, on CSRD compliance and sustainability reporting in ERP systems and on ERP data archiving and retention obligations.
