Glossary and FAQ
Glossary and FAQ
Glossary
| Term | Explanation |
|---|---|
| DORA | Digital Operational Resilience Act – EU regulation on digital operational resilience in the financial sector. Art. 28(3) obliges financial entities to keep the Register of Information. |
| Register of Information (RoI) / Informationsregister | The register of all contractual arrangements on ICT services with third-party providers – maintained in this app in 15 templates. |
| EBA | European Banking Authority – defines the templates, column codes, code lists and taxonomy for the register. |
| ITS (EU) 2024/2956 | Implementing regulation with the implementing technical standards for the register; basis of the 15 templates and mandatory fields in the app. |
| Template (B_xx.xx) | One of the 15 tables of the register, e.g. B_05.01 ICT third-party service providers. Overview: The 15 EBA templates at a glance. |
| Column code (c0010 …) | Technical identifier of a column in the EBA template; the app shows it in grey next to the plain-language label and uses it as the header row in export and import. |
| LEI | Legal Entity Identifier – 20-character code identifying legal entities uniquely (ISO 17442); the last two characters are check digits. |
| GLEIF | Global Legal Entity Identifier Foundation – operates the public LEI register. The app queries it via the GLEIF button (Validation and data quality: consistency checks, EBA rules, GLEIF LEI check). |
| EUID | European Unique Identifier – identifier from the European business registers interconnection (BRIS). Selectable in the app only as type of identification code; no online check. |
| xBRL-CSV | Data format of the EBA submission: CSV files plus JSON metadata following the xBRL standard (OIM), packaged as a ZIP (“report package”). |
| Filing indicators | File in the package stating per template whether it contains data (true/false). |
| Taxonomy | The rule set published by the EBA (data points, rules) referenced by report.json. Label in the app: its-2024-2956/4.0 – to be verified before submission. |
| Reporting reference date | Date the register refers to (field in B_01.01); appears in the package file name and in parameters.csv. |
| Submission deadline | Date of submission to the supervisor (settings); drives the countdown and the automatic epic. Set anew and verify every year. |
| Base currency | Currency of the report (settings, default EUR); written to parameters.csv. |
| Master arrangement / subsequent arrangement | Types of arrangement in B_02.01: a subsequent arrangement (type 3) must refer to a master arrangement (type 2) (rule V-014). |
| Supply chain / rank | B_05.02: chain of providers behind a contract; rank 1 = direct provider, rank 2 = its subcontractor (“4th party”), etc. |
| Critical or important function | Classification of a business function in B_06.01. In the app it triggers, together with the checkbox in B_02.02, the obligation to assess in B_07.01 (rule V-007). |
| Key (natural key) | The fields that make a record unique (e.g. contract reference). Decide over duplicates, references and the Excel import (upsert). |
| Reference | Field pointing to a record of another template; a dropdown in the editor. An “orphaned reference” points to a record that does not (or no longer) exist (rule V-005). |
| Upsert | Import behaviour: existing key → update the record, otherwise create it. |
| Finding | Result row of the EBA rule validation with severity Error or Warning, rule id (V-001 …), template, record and message. |
| Annual-report epic | Jira issue the app creates as an umbrella for the annual submission (manually or automatically). |
| “RoI Record” issue panel | Section in the Jira issue view that shows a linked register record. |
| BaFin MVP portal | BaFin’s reporting and publishing platform through which the package is submitted outside the app (per the app’s hint text). |
FAQ
Do I have to fill in all mandatory fields before I can save?
No. Drafts may be incomplete; on save only keys, references, data types and codes are checked. Mandatory fields are checked by validation (V-001).
Why can’t I delete a provider?
Because it is still referenced in contracts, supply chains or assessments. Delete those records first.
Do validation errors block the export?
No, not technically – the app generates the package but shows a yellow warning and records the error count in the history. Such a package should not be submitted.
Does the app upload the package to BaFin?
No. The app generates the package and downloads it to your browser; the submission happens outside.
Where is the register data stored?
In an own database, isolated per installation, on the Atlassian platform (Forge SQL). Settings and export history live in app storage; the language choice in the browser. No data is sent to third parties – except the LEI during a GLEIF check.
Is the GLEIF result stored?
No. It is only displayed.
Can I keep several reporting entities (several B_01.01)?
No, B_01.01 allows exactly one record per installation.
Is there an Excel export?
No. The CSV files of the xBRL-CSV package contain all data with column codes; they can be opened in Excel and – as worksheets B_xx.xx – imported again.
Who may do what?
The app has no roles. Whoever can open it can do everything – including deleting all data. Access is controlled by your Jira administrator.
Why are the GLEIF messages in German although I selected English?
Known limitation of the current app version; the meaning is in the results table of the validation page.
How often do I have to set the submission deadline?
Every year – app hint: “Set anew every year — verify the binding date with BaFin/EBA.”
Can I restrict the export to one entity or period?
No, the package always contains the whole register with the reference date from B_01.01.
Related pages
Documentation baseline: app version 2.0.0 · 2026-08-25