The EU’s Digital Operational Resilience Act, DORA, applies from 17 January 2025, and for EU AIFMs and UCITS management companies the DORA register of information is likely to take more data work than any other requirement. The register calls for a complete record of every contract with an information and communication technology (ICT) third-party service provider, kept in standard templates and ready to hand to the regulator. The European Supervisory Authorities’ (ESAs’) voluntary dry run for the register closed its collection window on 30 August, so with four months to go we’ve set out where the rules stand and what they mean for investment managers.
Who’s in scope?
DORA lists the financial entities it covers, and these include managers of alternative investment funds and UCITS management companies, although smaller AIFMs registered under the de minimis regime in Article 3(2) of AIFMD are excluded. DORA covers ICT risk management, incident reporting, resilience testing and third-party risk. This post concentrates on the register, because it’s the part that turns your network of suppliers into a regulatory dataset.
What is the DORA register of information?
Under Article 28(3), every financial entity must keep and update a register of information on all its contractual arrangements for ICT services provided by third parties. It’s held at entity level and, for groups, at sub-consolidated and consolidated level, and it must distinguish the arrangements that support critical or important functions. Firms must report to their competent authority at least yearly on new arrangements, make the full register available on request, and tell the authority in good time about planned arrangements supporting critical or important functions.
The register serves three purposes, in that it helps firms monitor their own third-party risk, it lets national regulators supervise that risk, and it feeds the ESAs’ designation of critical ICT third-party providers, which will face EU-level oversight.
Where do the DORA technical standards stand?
The register templates themselves are still in draft, even though the ESAs submitted final draft implementing technical standards on the register to the European Commission on 17 January 2024, alongside three sets of regulatory technical standards (RTS). As at today the Commission hasn’t adopted the register standards, so firms are building to the ESAs’ final draft.
The three companion standards from that first batch, on the other hand, are now law. The Commission adopted them, they were published in the Official Journal on 25 June 2024 and they entered into force on 15 July:
- the RTS on the ICT risk management framework (Delegated Regulation 2024/1774)
- the RTS on classifying ICT-related incidents (2024/1772)
- the RTS on the policy for ICT services supporting critical or important functions (2024/1773)
A second batch is now with the Commission. On 17 July 2024 the ESAs published further final drafts, including the content, templates and timelines for reporting major ICT-related incidents and the RTS on threat-led penetration testing, and these now go through the Commission’s review.
How does the register of information dry run work?
To help firms prepare, the ESAs and national regulators organised a voluntary dry run of register reporting on a best-efforts basis. Materials, a draft data point model, CSV specifications and an Excel template were made available from 31 May, and participating firms submitted their registers through their competent authorities between 1 July and 30 August.
According to the ESAs’ plan, data quality checks finish on 31 October, with feedback and cleaned files returned to firms, followed by a lessons-learnt workshop in November and aggregated data quality reports in early December. The ESAs have said the first official register submissions will come in early 2025.
What it means in practice
The register is a data project rather than a policy document. It’s a structured dataset with identifiers, contract details, the functions each service supports and the chain of providers behind them, and most firms hold that information across procurement, legal, IT and operations teams in different formats.
Fund operations sit right in the middle of it, because fund accounting, transfer agency, data and document production, websites and investor portals typically depend on ICT services from third parties. Each of those relationships, and the functions they support, needs to be captured, and fund operations teams are often best placed to know which ones matter.
Deciding what counts as critical or important is also a judgement you’ll need to be able to explain to your regulator. That classification drives how much detail the register needs and which arrangements require advance notice.
The timeline
- 27 December 2022: DORA is published in the Official Journal
- 17 January 2024: the ESAs submit the first batch of final draft standards, including the register templates
- 25 June 2024: three first-batch RTS are published in the Official Journal
- 1 July to 30 August 2024: the dry run register collection takes place
- 17 July 2024: the second batch of final draft standards is published
- 31 October 2024: the planned end of dry run data quality checks and feedback to firms
- 17 January 2025: DORA applies, and registers must be in place
- Early 2025: the first official register reporting is expected
What to do now
- Build an inventory of every ICT arrangement, listing each third-party ICT service, the contract behind it and the functions it supports, including those that sit with your fund administrators and data providers.
- Decide what’s critical or important and document your assessment, so it can be explained and reused across the register and your notifications.
- Build to the draft templates while staying flexible, structuring the data in line with the ESAs’ final draft and being ready to adjust when the Commission adopts the final standards.
Four months isn’t long for a dataset that most firms have never assembled in one place. The firms in the best position on 17 January are likely to be those that treat the register as governed data, with clear owners and regular maintenance, rather than as a one-off spreadsheet.
At Kurtosys we help investment managers keep their fund data governed and consistent, so the same numbers flow into factsheets, regulatory documents, client reports and fund websites. That same discipline, one owned source with an audit trail, is what makes a register of information manageable year after year. If you’d like to talk through how your fund data and document production fit into your DORA preparations, get in touch.
Sources: Regulation (EU) 2022/2554 (DORA), ESAs: first set of rules under DORA, 17 January 2024, Delegated Regulation (EU) 2024/1773, ESAs: second batch of policy products under DORA, 17 July 2024, ESAs: factsheet on the 2024 dry run, 11 April 2024, as at 1 September 2024.
About this article
This article reflects the position at 1 September 2024 and was checked against the primary sources available at that time. Thomas Bjerkén, our regulatory reporting and fund data specialist, joined Kurtosys after it was published and now looks after our regulatory content. Some details may have changed since it was published.