# Linked AI supplier register example

All entities, contracts, references and dependency findings are synthetic. Internal EX identifiers are not legal identifiers; this is not an official filing or a completed DORA assessment.

Trace a fictional provider through its contractual arrangement to the financial entity, service user and supported function. The pack includes populated linked CSVs.

| Record relationship | Populated teaching entry | Official-structure handoff |
| --- | --- | --- |
| Entity and user | ENTITY-EX-01: fictional Example EU Finance SA. | Link entity scope and users through B_01 and B_04.01 as applicable. |
| Direct provider | PROVIDER-EX-01: fictional Example Text Services Ltd. | Provider and signing-party information link to B_05.01 and B_03.02. |
| Contract | CONTRACT-EX-01: direct subscription for the fictional drafting service. | General/specific arrangement information belongs in the B_02 family. |
| Service | SERVICE-EX-01: employee correspondence drafting, no customer action automation in the example. | Map the actual ICT service and users to the contract. |
| Function | FUNCTION-EX-01: internal administrative correspondence. | Identify the supported function in B_06.01. |
| Criticality assumption | Non-critical only for the teaching scenario, with an alternative process. | Real function assessment needs evidence; B_07.01 concerns relevant critical/important-function service assessments. |
| Identifier validation | All EX references are internal teaching identifiers, not LEIs or EUIDs. | Obtain valid legal identifiers and complete the official data requirements before filing. |

## Review steps

- Validate the legal identities: Confirm the contracting, supplying and using entities and the applicable valid LEI/EUID requirements.
- Reconcile linked references: Check that contract, provider, user and function records refer to the same actual arrangement.
- Evidence the function assessment: Have the accountable owner assess criticality, dependency and change triggers before mapping the complete official templates.

## Populated linked records

ENTITY-EX-01 uses SERVICE-EX-01 from PROVIDER-EX-01 under CONTRACT-EX-01. The service supports FUNCTION-EX-01. All names and identifiers are fictional.

## Register mapping

Use the actual 2024/2956 template instructions for B_01 entity scope, B_02 arrangements, B_03 signing entities, B_04 users, B_05 providers/supply chain, B_06 functions and the relevant B_07 assessments. This exercise does not contain every required field or controlled vocabulary.

## Data-quality finding

The EX references are suitable only for tracing this example. They must not be submitted as LEIs/EUIDs. No regulatory validation or filing has been performed.

## Source and scope

Guide: https://aona.ai/resources/guides/dora-ai-vendor-register-example/

Source check: 21 September 2026. General information, not professional approval or a completed control test.

- DORA: Regulation (EU) 2022/2554: https://eur-lex.europa.eu/eli/reg/2022/2554/oj/eng
- Commission Implementing Regulation (EU) 2024/2956: https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj/eng