DORA Register of Information: templates, build guide and data model

What this solves

The Register of Information is the one DORA deliverable with a hard annual date and a machine-readable format. It is not a document you write: it is a dataset you assemble, from contracts, from the CMDB and from people who do not think of themselves as data owners.

The first attempt is nearly always a spreadsheet that looks right and fails validation, because the coded fields take controlled vocabularies and the entities have to reference each other consistently.

What is inside

• Master Excel workbook: the 15 templates of ITS 2024/2956, B_01.01 to B_99.01
• EBA taxonomy column codes, and the 23 closed lists as dropdowns
• Row checks: ITS fill-in rules, the 49 active EBA validation rules, LEI check digits, 24 cross-template references
• Worked example: a fictitious banking group across all 15 templates
• Build guide PDF, 31 pages, column by column
• JSON Schema (draft-07) and SQL DDL for GRC or data-warehouse import
• ICT service types S01 to S19 (ITS Annex III) and total assets by entity type (Annex IV)

What it covers in the regulation

• Article 28(3): maintaining a register of information
• ITS (EU) 2024/2956: the 15 register templates
• ITS Annex III: the ICT service types S01 to S19
• EBA taxonomy and validation rules for the DORA module

Who uses it, and when

Whoever has been handed the register, often vendor management, sometimes data or architecture. Used from the first data collection right through to submission.

How to work through it

1. Map each ITS template to the system or team that already holds the data.
2. Load the data model so relationships between entities, contracts and services are right from the start.
3. Fill the coded fields from the controlled vocabularies, not free text.
4. Validate before the deadline, not on it.

Related