In short
The register of information that financial entities submit to BaFin in 2027 must reflect the position as at 31 December 2026. The legal basis is Article 28(3) DORA; form and content are set by Implementing Regulation (EU) 2024/2956. Submission via the MVP must be completed without errors by 31 March 2027; BaFin announces the window early in the year.
Reference Date and Submission: How 2026 and 2027 Connect
Regulation (EU) 2022/2554 (Digital Operational Resilience Act, DORA) has applied since 17 January 2025 (Article 64). Article 28(3) requires financial entities to maintain and update a register of information on all contractual arrangements for the use of ICT services. The Regulation does not set a calendar reference date. It requires reporting to the competent authority at least yearly (third subparagraph) and making the full register available upon the authority’s request (fourth subparagraph).
In Germany, BaFin sets the calendar. According to its page Informationsregister und Anzeigepflichten, the register must reflect the position as at 31 December of the previous year, and the submission process must be completed in full and without errors by 31 March at the latest. For the 2027 submission, the relevant position is therefore that of Thursday, 31 December 2026. BaFin expressly bases its annual request on the fourth subparagraph of Article 28(3) DORA, i.e. on its power to request the register (BaFin, 2026 submission period).
The specific 2027 submission window is still open. BaFin states that it announces on its website at the start of each year from when it will accept registers. In 2026 the window ran from Monday, 9 March, to Monday, 30 March 2026, closing one day before 31 March. Teams planning internally for Wednesday, 31 March 2027, should check the closing date once the window is announced. All deadlines are collected in the deadline overview.
According to BaFin, no taxonomy changes are planned for the 2027 submission cycle. The data structure used for the 2026 submission therefore remains the working basis.
| Date | Event | Source |
|---|---|---|
| 22 December 2024 | Implementing Regulation (EU) 2024/2956 enters into force (20th day after publication in the OJ of 2 December 2024) | Article 7, Regulation (EU) 2024/2956 |
| 17 January 2025 | DORA applies | Article 64 DORA |
| 9 to 30 March 2026 | 2026 submission window, position as at 31 December 2025 | BaFin, 2026 submission period |
| Early April 2026 | First data quality feedback from the ESAs via the MVP portal | BaFin DORA FAQ |
| 31 December 2026 (Thursday) | Reference date: position for the 2027 submission | BaFin, submission cycle |
| 1 January 2027 (Friday) | Start of application for institutions under Section 1(1b) KWG that do not already apply DORA | BaFin DORA FAQ |
| Early 2027 (open) | BaFin announces from when it accepts registers | BaFin, submission cycle |
| 31 March 2027 at the latest (Wednesday) | Submission completed in full and without errors; closing date of the window open | BaFin, submission cycle |
Legal Basis: Article 28(3) DORA and Implementing Regulation (EU) 2024/2956
Article 28(3) DORA combines five obligations: maintain and update the register at entity level and at sub-consolidated and consolidated levels; document the arrangements, distinguishing between ICT services supporting critical or important functions and the rest; report at least yearly on new arrangements, categories of providers, types of arrangement and the services and functions provided; make the full register, or specified sections, available on request; and inform the competent authority in a timely manner about any planned arrangement supporting critical or important functions and when a function has become critical or important.
The standard templates are laid down in Implementing Regulation (EU) 2024/2956, adopted under the mandate in Article 28(9) DORA. Under its Article 3(1), financial entities maintain the register using the templates set out in Annexes I to IV. Annex I contains column-by-column instructions, each with the column’s mandatory status. Financial entities may add further information where it is relevant for their risk or contract management (Article 5(2)).
Two definitions determine the scope. Under Article 3(21) DORA, ICT services are “digital and data services provided through ICT systems to one or more internal or external users on an ongoing basis”, including hardware as a service. Under Article 3(22), a critical or important function is one whose disruption would materially impair the financial performance or the soundness or continuity of the entity’s business, or whose failed performance would materially impair continuing compliance with the conditions of its authorisation. BaFin’s DORA FAQ clarifies that this resembles the protection goal of availability without being identical to it; a function can also be critical or important from a confidentiality perspective.
The FAQ add two points on scope. Where another supervised financial entity provides a regulated financial service, that service is not treated as an ICT service within the meaning of Article 3(21) for the purposes of ICT third-party risk management. For institutions under Section 1(1b) of the German Banking Act (KWG) that do not already apply DORA under Article 2, the obligations apply from 1 January 2027 according to the FAQ. Whether these institutions must already submit a register for the 31 December 2026 reference date is not expressly addressed in the FAQ and should be clarified with the supervisor.
Terminology: EU DORA, Regulation (EU) 2022/2554, should not be confused with the DORA metrics from the DevOps field, which measure the throughput and stability of software delivery. This article deals exclusively with the Regulation; the metrics are covered in the [guide to DORA metrics](/blog/dora-metrics-guide).
What Must Be in the Register: the Templates in Annex I
Article 5(1) of the Implementing Regulation lists fifteen content areas (points (a) to (o)), each with a template from Annex I. Under Article 4(1), each template is a table with a predefined number of columns and an undefined number of rows. Each data point takes a single value; where several values are valid, an additional row is added for each (Article 4(2)).
The overview below follows the order of the Regulation. For a financial entity that is not part of a group, several templates become simpler: B_01.02 then contains only the entity itself, and at entity level the signing and the using entity in templates B_03 and B_04 are the entity maintaining the register.
| Template | Content | Note from Annex I |
|---|---|---|
| B_01.01 | Entity maintaining the register | includes LEI, competent authority and date of the reporting (B_01.01.0060, ISO 8601) |
| B_01.02 / B_01.03 | Entities within the scope of consolidation, branches | without a group, only the entity maintaining the register |
| B_02.01 / B_02.02 | Contractual arrangements: general and specific information | unique reference number per arrangement; services, functions, notice periods, locations |
| B_02.03 | Intra-group arrangements | links where part of the ICT service supply chain is intra-group |
| B_03.01 to B_03.03 | Signing entities and providers | at entity level, the entity maintaining the register |
| B_04.01 | Entities making use of the ICT services | financial entities or ICT intra-group service providers |
| B_05.01 / B_05.02 | ICT third-party service providers and supply chain | identifier (LEI/EUID), rank in the chain |
| B_06.01 | Identification of functions | criticality, date of assessment, RTO, RPO |
| B_07.01 | Assessment of ICT services supporting critical or important functions | substitutability, last audit, exit plan, alternatives |
| B_99.01 | Terminology used | internal meaning of the options in closed lists |
Scope: Rank 1, Subcontractors and Intra-Group Providers
The Implementing Regulation places every provider in an ICT service supply chain. Under Article 2, the rank of the direct ICT third-party service provider must always be 1 and that of a subcontractor always higher than 1; the lower the number, the closer the arrangement is to the financial entity. In B_05.02, a provider that contracts with the direct provider is reported as a subcontractor with rank 2.
Which ranks belong in the register depends on the function supported. Article 3(2) of the Implementing Regulation and BaFin’s register page give the following picture:
In practice, the more functions are classified as critical or important, the deeper the documentation reaches into the supply chain. The function assessment is therefore the first work step before the reference date.
- Direct ICT third-party service providers (rank 1): always, regardless of whether the service supports a critical or important function.
- Subcontractors: for ICT services supporting critical or important functions or material parts thereof, all subcontractors ensuring that service (Article 3(2)(b)), or, in BaFin’s wording, effectively supporting it.
- Intra-group ICT providers that use subcontractors: at least the first subcontractor outside the group, even where no critical or important function is supported (BaFin).
- Groups: the parent undertaking decides, taking sectoral Union law into account, which entities are included in the register (Article 6(1)); the consolidated register covers all financial entities and ICT intra-group service providers of the group and sub-group (Article 6(2)).
What “Position as at 31 December 2026” Means for Individual Fields
The reference date fixes the position the register has to show. Several columns in Annex I depend on dates and periods; they should be checked before year-end, because later corrections must also reflect the position as at 31 December rather than the position on the day of submission.
The option “Assessment not performed” is permitted in several closed lists. For the question on alternatives in B_07.01.0110, however, Annex I sets an obligation: “For each ICT third-party service provider supporting a critical or important function, the assessment to identify an alternative service provider shall be performed.” If that assessment is missing at the reference date, the register shows a gap that the Regulation itself defines as an obligation.
The contract fields mirror Article 30(2) DORA: the locations where services are provided and data is processed, including the storage location (point (b)), and termination rights and minimum notice periods (point (h)). Where these details are missing from the register, they are often missing from the contract already. The contract side is covered in DORA Article 30 for IT service providers.
| Column | Requirement in Annex I, Regulation (EU) 2024/2956 | Check by 31 Dec 2026 |
|---|---|---|
| B_02.01.0050 | Annual expense or estimated cost “for the past year”, reported in units | Is the data source for 2026 defined for each arrangement, without double counting between overarching and subsequent arrangements? |
| B_02.02.0080 | End date; indefinite “9999-12-31”; if terminated, the termination date; if renewal is foreseen, the renewal date | Have 2026 renewals and terminations been recorded? |
| B_02.02.0090 | Reason for termination or ending from a closed list | Is a reason recorded for each ended arrangement? |
| B_02.02.0100 / 0110 | Notice periods for both parties in calendar days; mandatory for critical or important functions | Do the periods match the current contract? |
| B_02.02.0140 to 0160 | Storage of data, storage location and processing location as ISO 3166 country code, one row per country | Have location changes during the year been captured? |
| B_06.01.0060 / 0080 | Criticality Yes, No or “Assessment not performed”; date of last assessment, “9999-12-31” if none | Has every function been assessed and the date documented? |
| B_06.01.0090 / 0100 | RTO and RPO in hours; below one hour “1”, not defined “0” | Are the values aligned with business continuity management? |
| B_07.01.0050 / 0080 / 0110 | Substitutability on four levels, exit plan Yes/No, alternative providers | Is the assessment of alternatives in place for each provider supporting a critical or important function? |
LEI and EUID: Identifying Providers
Article 3(5) of the Implementing Regulation requires a “valid and active” legal entity identifier (LEI) or the European Unique Identifier (EUID) under Article 16 of Directive (EU) 2017/1132, and both where available, for all ICT third-party service providers that are legal persons. Individuals acting in a business capacity are exempt. For subcontractors supporting critical or important functions, financial entities ensure the identifiers through the direct provider (Article 3(6)).
BaFin’s FAQ add that financial entities obtain the identifiers from the providers themselves. There will be no dummy LEI for smaller providers, as a fictitious LEI would defeat the purpose of unique identification. Where the provider is a natural person, it can be identified by commercial register number, VAT identification number, passport number or identity card number.
From the 2026 cycle, BaFin reports type 705 error messages after corrected registers were uploaded again. The cause was amended LEIs where the dependencies in the data model had not been observed; BaFin points out that the LEIs of providers and subcontractors must be included in table 05.02. Requesting missing identifiers from providers is therefore work for the weeks before the reference date, not for the submission window.
Data Quality: Validation and ESA Feedback
Article 3(3) of the Implementing Regulation requires accurate and consistent information, regular review and prompt correction of any errors or discrepancies detected. Article 3(4) sets six data quality principles: accuracy, completeness, consistency, integrity, uniformity and validity.
Validation runs in two stages. Submitted registers are validated first by BaFin and then by the ESAs, which can take up to 48 hours. According to BaFin, the reporting obligation is only properly met once the ESAs have validated the register. The ESAs then check data quality by comparing the information reported by many financial entities on identical facts. In 2026 they provided this feedback for the first time, in early April and for around 90 per cent of the registers submitted to BaFin.
A finding in the data quality feedback is not automatically an error. The ESAs assume that information reported by the majority is correct, which, as BaFin notes, need not necessarily be the case. An entity that stands by its data after review keeps its entries and documents the deviation internally, for example with a screenshot of the GLEIF record.
For completing the register, BaFin refers to the ESA validation rules, its filling-in guidance, a sample completed Excel template and an overview of possible error codes. According to BaFin, test submissions are possible at any time via the “TEST: Digital Operational Resilience Act (DORA)” procedure.
Submission in 2027: Channel, Format and What Is Still Open
Registers are submitted exclusively via BaFin’s reporting and publication platform (MVP), either as an xBRL file following the ESA taxonomy or using BaFin’s Excel template. BaFin analyses the data, among other things for concentration risks, and forwards the registers to the ESAs, which use them to designate critical ICT third-party service providers each year.
There is no grace period. According to BaFin’s FAQ, submission after the deadline is no longer possible for the current cycle, and the register is then deemed not submitted or not correctly submitted. BaFin does not accept registers sent by email, even after the deadline. Because rejected registers must be corrected and uploaded again as a new report before the deadline, planning needs a buffer before the window closes.
As at 30 October 2026, the opening and closing dates of the 2027 window have not been published. The framework is documented: position as at 31 December 2026, completion by 31 March 2027 at the latest, and an announcement of the opening date at the start of the year. The wider set of obligations beyond DORA is mapped in the EU regulation overview; the state of supervision is described in DORA regulation 2026.
Between Reference Dates: Updating and Notifying
The register is not a once-a-year document. According to BaFin’s FAQ, changes to contractual arrangements for ICT services in use must be entered promptly. During the year, financial entities submit the updated register only when requested; otherwise it follows in the next annual cycle.
Separate from this is the duty to inform under the fifth subparagraph of Article 28(3) DORA: planned arrangements for ICT services supporting critical or important functions, and a function becoming critical or important, must be notified to the authority in a timely manner. Where this overlaps with sectoral outsourcing notifications under the KWG, VAG or KAGB, notification continues via the MVP procedure for outsourcing notifications; where there is no overlap, BaFin’s Excel form is sent to the supervisor by email. BaFin derives the number of new arrangements (third subparagraph) from the submitted registers, so no separate report is required.
Work Plan to 31 December 2026
From 30 October 2026, there are 62 calendar days left until the reference date. The sequence follows from the dependencies between the templates: without a function assessment the scope is unclear, without the scope the subcontractors are missing, and without valid identifiers validation fails.
The [ICT third-party register](/templates/ict-third-party-register) is available as a working template for single entities. It covers templates B_01.01, B_02.01/B_02.02, B_05.01, B_05.02, B_06.01 and B_07.01 and exports the columns with their RoI codes. The export is not a submission: BaFin only accepts xBRL or its own Excel template via the MVP. Scope of consolidation, branches and intra-group links (B_01.02, B_01.03, B_02.03) are not included. For assessing individual providers, the [vendor assessment](/templates/vendor-assessment) can be used.
- Reconcile the contract inventory: compare ICT service contracts held by procurement, legal and business units with the 2026 register; add new arrangements, renewals and terminations from the year (B_02.01, B_02.02).
- Assess functions: record criticality, date of assessment, RTO and RPO for each function (B_06.01).
- Complete the supply chains: for critical or important functions, record subcontractors with their rank (B_05.02); for intra-group providers, at least the first external subcontractor.
- Collect identifiers: request the LEI or EUID of all providers and relevant subcontractors and check that they are valid.
- Update the B_07.01 assessments: substitutability, last audit, exit plan, reintegration and alternatives.
- Define the cost basis: determine the source for 2026 expenses per arrangement (B_02.01.0050).
- Dry run: after the reference date, use a test submission via the “TEST” procedure and apply the ESA validation rules before the window opens.
What ICT Service Providers Contribute by the Reference Date
According to BaFin’s FAQ, DORA applies only to financial entities; ICT third-party service providers are affected indirectly through contract design. For the register, financial entities mainly need from their providers their own LEI or EUID, the subcontractors and their identifiers where critical or important functions are supported, the locations of service provision and data, and the contractual notice periods.
Providers that make this information available in a structured form before year-end make it easier for their financial clients to reconcile at the reference date. As the ESAs use the registers for the annual designation of critical ICT third-party service providers, this information matters beyond the individual client. Contract requirements from the provider’s perspective are covered in DORA Article 30 for IT service providers, and the distinction from NIS2 in DORA vs NIS2.
Sources and Status
This article reflects the position as at 30 October 2026; all sources were retrieved on that date. It is intended for orientation and does not replace legal advice; the text published in the Official Journal prevails.
- [Regulation (EU) 2022/2554 (DORA), OJ L 333, 27.12.2022, p. 1](https://eur-lex.europa.eu/eli/reg/2022/2554/oj) (2022): Article 3(19), (21), (22); Article 28(3) and (9); Article 30(2); Article 64
- [Commission Implementing Regulation (EU) 2024/2956 of 29 November 2024, OJ L, 2.12.2024](https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj) (2024): Articles 1 to 7, Annex I
- [BaFin, Informationsregister und Anzeigepflichten](https://www.bafin.de/DE/unternehmen-maerkte/aufsicht/alle-unternehmen/it-cybersicherheit/register-anzeigepflichten/register-anzeigepflichten_node.html) (2026, German): submission cycle, MVP, key content, further notification duties
- [BaFin, FAQs zu DORA](https://www.bafin.de/SharedDocs/Fragen-antworten/DE/faq-dora/faq-dora_node.html) (2026, German): sections on scope, ICT third-party risk management and the register of information
- [BaFin, Einreichungsperiode der Informationsregister 2026, retrieved via a BVI mirror](https://direkt.bvi.de/fileadmin/user_upload/letter/2026/Information_Einreichungsperiode_Informationsregister_2026.pdf) (2026, German): points 1 to 4 (format, reference date 31.12.2025, window 9 to 30 March 2026, test procedure)
Key Takeaways
- According to BaFin, the register for the 2027 submission must reflect the position as at 31 December 2026; submission must be completed without errors by 31 March 2027 at the latest.
- The reference date and deadline are BaFin supervisory practice; Article 28(3) DORA requires at least yearly reporting and provision of the register on request.
- Form and content are set by Implementing Regulation (EU) 2024/2956: templates B_01.01 to B_99.01, one value per data point, six data quality principles.
- Direct providers (rank 1) always belong in the register; subcontractors where critical or important functions are supported; for intra-group providers, at least the first external subcontractor.
- Every provider that is a legal person needs a valid LEI or EUID; there is no dummy LEI.
- The 2027 submission window had not been published by 30 October 2026; in 2026 it closed on 30 March.
Frequently Asked Questions
31 December 2026. According to BaFin, the register must reflect the position as at 31 December of the previous year. Contracts, assessments and identifiers should therefore be complete at year-end; later corrections must also reflect the position on that date.
No. Article 28(3) DORA requires at least yearly reporting and making the register available on the authority’s request. The 31 December reference date and the 31 March deadline are set by BaFin, which bases its annual request on the fourth subparagraph of Article 28(3). Other supervisory authorities may set different dates.
According to BaFin, by 31 March 2027 at the latest, completed in full and without errors, including validation by the ESAs. BaFin announces the specific window at the start of the year; as at 30 October 2026 it has not been published. In 2026 it ran from 9 to 30 March.
Yes, for ICT services supporting critical or important functions: all subcontractors ensuring the service (Article 3(2)(b), Implementing Regulation (EU) 2024/2956). Otherwise the direct provider (rank 1) is sufficient. For intra-group providers, BaFin requires at least the first subcontractor outside the group.
Legal persons must be identified by LEI or EUID, and by both where available (Article 3(5)). BaFin does not accept a dummy LEI. Individuals acting in a business capacity are exempt; according to BaFin they can be identified by commercial register, VAT identification, passport or identity card number.
No. According to BaFin’s FAQ, this is no longer possible for the current cycle, and the register is deemed not submitted or not correctly submitted. BaFin does not accept submissions by email either. The next submission is only possible in the following regular cycle.