Direct Answer: What Related-Party Pricing Evidence Proves
Related-party pricing evidence is the collection of records used to show that a transaction between related entities was priced on terms that could have been agreed between independent parties. In practice, it usually includes the related-party agreement, invoices and payment records, a transfer-pricing policy or comparables analysis, board or management approvals, and evidence that the stated price was actually implemented. The evidence should connect the commercial terms—such as price, margin, royalty rate, service fee, interest rate, or cost reimbursement—to the economic ownership of goods, functions, assets, risks, and intellectual property.
Also worth reading: What is the definitive chargeback representment evidence checklist for merchants? · How Does an Interchange-Plus Pricing Calculator Work for Merchants in 2026? · How Do International Transfer Pricing Rules Affect Cross-Border Digital Businesses?
As of 27 September 2026, the central question is not merely whether a buyer and seller are related. Tax authorities want to know whether the relationship affected the amount charged and whether the company can support its arm’s-length position. A contract can describe an arm’s-length price, but the contract alone is weak evidence if payments differ from the contract, third-party data conflict with the chosen price, or the company cannot explain why its method was appropriate.
For payment, wallet, and merchant-service businesses, the same principle applies to intercompany software licenses, payment-processing fees, platform commissions, technical-service charges, and cost-sharing arrangements. Digital businesses should not assume that a percentage fee is defensible simply because it appears in an internal agreement. They need a contemporaneous method, reliable inputs, and a traceable explanation of how the charge was calculated and collected.
| Evidence item | What it should establish | Common weakness |
|---|---|---|
| Related-party agreement | Agreed services, pricing formula, duration, and payment terms | Signed after pricing began or conflicts with invoices |
| Pricing policy or study | Method, comparables, assumptions, and arm’s-length result | Prepared years after the transaction |
| Invoices and ledgers | The price was actually billed and paid | Round figures without a calculation trail |
| Third-party comparables | External market context | Weak sample, obsolete period, or unexplained adjustments |
| Approvals and board minutes | Commercial acceptance and governance | Generic approval with no pricing discussion |
Testing normally begins by identifying the relationship and defining the transaction accurately. Related parties can include parent companies, subsidiaries, common-control entities, owners, directors, family members, and entities controlled through contractual or economic arrangements. The exact legal definition varies by jurisdiction, so a group-level relationship should not be used as a substitute for checking the relevant local rules. Vietnam, the United Arab Emirates, Malaysia, and other jurisdictions featured in current compliance discussions all place some form of documentation or scrutiny on related-party transactions.
The next step is to reconstruct what each party contributed. An intercompany payment-processing agreement, for example, should distinguish the acquiring service, settlement activity, fraud screening, merchant support, working-capital funding, and access to proprietary software. A fee of 2.5% may be plausible for one bundle of services but not another if the entities, risks, transaction volumes, or geographic coverage differ. The tax authority does not need to prove that every element was mispriced if the available evidence fails to support the price actually charged.
Several pricing methods may be used, depending on the transaction. A comparable uncontrolled price or transaction-based method examines external prices with economically similar products or services. Other methods reconstruct the expected profit from functions performed, risks assumed, and assets used, or apply a statutory rate to an appropriate tax base. The method matters less if it is unsuitable than if the company cannot explain why it was selected and consistently implemented it.
No single percentage, margin, or document guarantees acceptance. The result must reflect the facts of the specific year, including the parties’ commercial roles, the reliability of third-party data, and the consistency of actual performance. Evidence that looks persuasive on a slide but cannot be traced to contracts, invoices, accounts, and contemporaneous decisions is not audit-ready.
Building a Defensible Evidence File
A useful file starts with the legal and economic relationship, followed by the transaction inventory. Each arrangement should have a clear owner, description, effective date, value, currency, tax treatment, and connection to the wider group structure. For a digital-payments group, this could include merchant acquiring, wallet issuance, payment orchestration, fraud services, software development, data processing, and brand or license charges. Values should reconcile to monthly invoices, general-ledger entries, tax returns, and statutory accounts, ideally within normal rounding differences such as less than 1% for aggregate reconciliations.
The pricing memorandum or policy should then state the method, source data, date, and adjustments. External benchmarks should be checked for comparability in product, geography, customer type, volume, payment method, service quality, and contractual protections. Private database figures may have commercial confidentiality restrictions, so a company may need to describe the data source while submitting the underlying records under controlled access. The analysis should explain exclusions rather than quietly removing inconvenient observations.
Finally, the evidence should prove implementation. Signed agreements are useful only when the pricing formula appears in invoices, the formula can be recalculated, and payments follow the stated schedule. Deviations should be documented with a commercial reason, approval, and, where needed, a corrected invoice. A group can spend months preparing a study while continuing to invoice customers under an unstudied legacy rate, weakening the value of the work.
| Build stage | Practical record | Suggested timing |
|---|---|---|
| Transaction identification | Contract, group chart, service description, annual value | Before the pricing period or within the first quarter |
| Benchmarking | Third-party data, quotations, comparable margins | Annually, with a post-year-end review |
| Approval | Board or management decision with versioned attachments | Before material invoices are issued |
| Implementation | Invoice calculation, ledger reconciliation, payment proof | Monthly or quarterly |
| Monitoring | Exception report and corrective-action log | Quarterly; annually for a full refresh |
One frequent mistake is treating a related-party agreement as conclusive. An agreement is evidence of the parties’ stated intention, but it is not necessarily evidence that the price is arm’s length. Auditors often compare the contract rate with invoices, payment records, third-party quotations, and the company’s own pricing to unrelated customers. A memorandum that describes a 3% processing fee while invoices show 3% for one period and 4.5% after an undocumented change invites questions about when the policy became effective and why.
Another error is using a benchmark without adjustments. Two payment processors can both describe a “platform fee,” yet one assumes merchant-acquiring risk, supports chargebacks, provides local settlement, and carries regulatory costs while the other performs only software access. Comparing headline rates without controlling for those differences can make a supported price appear unsupported. The evidence should show which factors were adjusted, how the adjustment was calculated, and whether the selected range is still reasonable after rounding or exclusions.
Documentation timing is also important. A study prepared four years after a transaction may still contain useful data, but it is harder to establish that management actually relied on it when pricing decisions were made. Contemporaneous evidence is stronger because it connects the known commercial conditions at the time. The company should not backdate records, but it can create a reconstruction that identifies missing information, explains limitations, and compares the result with what was actually billed.
Finally, a company may mistakenly assume that losses, temporary losses, or favorable results eliminate transfer-pricing risk. A loss can be accepted if it reflects a genuine commercial profile and can be tested against comparables, but it is not automatically justified by “building a customer base.” Similarly, a high royalty may be defensible for valuable intellectual property, but a general percentage fee is not a substitute for evidence about ownership, development history, useful life, and economic benefits.
Comparing Strong, Moderate, and Weak Evidence
Strong evidence is not merely extensive; it is coherent. A contract, pricing memorandum, external benchmark, invoice sample, ledger reconciliation, and approval record should tell the same story about the same transaction and period. The record should show why the method fits the business and how the final number was reached. Strong files also address contrary facts, such as customer discounts, volume rebates, exceptional service costs, or changes in risk.
Moderate evidence may support the company but leave a reasonable question unanswered. For example, a group may provide a three-year pricing policy, two external comparables, and a list of related transactions without reconciling them to the general ledger. The evidence may be enough for preliminary review, but an auditor could request a better bridge between the policy and actual invoicing. This category is common in growing payments businesses where procedures have not yet been standardized across entities.
Weak evidence relies on labels, isolated rates, or retrospective assumptions. Statements such as “the fee is market rate” without a source, a contract with no pricing formula, or a study that does not mention the actual year and service are unlikely to withstand closer examination. Even weak evidence is worth organizing, because a documented gap is more honest than presenting assumptions as facts.
| Evidence quality | Typical contents | Likely tax-authority response |
|---|---|---|
| Strong | Contemporaneous agreement, method, comparables, approvals, invoices, reconciliation | Focused testing rather than broad reconstruction |
| Moderate | Several relevant records, but gaps in timing, comparability, or reconciliation | Follow-up requests and adjustment of unsupported differences |
| Weak | Unsupported rate, incomplete contract, retrospective narrative | Scrutiny, formal inquiry, or transfer-pricing adjustment |
A digital-payments company should start with a transaction map rather than a long legal argument. Identify every charge between group entities that affects pricing: interchange-like arrangements, processing fees, wallet float services, merchant-acquiring commissions, chargeback handling, software licenses, data services, technical support, and funding costs. For each charge, record the amount charged, amount paid, currency, invoice frequency, service period, and responsible accounting owner. A 0.3% difference may look small, but across high transaction volumes it can become material; the file should therefore show both percentage rates and absolute annual amounts.
The company should test whether the payment flow matches the pricing narrative. A seller entitled to a fixed monthly platform fee may not have earned that fee if actual services were not provided or were performed by a different entity. Conversely, services bundled into a simple rate can be valid if the commercial arrangement is clear and the group can explain the allocation. The review should also examine whether payment terms, settlement delays, chargebacks, and currency risk were priced consistently across countries.
Costs matter when an analysis is commissioned. External transfer-pricing studies, database licenses, local tax advice, and legal support can range from several thousand dollars for a limited review to tens of thousands or more for multiple entities, countries, and complex intellectual-property ownership. A company can reduce cost by preparing complete contracts, invoices, ledgers, and descriptions before consulting an adviser, but it should not buy a generic report that omits the underlying calculations. A low-priced document is not economical if it creates a larger adjustment or cannot be defended in an audit.
| Review approach | Indicative effort | Best use |
|---|---|---|
| Internal screening | 1–3 staff weeks | Identify missing contracts and reconcile amounts |
| Single-country focused review | Several thousand dollars | One material related-party arrangement |
| Multi-entity group study | Often tens of thousands of dollars | Several jurisdictions or high-value IP and service flows |
| Ongoing monitoring | Monthly data plus annual update | Payment volumes and product lines change frequently |
When to Act and When to Accept Uncertainty
A company should act promptly when a related-party arrangement is material, lacks a signed agreement, uses a rate that has not been reviewed, or changed recently. New products, acquisitions, new legal entities, revised payment terms, and expansion into another country are natural control points. A trigger does not always mean the current price is wrong; it means the company should determine whether a new study, amended agreement, invoice correction, or documented explanation is needed. Quarterly monitoring is usually sensible for high-volume payments because transaction values can change faster than annual corporate documents.
There is no universal threshold in every jurisdiction that makes a transaction immaterial. Companies should nevertheless set internal thresholds based on exposure, risk, and administrative capacity. As a practical screening rule, any related-party item representing 5% or more of a segment’s annual expenses deserves a documented review, while a lower percentage can still require attention if it involves intellectual property, a tax rate, a permanent establishment risk, or a new jurisdiction. These percentages are internal decision aids, not legal safe harbors, and should be adapted after local advice.
Waiting is reasonable when the arrangement is minor, stable, fully documented, and clearly below the group’s risk threshold, provided the company continues to monitor it. Waiting is less defensible when the company is preparing for an audit, negotiating a tax settlement, changing ownership, or discovering inconsistent historical invoices. A later review can quantify exposure and identify corrective action, but it cannot replace evidence that was never created. A business should therefore act when the gap becomes visible rather than wait for an authority to ask about it.
A Practical Decision Standard in 2026
The best test is whether an independent reviewer could follow the pricing story without relying on unexplained expertise. That reviewer should be able to identify the related parties, understand the transaction, see the arm’s-length method, recalculate the invoice, compare the result with external evidence, and confirm that the price was approved and implemented. The file need not disclose every confidential customer detail, but confidentiality protections should not be used to conceal the method or basic calculation.
For 2026 compliance work, prioritize the highest-risk items first: intellectual-property charges, intercompany financing, cross-border service fees, payment-processing allocations, and arrangements where actual invoices differ from the policy. Obtain current local guidance because transfer-pricing rules, documentation thresholds, and audit practices can change. The 27 September 2026 date should guide the review period, not be treated as a universal legal deadline, and the company should distinguish clearly between facts it has verified and assumptions requiring professional confirmation.
The conclusion is measured rather than absolute. Related-party pricing evidence is valuable because it reduces uncertainty, creates accountability, and can preserve a transaction during a review; it does not guarantee acceptance by any tax authority. In digital payments, where margins may be expressed in fractions of a percent and transaction values are large, a small unsupported adjustment can scale quickly. The right response is a documented, current, and internally consistent evidence trail, supported by methods that match the real commercial arrangement.