Export Guide
The final step in preparing the DORA Register of Information is exporting it as an xBRL-CSV package. This guide explains the export format, the structure of the output ZIP file, naming conventions, and what to do after export.
What is xBRL-CSV?
xBRL-CSV is a tabular reporting format defined by XBRL International. It represents structured financial and regulatory data as CSV files within a ZIP package, accompanied by JSON metadata that describes the report's taxonomy and parameters. The EBA has adopted xBRL-CSV for DORA reporting, using the EBA Taxonomy 4.0.
Unlike traditional XBRL (which uses XML), xBRL-CSV uses plain CSV files that are human-readable and easy to inspect. The JSON metadata provides machine-readable context including the taxonomy reference, entity identifier, reference date, and currency.
Prerequisites for Export
Before you can export, ensure the following are configured in Settings:
- LEI — Your 20-character Legal Entity Identifier. This is embedded in the filename and the parameters file. Export will fail without a valid LEI.
- Country — Your ISO 3166-1 alpha-2 country code (e.g., LV, DE). This is part of the filename convention.
- Reporting type — IND (individual) or CON (consolidated). This determines the scope identifier in the filename.
- Reference date — The reporting reference date, typically
2025-12-31. - Reporting currency — The base currency for monetary parameters (e.g., EUR).
Recommendation: Run validation before exporting. While the export itself does not block on validation errors, submitting an invalid register to your competent authority will result in rejection. Fix all errors first.
ZIP Package Structure
The export produces a single ZIP file containing the following structure. The top-level directory inside the ZIP uses the package naming convention described below.
{package-name}/
META-INF/
reportPackage.json # Package manifest (points to report.json)
reports/
report.json # xBRL-CSV report metadata (EBA Taxonomy 4.0)
parameters.csv # Entity identifier, reference date, currency
FilingIndicators.csv # 15 templates, all reported = true
b_01.01.csv # B_01.01 - Entity maintaining the register
b_01.02.csv # B_01.02 - Entities in consolidation
b_01.03.csv # B_01.03 - Branches
b_02.01.csv # B_02.01 - Contractual arrangements (general)
b_02.02.csv # B_02.02 - Contractual arrangements (specific)
b_02.03.csv # B_02.03 - Intra-group links
b_03.01.csv # B_03.01 - Entity signatories
b_03.02.csv # B_03.02 - Provider signatories
b_03.03.csv # B_03.03 - Financial entity providers
b_04.01.csv # B_04.01 - Entities using ICT services
b_05.01.csv # B_05.01 - ICT providers
b_05.02.csv # B_05.02 - Supply chain
b_06.01.csv # B_06.01 - Functions
b_07.01.csv # B_07.01 - Assessments
b_99.01.csv # B_99.01 - DefinitionsMETA-INF/reportPackage.json
The package manifest. Contains a single documentURLs array pointing to the report metadata file:
{
"documentURLs": ["../reports/report.json"]
}reports/report.json
The xBRL-CSV report descriptor. Specifies the document type and extends the EBA DORA taxonomy:
{
"documentInfo": {
"documentType": "https://xbrl.org/2021/xbrl-csv",
"extends": [
"http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/dora/4.0/mod/dora.json"
]
}
}reports/parameters.csv
Contains the reporting parameters as name-value pairs. These identify the reporting entity, reference date, and base currency:
name,value
entity,rs:{LEI}.{IND|CON}
refDate,2025-12-31
baseCurrency,iso4217:EURThe entity value combines the LEI with the reporting scope (IND or CON), prefixed with rs:.
reports/FilingIndicators.csv
Lists all 15 DORA templates with their reporting status. All templates are reported as true, even if they contain no data rows (empty templates are valid):
templateID,reported B_01.01,true B_01.02,true B_01.03,true ... B_99.01,true
Template Data Files (b_01.01.csv ... b_99.01.csv)
Each template is exported as a separate CSV file. The header row uses DPM column identifiers (c0010, c0020, etc.), and data rows contain the cell values. Templates with no data produce a header-only CSV file.
c0010,c0020,c0030,c0040,c0050,c0060 529900T8BM49AURSDO55,Acme Bank Ltd,LV,FE_1,FCMC,2025-12-31
Filename Naming Convention
The ZIP file and its top-level directory follow the EBA naming convention:
{LEI}.{IND|CON}_{COUNTRY}_DORA010100_DORA_{REFDATE}_{TIMESTAMP}.zipWhere:
| Component | Description | Example |
|---|---|---|
LEI | 20-character Legal Entity Identifier | 529900T8BM49AURSDO55 |
IND|CON | Reporting scope: individual or consolidated | IND |
COUNTRY | ISO 3166-1 alpha-2 country code | LV |
DORA010100 | Fixed DORA module identifier | DORA010100 |
DORA | Fixed framework identifier | DORA |
REFDATE | Reference date (yyyy-mm-dd) | 2025-12-31 |
TIMESTAMP | Generation timestamp (YYYYMMDDHHMMSSsss) | 20260315143022123 |
Full example filename:
529900T8BM49AURSDO55.IND_LV_DORA010100_DORA_2025-12-31_20260315143022123.zip
CSV Encoding Details
| Property | Value |
|---|---|
| Character encoding | UTF-8 |
| Byte Order Mark (BOM) | None (no BOM) |
| Delimiter | Comma (,) |
| Line ending | CRLF (\r\n) |
| Text qualifier | Values containing commas or newlines are quoted |
After Export: Submission
Once you have the ZIP file, the next step is to submit it to your competent authority. The exact submission process depends on your jurisdiction:
- Identify your competent authority — This may be the ECB (for significant credit institutions in the euro area), your national financial supervisory authority (e.g., FCMC in Latvia, BaFin in Germany, AMF in France), or another body designated under DORA.
- Access the collection platform — Competent authorities provide dedicated collection platforms or portals for receiving DORA register submissions. Check your authority's website for access instructions.
- Upload the ZIP package — Upload the exported ZIP file through the authority's platform. The platform will typically run its own validation and provide feedback.
- Review feedback — If the authority's validation identifies issues, you will receive error reports. Fix the issues in this tool, re-validate, re-export, and resubmit.
Data stays local: Remember that the export is generated entirely in your browser. The ZIP file is created client-side using the fflate compression library. No data is transmitted to any server during the export process. The file downloads directly to your device.
Inspecting the Export
After downloading, you can inspect the ZIP contents to verify correctness:
- Unzip the file with any standard archive tool (7-Zip, macOS Archive Utility,
unzipon Linux). - Check report.json to verify the taxonomy reference points to the EBA DORA 4.0 module.
- Check parameters.csv to confirm your LEI, reporting scope, reference date, and currency are correct.
- Open the template CSV files in a text editor or spreadsheet application. Verify that headers use DPM column codes (c0010, c0020, ...) and data rows contain the expected values.
- Check FilingIndicators.csv to confirm all 15 templates are listed with
true.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Export button is disabled | LEI or Country is not configured in Settings | Go to Settings and fill in the required fields |
| Filename shows "undefined" | LEI, country, or reference date is missing | Check all Settings fields are populated |
| Empty template CSVs | No data rows entered for that template | This is valid — templates with no data export as header-only CSVs. The filing indicator is still set to true. |
| Authority rejects the file | Validation errors in the data, incorrect naming, or taxonomy mismatch | Run validation in this tool, fix all errors, and re-export. Check the authority's error report for specific issues. |