Contents

Generate and download the xBRL-CSV package

Generate and download the xBRL-CSV package

Outcome: with one click you generate the xBRL-CSV package (ZIP) from the register, download it, tell from the banner whether it is fit for submission, and know what it contains.

Prerequisites

  • Entity maintaining the register (B_01.01) is entered – with LEI and Reporting reference date. Both values determine the file name and the parameters.csv file. Without the LEI the file name starts with UNKNOWNLEI; without the reference date today’s date is used.
  • Base currency of the report in the settings is correct (default EUR).
  • Validation reports no errors (Validation and data quality: consistency checks, EBA rules, GLEIF LEI check). The app generates the package even with errors but then warns clearly – such a package is not fit for submission.
  • Your browser allows downloads from Jira.

Generate and download the package (click by click)

  1. Click Import & export (area Reporting). The card xBRL-CSV export is at the top with the hint “Generates the ZIP package (one CSV per template + JSON metadata) for upload via the BaFin MVP portal. The upload itself happens outside the app.”
  2. Click Generate & download xBRL-CSV package. While generating, the button reads “Generating…”.
  3. Expected result: the browser automatically downloads a ZIP file (file name see below), and a banner appears in the card:
  • ✓ „Package ‹file name› generated without errors and downloaded.“
  • ⚠ „Package generated, but it contains n validation errors — fix them in the validation center before submitting.“ – the package was generated and downloaded anyway; do not use it for submission.
  • ✕ a red error message – no package was generated (see troubleshooting).
  1. Below the button the Export history (audit trail) appears with the columns File, Created, Taxonomy and Validation (“no errors” or “n errors”). It lists the last 25 exports; the cockpit shows the last five.
  2. Check the package (section “Verify the package”) and upload it outside the app in your supervisory authority’s portal. The app does not store the package – keep the ZIP file yourself.
Figure 1: The “Import & export” page before the first export.
Figure 2: Successful export without validation errors; the export history below.
Figure 3: Export despite validation errors – yellow warning, history entry with “3 errors”.
Figure 4: The cockpit lists the recent exports with their validation state.

What is generated

File name: ‹LEI›.CON_FR_DORA010000_DORA_‹reference date›_‹timestamp›.zip, example: 529900NRDPAY01000021.CON_FR_DORA010000_DORA_2025-12-31_20260825113436.zip (timestamp = generation time in UTC, YYYYMMDDhhmmss).

File in the ZIPContent
META-INF/reports.jsonReport package descriptor (xBRL Report Packages).
reports/report.jsonxBRL-CSV metadata (OIM): document type https://xbrl.org/CT/2023-04-19/csv and reference to the taxonomy entry point http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/dora/4.0/mod/dora.json.
reports/parameters.csvReport parameters: entityID = lei:‹LEI from B_01.01›, refPeriod = reporting reference date from B_01.01, baseCurrency = iso4217:‹base currency from the settings›.
reports/FilingIndicators.csvOne row per template: B_xx.xx,true (contains records) or B_xx.xx,false (empty).
reports/b_01.01.csv … reports/b_99.01.csvAlways all 15 templates, one CSV per template. Header = EBA column codes (c0010,c0020,…), one row per record. Yes/no as true/false, dates as YYYY-MM-DD, dropdown fields as code (e.g. S16), empty fields empty. The app field Supports a critical or important function is not exported.

Verify the package

  1. Open the ZIP file and check that the files listed above are present.
  2. Compare FilingIndicators.csv with the Completeness per template table in the cockpit: templates with records must read true.
  3. Check LEI and reference date in the file name; check the base currency in parameters.csv.
  4. Spot-check a CSV (e.g. b_05.01.csv) and compare the number of rows with the number of records in the cockpit.

Limitations and notes

  • The package is always generated for the whole register – there are no partial or filtered exports and no choice of a reference date other than the one in B_01.01.
  • Validation errors do not prevent generation; the warning banner and the export history record the error count.
  • Taxonomy label in the package and history: its-2024-2956/4.0; module code in the file name: DORA010000. Taxonomy entry point, module code, file-name pattern, column codes and code lists are marked in the app as “to be verified before a real submission”.
  • The app stores no packages, only the history (file name, time, taxonomy, rows per template, error count). The history cannot be deleted in the app and survives “Delete all register data”.
  • The upload to the supervisor (e.g. BaFin MVP portal) and its technical validation take place outside the app.

Rendered from the app’s own interface with the built-in demo data (“Nordpay”, a fictitious payment institution); the Jira frame around it is not shown.

Documentation baseline: app version 2.0.0 · 2026-08-25