Create, edit and delete records (maintaining the register)

Outcome: you create, change or delete records in any of the 15 templates – with plain-language fields instead of column codes – and know which consistency checks the app performs immediately.

Prerequisites and recommended order

Many templates refer to records of other templates (e.g. a contract detail in B_02.02 needs the contract from B_02.01, the provider from B_05.01 and the function from B_06.01). The app only allows references to existing records. Therefore enter data in this order:

#	Template	Requires (references to)
1	Entity maintaining the register `B_01.01`	–	Fields
2	Entities within scope of consolidation `B_01.02`	–	Fields
3	Branches `B_01.03`	`B_01.02`	Fields
4	ICT third-party service providers `B_05.01`	–	Fields
5	Business functions `B_06.01`	`B_01.02`	Fields
6	Contractual arrangements — general information `B_02.01`	–	Fields
7	Contractual arrangements — specific information `B_02.02`	`B_02.01`, `B_01.02`, `B_06.01`, `B_05.01`	Fields
8	Linked / intra-group arrangements `B_02.03`	`B_02.01`	Fields
9	Signing financial entities `B_03.01`	`B_02.01`, `B_01.02`	Fields
10	Signing ICT service providers `B_03.02`	`B_02.01`, `B_05.01`	Fields
11	Intra-group service providers (signing) `B_03.03`	`B_02.01`	Fields
12	Entities making use of the ICT services `B_04.01`	`B_01.03`, `B_02.01`, `B_01.02`	Fields
13	ICT service supply chains `B_05.02`	`B_02.01`, `B_05.01`	Fields
14	Assessment of the ICT services (critical/important) `B_07.01`	`B_02.01`, `B_05.01`	Fields
15	Definitions `B_99.01`	`B_01.02`	Fields

The list view of a template

Figure 1: List view (here B_05.01 with the 10 demo providers).

Header: template name, below it “Template B_xx.xx · n records”.
Search box “Search…”: filters as you type by name and key fields (contains search).
+ New: opens the editor for a new record.
The table shows the first six fields of the template; all fields are visible in the editor. References are displayed by their key (e.g. a provider’s LEI, not its name), code-list values as plain text, yes/no as a badge.
Row actions: Edit and Delete; double-clicking a row also opens the editor.
Empty template: “No records in B_xx.xx yet. Start with "+ New" or import an existing EBA Excel file under "Import & export".”

Create a record

In the navigation click the template you want (e.g. ICT third-party service providers B_05.01).
Click + New at the top right. The editor opens on the right with the title B_xx.xx · New record.
Fill in the fields. Mandatory fields per ITS are marked with * (tooltip “Mandatory field per ITS”); the EBA column code follows every label in grey (e.g. · c0010), and an input hint may appear below the field.
Click Save (“Saving…” while saving). Expected result: the editor closes, the list reloads and the new record appears at the top (newest first).
If a check fails, the editor stays open and shows a red message at the top (table below). Correct the input and click Save again. Cancel or × discards the input.

Figure 2: The editor for a new record in B_02.02. References are dropdowns, mandatory fields carry an asterisk, column codes appear in grey next to the label.

Controls in the editor

Field kind	Control in the editor	Notes
Reference to another template (e.g. contract reference, ICT service provider, LEI of the entity using the service)	Dropdown “– please select –” with the existing records of the referenced template in the format `key — name`.	If the list is empty, the referenced record does not exist yet – create it there first. The list is loaded when the editor opens (max. 1,000 entries).
Code list (e.g. type of ICT service, critical or important?)	Dropdown with plain-language labels.	The technical codes (e.g. `S16`) appear only in the export – see the code lists in The 15 EBA templates at a glance.
Yes/no field (e.g. Is data stored?)	Checkbox labelled “Yes”.	Checked = yes, empty = no.
Date	The browser’s date picker.	Stored as YYYY-MM-DD; the display follows the browser.
Number	Number field (whole number or two decimals).	Notice periods, RTO/RPO, rank: whole numbers. Costs, total assets: decimals.
LEI	Text field (max. 20 characters, upper case automatically) with the GLEIF button.	Check see Validation and data quality: consistency checks, EBA rules, GLEIF LEI check. The LEI is not checked on save; the validation checks the check digits (V-002).
Country and currency codes	Text field; converted to upper case automatically.	Format ISO 3166-1 alpha-2 (`DE`) or ISO 4217 (`EUR`) – checked by validation (V-003).
Text	Single-line text field; reasons/definitions multi-line.	Key and reference fields max. 100 characters, “Term” max. 200 characters.

Filled-in editor for an assessment in B_07.01 with contract and provider selected — Figure 3: Filled-in example (B_07.01): contract reference and provider from the dropdowns, substitutability from the code list, exit plan as a checkbox.

What is checked on save

On save the app checks keys, references, data types and codes – not the completeness of mandatory fields. The full table of checks with the exact messages is in Validation and data quality → Consistency checks on save. The most important cases:

Key field empty (e.g. contract reference) → “Missing required value: "…" (key field of …)”.
Same key already exists → “A record with this key already exists in …”.
Reference to a non-existent record (only possible via import – the editor offers existing records only) → “Reference not found: …”.
Second record in Entity maintaining the register (B_01.01) → “… may only contain a single record. Please edit the existing entry.”
Invalid date, not a whole number, not a number, text too long → matching message naming the field.

Edit a record

Open the template and click Edit in the row – or double-click the row (tooltip “Double-click to edit”). Use the search box “Search…” to find records by name and key values.
The editor opens with the title B_xx.xx · Edit record. Change the fields and click Save.
Expected result: the editor closes and the list shows the changed values. Name changes (e.g. a provider’s name) take effect everywhere immediately because other templates store only the key.

Delete a record

Click Delete in the row.
The browser asks “Really delete record "…"?” – confirm with OK.
Expected result: the row disappears. If the record is still referenced, a red message appears instead and nothing is deleted (Figure 4). Delete the dependent records first – easiest in the reverse of the entry order.

Figure 4: Attempt to delete a provider that is still referenced in contract details (B_02.02) – the app blocks it and names the referencing template.

Tips

The Cockpit shows the share of filled mandatory fields per template – that is how you find templates “in progress”.
After larger changes check completeness in the Validation center (Validation and data quality: consistency checks, EBA rules, GLEIF LEI check).
Large data sets are faster to bring in via Excel import (Import an EBA Excel 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