A certificate from a notified body does not last forever. And very occasionally a high-risk AI system may be used while the conformity assessment is still under way. Three short articles in Section 5 of Chapter III of the AI Act deal with this. Article 44 is about the certificate itself: the language, the validity, the extension and the suspension or withdrawal. Article 45 sets out whom the notified body informs. Article 46 contains the exception: for exceptional reasons a market surveillance authority may authorise a system to be placed on the market or put into service for a limited period before the assessment is complete.
Suppose it is January 2029. After days of heavy rain a dyke is at risk of failing in a Dutch safety region (veiligheidsregio), and the emergency control room is receiving more emergency calls than it can handle. A supplier has a system that sorts emergency calls by urgency, but the conformity assessment is not finished. May the safety region use it anyway? And what does the municipality down the road do, which uses a system whose certificate expires in three months? The examples are invented.
In short
The Digital Omnibus on AI (Regulation (EU) 2026/1744) did not amend Articles 44, 45 and 46. It did replace Article 43(3), on AI in products that already fall under European product legislation.
A certificate from a notified body is valid for the period it indicates: no more than five years for AI systems covered by Annex I and no more than four years for AI systems covered by Annex III. Extension is possible only at the request of the provider and after a re-assessment. If the system no longer meets the requirements and the provider does not take corrective action in time, the notified body suspends or withdraws the certificate or imposes restrictions on it. An appeal procedure against its decisions must be available.
The notified body reports issued, refused, restricted, suspended and withdrawn certificates to the notifying authority and, partly only on request, to other notified bodies. The organisation that uses the system is not part of that chain.
For exceptional reasons of public security, the protection of life and health of persons, environmental protection or the protection of key industrial and infrastructural assets, a market surveillance authority may authorise a specific high-risk AI system to be placed on the market or put into service for a limited period while the assessment is carried out. It may do so only if it concludes that the system complies with the requirements of Section 2. In urgent cases law enforcement authorities and civil protection authorities may start without authorisation, provided they request it during or after the use without undue delay. If the authorisation is refused, the use stops at once and all results and outputs are discarded.
For the systems of Annex III no market surveillance authority has yet been designated in the Netherlands. Who will decide on an authorisation is therefore not yet settled.
This piece is about the certificate and about the derogation. When a provider needs a notified body is covered in conformity assessment: internal control or a notified body. Who designates those bodies, and what happens when an assessor itself no longer meets the requirements, is covered in notifying authorities and notified bodies under Articles 28 to 39. And what follows after the assessment is covered in the EU declaration of conformity and the CE marking of Articles 47 and 48.
Where these articles sit in the route
Most providers of a high-risk AI system carry out the conformity assessment themselves, using the internal control of Annex VI. That applies to the systems in points 2 to 8 of Annex III, such as systems for welfare benefits, creditworthiness, education and recruitment (Article 43(2)). No notified body is involved, and so there is no certificate within the meaning of Article 44 either.
There is a certificate only where a notified body has assessed under Annex VII. That is the mandatory route for biometric systems in point 1 of Annex III where the provider has not fully applied harmonised standards or common specifications, or where these do not exist (Article 43(1)). The provider may also choose that route voluntarily. Where the system is intended to be put into service by law enforcement, immigration or asylum authorities, the market surveillance authority acts as the notified body (Article 43(1), third subparagraph). For AI in products covered by the product legislation of Annex I, Section A, such as medical devices, the provider follows the assessment procedure of that product legislation, and the requirements of the AI Act form part of that assessment (Article 43(3), as replaced by Regulation (EU) 2026/1744).
Annex VII has two outcomes. The notified body assesses the provider's quality management system and notifies its decision on it (point 3.2). And it assesses the technical documentation of the system; where the system conforms to the requirements of Section 2, it issues a Union technical documentation assessment certificate (point 4.6). That certificate contains the name and address of the provider, the conclusions of the examination, the conditions (if any) for its validity and the data necessary to identify the AI system.
Article 44: the certificate
The language. The certificate is drawn up in a language that can be easily understood by the relevant authorities in the Member State in which the notified body is established (paragraph 1). A certificate from a body in another Member State therefore does not have to be in Dutch.
The validity. A certificate is valid for the period it indicates. That period may not exceed five years for AI systems covered by Annex I and four years for AI systems covered by Annex III (paragraph 2). Shorter is allowed: the notified body sets the period, the Regulation only the maximum.
The extension. Extension is not automatic. The provider requests it, and the notified body carries out a re-assessment in accordance with the applicable conformity assessment procedures. Each extension is again for no more than five years for Annex I and four years for Annex III (paragraph 2).
Supplements. A supplement to a certificate remains valid as long as the certificate it supplements is valid (paragraph 2). Such a supplement comes about when the provider changes the system in a way that could affect compliance or the intended purpose. The notified body that issued the certificate assesses that change and decides whether a supplement is sufficient or a new conformity assessment is needed (Annex VII, point 4.7; Article 43(4)).
Suspension, withdrawal, restriction. Where the notified body finds that the system no longer meets the requirements of Section 2, it suspends or withdraws the certificate or imposes restrictions on it, taking account of the principle of proportionality, unless the provider takes appropriate corrective action within an appropriate deadline set by the body. The body gives reasons for its decision (paragraph 3). It obtains that knowledge through, among other things, the periodic audits of the approved quality management system, during which it may also carry out additional tests of systems that hold a certificate (Annex VII, point 5.3).
Appeal. An appeal procedure against decisions of notified bodies, including on certificates issued, must be available (paragraph 3, second subparagraph). How that will work in the Netherlands is set out below.
Article 44 is about the system: does it still comply? That is different from Article 36, which governs what happens to certificates when the designation of the assessor itself is restricted, suspended or withdrawn.
Article 45: who hears what?
A notified body does not keep its decisions to itself. It informs the notifying authority of (paragraph 1):
- the Union technical documentation assessment certificates, the supplements to them and the quality management system approvals it has issued;
- any refusal, restriction, suspension or withdrawal of such a certificate or approval;
- circumstances affecting the scope of or the conditions for its notification;
- requests for information about its assessments that it receives from market surveillance authorities;
- on request: the assessments and other activities it has performed within the scope of its notification, including cross-border activities and subcontracting.
It informs the other notified bodies of the quality management system approvals it has refused, suspended or withdrawn, and of the certificates and supplements it has refused, withdrawn, suspended or otherwise restricted. What it has issued, it reports to them on request (paragraph 2). Bodies carrying out similar assessments covering the same types of AI systems receive relevant information on negative assessment results and, on request, on positive ones (paragraph 3).
In our reading this works, together with the application rules, as a brake on going from one assessor to the next. With every application the provider declares in writing that the same application has not been lodged with any other notified body (Annex VII, points 3.1(f) and 4.2(b)), and a body that rejects a system lets the others know.
Who is not in the chain. The deployer, the organisation that uses the system, hears nothing from the notified body. It depends on the provider, which informs deployers when it takes corrective action (Article 20(1)), on the registration in the EU database, which contains the type, number and expiry date of the certificate (Annex VIII, Section A, point 8), and on what it has arranged for itself in the contract.
A difference between the language versions. Paragraph 4 reads in the English text: "Notified bodies shall safeguard the confidentiality of the information that they obtain, in accordance with Article 78." The Dutch, German and French texts place the duty on the notifying authorities instead; the Dutch text reads "Aanmeldende autoriteiten waarborgen dat de door hen verkregen informatie overeenkomstig artikel 78 vertrouwelijk wordt behandeld." For notifying authorities the same sentence already appears in Article 28(6). In our reading it makes little difference to the outcome: Article 78(1) requires notified bodies and any other person involved in the application of the Regulation to respect confidentiality.
Article 46: using a system while the assessment is still under way
The main rule is strict: the provider ensures that the conformity assessment has been carried out before the system is placed on the market or put into service (Article 16, point (f)). Article 46 makes a narrow exception to that. Recital 130 gives the reason: under certain conditions, rapid availability of innovative technologies may be crucial for the health and safety of persons, the protection of the environment and climate change and for society as a whole.
The authorisation (paragraph 1). Upon a duly justified request, a market surveillance authority may authorise specific high-risk AI systems to be placed on the market or put into service within the territory of its Member State. It may do so only for exceptional reasons of:
- public security;
- the protection of life and health of persons;
- environmental protection;
- the protection of key industrial and infrastructural assets.
The authorisation is for a limited period, while the necessary conformity assessment procedures are being carried out, and those procedures are completed without undue delay. The Regulation does not say who submits the request. In our reading that can be the provider, but also the organisation that wants to use the system.
No discount on the requirements (paragraph 3). The market surveillance authority issues the authorisation only if it concludes that the system complies with the requirements of Section 2. Article 46 therefore derogates from the procedure of Article 43, not from the requirements themselves: risk management, data, technical documentation, logging, transparency, human oversight, and accuracy, robustness and cybersecurity. Anyone who wants an authorisation must be able to show the authority that the system meets them.
Urgency without authorisation (paragraph 2). In a duly justified situation of urgency for exceptional reasons of public security, or in the case of a specific, substantial and imminent threat to the life or physical safety of natural persons, law enforcement authorities or civil protection authorities may put a specific high-risk AI system into service without authorisation. The condition is that they request the authorisation during or after the use without undue delay. If it is refused, the use is stopped with immediate effect and all results and outputs of that use are immediately discarded.
Scrutiny by the other Member States and the Commission (paragraphs 3 to 6). The market surveillance authority informs the Commission and the other Member States of every authorisation; it does not have to include sensitive operational data in relation to the activities of law enforcement authorities. If no Member State or the Commission raises an objection within 15 calendar days, the authorisation is deemed justified. If a Member State objects within that period, or the Commission considers the authorisation contrary to Union law or the conclusion on compliance unfounded, the Commission enters into consultations with the Member State concerned without delay. The operators concerned are consulted and can present their views. The Commission then decides whether the authorisation is justified. If it finds that it is not, the market surveillance authority withdraws the authorisation.
Products (paragraph 7). For high-risk AI systems related to products covered by the product legislation of Annex I, Section A, only the derogations laid down in that product legislation itself apply. For a medical device that is Article 59 of Regulation (EU) 2017/745, under which a competent authority may, on a duly justified request, authorise the placing on the market or putting into service of a specific device whose use is in the interest of public health or patient safety or health. See also medical AI under the AI Act and the MDR.
What Article 46 does not do
- It lifts no prohibition. Article 46 derogates only from Article 43. The prohibited practices of Article 5 remain prohibited. Real-time remote biometric identification in publicly accessible spaces for law enforcement has its own system of prior authorisation, with its own urgency rule (Article 5(3)).
- It does not postpone the other obligations. In our reading the other obligations continue to apply, such as the obligations of the deployer (Article 26) and the fundamental rights impact assessment before first use (Article 27(1) and (2)). Article 27(3) does mention Article 46(1): in that case the deployer may be exempted from notifying the market surveillance authority of the results. In our reading the assessment itself remains necessary.
- It does not settle the registration. The EU declaration of conformity, the CE marking and the registration in the EU database (Article 49) normally follow a completed assessment, and a public authority may not use a system that has not been registered in the EU database (Article 26(8)). The Regulation does not expressly say how this works under an authorisation. Put that question to the market surveillance authority with the request.
- It is not a route for haste. Backlogs, a tender that overruns or a competitor that is faster are not among the four reasons.
- It does not apply across borders. The authorisation applies within the territory of the Member State of the market surveillance authority that issues it.
Separately, AI systems used exclusively for military, defence or national security purposes fall outside the AI Act altogether (Article 2(3)). Article 46 is not needed for those.
Who decides in the Netherlands?
That is not yet settled. For the systems of Annex III no market surveillance authority has yet been designated in the Netherlands. For AI in products covered by Annex I, Section A, such as medical devices, it is the authority designated under that product legislation (Article 74(3)); there, only the derogations of that product legislation itself apply (Article 46(7)). The draft bill for the Dutch AI Act Implementation Act (Uitvoeringswet AI-verordening) was open for internet consultation until 1 June 2026; according to the Digital Affairs planning letter, submission to the House of Representatives is planned for the second quarter of 2027 (Parliamentary Paper 26643, No 1554). What the draft says:
- The market surveillance authorities. For Annex III the draft designates the Dutch Data Protection Authority (AP) for points 1, 3, 4, 5(a) and (d), 6, 7 and 8(b); the Minister of Economic Affairs and Climate Policy and the Minister of Infrastructure and Water Management for point 2 (critical infrastructure); and the AFM, DNB and the AP for point 5(b) and (c) (Article 2.2(1)(c) of the draft). Those authorities exercise the tasks and powers that the Regulation confers on the market surveillance authority (Article 2.2(3) of the draft). In our reading a request for authorisation for a system that sorts emergency calls (point 5(d)) would then go to the AP. That is not certain: the list in the draft names Section 3 of Chapter III and not Section 5, which contains Article 46, and the draft is not yet law.
- Articles 45 and 46. The transposition table attached to the draft explanatory memorandum states for both articles that by their nature they require no implementation. The draft therefore does not set out a Dutch procedure of its own for the authorisation.
- Appeal against the notified body. According to the draft explanatory memorandum (section 4.3.2), a decision of a notified body within the meaning of Article 1:3 of the General Administrative Law Act (Awb) is open to the legal remedies of Chapters 1, 6, 7 and 8 of that Act, and issuing a conformity certificate falls within that. The table calls this existing law.
- The notifying authority. For the biometric systems in point 1 of Annex III, the draft makes this the Minister of Economic Affairs and Climate Policy, with the exception of systems intended for law enforcement, immigration or asylum authorities (Article 2.1 of the draft). That minister would then receive the notifications of Article 45(1).
Who will supervise which AI systems in the Netherlands is covered in who will supervise and in the consultation on the Dutch AI Act Implementation Act.
Where the GDPR comes in
An authorisation is not a legal basis. Article 46 says nothing about personal data. A system that sorts emergency calls processes data about callers, often including data concerning their health. That requires a legal basis under Article 6 GDPR, for a safety region as a rule the performance of a task carried out in the public interest (paragraph 1, point (e)). According to recital 46 GDPR, processing based on the vital interest of another natural person (paragraph 1, point (d)) should in principle take place only where the processing cannot be manifestly based on another legal basis; the same recital mentions natural and man-made disasters as an example of processing that serves both important grounds of public interest and the vital interests of the data subject. For health data an exception under Article 9(2) GDPR is needed as well.
The DPIA does not wait for the crisis. Where processing is likely to result in a high risk to the rights and freedoms of natural persons, the data protection impact assessment is carried out prior to the processing (Article 35(1) GDPR). Article 35 GDPR has no urgent procedure. Anyone who wants to be able to deploy a new system in a crisis therefore carries out the DPIA in advance, for the scenario in which the system is needed.
Police and justice. Processing by competent authorities for the purposes of the prevention, investigation, detection or prosecution of criminal offences is not governed by the GDPR (Article 2(2)(d) GDPR) but by the regime of Directive (EU) 2016/680.
The certificate does not test the GDPR. The notified body assesses whether the system conforms to the requirements of Section 2 of Chapter III (Annex VII, point 4.6). That the system complies with the GDPR is something the provider itself declares in the EU declaration of conformity, where the system involves the processing of personal data (Annex V, point 5). And the deployer is as a rule itself the controller for its own use.
Discarding after a refusal. If the authorisation is refused after an urgent deployment, all results and outputs of that use must be discarded immediately (Article 46(2)). That only works if it has been established in advance where those outputs end up: in which systems, files and logs.
Main example: the safety region and the municipality
The high water. In the Netherlands a safety region is a public body that the municipal executives of the municipalities in a region set up together (Article 9 of the Safety Regions Act). Its tasks include organising disaster response and crisis management and providing the emergency control room function (Article 10 of the Safety Regions Act). The control rooms themselves are governed by the Dutch Police Act 2012; who the deployer is depends on who puts the system to use. In this example that is the safety region. In January 2029 the safety region from the introduction wants to use a system that evaluates and classifies emergency calls and helps establish priority in the dispatching of emergency services.
- Is it high-risk? Yes. Such a system is listed in Annex III, point 5(d). It is a new system, so the high-risk obligations apply.
- Which assessment goes with it? The internal control of Annex VI, by the provider (Article 43(2)). No notified body and no certificate are involved. The provider is simply not finished yet. If the system were also a medical device, for example for patient triage, only the derogations of the product legislation would apply (Article 46(7)).
- May the safety region start anyway? The AI Act does not define the term civil protection authority. In our reading a safety region falls within it, because disaster response and crisis management are its statutory task. In our reading an imminent dyke breach is also a specific, substantial and imminent threat to the life or physical safety of people. The safety region can then put the system into service without authorisation, provided it requests the authorisation during or after the use without undue delay (Article 46(2)).
- What does the market surveillance authority test? Whether the system complies with the requirements of Section 2 (paragraph 3). For that the safety region needs the provider's technical documentation and test results. Without those documents the authority cannot, in our reading, reach that conclusion.
- And if the authorisation is refused? Then the use stops at once and all results and outputs are discarded. The control room must therefore be able to fall back on its ordinary way of working, and must know in which files the system's priorities have ended up.
- What simply continues to apply? In our reading everything except the procedure of Article 43: human oversight by people trained for it, use in accordance with the instructions for use and keeping logs (Article 26), and the fundamental rights impact assessment, because a safety region is a body governed by public law (Article 27(1)). That assessment may rely on an earlier assessment in a similar case or on an assessment by the provider (Article 27(2)). Mind the registration as well: a public authority registers the use before deployment (Article 49(3)) and may not use an unregistered system (Article 26(8)); the Regulation does not expressly say how this works in an urgent deployment. The GDPR applies alongside.
The lesson: Article 46(2) only helps those who have prepared. A safety region that wants to be able to deploy a system in a crisis already has the DPIA, the fundamental rights impact assessment, the arrangements with the supplier about the documentation and the fallback scenario in place.
The backlog at the municipality. A municipality has a large backlog of applications for special assistance (bijzondere bijstand) and wants to start using a new system that assesses applications (Annex III, point 5(a)) while the supplier is still completing the internal control. In our reading that is not possible under Article 46. A backlog is not an exceptional reason of public security, of protection of life and health, of environmental protection or of protection of key assets, and a municipal social services department is not a law enforcement authority or civil protection authority that can start without authorisation.
The certificate that expires. The same municipality uses a module in its customer contact centre that infers from callers' voices whether someone is angry or upset. That is emotion recognition (Annex III, point 1(c)). The module analyses callers only: analysing the voices of the municipality's own staff would be emotion recognition in the workplace, which is in principle prohibited (Article 5(1)(f)). Callers must be informed of the operation of the system (Article 50(3)). The system came on the market in 2028 with a one-year certificate from a notified body, which expires in three months. What the municipality checks:
- Has the supplier requested the extension? Extension comes only at the request of the provider and after a re-assessment (Article 44(2)).
- Is the database correct? The registration in the EU database contains the expiry date of the certificate (Annex VIII, Section A, point 8) and is kept up to date.
- What does the contract say? The notified body does not inform the municipality (Article 45). The municipality therefore lays down that the supplier reports without delay if the certificate expires or is restricted, suspended or withdrawn, and what then happens to the use. See AI procurement contracts.
- What if the certificate is withdrawn? The AI Act does not say in so many words what the deployer then does. It must, however, inform the provider or distributor and the market surveillance authority and suspend the use where it has reason to consider that use in accordance with the instructions may result in the system presenting a risk within the meaning of Article 79(1) (Article 26(5)). In our reading a withdrawn certificate is a reason to examine that immediately.
Example 2: the bank and the insurer
Haste is not a reason. A bank wants to put a new model for the creditworthiness of consumers (Annex III, point 5(b)) into service before the supplier has finished the internal control, because a competitor is faster. That fits none of the four reasons of Article 46(1). The bank waits until the conformity assessment has been carried out and asks for the EU declaration of conformity and the registration. A certificate from a notified body is not part of this.
Fraud detection. A system that only detects financial fraud is excluded from point 5(b) of Annex III. In our reading it is then not a high-risk system, unless it falls under another point of Annex III. Without high risk there is no conformity assessment and so no derogation is needed either. The GDPR does apply.
The insurer and the expiry date. An insurer uses an emotion recognition module for callers, with a certificate, when handling claims by telephone. The insurer records the expiry date of four years at most in its contract management and asks the supplier about the re-assessment well in advance. For the pricing model for life and health insurance (point 5(c)) internal control suffices; there is no certificate there.
Briefly on education and HR. Systems for admission, assessment and monitoring during tests (Annex III, point 3) and for recruitment and workforce management (point 4) follow internal control. There is no certificate within the meaning of Article 44, and in our reading a school or employer has none of the four reasons of Article 46.
From when?
- Articles 44, 45 and 46 are in Section 5 of Chapter III. That section is in none of the exceptions of Article 113, third paragraph, and therefore falls under the general date of application of 2 August 2026 (Article 113, second paragraph).
- In practice, in our reading, they only acquire meaning once there are high-risk AI systems to which the requirements apply: from 2 December 2027 for Annex III and from 2 August 2028 for Annex I (Article 113, third paragraph, point (c), as replaced by Regulation (EU) 2026/1744). Before those dates no conformity assessment is required for an Annex III system, and so no derogation is needed either.
- Existing systems. For systems that were already on the market or in service before the date of application of Chapter III, the high-risk obligations apply only after a significant change in the design; systems intended to be used by public authorities must comply by 2 August 2030 at the latest (Article 111(2), as replaced by Regulation (EU) 2026/1744).
- The notified bodies have been subject to Section 4 since 2 August 2025 (Article 113, third paragraph, point (b)). Article 78 on confidentiality has applied since the same date.
- The Dutch AI Act Implementation Act is a draft; submission to the House of Representatives is planned for the second quarter of 2027.
Fines
The penalty provision of the Regulation does not itself name Articles 44, 45 and 46. For notified bodies it names the requirements and obligations of Article 31, Article 33(1), (3) or (4), and Article 34 (Article 99(4), point (f)). The Dutch draft goes further: it also makes infringement of Article 44(1) and (3) and Article 45(2) and (3) subject to a fine, up to the maximum of Article 99(4) (Article 3.7(3) of the draft). A provider that places a system on the market or puts it into service without a conformity assessment and without authorisation infringes Article 16, point (f); the maximum for that is EUR 15 million or, for an undertaking, 3 percent of worldwide annual turnover if that is higher (Article 99(4), point (a)). Anyone who supplies incorrect, incomplete or misleading information to a notified body or a national competent authority in reply to its request risks a fine of up to EUR 7.5 million or 1 percent (Article 99(5)). Whether a public authority can receive an AI Act fine is for each Member State to decide (Article 99(8)); in the Netherlands that has not yet been laid down by law. According to the draft explanatory memorandum, the fine provisions of the draft do not rule out such fines being imposed on public authorities. See fines under the AI Act and the GDPR for municipalities.
What to do now
As the user of a system with a certificate (municipality, insurer):
- Ask which document you are holding. A certificate within the meaning of Article 44 comes from a notified body and belongs to the procedure of Annex VII. For the systems in points 2 to 8 of Annex III it does not exist.
- Record the expiry date. Four years at most for Annex III and five years for Annex I. Ask the supplier about the re-assessment well in advance.
- Arrange the notification in the contract. You will not hear of a suspension, restriction or withdrawal from the notified body. Have the supplier take on that duty.
- Check whether the certificate covers this system and this version, and whether there are supplements for later changes.
As an organisation that wants to be able to use AI in a crisis (safety region, police, water authority, hospital):
- Decide now which systems you would want to use in a crisis and whether they fall under Annex III.
- Carry out the DPIA and the fundamental rights impact assessment in advance, per scenario. Neither has an urgent procedure for carrying it out; only for notifying the results of the fundamental rights impact assessment may an exemption apply (Article 27(3)).
- Agree with the supplier that the technical documentation and the test results are immediately available to the market surveillance authority.
- Lay down who requests the authorisation, and when. Only law enforcement authorities and civil protection authorities may start in urgent cases and request the authorisation during or after the use (Article 46(2)). Other organisations, such as a water authority or a hospital, request the authorisation in advance (paragraph 1); for a medical device the derogation of the product legislation applies (paragraph 7).
- Keep outputs separate. You must be able to discard them if the authorisation is refused, and you must be able to fall back on the ordinary way of working.
As a provider: plan the re-assessment well before the expiry date, report changes to the notified body before you implement them, and do not count on Article 46 to meet a deadline.
Want to know whether an application falls under Annex III and which obligations under the AI Act and the GDPR go with it? With the case check you describe the application in a few questions.
Frequently asked questions about certificates and the derogation of Article 46
Sources
Newsletter
Every Tuesday, the AI Act week ahead in 5 minutes
A practical briefing on deadlines, new guidance and enforcement, so you know what matters this week. No spam and you can unsubscribe in one click.
Practical and short · No spam · One-click unsubscribe