Resources › Guide

5 mistakes that get a DORA register rejected

Most first submissions of the DORA Register of Information fail for the same handful of reasons. Each is invisible in Excel and fatal at the authority's quality gate. Here are the five to watch, and how to catch them before you file.

1. Invalid or missing LEIs

Legal Entity Identifiers must be valid ISO 17442 codes and actually exist in the GLEIF register. A typo, a lapsed LEI, or a blank where one is required will fail. Fix: validate every LEI's format and existence up front.

2. Incomplete critical-function (CIF) data

When a function is assessed as critical or important, DORA requires a cascade of additional fields on the linked contracts and providers. Miss one and the row breaks. Fix: let criticality propagate automatically and flag the fields it makes mandatory.

3. Values outside the closed lists

Many columns only accept codes from the ESA taxonomy's closed lists (country, currency, service type…). A free-text value, or the wrong code, is rejected. Fix: pick from taxonomy-backed dropdowns, never type raw values.

4. Broken referential integrity

The 15 templates are interlinked: a contract points to a provider, a provider to its supply chain. A dangling reference (a contract citing a provider that isn't listed) fails cross-table checks. Fix: enforce the links as you build, not after.

5. Wrong format or taxonomy version

Even perfect data fails if the package isn't valid xBRL-CSV for the taxonomy in force, wrong column codes, wrong file names, wrong version. Fix: generate the package automatically against the current taxonomy.

The common thread

You can't eyeball these in a spreadsheet. The only reliable defence is to replay the regulators' checks before submission and correct every flag first. That's what Obligia does end to end.

Validate my register   Book a demo ›

General information, not regulatory advice; responsibility for submission remains with the entity.