Every checkpoint to run through before you file your DORA Register of Information — organised by template, cross-table consistency, LEI, DPM values and the final xBRL-CSV package.
In short — Before you submit your DORA Register of Information, verify each template is complete, that every arrangement reference, provider code and function identifier resolves across templates, that every LEI is valid and ISSUED on GLEIF, that closed-list fields use the correct DPM codes, and that the file is a correctly structured xBRL-CSV package.
This checklist assumes you already have a draft register. If you're still populating it, start with how to fill in the DORA Register of Information — then come back here for the pre-submission pass.
The register is built from 15 templates across 8 groups. Work through each group before moving to the cross-table checks — a template that's individually correct can still be incomplete.
Entity information (B_01.xx)
Contractual arrangements (B_02.xx)
Signatories, usage & providers (B_03–B_05)
Functions & assessments (B_06–B_07)
Definitions (B_99.01)
Cross-table consistency
Most rejections don't come from one wrong field — they come from a reference that exists in one template and nowhere else. See why registers get rejected for the detail behind each of these.
Consistency checks
A register can be correct table by table and still fail as a whole.
LEI checklist
Every reporting entity and every ICT third-party provider needs a Legal Entity Identifier. See the LEI and GLEIF guide for how to look one up.
LEI checks
DPM values checklist
Several fields only accept a fixed code from the EBA's Data Point Model dictionary — not free text. See DPM values in the register for the reference list.
DPM checks
Package checklist
The final output isn't an Excel file — it's an xBRL-CSV package built to the EBA taxonomy, and the packaging itself has its own failure modes.
Package checks
Run every check automatically
DoraReady checks your register against the EBA's 116 validation rules, flags exactly which line would fail and why, then generates the xBRL-CSV package. Everything runs in your browser: your data never leaves your machine.
That every template is complete, that arrangement references, provider codes and function identifiers resolve across templates, that every LEI is valid and ISSUED on GLEIF, that closed-list fields use the correct DPM codes, and that the file is a correctly structured xBRL-CSV package.
Does this checklist guarantee my register will be accepted?
No. It reduces the risk of technical rejection; it is not a guarantee of acceptance by the authority. At the EU dry run in 2024, only 6.5% (ESAs, 2024) of registers passed first time.
What's the single most commonly missed check?
Cross-table consistency: a template can be filled in correctly on its own and still break the register if a reference doesn't exist in the template that defines it.
Do I need to check templates that are empty for my entity?
Yes. Every mandatory template must be included in the package, even with no rows, or the submission can be rejected on structure alone.
The exact filing date is an annual obligation — verify the precise deadline with your competent authority (in France, the AMF or ACPR via OneGate).