Transfer Pricing Documentation for Dutch Structures

Transfer pricing documentation for Dutch structuresDutch transfer pricing documentation follows the OECD three-tier model, codified in articles 29b to 29h of the Wet op de vennootschapsbelasting 1969: a master file and local file for groups above the EUR 50 million consolidated revenue threshold, and country-by-country reporting above EUR 750 million. The documentation must be in the administration by the corporate income tax filing deadline — which only works if the underlying data is maintained year-round.For Dutch-headed and Dutch-resident entities, transfer pricing documentation is not a year-end deliverable that can be assembled from memory. The master file and local file must be present in the taxpayer's administration by the time the corporate income tax return is due, and the CbC report is filed within twelve months of year end with notification by year end.The recurring problem is not the policy. It is that the financial data supporting the policy — segmented P&Ls per transaction type, intercompany charge bases, allocation keys — is produced once, for the report, and then discarded.The three tiers and the data each one needs

Master file: group structure, value drivers, intangibles, financing arrangements, and the group's APAs and rulings. Mostly narrative, but it must stay consistent with what the local files claim.

Local file: the entity's controlled transactions with amounts and counterparties, a functional analysis, the method applied, the comparables, and a financial analysis reconciling the tested party's results to its statutory accounts.

CbCR: revenue, profit before tax, tax paid and accrued, capital, retained earnings, employees, and tangible assets per jurisdiction — sourced consistently and reconcilable to the consolidation.

Where the data breaks

Segmented results. The local file needs the tested party's results at transaction-type level; most ledgers only support entity-level reporting, so segmentation is done manually each year with a different logic.

Charge bases. Management fees, IP royalties and cost-plus recharges rely on allocation keys (headcount, revenue, usage) that live outside the ERP and are rarely versioned.

Reconciliation to statutory accounts. The financial analysis must tie back to filed accounts. Where segmentation is ad hoc, that reconciliation becomes the longest part of the exercise.

CbCR consistency. Table 1 figures must be drawn from a consistent source year over year, and the definition choice documented — the Dutch tax authority expects the source to be stated and applied consistently.

Making documentation continuousThe fix is to treat transfer pricing as a data product rather than an annual document. That means posting intercompany transactions with a transaction-type dimension in the ledger, storing allocation keys as versioned reference data with an owner, and generating segmented P&Ls monthly from the same logic the local file will use.The same segmented data feeds the Pillar Two calculation and the intercompany reconciliation process, so the investment is not single purpose.Transfer pricing data checklist

Thresholds assessed: EUR 50m consolidated revenue (master/local file), EUR 750m (CbCR)

CbCR notification filed with the Belastingdienst before year end

Intercompany transaction register per entity pair, per transaction type

Transaction-type dimension applied in the ledger to intercompany postings

Allocation keys documented, versioned, and owned, with the source of each key

Segmented P&L per tested party produced from ledger logic, not spreadsheets

Reconciliation from segmented results to statutory accounts

Benchmarking studies with search date, database, and refresh cycle recorded

Rulings and APAs registered and reflected consistently in the master file

CbCR data source definition documented and applied consistently year over year

Consistency check between master file narrative and local file positions

Documentation present in the administration by the CIT filing deadline

How we would approach this

We start by making intercompany flows visible at transaction-type level in the ledger, which removes most of the annual segmentation work.

We turn allocation keys into governed reference data with an owner and a version history.

We build the reconciliation from segmented results to statutory accounts once, as a repeatable report.

What transfer pricing documentation must a Dutch group keep?A local file and, above the EUR 50 million consolidated revenue threshold, a master file; groups above EUR 750 million consolidated revenue also file a country-by-country report. All are governed by Chapter VIA of the Dutch Corporate Income Tax Act.When must the documentation be available?The local file and master file must be in the group's administration by the filing deadline of the relevant corporate income tax return — not produced after a question from the tax authority.Primary sources

OECD Transfer Pricing Guidelines — https://www.oecd.org/tax/transfer-pricing/oecd-transfer-pricing-guidelines-for-multinational-enterprises-and-tax-administrations-20769717.htm

Belastingdienst — country-by-country reporting — https://www.belastingdienst.nl/wps/wcm/connect/nl/vennootschapsbelasting/content/landenrapport-country-by-country-report

Wet op de vennootschapsbelasting 1969, art. 29b-29h — https://wetten.overheid.nl/BWBR0002672