Intra-group stablecoin payments: how do you build a defensible transfer-pricing policy?
A group may use a stablecoin to accelerate internal settlement, reduce certain banking frictions or operate outside conventional market hours. Yet the payment rail does not answer the transfer-pricing question. A tax authority will first seek to understand the actual transaction: what each entity supplies, who controls the risks, who makes the decisions, what amount is due and why the consideration is arm’s length.
The analysis should therefore separate the underlying transaction — goods, services, royalties, financing, treasury activity or expense reimbursement — from the stablecoin settlement layer: asset, network, conversion time, fees, custody, foreign-exchange exposure and execution risks.
1. A stablecoin does not redefine the underlying transaction
A stablecoin transfer may settle an intercompany monetary liability when accepted under the contract. The amount discharged must nevertheless be established, including the effect of fees or a deviation from the peg. The payment method does not automatically turn a service into financing or a sale into a treasury activity.
It may nevertheless create additional steps and risks: acquiring the token, disposing of it on settlement, deviations from the reference value, network charges, conversion spreads or temporary custody by a group entity.
The documentation must therefore answer two separate questions. Is the price of the underlying transaction arm’s length? Have the costs and risks of digital settlement been allocated to the entities that actually control them?
2. Accurately delineate the transaction first
The OECD Guidelines require groups to identify the commercial and financial relations between associated enterprises and examine functions, assets and risks. For a stablecoin payment, the analysis should identify which entity:
selects the asset and network;
acquires and holds the tokens;
controls the keys or appoints the custodian;
determines execution timing;
bears conversion differences, fees and execution losses;
performs counterparty, sanctions and source-of-funds controls.
A contract allocating every risk to a subsidiary is not conclusive if the parent selects the wallet, provider, stablecoin and timing in practice. The entity’s financial capacity to bear the risk must also be assessed. OECD Chapter I, particularly paragraphs 1.86–1.98, considers contractual terms, actual conduct, control and financial capacity. These are general principles, not a stablecoin-specific rule.
3. Separate settlement, treasury services and financing
Direct settlement. The buyer acquires stablecoins and promptly pays the related company. The primary issue remains the price of the goods or services; conversion and network charges are settlement costs.
Treasury service. A central entity acquires, holds and distributes stablecoins for several companies. The group must determine whether it provides a routine service, performs a more substantive treasury function or controls risks requiring a distinct return.
Implicit financing. An entity advances stablecoins, retains a receivable or leaves a material balance outstanding. The arrangement may need to be analysed as financing, considering duration, currency, credit risk, security and arm’s-length remuneration.
The accounting label, or the token’s aim to maintain a stable value, does not determine the answer.
4. Build the price from observable evidence
The file should retain the transaction value in the invoicing currency and document how the token quantity was calculated. A robust policy specifies:
the pricing or conversion source;
the relevant timestamp;
the rule for a deviation from the reference value;
treatment of network charges and commissions;
differences between acquisition, transfer and final conversion;
the person authorised to approve exceptions.
Suppose one company owes another EUR 100,000 but settles with a US-dollar stablecoin. The file should separately evidence the EUR/USD conversion, the token’s USD price, the number of tokens transferred, fees and the value ultimately received. The on-chain token amount alone does not prove that EUR 100,000 was discharged.
5. Allocate fees and risks by reference to actual functions
Groups should avoid automatically assigning every fee to the payer or recipient. Allocation should reflect the operating model and the value of the activity performed.
If a treasury centre negotiates spreads, selects providers, sets limits and monitors wallets, a distinct return may be appropriate. If it merely executes standardised instructions without controlling significant risks, routine service remuneration may be more consistent. Where it provides funds, the financing analysis is separate.
OECD guidance addresses treasury functions, intra-group loans and cash pooling. It does not establish a stablecoin-specific transfer-pricing rule: applying those principles to a digital settlement rail remains fact-dependent.
6. Build an audit trail connecting contracts and blockchain records
A defensible transaction must be reconstructable without starting from a block explorer alone. The minimum file connects:
the intercompany agreement;
the invoice and business purpose;
the invoicing currency;
sending and receiving addresses;
network and transaction identifier;
token quantity and timestamp;
valuation source;
fees and spreads;
accounting entries in both entities;
approvals and compliance checks.
Tax, reporting, sanctions, AML and exchange-control rules remain jurisdiction-specific. Arm’s-length valuation does not establish that the payment is legally permitted.
Worked example: a settlement difference must not become an unexplained margin
Fictional facts: a French subsidiary owes a related company EUR 100,000. Their contract accepts digital settlement. At an agreed EUR/USD rate of 1.08 and an assumed USD 1 token price, the gross payment is 108,000 tokens. After USD 50 in charges, the beneficiary receives USD 107,950: dividing by 1.08 gives EUR 99,953.70, a EUR 46.30 shortfall.
The file must explain who bears the charges and whether the contract treats the debt as fully discharged. The difference alone does not establish a profit transfer. It does raise a transfer-pricing question if differences are allocated between related entities without economic support. The rates are teaching assumptions, not market quotes.
For the French entity, CGI Article 57 governs the adjustment of profits indirectly transferred to foreign associated enterprises within its conditions. Blockchain evidence does not replace support for the price, expense or intercompany service. OECD guidance does not replace national law, and the use of a stablecoin does not justify an automatic markup.
7. The BECTRA framework: eight policy decisions
Transaction — identify what is actually being paid.
Entities — define the payer, recipient and treasury-centre roles.
Asset — specify permitted stablecoins and networks.
Valuation — set sources, timestamps and exception rules.
Fees — allocate spreads, commissions and network charges.
Risks — assign risks to the entities that actually control them.
Evidence — connect invoices, ledgers, wallets and on-chain records.
Review — periodically reassess deviations, providers and regulatory change.
Conclusion
The principal risk is not the use of a stablecoin. It is treating settlement as a purely technical detail when it may shift functions, costs and risks among associated enterprises. A defensible policy keeps the underlying transaction at the centre, then documents the digital rail, valuation, governance and execution evidence separately.
Further reading
Sources
Sources checked on 21 October 2026. Stablecoin application and worked example: BECTRA analysis.
OECD — Transfer Pricing Guidelines, 2022, Chapters I, V, VII and X: Read the official source
Légifrance — French General Tax Code, Article 57, version dated 18 August 2026, consulted on 21 October 2026: Read the official source
French tax administration — BOI-SJ-RES-20-10, 15 April 2026, paragraph 10: Read the official source
Comments