Skip to content

Register of Information glossary

The vocabulary of Register of Information reporting is split across several documents, and a term that means one thing in your workbook is often written another way in the feedback you get back. These are the terms this validator uses, defined once. Where a definition rests on a published document, the source is linked beneath it.

Register of InformationRoI
The structured record a financial entity keeps of its contractual arrangements for the use of ICT services provided by third-party providers, and reports to its supervisory authority. It is not a document written in prose: it is a set of tabular templates with defined fields, identifiers and closed-set values, which is why it can be validated mechanically at all.
ITS (EU) 2024/2956the Implementing Regulation
The implementing technical standard that lays down the templates and the reporting format for the Register of Information. It is the document this validator is built against: the template structure, the field list and the reportable forms all come from it and from the EBA material published alongside it.
RT templatesRT.01.01 … RT.07.01
The reporting templates that make up the register. Each one is a sheet in the workbook, named for its code, and each holds a defined set of fields. RT.99.01 is the odd one out: it is an options legend listing permitted values, not a template you report. The table further down this page lists every template this validator knows, generated from the specification rather than typed by hand.The ESA reporting template carries 14 reporting templates, RT.01.01 to RT.07.01, plus RT.99.01, which is an options legend rather than a reportable template.
Data Point ModelDPM
The EBA’s data model, and the notation its systems speak. Every RT template has a DPM counterpart written B_xx.xx, and every column has a code written c0010, c0020 and so on. You look at RT.05.01; the feedback you receive says B_05.01 c0010. They are the same place. Every finding this validator reports prints both, so you never have to translate between them.
xBRL-CSV reporting package
The form a submission actually takes: not a spreadsheet, but a ZIP archive laid out to a defined structure, containing the register as CSV files plus the metadata that tells the receiving system how to read them. Producing one is a packaging step, separate from getting the content right, and a register can be perfectly correct and still fail because the package is not.A submission is an xBRL-CSV reporting package following Report Package 1.0, containing META-INF/reportPackage.json and a reports folder. Source
UTF-8
The character encoding a reporting package must use. This matters more than it sounds: an accented entity name or a non-breaking space saved from a spreadsheet in a legacy encoding is a common way for a package that looks right on screen to be rejected on arrival.Reports must use UTF-8 encoding. Source
Closed setsdrop-down values, eba_ prefix
Many fields accept only a value drawn from a fixed published list — a country, a currency, a type of arrangement. Those values have to be written in the coded form the taxonomy expects rather than in the words a reader would use, which is why a register that reads correctly to a person can still be wrong to a machine.Values drawn from a closed set must be written with the eba_ prefix, for example eba_CT:x12. Source
Legal Entity IdentifierLEI
A 20-character code identifying a legal entity, defined by ISO 17442: eighteen alphanumeric characters followed by two check digits. The check digits are computed from the rest of the code with the MOD 97-10 algorithm, so a mistyped LEI can usually be detected offline, without asking anyone whether the code exists. That is exactly what this validator does.
GLEIF
The Global Legal Entity Identifier Foundation, which operates the database of issued LEIs. This is the boundary of what an offline tool can tell you: a check digit proves a code is well formed, not that it was ever issued, nor that it is still active. A structurally valid LEI that is not in the database will pass here and can still be rejected.Several published checks require an LEI to be valid according to the GLEIF database, which no offline tool can establish. Source
EUIDdefinition pending verification
The European Unique Identifier, which appears alongside the LEI in the identifier checks published by the EBA. Its full definition and validation rules are not yet grounded in the specification documents held in this repository, so no rule here validates it and no definition is asserted beyond that.
Validation rules
The published checks a register is tested against before it is accepted, spanning file-level technical checks, model-level checks, business rules about the content, and identifier checks. This validator implements a subset of them and states which; a clean result here means the checks that ran found nothing, not that a submission will be accepted.The EBA publishes 120 checks for Register of Information reporting, in four categories: technical checks, DPM technical checks, DPM business validation rules, and LEI/EUID checks. Source
Blocking and warning
How this tool grades what it finds. Blocking means the value is wrong on its own terms — an identifier that fails its check digit, a mandatory field left empty. Warning means something that merits a look but may be legitimate. These are this validator’s words for its own findings, not a regulator’s classification, and every finding shows the rule and the source behind it.
ICT third-party service provider
The counterparty whose services a financial entity records in the register — the supplier side of the arrangement. Much of the register exists to describe who they are, what they provide, and how the arrangement is structured, which is why identifiers and closed-set classifications carry so much of the content.
Competent authorityNCA
The national supervisory authority a financial entity submits its register to. Which authority, in what window and through which channel, depends on the entity and the Member State; those are questions for the authority itself, and this site does not answer them on its behalf.

Template reference

Every reporting template this validator recognises, with the DPM code the same template is called in validation feedback. Generated from the specification, so it cannot drift from what the tool actually reads.

TemplateDPM codeFields
RT.01.01B_01.016
RT.01.02B_01.0211
RT.01.03B_01.034
RT.02.01B_02.015
RT.02.02B_02.0218
RT.02.03B_02.032
RT.03.01B_03.012
RT.03.02B_03.023
RT.03.03B_03.032
RT.04.01B_04.014
RT.05.01B_05.019
RT.05.02B_05.027
RT.06.01B_06.0110
RT.07.01B_07.0112
DORA Validation

DORA Validation is an independent tool. It is not endorsed by, affiliated with, or approved by any supervisory authority.