DORA Register of Information – A Practical Guide for Financial Entities
Updated October 2026
Article 28(3) of the Digital Operational Resilience Act (Regulation (EU) 2022/2554) requires every financial entity in scope to maintain and update a register of information covering all of its contractual arrangements for ICT services provided by ICT third-party service providers, at entity level and at sub-consolidated and consolidated levels. The DORA Register of Information follows the standard templates in Commission Implementing Regulation (EU) 2024/2956, and competent authorities collect it every year, at individual or consolidated level, and pass it to the European Supervisory Authorities (ESAs), which use it to designate critical ICT third-party service providers.
The register sits at the centre of your ICT third-party risk management under DORA. An incomplete register leaves your own risk management with gaps and leaves your competent authority without data it needs for ICT oversight. A complete, current one helps you manage concentration risk, subcontractor chains, and critical function dependencies.
Related reading: COREP Reporting Explained | EMIR Reporting Explained
Legal Basis and Purpose
Article 28(3) of Regulation (EU) 2022/2554 (DORA) requires financial entities to maintain and update, at entity level, at sub-consolidated level, and at consolidated level, a register of information in relation to all contractual arrangements on the use of ICT services provided by ICT third-party service providers.
The register serves three purposes, and understanding all three matters for how you populate it:
- ICT risk management: The register is part of your ICT risk management framework under Article 28(3) of DORA. It gives you a structured view of your ICT dependencies, helping you identify concentration risks, single points of failure, and critical function reliance on specific providers.
- Supervisory oversight: Financial entities must make the full register, or specified sections of it, available to their competent authority on request. The CSSF, ECB, or relevant national authority uses this data to understand the ICT dependency landscape across the entities it supervises.
- Oversight Framework input: The ESAs use register data to support designation of critical ICT third-party service providers (CTPPs) under Article 31 of DORA and the Oversight Framework structured under Article 32. Your register feeds into the identification and oversight of providers that pose systemic risks to the financial sector.
Article 28(9) mandates the ESAs to develop implementing technical standards (ITS) establishing the standard templates. The ESAs delivered these through their joint Final Report (JC 2023/85), and the resulting Commission Implementing Regulation specifies the exact templates, data fields, and fill-in instructions.
Who Needs to Maintain the Register
DORA applies to a broad range of financial entities. DORA Article 2 determines the financial entities within the Regulation’s scope. In Luxembourg, Circular CSSF 25/882, as amended by Circular CSSF 26/915, establishes additional CSSF requirements for the entities within the circular’s scope, including annual register submission, subject to the applicable entity, branch and competent-authority provisions.
The CSSF confirmed on 27 August 2026 that Circular CSSF 26/915 extended the scope of Circular CSSF 25/882 to qualifying Luxembourg branches of third-country undertakings. The best-effort arrangements for certain third-country credit-institution branches applied to the 2026 collection, which the CSSF’s 17 February 2026 communique linked to the quality of the submission of 31 March 2027. DORA’s register-of-information obligation also applies to financial entities qualifying as microenterprises.
Circular CSSF 25/882, as amended by Circular CSSF 26/915, covers the following entity types:
- Credit institutions, investment firms, market operators operating a trading venue, and APAs and ARMs benefiting from the relevant derogations under the Luxembourg Law of 5 April 1993 on the financial sector
- Payment institutions, account information service providers, and electronic money institutions
- Crypto-asset service providers and issuers of asset-referenced tokens under MiCAR
- Central securities depositories
- Central counterparties
- UCITS management companies and self-managed investment companies
- Alternative investment fund managers and internally managed AIFs
- Institutions for occupational retirement provisions (SEPCAVs and ASSEPs)
- Administrators of critical benchmarks
- Crowdfunding service providers
DORA defines a microenterprise in Article 3(60) by reference to fewer than 10 employees and annual turnover and/or annual balance sheet total not exceeding EUR 2 million, subject to the exclusions specified in that definition. Microenterprise status does not remove the obligation to maintain a register of information under Article 28(3). Proportionality affects the application of ICT third-party risk management requirements, not whether the register must exist.
The obligation applies to each financial entity individually, not just at group level. A group with three licensed entities in Luxembourg must be able to meet the register requirements at each applicable entity and consolidation level. The ESAs’ register-of-information FAQ states that the register contents should be available at the financial entity and, for the parent undertaking, at sub-consolidated and consolidated level, with each group entity remaining responsible for maintaining its own register. Recital 2 of Implementing Regulation (EU) 2024/2956 allows groups to develop a single register at entity, sub-consolidated and consolidated levels, provided the single register lets each financial entity meet its own obligation to maintain, update and report its register.
Template Structure
The ITS establishes a set of interconnected templates that capture your ICT provider landscape from multiple angles. Understanding the structure saves time because you can plan your data collection around the template relationships rather than filling each one independently.
Entity-Level Templates
B_01.01 (Financial Entity) identifies the financial entity maintaining the register. This is your entity’s LEI, name, type, and the competent authority supervising it. One row per register.
B_02.01 (Contractual Arrangements: General Information) records contractual arrangements with direct ICT third-party service providers relevant to the ICT services received by the financial entity, including arrangements signed on its behalf by another entity. Where an ICT intra-group service provider forms part of the supply chain, its relevant contractual arrangements with direct ICT service providers must also be recorded and linked through B_02.03 as applicable. Each arrangement gets a unique contractual arrangement reference number that must remain consistent over time. The contractual arrangement reference number must be used consistently in the templates and fields that refer to the same arrangement. Other templates, including the entity, provider, function and internal-definition templates, use their own applicable identifiers and relationships rather than all referencing B_02.01 directly.
B_02.02 (Contractual Arrangements: Specific Information) provides detail for each arrangement listed in B_02.01: the ICT services in scope, the functions supported by those services, notice periods, governing law, and other contractual specifics. This is where you link ICT services to your business functions.
B_03.01 (Entities Signing Contractual Arrangements) identifies the entities that signed each contract for receiving ICT services. B_03.02 (ICT Third-Party Service Providers Signing Contractual Arrangements) identifies the providers that signed for delivering the services. B_03.03 (Entities Signing Contractual Arrangements for Providing ICT Services to Other Entities Within the Scope of Consolidation) identifies entities listed in B_01.02 that sign contractual arrangements reported in B_02.01 to provide ICT services to other entities within the consolidation. The signing entity is not always the entity using the service, particularly in group structures where a parent or shared services company signs framework agreements on behalf of multiple subsidiaries.
B_04.01 (Entities Making Use of ICT Services) identifies which entities in the group actually use the ICT services provided under each contractual arrangement. In a group structure, the entity signing the contract (in B_03.01) and the entity consuming the service (in B_04.01) can differ. This template closes the loop between who signed and who depends on the service.
B_05.01 (ICT Third-Party Service Providers) identifies direct ICT third-party providers, ICT intra-group service providers, subcontractors included in B_05.02, and the ultimate parent undertakings of those providers. It records the identifiers and other provider information specified in the ITS, applying the relevant LEI, EUID and permitted alternative-identifier rules.
B_05.02 (ICT Service Supply Chains) maps the subcontracting chains. B_05.02 identifies the ICT service supply chain according to the ITS reporting rules. For services supporting critical or important functions, or material parts thereof, it includes subcontractors that effectively underpin service provision, meaning those whose disruption would impair the service’s security or continuity. Where an intra-group provider uses subcontractors, at least the first external subcontractor must also be included, even for services not supporting a critical or important function.
B_06.01 (Functions Identification) records the financial entity’s functions supported by ICT services provided by ICT third-party service providers. It identifies the relevant functions and their criticality or importance assessments using the prescribed function identifiers and fields. This classification drives additional reporting requirements: contractual arrangements supporting critical or important functions require more granular data.
B_07.01 (Assessment of ICT Services) captures the risk assessment for ICT services provided by ICT third-party service providers that support a critical or important function or material parts thereof. The prescribed fields cover matters including provider substitutability, reasons for difficult substitution, the date of the last audit of the ICT third-party provider, the existence of an exit plan, the feasibility of reintegrating the service, the impact of service discontinuation, and the identification of alternative providers. B_07.01 applies only to ICT services that support a critical or important function or material parts thereof.
The complete ITS contains 15 templates, including B_99.01 (Definitions from entities making use of the ICT Services). B_99.01 records the financial entity’s internal explanations and definitions of prescribed closed-set indicators, such as the meaning of low, medium and high impact or substitutability assessments. ICT service types are reported in B_02.02 and B_05.02 using the S01-S19 identifiers in Annex III.
Consolidated and Sub-Consolidated Templates
For groups, the register must also be maintained at sub-consolidated and consolidated levels. Article 6(1) of the ITS requires parent undertakings to take into account the relevant sectoral Union legislation when determining which entities are included in the register. Under Article 6(2), a register maintained at sub-consolidated or consolidated level includes all financial entities and ICT intra-group service providers that are part of the sub-group or group.
The ITS uses the same prescribed template set at entity, sub-consolidated and consolidated levels, as applicable. B_01.02 is also required for an entity that is not part of a group, in which case it identifies that financial entity only. B_01.03 identifies relevant branches, where applicable. B_02.03 links consecutive contractual arrangements when an ICT service supply chain contains an intra-group ICT service provider. It connects the contract between the service-using entity and its intra-group provider to that provider’s contract with its next direct ICT service provider, whether another group entity or an external provider.
A consolidated register draws on every entity in scope. Article 3(3) of the ITS requires the entity maintaining the sub-consolidated or consolidated register to ensure that entity-level information is correct and consistent with the information at those levels, and B_02.01.0010 requires the contractual arrangement reference number to be unique and consistent over time at entity, sub-consolidated and consolidated level, where applicable.
The 19 ICT Service Types
The ITS defines a closed list of ICT service types. When populating B_02.02 (Contractual Arrangements: Specific Information), the ITS requires each ICT service to be mapped to one of these 19 categories using the identifier codes S01 through S19:
- S01: ICT project management
- S02: ICT development (business analysis, software design, testing)
- S03: ICT help desk and first-level support
- S04: ICT security management services (protection, detection, response, recovery)
- S05: Provision of data (data provider subscriptions)
- S06: Data analysis
- S07: ICT facilities and hosting services (excluding cloud)
- S08: Computation (excluding cloud)
- S09: Non-cloud data storage
- S10: Telecom carrier (excluding traditional analogue telephone per Article 3(21) DORA)
- S11: Network infrastructure
- S12: Hardware and physical devices (as a service)
- S13: Software licensing (excluding SaaS)
- S14: ICT operation management including maintenance
- S15: ICT consulting
- S16: ICT risk management (verification of compliance per Article 6(10) DORA)
- S17: Cloud services: IaaS
- S18: Cloud services: PaaS
- S19: Cloud services: SaaS
The distinction between S17, S18 and S19 is relevant to accurate ICT service classification and the assessment of applicable requirements. DORA establishes ICT third-party risk requirements across ICT service types, while Chapter 3 of Circular CSSF 25/882 provides additional Luxembourg-specific clarifications on cloud computing and the cloud officer. The applicable obligations depend on the relevant service, entity and arrangement, rather than exclusively on whether a service is cloud-based.
Critical or Important Functions: The Data Depth Driver
The register is proportionate by design. For ICT services supporting standard (non-critical) functions, you report the basic contractual and provider information. For ICT services supporting critical or important functions, the ITS requires additional data: substitutability and exit-related assessment fields, subcontractor details where within the ITS reporting scope, and supply chain mapping.
This means the classification of your functions in B_06.01 directly drives the volume and depth of data you need to collect. Classifying too many functions as critical increases the volume of data to collect and maintain. Classifying too few leaves ICT services that support critical or important functions outside the additional data requirements in B_02.02, B_05.02 and B_07.01.
DORA does not provide a bright-line test for the “critical or important function” classification. Article 3(22) defines a critical or important function as a function whose disruption would materially impair the financial entity’s financial performance or the soundness or continuity of its services and activities, or whose discontinued, defective or failed performance would materially impair its continuing compliance with the conditions and obligations of its authorisation or with its other obligations under applicable financial services law. That leaves room for judgment.
A practical approach: start with the functions that your Business Continuity Plan (BCP) classifies as mission-critical. These are your candidates for “critical or important” under DORA. Assess each function against the definition in Article 3(22) of DORA, considering whether its disruption would materially impair the entity’s financial performance, the soundness or continuity of its services and activities, or its continued compliance with applicable authorisation conditions and financial-services obligations. BCP classifications can provide supporting evidence. Provider substitutability is a separate ICT third-party risk assessment and does not, by itself, determine whether a function is critical or important.
Contractual Arrangement Reference Numbers
Every contractual arrangement gets a unique reference number in B_02.01. That number must be:
- Unique within your entity and across the group (at consolidated level)
- Consistent over time (the same contract keeps the same reference number across reporting periods)
- Used consistently in every template that refers to the same arrangement (for example B_02.02, B_03.01, B_03.02, B_03.03, B_04.01 and B_05.02)
The reference number is your internal identifier. It does not need to match the contract number your legal team uses, but it must be traceable back to the actual agreement. A mapping table between your contract management system’s identifiers and the register reference numbers keeps that linkage; losing it makes future updates painful.
The reference number covers three types of arrangements:
- Standalone agreements
- Overarching or framework arrangements (master agreements, framework contracts)
- Subsequent or associated arrangements (implementing arrangements, subservice arrangements, order forms)
Service level agreements subordinated to one of these contract types are part of the parent arrangement and carry no reference number of their own.
Submission Process and CSSF Deadlines
The 2026 CSSF Collection
The CSSF collected the 2026 registers, at individual or consolidated level, between 11 February and 31 March 2026 through its eDesk portal. The reference date was 31 December 2025, so each register had to contain all contractual arrangements contracted up to that date. Entities under the direct supervision of the ECB were outside this CSSF collection. The CSSF communique of 17 March 2026 confirmed the 31 March 2026 deadline and the extended deadline for third-country branches of credit institutions: 30 June 2026, on a best-effort basis.
As of 16 March 2026, only 40% of the financial entities required to submit to the CSSF had done so, and the CSSF urged the rest to file as soon as possible so that issues could be addressed in time. The validation checks defined by the ESAs had not changed since April 2025, but in 2026 they were applied to more data fields, and the CSSF warned that a register accepted in 2025 could be rejected in 2026.
The Next Collection
Article 28(3) of DORA treats maintaining the register and reporting on it as distinct duties. It requires the register to be maintained and updated on an ongoing basis; it requires financial entities to report to the competent authority at least yearly on the number of new arrangements on the use of ICT services, the categories of ICT third-party service providers, the types of contractual arrangement, and the services and functions provided; and it requires the full register to be made available to the competent authority on request. In Luxembourg, Circular CSSF 25/882 requires financial entities to submit the full register annually, at individual or consolidated level as applicable. The ESAs’ final Q&A 2025_7309 clarifies that the annual register submission generally fulfils Article 28(3)’s requirement to report information on new ICT contractual arrangements; a separate annual communication is not normally necessary.
At EU level, the ESAs’ Decision ESA 2024 22 requires competent authorities to send the registers to the ESAs annually, with a reference date of 31 December of the calendar year preceding the reporting date (Article 4). The CSSF’s 2026 reference date of 31 December 2025 matched that rule. Circular CSSF 25/882 (point 18) also sets year-end reference dates for the recurring Luxembourg collection: the register of year n contains all arrangements contracted until the end of year n. Accordingly, under the currently applicable framework, the register reported in 2027 relates to arrangements contracted up to 31 December 2026, unless the applicable requirements are subsequently changed.
As at 22 October 2026, Circular CSSF 25/882 (point 18) already establishes a standing submission period of 28 February to 31 March of year n+1 for registers covering arrangements contracted up to the end of year n, following the instructions on the CSSF website. On that basis, the prescribed 2027 reporting period runs from 28 February to 31 March 2027, with a reference date of 31 December 2026, unless subsequently amended.
Points 3 and 4 of the circular provide that its Chapter 2 does not apply to EU branches or to significant credit institutions for which the ECB is the competent authority. The CSSF’s 2026 communiques do not set out the 2027 portal-opening or channel arrangements. The CSSF’s communique of 17 February 2026 also referred to “the submission of 31 March 2027” in explaining why third-country branches of credit institutions were invited to file on a best-effort basis in 2026. The CSSF publishes its register-of-information communiques and guidance on its ICT and cyber risk page for DORA entities and asks financial entities to monitor those pages closely.
The Two-Stage Quality Check
The CSSF’s 2026 communiques set out validation in two stages. Uploaded registers were to be validated by the CSSF first, and the submitting entity was to be invited to fix any errors and resubmit before 31 March 2026. The CSSF stated that it would forward the registers to the ESAs for additional quality control checks during April 2026. Under the ESAs’ Decision ESA 2024 22, competent authorities submit the registers to the EBA, acting on behalf of all three ESAs, through the EBA’s EUCLID reporting channel, and the EBA may run further quality checks and require revisions that competent authorities pass on to financial entities (Articles 6 and 7).
The CSSF specified that, if the ESAs rejected a register during the April 2026 checks, the submitting entity would be informed and required to correct and resubmit it to the CSSF for onward transmission before the end of April 2026. The CSSF advised submitting entities to keep the relevant resources available throughout April for that validation process.
Submission Channel
The CSSF ran the 2026 collection through its eDesk portal, using the procedure “Submission of the Register of Information”. Before uploading, the submitting entity had to communicate its LEI to the CSSF and assign the eDesk role “DORA Reporting” to at least one employee; upload and validation messages went only to the person who uploaded the file. The register itself had to be filed as plain-csv files inside a .zip file, following the folder structure and file naming convention defined by the ESAs, and the CSSF referred entities to the ESAs’ reporting instructions on the EBA website. Checking the data against the ESAs’ validation rules before upload reduces the risk of an automatic rejection.
Common Errors and How to Avoid Them
Inconsistent Reference Numbers
An important data-quality risk is using inconsistent reference numbers for the same contractual arrangement across templates. B_02.01 assigns the number. B_02.02, B_03.01, and every other template that refers to the arrangement must use the exact same alphanumeric string. A typo or formatting inconsistency, such as a missing leading zero or a different separator, can break cross-template references and may trigger automated validation errors. Financial entities should also reconcile contractual arrangement identifiers against their source contracts, because automated validation is not a substitute for completeness and accuracy controls.
Missing Subcontractor Chains
A register that lists only direct ICT providers omits the supply chain captured in B_05.02. If a cloud provider uses a subcontractor that effectively underpins an ICT service supporting a critical or important function, or a material part thereof, the subcontractor must be included in the supply-chain reporting. For other arrangements, apply the specific requirements of B_05.02, including the rule for the first external subcontractor used by an intra-group service provider. The information may not be easy to obtain from your provider, but DORA places the obligation on the financial entity to maintain this data.
Review contractual provisions and provider disclosure arrangements against DORA Article 30 and any applicable subcontracting requirements, including those for ICT services supporting critical or important functions. Where the existing arrangements do not provide the information or contractual rights required under the applicable rules, assess and document the necessary remediation.
Misclassifying ICT Service Types
The ITS requires each ICT service reported in B_02.02 to be assigned the relevant S01-S19 service type. Where a contractual arrangement includes distinguishable ICT services of different types, those services must be represented using the applicable rows and categories. The classification should reflect the services actually provided and the descriptions in Annex III. If in doubt, the ITS instructions provide descriptions for each category.
Over-Classifying Critical Functions
Marking every function as “critical or important” triggers the full data requirement for every associated ICT service. This creates a volume of reporting that is difficult to maintain and may not reflect your actual risk profile. Be deliberate about the classification. The classification should be supported by documented impact assessments and applied consistently across the entity’s functions. A competent authority may challenge classifications that are not adequately supported by the criteria in Article 3(22) of DORA.
Forgetting Intra-Group ICT Services
Groups that have an ICT shared services entity (an “ICT intra-group service provider” in DORA terms) must capture those arrangements in the register. These intra-group arrangements are in scope: Article 6(2) of the ITS requires sub-consolidated and consolidated registers to include ICT intra-group service providers, and B_05.01 lists them. Template B_02.03 identifies the contractual-reference links along an intra-group ICT service chain, including links between successive intra-group arrangements and, where applicable, links to an external ICT third-party service provider. The relevant contractual arrangements themselves are reported through B_02.01 and the other applicable templates.
Using Provider Identifiers Incorrectly
Under Article 3(5) of Implementing Regulation (EU) 2024/2956 and template B_05.01, legal-person ICT third-party service providers established in the EU must be identified using a valid and active LEI or an EUID, and both identifiers where available. Where both are available, the additional identifier is recorded in B_05.01.0030, with its identifier type in B_05.01.0040. Legal-person ICT providers established outside the EU must use an LEI. Alternative identifiers such as CRN, VAT, PNR or NIN are permitted as primary identifiers only for individuals acting in a business capacity.
The applicable identifier-type values must follow Commission Implementing Regulation (EU) 2024/2956 as corrected on 19 September 2025. Check available LEIs through GLEIF and apply the ITS and current validation rules rather than assuming that any national identifier is acceptable.
Ongoing Maintenance Obligations
The annual collection captures the register as at its reference date. Between collections, Article 28(3) requires financial entities to keep maintaining and updating it on an ongoing basis. The register should be updated when reportable contractual arrangements, providers, ICT services, functions or supply-chain relationships change. Subcontractor changes require an update where the affected subcontractor falls within the ITS reporting scope.
In practice, this means integrating the register into your contract lifecycle management process. When procurement plans a new ICT service agreement, confirm whether it supports a critical or important function and whether a separate supervisory notification is required before the arrangement takes effect. Under Circular CSSF 25/882, entities subject to its Chapter 2 notification requirement must notify qualifying planned arrangements at least three months before they come into effect, reduced to one month when using a qualifying Luxembourg support PFS. Register maintenance is an additional, separate obligation and should be integrated into the contract onboarding workflow. When a contract is terminated, record its termination date and reason in the relevant fields.
Final EIOPA Q&A DORA 253-3393 clarifies that, where an arrangement was included in the register reported for year X and terminates during year X+1, it is included in the X+1 register with its termination date in B_02.02.0080 and reason in B_02.02.0090. It is excluded from the X+2 register. When a provider notifies you of a change to a subcontractor within the B_05.02 reporting scope, the supply chain template gets updated.
Assign a register owner at the entity level, within the ICT risk management function or the compliance team, so that the Article 28(3) duty to maintain and update the register on an ongoing basis has a named responsible function.
How the Register Feeds the CTPP Oversight Framework
Beyond your own risk management and supervisory reporting, the register data feeds into the ESA Oversight Framework for Critical ICT Third-Party Service Providers (CTPPs). The ESAs aggregate register data across the financial sector to identify providers on which a significant number of financial entities depend.
Providers designated as CTPPs are subject to direct ESA oversight, including inspections and recommendations. Article 31(2) of DORA identifies four designation criteria: potential systemic impact, the systemic character of the financial entities depending on the provider, reliance on its services for critical or important functions, and the degree of substitutability. Article 31(8)(iv) separately excludes certain providers whose services and financial-entity clients are confined to a single Member State. Commission Delegated Regulation (EU) 2024/1502 specifies the assessment criteria in greater detail.
Your register contribution matters because it directly informs these assessments. If your entity depends on a provider that is a CTPP (or a candidate for designation), the quality and completeness of your register data affects the ESA’s ability to oversee that provider effectively.
In January 2026, the ESAs and UK financial regulators signed a Memorandum of Understanding on oversight of CTPPs under DORA, reflecting the cross-border nature of major cloud and ICT providers. The memorandum establishes a framework for cooperation between the ESAs and UK financial regulators on oversight of critical ICT third-party service providers. It does not create an additional register-of-information obligation for financial entities.
EBA ICT Risk Report: Supervisory Context
The EBA’s 23 February 2026 follow-up report on ICT risk assessment under the SREP finds that competent authorities have made progress in strengthening ICT risk assessment, driven largely by DORA implementation. The register provides competent authorities with structured information on financial entities’ ICT third-party dependencies. Such information may inform supervisory ICT risk assessment.
Maintaining an accurate register supports compliance with DORA and provides supervisors with reliable information about ICT third-party dependencies. Recital 1 of Implementing Regulation (EU) 2024/2956 describes the information in the register as essential for the effective supervision of financial entities by their competent authorities.
Frequently Asked Questions
Does the register cover all ICT services, even small ones?
Yes. Article 28(3) refers to “all contractual arrangements on the use of ICT services provided by ICT third-party service providers.” Article 28(3) does not establish a materiality threshold for contractual arrangements involving ICT services within DORA’s scope. However, Article 3(21) defines ICT services as digital and data services provided on an ongoing basis and expressly excludes traditional analogue telephone services. The ESAs’ reporting FAQ clarifies that a one-off purchase of a static solution without ongoing maintenance, support or updates does not meet that definition. The proportionality is built into the template design: non-critical ICT services require less granular data than services supporting critical or important functions.
Do microenterprises need to maintain the register?
Yes. All financial entities subject to DORA, including microenterprises, must maintain and update a register of information under Article 28(3). Article 16 provides a simplified ICT risk management framework for the categories of financial entities specified in that provision; it does not exempt them from Article 28(3). The register requirements remain subject to the applicable principle of proportionality.
What if my ICT provider does not have an LEI?
For an ICT provider that is a legal person established in the EU, the ITS requires a valid and active LEI or an EUID, and both where available, in accordance with Article 3(5) of Implementing Regulation (EU) 2024/2956. For a legal person established outside the EU, an LEI is required. Other identifier types, including CRN, VAT, PNR and NIN, are permitted as primary identifiers only for individuals acting in a business capacity. Consult the applicable ESA technical instructions and validation rules if a required identifier is unavailable.
How often do we need to update the register?
Updating is continuous. Article 28(3) requires the register to be maintained and updated, so it changes whenever circumstances do: new contracts, terminated contracts, provider changes, subcontractor changes within the ITS reporting scope, critical function reclassifications. Reporting follows a separate yearly cycle, described in the submission section above. A periodic internal reconciliation, quarterly for example, catches changes that were missed when they happened.
Do intra-group ICT services need to be in the register?
Yes. ICT intra-group service providers are in scope: the ESAs’ register-of-information FAQ states that they are recorded in the registers kept by the financial entities belonging to the group. The entity receiving the intra-group ICT service reports the arrangement in the standard templates, treating the intra-group provider as it would any ICT third-party service provider. Template B_02.03 records the contractual-reference links along an intra-group ICT service chain. These can include links between two intra-group contractual arrangements and links from an intra-group arrangement to a related contract with an external ICT third-party service provider.
What is the penalty for not submitting by the deadline?
DORA does not specify a fixed penalty schedule for late submission. The competent authority has supervisory powers to address non-compliance, which may include supervisory measures, enhanced monitoring, or administrative sanctions depending on the jurisdiction and the entity type. In Luxembourg, the CSSF has a range of enforcement tools. The more practical risk is data quality. In the 2026 collection, the CSSF set aside April 2026 for the ESAs’ quality checks and any resubmissions, so a late register left less time for correction rounds before the end of April.
Can we submit a partial register and complete it later?
The CSSF expects a complete register at the time of submission. Point 18 of Circular CSSF 25/882 provides that the register of year n should contain all arrangements contracted until the end of year n, and point 19 requires financial entities to correct data promptly when the CSSF requests it. Questions on the content of a register go to ictrisksupervision@cssf.lu, the contact the CSSF’s 11 February 2026 communique gives for that purpose.
Practical Implementation Checklist
- Inventory all ICT service contracts across legal, procurement, and IT departments
- Assign unique contractual arrangement reference numbers in a mapping table
- Identify and classify functions under DORA Article 3(22), using BCP impact assessments as supporting evidence; assess ICT provider substitutability separately under the applicable third-party risk assessment requirements.
- Map each ICT service to one of the 19 service type categories (S01-S19)
- Collect provider identifiers in accordance with Article 3(5) of the ITS, recording both a valid and active LEI and an EUID where both are available for a legal-person ICT third-party service provider; check LEI validity through GLEIF
- Request subcontractor chain information from all providers supporting critical functions
- Populate the templates (B_01.01 through B_07.01, plus B_99.01)
- If part of a group: coordinate with the ultimate parent on consolidated-level templates
- Validate data against the ESAs’ validation rules before submission
- Submit within the 28 February to 31 March window that Circular CSSF 25/882 sets for the year after the reference date, through the channel the CSSF publishes (the 2026 collection used eDesk and closed on 31 March 2026)
- Assign a register owner for ongoing maintenance
- Integrate register updates into the contract lifecycle management process
Related Articles
- COREP Reporting Explained: The Common Reporting framework for capital requirements, which intersects with ICT risk through the SREP process
- FINREP Reporting Explained: Supervisory financial reporting covering financial position and performance, distinct from the DORA ICT third-party register
- EMIR Reporting Explained: Derivatives reporting where ICT infrastructure providers are often critical dependencies
- MiCAR Reporting Obligations: Crypto-asset service providers authorised under MiCAR and issuers of asset-referenced tokens fall within DORA’s financial-entity scope; other MiCAR participants are not automatically subject to DORA
- MREL Prior Permission for Own Funds Reduction: Another recent prudential process guide for banks navigating regulatory workflows
- PSD2 Reporting Requirements: Payment institutions subject to DORA must maintain the register alongside their PSD2 obligations
Key Takeaways
- The DORA Register of Information under Article 28(3) requires all in-scope financial entities to maintain a structured inventory of every ICT third-party service arrangement at entity, sub-consolidated, and consolidated levels
- The ITS contains 15 interconnected templates, including B_99.01. B_02.01 establishes the contractual arrangement reference number, which is used consistently wherever the corresponding contractual arrangement is referenced; other templates also rely on entity, provider and function identifiers
- ICT services supporting critical or important functions require additional data (substitutability and exit-related assessment fields, supply chains, subcontractor details) compared to standard services
- The CSSF’s 2026 collection closed on 31 March 2026 (30 June 2026, best effort, for third-country branches of credit institutions), with ESA quality checks announced by the CSSF for April 2026; as at 22 October 2026 Circular CSSF 25/882 already sets a 28 February to 31 March window of the following year, with a 31 December 2026 reference date for the 2027 collection, unless amended
- The 19 ICT service type categories (S01-S19) are a closed list. Map each ICT service to the applicable type, representing distinguishable services of different types using the applicable rows
- B_05.02 must capture the subcontractors that effectively underpin ICT services supporting critical or important functions or material parts thereof, and the other providers required by its specific intra-group supply-chain rules
- Maintenance is ongoing: the register has to be updated as contracts, providers, and function classifications change, between the yearly collections
- Register data feeds the ESA CTPP Oversight Framework, meaning your submission quality affects the supervisory response to systemic ICT providers
Sources and References
- Regulation (EU) 2022/2554 (DORA): Digital Operational Resilience Act, Article 28 https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32022R2554
- Commission Implementing Regulation (EU) 2024/2956 of 29 November 2024 (ITS on standard templates for the register of information), as corrected by the corrigendum published in OJ L 2025/90725 on 19 September 2025. The corrigendum corrects technical instructions including B_05.01.0020, B_05.01.0090, B_06.01 column references and B_07.01.0110. https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj. Corrigendum: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2956R(01)
- ESAs Joint Final Report on Draft ITS on Register of Information (JC 2023/85, 10 January 2024) https://www.eba.europa.eu/sites/default/files/2024-01/30b47816-8d6d-432f-8dbd-b900c4306cf4/JC%202023%2085%20-%20Final%20report%20on%20draft%20ITS%20on%20Register%20of%20Information%20%281%29.pdf
- ESAs Proposals for Further Changes to the Annex of the ITS on Register of Information (JC 2024/79): Updated ICT service type taxonomy and template amendments
- Commission Delegated Regulation (EU) 2024/1502 of 22 February 2024 supplementing Regulation (EU) 2022/2554 by specifying the criteria for the designation of ICT third-party service providers as critical for financial entities http://data.europa.eu/eli/reg_del/2024/1502/oj
- ESAs Decision ESA 2024 22 of 8 November 2024 concerning the reporting by competent authorities to the ESAs of information necessary for the designation of critical ICT third-party service providers (consolidated version) https://www.eba.europa.eu/sites/default/files/2025-01/4105fa1e-2de5-4dd2-9d9a-b89924039636/EBA%20BS%202025%20048%20%28EBA%20DC%20562%20-%20ESA%202024%2022%20-%20Decision%20on%20reporting%20of%20information%20for%20CTPP%20designation_consolidated%29.pdf
- Circular CSSF 25/882 (as amended by Circular CSSF 26/915): DORA ICT third-party arrangements and cloud computing requirements https://www.cssf.lu/en/Document/circular-cssf-25-882/
- CSSF Communique: Application of the Digital Operational Resilience Act (DORA) to Third-Country Branches in Luxembourg (27 August 2026) https://www.cssf.lu/en/2026/08/application-of-the-digital-operational-resilience-act-dora-to-third-country-branches-in-luxembourg/
- Circular CSSF 26/915 on the applicability of DORA to third-country branches in Luxembourg (27 August 2026) https://www.cssf.lu/en/Document/circular-cssf-26-915/
- CSSF Communique: DORA Submission Timeframe for Register of Information, eDesk Portal Open as of 11 February 2026 https://www.cssf.lu/en/2026/02/dora-submission-timeframe-for-register-of-information-edesk-portal-open-as-of-11-february-2026/
- CSSF Communique: DORA Submission Timeframe for Register of Information for Third-Country Branches of Credit Institutions (17 February 2026) https://www.cssf.lu/en/2026/02/dora-submission-timeframe-for-register-of-information-for-third-country-branches-of-credit-institutions-having-their-head-office-in-a-third-country/
- CSSF Communique: DORA Register of Information Collection, Update 17 March 2026 https://www.cssf.lu/en/2026/03/dora-register-of-information-collection/
- CSSF: ICT and Cyber Risk for DORA Entities (register of information communiques and guidance) https://www.cssf.lu/en/ict-and-cyber-risk-for-dora-entities/
- ESAs: DORA Register of Information reporting FAQ (updated 28 March 2025) https://www.eba.europa.eu/sites/default/files/2025-03/31bb6e60-7d10-4405-a8c5-9f04934630ac/20250328%20-%20DORA%20RoI%20reporting%20FAQ%20%28updated%29.pdf
- ESAs final Q&A 2025_7388 on the register of information and Article 16 DORA https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2025_7388
- ESAs final Q&A 2025_7309 on the annual register submission and Article 28(3) https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2025_7309
- EIOPA final Q&A DORA 253-3393 on terminated contractual arrangements https://www.eiopa.europa.eu/qa-regulation/questions-and-answers-database/dora-253-3393_en
- EBA Follow-up Report on ICT Risk Assessment under SREP (2026) https://www.eba.europa.eu/publications-and-media/press-releases/eba-publishes-follow-report-ict-risk-assessment-under-supervisory-review-and-evaluation-process
- ESAs-UK Memorandum of Understanding on CTPP Oversight https://www.eiopa.europa.eu/european-supervisory-authorities-and-uk-financial-regulators-sign-memorandum-understanding-oversight-2026-01-14_en
Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.
