DORA register of information: what to record about your ICT third-party providers

The register of information is the most data-heavy obligation in the Digital Operational Resilience Act. Every in-scope financial entity must keep a structured record of all contractual arrangements for ICT services, and supervisors collect it in a fixed format. Many firms treated the first submission as a one-off project. This guide explains what the register must contain and how to keep it accurate year after year.

DORA ICT third-party risk Register of information Published: 8 min read

The legal basis: Article 28(3) DORA

DORA, Regulation (EU) 2022/2554, has applied since 17 January 2025. Article 28(3) requires financial entities, as part of their ICT third-party risk framework, to maintain and update a register of information on all contractual arrangements for the use of ICT services provided by ICT third-party service providers. The register must be kept at entity level and, for groups, at sub-consolidated and consolidated levels.

The register must distinguish arrangements that support critical or important functions from the rest. Financial entities must report to their competent authority at least yearly on new arrangements, categories of providers, types of contractual arrangements and the services and functions provided, and must make the full register available on request. They must also inform the authority in a timely manner about planned arrangements for ICT services supporting critical or important functions.

The templates: Implementing Regulation (EU) 2024/2956

The format is not left to each firm. Commission Implementing Regulation (EU) 2024/2956 sets out implementing technical standards with standard templates. The register is a relational data model: separate tables are linked by keys such as the contractual arrangement reference number, the identifier of the provider and the function identifier. Supervisors collect the data in a machine-readable format, so the quality of identifiers and links matters more than formatting.

The templates are grouped into a small number of blocks. Knowing the purpose of each block makes the data collection much easier to organize internally.

  • Entity information: the entity maintaining the register, entities in scope of the consolidated register, and branches
  • Contractual arrangements: general and specific information per contract, including start and end dates, governing law, notice periods and annual cost, plus intra-group arrangements
  • Links between contracts, the entities using the services and the providers signing them
  • ICT third-party service providers: identification, ultimate parent, type of person, country, and the ICT service supply chain including subcontractors
  • Functions: identification of the business functions supported, whether they are critical or important, and their recovery objectives
  • Assessment of ICT services: substitutability, possibility of reintegration, exit plan, impact of discontinuation and alternative providers

Identifiers and data quality

Data quality was a frequent problem in the first reporting cycles. The ITS rely on standard identifiers, mainly the Legal Entity Identifier (LEI) for financial entities and, where available, for providers. For providers without an LEI, the templates allow alternative codes, but supervisors expect consistency. The same provider must not appear under different names or codes across entities in a group.

Check the basics before submission: every contract links to at least one entity and one provider, every function referenced exists in the function table, dates are logical, currencies and amounts are filled in, and the ultimate parent of each provider is identified. Validation rules published by the European Supervisory Authorities test exactly these relationships, so build the same checks into your own process.

Check your readiness for free

10–15 minutes, no account needed: readiness score, gap report and AI recommendations.

Scope: what counts as an ICT service

DORA defines ICT services broadly as digital and data services provided through ICT systems to users on an ongoing basis, including hardware as a service and technical support through software or firmware updates. In practice the register covers cloud platforms, SaaS applications, data centers, network and telecom services, core banking or insurance systems, market data feeds, managed security services and software maintenance contracts. Intra-group ICT services are included.

Firms often underestimate the register because ICT services are bought outside IT. Marketing tools, HR systems, payroll platforms and compliance screening services are all ICT services. A practical method is to start from accounts payable: list every supplier paid in the last twelve months and classify which ones provide ICT services. Then confirm with procurement and business owners that no free or bundled services were missed.

Critical or important functions and the supply chain

The register is only useful if it reflects which services support critical or important functions. That requires an up-to-date business impact analysis and a function inventory, ideally the same one used in your ICT risk and business continuity frameworks. Commission Delegated Regulation (EU) 2024/1773 sets out what the contractual policy must cover for ICT services supporting critical or important functions, and those contracts carry more data points in the register.

For ICT services supporting critical or important functions, the register also records the supply chain: which subcontractors effectively underpin the service. Ask providers for this information in a structured way, and add a contractual obligation to keep you informed of material subcontracting changes. Supervisors use this data to analyze concentration risk across the sector, and the ESAs use it in the process of designating critical ICT third-party providers for EU-level oversight.

Typical gaps and how to fix them

After the first reporting cycle, most firms know where their register is weak. These are the issues that come up most often.

  • Register maintained in a spreadsheet by one person, with no link to procurement or contract management
  • Missing or wrong LEIs for providers, and duplicate provider records across group entities
  • Contracts classified as not supporting critical functions without a documented assessment
  • Exit plans and substitutability assessments left blank or filled with generic text
  • Supply chain information missing because providers were never asked
  • No process to update the register when a contract is signed, renewed, changed or terminated
  • Register not reconciled with the ICT third-party risk strategy and the outsourcing register

Keeping the register alive

Treat the register as a by-product of your procurement and contract management process, not as an annual reporting task. Add mandatory fields to the onboarding workflow for any new ICT supplier: legal entity details and LEI, the services provided, the functions supported, the criticality assessment, data locations, subcontractors and exit considerations. Assign data owners per contract and review the register on a fixed schedule, for example quarterly, plus whenever a contract changes.

Your competent authority sets the exact submission dates and channels, which have differed between member states and sectors. Check your national authority's communications each year, and test your file against the latest ESA validation rules before submission.

The register depends on mature ICT third-party risk management in general. A free self-assessment on baltum.ai shows how your DORA practices compare with the regulation's main pillars and which gaps to prioritize.

Frequently asked questions

Does the register of information apply to small financial entities?

Yes. All financial entities in scope of DORA must maintain the register. Proportionality affects other parts of the framework, but the register obligation applies across the board, and microenterprises still need to record their ICT arrangements.

Do intra-group ICT services need to be recorded?

Yes. Intra-group ICT service providers are included in the register, and the templates contain fields to identify intra-group arrangements.

How often must the register be reported?

DORA requires at least yearly reporting to the competent authority, and the full register must be available on request at any time. National authorities set the exact dates and technical channels.

Is the register the same as the EBA outsourcing register?

No. They overlap, but the DORA register covers all ICT services regardless of whether they qualify as outsourcing, and it uses a different data model. Many firms maintain one source of data that feeds both.

What if a provider has no LEI?

The templates allow alternative identifiers for providers without an LEI. Use them consistently, and consider asking key providers to obtain an LEI, since supervisors prefer it for matching providers across the sector.

Check your readiness for free

10–15 minutes, no account needed: readiness score, gap report and AI recommendations.

This article is for general information and is not legal advice. baltum.ai is independent software, not a certification body.