Signal — FT Cases

Tobacco Group v Staatssecretaris van Financiën

The taxpayer’s contemporaneous TP documentation — monthly invoices, the receivables purchase agreement, and the PwC TP report — defeated the tax authority’s attempt to use a 12-year reassessment window. Documentation did the work that the merits could not.

This is an Advocate-General’s Conclusion (Conclusie), not a final judgment of the Hoge Raad. The AG’s recommendation is advisory: the Hoge Raad may follow it, depart from it, or issue a shorter ruling without engaging the analysis. The substantive TP documentation principle it illustrates is well-established Dutch and OECD practice regardless of the final outcome.

Context

LuxLeaks broke in November 2014. Within weeks, the Dutch tax authority had opened investigations into intercompany arrangements that had previously been assessed without challenge. The question this case raises is not whether those arrangements were arm’s length — the courts deliberately left that open — but whether the authority was entitled to reopen tax years dating back to 2003 using a 12-year extended reassessment period (Art. 16(4) AWR) rather than the standard five-year window.

The extended period exists to compensate for limited Dutch audit reach over income that has arisen abroad and been concealed from the Dutch authorities. It is not a general tool for revisiting transfer pricing positions after new information becomes available from foreign sources.

The facts

A Dutch tobacco group company paid factoring fees to a Belgian coordination centre under a Receivables Purchase Agreement (RPA). The fees were high — €3–4m per year — and the Belgian entity held an excess profit ruling covering 92 per cent of its income from those fees, a fact that only emerged via LuxLeaks. The authority challenged the fees as non-arm’s length and sought to use the 12-year window to reach tax years 2003–2007, well outside the standard five-year period.

What the Dutch administration did contain throughout the audit period: the RPA itself, monthly invoices from the Belgian entity, bank statements showing payments, a PwC memo, and a PwC transfer pricing report supporting the fee level as arm’s length. What it did not contain: the Belgian TP documentation, the excess profit ruling, or any disclosure of the Belgian entity’s actual functions and risk profile as presented to the Belgian authorities.

The decision

Both the Rechtbank and the Gerechtshof held that the Dutch documentation was sufficient. The standard for applying the 12-year extended period is not whether the documentation would have proved the fees non-arm’s length — it is whether the documentation gave the authority enough to ask questions. It did. The RPA, invoices, and TP report all pointed to a factoring arrangement that a diligent inspector could have investigated by simply asking what the Belgian entity actually did and what Belgian fiscal treatment it received.

The Advocate-General endorsed this analysis. The authority’s inability to discover the Belgian ruling was not caused by concealment of Dutch-side facts; it was caused by a failure to ask the questions that the Dutch documentation invited. That is not the gap the 12-year period was designed to fill.

Outcome. The Advocate-General recommends dismissal of the Staatssecretaris’s cassation appeal. The extended 12-year reassessment period is inapplicable: the Dutch administration contained sufficient contemporaneous documentation — the RPA, monthly invoices, and the PwC TP report — to enable investigation within the standard five-year window. The Hoge Raad ruling is awaited; if it follows the Conclusion, the taxpayer prevails.

ajiho commentary

The signal here is not about the outcome on the factoring fees — the courts never reached that question. It is about what saved the taxpayer: contemporaneous, accessible, Dutch-side documentation. The RPA set out the commercial framework. The monthly invoices quantified each payment. The PwC report provided a benchmarked arm’s length justification. Together they gave the authority a clear line of inquiry it chose not to pursue.

This is the documentation principle in its most practical form. A TP report that sits in a filing system and can be produced during an audit does not just support the arm’s length position on the merits. In the Netherlands and in many other jurisdictions, it also limits the authority’s ability to reach back beyond the standard reassessment window. Documentation is both a substantive defence and a procedural one.

The counterpoint is equally clear: the Belgian TP documentation told a materially different story about the entity’s functions and risks. Groups that present different characterisations of the same entity to different tax authorities — even if each characterisation is technically defensible in its own jurisdiction — face the risk that the mismatch is eventually exposed. LuxLeaks was an unusual trigger; DAC6 mandatory disclosure, BEPS country-by-country reporting, and the expansion of automatic information exchange mean the probability of exposure has increased substantially since 2014.

Case reference

Staatssecretaris van Financiën v [X] B.V. · Conclusie Advocaat-Generaal P.J. Wattel · Parket bij de Hoge Raad · Zaaknummer 24/04260 · ECLI:NL:PHR:2025:727 · 27 June 2025

Document in Dutch. Advocate-General’s Conclusion only — Hoge Raad judgment pending. Prior instances: Rechtbank Noord-Holland (ECLI:NL:RBNHO:2021:2526) and Gerechtshof Amsterdam (ECLI:NL:GHAMS:2024:2844). Access via rechtspraak.nl.

This article is published by ajiho for general information only. It reflects ajiho’s own analysis of publicly available sources and does not constitute legal, tax or professional advice, nor a substitute for taking it. No client or confidential information is used in any Signal publication. Where the subject is a court or tribunal decision, the summary is ajiho’s reading of the published judgment and does not account for any subsequent appeal or development. You should take specific professional advice before acting on anything set out here.

Have an arrangement that raises the same question? That’s a conversation worth having.