Guides to the package itself
The parts of a DORA report package that people search for by name after a rejection: the filename, the control files, the folder layout, the Excel conversion. Each one with the checks that read it and the regulators that differ.
| The DORA register zip filename, part by part What each element of <LEI>.<CON|IND>_<CC>_DORA010100_DORA_<yyyy-mm-dd>_<timestamp>.zip means, which checks read it (102, 105, 109, 111, 714), and how the CBI, NBB, Norway, Sweden, Finland and Denmark change it. |
| parameters.csv in a DORA report package The five lines of reports/parameters.csv: entityID with the rs: prefix, refPeriod, baseCurrency, decimalsInteger and decimalsMonetary, with the national variants and the checks that read them (714, 320, 701). |
| FilingIndicators.csv: declaring the 15 templates What reports/FilingIndicators.csv must contain, why every DORA template is normally declared true, what 808 means, and how empty templates are handled by the ESAs, the NBB and Banca d'Italia. |
| report.json and reportPackage.json, exactly The two JSON control files of an xBRL-CSV DORA package: documentType, the extends URL for EBA DPM 4.0, generatingSoftwareInformation, and the errors when they are missing or wrong. |
| The report package, folder by folder The exact zip layout the ESAs and the national portals accept for a DORA Register of Information: one root folder named like the zip, META-INF and reports, lower-case table files, UTF-8, no extras. |
| From the Excel register to xBRL-CSV How to turn a register kept in Excel into the xBRL-CSV package the ESAs require: one sheet per template, column codes, enumerated codes instead of labels, dates and amounts, keys, and which regulators still take Excel. |