The fifty million euro threshold is the most misread figure in Dutch transfer pricing. It is read as the point at which documentation begins, when in fact it is the point at which documentation acquires a prescribed form. Below it, a Dutch taxpayer still has to be able to show how its intercompany prices were set; above it, that showing has to be organised into two specific files, with specific contents, available at a specific moment. Groups that treat the threshold as an on switch tend to arrive at the crossing year with nothing to convert, and groups that treat it as a formatting exercise tend to arrive with a Local File that describes a company other than the one the inspector is looking at.
Where the threshold sits, and where it does not
Two obligations run in parallel and are frequently collapsed into one. The first is the general obligation under article 8b of the Wet op de vennootschapsbelasting 1969: transactions between associated enterprises must be priced at arm’s length, and the taxpayer must hold in its administration the information showing how those conditions were arrived at. That obligation has no turnover threshold whatsoever. It applies to a BV with a single intercompany loan as much as to a Dutch entity in a group turning over billions. We set out its scope in the foundational article on the article 8b obligation, and everything below assumes it as the floor.
The second obligation is the standardised documentation package introduced with the Dutch implementation of BEPS Action 13. A Dutch taxpayer belonging to a multinational group whose consolidated turnover reached EUR 50 million or more in the financial year preceding the year being documented must prepare a Master File and a Local File. Country-by-Country Reporting sits far higher, at consolidated group turnover of EUR 750 million, with its own notification and filing mechanics and no bearing on the fifty million question.
That the test looks to the preceding financial year matters more than it appears to, and it is the source of the timing confusion addressed in the worked example below.
What the Master File is actually for
The Master File is a group document. It gives the Dutch inspector the context in which the Dutch entity’s results are supposed to make sense. Its expected contents follow the OECD template: the group’s legal and ownership structure and geographic footprint; the drivers of business profit; the supply chain for the five largest products or service lines by turnover, plus any others exceeding five per cent of group turnover; important intragroup service arrangements other than research and development services; the principal markets served; a functional analysis of the main contributions to value creation by individual entities.
Beyond that, it covers the group’s intangibles: the overall strategy for development, ownership and exploitation, the list of important intangibles and which entities own them, the relevant intercompany agreements, and the group’s transfer pricing policies on research and development and on intangibles. It covers intercompany financial activity, including which entities perform a central financing function, where they are resident, and the general policy on financing between group members. Finally it covers the group’s financial and tax position: the consolidated annual accounts, and a list and short description of existing unilateral advance pricing agreements and other rulings relating to the allocation of income between countries.
The Master File explains the system. It does not, and is not meant to, prove that the Dutch entity’s margin is defensible.
What the Local File has to do
The Local File is the document that carries the Dutch tax burden. It describes the Dutch entity: its management structure, its local organisation chart, to whom local management reports and in which countries those persons sit, a description of the business and strategy including any business restructurings or intangible transfers in the current or preceding year, and the key competitors.
Then, per category of controlled transaction, it has to set out:
- the transaction and its context, and the amounts of intragroup payments and receipts broken down by counterparty jurisdiction;
- the associated enterprises involved, their relationship, and copies of the relevant intercompany agreements;
- a comparability and functional analysis of the Dutch entity and the relevant counterparties, including any changes from prior years;
- the selected method, chosen from CUP, resale price, cost plus, TNMM or profit split, and the reasons for selecting it over the alternatives;
- which associated enterprise is the tested party, and why;
- the list and description of selected comparables with the financial indicators relied on, and any comparability adjustments;
- the conclusion that the conditions applied are arm’s length.
It must also include the local statutory accounts, a schedule reconciling the financial data used in the pricing analysis to those accounts, and summary schedules of relevant financial data for the comparables with their sources. Both files may be prepared in Dutch or in English. That is a genuine convenience, and it is also where the most common failure originates.
The translation error
A group head office produces a global Master File and a set of country files generated from a single template. The Dutch finance lead receives the Netherlands chapter, confirms the entity name and the year are correct, and files it. Formally the group now has two documents. Substantively it has one document and a cover sheet.
The failure patterns are consistent. The functional analysis describes a distributor model the Dutch entity outgrew two years ago, or omits that Dutch staff now negotiate directly with regional customers. The benchmarking study uses a pan-European comparable set with no explanation of why that set fits the Dutch entity. The agreements annexed are group templates rather than the versions actually signed, and sometimes nothing was signed at all. The reconciliation to the Dutch statutory accounts is absent, so the margin tested cannot be traced to the figures in the return. Where intangibles are involved, the file asserts legal ownership without addressing DEMPE at all: development, enhancement, maintenance, protection and exploitation, and specifically who performs and controls those functions and who bears the associated risk. Legal title in a low-substance entity is not an argument; it is the thing the inspector is testing.
A Local File that could be lifted and dropped into any jurisdiction by changing the entity name is not documentation. It is a statement that nobody looked at the Dutch company.
When the files have to exist
The Master File and Local File must be present in the taxpayer’s administration within the period set for filing the Dutch corporate income tax return for the year concerned. They are not filed with the return. They sit in the administration and are produced on request.
The practical consequence is that the analysis has to be contemporaneous. A benchmarking study built after an inspector’s first letter, using data selected in hindsight, carries considerably less weight than the same study run before the return was filed. Where the file is absent or materially deficient, the exposure is evidential as much as arithmetical: the taxpayer has nothing of its own to rely on, and faces the consequences attaching to an administration that does not meet the statutory requirement, including a materially heavier position on the burden of proof.
The same discipline applies to any downward adjustment. Under the Dutch rules against mismatches in the application of the arm’s length principle, in force since 1 January 2022, a downward adjustment in the Netherlands is denied to the extent there is no corresponding upward inclusion in the counterparty jurisdiction. The informal capital route closed with those rules, and documentation that still relies on it is documenting a position that no longer exists.
A group that crosses mid-year
Take a group with a Dutch operating BV that reports consolidated turnover of EUR 44.6 million for FY2024. In July 2025 it acquires a competitor, and FY2025 consolidated turnover closes at EUR 58.3 million. The Dutch BV’s own turnover is EUR 26 million, earned as a limited-risk distributor buying from a related principal.
Because the threshold is tested on the preceding financial year, the Master File and Local File obligation attaches for FY2026, with both documents required in the administration by the FY2026 return deadline. For FY2025 itself, the year of the crossing, no standardised package is required. Article 8b is unaffected: the BV must still hold information showing how its distribution margin and the new post-acquisition intercompany flows were set.
Suppose the BV reports an EBIT margin of 1.4 per cent, or EUR 364,000. Suppose further that a properly constructed TNMM study of comparable limited-risk distributors were to produce an interquartile range of 2.6 to 5.1 per cent. An adjustment to the lower quartile would give EUR 676,000, an uplift of EUR 312,000, which at the top corporate income tax rate of 25.8 per cent is roughly EUR 80,500 of additional tax for a single year. Repeated across three years still open to assessment, that is in the order of EUR 241,500 before interest, on a company that was, in its own view, compliant. The figures are illustrative; an inspector proposing an adjustment within a range need not stop at the lower quartile, and the FY2025 exposure is not reduced by the absence of a Local File. It is simply harder to defend.
What to do with the year before the threshold
The year in which a group approaches EUR 50 million is the useful year. Functional interviews, agreements, benchmarking and reconciliations can be built while the facts are current and no deadline applies, so that the first mandatory Local File documents a position already tested rather than one assembled under pressure. Groups reorganising ownership at the same time should align the two exercises with the considerations in our guide to setting up a holding structure in the Netherlands, since the documentation consequences of a restructuring belong in the Local File for the year in which it occurs.
Montclare has published a short self-assessment, the Transfer Pricing Readiness Check, which sets out ten questions that identify where a group’s exposure sits. It can be downloaded from our transfer pricing page.
This article is informational and does not constitute tax advice. Each engagement is subject to scope and applicable regulation.