XBRL-CSV format for the DORA register of information

Many register-of-information filing failures are technical before they are business issues. The expected format is not a free-form Excel workbook: it is an xBRL-CSV package (“plain CSV”) aligned with the EBA DORA taxonomy for reporting under Implementing Regulation (EU) 2024/2956.

This article covers package structure, file rules, and errors that fail a deposit even when substance is “almost right”. Business view of templates: complete guide.

What DORA xBRL-CSV is (and is not)

It is not “save a table as CSV”. It is a ZIP file containing:

• reporting metadata (report.json, parameters.csv, FilingIndicators.csv, META-INF/reportPackage.json)
• one CSV per template (b_01.01.csv … b_99.01.csv)

Each package covers one module (DORA), one reference date, and the declared reporting level.

ZIP package structure

{LEI}.CON_{Country}_{FrameworkVersion}_DORA_{RefDate}_{Timestamp}.zip
├── reports/
│   ├── report.json
│   ├── parameters.csv
│   ├── FilingIndicators.csv
│   ├── b_01.01.csv
│   ├── … (all templates)
│   └── b_99.01.csv
└── META-INF/
    └── reportPackage.json

ZIP naming

{LEI}.CON_{Country}_{FrameworkVersion}_DORA_{RefDate}_{Timestamp}.zip

Parameter	Role
{LEI}	Reporting entity LEI (20 characters)
CON / IND	Reporting level per applicable convention
{Country}	ISO 3166-1 alpha-2 (e.g. FR)
{FrameworkVersion}	Framework version (e.g. DORA010100)
{RefDate}	Register reference date (yyyy-mm-dd)
{Timestamp}	Creation timestamp (yyyyMMddHHmmssSSS)

Wrong naming or a reference date inconsistent with parameters.csv is a classic technical rejection.

Steering files

report.json

Points to the EBA DORA taxonomy entry (extends URL). A wrong taxonomy / framework version invalidates the package.

parameters.csv

Typical parameters: entityID, refPeriod, baseCurrency (e.g. iso4217:EUR), integer/monetary decimal settings.

FilingIndicators.csv

One indicator per template, true if reported, false otherwise. A missing indicator row is an error — even for intentionally empty templates (branches, intra-group…).

{table}.csv content

• First row: column codes (c0010,c0020,…)
• Following rows: data
• Closed lists: full EBA codes with eba_ prefix (e.g. eba_CT:x12, eba_GA:FR, eba_TA:S19)
• Countries: eba_GA:XX · Currencies: eba_CU:XXX

Technical CSV rules

Type	Format
Encoding	UTF-8 mandatory
Separator	Comma ,
Date	yyyy-mm-dd
Boolean	true / false (lowercase)
Monetary	Amount in units (not thousands)
Empty field	Empty cell (no explicit null token)
Unknown / open-ended date	9999-12-31
Text with comma	Wrap in double quotes

Frequent technical pitfalls

1. Excel “Save as CSV” changing encoding, separator (;) or corrupting eba_ codes
2. Incomplete FilingIndicators
3. Codes without EBA prefix — FR instead of eba_GA:FR
4. Malformed LEI
5. Monetary decimals / units inconsistent with parameters.csv
6. Framework / taxonomy version misaligned with the authority’s exercise
7. Wrong deposit channel — in France, RoI dry runs / filings often use a dedicated OneGate package, distinct from usual reporting tabs

Homologate the package before the campaign: it is the only way to separate business errors from packaging errors.

Link to data quality

Format cannot fix an incoherent model. Keys (arrangement number, LEI, provider code, function ID) must be stable before CSV generation. See mandatory fields and 2025 mistakes.

Go further

• Complete guide
• Operating model

Axenia’s role. Axenia prepares register exports in a structure compatible with packaging and coding expectations, reducing last-minute manual rework and technical rejections.

---

Based on xBRL-CSV / EBA taxonomy specifications for the DORA module and Implementing Regulation (EU) 2024/2956. Always verify the framework version and your authority’s deposit instructions. Not legal advice.