Skip to main content
Praxikon

EU declaration of conformity and CE marking for high-risk AI: what Articles 47 and 48 of the AI Act require

··29 min read

Once the conformity assessment is complete, two steps remain before a high-risk AI system may go to market. The provider draws up an EU declaration of conformity for the system (Article 47 AI Act) and affixes the CE marking (Article 48). With the declaration, the provider assumes responsibility in writing for compliance with the requirements of Chapter III, Section 2. The marking shows everyone that it has done so. Both obligations rest on the provider (Article 16, points (g) and (h)). Authorised representatives, importers and distributors check them. A municipality that buys a system looks for them when it procures.

Suppose a Dutch software company develops a model that helps municipalities handle applications for social assistance. For each application, the model gives the caseworker a signal on whether a more thorough check is needed. The company sells the system as a web application to dozens of municipalities. The internal control is done. The product manager asks: "What still has to go on paper, who signs it, and where do you show a CE marking on software that runs in a browser?" And the procurement officer at one of those municipalities asks: "What should I actually get from them?" The example is fictitious.

In short

Article 47 requires the provider to draw up, for each high-risk system, a written, machine readable, physically or electronically signed EU declaration of conformity. It states that the system meets the requirements of Section 2 and contains the eight items of Annex V, including a statement on the GDPR where the system processes personal data. The declaration is translated into a language the authorities can easily understand, is kept available for ten years and is kept up to date. Where the system also falls under other harmonisation legislation with its own declaration, a single declaration covers everything. Article 48 governs the CE marking: the general principles of Regulation (EC) No 765/2008, affixed visibly, legibly and indelibly, digital for systems provided only digitally, and followed by the notified body's number where one was involved in the assessment. The Digital Omnibus (Regulation (EU) 2026/1744) left Article 47, Article 48 and Annex V untouched. Under the text, Articles 47 and 48 apply from 2 August 2026. In our reading they only acquire an object once a high-risk AI system exists: for Annex III systems from 2 December 2027, for Annex I systems from 2 August 2028.

This piece is about what comes after the assessment. How the assessment itself works and when a notified body is needed is covered in internal control or a notified body. What sits in the file behind the declaration is covered in technical documentation under Article 11. Registration in the EU database is covered in registering AI systems.

Where the declaration and the marking sit in the route

Article 16 lists the provider's obligations. Under point (f), the provider ensures that the conformity assessment of Article 43 is carried out before the system is placed on the market or put into service. Under point (g), it draws up the EU declaration of conformity in accordance with Article 47. Under point (h), it affixes the CE marking in accordance with Article 48. Under point (i), it registers itself and the system in accordance with Article 49(1).

Article 47 itself does not name a moment by which the declaration must be ready. In our reading, that follows from the rest of the Regulation: registration under Article 49(1) takes place before the system is placed on the market or put into service, and the provider then submits a copy of the declaration (Annex VIII, Section A, point 11). Importers and distributors also verify, before placing the system on the market or making it available, that the CE marking is there and that the declaration accompanies the system (Article 23(1)(c) and Article 24(1)). The declaration and the marking should therefore exist at the moment the system goes to market or is put into service.

The Regulation defines the CE marking as a marking by which a provider indicates that an AI system is in conformity with the requirements set out in Chapter III, Section 2, and other applicable Union harmonisation legislation providing for its affixing (Article 3, point (24)). The declaration is the document, the marking is the sign on the system. Both concern the same statement by the provider.

Article 47: what the declaration is

Per system, identified precisely. The provider draws up a declaration "for each high-risk AI system", and the declaration identifies the system for which it has been drawn up (paragraph 1). Annex V asks for the AI system's name and type and any additional unambiguous reference allowing its identification and traceability (point 1). In our reading, in practice that means a version or release number: a declaration about "our welfare model" without a version does not show which version the vendor assessed.

Written, machine readable and signed. Paragraph 1 speaks of a "written machine readable, physical or electronically signed" declaration. In our reading it says: a written declaration, in machine-readable form, signed by hand or electronically. Article 47 does not say which type of electronic signature suffices. A scanned PDF without a text layer is in our reading a weak choice, because the declaration must be machine readable.

Translated. The declaration is translated into a language that can be easily understood by the national competent authorities of the Member States in which the system is placed on the market or made available (paragraph 2). A vendor supplying five Member States must therefore check, for each of them, which language works there. The Netherlands has not yet designated a market surveillance authority for the AI Act. In our reading, Dutch is therefore the safe choice for the Dutch market.

Ten years at the authorities' disposal. The provider keeps the declaration at the disposal of the national competent authorities for ten years after the system has been placed on the market or put into service, and submits a copy on request (paragraph 1). Article 18(1)(e) repeats this as part of the documentation the provider keeps for ten years.

Up to date. The provider keeps the declaration up to date "as appropriate" (paragraph 4). After every substantial modification, the system undergoes a new conformity assessment (Article 43(4)). There is one exception for systems that continue to learn after being placed on the market or put into service: changes that the provider pre-determined at the moment of the initial assessment and described in the technical documentation (Annex IV, point 2(f)) are not a substantial modification (Article 43(4), second subparagraph). In our reading, a new or updated declaration for the new version belongs with it.

A single declaration where laws overlap. Where the system is also subject to other Union harmonisation legislation that requires an EU declaration of conformity, a single declaration is drawn up in respect of all Union law applicable to it, containing the information needed to identify that legislation (paragraph 3). Where the AI system in a medical device is high-risk via Article 6(1), because the MDR requires a third-party conformity assessment for the device, the manufacturer makes one declaration under the MDR and the AI Act; for such systems the Section 2 requirements apply from 2 August 2028. See medical AI under the AI Act and the MDR. The Cyber Resilience Act also has its own EU declaration of conformity and the same single-declaration rule (Article 28(3) of Regulation (EU) 2024/2847); that regulation largely applies from 11 December 2027. The Omnibus inserted a provision into the AI Act under which a high-risk system that falls within the scope of that regulation and meets the conditions of Article 12(1) of Regulation (EU) 2024/2847 is deemed to comply with the cybersecurity requirements of Article 15 (Article 42(3), inserted by Article 1, point (18), of Regulation (EU) 2026/1744). One of those conditions is that the required level of cybersecurity protection is demonstrated in the declaration issued under that regulation. Whether a system is a product with digital elements within the meaning of that regulation is a separate question that this piece does not answer.

Annex V can change. The Commission may amend Annex V by delegated act in light of technical progress (paragraph 5). In the consolidated text of 27 July 2026, Annex V is unchanged. The Omnibus also left Article 47 untouched: Article 47(5) appears unchanged in paragraphs 2, 3 and 6 of Article 97, which the Omnibus replaced (Article 1, point (37), of Regulation (EU) 2026/1744).

Annex V: the eight items

PointWhat Annex V requiresWhat it means for the vendor of the welfare model (our translation)
1AI system name and type, and unambiguous references for identification and traceabilityProduct name, version and an identifier that also appears in the registration and the instructions for use
2Name and address of the provider or, where applicable, of its authorised representativeThe company itself; an authorised representative only exists for a provider outside the EU
3A statement that the declaration is issued under the sole responsibility of the providerThis sentence appears in the declaration as such; the IT firm or the customer cannot take over that responsibility
4A statement that the system is in conformity with the Regulation and, if applicable, with other relevant Union law that provides for a declarationOnly the AI Act, unless the system also falls under such other legislation
5Where the system processes personal data: a statement that it complies with the GDPR, Regulation (EU) 2018/1725 and Directive (EU) 2016/680The model processes applicants' data, so this statement must be included
6References to relevant harmonised standards used or other common specifications in relation to which conformity is declaredNo harmonised standard has yet been published for the Section 2 requirements. For the quality management system of Article 17 there is one: the reference of EN 18286:2026 has been in the Official Journal since 14 October 2026 (Implementing Decision (EU) 2026/2274). If the vendor applies that standard, it lists it here
7Where applicable: name and identification number of the notified body, the procedure performed and the certificate issuedNot applicable: Annex III point 5 falls under internal control (Article 43(2))
8Place and date of issue, name and function of the signatory, for or on behalf of whom that person signed, and a signatureA director or someone authorised to represent the company, with a date

The right-hand column is our practical translation, not text from the Regulation.

Two points deserve more attention than they usually get. The first is point 3, read together with Article 47(4): by drawing up the declaration, the provider assumes responsibility for compliance with the requirements of Section 2. The signature is therefore not a formality at the end of a project. In our reading, the signatory signs only once the internal control is really finished and the technical documentation can carry it. If an item of Annex V is missing, the declaration has not been drawn up correctly (Article 83(1)(d)). If the system does not meet the requirements in substance, the provider breaches Article 16(a), to which the fine of Article 99(4)(a) attaches.

The second is point 5. The provider declares that the system complies with the GDPR. In our reading, that statement concerns the system: how it was designed and built. It does not cover every processing operation a municipality later carries out with it. For its own processing, the municipality remains the controller, with its own accountability (Article 5(2) GDPR) and, where needed, its own DPIA (Article 35 GDPR). A vendor that signs point 5 must be able to show what it bases that on. A procurement officer may therefore ask.

Article 48: the CE marking

The general principles. The CE marking is subject to the general principles of Article 30 of Regulation (EC) No 765/2008 (paragraph 1). That article provides, among other things, that the marking is affixed only by the manufacturer or its authorised representative. It is affixed only to products for which harmonisation legislation provides for it. Whoever affixes it takes responsibility for conformity. It is the only marking that attests conformity with that legislation. No signs may be added that mislead third parties about its meaning or form. And Member States act against improper use, with penalties that may be criminal for serious infringements. Under the AI Act, the provider affixes the marking (Article 16(h)). The same regulation sets the graphic form: the letters "CE" in fixed proportions, and at least 5 mm high where the specific legislation does not set another dimension (Annex II to that regulation).

Visible, legible and indelible. The marking is affixed to the system in that way. Where that is not possible or not warranted on account of the nature of the system, it is affixed to the packaging or to the accompanying documentation (paragraph 3).

Digital for digital systems. For high-risk AI systems provided digitally, a digital CE marking is used only if it can easily be accessed via the interface from which the system is accessed, or via an easily accessible machine-readable code or other electronic means (paragraph 2). Recital 129 explains the distinction: a high-risk system integrated into a product gets a physical marking, which may be supplemented by a digital one; a system provided only digitally gets a digital marking. For the welfare model, in our reading, that means a marking the caseworker finds in the web application itself, for example on a fixed screen with information about the system, together with the version and a reference to the declaration. How the 5 mm minimum height translates to a screen is not expressly addressed by either text. In our reading, make sure the marking is clearly legible in the normal view.

The notified body's number. Where a notified body was responsible for the conformity assessment, its identification number follows the marking. The body affixes the number itself, or the provider or its authorised representative does so under the body's instructions. The number also appears in any promotional material stating that the system fulfils the requirements for CE marking (paragraph 4). Under internal control, as with the welfare model, there is no notified body and therefore no number. For biometric systems that follow the route of Annex VII, there is. For biometrics, that route is required where the provider has not applied (or has only partly applied) harmonised standards or common specifications (Article 43(1)).

One marking for several laws. Where the system is also subject to other Union law that provides for CE marking, the marking indicates that the system also fulfils the requirements of that other law (paragraph 5). There is no second CE sign alongside it.

A CE marking is not a quality label for your use case. It says that the provider declares that the system meets the requirements of Section 2. It says nothing about whether a municipality uses the system lawfully, whether the legal basis under the GDPR is in order or whether caseworkers are properly trained. Those are the deployer's obligations.

Who does what in the chain

RoleWhat the Regulation requires regarding the declaration and the marking
ProviderDraws up the declaration and affixes the marking (Article 16(g) and (h)), keeps the declaration available for ten years and up to date (Article 47(1) and (4), Article 18(1)(e)), submits a copy on registration (Article 49(1), Annex VIII Section A point 11)
Authorised representative (provider outside the EU)Verifies that the declaration and the technical documentation have been drawn up and that an appropriate conformity assessment has been carried out, and keeps a copy of the declaration available for ten years (Article 22(3)(a) and (b))
ImporterVerifies before placing on the market that the CE marking is affixed and that the system is accompanied by the declaration and the instructions for use (Article 23(1)(c)), does not place a system with falsified documentation on the market (paragraph 2) and keeps a copy of the declaration for ten years (paragraph 5)
DistributorVerifies before making the system available that the CE marking is there and that the declaration and the instructions for use accompany it (Article 24(1))
DeployerNo express duty to check the marking or the declaration. A public authority does not use a system that is not registered in the EU database, informs the provider or distributor (Article 26(8)) and registers its own use (Article 49(3))

Two additions. Whoever puts its name or trademark on a system, substantially modifies it or changes its intended purpose so that it becomes high-risk is considered the provider and takes on the obligations of Article 16, so also the declaration and the marking (Article 25(1)). A municipality that rolls out the vendor's welfare model under its own name then signs itself, unless the contract allocates the obligations otherwise (Article 25(1)(a): "without prejudice to contractual arrangements"). See when do you become a provider. And the authorised representative terminates the mandate if it considers that the provider is acting contrary to its obligations, and informs the market surveillance authority (Article 22(4)). More on that role in the authorised representative under Articles 22 and 54.

How Articles 47 and 48 connect with Articles 43 and 49

Article 43 is the test, Article 47 is the statement about the result, Article 48 is the visible sign and Article 49 makes the whole findable. The declaration says nothing the assessment has not demonstrated: it is the written record of the internal control under Annex VI or of the assessment by a notified body.

Registration under Article 49(1) applies to the systems of Annex III, except point 2 (critical infrastructure), which are registered at national level (paragraph 5). A copy of the declaration goes into the registration (Annex VIII, Section A, point 11). The information in the EU database will be publicly available in a user-friendly manner, except for the secure section for law enforcement, migration, asylum and border control (Article 71(4) and Article 49(4)). In our reading, a municipality will therefore be able to check in the database whether the declaration it received from the vendor is the same as the registered one.

If something is missing, the supervisor has its own route. Where the market surveillance authority finds that the CE marking has been affixed in violation of Article 48, that there is no marking, that no declaration has been drawn up or that it has not been drawn up correctly, or that registration in the EU database has not been carried out, it requires the provider to put an end to that non-compliance within a period it sets (Article 83(1)(a) to (e)). If the non-compliance persists, it takes appropriate and proportionate measures to restrict or prohibit making the system available on the market, or to ensure that it is recalled or withdrawn without delay (paragraph 2). This is a formal non-compliance: the authority does not first have to show that the system fails the substantive requirements.

What a municipality checks when it buys

A municipality that buys the welfare model is a deployer. The Regulation does not, in so many words, require it to check the CE marking or the declaration. Still, in our reading, this is the simplest vendor check there is, and part of it follows from the law itself.

  1. Ask for the declaration. With importers and distributors, the system must be accompanied by the declaration (Article 23(1)(c) and Article 24(1)). In our reading, a municipality buying directly from the provider may expect the same declaration.
  2. Put the declaration next to what you buy. Does the name and version (point 1) match what is delivered? Is the provider the same party you contract with (point 2)? Is there a GDPR statement (point 5)? Is the declaration dated and signed by someone with a stated function (point 8)? Under internal control, is there no notified body, and for biometrics, is there one with a certificate where the Annex VII route was followed, which biometrics require when no harmonised standards or common specifications were applied (point 7, Article 43(1))?
  3. Look for the CE marking in the interface. For a web application, in our reading, there should be a digital marking the caseworker can find (Article 48(2)).
  4. Check the registration. As a public authority, the municipality does not use an Annex III system that is not registered in the EU database, and informs the provider or distributor (Article 26(8)). It then registers itself, selects the system and registers its use (Article 49(3)).
  5. Agree what happens with a new version. Have the vendor commit contractually to report when a substantial modification requires a new assessment and a new declaration, and to send the new declaration. See AI procurement contracts and assessing an AI vendor.

That is not the end of it. The municipality uses the system in accordance with the instructions for use, assigns human oversight and monitors its operation (Article 26(1), (2) and (5)). It uses the Article 13 information for its DPIA (Article 26(9)). And because it is a body governed by public law using an Annex III system, it carries out a fundamental rights impact assessment (Article 27). What else Article 26 asks is covered in deployer obligations. For this type of system in particular: fraud signals in social assistance.

When the municipality builds it itself

If a municipality builds the model itself or has it built, and puts it into service under its own name, it is the provider: the definition requires both (Article 3, point (3)). Putting into service includes supply for own use (Article 3, point (11)). In our reading, the system then also needs a declaration and a CE marking, even though it is never sold: Article 16(g) and (h) make no distinction between selling and using it yourself.

For the municipality, that means three practical things. It decides who signs on its behalf (Annex V, point 8) and records on what authority. It signs the GDPR statement of point 5 about its own system, so in our reading only once the DPIA and the legal basis assessment are complete. And it registers twice: as provider, itself and the system (Article 49(1)), and as deployer, its use (Article 49(3)). The digital CE marking goes into the caseworkers' application.

In our reading, the model falls under Annex III point 5(a): it evaluates whether people are eligible for essential public assistance benefits. Because it profiles applicants, in our reading the municipality cannot rely on the exception in Article 6(3).

Example 2: the bank

A bank that develops its own model to assess the creditworthiness of individuals is the provider of a high-risk system under Annex III point 5(b). It follows internal control (Article 43(2)), draws up the declaration, affixes a digital CE marking in the application in which underwriters work with the model, and registers itself and the system in the EU database (Article 49(1)). Because the bank also uses the model itself, it is also the deployer and carries out a fundamental rights impact assessment before use (Article 27(1), Annex III point 5(b)); for Annex III systems that obligation applies from 2 December 2027.

Financial law changes little here. Article 47(3) requires a single joint declaration only where other harmonisation legislation also requires an EU declaration of conformity. In our reading, that is not the case for an internal credit model, so the bank writes a declaration under the AI Act alone. The special rule for financial institutions in Article 18(3) concerns keeping the technical documentation, not the declaration. In our reading, the bank keeps the declaration available for ten years under Article 47(1) and Article 18(1)(e).

If the bank buys the model from a fintech, the roles reverse. The bank is the deployer and has no obligation under Article 26(8), which applies only to public authorities. In our reading, the questions from the procurement check above are just as useful. If the fintech is established outside the EU, there must be an authorised representative that has verified the declaration (Article 22), and the importer checks the marking and the declaration (Article 23). As deployer of a system under Annex III point 5(b), the bank also carries out a fundamental rights impact assessment (Article 27(1)). How banking rules relate to the AI Act more broadly is covered in the EBA mapping for the financial sector and AI in credit decisions.

From when?

Article 47(1) and Article 48 are themselves written as obligations and are in Section 5 of Chapter III. That section appears in none of the exceptions in Article 113, third paragraph. It thereby falls under the general date of application of 2 August 2026 (Article 113, second paragraph). In our reading they only acquire an object once a high-risk AI system exists: classification via Article 6(2) and Annex III applies from 2 December 2027, via Article 6(1) and Annex I from 2 August 2028 (Article 113, third paragraph, point (c), as replaced by Article 1, point (40), of Regulation (EU) 2026/1744). Article 16(g) and (h) and the Section 2 requirements apply from those same dates. On that reading, whoever places an Annex III system on the market or puts it into service from 2 December 2027 needs the declaration and the marking at that moment.

If a system was placed on the market or put into service before that date, the high-risk obligations apply only if it subsequently undergoes significant changes in its design. Providers and deployers of systems intended to be used by public authorities must comply with the Regulation by 2 August 2030 (Article 111(2), as amended by Article 1, point (39), of Regulation (EU) 2026/1744). If the welfare model is already running at municipalities before 2 December 2027, the vendor and those municipalities therefore have until 2 August 2030 at the latest, or less if the model undergoes significant changes before then. Recital 39 of Regulation (EU) 2026/1744 clarifies that this rule works per type and model: if at least one unit of a type and model was lawfully placed on the market or put into service before the date, other units of the same type and model also fall under the transitional rule, as long as the design remains unchanged.

Fines

The Regulation does not name Articles 47 and 48 themselves in the penalty rules. They come in through the obligations of the roles. Non-compliance with the obligations of providers under Article 16, of authorised representatives under Article 22, of importers under Article 23, of distributors under Article 24 and of deployers under Article 26 is subject to administrative fines of up to EUR 15 million or, for an undertaking, up to 3 percent of total worldwide annual turnover, whichever is higher (Article 99(4)(a) to (e)). For SMEs and start-ups the lower of the two applies (paragraph 6), and since the Omnibus also for small mid-cap enterprises (paragraph 6a, inserted by Article 1, point (38), of Regulation (EU) 2026/1744). Whether a municipality can be fined under the AI Act is for each Member State to decide (paragraph 8); in the Netherlands this has not yet been laid down in law. See AI Act and GDPR fines for municipalities.

Separately, Article 30(6) of Regulation (EC) No 765/2008 requires Member States to act against improper use of the CE marking and to provide for penalties.

What to do now

  1. Establish whether you are the provider. Do you develop the system or have it developed, and place it on the market or put it into service under your own name or trademark (Article 3, point (3))? Or do you put your name on a purchased system or substantially modify it (Article 25(1))? Then you draw up the declaration and affix the marking. If you only use a purchased system, you do not.
  2. Make one declaration per version. Include the eight points of Annex V, with an unambiguous version identifier that also appears in the registration and the instructions for use.
  3. Appoint the signatory. Record who signs on behalf of your organisation, and that this person signs only once the assessment and the technical documentation are complete.
  4. Substantiate the GDPR statement. Point 5 requires a statement on the GDPR. Make sure you can show what it rests on.
  5. Choose the form of the marking. Physical on a product, digital in the interface for a system provided only digitally, with the notified body's number where one was involved.
  6. Arrange translation, retention and updates. Translate for every Member State you supply, keep for ten years and issue a new declaration after every substantial modification.
  7. Are you a deployer? Ask for the declaration, look for the marking, check the registration and agree that you receive every new declaration.

Unsure whether your system is high-risk and whether you are the provider or the deployer? With the case check you describe the use case in a few questions and see which AI Act and GDPR obligations come into view.

Frequently asked questions about the EU declaration of conformity and the CE marking

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

Written by

Zahed Ashkara, freelance AI and privacy consultant and legal adviser

Zahed Ashkara

Freelance AI and privacy consultant and legal adviser · AI governance & safety

Zahed Ashkara is a freelance AI and privacy consultant and legal adviser for the GDPR and the EU AI Act. Organisations hire him as AI governance consultant, privacy counsel, external DPO or AI governance lead, have him carry out a DPIA, FRIA or AI Act classification, or book an in-company training. He focuses on AI governance and safety, including AI agents. He works exclusively as a freelancer, through Embed AI (trade name Praxikon). He is a Certified AI Compliance Officer (CAICO) and has been a member of the NEN standards committee Artificial Intelligence & Big Data since July 2026.

Follow on LinkedInView expert profile

Use these sources in your AI assistant too: Praxikon in Claude and other assistants

Real-World Stories

Discover how organizations apply this in practice

Related articles

The quality management system for high-risk AI: what Article 17 of the AI Act asks of providers

A provider of a high-risk AI system must have a quality management system that ensures compliance with the AI Act, documented in written policies, procedures and instructions (Article 17). That obligation rests on the provider, not on the organisation that only uses a system it has bought. What the thirteen aspects of paragraph 1 require, what the Digital Omnibus changed for SMEs and small mid-caps, how sectoral quality systems and bank governance count, what EN 18286:2026 does and does not prove, and how it connects with Articles 9, 10, 11, 12, 72 and 73, with a municipality that builds its own system and a bank as examples.

EU AI ActArticle 17Quality management

Technical documentation for high-risk AI: what Article 11 and Annex IV of the AI Act ask of providers

A provider of a high-risk AI system draws up technical documentation before the system is placed on the market or put into service, keeps it up to date and retains it for ten years (Articles 11 and 18). The documentation contains at least the nine points of Annex IV. What those points require, what the Digital Omnibus changed for SMEs and small mid-caps, how a single set of documentation works for products under Annex I, how it connects with Articles 9, 10, 12, 13, 15, 17, 43, 47 and 72, and what a deployer can and cannot ask of its vendor, with a municipality that builds its own system and a bank as examples.

EU AI ActArticle 11Annex IV

Deployer obligations for high-risk AI: what Article 26 of the AI Act requires

An organisation that uses a high-risk AI system has twelve paragraphs of obligations of its own (Article 26 AI Act): use in accordance with the instructions, human oversight by competent people, sound input data, monitoring and notification, keeping logs, informing workers and affected persons, registration by public authorities, feeding the DPIA and cooperating with the authorities. What each paragraph requires, what the Digital Omnibus did and did not change, the rules for banks and insurers, the difference with the provider, and how the FRIA and the right to explanation connect, with a municipality, a bank and an employer as examples.

EU AI ActArticle 26Deployer