The 15 EBA templates at a glance

Templates: Master data (B_01.01, B_01.02, B_01.03)

This page describes the templates of the navigation group Master data: for each template what one record is, which key must be unique, which templates refer to it, and all fields with label, EBA column code, mandatory status and input type. Using the editor is described in Create, edit and delete records (maintaining the register).

B_01.01 – Entity maintaining the register

  • One record is: the entity maintaining the register itself – exactly one record (the app prevents a second one).
  • Key (must be unique): LEI. The key decides during Excel import whether a record is updated or created.
  • Referenced by: no other template – records can be deleted and their keys changed at any time.
  • Specific validation rules: V-006 – details in Validation and data quality: consistency checks, EBA rules, GLEIF LEI check. (V-001 to V-005 and V-015 apply to all templates in addition.)

Fields

Field (label in the app)EBA columnMandatory (ITS)InputHint in the appTechnical name
LEIc0010LEI (20 characters) + GLEIF button20-character Legal Entity Identifierlei
Name of the entityc0020Textname
Countryc0030Country code ISO 3166-1 alpha-2 (e.g. DE)ISO 3166-1 alpha-2, e.g. DEcountry
Type of entityc0040Dropdown “Type of entity”entity_type
Competent authorityc0050Texte.g. BaFincompetent_authority
Reporting reference datec0060Dateusually 31 Dec of the reporting yearreporting_date

B_01.02 – Entities within scope of consolidation

  • One record is: one entity within the scope of consolidation, unique by LEI.
  • Key (must be unique): LEI. The key decides during Excel import whether a record is updated or created.
  • Referenced by: Branches B_01.03, Contractual arrangements — specific information B_02.02, Signing financial entities B_03.01, Entities making use of the ICT services B_04.01, Business functions B_06.01, Definitions B_99.01. While references exist, a record can neither be deleted nor have its key changed.
  • Validation rules: the general rules V-001 to V-005 and V-015 – details in Validation and data quality: consistency checks, EBA rules, GLEIF LEI check.

Fields

Field (label in the app)EBA columnMandatory (ITS)InputHint in the appTechnical name
LEIc0010LEI (20 characters) + GLEIF buttonlei
Name of the entityc0020Textname
Countryc0030Country code ISO 3166-1 alpha-2 (e.g. DE)country
Type of entityc0040Dropdown “Type of entity”entity_type
Position within the groupc0050Dropdown “Position within the group”hierarchy
LEI of the direct parentc0060LEI (20 characters) + GLEIF buttonparent_lei
Date of last updatec0070Datelast_update
Date of integration into the groupc0080Dateintegration_date
Date of deletionc0090Datedeletion_date
Reporting currencyc0100Currency code ISO 4217 (e.g. EUR)ISO 4217, e.g. EURcurrency
Total assetsc0110Number (2 decimals)total_assets

B_01.03 – Branches

  • One record is: one branch, unique by its identification code; the head office must exist in B_01.02.
  • Key (must be unique): Branch identification code. The key decides during Excel import whether a record is updated or created.
  • Referenced by: Entities making use of the ICT services B_04.01. While references exist, a record can neither be deleted nor have its key changed.
  • Validation rules: the general rules V-001 to V-005 and V-015 – details in Validation and data quality: consistency checks, EBA rules, GLEIF LEI check.

Fields

Field (label in the app)EBA columnMandatory (ITS)InputHint in the appTechnical name
Branch identification codec0010Text (max. 100 characters)branch_id
LEI of the head officec0020Dropdown from Entities within scope of consolidation B_01.02 (LEI)head_office_lei
Name of the branchc0030Textname
Country of the branchc0040Country code ISO 3166-1 alpha-2 (e.g. DE)country

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