Error codes · EBA technical checks (reception)
720: Valid table names must be used as .csv filenames
Rejects the file also shown as EBA.720
Official text
Valid table names must be used as .csv filenames
How it appears in feedback
[LEI].[IND/CON],,,720, Extra files found in the submission: [filename]
What triggers it
Something in reports/ is not one of the expected names: an .xlsx left in the folder, a misspelled or upper-case table name (B_01.01.csv instead of b_01.01.csv), hidden folders/files created by the zip tool (e.g. __MACOSX, .DS_Store, Thumbs.db). Since the May 2025 simplification, MISSING table files are tolerated and lower-case names accepted; extra or upper-case files are still rejected.
A CSV file in reports/ is not one of the DORA table names, or is not in lower case.
Templates: reports/ folder
How to fix it
Only b_01.01.csv ... b_99.01.csv (lower case), report.json, parameters.csv, FilingIndicators.csv in reports/. Zip from a clean folder; inspect the archive listing before upload.
Files must be b_01.01.csv … b_99.01.csv, all lower case. Upper-case names are rejected; missing or empty table files are accepted.
Sources
- EBA, Overview of technical checks, validation rules and business checks to be applied by the EBA for RoI reporting (updated 28 April 2025), xlsx (read 2026-10-31)
- ESAs/EBA, Observations from reporting of RoI to the ESAs - key common issues identified (16 Apr 2025, updated 16 May 2025), slides (read 2026-10-31)
- CSSF, Guidance for interpretation and resolution of ESA error messages related to the DORA register, v1.0, 15 May 2025 (read 2026-10-31)
- AFM, Q&A-sessie DORA-informatieregister (March 2026 session; PDF, Dutch) (read 2026-10-31)