Short Answer
Frequent errors include weak or missing functional analyses, benchmarking studies that rely on poorly matched comparables, intercompany agreements that don't reflect how the parties actually operate, and documentation prepared after the fact rather than when the transactions occur. Inconsistencies between the documentation, the tax return, and the company's real conduct are also a leading source of audit exposure.
Comprehensive Answer
The short answer names the major categories of error. In practice, these mistakes rarely appear in isolation. They compound one another, and the way they surface during an audit often depends on small details in how a file was built. This article looks at how each problem arises, what it looks like in a real file, and how to avoid it.
Functional analyses that describe the org chart, not the business
A functional analysis is meant to capture which entity performs which functions, owns which assets, and bears which risks. A common failure is building it from job titles or legal entity descriptions rather than from interviews with the people doing the work. The result reads well but does not match reality.
- Risk allocation on paper only. A subsidiary is labeled a limited-risk distributor, yet it negotiates prices, absorbs inventory write-downs, or funds marketing campaigns on its own initiative.
- Overlooked intangibles. Local teams that develop customer relationships, know-how, or processes are described as routine service providers, so their contribution is never valued.
- Static descriptions. The analysis is copied forward each cycle even after a restructuring, acquisition, or change in who makes key decisions.
Benchmarking built on weak comparables
A benchmarking study is only as credible as the companies in the set. Frequent problems include:
- Accepting database search results without reviewing the underlying business descriptions, so companies with different activities remain in the set.
- Using overly broad or overly narrow screening criteria that either dilute comparability or leave too few data points.
- Choosing a profit level indicator that does not fit the tested party's functions.
- Cherry-picking the range or position within the range without a documented rationale.
- Reusing an old study without checking whether the comparables still qualify.
Reviewers typically focus on the rejection and acceptance reasoning. If the file cannot explain why a company was included or excluded, the conclusion becomes difficult to defend.
Intercompany agreements that diverge from conduct
Tax authorities generally look at what the parties actually do, not just what the contract says. Agreements cause trouble in several ways:
- Terms are boilerplate and do not address pricing method, service scope, or payment timing.
- The contract assigns a fee or royalty rate that the parties never actually applied in their invoices.
- Agreements are signed well after the activity began, with retroactive effective dates that invite skepticism.
- Entities are named in the agreement that no longer exist or no longer perform the stated role.
The remedy is a periodic check that compares contract terms against invoices, payment flows, and operational reality, then updates one or the other.
Timing: documentation created after the fact
Contemporaneous documentation shows that pricing was considered when the transactions occurred. Preparing it only when an audit notice arrives creates both a practical and a credibility problem. Key personnel may have left, data may be hard to reconstruct, and the analysis may look engineered to justify a result already reached. A sound process sets an annual calendar: confirm facts, update the analysis, test results before year-end, and finalize the file shortly after the period closes.
Inconsistencies across documents
Even a well-built file can fail if it conflicts with other company records. Reviewers compare the transfer pricing report to tax returns, financial statements, customs declarations, and public disclosures. Typical inconsistencies include:
- A report describing an entity as low-risk while its financial statements show volatile results.
- Year-end adjustments recorded in the books but not mentioned in the documentation.
- Customs values that differ from intercompany transfer prices without explanation.
- Marketing materials or investor presentations that describe a local entity's role differently than the report does.
Process failures that sit behind the technical errors
Many documentation problems trace back to ownership. When tax, finance, legal, and operations do not coordinate, nobody notices that a new service arrangement, financing transaction, or cost-sharing practice has gone undocumented. Other process gaps include relying entirely on an outside provider without internal review, failing to retain supporting workpapers, and neglecting transactions that seem small but recur, such as management fees, intercompany loans, or guarantees.
Practical safeguards
- Interview business personnel and document the facts they provide.
- Maintain an inventory of all intercompany transactions, including minor ones.
- Align agreements, invoices, and documentation on a regular schedule.
- Record the reasoning behind each major judgment, such as method selection and comparable screening.
- Cross-check the final report against the tax return and other filings before finalizing.
- Assign a named internal owner responsible for keeping the file current.
Treating documentation as a living record of how the business operates, rather than a compliance deliverable, addresses most of these errors at the source.