Back to Insights
Documentation11 min read
Loading page…
Documentation11 min read
A TP study is the benchmarking analysis; a Local File is the full statutory document that contains it plus entity, transaction and financial disclosures..
No - though practitioners use the terms loosely. A transfer pricing study is the economic analysis: method selection, comparables search and the arm's length range for a transaction. A Local File is the complete statutory document a jurisdiction prescribes - entity information, transaction descriptions, agreements, functional analysis and financial reconciliations - with the study embedded as its economic core. The underlying framework can be reviewed in the OECD Transfer Pricing Guidelines 2022.
Local File vs TP Study: Are They the Same Thing? is not only a definition or filing question. It affects how a multinational group captures transactions, allocates responsibility, prepares financial data and responds when a tax authority asks for evidence. The key professional issue is the TP study as the economic engine inside a wider jurisdiction-specific Local File. A technically correct rule can still be applied badly when the facts, accounting records and documentation workflow are disconnected. For the official position, refer to BEPS Action 13: Transfer Pricing Documentation and CbCR.
The analysis in this article is framed for Global. OECD materials provide a common technical language, but local legislation, rules, forms and administrative guidance govern the legal obligation. Thresholds and deadlines are therefore presented with a verification date and should be reconfirmed before a filing or transaction decision. Additional authoritative context is available in Transfer Pricing Country Profiles.
| TP study (benchmarking analysis) | Local File (statutory document) | |
|---|---|---|
| Scope | One transaction class (or a tested party's aggregated flows) | Every material related-party transaction of the entity |
| Core content | Method selection and rationale; comparables search strategy, screening and set; PLI computation; arm's length range and conclusion | Entity structure and management; business and strategy; transaction descriptions, values and counterparties; intercompany agreements; full FAR analysis; the study; financial statements and tested-party reconciliation |
| Governing standard | Economic soundness and reproducibility | The jurisdiction's prescribed content list - Rule 10D (India), Ministerial Decision 97 of 2023 (UAE), GAufzV (Germany), the IRAS Guidelines (Singapore) |
| Sufficiency alone? | Supports pricing; does not discharge documentation rules by itself | Discharges the statutory obligation - if every prescribed element is present |
The classic failure: a group commissions "a TP study," receives an excellent benchmarking report, and files confident it is documented. On audit, the authority tests the file against the statutory list - and the missing entity profile, agreement inventory, transaction-by-transaction descriptions and financial reconciliation are each a documentation default, penalisable regardless of how sound the range was (India's Section 271AA at 2% of transaction value being the sharp example). Conversely, a Local File whose embedded study is thin fails substantively even though every prescribed heading is present. Both layers must hold. The underlying framework can be reviewed in the UN Practical Manual on Transfer Pricing 2021.
Ask two questions of any document: *Does the economic analysis establish an arm's length range reproducibly?* (the study test) and *Does the document contain every element the jurisdiction's rule prescribes, reconciled to the accounts?* (the file test). Multi-jurisdiction groups add a third: one core study can travel, but each country's Local File must be assembled to its own content list - a single "global report" typically satisfies no specific rulebook completely. For the official position, refer to Toolkit for Transfer Pricing Documentation Requirements.
Only if expanded to cover the jurisdiction's full prescribed content - most standalone studies lack the entity, agreement and financial-reconciliation blocks. Additional authoritative context is available in Transfer Pricing Portal.
Where formal Local File thresholds are not met, a proportionate study-plus-support is the sensible standard - the arm's length principle applies regardless, and authorities can request evidence.
Yes - the Master File is the group-level blueprint; the Local File defends one entity; the study is the economic engine inside the Local File.
Platforms like TP DOC GEN AI generate both layers from one fact model - the reproducible study and the jurisdiction-complete file around it - which is precisely the two-test structure audits apply.
State the exact alternatives being compared and the transaction, entity, period and jurisdiction to which the decision applies. Avoid comparing labels without first aligning scope. For Local File vs transfer pricing study, record unresolved assumptions and the person responsible for confirming them before the conclusion is approved. The underlying framework can be reviewed in the Rule 10B - Determination of Arm's Length Price.
Identify which requirements are prescribed locally and which elements arise from OECD-based analysis. A common global policy does not override a domestic form, threshold or deadline. For Local File vs transfer pricing study, record unresolved assumptions and the person responsible for confirming them before the conclusion is approved.
List the data, contracts, interviews, comparables and reconciliations needed for each alternative. The apparently simpler option can be weaker if the necessary evidence does not exist. For Local File vs transfer pricing study, record unresolved assumptions and the person responsible for confirming them before the conclusion is approved.
Model compliance effort, tax exposure, double-tax risk, audit defensibility and operational constraints. The best decision is rarely determined by one margin or threshold alone. For Local File vs transfer pricing study, record unresolved assumptions and the person responsible for confirming them before the conclusion is approved.
Document why the selected route is more reliable and specify the changes that would cause reconsideration. Review annually and after material business events. For Local File vs transfer pricing study, record unresolved assumptions and the person responsible for confirming them before the conclusion is approved.
A business purchases a benchmarking report and believes its Local File is complete. The report contains a search and range but no entity overview, transaction schedule, agreements, FAR or financial reconciliation. The economic study may be useful, yet the statutory documentation obligation remains incomplete. For the official position, refer to Rule 10D - Information and Documentation.
The example does not establish a universal answer. It shows why the sequence matters: define scope, establish conduct, apply the local rule, perform the economic analysis, reconcile the figures and document the review. If one of those links changes, the conclusion may also change.
Comparisons fail when the two columns do not use the same unit of analysis. One side may describe a legal filing rule while the other describes an economic method. The article and the taxpayer's decision memo must distinguish legal obligation, analytical effect and operational consequence.
The reviewer will ask whether the preferred alternative was chosen before the facts were gathered. Record the selection criteria early, test each option against the same facts and explain material assumptions. This limits hindsight and outcome-driven analysis.
A sound comparison ends with a decision rule, not a universal winner. Specify the circumstances in which each alternative is stronger and the facts that require the conclusion to be reopened.
TP DOC GEN AI can connect the transaction record and FAR profile to method selection, comparable-company screening, accept-reject reasoning, tested-party financials and deterministic PLI or range calculations. The platform supports analysis and produces a reviewable trail; it does not replace professional judgement on delineation, comparability or the final tax position.
Relevant product page: See the TP DOC GEN AI workflow. The most useful demonstration is an anonymised scenario that mirrors the entity, transaction and jurisdiction your team actually handles.
Next step: Book a personalised demo and ask the specialist to show the source trail, calculation controls, reviewer workflow and final Word/PDF output.
No. The answer depends on legal requirements, the accurately delineated transaction and the reliability of available data. A decision tree is more useful than a universal hierarchy.
Often one can be primary and the other corroborative, or a global framework can be supplemented by local compliance. Explain the purpose of each and investigate conflicting results.
Record scope, facts, alternatives, evidence, quantitative impact, assumptions, reviewer and reconsideration triggers. This makes the decision reproducible rather than outcome-driven.
At least annually and whenever material functions, risks, contracts, markets, thresholds or regulations change.
Define the exact entity, transaction or obligation and governed period. Then identify the official rule, responsible business owner, required source records and deadline. Starting with a template before scope is settled usually creates rework and hides omissions.
Use a group framework for definitions, data and review, but document local overlays for Global. Maintain one approved transaction population, a jurisdiction-specific obligation register and a controlled process for exceptions.
In the working papers and final narrative wherever facts are interpreted, alternatives are rejected, comparability adjustments are made or a legal threshold is applied. The record should identify the evidence, reasoning, reviewer and date.
Show the last-verified date, link directly to official authorities, avoid absolute claims that depend on facts and schedule a periodic regulatory review. This also improves trust for search engines and answer engines.
From a finance-function perspective, Local File vs transfer pricing study should not sit in a tax-only folder. The underlying transaction originates in contracts, operating decisions and accounting systems. Tax can analyse the position only when legal, finance and business owners provide a common description and agree how the numbers are extracted.
For Global, the official source should be retained with an access or verification date because webpages, forms and administrative guidance can change. When the law changes, update the current-year workpaper while preserving the source used for an earlier filing. Version control is part of technical accuracy.
AEO and GEO visibility depend on answer quality, not merely question-shaped headings. Each answer should be self-contained, identify the jurisdiction and period, distinguish a general principle from a filing rule, and link to the primary authority. This makes the page easier for professionals, search engines and AI answer systems to interpret.
The practical standard for Local File vs transfer pricing study is reproducibility. A reviewer who was not involved in preparation should be able to locate the source facts, understand the judgement, reperform the material calculation and identify the final approved output without relying on the original preparer's memory.
Management information should also track exceptions: transactions without agreements, entities with changed functions, missing segmental accounts, unreconciled disclosure values, stale comparable searches and deadlines without an owner. An exception register converts a long report into an operating control.
Finally, materiality should guide effort but should not be confused with legal scope. A low-value item may require disclosure even when extensive benchmarking is disproportionate, while a high-value recurring flow may justify deeper analysis, bilateral certainty or more frequent monitoring. Record both the legal requirement and the risk-based response.
A defensible position on Local File vs transfer pricing study combines current law, verified facts, reliable analysis, reconciled financial information and an accountable review trail. The goal is not simply to produce a long document. It is to create a record that another professional can understand, reperform and defend after the people and systems involved have changed. Additional authoritative context is available in Transfer Pricing Guide CTGTP1.
This article provides general educational information and is not tax, legal, accounting or investment advice. Transfer-pricing outcomes depend on the applicable law, tax year, jurisdiction and facts. The draft should undergo a final legal and factual verification before publication, and qualified advisers should be consulted before filing or adopting a position.
Topics
