DORA · Register of Information (RoI)
Validate your DORA Register of Information before you file it.
Drop in the RoI report package you are about to submit. The validator opens it here, in your browser, and checks it against the fifteen EBA templates. You get a count.
Validation rules last updated 5 August 2026
The xBRL-CSV RoI package your reporting tool produces.
Personal mailboxes are not accepted.
Templates read
- B_01.01
- B_01.02
- B_01.03
- B_02.01
- B_02.02
- B_02.03
- B_03.01
- B_03.02
- B_03.03
- B_04.01
- B_05.01
- B_05.02
- B_06.01
- B_07.01
- B_99.01
Stop finding them. Stop having them.
Our DORA register solution is a single Excel workbook. It validates every field as you type, checks LEIs against GLEIF, enforces the references between templates, and exports a submission-ready package for your authority.
Under €1,000 a year.
What leaves your browser
Your RoI is opened and validated here, on your own machine. The file is never uploaded — none of its contents reach Fund-XP: no provider names, no contract references, no figures.
Three things are sent to us when you run a check: the email address you enter, the name of the file you select, and the number of problems the check found. File names in this submission format normally start with your LEI, so treat the name as identifying your entity.
Checking LEIs against the public GLEIF database sends those LEIs to gleif.org. They are public identifiers.
What the validator checks
More than 200 validation rules, across the fifteen EBA templates.
The figure you get back is far higher, because every rule runs once per row: a register with a few hundred contracts executes several thousand individual checks.
Package structure
The two JSON manifests, the reporting parameters, the filing indicators, and whether every template declared as reported is actually present.
Column layout
Each template against its expected columns, including the extra column Italy, Luxembourg and Romania require on B_02.03, B_03.01 and B_03.03.
Codes and identifiers
Every closed-list value against the EBA taxonomy, LEI check digits under ISO 17442, and EUID patterns for each national business register.
References between templates
Contract reference numbers, provider identification codes, function identifiers and branch codes, each traced to the template that is meant to define it.
Supply chains
Whether each rank in B_05.02 connects to the rank above it for the same contract and service, and whether direct providers are reported as such.
Live GLEIF status
Whether each LEI exists, is still issued rather than lapsed, sits in the country you declared, and reports the ultimate parent you reported.
Questions
What is the DORA Register of Information (RoI)?
Under the Digital Operational Resilience Act, every financial entity in the EU maintains a Register of Information — the RoI — listing its contractual arrangements for ICT services, and reports it to its competent authority each year. It spans fifteen templates, B_01.01 through B_99.01, covering entities in scope, contracts, ICT third-party service providers, supply chains, and the functions those services support.
What file does the validator accept?
The xBRL-CSV report package you submit to your regulator: a zip holding META-INF/reportPackage.json, reports/report.json, parameters.csv, FilingIndicators.csv and one CSV per template.
Why does the validator only give a number?
The free validator tells you whether your RoI is clean, and how much work it needs if it is not. Locating each problem, explaining it, and stopping it recurring next year is what the solution does.
Does a clean result mean my RoI filing will be accepted?
It means it passes the validation rules we run, which are the ones our own clients' registers pass. Your authority may apply further rules of its own.
Reference
The rules this validator applies come from the European Banking Authority. Its page on preparing for the DORA application carries the reporting templates, the taxonomy and the filing guidance for the Register of Information.