EU DORA Intelligence Managerby LupaLynx
Request free validation

DORA Insights Guidance article

How to Prepare a DORA Register of Information

The Register can be a structured record of how financial entities use ICT services and how those services connect to contractual arrangements, providers, subcontractors and critical or important functions.

The DORA Register of Information is often approached as a reporting exercise. It is also a structured record of how financial entities use ICT services and how those services connect to contractual arrangements, providers, subcontractors and critical or important functions.

Under Article 28 of DORA, financial entities must maintain and update a Register of Information for contractual arrangements on the use of ICT services provided by ICT third party service providers.

Preparing a Register well starts with understanding the relationships behind the data, rather than completing each table in isolation.

Start with the entities in scope

First, identify the financial entities that need to be included. This may include the individual financial entity and, where applicable, entities within a group, branches and the relevant subconsolidated or consolidated level.

The implementing standards allow groups to maintain a single Register where it enables each relevant entity to meet its own maintenance and reporting obligations.

A clear entity structure provides the foundation for the rest of the Register. It helps establish which entity enters into an arrangement, which entity uses the ICT service and how services are provided within a group.

Identify the contractual arrangements

The Register should capture contractual arrangements with direct ICT third party service providers. This includes overarching arrangements, such as a master services agreement, as well as related subsequent arrangements, such as statements of work or service orders.

Each contractual arrangement needs a unique reference number so it can be identified clearly throughout the Register.

This is where many firms can gain a clearer perspective. A contract is rarely just a standalone document. It may support several ICT services, be used by several entities or sit within a wider group arrangement.

Connect services, providers and subcontractors

Next, identify the ICT services provided under each arrangement, the direct providers delivering them and any recorded subcontractors involved in the service supply chain.

The Register templates cover direct ICT third party providers, subcontractors and the ICT service supply chain, alongside the entities using the relevant services.

This makes it possible to move beyond a list of suppliers. Firms can start to understand how a service reaches the organisation, where dependencies extend beyond the direct provider and whether several important services rely on related providers or group entities.

Consider critical or important functions

A key part of the Register is understanding whether an ICT service supports a critical or important function, or a material part of one.

This requires collaboration across Legal, Procurement, ICT, Risk, Compliance and the business teams responsible for the functions. The relevant information may already exist across contracts, outsourcing records, service inventories, risk assessments and operational resilience documentation.

Bringing this information together helps a firm understand which services are especially significant, which arrangements support them and where further review may be needed.

Check quality before preparing an export

The technical standards set out 15 template types, covering entities, contracts, providers, services, supply chains, functions and the assessment of services supporting critical or important functions. The relevant templates will depend on the firm’s structure and arrangements.

Before preparing an export, review the Register for missing information, inconsistent entries and relationships that do not make sense. Each data element should contain a single value. Where more than one value is relevant, an additional row may be required.

The European Banking Authority also publishes reporting resources, validation rules and observations on common data quality issues.

Treat the Register as connected information

A well prepared Register can support more than a reporting submission. It can help teams explore which entities use an ICT service, which contracts support it, which providers are involved and how dependencies extend across the organisation and supply chain.

Maintain the information. Understand the connections. Put it to use.

Official sources

This article provides general information. Consider your organisation’s circumstances and applicable supervisory instructions when preparing or submitting the Register.

Start with a clearer view of your Register.

Explore missing information, inconsistent entries and relationships that need review through a free Register validation review.

Request free validation