Contents

Import an EBA Excel register

Import an EBA Excel register

Outcome: you bring in an existing register from an Excel file in EBA format as the starting data set, or update existing records in bulk.

Requirements for the Excel file

  • File format .xlsx or .xls. The file is read in your browser; only the recognised rows are sent to the app.
  • One worksheet per template, named after the EBA code (B_01.01, B_02.02 …; spaces and case do not matter). Other worksheets are ignored.
  • A header row with the EBA column codes (c0010, c0020 …). The first row containing such codes counts as the header; rows above it (titles, explanations) are ignored. Columns without a code are ignored.
  • Below it one row per record; completely empty rows are skipped.
  • Values as in the export: dropdown fields as code (e.g. S16, LEI, YES – code lists in The 15 EBA templates at a glance), dates as text YYYY-MM-DD (Excel cells formatted as dates arrive as numbers and are rejected), yes/no as true/false or 1/0, countries/currencies as ISO codes.
  • References must exist – either already in the register or in the same file (the app imports the worksheets automatically in dependency order, parents first).

Run the import (click by click)

  1. Click Import & export and scroll to the card Import from EBA Excel (hint: “Imports an existing register (EBA Excel template) as the starting dataset. Existing records are updated by their keys (upsert); all integrity checks stay active.”).
  2. Click the file field (labelled by the browser, e.g. “Choose file”) and select the Excel file. Before that it reads “No file selected yet.”.
  3. Expected result: a Preview: ‹file name› table with Template and Rows per recognised worksheet (Figure 1). If “No templates recognised. Expected: worksheets named after EBA templates (B_01.01 …) with column codes (c0010 …) in a header row.” appears instead, check sheet names and header row.
  4. Click Start import (“Importing…” while importing).
  5. Expected result: table Import result per template with New (created), Updated (existing key updated), Skipped (empty rows) and Errors (“none” or a red badge; click it to show the first 20 messages “Row n: ‹message›”, Figure 2).
  6. Fix row errors in the Excel file and import it again – rows already imported are then only updated. Afterwards run validation (Validation and data quality: consistency checks, EBA rules, GLEIF LEI check).
Figure 1: Preview after selecting the file – two recognised worksheets (B_05.01 with 2 rows, B_02.01 with 1 row).
Figure 2: Import result without row errors.

Import rules

  • Upsert: for every row the app checks by the template key (see The 15 EBA templates at a glance) whether the record exists – then its fields are overwritten; otherwise it is created. The import can be repeated.
  • Every row is subject to all consistency checks as when saving in the editor; a faulty row does not abort the import, it is reported in the result.
  • The row number in an error message counts from the header row (header = 1, first data row = 2); empty rows are not counted.
  • Mandatory fields per ITS may stay empty (as in the editor); validation checks them.
  • There is no Excel export; the CSV files of the xBRL-CSV package serve as a backup of the register.

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