# Technology and SaaS: decisions taken at group level
A Dutch SaaS subsidiary inside a foreign group runs its own product and commercial calls, but three categories of decision move to group level as a matter of course: assignment or licensing of the software itself, sign-off on customer contracts that expose more liability than the subsidiary can carry, and control over how customer data moves between group entities. This applies to any Dutch B.V. operating inside a larger technology group, whatever the parent's own jurisdiction.
Why this arises in technology and SaaS
In most sectors, the group's reserved decisions concern capital, real assets or personnel. In technology and SaaS the group's principal asset is the software and the customer contract that licenses it, and both are mobile between entities in a way a factory or a fleet is not. That question belongs to corporate law and governance rather than to any other practice area, because it turns on the powers reserved to the board and general meeting, not on the underlying technology itself. Groups therefore centralise decisions about where the intellectual property sits, who may license it, and how the data is processed, because those choices determine which entity actually holds the value the business is built on. A second driver is the sector's reliance on freelance and contract developers rather than employees alone, which raises an ownership question that does not arise where development staff are all in-house.
The mechanics in short
A Dutch B.V.'s day-to-day management sits with its board. Decisions that change the company's identity or expose it beyond its ordinary business, such as disposing of a material part of the business, issuing new shares, or granting an exclusive licence over its core software, are reserved to the general meeting under the applicable Dutch rules on important decisions. Inside a group, the parent exercises that role as shareholder, and most groups add a contractual layer on top: an internal approval matrix routing decisions above a stated threshold to a group board, regardless of what Dutch company law itself requires. The two layers do not always align. The articles of association of the Dutch entity set the statutory floor; the group's internal matrix sets whatever ceiling the parent chooses. If a decision is later disputed, a Dutch court applying Dutch law reviews it against the company's own articles and the statutory floor, not against the parent's internal policy, which has no standing of its own before a Dutch court.
The pattern specific to SaaS group structures
Three situations recur in technology and SaaS that would be wrong to generalise to another sector.
First, intellectual property built by contractors. Dutch copyright law vests software written by an employee in the course of employment in the employer automatically. It does not do the same for a freelance developer or an outsourced team: the code stays with the person who wrote it unless there is a written assignment. SaaS companies that grew through contract development frequently discover, at the point of a group reorganisation or an investment round, that a material part of the codebase was never formally assigned to the entity meant to own it.
Second, data processing allocated across the group. A SaaS business commonly splits hosting, support and account management across different group entities and different countries. A group decision to move hosting or support for Dutch customers to another group entity is, in substance, a decision about who is controller and who is processor for data the Dutch entity is contractually responsible for towards its own customers. That allocation has to be documented; it is not settled by an internal reporting line, and the Dutch Data Protection Authority is the relevant supervisory authority for processing that touches the Netherlands.
Third, enterprise contracts that outrun local authority. SaaS sales teams routinely negotiate liability caps and indemnities with enterprise customers that exceed what the Dutch subsidiary could itself absorb on its own balance sheet. Group sign-off on such a contract is then a commercial necessity, not only a formality dictated by an internal matrix: the subsidiary genuinely cannot carry the exposure alone. This is the point at which a group decision and the Dutch entity's own contractual exposure become the same question, which does not arise in a sector where customer contracts carry limited financial risk.
What to check
Start with the articles of association of the Dutch entity: do they name specific decisions reserved to the general meeting, and does that list match what the group's own approval matrix assumes it controls. Check the assignment paperwork for any code written by a contractor, a freelancer or an outsourced team, not only for employees. Check whether there is a documented data processing agreement between the Dutch entity and any other group entity that touches its hosting or support, stating who is controller and who is processor. Check who actually signed the last enterprise contract carrying a liability cap above the subsidiary's own balance sheet, and against what authority.
Decisions and what typically moves in the Netherlands
| Decision | Who typically decides | What moves in the Netherlands |
|---|---|---|
| Issuance of shares or options | General meeting, exercised by the parent as shareholder | Shareholder register updated; a Trade Register filing where registered particulars change |
| Assignment or exclusive licence of software IP | Group board, formalised at the level of the Dutch entity | A written assignment or licence deed; no filing requirement of itself |
| Cross-group data processing arrangement | Group compliance function, documented at entity level | A data processing agreement naming the Dutch entity; the Dutch Data Protection Authority is the relevant authority if it is disputed |
| Enterprise contract above local liability authority | Group board approval under the internal matrix | No filing; a contractual document only, held at the Dutch entity |
What this does not cover
- Works council consultation or other employment law consequences of a group decision.
- Platform-specific regulation for large gatekeepers, which applies to a small number of companies only.
- The tax treatment of moving intellectual property or data between group entities.
- The internal procedure of the general meeting itself, including notice and quorum.
Questions
Does a group board resolution bind the Dutch subsidiary automatically?
No. A group board resolution has whatever force the group's own contracts give it. It binds the Dutch entity only once implemented through that entity's own board or general meeting, acting within its articles of association.
Who owns code written by a freelance developer for a Dutch SaaS company?
The developer does, unless there is a written assignment. Dutch copyright law transfers software written by an employee to the employer automatically; it does not extend that default to contractors or freelancers.
Which authority is relevant to a group decision on data processing that touches the Netherlands?
The Dutch Data Protection Authority is the supervisory authority for processing operations that touch the Netherlands, including processing carried out by another group entity on the Dutch entity's behalf.
This material is written by Eva Kuipers, who works on governance and Enterprise Chamber matters at Nolthenius & Partners, with a focus on how group-level decisions map onto the reserved powers of a Dutch entity's own board and general meeting.
A structure report sets out a group's shareholding chain and the decisions reserved at each layer for the Dutch entity in one document: see a structure report. The same reserved-decision question recurs with a different shape in other sectors: compare shareholder rights in an automotive joint venture, or the point in a deal where it resurfaces, post-closing integration in a life sciences transaction. For a group with a UK parent specifically, an ownership chain report for a UK parent sets out how that layer is documented. Where a group decision is later challenged as harmful to the Dutch entity, the standard applied to the director who implemented it is set out at the standard for director liability.
This subject sits within the corporate practice at the firm.
Last legal review: 2026-09-29