--- title: "Crypto Transfer Pricing: BEPS, Arm's Length, and Common Audit Triggers (2026)" slug: crypto-transfer-pricing-beps publishedAt: 2026-05-10T09:00:00Z author: Finconduit Editorial Team tags: OECD, BEPS, GloBE canonicalUrl: https://finconduit.com/resources/crypto-transfer-pricing-beps --- # Crypto Transfer Pricing: BEPS, Arm's Length, and Common Audit Triggers (2026) Crypto transfer pricing under OECD Guidelines and BEPS — arm's length, DEMPE substance, the three core inter-company transactions, Master File / Local File / CbCR, Pillar Two, and the audit triggers. Transfer pricing is the largest tax\-**audit** risk in crypto group structures — and the area where most multi\-jurisdiction crypto firms run thinnest documentation. The [OECD Transfer Pricing Guidelines](https://www.oecd.org/tax/transfer-pricing/oecd-transfer-pricing-guidelines-for-multinational-enterprises-and-tax-administrations-20769717.htm) and the [BEPS Action Plan](https://www.oecd.org/tax/beps/) apply the same way to a **CASP** group with operating, holding, and IP entities as they apply to a Big Pharma group with R&D, manufacturing, and licensing entities. The difference is that crypto founders rarely come from a tax\-savvy background, treat **inter\-company** arrangements as paperwork, and attract disproportionate scrutiny from **tax authorities** reviewing offshore structures.¹[^1]²[^2] The pattern is consistent across **audits** in **Germany**, **France**, the **Netherlands**, and increasingly Italy and Spain. An EEA operating **CASP** pays a **royalty** to a **Cayman** or **BVI holding company** for **IP licensing** — without **DEMPE** substance in the holding entity. The **tax authority** denies the deduction, recharacterises the **royalty** as a profit shift, and applies a **transfer pricing** adjustment plus interest plus penalties. The original **15%** Cypriot tax structure becomes a **30%**\+ effective burden once the German **Bundeszentralamt für Steuern** is finished with the file. This guide explains crypto **transfer pricing** in plain language: what **arm's length** actually requires, the three transactions that show up in almost every crypto group \(IP **royalty**, **management fee**, **intra\-group** trading spread\), the documentation **tax authorities** expect \(**Master File**, **Local File**, **country\-by\-country reporting** under [BEPS Action 13](https://www.oecd.org/tax/beps/action13)\), the methods for setting prices, the common mistakes that trigger **audits**, the **GloBE** **Pillar Two** **15% minimum tax** for groups above **€750 million**, and the operational discipline that turns a defensible structure into one that survives a six\-figure **audit**.³[^3] ## What Transfer Pricing Actually Requires Transfer pricing applies whenever two associated enterprises \(companies in the same group\) transact across borders. The **arm's length principle** requires that the price charged in the **inter\-company** transaction equals what unrelated parties would have charged for the same transaction in comparable circumstances. The **OECD Transfer Pricing Guidelines** set the framework; each **EU** member state plus the **UK** transposes them into national law via specific **transfer pricing** legislation. For a typical crypto group with a **Lithuania**n operating **CASP** and a **Cayman holding** entity, three classes of **inter\-company** transaction need defensible **arm's length** pricing: royalties for IP licensed by the holding entity to the operator; **management fee**s for services the operator provides to the group; and **intra\-group** spread on crypto\-asset transactions where the group operates as principal across multiple legal entities. Get any of these wrong and the EEA **tax authority** will reallocate income to the operating entity, increasing taxable profits at the higher tax rate. > **Warning:** Tax authorities increasingly treat 'no documentation = no defence' as the default. Even an arm's length price that is genuinely arm's length will be challenged if the documentation is thin. Master File \+ Local File \+ country\-by\-country reporting must exist in approved form before the audit, not be produced in response to it. Plan for documentation as a continuous workstream, not an annual scramble. ## The Three Inter\-Company Transactions Every Crypto Group Has Audits cluster around three transaction types. Each requires specific **arm's length** analysis and specific documentation. None of them survive a serious **audit** on the strength of 'because we said so'. *Table: The three core inter\-company transactions in a typical crypto group — and what tax authorities probe.* | Transaction | Typical pricing approach | What auditors scrutinise | | --- | --- | --- | | IP royalty \(operating entity → holding entity\) | Royalty as % of revenue or % of operating profit | DEMPE substance in the holding entity; benchmark to comparable third\-party crypto IP licences \(rare data\); quantum of royalty vs operating margin | | Management fee \(parent → subsidiaries OR subsidiaries → parent\) | Cost\-plus 5–10% on documented services | Service substance — were the services actually rendered?; cost\-pool integrity; mark\-up benchmark; double\-counting with royalty | | Intra\-group trading spread \(between operating entities or between operator and treasury\) | Market\-comparable spread for the asset class | Whether the spread reflects real market data; whether the principal/agent characterisation is consistent; thin\-trading\-pair distortions | | Loan / financing \(cash\-pooling, intra\-group lending\) | Interest at credit\-rated benchmark | Implicit credit support from parent; thin capitalisation rules in the borrowing jurisdiction | | Free use of brand / customer data / trading algorithms | Should be a charged fee | Tax authorities increasingly probe 'free use' positions; un\-priced transfers are often deemed pricing transactions | ## **DEMPE** — The Substance Test for IP Royalties The **DEMPE** concept \(**Development, Enhancement, Maintenance, Protection and Exploitation**\) is the defining substance test for IP\-related **transfer pricing**. The **OECD Guidelines** require that the entity earning the bulk of IP\-related profit must perform the **DEMPE** functions — not just hold legal title to the IP. A **Cayman holding** company that 'owns the trademark' but performs none of the **DEMPE** functions is a hollow structure that German, French, and Dutch **tax authorities** deny standing as IP owner for **transfer pricing** purposes. - Development — designing the IP. For a crypto firm, this is engineering the trading algorithm, the matching engine, the security model, the smart contract architecture. - Enhancement — improving the IP. Continuous protocol upgrades, new features, performance improvements. - Maintenance — operating the IP. Bug fixes, infrastructure operations, security patching. - Protection — defending the IP. Legal enforcement of trademarks, copyright registrations, defensive patents, legal action against infringers. - Exploitation — commercialising the IP. Customer\-facing operations, pricing, distribution. > **Note:** Most crypto holding\-entity structures fail DEMPE on day one. The Cayman entity has no engineers, no infrastructure operations, no legal staff, and no commercial team — those are at the operating subsidiaries. Tax authorities increasingly hold that the IP\-owning entity must hold a fair share of these functions to retain a fair share of the IP profit. Hollow IP holding companies are the highest\-risk crypto transfer pricing structure. ## The Documentation Stack **BEPS** **Action 13** standardised **transfer pricing documentation** across the **OECD**. The framework has three tiers; tier 1 applies to all multinational groups \(above the de minimis revenue threshold\), tier 3 applies only to groups above **€750 million** consolidated revenue. *Table: Transfer pricing documentation tiers under BEPS Action 13.* | Tier | Document | What it contains | Threshold | | --- | --- | --- | --- | | Tier 1 — Master File | Master File | Group\-wide overview: business model, IP, intra\-group financing, transfer pricing policies | All multinational groups \(de minimis varies by jurisdiction\) | | Tier 2 — Local File | Local File | Country\-specific detail: local entity, controlled transactions with comparables analysis, financial information | Most multinational groups; thresholds vary | | Tier 3 — Country\-by\-Country Report | CbC Report | Per\-country revenue, profit, tax paid, employees, capital, tangible assets | Groups with consolidated revenue ≥ €750 million \(Council Directive EU 2016/881\) | The **Master File** and **Local File** should be drafted before the financial year\-end and finalised within 12 months of year\-end \(specific deadlines vary by jurisdiction\). CbC Reports are filed with the parent's **tax authority** and exchanged automatically with subsidiary jurisdictions under tax\-treaty information exchange. Late or missing documentation triggers per\-jurisdiction penalties on top of any **transfer pricing** adjustment. ## Transfer Pricing Methods — Choosing the Right One The **OECD Guidelines** recognise five **transfer pricing** methods. Each fits different transaction types; choosing the wrong method is itself an **audit** trigger. *Table: OECD transfer pricing methods — when each applies and why crypto groups misapply them.* | Method | Best for | Common crypto\-group misuse | | --- | --- | --- | | Comparable Uncontrolled Price \(CUP\) | Identical comparable transactions exist \(rare for IP\) | Applied to royalties without true comparables — thin crypto IP licensing market | | Resale price method | Distribution arrangements with limited functional risk | Rarely applicable in pure crypto | | Cost\-plus method | Routine services \(management fees, back\-office\) | Mark\-ups too low \(3–5% common; should be 5–10% for substantive services\) | | Transactional Net Margin Method \(TNMM\) | Operating\-margin benchmarks for principal entities | Inappropriate comparables — Big Tech / SaaS used as comparables for crypto\-trading firms | | Profit Split | Highly integrated activities; both entities contribute IP / value | Underused when it is the genuinely correct method \(e.g. integrated trading \+ custody groups\) | ## The Most Aggressive Tax Authorities Three **EU** **tax authorities** are notably more aggressive than peers on crypto **transfer pricing** **audits**. Operators in or with subsidiaries in these jurisdictions should expect higher **audit** probability and tighter documentation expectations. - **Germany** — **Bundeszentralamt für Steuern** \(BZSt\) and the local **Finanzamt** offices apply the most rigorous **transfer pricing** methodology in Europe. Aggressive on **royalty** challenges, hollow holding companies, and **DEMPE** substance. Combined CIT \+ trade tax of approximately **30%** means adjustments are large. - **France** — **DGFiP** runs frequent **audits** of multinational crypto groups with French operating entities. Particularly aggressive on management\-fee structures and on **permanent establishment** positions where remote\-working developers create unintended **PE** exposure. - **Netherlands** — **Belastingdienst** is structurally tax\-friendly but selectively aggressive. Audits cluster around **royalty** structures using the historic Dutch CV/BV ruling regimes \(largely closed under post\-**BEPS** reforms but still relevant for legacy structures\). > **Warning:** If your crypto group has German, French, or Dutch operating subsidiaries, plan transfer pricing documentation to a higher standard than the OECD baseline. Use third\-party economic analysis \(PwC, EY, Deloitte transfer pricing teams or specialist boutiques like NERA, Charles River Associates\) for benchmarking; do not rely on internally\-built royalty rates without external defence. ## **Pillar Two** — The **15%** Global Minimum Tax **OECD** [GloBE Rules](https://www.oecd.org/tax/beps/pillar-two-model-rules.htm) implementing **Pillar Two** of the **BEPS** 2.0 framework apply to multinational groups with consolidated annual revenue ≥ **€750 million**. The rules impose a **15%** effective minimum tax on group profits in each jurisdiction, calculated through a top\-up tax mechanism that activates when the local effective rate falls below **15%**.⁴[^4] Implications for crypto groups: a **Cayman holding** entity that pays **0%** **Cayman** corporation tax does not survive **Pillar Two** for groups above the threshold. The home\-country parent \(or another in\-scope jurisdiction\) levies a top\-up tax to bring the global effective rate to **15%**. The economic benefit of pure\-**Cayman** structures collapses; the structural reason crypto groups have used **Cayman holding** entities erodes for any group at this scale. Below **€750 million** consolidated revenue, **GloBE** does not apply directly — but **audit**ors at jurisdictional level take cues from **Pillar Two** policy when scrutinising **transfer pricing**. Crypto groups designing structures in 2026 should assume **Pillar Two** applies above **€750 million** and plan structures that work both below and \(eventually\) above the threshold. ## The Mistakes That Trigger Audits - Hollow IP holding companies. **Cayman** or **BVI** entity with the trademark and zero substance — guaranteed **audit** trigger in any aggressive jurisdiction. - Royalty rates set by 'industry rule of thumb' rather than benchmarked. Auditors ask for the comparable analysis; without it, the deduction is reduced. - Management fees with thin documentation. 'Centralised group services' invoices with no underlying time records and no specific service description. - Permanent establishment exposure from remote workers. A senior engineer in **France** working remotely for a **Cayman**\-incorporated DAO Foundation often creates a French **PE** for the Foundation — taxed at French rates. - Inconsistent characterisation across jurisdictions. The same flow described as a **service fee** in one **Local File** and as a **royalty** in another invites adjustment. - Year\-end true\-ups that are too aggressive. Year\-end **transfer pricing** adjustments are normal; but adjusting €5M between entities in December based on 'actual profit' without documented **arm's length** analysis is a transparent profit\-shift. - Ignoring the [OECD Model Tax Convention](https://www.oecd.org/tax/treaties/model-tax-convention-on-income-and-on-capital-condensed-version-20745419.htm) permanent\-establishment rules. Cross\-border crypto teams without **PE** analysis are a structural risk — particularly post\-COVID with distributed engineering teams.⁶[^5] ## Frequently Asked Questions ### Do small crypto groups really need **transfer pricing documentation**? If you have any cross\-border **inter\-company** transactions, yes. Documentation thresholds vary by jurisdiction — **Germany** applies them broadly, **Cyprus** and **Malta** have more permissive de minimis rules, but every **EU** jurisdiction now expects at least **Local File** equivalents for material transactions. A €5 million group with €500,000 of **inter\-company** **royalty** is well above almost any threshold and needs **Master File** \+ **Local File** documentation. ### Can I just use a 5% **royalty** rate on revenue and call it **arm's length**? Sometimes yes, sometimes no — the rate must be benchmarked. 5% is plausible for some IP types, implausible for others. Without benchmarking analysis \(third\-party data on comparable **IP licensing** in similar industries\), the rate is not defensible. The cost of a one\-off third\-party benchmarking study \(€15,000–€50,000\) is materially below the cost of a **transfer pricing** adjustment and back\-tax. ### What if my **Cayman holding** entity has zero employees? It will fail **DEMPE** substantially. The **OECD Transfer Pricing Guidelines** and German / French **audit** practice both require that the IP\-owning entity perform a fair share of **DEMPE** functions. Practical responses: \(a\) move some **DEMPE** functions to **Cayman** \(engineering, legal, IP management — expensive but clean\); \(b\) reduce the IP entity's profit share to reflect lower **DEMPE**; or \(c\) restructure the IP elsewhere \(**Cyprus** IP Box, **Switzerland**\) where substance can be built more easily. ### Does **Pillar Two** apply to crypto groups at all? Above **€750 million** consolidated annual revenue, yes — including the largest **CASP**s \(Coinbase Europe, Kraken, Bitstamp, several stablecoin issuers\). Below that threshold, **GloBE** rules do not apply, but the policy direction influences **audit** posture in every developed jurisdiction. Plan structures that survive both today's regime and a future **Pillar Two** extension. ### If my engineers are remote in different **EU** countries, where do they create **permanent establishment**s? Potentially in each country. Under the **OECD** Model Tax Convention, a **permanent establishment** can arise where a fixed place of business exists or where dependent agents conclude contracts. A senior engineer working from a French apartment can create a French **PE** for the foreign\-incorporated employer — particularly if they have significant decision\-making authority. The right response is a **PE** risk\-assessment per country plus structural responses \(employer\-of\-record arrangements, contractor agreements, formal local subsidiaries\) where exposure is material. ### Should I file country\-by\-country reports if I'm below the **€750 million** threshold? Filing is mandatory only above the threshold. Below it, the **Master File** \+ **Local File** regime applies. But many crypto groups voluntarily prepare CbC\-style internal data because **tax authorities**, banks, and investors increasingly request equivalent transparency. The marginal effort to maintain CbC\-style data is small when **Master File** \+ **Local File** documentation is already being prepared. > **Call to action:** Building or remediating a multi\-jurisdiction crypto group structure? Finconduit makes vetted introductions to specialist transfer pricing economists, OECD\-experienced tax counsel, and substance\-build providers — and supports Master File / Local File documentation. Get a free transfer pricing risk assessment. ## Related Guides - [EEA vs UK vs Offshore: Where to Incorporate Your Crypto Business](/resources/eea-uk-offshore-crypto-incorporation): Which jurisdiction maximises regulatory access and tax efficiency - [Cayman Foundation Companies for DAO Treasuries](/resources/cayman-foundation-dao-treasury): Foundation Companies Act 2017, CIMA, and the alternatives - [MiCA Compliance Guide for CASPs](/resources/mica-compliance-guide-casps): Authorisation walkthrough — capital, governance, supplier stack - [UAE VARA Licence Guide](/resources/uae-vara-licence-guide): Application, capital, timeline, and ADGM FSRA comparison Crypto **transfer pricing** is the most under\-budgeted tax\-risk area in the industry. A **Cayman holding** company with a hollow **IP licence** is the kind of structure that survives in the founder's imagination and dies in the first serious **audit**. The correct response is not 'build a thinner offshore wrapper' — it is build the substance, document the **arm's length** analysis, file **Master File** \+ **Local File** on time, and assume **Pillar Two** applies once you cross **€750 million**. The tax\-savings narrative for offshore holdings is collapsing under **DEMPE**, **GloBE**, and aggressive **EU** **audit** practice. Build structures that work in 2030's tax world, not 2018's. - [Pillar Two and the 15% Global Minimum Tax](/resources/pillar-two-global-minimum-tax-crypto) — how the 15% global minimum tax interacts with transfer\-pricing positions across a crypto group's entities. ## Footnotes [^1]: OECD Transfer Pricing Guidelines for Multinational Enterprises and Tax Administrations \(2022 consolidated edition\). [^2]: OECD Base Erosion and Profit Shifting \(BEPS\) Action Plans, 15 actions issued 2013–2015. [^3]: BEPS Action 13 — Country\-by\-Country Reporting; transposed into EU law via Council Directive \(EU\) 2016/881. [^4]: OECD GloBE Rules — Pillar Two model rules implementing the 15% global minimum tax for multinational groups with €750 million\+ consolidated revenue. [^5]: OECD Model Tax Convention on Income and on Capital — Article 5 Permanent Establishment definition; relevant to remote\-working crypto teams. --- Source: https://finconduit.com/resources/crypto-transfer-pricing-beps