DPM technical checks: values and keys
The DPM technical checks confirm that every value fits the EBA's Data Point Model (DPM): the right type, the right format and a valid code. They are a separate step in the EBA's validation (EBA explainer (opens in a new tab), EBA (opens in a new tab)).
What usually lies behind them in the workbook
| Kind of value | What the EBA expects | In the Excel workbook |
|---|---|---|
| Date | yyyy-mm-dd |
Enter a real date, not text such as "31-12-2025". |
| Integer or amount | A number, not text | No units or currency signs in the cell. |
| Boolean | true, false, 1 or 0 |
Enter true or false. Some yes/no fields are not booleans but drop-downs; choose from the list there. |
| Drop-down | The DPM code with the eba_ prefix, such as eba_GA:NL |
Choose from the drop-down. The readable ITS text is replaced by the code for reporting (EBA FAQ, question 25 (opens in a new tab)). |
| Key | No two rows with the same key values (code 806) | Look for duplicate rows, such as a contract pasted twice. |
The EBA publishes every allowed drop-down code in one workbook (EBA (opens in a new tab)).
A few DPM checks concern the package itself: 505 (report.json points to the module entry point), 510 (template IDs in FilingIndicators.csv), 512 (the taxonomy used) and 514 (the reporting entity).
Does DORA Convert catch these checks?
Yes, all twelve. The checks on values and keys run on your workbook, row by row and column by column, with an error on the cell. The package checks run on the built package before you can download it.
The DPM business rules (codes such as e23674_e or v8826_m) are not on this page but with the template they belong to.
Below is every DPM technical check with its official description.
Codes and official descriptions
Numeric fact must not be reported with a string value.
Reference date inside an instance as well as within filename must be valid.
Date-type metric must be reported with format yyyy-mm-dd.
Integer-type metric must be reported with an integer.
Boolean-type metric must be reported with a boolean value (true/false/1/0).
trueItemType must be reported with true value.
Extensible main property and explicit key dimension must be reported only with one of the restricted values of a hierarchy.
Each report must contain a report.json, and it must point to the module entrypoint JSON file.
Filing-indicator values must be those given by the filing-indicator label resources / DPM TemplateCode field.
The module referenced by the instance document must not refer to a taxonomy having FromDate = ToDate.
Reporting subject must include entity type with . qualifier if the reference date is on or after 2022-12-31 and the module code does not contain CON or IND.
For open tables, multiple rows with identical key values are not allowed.
From the EBA's published catalogue, as recorded on 10 March 2026. The official text is in English.
Sources
- EBA: Overview of the RoI reporting technical checks and validation rules (28 April 2025) (opens in a new tab)
- EBA: DORA RoI reporting FAQ (28 March 2025, PDF) (opens in a new tab)
- EBA: List of possible values for all data fields with drop downs (3 March 2025) (opens in a new tab)
- EBA: RoI validation feedback explanation (10 February 2025, PDF) (opens in a new tab)