Chief financial officers (CFOs) now own multi-jurisdiction compliance under the OECD’s Base Erosion and Profit Shifting (BEPS) rules without infrastructure built for it. The Organisation for Economic Co-operation and Development (OECD) requires three documentation tiers, and in 2026 two forces make manual work untenable: Pillar Two enforcement is maturing, and public Country-by-Country Reporting (CbCR) turns confidential filings into public disclosures.
The verdict is simple. Automation is now the only reliable way to produce consistent Master File, Local File, and CbCR output across every entity. The same €750 million revenue threshold triggers CbCR and the Pillar Two global minimum tax at once, so a growing group crosses both lines in one year. Spreadsheets copied per entity drift apart, and mismatched numbers are exactly what tax authorities flag. The fix starts with the OECD transfer pricing documentation rules.
What Is BEPS Documentation and Why Does Arm’s-Length Pricing Matter?
BEPS documentation is the evidence that intercompany prices between related entities meet the arm’s-length principle, the rule that related parties should transact as independent ones would. The OECD/G20 launched the BEPS Project in 2013 and finalized all 15 Actions in October 2015 (OECD BEPS package). Action 13 created the three-tiered documentation standard; Pillar Two is a later, distinct regime.
Action 13 (transfer pricing documentation) and BEPS 2.0 / Pillar Two (a 15% global minimum tax) are related but separate. Action 13 proves your pricing; Pillar Two taxes undertaxed profit. Documentation exists to prove the chosen transfer pricing method and its result. The five OECD methods are the comparable uncontrolled price (CUP), transactional net margin method (TNMM), cost plus, resale price, and profit split. For fundamentals, see Commenda’s guide to what transfer pricing is and how it works.
What Are the BEPS Action 13 Documentation Requirements for 2026?
Action 13 requires three tiers: a Master File covering the whole group, a Local File for each entity’s transactions, and a Country-by-Country Report of per-jurisdiction data. CbCR applies to multinational enterprise (MNE) groups with consolidated revenue of €750 million or more; Master File and Local File thresholds vary by jurisdiction. The standard comes from the OECD Action 13 2015 Final Report.
| Tier | What it contains | Scope trigger | Source |
|---|---|---|---|
| Master File | Group structure, value drivers, intangibles, intercompany financing | Thresholds vary by jurisdiction | OECD Action 13 2015 Final Report |
| Local File | Entity controlled transactions, functional analysis, benchmarking, method selection | Thresholds vary by jurisdiction | OECD Action 13 2015 Final Report |
| CbCR | Per-jurisdiction revenues, profit/loss, tax paid and accrued, employees, tangible assets | €750m consolidated group revenue | OECD CbCR for tax purposes |
The €750 million threshold has applied to fiscal years beginning on or after 1 January 2016, and the OECD estimates it exempts roughly 85-90% of MNE groups while still capturing about 90% of corporate revenue (OECD Action 13 2015 Final Report).
What Goes in the Local File?
The Local File is the core arm’s-length evidence: it documents the entity’s controlled transactions, the functional analysis, the benchmarking study, and the chosen method. Functional analysis maps who performs functions, owns assets, and bears risks. Benchmarking compares the entity’s result against independent comparables. Together they prove the price sits within an arm’s-length range, per the OECD Action 13 2015 Final Report.
For a deeper build-out, see Commenda’s guide to transfer pricing documentation best practices.
Which Intercompany Transactions Must You Document?
Every controlled transaction must be documented, not just goods. That includes services, intellectual property (IP) and intangible transfers, intragroup financing, and cost-sharing arrangements (CSAs). Intangibles carry pricing risk because value is hard to benchmark. Intragroup financing risk is the interest rate and guarantee terms between related entities. A CSA is an agreement where entities share the cost and risk of developing an asset. Each requires its own arm’s-length benchmark.
Why Does BEPS Documentation Matter More in 2026?
The compliance surface expanded from confidential filings to public disclosure and minimum-tax exposure. The EU Public CbCR Directive (2021/2101) applies to financial years starting on or after 22 June 2024, so a calendar-year group’s first public report (FY2025) is due by 31 December 2026 (EUR-Lex). Australia’s broader public regime applies to periods from 1 July 2024, with first reports due around 30 June 2026 (Australian Taxation Office).
Inconsistent documentation across jurisdictions is now a double-taxation risk. When two tax authorities read conflicting files, each can make a competing adjustment, taxing the same profit twice. Strong contemporaneous documentation is the first defense before a Mutual Agreement Procedure (MAP) or dispute resolution. CbCR data is also exchanged widely: 116 jurisdictions are signatories to the OECD’s CbC Multilateral Competent Authority Agreement (list updated 25 June 2026), so mismatches are visible across borders and can dent investor trust.
What Are the Key BEPS and Pillar Two Filing Deadlines in 2026?
Deadlines are jurisdiction-dependent, but the anchors are clear: a calendar-year FY2025 CbCR is due by the end of 2026, and the first GloBE Information Returns land in 2026. There is no single global date. The table below routes the 2026 picture.
| Regime | Who is in scope | Trigger | Typical deadline | Source |
|---|---|---|---|---|
| CbCR filing | MNE groups ≥ €750m | Consolidated revenue | Within 12 months of fiscal year-end (FY2025 due end of 2026) | OECD Action 13 |
| CbCR notification | Same groups | Reporting entity/jurisdiction | Often by fiscal year-end or with the return | OECD Action 13 |
| Master File / Local File | Varies by jurisdiction | Local thresholds | Return-filing date to on-request windows (e.g., 30 days) | OECD Transfer Pricing Guidelines |
| GloBE Information Return | Groups ≥ €750m | Pillar Two scope | 18-month transitional rule; FY2024 due 30 June 2026 | OECD December 2023 Administrative Guidance |
| EU public CbCR | Groups > €750m with EU presence | Two consecutive years | Within 12 months; FY2025 due 31 December 2026 | EU Directive 2021/2101 |
| Australia public CbCR | CbC parents ≥ A$1bn | Global income | Within 12 months; first reports ~30 June 2026 | Australian Taxation Office |
All 27 EU member states have transposed the directive, communicating 98 national implementing measures (EUR-Lex national implementing measures record), and Romania applied it early to financial years from 1 January 2023. Track your own dates with Commenda’s compliance calendar.
How Does Pillar Two Change BEPS Compliance for CFOs?
Pillar Two imposes a 15% global minimum effective tax rate on groups with consolidated revenue of €750 million or more, the same threshold as CbCR. The rules come from the OECD GloBE Model Rules, published 20 December 2021. GloBE stands for Global Anti-Base Erosion. Where an entity’s tax rate falls below 15%, a top-up tax applies.
Three mechanisms collect it: the Income Inclusion Rule (IIR), a parent-level top-up effective in many jurisdictions from 2024; the Undertaxed Profits Rule (UTPR), a backstop generally from 2025; and the Qualified Domestic Minimum Top-up Tax (QDMTT), where a jurisdiction collects its own top-up first. The new filing is the GloBE Information Return (GIR). The strongest link to Action 13 is the transitional CbCR safe harbour for FY2024-2026, which relies directly on qualifying CbCR data, so poor CbCR quality cascades into Pillar Two exposure. As of mid-2026, the US GILTI regime is not treated as a Qualified IIR, which creates UTPR and QDMTT friction for US-parented groups abroad; see Commenda on US corporate filing via Form 1120.
What Does Manual BEPS Compliance Actually Cost?
Manual compliance costs show up as advisor fees per entity, penalty exposure per jurisdiction, and internal hours lost to reconciliation. The scale is real: the OECD’s 2024 CbCR peer review counted 138 jurisdictions reviewed, with over 115 having introduced a domestic CbC filing obligation. Each jurisdiction can mean a separate local advisor bill and a separate deadline.
The deepest problem is version control. Spreadsheets copied per entity drift apart, so the Master File narrative, the Local File numbers, and the CbCR totals stop matching. Those mismatches are exactly what audit selection algorithms flag when authorities compare filings.
| Manual cost driver | Why it bites | Source |
|---|---|---|
| Per-jurisdiction advisor fees | 115+ jurisdictions have a domestic CbC filing obligation | OECD 2024 CbCR peer review |
| Cross-border mismatch detection | CbCR is exchanged among 116 CbC MCAA signatories | OECD CbC MCAA list (25 June 2026) |
| Pillar Two cascade | Transitional CbCR safe harbour (FY2024-2026) relies on CbCR data | OECD December 2023 Administrative Guidance |
| Public disclosure error risk | EU first public report (FY2025) due 31 December 2026 | EU Directive 2021/2101 |
How Do You Automate BEPS Documentation Across Jurisdictions?
Automation pulls trial-balance and transaction data from the enterprise resource planning (ERP) system, maps it to entities and transaction types, applies each jurisdiction’s rules, and generates Master File, Local File, and CbCR output from one reconciled dataset. It ingests intercompany ledgers automatically instead of by manual export, integrates the benchmarking study into the Local File and flags when comparables need a refresh, and produces jurisdiction-specific formats including the CbCR XML schema for automatic exchange.
Automation also handles agreements. A transfer pricing agreement (TPA) is the intercompany contract that documentation must match. An Advance Pricing Agreement (APA) is negotiated certainty agreed in advance with a tax authority. Automation stores these agreements, keeps documentation consistent with the agreed terms, and supports an APA application, but it does not replace one. The EU now mandates an Inline XBRL/XHTML format for public CbC reports from financial years starting 1 January 2025 (European Commission Implementing Regulation 2024/2952), which reinforces why format-aware generation matters. Where entity count drives scope, see Commenda on the difference between a division and a subsidiary.
What Should CFOs Look For in a BEPS Documentation Automation Tool?
Look for a platform that generates all three Action 13 tiers from one dataset, covers every jurisdiction you file in, and keeps a full audit trail. The right tool aligns to the OECD standard, integrates with your ERP, and adapts as Pillar Two and public CbCR mandates evolve. The criteria below map to what 2026 filing actually demands.
| Criterion | Why it matters | Source / note |
|---|---|---|
| OECD Action 13-aligned templates | Three tiers must tell one consistent story | OECD Action 13 2015 Final Report |
| Multi-entity, multi-jurisdiction coverage | 115+ jurisdictions carry CbC obligations | OECD 2024 CbCR peer review |
| ERP integration | Automated data pulls, no manual export | Commenda supports 100+ ERPs, APIs, and custom integrations |
| Audit trails and version control | Timestamped lineage defends filings | Governance requirement |
| Automated validation checks | Catches mismatches before submission | Reduces audit selection risk |
| Jurisdiction-specific formats | CbCR XML and EU Inline XBRL/XHTML | European Commission Implementing Regulation 2024/2952 |
| Compliance calendar and dashboard | Per-entity deadline tracking | Prevents late-filing penalties |
| Pillar Two / GIR and public CbCR adaptability | Safe harbour depends on CbCR data quality | OECD December 2023 Administrative Guidance |
The UK shows why adaptability matters; regimes shift, as Commenda covers in HMRC’s proposed UK transfer pricing overhaul.
How Commenda Automates BEPS Documentation for Global Teams
Commenda’s transfer pricing platform generates Master File, Local File, and CbCR documentation from your ERP data across every jurisdiction you operate in, with timestamped audit trails and per-entity deadline tracking. It stores your transfer pricing agreements, keeps documentation consistent with agreed terms, and feeds qualifying CbCR data into your Pillar Two safe harbour analysis. Compliance becomes certain rather than assumed.
Because Commenda connects to 100+ ERPs, APIs, and custom integrations, your Master File narrative, Local File numbers, and CbCR totals stay reconciled from one dataset. Book a demo to get a free assessment of your 2026 BEPS and Pillar Two documentation exposure.








