Skip to main content
Praxikon

Importers and distributors of high-risk AI: what Articles 23 and 24 of the AI Act require

··32 min read

Most explanations of the AI Act deal with two parties: the provider that develops an AI system and brings it to market, and the deployer that uses it. In practice there are often parties in between. A supplier from outside the European Union sells through a European subsidiary, a reseller or an integrator. For those intermediaries the Regulation has its own obligations: Article 23 for the importer and Article 24 for the distributor. They are short, but they decide who in the chain must check what before a high-risk AI system reaches a customer.

Suppose a Dutch municipality wants to use a system that helps caseworkers handle applications for social assistance. The system was developed by an American company and carries that company's name. The municipality does not buy directly, but through a Dutch reseller that sells the licences, configures the system and provides first-line support. The procurement officer asks: "Who is actually responsible for what here? And what should I put in the contract?" The example is fictitious.

In short

An importer is a party in the EU that places on the market an AI system bearing the name or trademark of a party outside the EU (Article 3, point 6). A distributor is any other party in the supply chain that makes the system available on the EU market (Article 3, point 7). Before placing the system on the market, the importer verifies that the provider has carried out the conformity assessment, drawn up the technical documentation, affixed the CE marking with the declaration and instructions for use enclosed, and appointed an authorised representative (Article 23(1)). When in doubt, it does not supply (paragraph 2). It adds its own name and address (paragraph 3), looks after storage and transport (paragraph 4), keeps the documents for ten years (paragraph 5) and cooperates with the authorities (paragraphs 6 and 7). The distributor checks the CE marking, the declaration, the instructions for use, the name and address of provider and importer and the provider's quality management (Article 24(1)), does not supply when in doubt (paragraph 2), takes corrective action if it already has (paragraph 4) and gives the authorities information (paragraphs 5 and 6). Anyone who puts their own name on the system, substantially modifies it or changes its purpose so that it becomes high-risk is a provider (Article 25(1)). The Digital Omnibus (Regulation (EU) 2026/1744) did not amend Articles 23, 24 and 25(1). It does allow the Commission, under the new Article 2(13), to limit the application of specific requirements and obligations in Articles 9 to 15 and 17 to 25, and so also in Articles 23 and 24, for Annex I systems, where the Union harmonisation legislation in Section A of Annex I provides an equivalent or higher level of protection, through delegated acts it adopts by 2 August 2027. Articles 23 and 24 apply to Annex III systems from 2 December 2027 and to systems related to products under Section A of Annex I from 2 August 2028. They do not apply to systems related to products under Section B of Annex I (Article 2(2)).

This piece is about the intermediaries. What the provider itself must do is covered in, among others, internal control or a notified body and the EU declaration of conformity and CE marking. What the deployer must do is covered in deployer obligations.

Who is the importer, who is the distributor?

The Regulation works with fixed roles, together called "operators" (Article 3, point 8). Five of them matter here.

RoleDefinition (Article 3)In the example
Provider (point 3)Develops an AI system or has it developed, and places it on the market or puts it into service under its own name or trademarkThe American company
Authorised representative (point 5)Party in the EU with a written mandate from the provider to perform obligations on its behalfThe office in the EU that the American company appoints for this
Importer (point 6)Party in the EU that places on the market an AI system bearing the name or trademark of a party established in a third countryThe Dutch reseller, if it is the first to supply the system in the EU
Distributor (point 7)Party in the supply chain other than the provider or the importer that makes an AI system available on the Union marketA further link after the importer, for example a second reseller
Deployer (point 4)Uses an AI system under its authorityThe municipality

Two concepts make the difference between importer and distributor. "Placing on the market" is the first making available of a system on the Union market (point 9). "Making available on the market" is any supply in the course of a commercial activity, whether in return for payment or free of charge, for distribution or use on the Union market (point 10). The importer therefore makes the first supply in the EU of a system bearing a foreign name. The distributor makes every supply after that. An importer only exists where the provider is outside the EU; a Dutch provider has no importer, though it may have distributors.

A party can also hold two roles at once, and then it carries the obligations of both. The Regulation itself gives the example of an operator that is a distributor and an importer at the same time (recital 83).

For software supplied as a service, the allocation of roles is less obvious than for a box arriving at a port. The Regulation makes no exception for software as a service. In our reading, the party that makes the first supply in the EU, that is the party that first sells the subscription to a customer in the EU, is the importer, even if the software runs on servers outside the EU. If the American company signs the contract with the municipality itself, there is in our reading no importer, and the provider supplies directly, with its authorised representative in the EU. Set out the roles in the contract rather than reconstructing them afterwards.

Article 23: what the importer must do

Four checks before placing on the market. Before placing the system on the market, the importer ensures that it complies with the Regulation by verifying that (paragraph 1):

  1. the provider has carried out the conformity assessment procedure of Article 43 (point (a));
  2. the provider has drawn up the technical documentation in accordance with Article 11 and Annex IV (point (b));
  3. the system bears the required CE marking and is accompanied by the EU declaration of conformity referred to in Article 47 and instructions for use (point (c));
  4. the provider has appointed an authorised representative in accordance with Article 22(1) (point (d)).

These are checks on what the provider has done. In our reading, the importer does not have to retest the model itself, but it must be able to show that it verified the four points, and with what. A declaration without a version number, or instructions for use that do not match the system supplied, should stand out in that check. What the technical documentation looks like is covered in technical documentation under Article 11; what belongs in the instructions for use is covered in instructions for use under Article 13. The authorised representative represents the provider from outside the EU in the Union; see the authorised representative under Articles 22 and 54. If there is none, the importer in our reading does not place the system on the market: paragraph 1 requires it to verify that one has been appointed.

No placing on the market when in doubt. Where the importer has sufficient reason to consider that the system is not in conformity with the Regulation, is falsified or is accompanied by falsified documentation, it does not place it on the market until it has been brought into conformity (paragraph 2). Where the system presents a risk within the meaning of Article 79(1), that is a risk to the health or safety or to the fundamental rights of persons, it informs the provider, the authorised representative and the market surveillance authorities.

Own name and address. The importer indicates its name, registered trade name or registered trademark, and the address at which it can be contacted, on the high-risk AI system and on its packaging or its accompanying documentation, where applicable (paragraph 3). The Dutch text mentions only the packaging and the documentation, not the system itself. For a web application, it is in our reading sensible to put these details in the instructions for use and on the system's information screen, next to the provider's details (which the provider gives under Article 16, point (b)).

Storage and transport. While the system is under its responsibility, the importer ensures that storage or transport conditions, where applicable, do not jeopardise compliance with the requirements of Section 2 (paragraph 4). For hardware with embedded AI, this is meant literally. For software it concerns, in our reading, the way the importer keeps and passes on the software: it supplies the assessed version, without changes of its own along the way.

Keep for ten years. The importer keeps, for ten years after the system has been placed on the market or put into service, a copy of the certificate issued by the notified body, where applicable, of the instructions for use and of the EU declaration of conformity (paragraph 5). The Dutch text attaches "where applicable" (in voorkomend geval) to the instructions for use and the declaration instead; the English text, which attaches it to the certificate, fits practice, because under internal control there is no certificate. That term lies with the importer itself. If the supplier no longer exists in five years, the importer must still be able to produce the documents.

Information for the authorities. Upon a reasoned request, the importer gives the competent authorities all information and documentation necessary to demonstrate conformity with Section 2, including the documents of paragraph 5, in a language they can easily understand. It also ensures that the technical documentation can be made available to those authorities (paragraph 6). In our reading this means the importer need not hold the technical documentation itself, but must have arranged with the provider that it becomes available on request.

Cooperation. The importer cooperates with the competent authorities in any action they take in relation to the system it placed on the market, in particular to reduce and mitigate its risks (paragraph 7).

Article 24: what the distributor must do

Check before making available. Before making the system available on the market, the distributor verifies that it bears the CE marking, that it is accompanied by a copy of the EU declaration of conformity and instructions for use, and that the provider and the importer have complied with their obligations under Article 16, points (b) and (c), and Article 23(3) (paragraph 1). Article 16, point (b), concerns the provider's name and address, point (c) the quality management system of Article 17. Article 23(3) is the importer's name and address. The Regulation does not say how a distributor checks the provider's quality management. In our reading, a written confirmation from the provider, referring to its quality management system, is the minimum the distributor should have on file.

The distributor's check is lighter than the importer's. It does not verify whether the conformity assessment was carried out or whether the technical documentation exists; the importer, or for a European provider the provider itself, has done that. The distributor looks at what visibly comes with the system.

No supply when in doubt. Where the distributor considers or has reason to consider, on the basis of the information in its possession, that the system is not in conformity with the requirements of Section 2, it does not make it available on the market until it has been brought into conformity (paragraph 2; the Dutch text speaks here of placing on the market, the English text of making available on the market). Where it presents a risk within the meaning of Article 79(1), it informs the provider or the importer. The criterion "on the basis of the information in its possession" is in our reading a deliberate limit: the distributor need not investigate on its own, but may not look away from what it knows, for example from customer complaints.

Storage and transport. Like the importer, the distributor ensures that storage or transport conditions do not jeopardise compliance while the system is under its responsibility (paragraph 3).

Corrective action after supply. Where the distributor considers or has reason to consider, on the basis of the information in its possession, that a system it has already made available is not in conformity with the requirements of Section 2, it takes the corrective actions necessary to bring it into conformity, to withdraw it or to recall it, or ensures that the provider, the importer or any relevant operator does so (paragraph 4). Where it presents a risk within the meaning of Article 79(1), it immediately informs the provider or importer and the competent authorities, giving details of the non-compliance and of any corrective action taken. A software reseller will usually not be able to bring the system into conformity itself. In our reading its route is then: have the provider correct it, and if necessary stop supplying new customers.

Information and cooperation. Upon a reasoned request, the distributor gives the competent authority all information and documentation on the actions it took under paragraphs 1 to 4 (paragraph 5), and it cooperates with the authorities (paragraph 6). Article 24 sets no retention period. In our reading a distributor can only comply with paragraph 5 if it records which checks it carried out and what it did.

The other direction of the chain. Where the provider itself takes corrective action, it informs the distributors and, where applicable, the deployers, the authorised representative and importers (Article 20(1)). And a deployer that identifies a serious incident informs first the provider, and then the importer or distributor and the market surveillance authority (Article 26(5)). Importers and distributors are therefore also a relay. How reporting a serious incident works is covered in reporting a serious incident under Article 73.

Importer and distributor side by side

Importer (Article 23)Distributor (Article 24)
WhenBefore placing on the market (first supply in the EU)Before every making available
CheckConformity assessment, technical documentation, CE marking with declaration and instructions for use, authorised representative (paragraph 1)CE marking, declaration, instructions for use, name and address of provider and importer, provider's quality management (paragraph 1)
When in doubtNo placing on the market with sufficient reason, also where falsified (paragraph 2)No making available on the basis of the information in its possession (paragraph 2)
Informing on a riskProvider, authorised representative and market surveillance authorities (paragraph 2)Provider or importer (paragraph 2); after supply also the competent authorities, immediately (paragraph 4)
Own nameName and contact address added (paragraph 3)No own indication
RetentionTen years: certificate, instructions for use, declaration (paragraph 5)No period stated
AuthoritiesInformation on request, technical documentation available, cooperation (paragraphs 6 and 7)Information on its own actions on request, cooperation (paragraphs 5 and 6)

Article 25(1): when you become the provider yourself

An importer or distributor stays one as long as it passes on someone else's system. In three situations, a distributor, importer, deployer or other third party becomes the provider of a high-risk AI system, with all the obligations of Article 16 (Article 25(1)):

  • Own name or trademark (point (a)). It puts its name or trademark on a high-risk system already placed on the market or put into service, without prejudice to contractual arrangements that allocate the obligations otherwise. A reseller that sells the American welfare system to municipalities under its own product name is a provider under that provision, without prejudice to such a contractual arrangement. How far such an arrangement reaches as against the supervisory authority, the Regulation does not say. In our reading, do not rely on it without an express agreement with the original provider.
  • Substantial modification (point (b)). It makes a substantial modification to a high-risk system in such a way that it remains high-risk. A substantial modification is a change after placing on the market that the provider did not foresee in the initial conformity assessment and that affects compliance with Section 2, or changes the assessed intended purpose (Article 3, point 23).
  • Changed purpose (point (c)). It modifies the intended purpose of an AI system that was not high-risk, including a general-purpose AI system, so that it becomes high-risk. This concerns precisely systems that were not high-risk to begin with.

When that happens, the initial provider is no longer the provider of that specific system. It does cooperate closely with the new provider and makes the necessary information, technical access and other assistance available (Article 25(2)). Since the Omnibus, paragraph 2 sets out what that includes in particular, where relevant: technical documentation sufficient to assess compliance with Article 16, information on known limitations and failure modes, and targeted technical access, including for testing and validation. Paragraph 2 does not apply where the initial provider has clearly specified that its system is not to be changed into a high-risk system; it then does not fall under the obligation to cooperate and hand over the documentation. More on the three routes in when do you become a provider under Article 25.

For a reseller or integrator this is the most important question in the whole piece. An importer checks four points and keeps documents. A provider carries out the conformity assessment, draws up the technical documentation and the declaration, affixes the CE marking, runs a quality management system and registers the system. Your own logo on the product can mean that step.

What the Digital Omnibus changed

Regulation (EU) 2026/1744, the Digital Omnibus on AI, lists in Article 1 the provisions of the AI Act it amends. Articles 23 and 24 are not among them, and neither is Article 25(1). The definitions of importer and distributor in Article 3, points 6 and 7, stayed the same; in Article 3 the Omnibus only amended point 14 and inserted points 14a and 14b (Article 1, point (4)).

That the text stayed the same does not mean nothing can change. The Omnibus added a new paragraph 13 to Article 2 (Article 1, point (3)). For high-risk AI systems referred to in Article 6(1), the Annex I systems, the application of specific requirements or obligations in Articles 9 to 15 and 17 to 25 may be limited, where the Union harmonisation legislation in Section A of Annex I lays down requirements or obligations with an equivalent or higher level of protection and the limitation does not reduce the overall level of protection of the Regulation. By 2 August 2027 the Commission adopts delegated acts specifying the systems, requirements and obligations concerned, the conditions and the scope of the limitation. Anyone importing or distributing Annex I systems should therefore watch those acts. For Annex III systems, Article 2(13) changes nothing.

Amended, and relevant to the chain:

  • Article 25(2) was replaced, with the list of what the initial provider's cooperation includes in particular (Article 1, point (12)(a)).
  • The first subparagraph of Article 25(4) was replaced. The written agreement between the provider and the third party that supplies something used or integrated in the high-risk system was already in the original text. What is new is that a third party supplying an AI model is now expressly covered, alongside an AI system, tools, services, components or processes (Article 1, point (12)(b)).
  • In Article 99(4), point (da) was inserted, so the obligations of Article 25(2) and (4) also fall under the fine of paragraph 4 (Article 1, point (38)(b)).
  • The application dates of Chapter III, Sections 1 to 3, are in the replaced point (c) of the third paragraph of Article 113 (Article 1, point (40)(b)).
  • Article 2(2) was replaced (Article 1, point (2)(a)). As in the original text, only the provisions listed in that paragraph apply to Annex I systems related to products under Section B; Articles 23 and 24 are not among them. See "From when?" below.

Main example: the municipality, the reseller and the supplier outside the EU

Back to the municipality. The system helps caseworkers assess whether someone is entitled to social assistance. That falls under Annex III, point 5(a): AI systems intended to be used by or on behalf of public authorities to evaluate the eligibility of natural persons for essential public assistance benefits and services. The roles are, in our reading:

  • The American company is the provider. It developed the system and places it on the market under its own name. Because it is established outside the EU, it appoints an authorised representative in the EU before making its system available on the Union market (Article 22(1); the Dutch text speaks of placing on the market in the Union).
  • The Dutch reseller is the importer, if it is the first to supply the system in the EU. It carries out the four checks of Article 23(1), adds its name and address and keeps the documents for ten years.
  • Variant: a European sales subsidiary. If the American company first supplies its own sales subsidiary in Ireland, a separate legal person, which then sells to the Dutch reseller, the Irish subsidiary is in our reading the importer (the system carries the name of the American parent) and the Dutch reseller is a distributor. A branch without legal personality of its own is not a separate party; the importer is a natural or legal person (Article 3, point 6).
  • Variant: own product name. If the reseller sells the system under its own name, it is the provider under Article 25(1)(a), without prejudice to contractual arrangements that allocate the obligations otherwise. How far such an arrangement reaches as against the supervisory authority, the Regulation does not say; in our reading, do not rely on it without an express agreement with the original provider.
  • The municipality is the deployer.

The Regulation does not require the municipality to repeat the importer's checks. It does have its own obligations, and several of them touch the chain. It uses the system in accordance with the instructions for use and assigns human oversight (Article 26(1) and (2)). If it has reason to consider that the system presents a risk, it informs the provider or distributor and the market surveillance authority without undue delay, and suspends use. On a serious incident, it informs first the provider, then the importer or distributor and the market surveillance authority (Article 26(5)). As a public authority, it does not use the system if it is not registered in the EU database, and informs the provider or distributor (Article 26(8)). It registers its own use (Article 49(3)); see registering AI systems. And because it is a body governed by public law using an Annex III system, it carries out a fundamental rights impact assessment before putting the system into use (Article 27).

What the municipality, in our reading, puts in the contract with the reseller:

  1. The roles by name. Who is the provider, who is the authorised representative, who is the importer, who is the distributor, with contact addresses. Then the municipality knows whom to inform on a risk or incident.
  2. The documents on delivery. The EU declaration of conformity for the version supplied, the instructions for use, the CE marking in the interface and evidence of registration in the EU database.
  3. A statement that the checks of Article 23(1) were carried out, with the authorised representative's details.
  4. Passing on corrective actions. The reseller immediately passes on every notice from the provider under Article 20, and reports every decision to withdraw or recall the system.
  5. A channel for incidents. Whom the municipality reaches if it cannot reach the provider, and within what time.
  6. No changes or own name without notice. If the reseller modifies the system or puts its name on it, the provider role shifts (Article 25(1)). The municipality wants to know.
  7. New versions. A substantial modification means a new conformity assessment (Article 43(4)) and then a new declaration (Article 16, point (g), and Article 47), which the municipality receives.
  8. After the contract ends. The importer keeps the documents for ten years. Agree that the municipality can still request them afterwards for its own file.

More on the procurement side in AI procurement contracts and assessing an AI vendor. For this kind of system specifically: welfare fraud risk scoring.

Example 2: the bank and the integrator

A bank wants to use a credit scoring model from a provider outside the EU to evaluate the creditworthiness of individuals. That is Annex III, point 5(b), with an exception for systems used to detect financial fraud. The bank does not buy directly: a European integrator connects the model to the bank's loan acceptance system and delivers the whole. This example is also fictitious.

Which role the integrator has depends, in our reading, on what it does. If it supplies the model unchanged and under the provider's name, and is the first to supply it in the EU, it is the importer and carries out the checks of Article 23. If it puts the model in its own product under its own name, it is the provider (Article 25(1)(a)). If it retrains the model on the bank's data in a way the provider did not foresee in the initial assessment and that affects accuracy or robustness, that can be a substantial modification, and it is also the provider (Article 25(1)(b), Article 3, point 23). The same applies to the bank if it does this itself.

The bank itself is the deployer. It carries out a fundamental rights impact assessment before putting the system into use (Article 27(1), Annex III, point 5(b)). For financial institutions subject to internal governance requirements under financial services law, the monitoring obligation of Article 26(5) is deemed fulfilled by complying with those rules. In our reading that rule only concerns monitoring: the notifications to the provider, the importer or distributor and the authority on a risk or a serious incident still apply. How the model relates to banking law is covered in AI in credit decisions.

For the bank, the practical question is the same as for the municipality: does it know who the provider is? With an integrator that delivers the whole under its own name, the integrator is the party that signs the declaration, not the original model builder. That should be clear from the contract and the declaration.

In brief: education and HR

Education. A school board buys, through a Dutch distributor, a platform from a provider outside the EU that evaluates learning outcomes (Annex III, point 3(b)). If there is a European importer between the provider and the Dutch distributor, the distributor has all the obligations of Article 24, starting with the check of paragraph 1, but not those of Article 23. The school board finds out who the importer is, and requests the declaration and the instructions for use. If the distributor adds its own module that changes the evaluation, that can be a substantial modification.

HR. An employer buys recruitment software that filters applications and ranks candidates (Annex III, point 4(a)) from a provider outside the EU, through a Belgian reseller. If that reseller is the first to supply it in the EU, it is the importer. If it offers the software under its own brand, it is the provider. The employer, as deployer, informs workers' representatives and the affected workers before putting the system into service or using it at the workplace (Article 26(7)).

From when?

Articles 23, 24 and 25 are in Section 3 of Chapter III. That Section applies from 2 December 2027 for AI systems classified as high-risk under Article 6(2) and Annex III, and from 2 August 2028 for AI systems classified as high-risk under Article 6(1) and Annex I (Article 113, third paragraph, point (c), as replaced by Article 1, point (40), of Regulation (EU) 2026/1744). That is what the text says; it is not a reading.

The date of 2 August 2028 applies to Annex I systems related to products under Section A of Annex I. For high-risk AI systems related to products covered by the Union harmonisation legislation in Section B of Annex I, only Article 6(1), Article 60a and Articles 102 to 112 apply, and Articles 57, 58 and 59 only in so far as the AI Act requirements have been integrated in that harmonisation legislation (Article 2(2), as replaced by Article 1, point (2), of Regulation (EU) 2026/1744). Articles 23 and 24 therefore do not apply to those systems.

Articles 47 and 48 work differently. They sit in Section 5 of Chapter III, and that section appears in none of the exceptions in Article 113, third paragraph. It thereby falls under the general date of application (Article 113, second paragraph): formally, 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. More in the EU declaration of conformity and CE marking.

Where a system was placed on the market or put into service before that date, the Regulation applies to the operators of that system only if it subsequently undergoes significant changes in its design. Providers and deployers of systems intended to be used by public authorities must comply by 2 August 2030 at the latest (Article 111(2), as amended by Article 1, point (39), of Regulation (EU) 2026/1744). 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 are also covered by the transitional rule, as long as the design remains unchanged. Article 111(2) does not separately mention importers and distributors in the 2 August 2030 sentence. The first sentence of paragraph 2 does speak of "operators", and operators include importers and distributors (Article 3, point 8). Recital 39 also says that other units of the same type and model may continue to be "made available" on the Union market. In our reading importers and distributors therefore follow the system: if it falls under the transitional rule, so do their obligations for that system.

Fines

Non-compliance with the obligations of importers under Article 23 and of distributors under Article 24 is subject to administrative fines of up to 15 million euros or, for an undertaking, up to 3 percent of total worldwide annual turnover for the preceding financial year, whichever is higher (Article 99(4), points (c) and (d)). An importer or distributor that becomes a provider under Article 25(1) falls under paragraph 4, point (a), for the obligations of Article 16. Since the Omnibus, the obligations of Article 25(2) and (4) fall under paragraph 4, point (da). Supplying incorrect, incomplete or misleading information to the authorities in reply to a request risks a fine of up to 7.5 million euros or 1 percent (paragraph 5).

For SMEs and start-ups, the lower of the amount and the percentage applies (paragraph 6), and since the Omnibus also for small mid-cap enterprises for the fines of paragraphs 4 and 5 (paragraph 6a). Many software resellers are SMEs. The Netherlands has not yet designated a market surveillance authority for the AI Act. According to the planning letter of 31 August 2026, the State Secretary intends to submit the AI Act Implementation Act bill, which is to designate the supervisors, to the House of Representatives in the second quarter of 2027 (Parliamentary Paper 26643, no. 1554, in Dutch). See also AI Act and GDPR fines for municipalities.

What to do now

  1. Determine your role per system. Are you the first in the EU to place on the market a system bearing the name of a party outside the EU? Then you are the importer. Do you supply it onwards after that? Then you are a distributor. Do you only use it? Then you are a deployer.
  2. Check whether you become the provider. Own name or trademark, substantial modification or changed purpose: then the obligations of Article 16 apply (Article 25(1)).
  3. Make a checklist. Importer: the four points of Article 23(1). Distributor: the points of Article 24(1). Record when and with which documents you checked.
  4. Add your name. As importer in the instructions for use, the documentation and, for software, the information screen.
  5. Arrange retention. As importer for ten years, also if the relationship with the provider ends. As distributor, a file of your checks and actions.
  6. Arrange the reporting route. Who informs whom on a risk, a corrective action or a serious incident, in both directions of the chain.
  7. Are you a deployer? Have the roles, the documents and the reporting route set out in the contract.

Not sure whether your system is high-risk and which role you have? With the case check you describe the use in a few questions and see which AI Act and GDPR obligations come into view.

Frequently asked questions about importers and distributors under the AI Act

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

What does a harmonised standard prove? Articles 40, 41 and 42 of the AI Act on standards, common specifications and the presumption of conformity

A supplier who says it follows the European standard is saying less than it seems. Article 40 of the AI Act gives a presumption of conformity only for a harmonised standard whose reference is published in the Official Journal, and only for the requirements the standard covers. Article 41 lets the Commission adopt common specifications when standards fail to arrive. Article 42 adds three narrow presumptions: data from the setting of use, a cybersecurity certificate under Regulation (EU) 2019/881 and, since the Digital Omnibus, the Cyber Resilience Act. With what had been published by 19 November 2026, what you do without a standard, a Dutch municipality procuring a system for social assistance applications and a bank as examples.

EU AI ActArticle 40Article 41

Can the list of high-risk AI still change? Articles 7 and 8 of the AI Act on amending Annex III and complying with the requirements

Annex III of the AI Act is not a fixed list. Article 7 lets the Commission add, modify and remove use cases by delegated act, within the eight areas and against eleven criteria. Article 8 says what complying with the requirements means: taking into account the intended purpose and the state of the art, and for products under Section A of Annex I, the option to integrate testing and documentation processes. With the Commission's first annual report on Annex III, what the Digital Omnibus on AI did and did not change, a Dutch municipality with a system that currently falls outside Annex III and an insurer as examples.

EU AI ActArticle 7Article 8

When a high-risk AI system does not comply: corrective actions, documentation keeping and cooperation under Articles 18, 20 and 21 of the AI Act

What must a provider do when its high-risk AI system does not (or no longer) comply with the AI Act, and how long does it keep the documentation? Article 18 (ten years of documentation keeping), Article 20 (corrective actions and the duty to inform the supply chain and the supervisor) and Article 21 (cooperation with the authorities, access to logs, confidentiality). With what the Digital Omnibus did and did not change, when it applies and which fines apply, and with a municipality that receives a notice from its supplier and a bank with its own credit model as examples.

EU AI ActArticle 18Article 20