What the register is
DORA, the EU’s Digital Operational Resilience Act (Regulation (EU) 2022/2554), applies from 17 January 2025. Article 28(3) asks every financial entity in scope to keep a register of all its contractual arrangements for ICT services from third parties. The implementing standards (Commission Implementing Regulation (EU) 2024/2956 of 29 November 2024) fix the templates, and ask for the register at entity level and, for groups, at sub-consolidated and consolidated level (Article 3(1)).
The EBA says the register is used by competent authorities and the ESAs to supervise compliance with DORA and to designate the critical ICT third-party service providers (CTPPs) that come under EU oversight. It gives supervisors one structured dataset of the cloud, software and data providers the EU financial sector depends on. On 18 November 2025 the ESAs designated the first critical providers from it: 19 names on the published list, including Amazon Web Services, Google Cloud and Microsoft.
How the register reaches the ESAs
Firms do not send the register to the ESAs. Under the ESAs’ decision of 8 November 2024 (ESA 2024 22), each competent authority collects the registers from its entities and sends them to the ESAs through the EBA’s EUCLID platform, on an annual basis (Articles 2, 3, 4(1) and 6). Registers go at individual level for entities outside a group, and at the highest level of consolidation in the Union for groups (Article 3).
The authorities’ deadline is 31 March, for a reference date of 31 December of the year before (Articles 4(2) and 5(1)(a)). The first round was different: reference date 31 March 2025, due 30 April 2025. In 2026 the ESAs started collecting on 25 February, took registers until 31 March and asked for corrected ones by 30 April (EBA Board of Supervisors minutes, 18 March 2026). Each authority sets an earlier deadline for its own firms; in the EBA’s words, “The ESAs do not maintain a record of such individual deadlines” (FAQ, question 12).
How national authorities collect it
The format at the EBA is fixed: xBRL-CSV only, in the plain-csv reporting package the EBA describes in its preparation slides, with xBRL-JSON metadata files from the taxonomy, against the DORA module of reporting framework 4.0. How firms reach their own authority is not. The Line4 returns library holds 16 national authorities’ rules for the register, each read on the authority’s own pages, and they differ on deadline, format and identifiers.
What goes wrong in validation
The register is unlike a COREP return. It is not a grid of numbers that must add up: it is a set of linked tables of text, codes and dates, joined by keys such as the contract reference and the provider’s identifier. Most problems are in those links.
The ESAs’ dry run in 2024 showed how hard this is. Registers came from 1,039 financial entities in 27 Member States; 947 passed the first integration checks, and of those only 6.5% passed all 116 data quality checks. Missing mandatory information was 86% of all errors (ESA 2024 35).
EBA’s list of validation rules of 12 October 2026 has 49 active rules for the DORA module, all warnings, and the EBA has published an overview of the technical checks, validation rules and business checks it applies to the registers (updated 28 April 2025). Authorities can be stricter: BaFin wants the submission “completed without errors” by 31 March.
An example: one contract across three tables
The register only works if its tables join. Here is one cloud contract, followed through three templates.
- B 02.01, contractual arrangements
- Contract reference CA-0042, start date, type of arrangement
- B 03.02, providers signing
- CA-0042 signed by the provider with LEI 5299…
- B 05.01, ICT third-party service providers
- One row for LEI 5299…, with the provider’s name, country and the type of code
The contract in B 02.01 has a signing provider in B 03.02, and that provider has its own row in B 05.01 with a valid identifier. Drop the B 05.01 row and every table still looks fine on its own, but the ESAs cannot tell who the contract is with.
What the authority receivesShowHide
b_02.01.csv CA-0042, ...
b_03.02.csv CA-0042, 5299..., ...
b_05.01.csv 5299..., Example Cloud Ltd, ...An illustration by Line4: the reference, the shortened LEI and the provider name are made up, and column codes are left out. Template names are the EBA’s.
What it means for supervisors
If you collect the register, your deadline is only part of the job. The registers arrive close to the ESAs’ 31 March date, often from firms that are not used to XBRL, and they have to pass the EBA’s checks after they leave you. Running the same checks when each firm submits gives the firm time to fix its own file.
The register is also your own dataset. Joined across firms, it shows which providers your market depends on, and where many firms rely on one provider for critical functions. That is a supervisory question you can ask before the ESAs’ designation, not after.
Where AI fits, and where people decide
AI can help where the register is text: matching provider names to identifiers, flagging a service description that does not fit its code, and drafting the question for a firm whose register looks thin for its size. Line4 Check does not read the register yet: its tables are keyed text, not the numeric cells its engine checks.
Whether a provider is critical, and what a concentration means, are supervisory decisions. Rules decide whether the register is complete and consistent. Supervisors decide what it says about risk.
- 1Publish your deadline, format and identifier rules early: the ESAs keep no record of national deadlines.
- 2Say whether you take only xBRL-CSV, or Excel or a web form you convert yourself.
- 3Check keys across tables, not only each table on its own.
- 4Check every provider LEI or EUID resolves, and that coded fields use the EBA’s value lists.
- 5Run the EBA’s checks at submission, so firms fix files before your 31 March deadline.
- 6Join registers across firms to see which providers your market depends on.
Where Line4 fits
Line4 is SupTech software for financial regulators. It collects returns in XBRL, Excel and CSV by portal, API or MCP, validates them against your taxonomies and rules at the point of submission (see XBRL software for regulators), and puts AI to work reading them, with supervisors making every decision. If you work with a standard we have not yet run in production, we will say so plainly and show you how we would approach it.
In the returns library
One page per return: who files it, how often and by when, the format and the validation rules, with links to the official documents.
- DORA register of information (ICT third-party contracts)EBA
- Register of information on ICT third-party arrangements (DORA RoI)CBI
- Register of information on ICT third-party arrangements (DORA RoI)BaFin
- Register of information on ICT third-party arrangements (DORA RoI)ACPR
- Register of information on contracts with ICT third-party service providers (DORA RoI)BdE
- DORA register of information (ICT third-party arrangements)DNB
- DORA register of information, ICT third-party contracts (DORA_ROI)NBB
- DORA register of information (ICT third-party contracts)FI
Browse every return in the library.
Questions
What is the DORA register of information?
The register every financial entity in scope of DORA keeps of all its contractual arrangements with ICT third-party service providers, under Article 28(3) of Regulation (EU) 2022/2554. Its templates are set by Commission Implementing Regulation (EU) 2024/2956 of 29 November 2024.
Who receives the DORA register of information?
The firm’s national competent authority, which sends the registers on to the European Supervisory Authorities (EBA, EIOPA and ESMA) through the EBA’s EUCLID platform, under the ESAs’ decision of 8 November 2024 (ESA 2024 22).
When is the DORA register of information due?
Authorities send registers to the ESAs by 31 March each year, with a reference date of 31 December of the year before. Each authority sets an earlier deadline for its firms: in the Line4 returns library they range from 28 February (Sweden’s FI and Finland’s FIN-FSA) to 31 March (BaFin, the ACPR, the Central Bank of Ireland and the Danish FSA).
What format is the DORA register of information in?
xBRL-CSV, in a plain-csv reporting package built on the DORA module of EBA reporting framework 4.0. Some authorities also accept Excel or a web form and convert it, and Banco de España takes XBRL-XML on its own extension and converts it to xBRL-CSV.
How many templates does the register have?
Fifteen, B 01.01 to B 99.01: the entity and its scope, the contractual arrangements, the entities and providers that signed them, who uses each ICT service, the providers and their supply chains, the functions supported, the assessment of each service, and the entity’s own definitions.
What validation rules apply to the register?
EBA’s list of validation rules of 12 October 2026 has 49 active rules for the DORA module, all warnings, and the EBA publishes an overview of the technical checks and business checks it runs. Most problems are links between tables, provider identifiers and codes outside the EBA’s value lists.
Why do the ESAs collect the register?
To designate the critical ICT third-party service providers (CTPPs) that come under EU oversight, and to supervise compliance with DORA. The ESAs designated the first CTPPs from the registers on 18 November 2025: 19 providers on the published list.
Do regulators outside Europe collect a register of ICT providers?
Yes, a few. In Australia, APRA’s CPS 230 says an entity must submit its register of material service providers to APRA every year. In Singapore, MAS asks banks to submit their outsourcing registers every six months and on request, on a MAS template used from 11 December 2024. In the US, the interagency guidance on third-party relationships of 6 June 2023 sets no register filing. DORA’s 15 templates are far more detailed than either. Line4 checks the DORA register today and can run the same link and identifier checks on an APRA or MAS register.
- EUR-Lex: Commission Implementing Regulation (EU) 2024/2956, templates for the register of information (as published by the EBA)
- ESAs: Decision of 8 November 2024 on reporting for the designation of critical ICT third-party service providers (ESA 2024 22, consolidated)
- EBA: Implementing technical standards on the register of information
- EBA: Preparation for DORA application
- EBA: FAQ on reporting of the registers of information (updated 28 March 2025)
- EBA: Preparing the plain csv reporting package for DORA (slides, 17 January 2025)
- EBA: Overview of the technical checks, validation rules and business checks for RoI reporting (updated 28 April 2025)
- EBA: List of possible values for data fields with drop-downs (updated 3 March 2025)
- EBA: Reporting framework 4.0 taxonomy package (errata 5), DORA module
- EBA: Validation rules packages (list of 12 October 2026)
- ESAs: DORA dry run exercise summary report (ESA 2024 35, December 2024)
- EBA: The ESAs designate critical ICT third-party providers (press release, 18 November 2025)
- ESAs: List of designated critical ICT third-party service providers (18 November 2025)
- EBA: Board of Supervisors minutes, call of 18 March 2026 (2026 register collection)
- Central Bank of Ireland: Reporting registers of information
- BaFin: DORA registers and notifications
- Banco de España: Instrucción I.E. 2008.02 (file formats)
- DNB: DORA register of information collection, first quarter 2027
- APRA: CPS 230 Operational Risk Management
- MAS: Response to consultation on management of outsourced relevant services (11 December 2023)
- Federal Reserve: Interagency guidance on third-party relationships (6 June 2023)
