In recent communications, the CSSF has reiterated both the importance and urgency of the Register of Information obligation, reminding financial entities that the RoI is a cornerstone of DORA’s oversight framework and a key input for EU‑level supervision.
Fast‑approaching deadlines
Financial entities subject to DORA and required to submit a Register of Information at individual or consolidated level must take note of the following deadlines:
- 31 March 2026 for most financial entities
- 30 June 2026 for third‑country branches of credit institutions
Despite the regulatory clarity, supervisory data shows that, as of 16 March, only around 40% of entities required to submit an RoI have done so. With the deadline rapidly approaching, the CSSF has explicitly urged remaining entities to submit their registers as soon as possible, allowing sufficient time to identify and remediate potential issues.
Quality checks do not stop at submission
Submission to the CSSF is not the end of the process. As previously communicated, the CSSF will forward all registers to the ESAs. During April 2026, the ESAs will carry out additional quality and consistency checks. Where deficiencies or errors are detected, the ESAs may reject the register, triggering a remediation cycle:
- The financial entity is informed by the CSSF
- Identified issues must be corrected
- The RoI must be resubmitted to the CSSF, which will forward it again to the ESAs
This process must be completed before the end of April 2026.
For this reason, the CSSF strongly recommends that affected firms ensure the availability of relevant resources throughout April, to avoid delays, rejections, or supervisory friction during the validation phase. In practice, this means DORA compliance teams, IT, procurement, risk management and legal functions must remain mobilized well beyond the initial filing date.
Why the Register of Information is proving challenging
The RoI is not a simple inventory exercise. It requires financial entities to demonstrate a consistent, structured and risk‑based view of their ICT third‑party ecosystem, including:
- Mapping ICT service providers and subcontracting chains
- Classifying critical and important functions
- Aligning contractual data with DORA taxonomy and definitions
- Ensuring consistency across group entities and consolidation scopes
- Reconciling IT, operational risk and outsourcing records
For many organizations, this is the first time such information is being assembled in a single, supervisory‑ready dataset, exposing data gaps, inconsistencies and governance weaknesses.