Loading...
Loading...
Build a coherent Master File, Local File, and CbCR evidence trail with an annotated source-lineage model, cross-document controls, and a practical local-rules overlay.
Borys Ulanenko
CEO of ArmsLength AI
Continue exploring
Browse the full resource library or contact us if you want recommendations for your specific use case.
A documentation package is useful when a reviewer can move from a conclusion to the underlying facts and numbers without guessing. For example, a statement that an entity is a routine distributor should lead to the relevant agreement, named decision makers, operating records, segmented accounts, method selection, comparable search, calculation, and ledger reconciliation.
OECD Chapter V focuses on three objectives: helping taxpayers assess compliance, giving tax administrations information for risk assessment, and providing information for an audit. Page count is not one of those objectives. The practical goal is a concise, consistent, reproducible account of the material controlled transactions.
Effective transfer pricing documentation connects three components where applicable under local rules: (1) a Master File providing the group-level context, (2) Local Files analysing the local entity's material controlled transactions, and (3) a Country-by-Country Report presenting specified information by tax jurisdiction. A defensible package is timely under local law, internally consistent, fact-specific, and traceable to source evidence.
For specific components, see our deep-dives on Master File best practices, Local File requirements, and CbCR preparation.
Use these levels to decide where remediation effort will have the greatest value. They describe documentation quality, not a promised audit outcome.
| Level | Characteristics | Next control |
|---|---|---|
| Source-backed | Material statements and calculations trace to approved records; cross-document checks are complete | Preserve sign-off, sources, and version history |
| Substantive | Fact-specific analysis is complete but some evidence paths or reconciliations require manual explanation | Close lineage and reconciliation gaps |
| Form-complete | Required headings are present, but parts rely on generic language or disconnected data | Replace boilerplate with entity- and transaction-specific evidence |
| Incomplete | Material transactions, agreements, analysis, financial ties, or local requirements are missing | Triage statutory deadlines and material exposures first |
The target is not an "audit-proof" document. It is a complete record that applies the relevant rules to the facts, exposes its assumptions, and can be reproduced by a reviewer.
OECD paragraph 5.15 notes that a documentation package cannot be expected to anticipate everything a full audit may require. Build a proportionate core file and retain an indexed evidence pack so additional questions can be answered efficiently.
A well-organised file should let an internal reviewer, adviser, or tax authority answer the following questions from the same evidence base.
For each tested transaction, show the path from source system to transaction schedule, segmented profit-and-loss account, tested result, statutory accounts, and any return disclosure. Record every mapping rule and reconciling item.
Connect descriptions of functions, assets, risks, intangibles, and decision rights to identified people, agreements, approvals, operational records, and financial consequences. Replace labels such as "routine" or "limited-risk" with the facts that support them.
Compare the current Master File, Local Files, CbCR, agreements, financial statements, tax returns, and prior-year files. Differences may be legitimate; unexplained differences are the problem. Date-stamp the source used for each document and record why a fact changed.
Retain the method-selection reasoning, tested-party decision, search strategy, screening log, calculation inputs, adjustments, range, and conclusion. The IRS's current documentation FAQs similarly emphasise information symmetry and a clear explanation of comparability adjustments.
Explain anomalies; do not conceal them. Losses, restructurings, intangible transfers, financing changes, unusual margins, and CbCR patterns may have commercial explanations. State the fact, link the evidence, quantify the effect, and explain how it was treated. CbCR is a high-level risk-assessment tool and is not conclusive evidence that transaction prices are or are not arm's length.
BEPS Action 13 established the global standard for transfer pricing documentation. While implementation varies by jurisdiction, the core framework consists of three interconnected documents that together tell one consistent story about your MNE.
| Document | Scope | Purpose | Key Content |
|---|---|---|---|
| Master File | Group | Provide a high-level overview of global operations and policies | Organisational structure, business description, intangibles, financing, APAs and rulings specified in Annex I |
| Local File | Local taxpayer | Analyse material controlled transactions affecting the jurisdiction | Functional and comparability analysis, method selection, agreements, financial data and reconciliation |
| CbCR | Tax jurisdiction | Report the information prescribed in Annex III by jurisdiction | Revenue, profit or loss, tax, capital, earnings, employees, tangible assets, entities, activities, and additional information |
The files should reconcile, but they do not have identical scope or aggregation. Record legitimate differences—such as entity-level versus jurisdiction-level data—in a cross-document mapping instead of forcing artificial agreement.
| Question | Global reference point | Local action |
|---|---|---|
| Master File + Local File | OECD Chapter V recommends the structure; Annexes I and II specify content | Check domestic scope, materiality, timing, filing or availability, language, retention, and exemptions |
| CbCR | Action 13 CbCR guidance uses annual consolidated group revenue of at least EUR 750 million in the immediately preceding fiscal year, or the applicable near-equivalent domestic-currency amount | Confirm the domestic rule, reporting entity, notification, surrogate filing, deadline, exchange relationships, and schema |
| Penalty or protection rules | OECD discusses proportionate documentation obligations and penalties but does not create domestic protection | Check the statute, regulations, and current tax-authority guidance for every filing jurisdiction |
Below a formal threshold: A Master File or Local File may not be legally required, but the taxpayer may still need records supporting return positions, transfer pricing calculations, or another local obligation. Determine that record set from the applicable local rules.
Before finalizing any section of your documentation, apply the 3C Test:
Was this prepared when it claims to be?
Test: Can you show which version existed at each relevant deadline and which source data was available then?
Does this match other documents?
Test: Search for the same term across documents. Does "marketing support" mean the same thing in both your German and US files?
Would an intelligent skeptic believe this?
Test: Can a reviewer follow each key assertion to the facts, analysis, and financial result without relying on an unsupported label?
If any section fails one of these tests, fix it before filing.
The Master File provides a high-level group overview of organisational structure, business operations, intangibles, financing, and transfer pricing policies. Where the framework applies, it supplies context that the Local Files develop at entity and transaction level.
| Pillar | Content | Common Mistakes |
|---|---|---|
| 1. Organizational Structure | Legal and ownership structure, operating-entity locations | Outdated charts; missing reporting-period changes |
| 2. Business Description | Products, supply chain, profit drivers, services | Generic industry boilerplate; no value chain insight |
| 3. Intangibles | Strategy, important intangibles and owners, agreements, policies, transfers | Missing important intangible groups or reporting-period transfers |
| 4. Financial Activities | Treasury, loans, guarantees, cash pools | Ignoring financing entirely; missing policies |
| 5. Financial/Tax Positions | Consolidated statements, APAs, rulings | Missing an APA or ruling that falls within the Annex I scope |
An Annex I-complete Master File covers the required categories. A high-quality Master File also connects those categories: it shows how supply chains, important profit drivers, functions, assets, risks, intangibles, financing, and changes during the year relate to the group's transfer pricing policies.
OECD paragraph 5.18 calls for a high-level overview, not an exhaustive data dump. Use precise cross-references to controlled source documents where they satisfy the requirement, and keep detailed transaction analysis in the Local File.
One controlled core, documented local overlays: A group-wide Master File can reduce inconsistency; HMRC expressly permits a single OECD-compliant group file to be made available to relevant UK entities. Other jurisdictions may require local language, timing, format, or additional information. Control the global narrative centrally, record every local change, and never let translation or an overlay silently alter the underlying facts.
→ Complete guidance: Master File Best Practices: A Complete Guide
The Local File focuses on the local taxpayer and its material controlled transactions. It supplements the Master File with transaction amounts, counterparties, agreements, functional and comparability analysis, method selection, tested-party reasoning where relevant, conclusions, and financial reconciliation described in OECD Annex II.
The following is a working summary of the three Annex II categories, not a substitute for the official Annex or domestic additions.
Section A: Local Entity
Section B: Controlled Transactions (for each material category)
Section C: Financial Information
Use a controlled schedule to define the Local File population before drafting. One row may represent a material category of controlled transactions where that aggregation is appropriate under Annex II and local rules.
| Schedule field | What the reviewer should be able to verify |
|---|---|
| Local entity and period | Exact legal entity, tax jurisdiction, fiscal period, currency, and source ledger |
| Transaction category | Nature of the controlled transaction, commercial context, and reason any transactions are aggregated |
| Counterparties | Legal names, tax jurisdictions, relationship, and amounts paid or received by counterparty jurisdiction |
| Terms and conduct | Applicable agreement version and evidence of functions, assets, risks, decision rights, and implementation |
| Method application | Selected method, tested party where relevant, indicator, comparables, assumptions, adjustments, and conclusion |
| Financial lineage | Source accounts, mapping and allocation rules, segmented result, reconciling items, invoices, and booked adjustments |
| Ownership and status | Source owners, preparer, reviewer, approval date, open exceptions, final version, and retention location |
The schedule is an index and control record, not a substitute for the transaction analysis or the financial information required by Annex II.
The functional analysis is the factual basis for delineating the transaction and informs method selection, tested-party choice where applicable, comparable selection, and the conclusion.
| Element | Weak (Generic) | Strong (Entity-Specific) |
|---|---|---|
| Functions | "Performs marketing and sales" | "Executes campaigns designed by HQ using €2M annual budget; manages 15-person sales team covering DACH region; handles post-sale support with 48-hour SLA" |
| Assets | "Uses typical business assets" | "Operates 10,000 sqm warehouse valued at €8M; utilizes parent's trademark under license; maintains €2M average inventory" |
| Risks | "Bears normal business risks" | "Assumes credit risk on 45-day receivables (bad debt ~1.5%); inventory obsolescence capped at 3% via buy-back clause; no product liability (retained by manufacturer)" |
The figures above are illustrative drafting examples, not benchmarks or facts to reuse. A final file should use the entity's verified records and explain the actual decision process and consequences.
The Specificity Test: Read your functional analysis aloud. If it could describe any company in your industry, it's too generic. Add entity-specific facts: headcount numbers, specific assets, contractual risk allocations, decision-making authority examples.
→ Complete guidance: Local File Best Practices: Building Audit-Ready Documentation
The CbCR is a standardised template containing specified aggregate information by tax jurisdiction and a list of constituent entities and activities. Under OECD paragraph 5.25, it may support high-level transfer pricing and other BEPS risk assessment, but it is not a substitute for transaction-level functional and comparability analysis and is not conclusive evidence that prices are or are not appropriate.
| Table | Content | Preparation control |
|---|---|---|
| Table 1 | Prescribed financial and activity indicators aggregated by tax jurisdiction | Apply one documented source and treatment policy consistently across jurisdictions and years |
| Table 2 | Constituent entities, tax residence, different jurisdiction of organisation where applicable, and main activities | Reconcile to the legal-entity and permanent-establishment population |
| Table 3 | Additional information needed to understand compulsory information | Explain source choices, changes, exceptional items, and other points necessary to understand the data |
Before filing, ask whether patterns in the report require a factual explanation, including:
The presence of a pattern does not establish a transfer pricing error. Trace it to the source data, identify the business or accounting reason, and ensure any explanation agrees with the Master File and relevant Local Files.
Use Table 3 for understanding, not advocacy: Include the brief information necessary to understand the compulsory figures and the basis used to prepare them. Do not assert that legal ownership alone explains intangible returns; any supporting transfer pricing analysis belongs in the relevant documentation and must consider functions, assets, risks, and conduct.
→ Complete guidance: CbCR Preparation Guide: Avoiding Common Errors
The three reporting layers should tell one coherent story at different levels of detail. Supporting evidence makes that story reproducible.
| Statement to support | Master File | Local File | Supporting evidence |
|---|---|---|---|
| The group creates value through identified activities and intangibles | Group structure, important profit drivers, supply chain, intangibles, and financing overview | Local entity's role in that operating model | Organisation charts, process maps, development records, registrations, budgets, and decision records |
| The local entity performs a defined role | High-level functional contribution of important group entities | Detailed functions, assets, risks, transaction flows, and changes from prior years | Agreements, interviews, job responsibilities, approvals, operational records, and work product |
| The selected method is appropriate | Group policy and general pricing approach | Delineated transaction, method selection, tested party where relevant, indicator, comparability analysis, and conclusion | Search strategy, screening log, comparable source documents, calculation, and adjustment support |
| The tested result agrees to the accounts | Consolidated financial statement required by Annex I if otherwise prepared | Local accounts and the allocation schedules required by Annex II | Trial balance, mapping rules, segmented accounts, invoices, adjustment entries, and reconciliation |
| CbCR figures are understandable | Group and entity context | Transaction-level explanations where relevant | CbCR data dictionary, entity mapping, source extracts, currency treatment, consolidation rules, and Table 3 support |
Consider the statement: "The local entity distributes products and does not control strategic market risk."
The Local File should identify the transaction and counterparties, describe the local and group decision process, and explain how those facts inform method selection. A reviewer should be able to move from the statement to:
The label "routine distributor" is not evidence. The documented functions, assets, risks, decision rights, financial capacity, and conduct are the evidence.
Maintain one register that supports both drafting and review:
| Field | Purpose |
|---|---|
| Statement or data point | The exact proposition or number being supported |
| Document and section | Master File, Local File, CbCR field, agreement, or calculation where it appears |
| Authoritative source | System report, contract, interview, official guidance, calculation, or other record |
| Source owner and period | Person accountable for the source and the period it covers |
| Transformation | Mapping, allocation, currency conversion, adjustment, or judgement applied |
| Reviewer and sign-off | Who checked the source, transformation, and conclusion, and when |
| Version and retention location | Approved version, immutable path, retention rule, and access control |
Before approval, compare:
Record an explanation and owner for every legitimate difference. Do not force figures with different scope or aggregation to match without a reconciliation.
Different transaction types require different documentation approaches. Within the OECD framework, the arm's length principle applies across them, but the economically relevant characteristics and supporting evidence differ; domestic adoption and additions still need to be checked.
Intercompany services analysis should address whether an activity was performed, whether it provided economic or commercial value for which an independent enterprise would have paid or performed the activity itself, how the charge was determined, and whether shareholder activities or incidental benefits were excluded under the adopted OECD guidance.
The OECD simplified approach applies a 5% markup to the relevant cost pool for qualifying low-value-adding intra-group services, subject to the conditions and local adoption of the approach. The OECD issued proposed Chapter VII revisions for public consultation in June 2026; those proposals are not final guidance.
Key Documentation:
→ Documentation for Services Transactions
OECD Chapter X applies the Chapter I accurate-delineation framework to financial transactions. The analysis starts with the commercial and financial relations and economically relevant characteristics; it is not limited to pricing the instrument as labelled by the parties.
Key Documentation:
→ Documentation for Financial Transactions: Loans, Guarantees, Cash Pools
Intangibles documentation should identify legal ownership and the parties that perform and control relevant functions, use assets, assume risks, provide funding, and have the financial capacity to assume those risks. The OECD analysis considers development, enhancement, maintenance, protection, and exploitation activities when determining arm's-length compensation; legal ownership alone does not establish entitlement to retain all intangible-related returns.
Key Documentation:
→ Documentation for Intangibles: DEMPE Analysis and Beyond
A restructuring analysis should preserve a before-and-after record: what changed, the business reasons and expected benefits, the options realistically available, what was transferred or terminated, and whether the facts support arm's-length compensation.
Key Documentation:
→ Documentation for Business Restructurings
Agreements record intended terms and are a starting point for transfer pricing delineation. The analysis must also consider actual conduct, and local counsel should determine legal effect and execution requirements.
Key evidence:
→ Intercompany Agreements: Essential Documentation Requirements
Country rules change too often for an undated summary table to be a reliable compliance tool. Maintain a live jurisdiction register beside the global documentation rather than embedding remembered thresholds and deadlines in the narrative.
| Field | Question to answer | Source standard |
|---|---|---|
| Scope | Which entity, group, transaction, revenue, and materiality tests apply? | Current statute, regulations, and tax-authority guidance |
| Required records | Master File, Local File, CbCR, schedule, return form, notification, agreement, or supporting calculations? | Official domestic rule plus OECD Annex reference where adopted |
| Timing | When must each item be prepared, filed, available, or produced on request? | Exact trigger, due date, extension rule, and response period |
| Language and format | Which language, electronic format, schema, signature, or certification is required? | Current filing specification or official administrative guidance |
| Retention | What must be retained, for how long, from which start date, and subject to which holds? | Domestic record-keeping and limitation rules |
| Consequences | Which fixed, daily, transaction-based, adjustment-based, or behaviour-based rules apply? | Current statute and authority guidance; record the provision and effective date |
| Owner and verification | Who checked the rule, from which primary source, and on what date? | Named preparer and reviewer, source URL, effective date, and next review date |
Start with the OECD Transfer Pricing Country Profiles, which were last updated on 22 January 2026, then confirm the position in the relevant domestic law and tax-authority materials. The profiles help compare implementation but do not replace local law.
Official UK example, not a global rule: HMRC's Master File manual and Local File manual state that in-scope UK entities prepare those files under the 2022 OECD Guidelines. HMRC normally expects a requested Master File within 30 days and permits a single OECD-compliant group Master File to be made available to relevant UK entities. Apply those statements only to the UK scope described in the current manuals.
OECD paragraph 5.27 says taxpayers ordinarily should consider whether pricing is appropriate before it is established and confirm the arm's-length nature of financial results at return filing. OECD paragraph 5.29 also recognises that preparation and production timing differs by jurisdiction. "Contemporaneous" therefore cannot be reduced to one universal date.
| Stage | Activity | Controlled output |
|---|---|---|
| Before or when pricing is set | Delineate the transaction, approve the policy, establish agreements and system logic, identify evidence owners | Approved policy, agreement record, pricing configuration, governance decisions |
| During the year | Monitor functions and risks, business changes, results, agreements, and source-data quality | Change log, exception log, interim calculations, remediation decisions |
| At year-end close | Finalise transaction population, amounts, segmentation, adjustments, and reconciliation | Approved data pack and accounting entries |
| Before each local deadline | Complete the required records, local overlay, review, translation, filing or availability step | Signed-off jurisdiction package and proof of filing or availability |
| After filing | Preserve the approved version, sources, validation output, correspondence, and corrections | Immutable archive, retention metadata, correction log |
→ Complete timing guidance: Contemporaneous Documentation: When Timing Matters Most
These weaknesses make the analysis harder to reproduce and may prevent the file from meeting local requirements.
Score each statement 0-2 (0 = No, 1 = Partially, 2 = Yes):
Contemporaneity
Consistency
Substance
Completeness
Score interpretation:
→ Complete guidance with remediation roadmap: 10 Common Documentation Weaknesses (and How to Fix Them)
OECD paragraphs 5.18 and 5.28 support proportionate documentation: the Master File is a high-level overview, and taxpayers should not face disproportionate cost and burden. Include what the rules and analysis require, then use precise cross-references to the evidence pack.
Results, functions, and market conditions can change. Record the change, source, period, and effect. Consistency means the documents use the same facts or explain legitimate differences; it does not mean every entity or year should look identical.
For a loss, restructuring, intangible transfer, financing change, or unusual CbCR pattern, state the fact, identify the decision and commercial context, quantify the effect, and link the supporting records. Do not treat the explanation as a substitute for the required method and comparability analysis.
Transfer pricing documentation records how a taxpayer identified and delineated controlled transactions, selected and applied a method, and connected the conclusion to the facts and financial data. OECD Chapter V describes three tiers: a Master File, Local File, and Country-by-Country Report. Domestic law determines which tiers and supporting records a taxpayer must prepare.
It depends on the jurisdiction, entity, group size, transaction type, amount, and reporting period. A country may adopt all or part of the OECD structure, add its own schedules, or apply separate record-keeping rules. Check the current domestic law and authority guidance using a source-dated jurisdiction overlay; the OECD country profiles are a useful starting point.
The Master File provides high-level group context: organisational structure, businesses, intangibles, intercompany financial activities, and financial and tax positions specified in OECD Annex I. The Local File focuses on the local taxpayer and its material controlled transactions under Annex II. The files should use consistent facts, with documented reconciliations for differences in scope, period, or aggregation.
Review the package for each reporting period and update every fact, amount, source, and conclusion affected by change. OECD paragraph 5.37 recommends annual review and update of the three-tier documentation. Paragraph 5.38 says tax administrations may permit database searches supporting part of the Local File to be updated every three years where operating conditions remain unchanged, while comparable financial data should be updated annually. Local law or changed facts may require a different cycle.
The consequences are domestic-law questions. Depending on the jurisdiction, missing or late records can affect fixed or tax-related penalties, evidentiary positions, response obligations, and access to a documentation-based defence. It also makes the pricing harder to reproduce. Identify the exact provision, effective date, and consequence in the jurisdiction register rather than applying another country's rule by analogy.
Timing varies by jurisdiction and by document. OECD paragraph 5.29 expressly recognises different practices, including completion by return filing or by the start of an audit. Work backwards from each local preparation, filing, availability, notification, and production deadline. Separately preserve the information used when pricing was established and when the financial result was confirmed.
Country-by-Country Reporting (CbCR) is the Action 13 template with specified aggregate information by tax jurisdiction and constituent-entity information. The global standard uses annual consolidated group revenue of at least EUR 750 million in the immediately preceding fiscal year, or the applicable near-equivalent domestic-currency amount, but domestic rules determine the reporting entity, notifications, surrogate filing, deadline, exchange, and format. Under OECD paragraph 5.25, CbCR supports high-level risk assessment and is not conclusive transaction-pricing evidence.
Detailed enough that an independent reviewer understands how the delineated transaction and method connect to the result. Specify which functions each party performs, which assets it uses, which risks it assumes, who makes the relevant risk-control decisions, and how those facts inform the analysis. Where a tested party is used, explain its selection and tested result. Use verified entity-specific evidence—such as roles, approvals, assets, transaction flows, and financial consequences—rather than generic labels.
Possibly. OECD paragraph 5.38 says tax administrations may permit a three-year database-search refresh where operating conditions are unchanged, while comparable financial data should be updated annually. Before rolling a study forward, confirm that the transaction, tested party, method, indicator, search strategy, independence, comparability, data availability, and local requirements remain valid. Record the review and run a new search when a material change affects reliability.
Penalties vary by jurisdiction, reporting period, conduct, type of failure, and amount at issue. OECD paragraphs 5.40-5.43 discuss fair, proportionate administration but do not prescribe domestic penalty amounts. Use current primary legislation and tax-authority guidance to record the applicable fixed, daily, transaction-based, adjustment-based, or behaviour-based consequences.
Include a dedicated loss analysis section that tests why the entity incurred losses and whether the controlled transaction remained arm's length. Preserve evidence for external factors, such as market conditions, and internal factors, such as startup activity, restructuring, capacity utilisation, or unusual costs. Analyse the duration and allocation of losses, the parties' functions and risks, the tested party selection, and whether reliable comparables experienced similar conditions. A loss does not by itself prove that pricing was or was not arm's length; the conclusion should follow from the accurately delineated transaction and the evidence.
Determine whether the difference is an error or a legitimate difference in scope, period, aggregation, or level of detail. Correct errors through the controlled process; reconcile legitimate differences in the evidence-lineage register. A group-level statement should not be copied into a Local File if the local facts differ.
OECD Annex II calls for copies of all material intercompany agreements concluded by the local entity, and Chapter I treats written terms as the starting point for delineation. Domestic law determines whether a written contract is required and when. For transfer pricing, map each material transaction to the agreement or other evidence of terms, then test those terms against actual conduct.
There is no OECD page-count rule. Include the Annex II and local-law content needed for the entity's material transactions, use cross-references where appropriate, and keep the evidence pack indexed. Complexity, materiality, transaction types, and local additions determine length.
The exact legal meaning depends on the jurisdiction. As an operating principle, preserve what was known when prices were set, monitor implementation, and finalise the required analysis by the applicable local deadline. OECD paragraph 5.27 distinguishes considering the pricing before it is established from confirming the financial result at return filing.
OECD paragraph 5.25 permits CbCR information to support high-level transfer pricing and other BEPS risk assessment and, where appropriate, economic and statistical analysis. It should not substitute for detailed functional and comparability analysis or support formulary adjustments by itself. Reconcile CbCR sources and aggregation to the other files and explain data needed to understand the compulsory information in Table 3.
Following OECD Chapter X, loan documentation should address: (1) accurate delineation—including whether purported debt should be regarded as debt and in what amount; (2) credit analysis—the borrower's creditworthiness, including relevant group-membership effects; (3) arm's length conditions—amount, interest rate, tenor, currency, repayment, covenants, security, and other economically relevant features; and (4) commercial rationale and capacity—why the parties entered the arrangement and how repayment is expected. Document the pricing method and evidence, and reconcile the agreement to funding flows, accruals, payments, and subsequent conduct.
Year-end drafting is faster and more reliable when evidence is captured as the transaction operates. Assign owners for agreements, functional facts, financial mappings, comparable data, jurisdiction rules, and review. Monitor material changes during the year, record decisions when they occur, and preserve the sources used for pricing and filing.
The final package should be an output of those controls: a clear account of the transaction, the analysis applied, the result booked, and the evidence retained. That is more useful than reconstructing the story after people, systems, or facts have changed.
Ready to build a source-backed documentation workflow? Explore our transfer pricing documentation software, see TP/OS, or talk to us.