What the EU AI Act requires of companies in the Netherlands
Regulation (EU) 2024/1689 has been in force since August 2024, and it lands on organisations in stages. Which duties reach you depends on two questions: what your systems do, and whether you build them or use them.
In short
- Risk follows the use case, not the industry. Annex III is a list of what systems do.
- Most companies are deployers, not providers. Of the risk tiers, the one they meet most often is Article 50 transparency, not high-risk.
- AI literacy under Article 4 has applied since 2 February 2025 and attaches to the organisation, not to a system. It asks for measures, not a guaranteed level of literacy per person (Article 4(1)).
- High-risk duties start 2 December 2027 for Annex III and 2 August 2028 for AI in a product under Annex I, Section A (Article 2(2) and Article 113, third paragraph, point (c)).
The four risk tiers
The Act sorts systems by what they are used for. Nothing here depends on your sector, your size or your turnover.
Unacceptable
Banned outrightSocial scoring, manipulative or deceptive techniques, exploitation of vulnerabilities, untargeted scraping of facial images, and emotion recognition at work and in education. Eight categories in Article 5(1), points (a) to (h), applying since 2 February 2025. The Digital Omnibus added two more, covering nudifiers and AI-generated child sexual abuse material (Article 5(1)(ba) and (bb)). Those apply from 2 December 2026 (Article 113, third paragraph, point (a)).
High
Heaviest obligationsTwo routes in. Annex III lists standalone use cases: biometrics, critical infrastructure, education, employment, essential services, law enforcement, migration, justice. Annex I covers AI that is a safety component of a product covered by the Union harmonisation legislation listed there, such as medical devices or toys, or that is itself such a product, where that product is required to undergo a third-party conformity assessment (Article 6(1)). For products under Section B of Annex I, such as vehicles, civil aviation and, since the Digital Omnibus, machinery, only Article 6(1), Article 60a and Articles 102 to 112 apply; the requirements reach those systems through the sector legislation itself (Article 2(2)). Where AI performs a safety function in machinery and it is unclear whether the third-party condition is met, we treat the system as high-risk. That follows the Commission's draft guidelines of 19 May 2026 and is our reading, not settled law.
Limited
Transparency onlyProviders must design chatbots so that people know they are dealing with AI, unless that is obvious from the context (Article 50(1)). Deployers must disclose deep fakes as artificially generated or manipulated, and the same applies to AI-generated text published to inform the public on matters of public interest, unless it has undergone human review or editorial control and someone holds editorial responsibility for publishing it (Article 50(4)). Providers of generative AI also mark outputs in a machine-readable format (Article 50(2)). These duties have applied since 2 August 2026; generative systems already on the market before that date must meet the marking duty by 2 December 2026 (Article 111(4)). Of the four tiers, this is the one most companies meet, not the high-risk tier.
Minimal
No specific dutiesSpam filters, recommendation engines, most productivity tooling. The AI literacy duty in Article 4 still applies, because it attaches to the organisation rather than to a system.
Provider or deployer
Every obligation in the Act hangs on a role. Build a system, or have one built, and place it on the market or put it into service under your own name or trademark, and you are a provider (Article 3(3)). Payment is irrelevant: giving it away counts, and so does using something you built purely internally.
Use a system under your own authority in your operations and you are a deployer (Article 3(4)). That is where nearly every company sits. The duties are lighter but real: AI literacy (Article 4), transparency where Article 50 applies, and for high-risk systems the deployer obligations of Article 26, which apply from 2 December 2027 for Annex III systems and 2 August 2028 for AI in a product under Annex I, Section A (Article 2(2) and Article 113, third paragraph, point (c)).
A deployer can also turn into a provider through Article 25, but that route runs through high-risk systems only. It applies when you put your name or trademark on a high-risk system, when you substantially modify one so that it remains high-risk, or when you change the intended purpose of a system so that it becomes high-risk. That route applies to Annex III systems from 2 December 2027 and to AI in a product under Annex I, Section A, from 2 August 2028 (Article 2(2) and Article 113, third paragraph, point (c)).
The line matters more than it looks, because it moves. Put an AI feature into the product you sell and you become a provider for that feature. If that feature is high-risk, technical documentation (Article 11) and a conformity assessment (Article 43) come with it; if it is not, your provider duties are mainly AI literacy and, where it applies, Article 50.
Who supervises the AI Act in the Netherlands
The Act is a regulation, so its substance is identical in every member state. What differs is who enforces it and how the national implementing law is written, and the Netherlands has not finished that yet.
The draft Dutch implementing act proposes the Dutch Data Protection Authority (AP) and the Dutch Authority for Digital Infrastructure (RDI) as joint coordinating supervisors. Supervision follows the system, not the sector: the AP for most Annex III systems, the financial supervisors for credit scoring and for risk assessment and pricing in life and health insurance at financial institutions, and the existing product regulators for AI in products. That act is still a draft: it has not been submitted to the Dutch House of Representatives, and submission is planned for Q2 2027. Any English source presenting a settled list of Dutch supervisors is ahead of the facts.
One thing is already settled: general-purpose AI models are supervised by the European Commission and the AI Office under Article 88, not by national authorities.
Frequently asked questions
Click a question to see the answer. These are fixed answers; the AI Act assistant inside the platform answers your own questions.
A deployer, almost certainly. You are a deployer when you use an AI system under your own authority in your operations (Article 3(4)), which covers nearly every business using ChatGPT, Copilot or AI features inside other software. You become a provider when you develop a system, or have one developed, and place it on the market or put it into service under your own name or trademark (Article 3(3)). Building an AI feature into your own product makes you a provider, and so does purely internal use of something you built yourself.
No, and this is the most common misreading. The AI Act classifies on what a system does, not on the industry it sits in. Annex III is organised by use case. A hospital using AI to forecast bed occupancy is not high-risk; the same hospital using AI to triage emergency patients falls under Annex III, point 5(d). Sector tells you where high-risk uses tend to cluster, nothing more.
No. Article 6(3) carves out systems that perform a narrow procedural task, improve the result of a previously completed human activity, detect decision-making patterns or deviations without replacing or influencing a previously completed human assessment without proper human review, or perform a preparatory task. The carve-out falls away the moment the system profiles natural persons. Human oversight on its own is not an exemption. The Commission reads it the same way in its draft guidelines of 19 May 2026, which are not yet final and not binding: a formal review does not save a system once its output effectively drives the outcome. A provider relying on the carve-out documents that assessment before placing the system on the market and registers it in the EU database (Article 6(4) and Article 49(2)).
Up to EUR 35 million or 7 percent of worldwide annual turnover, whichever is higher, for breaching the Article 5 prohibitions (Article 99(3)). Most other infringements, including those of the deployer obligations and Article 50, carry up to EUR 15 million or 3 percent (Article 99(4)), and supplying incorrect information to authorities up to EUR 7.5 million or 1 percent (Article 99(5)). For SMEs the lower of the two amounts applies rather than the higher (Article 99(6)). Since the Digital Omnibus, small mid-cap enterprises also get the lower amount, except for the Article 5 prohibitions (Article 99(6a)). Each member state sets the actual penalty rules (Article 99(1)). In the Netherlands they sit in the draft implementing act, so no Dutch authority can impose an AI Act fine yet.
Not settled yet. The draft Dutch implementing act proposes the Dutch Data Protection Authority (AP) and the Dutch Authority for Digital Infrastructure (RDI) as joint coordinating supervisors. Which authority supervises a system depends on what the system does, not on the sector: the AP for most Annex III systems, such as recruitment and triage, AFM and DNB for credit scoring and for risk assessment and pricing in life and health insurance at financial institutions, and the existing product regulators for AI in products, such as the Health and Youth Care Inspectorate (IGJ) for medical devices. That act is still a draft and has not been submitted to the Dutch House of Representatives; submission is planned for Q2 2027. Treat any list of Dutch supervisors as provisional. General-purpose AI models are a separate matter: those sit with the European Commission and the AI Office under Article 88, not with any national authority.
Next steps in English
The rest of this site is in Dutch. These two pages are not.
Reading Dutch? The full guide is at /eu-ai-act.