A software group expanding across Europe faces a structural question before it faces a tax one: where should the intellectual property live, which company should contract with customers, and where should the people who build and sell the product be employed. The Netherlands is a common answer, not because of a headline rate but because of a stable treaty network, a mature ruling practice, and a legal system that international counterparties understand. What follows sets out how a SaaS or software group can organise its European presence through a Dutch entity, and where the analysis turns on function rather than on paperwork.
Why the Netherlands for a software group
The Dutch corporate income tax rate reaches 25.8% in the top bracket, which is not low by regional standards. The reasons groups still centralise here are structural. The participation exemption removes economic double taxation on qualifying subsidiary dividends and gains; the treaty network reduces withholding on inbound royalty and service flows; and the tax authority will, in defined circumstances, give advance certainty on how a structure will be treated. For a group whose value is mobile and whose customers are spread across jurisdictions, predictability is worth more than a marginal rate difference.
None of this operates on its own. A Dutch entity is only useful to the extent that it does something real, and that principle runs through everything below.
Where the IP sits, and why ownership is not the question
The instinct is to place the group’s source code and trademarks in a single holding company and license them outward. Legal ownership can indeed sit in one place. The profit attributable to that IP, however, does not follow the title deed. Under the OECD framework that the Netherlands applies, returns from intangibles follow the DEMPE functions: development, enhancement, maintenance, protection and exploitation. The company entitled to the intangible return is the one that controls and performs those functions, and that bears the associated risk, not simply the one named on the register.
Legal title to the IP settles who signs the licence; it does not settle who is taxed on the profit.
For a SaaS group this is decisive. If the code is written by engineers employed in one country, the roadmap is set by a product team in another, and the Dutch entity holds only the certificate of ownership, the intangible return cannot be parked in the Netherlands on the strength of title alone. Aligning legal ownership with the location of decision-making, engineering leadership and risk control is the work; the paperwork follows it. The mechanics of pricing an IP-owning company and its licence flows are set out in our note on royalties, IP and DEMPE.
The revenue flows that have to be priced
A software group rarely sells one thing. A single customer contract can bundle several distinct flows, and each one has to be identified and priced separately when it crosses a group boundary. The common ones are:
- Software licence or right of use, the core grant that lets the customer run or access the product.
- Maintenance, covering updates, patches and version upgrades.
- Support, the human help desk and technical response function.
- Platform or hosting access, where the product is delivered as a service rather than installed.
- Brand and trademark, the right to trade under the group’s name and marks.
When the customer-facing company and the IP-owning company are different group entities, an intercompany arrangement has to move value between them at arm’s length. A local sales subsidiary that finds customers, signs contracts and provides first-line support is performing a real function and is entitled to a return for it; it is not entitled to the residual intangible profit unless it performs intangible functions. The transfer pricing sits at the join between these flows, and the Dutch documentation obligation under article 8b requires the group to be able to show its reasoning rather than assert it.
Recurring revenue and the timing question
Recurring revenue is the defining feature of the SaaS model, and it raises a recognition question that carries a tax dimension. An annual subscription invoiced in advance is not earned on the invoice date; it is earned across the service period. The accounting treatment, deferring revenue and releasing it over the term, generally drives the tax result, so the way contracts are written and billed affects the timing of taxable profit in the Dutch entity. Multi-year commitments, usage-based billing and upfront implementation fees each behave differently. The point for the group is that the contracting entity’s taxable base is shaped by the revenue recognition policy, and that policy has to be consistent, documented and defensible rather than chosen for a single year’s outcome.
Distributed teams, substance and permanent establishment
Software groups are natively distributed. Engineers, sales staff and support teams sit wherever talent is, which creates two related exposures. The first is substance. A Dutch entity meant to own IP or contract with customers must have enough real activity in the Netherlands, people with the authority and competence to make the relevant decisions, to support the functions it claims. Substance is not a fixed checklist; it is proportionate to what the entity does, and our substance note for 2026 sets out how the expectations are read in practice.
The second exposure is permanent establishment. A salesperson in another country who habitually concludes contracts for the Dutch entity can create a taxable presence there, pulling profit out of the Netherlands and into the country where the person works. Remote engineering teams, a fixed office, or a dependent agent can each trip the threshold. For a distributed group this is not a marginal risk; it is the central design constraint. Where each function is performed has to match where the group intends profit to be recognised, and the two can drift apart quietly as headcount grows.
The exit: participation exemption on a sale
Most software groups are built to be sold, whether to a strategic acquirer or a financial sponsor. The structure that carries the group through its operating life also determines the tax on exit. Under the Dutch participation exemption, a qualifying shareholding generally allows the gain on a sale of the subsidiary to be received free of Dutch corporate income tax at the level of the holding company. This is why the holding layer is not an afterthought. A group that places its operating and IP-owning companies under a Dutch holding, and that meets the conditions, can realise the enterprise value of a trade sale without a second layer of tax on the gain. The detailed conditions, and the cases where the exemption does not apply, are covered in our participation exemption explainer. On distributions rather than a sale, dividend withholding of 15% may apply, subject to treaty and directive relief.
A worked example
Consider a group with a Dutch entity that owns the software IP and two commercial subsidiaries, one serving the DACH region and one serving the Nordics. The Dutch entity does not merely hold the certificate. It employs the product leadership and the senior engineering function that set and control the development roadmap, and it bears the risk of the product succeeding or failing. On that basis it is entitled to the intangible return.
Each commercial subsidiary finds and signs customers, runs first-line support in the local language, and manages the client relationship. Under the intercompany arrangement, the subsidiaries are remunerated for the marketing, sales and support functions they actually perform, on an arm’s length basis; the residual profit attributable to the software itself accrues to the Dutch IP owner, because that is where the DEMPE functions sit. Customer contracts that bundle a licence, maintenance, platform access and support are unpicked so that each element is attributed to the entity that earns it.
The recurring subscription revenue is recognised across each service period rather than on invoice, so the Dutch entity’s taxable base tracks the contract term. The group monitors where its salespeople conclude contracts and where its engineers work, to avoid creating an unintended permanent establishment that would relocate profit. The whole arrangement sits under a Dutch holding company, so that when the founders sell, the gain on the operating group can fall within the participation exemption. No part of this depends on an invented number; it depends on functions being located where the group says they are, and on the documentation being able to prove it.
The order matters. The structure is not designed backwards from the exit; it is designed around who does the work, and the exit treatment follows from having done that honestly.
Montclare structures and operates Dutch and cross-border platforms for international groups. Our services are set out on our services page.
This article is informational and does not constitute tax advice. Each engagement is subject to scope and applicable regulation.