The 15 templates of the DORA Register of Information
The Register of Information isn't a single table, but 15 templates linked together. Understanding that structure — and above all the links between templates — is understanding where your register risks rejection.
In short — The DORA Register of Information has 15 templates (B_01.01 to B_99.01) across 8 groups, defined by Commission Implementing Regulation (EU) 2024/2956. They are linked by foreign keys, with B_02.01 (the arrangements) as the hub. It's the consistency between these templates that decides acceptance at submission.
15 templates, 8 groups
The structure of the Register of Information is set by Commission Implementing Regulation (EU) 2024/2956. It is made of 15 templates (the B_xx.xx tables) organised into 8 thematic groups. Each template covers one aspect of your arrangements with ICT third-party service providers: who keeps the register, which contracts, which signatories, which providers, which functions, and their assessment.
A register isn't read template by template. It stands — or falls — on the consistency of the whole.
The list of the 15 templates
1 · Entity information
B_01.01 Entity maintaining the register (and reporting date).B_01.02 List of entities within the scope of consolidation.B_01.03 List of branches.2 · Contractual arrangements
B_02.01 Arrangements — general information (the hub of the register).B_02.02 Arrangements — specific information (services, functions, terms).B_02.03 Intra-group arrangements (linked to related external contracts).3 · Signatories
B_03.01 Financial entities signing the arrangements.B_03.02 ICT third-party providers signing the arrangements.B_03.03 Financial entities providing ICT services (intra-group).4 · Service usage
B_04.01 Entities making use of the ICT services under each arrangement.5 · ICT providers
B_05.01 ICT third-party service providers (identification and details).B_05.02 ICT service supply chain (subcontracting, hierarchy).6 · Functions
B_06.01 Identification of functions supported by the ICT services.7 · Assessments
B_07.01 Assessment of ICT services supporting critical or important functions.8 · Definitions
B_99.01 Entity-specific definitions and closed-list values.The real trap: links between templates
The 15 templates aren't independent: they are linked by foreign keys. A value entered in one template must reference an existing record in another. The heart of the system is B_02.01: each arrangement gets a unique reference there, then reused almost everywhere.
B_02.02,B_03.01,B_03.02,B_03.03,B_04.01,B_05.02andB_07.01point to an arrangement reference inB_02.01;B_02.02,B_03.02andB_05.02point to a provider code inB_05.01;B_02.02andB_07.01point to a function identifier inB_06.01;B_03.03andB_04.01point to an entity LEI inB_01.02.
In other words: a template can be perfectly filled and still break the whole register if it references an arrangement, provider or function that exists nowhere else.
Common consistency errors
- a provider code used in
B_02.02but missing fromB_05.01; - an orphan arrangement reference (present in
B_04.01, never declared inB_02.01); - a function identifier in
B_07.01matching no row inB_06.01; - an invalid LEI, or one inconsistent between
B_01.02and the templates that reference it; - non-UTF-8 encoding or a non-ISO date format that breaks the xBRL-CSV parsing.
Check cross-template consistency before you submit
DoraReady checks that every arrangement reference, provider code and function identifier points to an existing record, among the EBA's 116 validation rules, and generates the xBRL-CSV package. Everything runs in your browser: your data never leaves your machine.
Run the free diagnosticFrequently asked questions
How many templates are there?
B_xx.xx) across 8 groups, defined by Commission Implementing Regulation (EU) 2024/2956.Which is the central template?
B_02.01 (arrangements — general information): each arrangement gets a unique reference there, reused as a foreign key by most of the others.