Register of Information
DORA register of information template / model
Operating model to maintain the DORA register: referentials, stable keys, mapping to the 13 templates, quality checks and update cadence.
A useful DORA register “template” is not a frozen Excel file that mimics the 13 CSVs. It is an operating model: which sources feed which templates, who validates what, how keys stay stable, and how you produce the xBRL-CSV package without rebuilding everything every year.
Regulatory structure: Implementing Regulation (EU) 2024/2956 (templates B_01.01 → B_99.01). Full map: pillar guide.
Principle: two layers
| Layer | Role |
|---|---|
| Living business layer | Internal referentials: entity, functions, providers, contracts, chains, assessments |
| Regulatory export layer | Mapping to the 13 templates + ZIP generation at a reference date |
If you only maintain the export layer, you start from scratch every campaign. If you maintain the business layer with stable keys, export becomes mechanical.
Freeze the four keys on day one
- Arrangement reference number — unique, stable, never reused for another contract
- Entity LEI (and LEIs of using/signing entities in a group)
- Provider code (LEI/EUID per rules) + code type
- Function ID
F1…Fn— unique for (LEI + licensed activity + function name)
These keys appear across almost every template. Changing them mid-flight breaks B_02.02, B_05.02 and B_07.01 at once.
Minimum working model
A. Reporting-entity sheet → B_01.01
LEI, name, country, EBA entity type, competent authority
B. Functions referential → B_06.01
Licensed activity, internal name, criticality, assessment date, RTO/RPO (hours), disruption impact — drives conditional fields in B_02.02
C. Providers referential → B_05.01
Identity, person type, country, ultimate parent, annual spend
D. Arrangements referential → B_02.01, B_03.*, B_04.01
Type (standalone / overarching / subsequent), link to framework, currency, annual cost, dates, signers, users
E. Arrangement × function × service matrix → B_02.02
ICT service type (S01–S19), location, notice, sensitivity, dependency — by criticality
F. Chains & assessments (critical scope) → B_05.02, B_07.01
Subcontracting by rank; substitutability; audit; exit plan; reintegration
G. Internal terminology (optional) → B_99.01
Local definitions of closed-list options
Quality checks before export
- Existence — no empty mandatories on submitted templates
- Conditionals — framework ↔ subsequent; amount ↔ currency; non-substitutable ↔ reason; critical function ↔ location/notice block
- Row completeness — no half-filled rows
- Format — LEI,
eba_codes,yyyy-mm-dddates, monetary amounts in units - Key coherence — every provider code in B_02.02 / B_05.02 exists in B_05.01; every function in B_02.02 exists in B_06.01
- FilingIndicators — one true/false entry per template, including empty ones
Packaging detail: XBRL-CSV format. Field detail: mandatory fields.
Recommended maintenance cadence
| Event | Update |
|---|---|
| New provider / contract | B_05.01, B_02.01, B_02.02, signers/users |
| Amendment / cost change | B_02.01 (and linked subsequent arrangements) |
| New function or criticality reclass | B_06.01 then review conditional B_02.02 rows |
| Subcontracting change | B_05.02 (+ B_05.01 if new node) |
| Audit / exit plan | B_07.01 |
| Quarterly review | Quality checks + LEI / ultimate parents |
| Filing campaign | Lock reference date → generate ZIP → homologate → deposit |
What not to do
- Keep a parallel “register Excel” without stable arrangement numbers
- Wait until filing week to invent functions and criticality
- Confuse a vendor certificate with “date of last audit” (B_07.01)
- Export from Excel and hope for a valid xBRL-CSV
- Treat B_05.02 (chains) as optional when critical functions sit on cascaded cloud
Cluster links
Axenia’s role. Axenia materializes this living business layer — arrangements, third parties, functions, dependencies, assessments — and derives register exports from it, so the “template” is no longer an annual file but a maintained framework.
Operating model inspired by the structure of Implementing Regulation (EU) 2024/2956. Adapt it to your governance and your authority’s instructions. Not legal advice.