EU AI Act Article 49: Registration in the EU Database, Implemented in Practice
EU AI Act Article 49 requires a high-risk system to be entered in the EU database under Article 71 before it goes live, with the information listed in Annex VIII. The EU database is the public number plate, our internal registry the vehicle file behind it: the public entry is generated from the registry record, exported at release and checked on every version.
For years I have used the image of the registration office: no car drives without a number plate, no model goes into production without a registry record. Article 49 of the AI Regulation is where the legislator turns the same image into law: a public EU database in which high-risk systems are listed before they run. It is addressed to providers and authorised representatives (paragraphs 1 and 2) and to deployers in the public sector (paragraph 3); through Art. 16(i) and Art. 26(8) the duty is tied to the general obligations of both roles. The database is governed by Article 71, the fields by Annex VIII.
The EU AI Act has been in force since 1 August 2024. Prohibitions and AI literacy have applied since February 2025, the obligations for GPAI models since August 2025, the transparency obligations under Article 50 since August 2026. After the postponement by the amending Regulation (EU) 2026/1744 (Digital Omnibus), the obligations for high-risk systems under Annex III apply from 2 December 2027, for Annex I products from 2 August 2028. Article 49 is one of those high-risk obligations. The Omnibus moved deadlines; it removed no obligation. The overview is in EU AI Act in practice.
What Article 49 requires
Art. 49(1): The provider of a high-risk system under Annex III, or its authorised representative, registers itself and the system in the EU database under Art. 71 before placing it on the market or putting it into service. Systems under Annex III point 2 (critical infrastructure) are excepted. The information is listed in Annex VIII Section A.
Art. 49(2): A provider that concludes under Art. 6(3) that its Annex III system is not high-risk still registers itself and the system, before placing it on the market or putting it into service. The information is listed in Section B, including the Art. 6(3) condition relied on.
Art. 49(3): Deployers that are public authorities, Union institutions, bodies, offices or agencies, or persons acting on their behalf, register themselves, select the system in the database and register its use before putting it into service or using it. Again without Annex III point 2. The information is listed in Section C.
Art. 49(4): Systems under Annex III points 1, 6 and 7 (law enforcement, migration, asylum, border control) are registered in a secure, non-public section of the database with reduced information. Only the Commission and the national authorities under Art. 74(8) have access.
Art. 49(5): Systems under Annex III point 2 are registered at national level.
Art. 71: The Commission sets up the database with the Member States (paragraph 1). Providers enter Sections A and B (paragraph 2), public-sector deployers Section C (paragraph 3). What is registered under Art. 49 is public and machine-readable, except for the section under Art. 49(4) and the real-world testing under Art. 60 (paragraph 4). It contains personal data only as far as necessary, including the names and contact details of the authorised persons who register (paragraph 5). The Commission is the controller (paragraph 6).
Annex VIII: Section A asks the provider for thirteen items: identity, submitting person, authorised representative, trade name and unambiguous reference, intended purpose, a basic and concise description of data and operating logic, status, notified body certificate, Member States, declaration of conformity under Art. 47, electronic instructions for use, optionally a URL. Section B repeats identity, reference, purpose and status and asks for the Art. 6(3) condition. Section C asks the deployer for identity, submitting person, the URL of the provider’s entry and summaries of the fundamental rights impact assessment under Art. 27 and the data protection impact assessment (DPIA). For all three: the information is thereafter to be kept up to date.
The technical example
A bank builds a credit pre-check model itself. It assesses the creditworthiness of retail customers, so Annex III point 5(b), and the bank is the provider under Art. 3(3) because it develops the system and puts it into service under its own name. The data flow: the application comes from the loan portal to the policy gateway, which pseudonymises, checks scope and data zone and calls the model. Back come a score band, a confidence and the supporting features; the gateway writes the evidence, the advisor decides. Art. 49(1) bites before the first real application: the Section A entry has to exist.
The same bank runs a document classifier in the credit process that sorts incoming documents by type: payslip, ID, bank statement. It operates in the area of Annex III point 5 but performs a narrow procedural task under Art. 6(3)(a), documented under Art. 6(4). That exempts it from Chapter III Section 2, not from registration: Art. 49(2) requires the Section B entry, with exactly that condition.
Third, a public authority that uses a purchased system to pre-sort applications for social benefits, Annex III point 5(a). It is a deployer and a public body, so Art. 49(3) applies: its own Section C entry, with the URL of the provider’s entry and the summaries of its fundamental rights impact assessment under Art. 27 and the DPIA. If the provider’s entry is missing, it cannot supply a URL, and under Art. 26(8) it may not use the system.
How we implement it
At SIFAMO we built the registration office before the EU database existed: the registry in the governance layer, no record, no route. Article 49 adds a public layer on top. The EU database is the number plate anyone can see: who the keeper is, which vehicle, whether it is registered. Our registry is the vehicle file behind it, with evaluation, scope, oversight, expiry and kill switch. The plate points to the file, the file feeds the plate.
Field by field against Annex VIII. Every registry record has an export view that produces the Annex VIII dataset. For the credit pre-check under Section A: item 4 is the model ID from the registry, our number plate, plus the trade name; the ID stays stable across versions, the version lives in the file. Item 5, the intended purpose, is a single field that also feeds the instructions for use under Art. 13 and the technical documentation under Annex IV, so that three documents never state three purposes. Item 6 is generated from data lineage and model card: data categories and decision logic, no feature weights, no thresholds. Item 7 follows the lifecycle state; the kill switch does not change it, decommissioning does. Items 8 and 9 do not apply to credit scoring under internal control per Annex VI, and the field says so with reasons. Item 11 is the declaration of conformity from the release gate, item 12 the versioned instructions for use.
Sections B and C. For the document classifier the Art. 6(3) condition is not free text but the field from the classification page in the first gate. The full assessment stays in the file and goes to the authority on request under Art. 6(4); the consolidated version of Annex VIII no longer asks for the summary of grounds to be public. For the public authority, the registry record of the purchased system has a mandatory field for the URL of the provider’s entry; no URL, no route.
Export at release, check on every version. The release gate with its three signatures has one additional item: Annex VIII export generated and submitted. Only when the identifier of the public entry is in the registry record does the gateway give the system a route. On every new version the export recomputes the dataset and compares it with the submitted state. If a public field has changed, the update is submitted before release. Otherwise the registry stores the hash and timestamp of the comparison. That way “kept up to date” is not an intention but a diff.
Who keeps the entry current. The business owner who signs the registry record is also the keeper of the public entry. The submitting person comes from compliance and holds the authority to represent that Art. 71(5) presupposes. Status changes such as withdrawal or recall have a deadline, and the expiry date of the registry record also triggers a review of the public entry.
Public and internal. Everything in Sections A, B and C is public and machine-readable under Art. 71(4). Competitors and journalists will read the purpose text, so we write it that way. Non-public are only the section under Art. 49(4) and the tests under Art. 60. What Annex VIII does not name stays in the file: evaluation, scope, oversight, bias checks, kill switch, expiry. The auditor sees the public entry with a timestamp before putting into service, the file behind it and per version the diff. I am an engineer, not a lawyer. But the registration office I wished for years ago now exists, and it only works if the file behind it is right.
Typical mistakes
“Not high-risk, so nothing to do.” The exception under Art. 6(3) exempts from the requirements, not from Art. 49(2). The system is still in the database.
Registration as a one-off project. Model swapped, purpose widened, and the public entry describes day one. Annex VIII demands maintenance, not submission.
Authority without a provider entry. The public body goes live because the provider promised to register. Art. 26(8) prohibits use as long as the entry is missing.
EU AI Act Article 49 checklist
For every Annex III system, which paragraph applies is settled: (1) as provider, (2) under Art. 6(3), (3) as a public body, (4) or (5) as a special case.
Registry record with an export view that produces the Annex VIII dataset field by field; items that do not apply are justified.
One source field for the intended purpose that feeds instructions for use, technical documentation and database entry.
Release gate includes export and submission; the identifier of the public entry is a precondition for the route.
On every version a diff against the submitted state; update before release, otherwise hash and timestamp.
Keeper of the entry and authorised submitting person named; deadline for status changes defined.
Open questions
Which interface the database offers for submission and updates is not set by the Regulation; Art. 71(1) refers to functional specifications by the Commission.
When an entry is no longer up to date is open. That a new model version with an unchanged purpose requires no update is my reading, not a settled one.
How detailed the operating logic under Section A item 6 has to be described, and how that relates to the protection of trade secrets under Art. 78, has not been specified so far.
Frequently asked questions
Does this apply to us as a deployer?
Only if you are a public authority, Union institution, body, office or agency, or act on their behalf; then Art. 49(3) applies. A private company that buys a high-risk system registers nothing itself but checks the provider’s entry under paragraph 1 before go-live. You still need the internal registry, see AI Governance.
Do we have to register a system we classified as not high-risk ourselves?
Yes, if it falls into an area of Annex III and you rely on Art. 6(3). Art. 49(2) requires the entry under Annex VIII Section B, including the condition you invoke.
What in our entry is public?
Under Art. 71(4), everything registered under Art. 49: identity, reference, purpose, logic description, status, declaration of conformity, instructions for use. Non-public are the section under Art. 49(4) and information on tests under Art. 60. The other articles in the series: all articles at a glance.
EU AI Act Article 49: Registration in the EU Database, Implemented in Practice
EU AI Act Article 49 requires a high-risk system to be entered in the EU database under Article 71 before it goes live, with the information listed in Annex VIII. The EU database is the public number plate, our internal registry the vehicle file behind it: the public entry is generated from the registry record, exported at release and checked on every version.
For years I have used the image of the registration office: no car drives without a number plate, no model goes into production without a registry record. Article 49 of the AI Regulation is where the legislator turns the same image into law: a public EU database in which high-risk systems are listed before they run. It is addressed to providers and authorised representatives (paragraphs 1 and 2) and to deployers in the public sector (paragraph 3); through Art. 16(i) and Art. 26(8) the duty is tied to the general obligations of both roles. The database is governed by Article 71, the fields by Annex VIII.
The EU AI Act has been in force since 1 August 2024. Prohibitions and AI literacy have applied since February 2025, the obligations for GPAI models since August 2025, the transparency obligations under Article 50 since August 2026. After the postponement by the amending Regulation (EU) 2026/1744 (Digital Omnibus), the obligations for high-risk systems under Annex III apply from 2 December 2027, for Annex I products from 2 August 2028. Article 49 is one of those high-risk obligations. The Omnibus moved deadlines; it removed no obligation. The overview is in EU AI Act in practice.
What Article 49 requires
The technical example
A bank builds a credit pre-check model itself. It assesses the creditworthiness of retail customers, so Annex III point 5(b), and the bank is the provider under Art. 3(3) because it develops the system and puts it into service under its own name. The data flow: the application comes from the loan portal to the policy gateway, which pseudonymises, checks scope and data zone and calls the model. Back come a score band, a confidence and the supporting features; the gateway writes the evidence, the advisor decides. Art. 49(1) bites before the first real application: the Section A entry has to exist.
The same bank runs a document classifier in the credit process that sorts incoming documents by type: payslip, ID, bank statement. It operates in the area of Annex III point 5 but performs a narrow procedural task under Art. 6(3)(a), documented under Art. 6(4). That exempts it from Chapter III Section 2, not from registration: Art. 49(2) requires the Section B entry, with exactly that condition.
Third, a public authority that uses a purchased system to pre-sort applications for social benefits, Annex III point 5(a). It is a deployer and a public body, so Art. 49(3) applies: its own Section C entry, with the URL of the provider’s entry and the summaries of its fundamental rights impact assessment under Art. 27 and the DPIA. If the provider’s entry is missing, it cannot supply a URL, and under Art. 26(8) it may not use the system.
How we implement it
At SIFAMO we built the registration office before the EU database existed: the registry in the governance layer, no record, no route. Article 49 adds a public layer on top. The EU database is the number plate anyone can see: who the keeper is, which vehicle, whether it is registered. Our registry is the vehicle file behind it, with evaluation, scope, oversight, expiry and kill switch. The plate points to the file, the file feeds the plate.
Field by field against Annex VIII. Every registry record has an export view that produces the Annex VIII dataset. For the credit pre-check under Section A: item 4 is the model ID from the registry, our number plate, plus the trade name; the ID stays stable across versions, the version lives in the file. Item 5, the intended purpose, is a single field that also feeds the instructions for use under Art. 13 and the technical documentation under Annex IV, so that three documents never state three purposes. Item 6 is generated from data lineage and model card: data categories and decision logic, no feature weights, no thresholds. Item 7 follows the lifecycle state; the kill switch does not change it, decommissioning does. Items 8 and 9 do not apply to credit scoring under internal control per Annex VI, and the field says so with reasons. Item 11 is the declaration of conformity from the release gate, item 12 the versioned instructions for use.
Sections B and C. For the document classifier the Art. 6(3) condition is not free text but the field from the classification page in the first gate. The full assessment stays in the file and goes to the authority on request under Art. 6(4); the consolidated version of Annex VIII no longer asks for the summary of grounds to be public. For the public authority, the registry record of the purchased system has a mandatory field for the URL of the provider’s entry; no URL, no route.
Export at release, check on every version. The release gate with its three signatures has one additional item: Annex VIII export generated and submitted. Only when the identifier of the public entry is in the registry record does the gateway give the system a route. On every new version the export recomputes the dataset and compares it with the submitted state. If a public field has changed, the update is submitted before release. Otherwise the registry stores the hash and timestamp of the comparison. That way “kept up to date” is not an intention but a diff.
Who keeps the entry current. The business owner who signs the registry record is also the keeper of the public entry. The submitting person comes from compliance and holds the authority to represent that Art. 71(5) presupposes. Status changes such as withdrawal or recall have a deadline, and the expiry date of the registry record also triggers a review of the public entry.
Public and internal. Everything in Sections A, B and C is public and machine-readable under Art. 71(4). Competitors and journalists will read the purpose text, so we write it that way. Non-public are only the section under Art. 49(4) and the tests under Art. 60. What Annex VIII does not name stays in the file: evaluation, scope, oversight, bias checks, kill switch, expiry. The auditor sees the public entry with a timestamp before putting into service, the file behind it and per version the diff. I am an engineer, not a lawyer. But the registration office I wished for years ago now exists, and it only works if the file behind it is right.
Typical mistakes
EU AI Act Article 49 checklist
Open questions
Frequently asked questions
Does this apply to us as a deployer?
Only if you are a public authority, Union institution, body, office or agency, or act on their behalf; then Art. 49(3) applies. A private company that buys a high-risk system registers nothing itself but checks the provider’s entry under paragraph 1 before go-live. You still need the internal registry, see AI Governance.
Do we have to register a system we classified as not high-risk ourselves?
Yes, if it falls into an area of Annex III and you rely on Art. 6(3). Art. 49(2) requires the entry under Annex VIII Section B, including the condition you invoke.
What in our entry is public?
Under Art. 71(4), everything registered under Art. 49: identity, reference, purpose, logic description, status, declaration of conformity, instructions for use. Non-public are the section under Art. 49(4) and information on tests under Art. 60. The other articles in the series: all articles at a glance.
Related: EU AI Act · All articles · AI Governance · AI Consultant
Recent Posts
Recent Comments