Quick Answer: How Do You Implement a Reliable Master File?
Build one controlled group-level narrative around the five categories in OECD Annex I, then link every material statement to an approved source and owner. Use an annual change review, reconcile the narrative to Local Files and CbCR, record local overlays, and release one approved version per reporting period.
OECD paragraph 5.18 says the Master File provides a high-level view of the group's global operations and policies and is not intended to require exhaustive listings of minutiae. It also says information is important when omitting it would affect the reliability of transfer pricing outcomes. The implementation challenge is therefore controlled selection, traceability, and consistency—not page count.
This page focuses on that operating model. For the three-tier framework and annotated Master File/Local File/CbCR evidence trace, use the Transfer Pricing Documentation Guide.
Put the Master File Requirements into an Operating Model
The OECD BEPS Action 13 framework includes the Master File as one of three tiers of transfer pricing documentation, alongside Local Files and Country-by-Country Reports. The work on this page starts after the group has identified the applicable content: assigning owners, collecting sources, controlling changes, reconciling other files, and releasing jurisdiction-ready versions.
Framework and Local Adoption
OECD Chapter V recommends the three-tier structure, and Annex I specifies Master File content. Domestic law determines who is in scope, which thresholds and materiality rules apply, when the file must be prepared or produced, the permitted language and format, retention, and consequences.
Maintain a jurisdiction register with the following fields:
| Field | Control to maintain |
|---|
| Scope test | Entity, group, revenue, transaction, period, exemption, and the exact domestic provision |
| Deliverable | Master File, domestic supplement, notification, filing, translation, certification, or on-request copy |
| Timing | Preparation, filing, availability, production, and extension dates with trigger events |
| Format and language | Portal, file type, schema, signature, language, and translation rules |
| Primary source | Current statute, regulation, and tax-authority guidance URL with effective date |
| Governance | Preparer, local reviewer, verification date, next review date, and approved overlay version |
The OECD Transfer Pricing Country Profiles, last updated on 22 January 2026, are a useful comparison point. Confirm every requirement in current domestic sources before relying on it.
NoteOfficial UK example, limited to the UK rule: HMRC states that an in-scope relevant person prepares the Master File in accordance with the 2022 OECD Guidelines, normally provides it within 30 days of an information notice, and may rely on a single OECD-compliant group Master File made available to relevant UK entities. Other jurisdictions may take a different approach.
Section-by-Section Implementation Notes
OECD Annex I to Chapter V specifies five required content sections. Each serves a distinct purpose in helping tax authorities understand the MNE's global operations.
Implementation Map
Assign an accountable owner, source set, and reviewer test before drafting each section.
| Annex I category | Typical source owners | Core source records | Reviewer test |
|---|
| Organisational structure | Legal, company secretariat, tax | Legal-entity register, ownership records, approved organisation chart | Do names, ownership, and locations agree with the reporting-period entity population? |
| Business description | Business-unit leaders, operations, finance, tax | Product and service data, supply-chain maps, management reporting, service arrangements, restructuring records | Can the narrative identify important profit drivers, major supply chains, markets, services, value contributions, and in-year changes? |
| Intangibles | IP legal, R&D, product, finance, tax | IP register, R&D organisation, licences, cost contribution arrangements, transfer records, policy | Are important intangibles, legal owners, agreements, strategy, policies, and transfers complete and mutually consistent? |
| Financial activities | Treasury, finance, tax | External facilities, treasury structure, cash-pool and guarantee records, intercompany financing policy | Does the overview identify how the group is financed, central financing entities, and group pricing policies? |
| Financial and tax positions | Group reporting, tax, legal | Consolidated statement if otherwise prepared, APA and ruling register | Does the package contain exactly the statement and list required by Annex I for the period? |
Pillar 1: Organizational Structure
OECD Requirement: A chart showing the MNE's legal and ownership structure, including the geographic location of operating entities.
What to Include:
- Legal and ownership structure of the group and geographic location of operating entities
Recommended (Best Practice):
- Show ownership percentages and intermediate holding companies where they help make the legal and ownership structure clear
- Identification of entities that engage in material intercompany transactions (not explicitly required by OECD Annex I, but helpful context)
Best Practices:
- Use a clear, multi-level organizational chart
- Show ownership links with percentages
- Indicate if entities are dormant or purely passive
- Capture acquisitions, mergers, and divestitures in the change register when they occur and reflect them in the applicable reporting-period version
Avoid:
- Applying an undocumented materiality filter that makes the ownership chain unclear
- Omitting an entity needed to understand legal ownership or the geographic location of operations
- Using a chart that does not reflect the reporting period
Pillar 2: Description of the MNE's Business
OECD Requirement: A general written description of the group's business, including important profit drivers, the supply chain for major products/services, key service arrangements, main geographic markets, and a brief functional analysis.
What to Include:
- Supply chain for the five largest products or service offerings by turnover, plus any other offering representing more than 5% of group turnover
- Key profit drivers (technology, brand, scale, market access)
- Supply chain flow from sourcing to customer
- Important intra-group service arrangements and pricing policies
- Main geographic markets
- Brief functional analysis of each major entity's contributions
- Significant restructurings, acquisitions, or divestitures during the year
Best Practices:
- Use supply-chain diagrams for clarity
- Describe what makes your group's operations unique—not generic industry boilerplate
- Connect profit drivers to where functions are performed
- Explain how value is created across the group
WarningReviewer test: Could this business description belong to an unrelated group in the same industry? If so, replace generic language with the group's actual profit drivers, supply chains, service arrangements, markets, important functional contributions, and in-year changes required by Annex I.
Pillar 3: Intangibles
OECD Requirement: A description of the group's strategy for developing, owning, and exploiting intangibles; a list of important intangibles and their legal owners; key intangibles-related agreements; TP policies for R&D and intangibles; and any significant intangible transfers during the year.
What to Include:
- Overall intangibles strategy and R&D locations
- List of material intangibles (patents, trademarks, software, know-how)
- Legal ownership of each intangible
- Key agreements: cost contribution arrangements, licence agreements, and other important intangibles-related arrangements
- Transfer pricing policies for royalties and R&D activities
- Any transfers of intangibles during the year (entities involved, consideration paid)
Best Practices:
- Focus on intangibles or groups of intangibles that are important for transfer pricing purposes
- Describe R&D organization clearly (e.g., "Research labs in Germany develop formulations; US holds resulting patents")
- Summarize key license terms without proprietary technical details
- Disclose intangible transfers with compensation terms
Avoid:
- Omitting an intangible or group of intangibles that is important for transfer pricing purposes
- Listing every minor trademark or low-value IP
Recommended: Distinguish legal ownership from economic contributions where relevant (not explicitly required by Annex I, but supports DEMPE analysis in the Local File)
Pillar 4: Intercompany Financial Activities
OECD Requirement: A general description of how the group is financed, including important financing arrangements with unrelated lenders; identification of central financing entities; and general transfer pricing policies for financing arrangements between associated enterprises.
What to Include:
- General description of how the group is financed, including important arrangements with unrelated lenders
- Group members performing a central financing function, including where they are organised and effectively managed
- General transfer pricing policies for financing arrangements between associated enterprises
Best Practices:
- Describe the financing structure at a high level
- Identify the entity responsible for external debt
- Explain material cash-pool and guarantee structures where they are part of the group's financing model
- State the group's transfer pricing policies for financing arrangements clearly, including the method and material pricing inputs where appropriate at Master File level
Avoid:
- Ignoring financing structures entirely
- Listing every loan contract or repayment schedule (that's Local File detail)
- Excessive derivative or hedging details unless central to the TP structure
Pillar 5: Financial and Tax Positions
OECD Requirement: Consolidated financial statements (if otherwise prepared) and a list of existing unilateral APAs and other tax rulings relating to the allocation of income among jurisdictions.
What to Include:
- The annual consolidated financial statement for the fiscal year, if otherwise prepared for financial reporting, regulatory, internal management, tax, or other purposes
- Unilateral APAs and tax rulings affecting income allocation (OECD minimum requirement)
- Years covered and general scope of each ruling
Best Practices:
- Attach published consolidated statements if available
- List the required APAs and rulings with enough information to provide the brief description required by Annex I, consistent with applicable confidentiality rules
WarningAnnex I requirement: Include the annual consolidated financial statement described above and a list with brief descriptions of existing unilateral APAs and other tax rulings relating to the allocation of income among jurisdictions. Check local rules for any additional scope or consequence.
Master File vs. Local File: Getting the Split Right
The Master File and Local File are complementary documents with distinct purposes:
| Aspect | Master File | Local File |
|---|
| Scope | Global, group-wide | Entity-specific |
| Detail Level | High-level overview | Granular analysis |
| Economic analysis | Group policies and high-level context | Method selection and supporting analysis for each material transaction category, including comparables where relevant |
| Functional Analysis | Brief summary per entity | Detailed FAR analysis |
| Transactions | Overview of transaction types | Analysis for each material category of controlled transactions, with appropriate aggregation where reliable |
| Financial Data | Consolidated financial statement if otherwise prepared | Annual local entity accounts plus allocation schedules tying method data to those accounts |
Key principle: Do not duplicate content unnecessarily. The Master File provides group context; the Local File applies the analysis to the local taxpayer's material controlled transactions. OECD Annex II permits a cross-reference where the local functional analysis duplicates Master File information.
Consistency is critical: The group-level description and local analysis should use the same underlying facts or explain legitimate differences in scope, period, and detail. Record those differences in the evidence register.
Common Master File Mistakes
Mistake 1: Boilerplate/Generic Content
Copy-pasting an industry description does not provide the group-specific profit drivers, supply chains, services, markets, functional contributions, and changes called for by Annex I.
Fix: Describe what your group actually does, where value is created, and how entities differ from each other.
Mistake 2: Inconsistency with Local Files
Unexplained discrepancies between Master File and Local File narratives, figures, or characterisations make the group story difficult to reconcile. Some differences are legitimate because the files have different scope and detail; those differences should be documented.
Fix: Maintain a central coordination process. The global tax team should review both documents for alignment before finalization.
Mistake 3: Missing Intangibles Disclosure
Annex I requires a list of intangibles or groups of intangibles important for transfer pricing and their legal owners, plus important related agreements, policies, strategy, and in-year transfers.
Fix: Reconcile the Master File population to the controlled IP register and have IP legal, R&D, product, finance, and tax review the result.
Using last year's data, outdated organisational charts, or stale business descriptions can make the reporting-period narrative inaccurate or incomplete.
Fix: Establish an annual review process and an event-driven change register so material changes are reflected in the applicable reporting-period version.
Mistake 5: Missing APAs and Tax Rulings
Annex I requires a list and brief description of existing unilateral APAs and other tax rulings relating to the allocation of income among jurisdictions.
Fix: Maintain a global APA and ruling register with status, period, jurisdiction, subject, owner, source, and the decision on whether it falls within Annex I or a local addition.
Mistake 6: Excessive Operational Detail
Including step-by-step manufacturing processes, detailed balance-sheet line items, or granular product specifications can obscure the high-level information the Master File is intended to provide.
Fix: Keep the Master File at "blueprint" level. Detailed analysis belongs in Local Files.
Build the Master File Evidence Register
The register is the working paper behind the narrative. It separates sourced facts from drafting judgement and makes annual updates faster.
| Field | Example of what belongs there |
|---|
| Annex I requirement | Exact category and bullet addressed |
| Master File statement | The proposition, figure, list, or diagram supported |
| Primary internal source | Legal register, management report, agreement, policy, consolidated statement, APA/ruling register |
| Source owner and period | Accountable function, named owner, fiscal period, extraction or approval date |
| Transformation or judgement | Materiality decision, aggregation, currency conversion, mapping, summary, or cross-reference |
| Cross-document use | Related Local Files, CbCR fields, agreements, policy, or prior-year statement |
| Reviewer result | Agreed, corrected, locally supplemented, or not applicable, with rationale |
| Approved version | Source version, Master File release, repository path, and retention status |
Minimum Reviewer Tests
- Completeness: Every Annex I bullet and applicable local addition maps to content or a documented not-applicable conclusion.
- Existence: Every important entity, agreement, intangible, financing arrangement, APA, ruling, and in-year change maps to an approved source.
- Period: Charts, lists, narrative, policies, and financial statements cover the reporting period.
- Consistency: Names, roles, transaction descriptions, changes, and financial facts reconcile to Local Files and CbCR, with explained scope differences.
- Presentation: Cross-references are precise, attachments are accessible, and confidential material is handled under applicable safeguards.
Control Translation and Local Overlays
Do not assume one language is accepted everywhere. Record the current domestic rule, source, required language, permitted alternatives, translation deadline, and reviewer in the jurisdiction register.
Where a translation or local supplement is required:
- freeze the approved global source version;
- identify terms that must remain consistent across documents;
- translate from that version and retain the translation record;
- review legal names, tax terminology, figures, tables, and cross-references;
- record every local addition separately from the global core; and
- link the local release back to the exact global version.
This helps prevent a translated or locally supplemented file from becoming an uncontrolled alternative narrative.
Annual Update vs. Full Refresh: A Decision Framework
OECD paragraph 5.30 recommends reviewing and, if necessary, updating the Master File by the ultimate parent's tax-return due date. Paragraph 5.37 also recommends annual review and update. Domestic law determines the enforceable deadline. A stable group may not need a complete rewrite, but it still needs a documented annual review.
Annual Update (Routine)
When: Business is stable, no material changes
What to update:
- Supply the current-period consolidated financial statement if otherwise prepared
- Confirm each Annex I population and narrative against current sources
- Update APA and ruling status and every time-sensitive reference
- Record a no-change conclusion, evidence considered, owner, and review date for stable sections
Expanded Update Triggers
Events that should trigger reassessment of affected sections and connected documents:
- Material acquisition or divestiture
- Business restructuring (model changes, function transfers)
- Significant intangible transfers
- New APAs or rulings
- Major market entry or exit
- Changes to intercompany financing structure
TipChange control: A material change can affect several sections and Local Files. Record the event, effective date, source, affected statements, jurisdictions, owner, reviewer, and release decision in one change register.
One Controlled Core, Traceable Local Releases
Use one approved global core where the domestic rules permit it. HMRC expressly accepts a single OECD-compliant group Master File made available to relevant UK entities, but that UK position is not a universal rule.
Each release should have a manifest:
| Manifest field | Purpose |
|---|
| Global version | Unique identifier, fiscal period, approval date, and content hash or immutable repository version |
| Jurisdiction and entity population | Who relies on the release and for which period |
| Local overlay | Additional content, translation, format, and the domestic source requiring it |
| Differences from core | Exact section, reason, approver, and confirmation that underlying group facts were not silently changed |
| Delivery status | Prepared, translated, filed, available, requested, submitted, corrected, or superseded |
| Retention | Final package location, access, retention rule, and hold status |
This structure lets the group correct one fact centrally while preserving what each jurisdiction received and when.
Master File Preparation Timeline
Build the schedule backwards from the earliest applicable domestic deadline. The dates below are relative because filing, availability, production, and translation requirements differ.
Relative Workflow
| Stage | Activities | Exit evidence |
|---|
| Scope and plan | Confirm entity population, jurisdiction register, earliest deadline, Annex I checklist, owners, reviewers, and release plan | Approved scope, RACI, due-date register, and data request |
| Collect and change-review | Compare prior-year content with legal, business, IP, treasury, tax, and financial changes | Completed change register and source population |
| Draft and evidence-link | Update the five categories and attach each material statement to the evidence register | Complete draft with no unsupported material statements |
| Reconcile | Compare Local Files, CbCR, agreements, policies, consolidated data, and prior releases | Resolved consistency log and documented legitimate differences |
| Approve and localise | Complete technical, tax, legal, business-owner, translation, and local-overlay reviews as applicable | Approved global core and jurisdiction release manifests |
| Deliver and retain | File, make available, or submit on request; archive final files and proof | Delivery evidence, immutable archive, retention and hold metadata |
Coordination Best Practices
Assign central control: Name one function to control the global narrative, sources, versions, and release manifest. Local teams remain responsible for confirming their facts and domestic requirements.
Use standardized templates: Provide subsidiaries with clear data request templates specifying exactly what information is needed and in what format.
Set a risk-based review buffer: Base it on group complexity, source availability, translation, local review, governance, and the earliest legal deadline.
Establish escalation paths: Define who resolves conflicts between subsidiary characterizations and central narrative.
TipUse event-driven updates: Do not wait for year-end to collect evidence of acquisitions, divestitures, restructurings, important intangible transfers, financing changes, or new APAs and rulings.
Common Timeline Failures
- Waiting for final financial data: Continue source collection and narrative review while relevant financial statements and reconciliations are being finalised; identify which approvals depend on final figures.
- Treating translation as formatting: Legal names, tax terms, figures, tables, and cross-references require review against the approved source version.
- Last-minute data requests: Late requests reduce the time available for owner validation, reconciliation, and correction.
Record Domestic Consequences Precisely
OECD paragraphs 5.40-5.43 discuss fair and proportionate administration of documentation-related penalties, but the OECD Guidelines do not create domestic penalty amounts or documentation defences. Those consequences depend on local law, the reporting period, the type and timing of the failure, taxpayer conduct, and sometimes the amount at issue.
For each jurisdiction, record:
| Field | Detail |
|---|
| Failure covered | Non-preparation, late filing, late production, incomplete content, incorrect information, format, language, or retention |
| Consequence | Fixed, daily, transaction-based, adjustment-based, behaviour-based, evidentiary, or other domestic effect |
| Legal source | Exact statute, regulation, official guidance, and effective date |
| Cure or correction | Extension, correction, voluntary disclosure, reasonable-cause, or other process if available |
| Owner and deadline | Entity, accountable owner, reviewer, action date, and status |
WarningDo not copy a penalty statement from another jurisdiction or an earlier year. Confirm the current primary source and obtain local advice for the facts at hand.
Annotated Master File Review Example
This example shows how to review a section without inventing facts or duplicating Local File analysis.
Example Statement: Important Supply Chain
Illustrative statement: The group sources specified inputs, manufactures the identified product families in named locations, and distributes them through identified regional channels. The principal business profit drivers are the listed capabilities and market relationships.
| Annotation | Reviewer action |
|---|
| Annex I coverage | Confirm the description covers the five largest product or service offerings by turnover plus any other offering above 5% of group turnover, main geographic markets, important profit drivers, and the relevant value-creation contributions |
| Source evidence | Link product-revenue report, approved supply-chain map, management reporting, service arrangements, entity register, and business-owner confirmation |
| Period check | Confirm product rankings, locations, flows, and markets for the reporting fiscal year |
| Local File boundary | Keep transaction amounts, detailed functional and comparability analysis, method application, and local financial reconciliation in the relevant Local Files |
| CbCR consistency | Compare entity population and main business activities; document aggregation or classification differences |
| Change test | Identify acquisitions, divestitures, restructurings, market entries or exits, new product lines, and important service changes |
| Approval | Obtain business-owner, finance, legal-entity, and transfer-pricing review and record the source versions used |
Example Change: Intangible Transfer During the Year
An important transfer should update more than the intangibles list. The change record should identify:
- the interests transferred, entities, jurisdictions, and compensation specified by Annex I, with the transaction date recorded as a practical change-control field;
- related legal agreements and the approved source for legal ownership;
- changes to development, ownership, exploitation, management, or R&D locations;
- effects on business description, functional contributions, financing, and policies;
- affected Local Files, agreements, CbCR classifications, APAs, rulings, and local overlays; and
- reviewers, approvals, release versions, and retained evidence.
The Master File remains high-level. Valuation, detailed delineation, method application, and local financial effects belong in the relevant transaction documentation.
Documentation Guides:
Transfer Pricing Certainty:
Benchmarking Resources:
Glossary:
This article is based on guidance from the OECD Transfer Pricing Guidelines (2022):
→ Search the full OECD Guidelines
Frequently Asked Questions
Is the Master File legally required for all MNEs?
No. OECD Chapter V recommends the framework, but domestic law determines scope. Test every relevant entity and period against the current local group, revenue, transaction, materiality, and exemption rules.
What revenue thresholds trigger Master File requirements?
There is no single Master File threshold. A domestic rule may use consolidated group revenue, entity revenue, controlled-transaction amounts, CbCR scope, or another test. Record the exact current provision, currency, measurement period, entity population, and effective date in the jurisdiction register.
How detailed should the Master File be?
OECD paragraph 5.18 calls for a high-level overview and says information is important if its omission would affect the reliability of transfer pricing outcomes. There is no OECD page-count rule. Cover every Annex I requirement with enough group-specific context to be useful, then cross-reference approved documents where permitted and keep local transaction detail in the Local File.
Can I use an English Master File in all jurisdictions?
Not necessarily. Check the domestic language and translation rules for each entity and period. Where a translation is required, link it to the approved global version, review tax terminology, legal names, figures, tables, and cross-references, and record local additions separately.
How often must the Master File be updated?
OECD paragraph 5.30 recommends review and, where necessary, update by the ultimate parent's tax-return due date; paragraph 5.37 recommends annual review and update. Domestic law sets the enforceable deadline. Even when a section is stable, retain the sources reviewed and the dated no-change conclusion; update the current-period consolidated financial statement required by Annex I if it is otherwise prepared.
Determine whether the difference is an error or follows from scope, period, aggregation, or level of detail. Correct errors through change control and reconcile legitimate differences in the evidence register. Do not force a Local File to repeat a group-level characterisation when the local facts differ.
Who should prepare the Master File?
Assign one accountable global owner for scope, sources, versioning, and release. Legal, business, R&D/IP, treasury, finance, local tax, and translation owners should validate their inputs. The appropriate final approver depends on the group's governance and domestic requirements.
Which APAs and rulings must be disclosed?
OECD Annex I requires a list and brief description of the group's existing unilateral APAs and other tax rulings relating to the allocation of income among jurisdictions. Local rules may add to that scope. Use a controlled register to document status, period, jurisdiction, subject, source, confidentiality handling, and the inclusion decision.
Can I use the same Master File for all group entities worldwide?
Often, but not automatically. HMRC expressly permits a single OECD-compliant group file for relevant UK entities. For every other jurisdiction, check domestic content, language, format, timing, and filing rules. Use one controlled core where permitted and create traceable local overlays rather than uncontrolled alternative versions.
What are the penalties for missing or inadequate Master Files?
Consequences vary by jurisdiction, period, type and timing of failure, conduct, and amount at issue. OECD paragraphs 5.40-5.43 do not prescribe domestic amounts. Record the exact current statute, regulation, authority guidance, effective date, consequence, and any correction process in the jurisdiction register.
Ready to put the evidence register and release workflow into practice? Explore TP/OS or talk to us.
Borys UlanenkoCEO of ArmsLength AI
