Regulation (EU) 2024/1689 · Artificial Intelligence Act ● Annex III: — days

Who Needs an Authorised Representative Under the EU AI Act?

Non-EU providers of high-risk AI often need an EU authorised representative. This guide covers Article 22 scope, mandate contents, contracts and importer overlap.

Renomira Team · 6 min read
Contract signing between business partners representing an AI provider appointment
Photo: European Space Agency / CC BY-SA 3.0 igo via Wikimedia Commons

If you provide AI systems into the EU from outside, the question who needs an authorised representative for ai decides whether your first shipment is lawful. Article 22 of the AI Act requires certain non-EU providers to appoint an established EU body to act on their behalf before placing high-risk systems on the market — an authorised representative eu ai act appointment with real obligations, not a mailbox. This guide sets out the scope, what the mandate must contain, how it interacts with importer duties, and the honest answer on authorised representative for general purpose ai — where the rules differ from high-risk systems.

Who must appoint under Article 22

The duty bites on providers of high-risk AI systems (and providers of general-purpose AI models, by parallel provision) that are established in third countries. The pattern is the same as other EU product legislation: if you want the EU market, you need someone inside it who can answer for your file.

In scope:

  • A non-EU provider placing an Annex III high-risk AI system on the EU market under its own name.
  • A non-EU provider placing an Annex I-style system on the market where the product legislation’s own rules require a responsible person and the AI Act routes it through Article 22.
  • A non-EU provider of a general-purpose AI model — Chapter V duties include appointing an authorised representative before placing the model on the market, with a written mandate covering the information obligations of Article 53/54.

Out of scope:

  • Providers established in the EU (obviously), and any provider whose system is not high-risk and not a GPAI model.
  • Open-source high-risk providers benefit from the documentation-relief provisions but not from exemption on Article 22 where the system is placed on the market commercially — do not treat “open weights” as an out.
  • Deployers: using an AI system does not require a representative, however EU-established you are — the deployer duties in Article 26 are yours to perform directly.

The frequently missed point: the appointment must be in place before the system or model is placed on the market. A representative nominated in the middle of a contract negotiation has already been late.

What the mandate must cover

Article 22(4) and (5) specify the instrument — a written mandate, laid down in a contractual arrangement — and the tasks. The representative acts in the interests of its principal and must be able to demonstrate its mandate on request:

  • Registration cooperation — completing the EU database registration for high-risk systems (Article 49) in collaboration with the provider.
  • Documentation retention — holding the technical documentation and declaration of conformity, and producing them to authorities on request for the required retention period.
  • Authority cooperation — responding to market surveillance requests, providing information, and taking corrective action when a system is found non-compliant.
  • Importer interface — a single point of contact established in the EU, which is the entire point of the institution.

Article 22(6) does the crucial work for your org chart: the authorised representative does not assume the provider’s obligations — the provider remains fully responsible for conformity. What it does do is make those obligations reachable from within the Union, which is exactly why authorities treat a silent representative as no representative at all.

How it differs from an importer or distributor

Three roles get confused constantly, and the difference is about who places the product on the market under whose name:

Role Established where Acts for Trigger Key source
Authorised representative EU Non-EU provider Article 22 mandate Written mandate, contractual
Importer EU Itself — releases under own name/channel First placement in the EU Article 23 duties
Distributor EU Makes available in the supply chain Availability, not placement Article 3(8), Article 24 duties

An importer takes title or releases the product into the EU market under its own commercial identity and owes verification duties — checking the provider has done the conformity work, the declaration exists, the mark is affixed, labelling is in the required language. A representative never becomes a party to the product in that sense. One firm can be both — but sign two capacities, not one blurred document, or you inherit duties you priced as a warehouse.

Appointing authorised representative ai systems: the contract checklist

A mandate that fails at the first authority request is worse than none. Require at minimum:

  1. Scope statement — the exact systems and regulations covered; generic “all EU legislation” wording invites gaps.
  2. Tasks and timelines — response deadlines for authority requests, defined in working days, with escalation contacts.
  3. Documentation custody — what the representative holds (technical file, declaration, DoC copy), formats, version control and update duties when the provider revises the system.
  4. Liability allocation — indemnities for the representative’s own failures, and clarity that provider liability under the Regulation is untouched.
  5. Termination and transition — notice periods that never strand an on-market system with no EU anchor; handover duties to a successor.
  6. Right to audit — your own right to inspect the representative’s readiness, because their silence becomes your non-compliance.
  7. Data protection contacts — the representative details that also need to appear in declarations and documentation.

Commercially, expect fees to scale with documentation volume and authority-contact risk: a compliance consultancy or law firm is typical; a virtual office is not a strategy.

The general purpose AI model question

The ai act authorised representative obligations for GPAI providers deserve their own paragraph because the regime is newer and the obligations are information-shaped rather than conformity-shaped. A non-EU GPAI provider must appoint an authorised representative established in the Union before placing the model on the market (Article 54). The written mandate obliges the representative to retain the information the provider must supply — the technical documentation provided to the AI Office, the public summary of training content, the copyright policy — and to hand it to the AI Office or national authorities on reasoned request.

Two practical notes. First, the exemption structure is narrower than the high-risk one: only providers of free, open-licence GPAI models without systemic risk can avoid parts of the Chapter V information duties — and even they must keep the information and designate a contact point. Second, if your EU subsidiary merely uses a non-EU group company’s model, the subsidiary is a deployer, not the natural representative. Appointing an affiliate that lacks independence and documentation custody creates the appearance of compliance; authorities ask for the mandate and the file, and an unprepared affiliate fails both.

Where firms actually trip

The failure pattern across mid-market providers is consistent:

  • Late appointment. The representative is negotiated alongside the first enterprise contract — after first placement. Every day in between is non-compliance with a rule that conditions market access.
  • Nominal mandates. A signed letter naming a contact and nothing else, with no documentation custody, no response timelines, no registration cooperation. Article 22(4) requires a written mandate covering specified tasks; a business card does not cover them.
  • Assumed transfer of responsibility. Boards hear “we have an EU representative” and conclude the EU problem is solved. Under Article 22(6) the provider keeps full responsibility; the representative makes it enforceable, not absent.
  • Importer/representative confusion. A distributor signs as “representative” in a supply agreement without the mandate structure, then cannot produce technical documentation when asked — because nobody told the provider what the distributor needed to hold.
  • Silence after appointment. Mandates rot: systems are revised, the technical file moves, the representative still holds 2024’s version. Build a version-update obligation into the contract and test it annually.

How to check your own position

If you are a non-EU provider, list every AI system and model you make available in the EU, classify each (high-risk, GPAI, neither), and check your register for a representative entry against each in-scope item with an appointment date earlier than first placement. Open the mandate document and verify the seven checklist items above are present as clauses, not aspirations — then ask your representative one blunt question: “Send me the technical documentation you hold for our current version.” If the answer takes days, your authority-response timeline is fiction. EU firms flip the test: ask which of your non-EU vendors have appointed representatives, and make the declaration number plus representative details a condition of renewal. A procurement team that runs this check quarterly never meets Article 22 in a crisis.

Frequently asked questions

Do all non-EU AI companies need an authorised representative in the EU?

No — only those placing high-risk AI systems or general-purpose AI models on the EU market fall under Article 22. Providers of non-high-risk AI tools into the EU do not need one under the AI Act, though other regimes (product legislation, the Data Act’s representative provisions) may still apply. Deployers never need one for AI Act purposes.

What is the difference between an authorised representative and an importer?

An authorised representative acts for a non-EU provider under a written mandate, holds documentation and answers authorities, and never takes a commercial position in the product. An importer is an EU business placing the product on the market under its own name and owes verification duties — checking conformity work, marking and labelling before release. One acts for you; the other buys and resells.

When must an authorised representative be appointed under the AI Act?

Before placing the system or model on the market. Article 22 makes appointment a precondition of lawful placement, so the mandate must be signed and operative ahead of the first commercial availability in the EU — not when a regulator first writes, and not when an enterprise customer asks.

Does a GPAI provider need an authorised representative?

Yes, if established outside the EU. Article 54 requires non-EU GPAI providers to appoint an EU authorised representative before placing the model on the market, with a mandate covering retention and supply of the Chapter V information — technical documentation, training-data summary and copyright policy — to authorities on request.

Can an authorised representative take over our compliance obligations?

No. Article 22(6) preserves the provider’s full responsibility for conformity; the representative performs specified tasks — registration support, documentation custody, authority contact — but does not inherit liability for the system’s compliance. Think of the mandate as giving your obligations an EU address, not moving them to a new owner.

Next step

Put this guide to work on your own estate.

Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.

  • Free forever plan
  • No credit card
  • EU-hosted · GDPR-native
Run a free scan Sign up free

Build a live AI register in minutes — upgrade only when you need the audit pack.

authorised representative eu ai actarticle 22 authorised representative ai actwho needs an eu representative for ainon eu provider authorised representative aiai act authorised representative obligationsappointing authorised representative ai systemsai act importers and authorised representativesauthorised representative for general purpose ai

Keep reading