Package checks: FilingIndicators.csv, parameters.csv and tables

After reception, the EBA reads the files in the package. These checks confirm that FilingIndicators.csv, parameters.csv and the table files have the shape the EBA expects (EBA (opens in a new tab)). They check the package's structure, not the content of your register.

What the EBA expects

File	Expectation
FilingIndicators.csv	Each template once, with a value true or 1; template IDs in capitals (EBA common issues (opens in a new tab)).
parameters.csv	A header row of exactly name and value, in that order (EBA Filing Rules (opens in a new tab), EBA common issues (opens in a new tab)).
Table files	Only column headers defined in the taxonomy, none twice. The column order may differ (EBA common issues (opens in a new tab)).

The package errors the AFM sees often have their own page: 701, 702, 714, 720, 807 and 808. So do 805 and 809.

Does DORA Convert catch these checks?

Largely. DORA Convert writes these files itself and checks the built package before you can download it: the structure of FilingIndicators.csv and parameters.csv, whether there is data to process, and every table's column headers against the official taxonomy. If a check fails, we don't offer the package.

Codes 803 and 804 concern row identifiers in closed tables. We don't run those beforehand.

Below is every package check with its official description.