A founder-owned group can run an excellent business and still be unprepared for a transfer pricing request. The tax authority may ask for intercompany agreements, functional analyses, benchmarking, invoices, allocation schedules, and the written reasoning behind management fees or shareholder loans. If those records don't exist, the company isn't defending its pricing policy. It's reconstructing one under pressure.
That problem has become more urgent as international documentation standards continue to expand. The OECD's framework now reaches beyond a basic pricing memo, while Canada has introduced a much tighter response deadline and the OECD continues to develop guidance for distribution returns and intra-group services. For high-net-worth individuals, family offices, real estate groups, and closely held multinationals, transfer pricing documentation must be built around actual conduct and retained throughout the year.
When the Tax Letter Arrives and the File Is Empty
The request arrives at the family office on a Tuesday morning. A foreign subsidiary paid a management fee to a related company, an operating entity borrowed from a family investment vehicle, and a real estate company shared accounting and technology costs with affiliates. The tax authority wants the agreements, the pricing analysis, the allocation key, and evidence that each recipient received a commercial benefit.
The controller finds signed contracts for some transactions. Invoices exist, but they use broad descriptions such as “administrative support.” A prior advisor prepared a general report years ago, but nobody can connect its assumptions to the current employees, systems, functions, or financial results. The group has records, but it doesn't have a coherent file.
That distinction matters. The OECD's 2015 BEPS Action 13 report established a global three-tier documentation framework and shifted transfer pricing documentation toward standardized transparency. Tax authorities can use the information to compare reported profits with the locations where business activity occurs.
Canada illustrates why an old annual timetable can fail. The Canada Revenue Agency describes rules under Budget 2025 that reduce the time to provide contemporaneous documentation after a request from 3 months to 30 days, raise the penalty threshold to the lesser of $10 million or 10% of gross revenue, introduce simplified documentation in qualifying circumstances, and apply the changes to taxation years beginning after November 4, 2025. Those details appear in the CRA's transfer pricing guidance.
Practical rule: A document assembled after the request may explain the result, but contemporaneous records show how the business made the decision.
A closely held group doesn't need the same infrastructure as a Fortune 500 company. It does need a disciplined record of who performed each function, who owned or used each asset, who bore each risk, how the price was selected, and what evidence supports the conclusion. That is the standard that makes a tax examination manageable instead of personal, disruptive, and expensive.
What Transfer Pricing Documentation Actually Is
Start with a household analogy. Suppose one family operates three shared accounts, one for the household, one for a rental property, and one for an investment activity. A sensible family keeps a central record of income and responsibilities, detailed records for each account, and a consolidated view showing how money moved between them.
A multinational group needs the same logic, expressed through tax documentation. The central record is the master file. The account-level record is the local file. The consolidated view is the Country-by-Country Report, or CbCR.
The three records answer different questions
The master file describes the group as a whole. It explains the organizational structure, business lines, important intangibles, financing, and broad transfer pricing policies. A reader should understand how the group creates value and how its entities interact.
The local file narrows the analysis to one taxpayer and one jurisdiction. It identifies the controlled transactions, explains the local entity's functions and risks, selects the most appropriate method, and supports the pricing with financial data and comparables where appropriate. The OECD's consolidated Transfer Pricing Guidelines describe the local file as a supplement to the master file and connect it to the arm's length analysis for material local transactions.
CbCR provides a jurisdiction-by-jurisdiction picture of revenue, profit, taxes paid, and indicators of economic activity. It helps tax administrations evaluate whether the group's reported tax outcomes align with the location of its people, assets, and operations.
What the records don't do
Transfer pricing documentation isn't the same thing as a tax return. It isn't a substitute for an intercompany agreement, and an agreement alone doesn't prove that the parties behaved consistently with its terms. It also can't create substance where the business lacks employees, decision-making authority, operational capacity, or evidence of service delivery.
The core question is simple: Would independent parties have agreed to these terms after considering the functions, assets, risks, market conditions, and expected benefits? The file should preserve the answer while the facts are available, not after personnel have left and financial records have been recoded.
The Master File, Local File, and CbCR Explained
The three tiers work together, but they serve different readers. A tax authority reviewing a local entity generally starts with the local file. It may then use the master file to understand the broader group and CbCR to assess the global pattern.
Master file
The master file gives the group-wide context. It should identify the legal and ownership structure, describe the major business lines, explain the group's financing arrangements, identify important intangibles, and summarize the policies governing significant categories of intercompany transactions.
For a family office or closely held group, the strongest master file connects the structure to reality. If one entity supposedly owns intellectual property, the file should identify who developed it, who funded development, who makes strategic decisions, and who controls relevant risks. If a central company charges management fees, the master file should explain what the central team does and which entities receive support.
Local file
The local file is where an examiner tests the pricing. It should include the local entity's organizational chart, financial statements, transaction schedules, agreements, invoices, functional analysis, method selection, and supporting calculations. A distribution company, for example, may need to explain its sales activities, inventory responsibilities, marketing functions, customer relationships, and exposure to market risk.
Service arrangements require more than a cost allocation spreadsheet. Retain work products, meeting records, service descriptions, employee responsibility summaries, time records where available, and communications showing what the recipient received. The analysis should explain why the allocation key reflects expected benefit rather than convenience.
Country-by-Country Report
CbCR reports global revenue, profit, taxes paid, and indicators of economic activity by jurisdiction. The OECD framework generally applies the CbCR tier to groups at or above the EUR 750 million consolidated revenue threshold, as described in the OECD's Action 13 report. Many family offices won't reach that threshold, but an operating group owned through a foreign holding structure may need to check the consolidated group position rather than relying on the size of one local company.
| Tier | Scope | Prepared by | Trigger or threshold | Typical contents |
|---|---|---|---|---|
| Master file | Group-wide | Central tax or finance team | Local rules and group profile | Structure, business lines, intangibles, financing, services, policies |
| Local file | Entity and jurisdiction-specific | Local finance team with tax advisors | Local materiality and jurisdictional rules | Transactions, agreements, functions, method, comparables, financial support |
| CbCR | Jurisdiction-by-jurisdiction | Ultimate parent or designated filer | Large multinational group requirements | Revenue, profit, taxes paid, and economic activity indicators |
The practical rule is straightforward. Prepare the master file when the group structure and cross-border policy require a central explanation. Prepare a local file when a jurisdiction has material controlled transactions or documentation expectations. Determine CbCR obligations from the consolidated group, not from one family-owned entity in isolation.
OECD Rules and US Sec. 6662 Side by Side
A U.S.-domiciled family discovers the problem during an examination: its foreign subsidiary has a polished global report, but no transaction-level analysis supporting the U.S. return. One report rarely satisfies every jurisdiction. The OECD framework provides a shared international structure, while U.S. penalty protection depends on documentation that meets the Internal Revenue Code and Treasury regulations.
The OECD approach uses a master file, local file, and CbCR. It expects contemporaneous support for the arm's length principle and gives tax administrations a consistent basis for reviewing group structure, local transactions, and jurisdictional results. The OECD's 2022 Transfer Pricing Guidelines address financial transactions, hard-to-value intangibles, and the transactional profit method. The guidelines were updated on 19 February 2024 to incorporate Amount B guidance, so a file built once and ignored can become outdated.
U.S. rules target penalty protection under IRC Section 6662 and Treasury Regulation 1.6662-6. A U.S. taxpayer needs a reasonable, documented analysis of its controlled transactions, with the relevant study prepared by the time the return is filed. The IRS guidance on Section 482 documentation is the practical reference point for the U.S. analysis. Reasonable cause and good faith may matter, but they do not turn a late reconstruction into persuasive contemporaneous evidence.
| Feature | OECD standard | U.S. Section 6662 and Regulation 1.6662-6 |
|---|---|---|
| Main structure | Master file, local file, and CbCR | Transaction-specific documentation supporting Section 482 positions |
| Primary purpose | Consistent global transparency and arm's length support | Support for pricing positions and penalty protection |
| Timing focus | Prepared by the local tax return due date as best practice | Qualified documentation available by the return filing date |
| Global reporting | CbCR framework for qualifying large groups | U.S. country reporting rules operate separately from the core study |
| Examination issue | Inconsistent group and local facts | Missing or inadequate support for the reported Section 482 result |
Treaty provisions can affect corresponding adjustments and dispute resolution. Pillar Two GloBE rules can create further data and tax-analysis obligations for groups within their scope. Foreign subsidiaries may face local-file forms, electronic filing, or deadlines that do not match the U.S. calendar. For HNWIs, family offices, and closely held cross-border groups, map each entity, transaction, and filing obligation before adopting one global documentation approach. A common framework is useful, but the U.S. file must stand on its own.
Building a Documentation Timeline That Survives an Audit
A year-end scramble is a poor control system. The OECD guidance recommends that the master file and local file be prepared no later than the local entity's tax-return due date, while the CbCR template should be completed within one year after the ultimate parent's fiscal year-end. Those are planning anchors, not permission to wait.
Canada's 30-day production period makes the point sharply. The OECD's Amount B update and its 2026 consultation on Chapter VII concerning intra-group services also show why a static file can age quickly. The EY summary of the OECD intra-group services consultation highlights the need to substantiate expected benefits, communications, deliverables, cost breakdowns, allocation keys, and pass-through costs.
A workable annual cycle
First quarter should be fact-finding. Update the functional analysis while prior-year financials, personnel information, budgets, and transaction records are still accessible. Review every intercompany agreement against actual conduct. The tax lead should flag changes in decision-making, employees, financing, intellectual property, markets, and risk allocation.
Second quarter should be analysis and policy control. Finalize the master file and refresh material benchmarking before the relevant tax returns are filed. The controller should produce segmented financial data by transaction category, not just a consolidated income statement. The legal and finance teams should approve agreements that reflect the business being conducted.
Third quarter should be data completion. Complete the local file and prepare the CbCR data pull if the group is in scope. Coordinate the data with Pillar Two GloBE inputs where applicable, because inconsistent revenue, tax, employee, and entity data can create avoidable questions.
Fourth quarter should be sign-off and preservation. Obtain written management approval, document the reasons for material pricing decisions, record open benchmarking issues, and lock an organized archive. Keep source documents, calculations, agreements, invoices, service evidence, and correspondence together.
Checklist for the accountant
| Deliverable | Owner | Dependency |
|---|---|---|
| Entity and transaction inventory | Controller | General ledger and legal entity list |
| Updated functional analysis | Tax lead and business managers | Interviews, organization charts, operating records |
| Agreement review | Legal and tax teams | Current contracts and transaction descriptions |
| Benchmarking and method memo | Transfer pricing advisor | Reliable segmented financial data |
| Service-benefit evidence | Service provider and recipients | Deliverables, communications, allocation schedule |
| CbCR and GloBE data reconciliation | Group finance | Jurisdictional financial and tax data |
| Final approval and archive | CFO or family-office principal | Completed file and unresolved-issue log |
Common Pitfalls for HNWI and Family Office Groups
Wealthy families often have strong advisors and weak evidence. The problem isn't a lack of intelligence. It stems from treating transfer pricing as a technical calculation detached from how the family truly operates.
The five traps that create avoidable exposure
A wire transfer isn't a pricing study. A recurring payment proves that money moved, not that unrelated parties would have agreed to the amount. Correction: prepare a contemporaneous method analysis that connects the charge to functions, benefits, costs, and commercial terms.
An old comparable isn't automatically reliable. A license database output can look authoritative while reflecting business conditions that no longer match the tested transaction. Correction: document the search strategy, selection criteria, rejected companies, relevant economic conditions, and the reason the final set remains comparable.
Group size can be misread. A foreign holding company may bring a wider operating group within CbCR obligations even when the family office itself appears modest. Correction: calculate the relevant consolidated group position and identify the ultimate parent, surrogate filer, and exchange responsibilities.
Shared services need proof of benefit. Management fees, guarantees, accounting support, technology, and back-office charges attract questions when the invoice describes no deliverable and the allocation key has no explanation. Correction: retain service descriptions, recipient communications, cost pools, exclusions, allocation calculations, and evidence of expected benefit.
Shareholder loans are still controlled transactions. A family lender may regard an operating company as part of the same enterprise, but a tax authority will examine the loan terms, borrower capacity, security, repayment expectations, and interest rate. Correction: document the credit analysis, currency, maturity, covenants, security, alternatives considered, and pricing method before funding.
The recurring failure is inconsistency. The agreement says one entity performs the work, the invoice says another entity supplied it, and the financial statements record the payment under a third description. Examiners don't need a dramatic error to challenge the file. They need only a gap between the written story and the operating facts.
The following video can help frame the practical risks that arise when related-party pricing is treated as paperwork rather than evidence.
Turning Documentation into a Year-Round Discipline
The strongest file is assembled in pieces. Employees create service evidence when they deliver work, finance records transaction data when it posts, and management makes pricing decisions before the invoice goes out. A year-end report should organize that evidence, not invent it.
The Australian Taxation Office's contemporaneous records guidance identifies records such as books, studies, budgets, plans, projections, analyses, and conclusions. Its practical message is useful across jurisdictions: records created while the facts are fresh provide stronger support in a dispute than a polished explanation produced long afterward.
The operating rhythm
Tie quarterly transfer pricing reviews to monthly management accounts. Review whether actual margins, service volumes, financing balances, and business functions still resemble the assumptions in the local file. If a real estate entity begins performing leasing administration or a family-office team takes on technology management, record that change before the next charge is calculated.
Refresh benchmarking on a deliberate schedule appropriate to the transaction. Maintain a rolling contemporaneous log for related-party loans, service charges, guarantees, royalties, cost-sharing, and other material flows. Each entry should capture the parties, amount or pricing basis, business rationale, responsible decision-maker, supporting agreement, and evidence retained.
A defensible file is a trail of business decisions, not a document that appears once a year.
A 90-day kickoff plan
Days 1 through 30, build the foundation. Inventory every related-party transaction, legal entity, account, agreement, invoice type, and recurring journal entry. Appoint one transfer pricing lead who can obtain information from finance, operations, legal, and the family office principal.
Days 31 through 60, test the highest-value flows. Perform a functional analysis of the largest services, financing arrangements, intellectual property charges, and distribution or real estate transactions. Compare the written agreements with actual conduct, then list missing evidence and benchmarking gaps.
Days 61 through 90, produce a usable first draft. Assemble the local file for the most important jurisdiction, create the supporting transaction schedule, organize service-benefit evidence, and outline the master file. Run a simulated audit by asking whether an unfamiliar reviewer could trace each material payment from agreement to invoice to financial result.
The next filing cycle should close the gaps, refresh the analysis, and formalize the archive. For a family office, that discipline is usually more valuable than a longer report. It gives the principal, controller, and tax advisor a shared factual record before a tax authority asks for one.
Blue Sage Tax & Accounting Inc. helps individuals, family offices, and closely held cross-border businesses build practical transfer pricing documentation, coordinate international tax compliance, and prepare audit-ready records throughout the year. Visit Blue Sage Tax & Accounting Inc. to discuss your intercompany transactions, documentation gaps, and next filing deadline.