Docs / Compliance

EBA export

How tprm.mlab.sh turns your register into the 15 EBA ITS templates, validates it, and packages a deposit-ready xBRL-CSV .zip.

Where it lives

The export workspace is at /eba/ (Licensed tier). It aggregates data automatically from every module — providers, contracts, functions, assessments, entity, scope, branches, intra-group and definitions — into the EBA ITS Reporting Framework 4.0 templates.

The 15 templates

Template	Official title
`B_01.01`	Entity maintaining the register of information
`B_01.02`	List of entities within the scope of the register
`B_01.03`	List of branches
`B_02.01`	Contractual arrangements – General information
`B_02.02`	Contractual arrangements – Specific information
`B_02.03`	List of intra-group contractual arrangements
`B_03.01`	Entities signing for receiving ICT services
`B_03.02`	ICT third-party service providers signing the arrangements
`B_03.03`	Entities signing for providing ICT services (intra-scope)
`B_04.01`	Entities making use of the ICT services
`B_05.01`	ICT third-party service providers
`B_05.02`	ICT service supply chains
`B_06.01`	Functions identification
`B_07.01`	Assessment of the ICT services
`B_99.01`	Definitions

Controlled codes

Each typed column is emitted with its controlled eba_* code rather than free text. You select human-readable values in the UI (a country, a service type, an arrangement type) and the export resolves them to the official codes — eba_GA: for countries, eba_TA:S01–S19 for ICT service types, eba_CO: for arrangement types, eba_CU: for currencies, and so on. See the DORA mapping for the full vocabulary list.

Preview & download

Preview any template — the column grid (c00xx) with resolved codes.
Download a single CSV per template, all raw CSVs at once, or the full deposit package.

Validation

Before you build the package, click Validate. The validator runs four classes of check and returns an errors / warnings / infos report per template:

Check	What it verifies
Referential integrity	Contract, provider and function keys resolve across templates — no dangling references.
Format	LEI is 20 characters, dates are `yyyy-mm-dd`, controlled values are valid `eba_*` codes.
Mandatory fields	Required columns are present and non-empty.
Uniqueness	Keys that must be unique (e.g. contract reference) are not duplicated.

Resolve all errors first. Warnings and infos won't block the package, but errors will. Fixing them before deposit avoids the most common authority rejections.

The deposit package

The deposit-ready package is a single .zip conforming to the official xBRL-CSV report-package structure:

{LEI}.CON_{COUNTRY}_DORA010100_DORA_{date}_{timestamp}.zip

{LEI}.CON_{COUNTRY}_DORA010100_DORA_{date}_{timestamp}.zip
├── META-INF/
│   └── reportPackage.json        # package manifest
└── reports/
    ├── report.json               # DORA taxonomy binding
    ├── parameters.csv            # reporting parameters
    ├── FilingIndicators.csv      # which templates are filed
    ├── B_01.01.csv
    ├── B_01.02.csv
    ├── B_01.03.csv
    ├── B_02.01.csv
    ├── B_02.02.csv
    ├── B_02.03.csv
    ├── B_03.01.csv
    ├── B_03.02.csv
    ├── B_03.03.csv
    ├── B_04.01.csv
    ├── B_05.01.csv
    ├── B_05.02.csv
    ├── B_06.01.csv
    ├── B_07.01.csv
    └── B_99.01.csv

Filename pattern

{LEI} — the reporting entity's 20-character LEI (from B_01.01).
{COUNTRY} — ISO 3166-1 alpha-2 code of the competent authority's country.
DORA010100 — the module identifier for the DORA register.
{date} — the register reference date (yyyy-mm-dd).
{timestamp} — generation timestamp, making each package unique.

From data to deposit, in order

Set the reporting entity and reference date (/ei/).
Complete providers, contracts, functions and assessments across the modules.
Open /eba/ and click Validate; resolve every error.
Download the deposit package .zip.
Submit it to your competent authority through their reporting channel.

Related: DORA mapping shows which module feeds each template, and the API reference documents the /eba/* endpoints.