Your DORA register, checked the way the ESAs check it.
Upload the xBRL-CSV report package and get back every finding the EBA's reception, data-point and business checks would raise, on the exact row and column, with the fix. Before the portal, not after the rejection email.
Why files get rejected
In the 2025 collection the top rejections were 807 (a reference to a row that does not exist), 805 (empty key), 808 (a template not declared true), 720 (a table file with the wrong name or case) and 714 (entityID not matching the filename). None of them is about the content of your register. All of them are visible before you upload.
What the portal does not tell you
National portals run their own checks first and hand the file to the ESAs afterwards. In 2026 a significant number of files that Irish and Luxembourg portals accepted still failed the ESAs' data-quality layer and had to be resubmitted in April. The validator runs both layers.
When the file is wrong on purpose
Some findings are warnings because the ITS says so: a parent LEI equal to the entity's own, a template left empty, a 9999-12-31 deletion date. The validator tells you which ones the ESAs will record and which ones reject the file, so you can decide.
Pricing
The validator is free, without an account, for as many files as you need. Paid plans add the parts that take a compliance officer's week: packaging for your regulator, carry-forward from last year's accepted file, and a human who has filed before.
Validate
Free
- All four layers of checks
- Row and column for every finding, with the fix
- No account, nothing stored
File
€450 per entity, per reporting year
- Everything in Validate
- Package built for your regulator: filename, folder, encoding, wrapper
- Carry-forward: last year's accepted register in, this year's changes out
- LEI status checked live against GLEIF before you submit
- Audit trail of every version and every check
Rescue
€400 one-off, 2 business days
- Your rejected file and the feedback zip in, an accepted file out
- A written note of what was wrong and why, for the file
- By a senior engineer who has run regulated production systems for fifteen years