Quick Answer: What Makes a Strong Local File?
A strong Local File demonstrates arm's length compliance through clear transaction descriptions, thorough functional analysis, defensible comparability analysis, and well-documented benchmarking results. Best practices include: addressing each material transaction type separately, linking the analysis to Master File context, ensuring financial segmentation supports the economic analysis, and preparing documentation contemporaneously for penalty protection.
The Local File is the most detailed element of the OECD's three-tiered documentation framework. While the Master File provides a global overview and the CbCR delivers financial data by jurisdiction, the Local File zooms in on the local entity's specific related-party dealings to prove they are priced at arm's length.
What Must the Local File Contain?
OECD Annex II to Chapter V prescribes the required Local File contents, organized into three main sections:
Section A: Local Entity Overview
| Required Content | Description |
|---|
| Management Structure | Local organization chart and description of reporting relationships |
| Business Description | Detailed description of the local entity's business and strategy |
| Business Restructurings | Any restructurings or intangible transfers affecting the entity in current or prior year |
| Key Competitors | Identification of main competitors (typically 3-5 in practice) |
Section B: Controlled Transactions
For each material category of controlled transactions:
| Required Content | Description |
|---|
| Transaction Description | Nature, context, and commercial rationale for each transaction type |
| Amounts | Intra-group payments and receipts broken down by counterparty jurisdiction |
| Related Parties | Identification of affiliated entities involved and their relationship |
| Agreements | Copies of material intercompany contracts |
| Functional Analysis | Functions, assets, risks of each party; changes from prior years |
| Method Selection | Transfer pricing method and why it's most appropriate |
| Tested Party | If applicable, identification and justification |
| Comparables | List of comparable transactions/companies with financial data |
| Adjustments | Any comparability adjustments performed |
| Conclusion | Statement that transactions were arm's length |
| Required Content | Description |
|---|
| Financial Statements | Annual accounts (audited if available) |
| Reconciliation Schedules | How financial data used in analysis ties to statements |
| Comparables Data | Summary of comparable company financial information and sources |
NoteOECD Guidance (¶5.22): The Local File should contain "more detailed information relating to specific intercompany transactions" and help ensure that the taxpayer has "complied with the arm's length principle in its material transfer pricing positions affecting a specific jurisdiction."
Determining Material Transactions
Not every related-party transaction requires full documentation. The Local File should focus on material categories of transactions—but materiality is both quantitative and qualitative.
Quantitative Materiality: Jurisdiction Thresholds
| Jurisdiction | Threshold for Documentation Relief | Notes |
|---|
| Germany | ≤€6M goods, ≤€600K other transactions | Above thresholds: full documentation mandatory |
| UK | £1M aggregate value per category | HMRC de minimis; intangibles, profit splits always material |
| India | Rule 10D exemption up to ₹1 crore (₹10M) | Above threshold: prescribed documentation required |
| Netherlands | Group revenue ≥€50M triggers Master/Local File | TP support expected regardless; formal file above threshold |
| Australia | Simplified record-keeping for less than AUD 2M dealings | PCG 2017/2 options for low-risk scenarios |
| US | No explicit threshold | Focus on transactions with significant tax effect |
| China | Tangible assets >CNY 200M; financial/intangibles >CNY 100M; other >CNY 40M | Local File completed by June 30 following year |
Qualitative Materiality: Always Material by Nature
Some transactions are inherently material regardless of amount:
- Intangibles transfers or licensing (patents, trademarks, know-how)
- Business restructurings (function/asset/risk transfers)
- Cost contribution arrangements
- Hard-to-value intangibles (HTVI)
- Financial transactions (large intercompany loans, guarantees)
- Profit splits (both parties have unique contributions)
WarningDocumentation Strategy: Even when excluding small transactions, list them in a "minor transactions not analyzed" section with amounts and brief justification. This demonstrates nothing was hidden and shows the preparer considered all related-party dealings.
Transaction-by-Transaction Analysis
Each material controlled transaction should have its own analysis section. Don't aggregate dissimilar transactions—purchase of goods is different from royalty payments which is different from management fees.
How to Structure Each Transaction Analysis
For each transaction category, include:
-
Description and Commercial Context
- What is being transferred/provided?
- Why does the transaction occur?
- How does it fit into the value chain?
-
Amounts and Counterparties
- Total payments/receipts for the year
- Breakdown by jurisdiction if multiple affiliates
-
Functional Analysis
- Functions performed by each party
- Assets used (tangible and intangible)
- Risks assumed by each party
- Changes from prior year
-
Method Selection and Rationale
- Which method was applied (CUP, TNMM, Cost Plus, etc.)
- Why this method is most appropriate
- Why alternatives were rejected
-
Comparability Analysis
- Search methodology and databases used
- Screening criteria and results
- Accept/reject matrix
- Final comparables and their financial data
-
Economic Analysis
- PLI selection and calculation
- Arm's length range determination
- Where tested party result falls
- Any adjustments performed
-
Conclusion
- Clear statement on arm's length compliance
Functional Analysis in the Local File
The functional analysis is the backbone of the Local File—it drives method selection, tested party identification, and comparable selection. A superficial FAR analysis is among the most common documentation weaknesses.
What Makes a Strong Functional Analysis?
| Element | Weak (Generic) | Strong (Entity-Specific) |
|---|
| Functions | "Performs marketing and sales" | "Executes marketing campaigns designed by HQ, manages 15-person sales team covering DACH region, handles post-sale support" |
| Assets | "Uses typical business assets" | "Operates 10,000 sqm warehouse; utilizes parent's trademark under license; employs €2M inventory on average" |
| Risks | "Bears normal business risks" | "Assumes credit risk on 45-day receivables (bad debt ~1.5%); inventory obsolescence risk capped at 3% via buy-back clause; no product liability (retained by manufacturer)" |
Two-Sided Analysis
The Local File should analyze both parties to the transaction, not just the local entity. Tax authorities (especially HMRC) criticize one-sided analyses that don't explain what the counterparty contributes.
Example structure:
- LocalCo functions: Distribution, marketing, customer service
- ParentCo functions: Product development, manufacturing, brand management, global strategy
- Risk allocation: LocalCo bears market risk within territory; ParentCo bears product and production risks
TipThe Specificity Test: Read your functional analysis aloud. If it could describe any company in your industry, it's too generic. Add facts specific to this entity: headcount numbers, specific assets, contractual risk allocations, decision-making authority examples.
Economic Analysis and Benchmarking Integration
The Local File must demonstrate how arm's length prices were determined. This means integrating the benchmarking study into the document—not just referencing an external report.
What to Include in the Economic Analysis
-
Method Selection Rationale
- Consideration of all methods
- Why selected method is most appropriate
- Cite OECD ¶2.1-2.12 on method selection
-
Tested Party Selection
-
PLI Selection
-
Comparables Search Documentation
- Database(s) used
- Search date
- Search criteria (NACE/NAICS codes, keywords, geographic scope)
- Number of initial results
- Quantitative screens applied
- Manual screening decisions
-
Accept/Reject Matrix
- Every company that passed initial filters
- Decision (Accept/Reject) for each
- Specific reason for rejection
- See our Quantitative Screening Guide
-
Comparables Data
- Final set with company descriptions
- Financial data (typically 3 years)
- PLI calculations for each
-
Arm's Length Range
- Range methodology (IQR vs. full range)
- Any adjustments (working capital, etc.)
- Final range
-
Results Comparison
- Tested party's actual result
- Where it falls in the range
- Conclusion on arm's length compliance
Updating Benchmarking Studies
| Approach | When Appropriate | Documentation Required |
|---|
| Full refresh | Every 3 years minimum; or when facts change materially | New search, new comparables set |
| Roll-forward | Intervening years when business unchanged | Same comparables, updated financials; confirm validity |
| Annual review | Every year | Check for M&A, business changes; update data |
NoteBest Practice: Update comparable financials annually; conduct full re-search every 3 years or when the tested party's business model changes. Document in the Local File: "The 2024 comparables set was reviewed in 2025 and deemed still appropriate. Financials were updated. No companies were removed or added."
Section C of the Local File requires financial data that ties the economic analysis to the audited accounts. This reconciliation is critical—tax authorities frequently challenge documentation where numbers don't trace back to financials.
What to Include
-
Annual Financial Statements
- Audited if available
- Same fiscal year as analysis
-
Segmentation Schedules
- How transaction revenue/costs were isolated
- Allocation keys for shared expenses
- Tie-out to total financials
-
PLI Calculation Details
- Source of each number
- Any adjustments made
Example Reconciliation Table
| Line Item | Per Financials | Related-Party | Third-Party | Notes |
|---|
| Revenue | €100M | €80M | €20M | IP sales segmented |
| Cost of Sales | €70M | €55M | €15M | By product line |
| Gross Profit | €30M | €25M | €5M | |
| Operating Expenses | €22M | €20M | €2M | Allocated by revenue |
| Operating Profit | €8M | €5M | €3M | |
| OP Margin | 8.0% | 6.25% | 15.0% | Tested: 6.25% |
WarningCommon Pitfall: Presenting analysis on a segmented basis without showing how segments add up to the whole. If an auditor can't follow the trail from financial statements to your analysis, they may distrust the entire study. Always include a reconciliation bridge.
Contemporaneous vs. Retrospective Documentation
"Contemporaneous" documentation means prepared before or at the time of filing the tax return—not reconstructed after an audit notice arrives.
Timing Requirements by Jurisdiction
| Jurisdiction | When Documentation Must Exist | Submission Timeline | Penalty Risk for Late |
|---|
| US | Generally by actual tax return filing for documentation-based penalty relief | Within 30 days of IRS request | Potential 20% or 40% of the tax underpayment attributable to the misstatement; relief is conditional |
| Germany | Extraordinary-transaction records: within 6 months after the relevant fiscal year-end; separate production rules apply | 30 days after request; specified records also due automatically after an audit order (see below) | €5K+ fixed; 5-10% of adjustment may apply; daily fines |
| India | By statutory due date for Form 3CEB (confirm annually) | Within 30 days of request | 2% of transaction value may apply |
| UK | Prepared before corporate tax return submission | Within 30 days of HMRC request | "Careless behavior" penalty; fixed penalty for record failures |
| Australia | By tax return filing | Upon ATO request | 25-50% of tax shortfall if no RAP |
| Netherlands | By tax return filing deadline | Within ~4 weeks of request | May lead to adverse procedural consequences |
For Germany, AO §90(4) also requires the transaction matrix, required Master File and extraordinary-transaction records within 30 days after notification of the audit order, without a separate request. A justified extension may be granted. The BMF guidance applies the new rules from 1 January 2025, including audit orders covering earlier years. For older proceedings, check the request and audit-order dates; the financial year alone does not determine the deadline.
US percentages apply to the relevant tax underpayment, not the income adjustment. Meeting timing requirements alone does not ensure relief: the analysis must also satisfy the substantive requirements in Treas. Reg. §1.6662-6.
Why Timing Matters
- Penalty Protection: Most jurisdictions only provide penalty relief if documentation was contemporaneous
- Credibility: Documentation created after audit appears self-serving
- Opportunity to Adjust: If you discover pricing issues during documentation, you can still adjust in the tax return
- Completeness: Information is fresher; key details aren't forgotten
TipWorkflow Recommendation: Treat the Local File as part of an ongoing transfer pricing process: set prices at year start (planning), monitor results mid-year, make adjustments if needed, and finalize documentation by year-end or shortly after. Don't wait until the last moment before the tax return.
Local File Preparation Timeline
A structured preparation process ensures documentation quality and contemporaneous completion. Rushing at year-end produces weak documentation that invites audit challenges.
Recommended Annual Workflow
During the Year (Ongoing):
- Maintain intercompany agreements current
- Track transaction volumes and pricing by category
- Flag any significant changes (restructurings, new transactions, function shifts)
- Update functional analysis inputs as business evolves
Q1 (Months 1-3 after fiscal year-end):
- Finalize year-end financials (draft or audited)
- Identify all material controlled transactions for the year
- Confirm materiality thresholds (quantitative and qualitative)
- Gather intercompany agreements and contract terms
Q2 (Months 4-6):
- Complete functional analysis updates
- Determine if benchmarking study needs refresh or roll-forward
- Update comparable financials if rolling forward prior study
- Begin drafting Section A (entity overview) and Section B (transactions)
Q3 (Months 7-9):
- Complete benchmarking updates or new searches
- Finalize economic analysis and arm's length conclusions
- Prepare Section C financial reconciliation schedules
- Cross-check consistency with Master File
Q4 (Months 10-12):
- Internal review and quality assurance
- Address any anomalies or results outside range
- Senior management review and sign-off
- Finalize and archive documentation before tax return filing
Coordination with Master File
The Local File should reference and align with the Master File. Key coordination points:
- Functional analysis: Entity characterization must match
- Business description: Local context should complement global narrative
- Transfer pricing policies: Local application should reflect stated group policies
- Timeline: Complete Master File first (provides context), then Local Files
NoteFor complex entities: Entities with intangibles, restructurings, or multiple transaction types should begin preparation earlier (Q1) to allow adequate time for thorough analysis. Don't underestimate the time required for proper functional interviews and comparables research.
Common Timeline Failures
- Waiting for audited financials: Draft sections A and B using management accounts while awaiting audit completion
- Delaying benchmarking updates: Start comparable data collection in Q1, not Q3
- Last-minute functional analysis: Schedule business unit interviews early in the process
- Overlooking translation requirements: Factor in 2-4 weeks for professional translation where needed
For recurring annual preparation, documentation software can help reuse templates and organize source facts. Review changes to the business, transactions and financial information before carrying last year's conclusions forward.
Local File Length and Detail: Finding the Right Balance
There's no magic page count—focus on completeness and clarity, not length.
Typical Ranges
| Entity Complexity | Estimated Length | Key Driver |
|---|
| Simple (1-2 routine transactions) | 10-20 pages | Straightforward functional profile |
| Moderate (3-5 transaction types) | 20-50 pages | Multiple transaction categories |
| Complex (many transactions, intangibles, financing) | 50+ pages | Extensive analysis required |
Quality Over Quantity
Tax authorities consistently criticize:
- Bloated documentation with generic filler text
- Boilerplate that doesn't reflect entity-specific facts
- Copy-paste from prior years without updates
They want:
- Clear, direct answers to compliance questions
- Entity-specific details in functional analysis
- Transparent methodology in benchmarking
- Reconcilable numbers to financials
Jurisdiction-Specific Requirements
While OECD Annex II provides the template, local rules add nuances.
Germany
- Strict thresholds: Documentation required for cross-border transactions above €6M goods or €600K other business transactions
- Intercompany agreements mandatory: Informal arrangements viewed unfavorably
- Timing: Production within 30 days after request; the transaction matrix, required Master File and extraordinary-transaction records are also due within 30 days after notification of an audit order without a separate request. Justified extensions are possible. The separate GAufzV §3 timely-record rule treats extraordinary-transaction records prepared within 6 months after the relevant fiscal year-end as timely; it does not extend an earlier production deadline.
- Language: Must be provided in German if requested
- Penalties: Potentially severe—€5K minimum; 5-10% of income adjustment may apply; daily fines for late submission
United Kingdom
- 2023 regulations: Formal Master/Local File now required for groups with €750M+ consolidated revenue under the Transfer Pricing Records Regulations
- Materiality: £1M de minimis per category (aggregate value), except categories always material (intangibles, profit splits)
- Focus: Two-sided functional analysis; HMRC criticizes one-sided presentations
- Penalty regime: Based on "reasonable care"; specific fixed penalties for record-keeping failures; documentation demonstrates diligence
India
- Low threshold: Rule 10D exemption from prescribed documentation up to ₹1 crore (₹10M); above threshold, comprehensive documentation required
- CA certification: Form 3CEB must be filed by the applicable statutory due date (confirm annually as dates shift)
- Aggressive audits: TPOs commonly conduct own searches and reject taxpayer comparables
- Penalty: 2% of transaction value may apply for failure to maintain prescribed documentation
Australia
- RAP standard: Documentation must support a "reasonably arguable position"
- Safe harbors: PCG 2017/2 provides simplified options for low-risk scenarios
- Focus areas: Marketing hubs, commodity trading, intercompany financing
- Timing: Must be contemporaneous—prepared by return filing
United States
- Terminology: Not called "Local File" but §1.6662-6 documentation requirements serve same purpose
- Penalty protection: Documentation generally must exist by return filing and be supplied within 30 days of request; adequacy and reasonableness also matter, so timely records do not guarantee relief
- Content: Effectively same as OECD Annex II—overview, functional analysis, method, comparables, results
- Principal + Background documents: Main report plus supporting data
Common Local File Weaknesses (and How to Avoid Them)
Based on audit experience worldwide, these are the most frequent problems:
1. Boilerplate Descriptions
Problem: Generic text that could apply to any company
Fix: Customize every section with entity-specific facts
2. Missing Intercompany Agreements
Problem: No contracts to support documented arrangements
Fix: Ensure all material transactions have written agreements; if none, document terms explicitly
3. Outdated Benchmarking
Problem: Using comparables data from years ago without updates
Fix: Update financials annually; full refresh every 3 years
4. Master File Inconsistency
Problem: Local File contradicts Master File descriptions
Fix: Cross-reference both documents during preparation; align terminology
5. Superficial Functional Analysis
Problem: Generic FAR that doesn't distinguish the entity
Fix: Conduct real interviews; include specific facts, numbers, examples
6. Numbers Don't Reconcile
Problem: Financial data in analysis can't be traced to statements
Fix: Include reconciliation schedules showing the tie-out
7. Non-Contemporaneous Preparation
Problem: Documentation prepared only after audit notice
Fix: Establish firm deadlines; prepare by tax return filing
8. Omitted Transactions
Problem: Material transactions missing from the Local File
Fix: Cross-check against related-party disclosures in statutory accounts
9. Poor Comparable Documentation
Problem: No accept/reject matrix; unclear search methodology
Fix: Document every step; maintain comprehensive matrix with reasons
10. No Explanation for Results
Problem: Tested party outside range with no explanation
Fix: Address anomalies; explain year-specific factors; note any adjustments made
Practical Example: Local File for a Distribution Subsidiary
Profile: GermanCo is a full-risk distributor purchasing products from USCo (parent) for resale in Germany.
Transaction Summary
| Transaction | Description | Annual Amount | Method |
|---|
| Purchase of Goods | Finished products from USCo | €50M | TNMM |
| Royalty | Trademark license from USCo | €2M (2% of sales) | CUP |
| Management Fee | Group services allocation | €0.5M | Cost Plus |
Section A: Local Entity
- Business: Full-risk distributor of consumer electronics in DACH region
- Strategy: Market expansion in premium segment
- Competitors: [Main competitors in relevant market]
- Restructurings: None in current or prior year
- Management: Reports to Regional VP (Switzerland), who reports to Global Sales SVP (US)
Section B: Controlled Transactions
B1: Purchase of Goods (€50M)
Functional Analysis:
- GermanCo: Marketing, sales, warehousing (10,000 sqm), customer service; bears inventory risk, credit risk (45 DSO), market demand risk
- USCo: Manufacturing, product development, brand ownership; bears production and product liability risks
Method: TNMM with GermanCo as tested party (simpler profile; USCo owns valuable IP)
PLI: Operating Margin (revenue-driven business)
Benchmarking: 12 comparable European distributors identified; IQR operating margin 2.8%-5.2%
Result: GermanCo OM = 4.1% → within arm's length range
B2: Royalty Payment (€2M)
Analysis: 2% of net sales for trademark use
Method: External CUP using trademark royalty database
Comparables: Industry royalty rates range 1.5%-3.5% for similar consumer products trademarks
Result: 2% within range → arm's length
B3: Management Fee (€0.5M)
Analysis: Allocation of group shared services (HR, IT, legal support)
Method: Cost Plus (5% markup on direct costs)
Basis: OECD elective simplified approach for low-value-adding services (where jurisdiction accepts)
Result: Cost + 5% consistent with OECD simplified approach → arm's length
[Reconciliation table showing how €50M purchases, €2M royalty, and €0.5M fee tie to German statutory accounts]
Documentation Guides:
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 a Local File required in every country?
Nearly all countries following OECD BEPS recommendations require Local Files (or equivalent documentation) for large MNEs, but specifics vary. Thresholds differ: Netherlands requires formal Master/Local Files if group revenue ≥€50M; Germany has transaction-level thresholds (€6M goods, €600K other business transactions); India has a Rule 10D exemption up to ₹1 crore but expects TP support regardless. Some countries (like the US) have documentation requirements under different names (§1.6662-6) but serve the same purpose. Even where not strictly mandated, documentation is necessary to demonstrate arm's length pricing if challenged. The safest approach: prepare a Local File for every jurisdiction with material related-party transactions.
What transactions should the Local File cover?
All material controlled transactions—both quantitative (exceeding monetary thresholds) and qualitative (involving intangibles, restructurings, or significant risk). Materiality thresholds vary: HMRC allows exclusion where aggregate value in a category doesn't exceed £1M (except always-material categories like intangibles); Germany requires documentation above €6M goods or €600K other transactions; India's Rule 10D threshold is ₹1 crore aggregate. However, certain transactions are always material regardless of amount: intangible transfers, business restructurings, cost contribution arrangements, and profit split arrangements. Document your materiality approach in the Local File and at least list any excluded transactions with brief justification.
How long should a Local File be?
Length depends on complexity: A simple entity with one routine transaction might need 10-20 pages; complex entities with multiple transaction types, intangibles, or financing may require 50+ pages. There's no regulatory minimum or maximum—focus on completeness and quality. Tax authorities criticize both inadequate documentation (too brief to be useful) and bloated documentation (padding with generic text). Every page should add value: specific facts, real analysis, clear conclusions. If you can defend your transfer pricing in 40 well-organized pages, that's preferable to 150 pages of boilerplate.
When must the Local File be prepared?
Prepare the evidence while facts are current, then meet the applicable local preparation and submission deadlines. In the US, documentation-based penalty relief generally requires records to exist when the return is filed and to be supplied within 30 days of an IRS request; substantive adequacy also matters. Germany has separate rules: extraordinary-transaction records are treated as timely if prepared within 6 months after the relevant fiscal year-end, while production is generally due within 30 days after request. The transaction matrix, required Master File and extraordinary-transaction records are due automatically within 30 days after notification of an audit order, subject to a justified extension. An earlier production deadline still applies. Verify the procedural dates and applicable local rules rather than treating tax-return filing as a universal German deadline.
Can I use the same benchmarking study for multiple years?
Yes, with conditions. It's common to use the same comparable set for 2-3 years if the business is unchanged, but you must: (1) update financial data for comparables each year, (2) verify comparables are still valid (not acquired, defunct, or diversified), and (3) document that you reviewed and confirmed appropriateness. OECD acknowledges multi-year approaches may be acceptable. However, never use stale data—a study with 2019 financials applied to 2025 results will be challenged. Document the roll-forward approach: "The 2024 comparables set was reviewed and deemed appropriate for 2025. Financials were updated. [Company X] was removed due to acquisition."
What if my Local File benchmarking differs from the Master File's global study?
Differences are acceptable if explained and justified. The Master File might present a global or regional policy, while the Local File uses jurisdiction-specific comparables—this is appropriate and often required. For example, the Master File might show European distributors at 3-5% margin, while your German Local File uses German/DACH comparables at 2.5-5%. Document the rationale: "Local analysis used German comparables to meet local expectations for domestic data. The range is consistent with the group's global benchmarking but reflects local market conditions." Avoid contradictions in business descriptions or functional analyses—those should align between documents.
Do I need separate Local Files for each transaction type?
No—one Local File per entity covers all material transactions in separate sections. The OECD uses "category of controlled transactions," meaning you group similar transactions (all goods purchases, all service fees) but analyze each category distinctly. Structure the Local File with: Section A (entity overview), Section B1 (Transaction Type 1), Section B2 (Transaction Type 2), etc., Section C (financials). Each transaction section should have its own functional analysis, method selection, and benchmarking. Don't prepare separate documents unless the transactions are completely unrelated or local rules require it.
What if I don't have intercompany agreements for some transactions?
Lack of agreements is a common pitfall that reduces credibility. Tax authorities expect written contracts for material arrangements—that's how independent parties would operate. If agreements don't exist: (1) document the terms explicitly in the Local File as if there were an agreement, (2) note that no formal contract exists but describe the understood arrangement, and (3) put proper agreements in place going forward. Some jurisdictions (Germany especially) view informal arrangements unfavorably and may question whether arrangements are truly arm's length. At minimum, include the key terms, pricing methodology, and risk allocation in your documentation.
What are the penalties for inadequate Local Files?
Penalties vary but can be substantial:
- Germany: Fixed €5,000 minimum; 5-10% of income adjustment may apply if documentation inadequate; daily fines for late submission
- India: 2% of transaction value may apply for failure to maintain prescribed documentation under Rule 10D
- US: A qualifying valuation misstatement can attract 20% of the attributable tax underpayment, rising to 40% for a gross misstatement. Documentation-based relief depends on the applicable timing, adequacy and reasonableness conditions; having a file is not automatic protection
- UK: "Careless" behavior penalty (0-30% of tax) if no documentation; fixed penalties for record-keeping failures
- Australia: 25-50% of tax shortfall if no reasonably arguable position; rates depend on behavior
Beyond penalties, inadequate documentation may shift the burden of proof to the taxpayer and allows tax authorities to estimate adjustments unfavorably. The cost of proper documentation is almost always less than the cost of penalties and audit defense.
Borys UlanenkoCEO of ArmsLength AI![Local File Best Practices [2026]: Building Audit-Ready TP Documentation](/_next/image?url=%2Fimages%2Fblog%2Fcovers%2Flocal-file-best-practices.png&w=3840&q=75)
