Published June 20, 2025Updated March 11, 202622 min read
15 Common Benchmarking Mistakes in Transfer Pricing (and How to Avoid Them)15 Common Benchmarking Mistakes in Transfer Pricing (and How to Avoid Them)
Transfer pricing benchmarking studies are full of recurring pitfalls. This guide catalogs 15 common mistakes—spanning screening, functional analysis, database filters, adjustments, and documentation coherence—plus remediation steps and a self-audit checklist.
Borys UlanenkoCEO of ArmsLength AI
22min read
Contents↓
Contents
TL;DR key takeaways
One of the most common mistakes: insufficient documentation of your screening process. Without an accept/reject matrix showing why each company was included or excluded, your study is materially weaker in audit.
Quality over quantity: 6 excellent comparables beat 15 marginal ones. Tax authorities will strip weak comparables from your set, potentially eliminating your range.
Refresh comparable financial data annually and confirm the set still fits the tested year. A full database re-search may often be done every three years if operating conditions remain unchanged, but should be refreshed sooner where facts, markets, or local rules require it.
Match the PLI to the value driver. Using ROA for a low-asset distributor or Operating Margin for a pass-through agent creates immediate audit risk.
A self-audit checklist before submission can catch most of these mistakes—and save you significant audit headache later.
We tested three AI configurations on 10 transfer pricing questions. ChatGPT with web search scored 83%, but models without web access fabricated most quotes. Here's what we learned.
The Berry Ratio (gross profit ÷ operating expenses) is a specialized PLI for low-risk distributors and agents. Learn when it's appropriate, when to avoid it, and how to defend your analysis—with calculation examples and jurisdictional guidance.
On November 10, 2025, HMRC updated INTM485120 with critical details on searching for comparables. The key takeaway? The Interquartile Range is not a default right - and relying on it blindly carries a median-sized risk.
More resources for your next workflow stepMore resources for your next workflow step
Browse the full resource library or contact us if you want recommendations for your specific use case.
What is transfer pricing benchmarking (and why mistakes matter)?
A transfer pricing benchmarking study supports an arm’s length result by comparing the tested party’s profitability to independent companies with similar economically relevant characteristics (functions, assets, risks, contractual terms, and economic circumstances). When the screening trail, comparability rationale, or financial adjustments aren’t coherent, tax authorities can more easily challenge (or rebuild) your analysis—often by stripping weak comparables, changing the profit level indicator (PLI), or rerunning the search.
Quick Answer: The 15 Most Common Mistakes
The most common benchmarking mistakes are:
Poor screening documentation — no reproducible trail for how comparables were found and rejected.
Wrong PLI selection — PLI doesn’t match the tested party’s value driver.
Inflated sample size with weak comparables — quantity over quality makes the range fragile.
Ignoring working capital adjustments — material working capital differences go unadjusted (or unexplained).
Outdated benchmarking studies — stale searches/financials don’t reflect the tested year’s conditions.
Wrong database or market — scope doesn’t fit the tested party’s market (or local expectations).
Mishandling loss-makers — blanket inclusion/exclusion without fact-based analysis.
Inconsistent multi-year analysis — mixing year-by-year and multi-year outcomes inconsistently.
Shallow functional analysis — boilerplate FAR that doesn’t support method/PLI/comparables.
Bad quantitative filter design — thresholds/sequence create false positives or arbitrary exclusions.
Unjustified method selection — “TNMM by habit” with no documented best-method rationale.
Missing non-WCA comparability adjustments (or rationale not to adjust) — known differences are ignored.
Benchmarking doesn’t match the actual story — transaction description, segmentation, and conduct don’t align.
These mistakes aren't hypothetical—they're routinely found in audits and have triggered significant adjustments. Addressing them before submission dramatically improves defensibility.
Mistake #1: Poor Screening Documentation (Reproducibility of the Search Process)
What it is: Failing to document the search and screening process for comparables in a way that is transparent, systematic, and verifiable. The study shows 10 final comparables but no record of the dozens of companies considered and rejected—meaning an auditor cannot reproduce how you got from the database to the final set.
Why it happens: Practitioners treat the search process as internal workpapers and only include results in the report. Time pressure or lack of a standardized process leads to skipping detailed documentation.
Tax authority reaction: Lack of screening documentation is a major red flag. HMRC notes that transfer pricing documentation is often "too high level" and insufficiently evidenced, making it impossible to confirm an arm's length result. The IRS expects sufficient documentation to show you reasonably selected and applied the best method—and that you can produce it quickly in audit. Weak support for comparable selection increases audit burden and invites extensive Information Document Requests asking for details you should have documented upfront.
Warning
Audit Risk: If you cannot show which companies were rejected and why, auditors may suspect you excluded companies arbitrarily to manipulate the outcome. The credibility of the entire study collapses.
How to fix it:
Document every step of your comparables search
Record database query parameters: keywords, NAICS/NACE codes, geographic scope, financial screens, date of search
Create an accept/reject matrix listing all companies that passed initial filters with your decision and reason for each
Ensure reasons are specific: "Reject – persistent losses," "Reject – >25% related-party sales," "Accept – functionally similar distribution services"
The matrix demonstrates a diligent, consistent process and can save hours in audit by proving you applied criteria systematically.
Mistake #2: Wrong PLI Selection
What it is: Choosing an inappropriate Profit Level Indicator for the tested party's business model. Using Return on Assets for a distributor with minimal assets, or Operating Margin when pass-through costs dominate.
Why it happens: PLI selection is sometimes done by rote ("we always use operating margin") or based on what makes the tested party look better. A shallow functional analysis contributes—if you haven't truly understood the tested party's value drivers, you'll pick a PLI that doesn't capture them.
Tax authority reaction: Using the wrong PLI attracts immediate auditor criticism. IRS regulations emphasize that the PLI should "provide the most reliable measure of an arm's-length result." Auditors may recompute your analysis with a different PLI—and if that yields a different result, expect an adjustment.
Note
PLI selection should follow the facts and circumstances of the delineated transaction. Operating margin is common for routine distributors where sales are a sensible base; net cost-plus is common where costs are the better proxy for value creation; return-on-assets-type indicators are more plausible in asset-intensive cases; and Berry ratio is appropriate only in relatively narrow intermediary/service cases where operating expenses reliably proxy value added and the result is not materially driven by the value of goods or other significant functions.
How to fix it:
Perform rigorous functional analysis first—identify what drives profits
If the tested party uses few tangible assets, avoid ROA
If substantial pass-through costs exist, consider Berry Ratio (document conditions)
Cross-check by testing different PLIs as a sensitivity analysis—if the choice alone is the difference between in-range and out-of-range, investigate
Mistake #3: Inflated Sample Size with Weak Comparables
What it is: Including too many comparables, some of which are poor quality matches, just to have a "big sample." Valuing quantity over quality.
Why it happens: Practitioners believe larger samples are inherently more defensible. Some include marginal comparables to ensure the tested party falls within range—padding the set with low- or high-margin companies to widen it. The "if in doubt, include it" approach leads to bloated sets where comparables aren't truly comparable.
Tax authority reaction: Tax authorities prioritize quality over quantity. Courts have consistently upheld authorities rejecting weak comparables from taxpayer sets—even when this reduces the sample size significantly. The underlying principle: a smaller set of truly comparable companies is more reliable than a larger set with "apples and oranges." The IRS FAQs explicitly encourage stress-testing your set by removing one comparable and seeing what happens—if your result hinges on a single company, the set isn't reliable.
How to fix it:
Focus on comparability, not count—6 excellent comparables beat 15 marginal ones
Use financial consistency checks: persistent losses, extremely high margins, erratic results all warrant investigation
Create a "quality scorecard" evaluating how closely each matches on industry, functions, market, size, asset intensity
Test: if removing one comparable changes your outcome from in-range to out-of-range, your set is too volatile
There's no regulatory "minimum 10" rule. Small sets are not automatically invalid; reliability matters more than a target count. Strive for a sample where you could defend each company individually in front of an auditor.
Mistake #4: Ignoring Working Capital Adjustments
What it is: Failing to perform working capital adjustments when comparables have materially different levels of receivables, payables, or inventory than the tested party. These differences affect profitability—a company carrying large receivables has financing costs that lower reported profit.
Why it happens: WCAs can be complex and are sometimes viewed as optional. Practitioners skip them to avoid complication or assume the impact is immaterial. In other cases, balance sheet data isn't readily available. Practice is inconsistent: some treat WCA as standard, others as "rarely needed."
Tax authority reaction: Working capital differences are a recognized comparability factor. The OECD and many local regulations acknowledge that where payment terms or inventory differ and impact pricing, adjustment can improve comparability. In some audits (particularly in India), authorities may compute WCAs even if the taxpayer did not. If the tested party's working capital is an outlier, auditors will ask why no adjustment was made.
OECD does not treat working capital adjustments as routine or mandatory; they should be made only where they are expected to improve reliability and can be computed on a sufficiently reliable basis.
How to fix it:
Assess working capital profiles early: compare DSO, days payable, and inventory days between tested party and comparables
Define a materiality threshold (e.g., "if differences in DSO exceed 30 days, consider adjustment")
When adjusting, use a consistent formula and reasonable interest rate
If you decide not to adjust, document why: "WC levels are within the range of comparables (all DSO 60–75 days), so no adjustment was made"
What it is: Relying on old or stale comparables for current-year transfer pricing without proper updates. Reusing the same set for multiple years under the assumption that "nothing has changed."
Why it happens: Benchmarking studies are time-consuming and costly. The OECD notes that some tax administrations may accept refreshing the comparables search every three years, with annual financial data updates in between. But this isn't a universal safe harbor—economic conditions change (recessions, booms, pandemics) and comparables can drift (acquired, diversified, defunct).
Tax authority reaction: Many tax authorities expect annual, contemporaneous documentation. While comparables searches might not be redone every single year if facts are constant, very old studies are viewed with suspicion. The IRS expects analysis reflecting the economic conditions of the tax year in question—especially after events like COVID-19. Tax authorities may conduct their own fresh search and find different results.
Warning
Post-COVID Alert: Studies based on pre-2020 data applied to 2020-2022 results are especially vulnerable. Economic volatility means comparability requires year-specific judgment.
How to fix it:
Update financials annually at minimum; conduct a full re-search every 3 years (or sooner if material changes occur)
Confirm existing comparables are still valid each year (still independent? still in same business?)
If operating conditions are unchanged, document that: "Screening of database as of 2025 did not identify new companies meeting criteria. The industry and functions remain consistent, so prior comparables were retained with updated FY2024 data."
Always use the latest available financial data for comparables
Mistake #6: Using the Wrong Database or Market
What it is: Conducting the comparables search in a database not appropriate for the transaction's geographic or industry context. Using only foreign comparables when local ones are available and preferred.
Why it happens: Convenience or subscription access—the analyst uses whichever database they have, even if it's not ideal for that region. Many countries have a preference or requirement for local market comparables, and ignoring this creates risk.
Tax authority reaction: In practice, some tax authorities may prefer local comparables where reliable local data exists—especially when market conditions are likely to differ materially. If your scope is misaligned (e.g., using only foreign comparables with no documented attempt to identify local candidates), expect questions and a potential re-run of the search by the auditor.
For an Indian tested party, there is no explicit statutory domestic-only rule, but using only foreign comparables without showing why economic circumstances are comparable increases challenge risk.
Start with the market scope that best reflects the economically relevant circumstances and local practice. Domestic comparables may be preferable where they are more reliable or locally expected, but a blanket local-only rule is not universal
If you expand to regional or foreign comparables, explain why those markets are sufficiently comparable
Document steps taken to find local comparables (even if none found): "Searches for domestic comparables were conducted. In [Country], data on independent companies providing XYZ services is scarce; therefore, regional comparables were used with adjustments as necessary."
Mistake #7: Mishandling Loss-Making Comparables
What it is: Improper inclusion or exclusion of comparables solely based on whether they have losses. This manifests two ways: (a) automatically excluding all loss-makers without analysis, even if losses reflect normal business cycles, or (b) including a loss-maker whose losses stem from extraordinary circumstances unlike the tested party's situation.
Why it happens: Loss-makers are contentious. Some practitioners take a "reject all losses" rule of thumb, believing independents don't persistently sell at losses (not always true). Others include loss-makers to defend a low margin without checking why the loss occurred. Without clear guidance, firms default to convenience or bias.
Tax authority reaction:OECD Guidelines explicitly state that you should not reject a comparable solely because it has losses (). Recent case law reinforces this: the Italian Supreme Court (Decision No. 19512, July 2024) ruled that loss-making comparables cannot be excluded just for being in loss—the reasoning must be economic, not automatic. Colombia's Council of State (2024) similarly clarified that a single year of loss doesn't justify exclusion unless losses are recurrent or signal materially different economic conditions.
Note
The Principle: Investigate the circumstances. Ask: Do losses reflect normal business volatility, or abnormal conditions (bankruptcy, restructuring, speculative strategy)? Document your reasoning for each loss-maker.
How to fix it:
Evaluate loss-making comparables on their merits
Ask: Is the loss due to normal industry downturn (include) or extraordinary circumstances (investigate/exclude)?
Are losses recurrent or a one-year dip? Single-year losses within a multi-year period may not warrant exclusion
If excluding, document why: "Company X rejected—two years of significant losses (30% negative margins) resulted from major restructuring, not reflective of routine operations or tested party's risk profile"
Don't apply blanket "Profit > 0" filters without secondary review
Mistake #8: Inconsistent or Improper Multi-Year Analysis
What it is: Inconsistency in using multi-year data—such as averaging multiple years of comparables data but testing the single-year result of the tested party. Or cherry-picking years for different companies without adjusting approach.
Why it happens: Practitioners automatically average three years of comparables data without realizing some tax authorities require year-by-year analysis. Others average because it makes the tested party look better (diluting one bad year). Inconsistencies arise when data availability varies—instead of dropping comparables, analysts average whatever is available for each.
Tax authority reaction: Consistency is universally expected. The Canada Revenue Agency explicitly states that arm's length pricing should be established year by year, not by averaging multiple years. If you mix single-year and multi-year data, auditors will flag it as methodological flaw. If your analysis masks a non-compliant year through averaging, the IRS will still target that year.
How to fix it:
Determine local expectations: does the tax authority prefer year-by-year or allow multi-year averaging?
Be consistent: if averaging comparables over three years, also consider the tested party's three-year average (as supplemental, not replacement)
Keep data alignment: use the same three years for all comparables and the tested party
Address missing data: if one comparable lacks a year, either exclude it or analyze it separately—don't silently let each have different denominators
Don't average away non-compliance: if one year is outside range, explain it rather than hoping averaging will mask it
Mistake #9: Shallow Functional Analysis
What it is: Providing a superficial functional analysis that doesn't adequately distinguish the tested party's profile or support the choice of comparables and method. Generic sentences like "Company A is a distributor that performs marketing and sales functions" that could describe any distributor anywhere.
Why it happens: Some view functional analysis as compliance formality and reuse boilerplate. If the preparer doesn't engage with operational teams, they can't gather nuanced information. Time constraints lead to cutting corners. Template-based or AI-generated outputs can be generic.
Tax authority reaction: Auditors place huge importance on functional analysis—it's often the first thing they read. The IRS has criticized taxpayers who present just a "functional analysis checklist" without connecting it to the transfer pricing method. HMRC notes common issues include analysis being too high-level or one-sided (not analyzing both sides of the transaction). A shallow functional analysis undermines confidence in the entire study.
How to fix it:
Invest time in a thorough functional analysis—it's the backbone of your study
Gather information from people who know the business: operations, finance, supply chain
Cover all five comparability factors: functions performed, assets used, risks assumed, contractual terms, economic conditions
Describe not just what functions are performed but how and their significance
Link functional analysis to your benchmarking choices: "Because the entity does not assume significant product liability risk, a routine cost-plus margin is appropriate, and comparables were chosen accordingly"
Perform a two-sided analysis: at least acknowledge what the counterparty does
Tip
The Test: Read your functional analysis aloud. If it could apply to any company in your industry, it's too generic. Add specific facts about this tested party.
Mistake #10: Incomplete Accept/Reject Matrix (Completeness and Internal Consistency)
What it is: Having an accept/reject matrix that is incomplete or internally inconsistent—missing key elements even when the search process itself was documented. The matrix might omit reasons for rejection, not list all companies considered, lack important fields (turnover, RP percentage), or show contradictions between stated criteria and actual accept/reject decisions.
Why it happens: Preparing a comprehensive matrix is tedious. Practitioners assume a narrative description suffices, or fear listing every rejected company gives auditors a roadmap to second-guess each exclusion. Sometimes it's oversight—the team screened internally but didn't document every step in the report.
Tax authority reaction: An incomplete matrix raises questions: What are you hiding? Did you apply criteria consistently? A narrower example exists in Israel: under the 2025 ITA circular for qualifying local R&D cost-plus arrangements, taxpayers seeking the circular's treatment must attach a TP study including a DEMPE analysis and benchmarking with an accept/reject matrix to the annual return. This is a specific regime, not a general rule for all Israeli TP documentation—but it illustrates how some administrations are formalizing matrix expectations. If only aggregate stats are given ("we excluded 10 companies due to losses"), auditors will ask you to name them and prove it.
How to fix it:
Include a detailed accept/reject matrix in your study
At minimum, list: each company that passed initial quantitative filters, whether accepted or rejected, and reason for rejection
What it is: Treating companies as “independent” when they have material related-party links, related-party transactions, or are part of a group that influences pricing. This can happen through superficial ownership screens, overreliance on a single database flag, or not validating independence during manual review.
Why it happens: Independence filters are easy to apply mechanically, but hard to apply correctly. Data can be incomplete, and “independence” indicators differ by database. Time pressure pushes teams to accept database labels at face value.
Tax authority reaction: If a comparable is shown to be non-independent, it can be removed—sometimes along with other companies screened using the same weak logic. That undermines the set and your screening credibility.
How to fix it:
Treat independence as a two-step test: (1) database/ownership screen, (2) manual validation using available disclosures
Document the independence criteria you used (ownership/control indicators and any related-party sales/purchases screens)
Re-validate independence during annual updates (ownership can change)
If independence data is imperfect, document what you checked and the limitations
Mistake #12: Bad Quantitative Filter Design (Thresholds and Sequence)
What it is: Applying quantitative filters (industry codes, size, profitability, data availability, independence) in a way that creates arbitrary exclusions, inconsistent denominators, or a biased candidate pool. Common symptoms include overly tight size filters, profitability screens applied too early, or inconsistent data availability requirements.
Why it happens: Filters are often copied from prior studies without checking whether they fit the tested party and data universe. Teams also confuse “efficient” with “defensible,” optimizing for speed rather than a transparent, reproducible funnel.
Tax authority reaction: If your quantitative screen looks arbitrary—or if it appears designed to force an outcome—auditors will rerun it with different thresholds and argue your set is unreliable.
How to fix it:
Use a broad-to-narrow sequence and document the company counts remaining after each step
Avoid early-stage “outcome filters” (e.g., strict profitability thresholds) unless you can defend why they’re economically required
Make data availability rules explicit (years required, treatment of missing years)
Tie each threshold to an economic rationale (not “firm policy”)
Mistake #13: Unjustified Method Selection (“TNMM by Habit”)
What it is: Selecting TNMM (or another method) by default without documenting why it’s the most appropriate method given the accurately delineated transaction, available data, and the reliability of internal vs external comparables.
Why it happens: TNMM is often practical with public data, so teams treat it as the default. But “practical” isn’t the same as “most appropriate,” and tax authorities expect to see the reasoning chain.
Tax authority reaction: If the method choice is weak, authorities may recharacterize the analysis (e.g., different method, different tested party, different PLI), which can cascade into a different outcome.
How to fix it:
Document the “best method” logic: what alternatives were considered and why they were less reliable
Before defaulting to TNMM, document whether internal comparable transactions or agreements were reviewed and why they were or were not reliable
Connect method selection to functional analysis and the availability/reliability of data
Ensure the tested party choice is consistent with the method’s logic
What it is: Recognizing material differences (capacity utilization, accounting classification, risk profile, or other structural differences) but either not adjusting—or adjusting inconsistently without explaining the impact.
Why it happens: Beyond working capital adjustments, many adjustments require judgment and extra analysis, so teams either skip them or apply them selectively. Sometimes the issue is documentation: the team did consider adjustments, but never wrote down why they were immaterial.
Tax authority reaction: If differences are obvious and unaddressed, auditors can argue your set isn’t comparable, remove companies, or substitute their own adjustments.
How to fix it:
Make an explicit “adjust or explain” step part of your process
Identify the largest comparability gaps and either (a) adjust, (b) exclude the company, or (c) explain why the impact is immaterial
Apply adjustment logic consistently across the set (no one-off tweaks)
Mistake #15: Benchmarking Doesn’t Match the Actual Story (Documentation Coherence Failure)
What it is: A disconnect between the narrative (transaction description, functional analysis, risk allocation) and the benchmarking mechanics (tested party, segmentation, PLI definition, financials used). For example: the report describes a “routine, low-risk distributor,” but the financial segmentation includes non-routine revenue streams or includes/excludes costs inconsistently with the chosen PLI.
Why it happens: Different teams own different parts of the file. Functional analysis is written from interviews, the benchmark is built from database work, and financial segmentation is done separately—without one person reconciling the full story end-to-end.
Tax authority reaction: Inconsistencies are easy audit wins. They trigger follow-up questions, broader information requests, and reduce trust in the whole analysis—even if the numbers are otherwise reasonable.
How to fix it:
Reconcile the chain: transaction → delineation → tested party → method/PLI → segmentation → comparable set → range test
Ensure PLI numerator/denominator definitions match how the tested party’s financials were prepared
Add a short “coherence check” section explaining how segmentation ties to the functional profile
Before finalizing a benchmarking study, run through this checklist to catch weaknesses before an auditor does.
A. Methodology & Scope
Tested Party Selection: Clearly identified the party to which the method can be applied most reliably and for which the most reliable comparables can be found (often, but not always, the less complex party)?
Most Appropriate Method: Considered multiple methods and documented why selected method is best?
PLI Selection: PLI consistent with functional profile (OM for revenue-driven, NCP for cost-driven, etc.)?
Multi-Year Analysis: Analyzing results yearly as authorities prefer? If using averages, applied consistently?
Range Determination: Explained the range approach required or preferred in the relevant jurisdiction, including whether any statistical tool is appropriate at all, and if so why?
Comparability Adjustments: Identified needed adjustments (WCA, capacity, accounting) and either made them or documented why not?
B. Comparable Selection & Screening
Database Choice: Using appropriate database for geography and transaction type?
Search Documentation: Documented search criteria (codes, keywords, filters, date of search)?
Accept/Reject Matrix: Comprehensive list of screened companies with reasons for each rejection?
Consistency: Applied criteria uniformly—if rejecting one company for X, rejected all failing that threshold?
Rejection Validity: Reasons aligned with comparability factors, not arbitrary?
Current Data: Used latest available financial data? No multi-year gaps?
C. Functional & Risk Analysis
Depth: Functional analysis contains specific details, not just boilerplate?
Two-Sided: Considered both sides of the transaction?
Risk Analysis: Clearly delineated which risks tested party bears vs. doesn't?
Link to Profit: Narrative connects functions/risks to expected profit level?
Comparables Alignment: Selected comparables perform similar functions and bear similar risks?
D. Financial Results
Tested Party PLI: Correctly calculated with appropriate inclusions/exclusions?
Adjustments Documented: WCA and other adjustments clearly shown with methodology?
Sensitivity Checks: Removed one comparable to test if outcome changes drastically?
Results Explanation: Explained where tested party falls in range and why?
E. Documentation Quality
Citations: External sources cited and credible?
Internal Consistency: All pieces tie together—functional analysis supports method, method supports comparables?
Local File Compliance: Covers all required points for applicable jurisdictions?
Clarity: Written so a tax inspector can follow without internal jargon?
Tax Authority Focus Areas
Understanding what tax authorities scrutinize helps you preempt problems:
United States (IRS)
Heavily focused on accuracy and completeness of documentation
Expects "best method" rule diligence—did you consider all methods?
Scrutinizes functional analysis and risk allocation
Common audit triggers: sustained losses, sudden profit changes, intangibles transfers
United Kingdom (HMRC)
Criticizes documentation that's "too high-level"
Expects two-sided functional analysis
Focuses on whether UK entity is adequately compensated for functions performed
May challenge results at an extreme point of the range without strong justification—and may argue for a central tendency
Germany (BMF)
Strong emphasis on documentation quality and comparability support
Germany's framework provides for the interquartile method and comparability adjustments where needed
Scrutinizes market differences if using pan-European comparables for German entity
From 2025, in a tax audit, the master file, transaction matrix, and extraordinary-transaction documentation must be submitted within 30 days of the audit order without separate request; the local file is submitted upon request within 30 days
Extraordinary-transaction documentation must be prepared within six months after year-end
India
India has no explicit statutory preference for domestic over foreign comparables
Transfer pricing rules allow an arm's-length range where the most appropriate method is not PSM/Other Method and the dataset includes six or more comparables; in that case the prescribed range runs from the 35th to the 65th percentile, with the median used if the tested result falls outside that range
Comparability adjustments are permitted where they can be made reliably and accurately
TPOs conduct own searches and commonly challenge taxpayer comparable sets
What's the single most common benchmarking mistake?
Insufficient documentation of the comparables selection process—essentially, poor or missing support for why certain comparables were chosen and others rejected. Tax authorities consistently complain about documentation that shows final outcomes without the trail. When rationale isn't clear, it raises suspicions of cherry-picking. This is one of the most prevalent issues and, fortunately, one of the easiest to fix: an accept/reject matrix is best practice and often audit-essential, even where not a universal legal requirement.
How often should I update my benchmarking study?
Refresh comparable financial data annually and confirm the set still fits the tested year. The OECD notes that some tax administrations may accept refreshing the database search every three years where operating conditions are unchanged, with annual financial updates for the comparable set. However, a full re-search should be done sooner where facts, markets, or local rules require it. Given recent volatility (COVID, supply chains, inflation), older studies may not reflect current arm's length conditions.
What are common risk indicators for a transfer pricing audit related to benchmarking?
Common risk indicators include: (1) consistent losses or low profits without clear reason, (2) significant year-on-year profit swings after reorganization, (3) large related-party transactions relative to overall business, (4) payments to low-tax jurisdictions, (5) industries or transaction types under regulatory focus (pharma, tech, intangibles), and (6) poor documentation quality from prior years—which signals higher risk. These are practitioner-observed patterns, not a formal universal trigger list published by any single authority.
Can I reuse the same benchmarking study for multiple years?
You can reuse elements, but don't copy-paste without updating. At minimum, update financials each year and check if comparables are still valid (not acquired, diversified, or defunct). If nothing significant changed, you might carry the same set for 2-3 years—but document that you reviewed and determined it still appropriate. Be cautious: if audited in Year 3, authorities will examine whether Year 3 conditions match Year 1's.
What if my comparable set is small (fewer than 5 companies)?
Small sets aren't automatically rejected—reliability matters more than a target count. Document thoroughly why more couldn't be found and whether additional adjustments are needed. If the set is genuinely robust, defend it confidently. However, if a single comparable drives your outcome, that's a vulnerability—consider whether you've applied filters too aggressively.
How do I know if my comparables are "good enough"?
Signs of a solid set: (1) they truly mirror the tested transaction's functional and risk profile, (2) no single comparable drives the outcome—removing one doesn't drastically change the range, (3) quality over quantity—each is defensible on its own, (4) consistent data across all (same years, same PLI denominator definitions), (5) no glaring differences unaddressed (different business models, persistent losses, different country). If defending any single comparable makes you uncomfortable, it probably doesn't belong.
What do tax authorities expect to see in documentation?
A complete local file analysis, including: (1) clear description of controlled transactions, (2) detailed functional analysis (FAR), (3) explanation of method chosen and why appropriate, (4) selection of comparables with search criteria and accept/reject summary, (5) comparables data with company descriptions and financials, (6) any comparability adjustments made, (7) arm's length range and how tested party compares, (8) conclusion on arm's length compliance. Documentation should allow an auditor to reproduce and understand your analysis step by step.
Related OECD Guidance
The OECD Transfer Pricing Guidelines provide comprehensive guidance on avoiding benchmarking mistakes:
Borys UlanenkoCEO of ArmsLength AI
