Reference: platform fields to Register of Information tables
This page lists every column the Register of Information export produces, and what the platform puts in it. Use it when you need to know where a value in the exported file came from, or which field to correct when a supervisor queries a cell.
Note: this is a reference, not a walkthrough. If you are setting DORA up, start with Digital Operational Resilience Act (DORA).
How to read this page
Every reporting table appears twice in the export, under two different names:
- Excel (XLSX) names the sheet
RT_01.03and labels each column with a cell code likeb_01.03.0010. - xBRL-CSV names the file
B_01.03and labels the same columnsc0010,c0020, and so on.
The two are the same table in the same column order. The tables below give both.
Example value shows what a single worked example produced, so you can see the shape of what lands in each cell rather than guessing from the label.
RT_01.01 · B_01.01
Comes from: Your organisation profile. The tenant organisation record.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| LEI of the financial entity maintaining the register of information | Alphanumerical | 984500CA0960470D7B49 |
|
| Name of the financial entity | Alphanumerical | DILIGENT CORPORATION |
|
| Country of the financial entity | Country | eba_GA:BE |
|
| Type of financial entity | Closed set of options | eba_CT:x12 |
|
| Competent authority | Alphanumerical | |
|
| Date of the reporting | Date | 2025-12-31 |
RT_01.02 · B_01.02
Comes from: Organisation model — entities. Elements of type Entity that are in DORA scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| LEI of the entity | Alphanumerical | 984500CA0960470D7B49 |
|
| Name of the entity | Alphanumerical | DILIGENT CORPORATION |
|
| Country of the entity | Country | eba_GA:BE |
|
| Type of entity | Closed set of options | eba_CT:x12 |
|
| Hierarchy of the entity within the group (where applicable) | Closed set of options | eba_RP:x53 |
|
| LEI of the direct parent undertaking of the entity | Alphanumerical | 984500CA0960470D7B49 |
|
| Date of last update | Date | 2026-08-19 |
|
| Date of integration in the Register of information | Date | 2021-10-13 |
|
| Date of deletion in the Register of information | Date | 9999-12-31 |
|
| Currency | Currency | EUR |
|
| Value of total assets - of the financial entity | Monetary |
RT_01.03 · B_01.03
Comes from: Organisation model — branches. Active elements of type Branch.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Identification code of the branch | Alphanumerical | DE-FRA-001 |
|
| LEI of the financial entity head office of the branch | Alphanumerical | 984500CA0960470D7B49 |
|
| Name of the branch | Alphanumerical | Frankfurt branch |
|
| Country of the branch | Country | eba_GA😀E |
RT_02.01 · B_02.01
Comes from: Contracts. Contracts in DORA scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | THC-49 |
|
| Type of contractual arrangement | Closed set of options | eba_CO:x1 |
|
| Overarching contractual arrangement reference number | Alphanumerical | |
|
| Currency of the amount reported in RT.02.01.0050 | Currency | |
|
| Annual expense or estimated cost of the contractual arrangement for the past year | Monetary | 250000 |
RT_02.02 · B_02.02
Comes from: Contracts. Contracts in DORA scope, with their third party.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | THC-49 |
|
| LEI of the entity making use of the ICT service(s) | Alphanumerical | 984500CA0960470D7B49 |
|
| Identification code of the ICT third-party service provider | Alphanumerical | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the ICT third-party service provider | Pattern | eba_qCO:qx2000 |
|
| Function identifier | Pattern | F1 |
|
| Type of ICT services | Closed set of options | eba_TA:S01 |
|
| Start date of the contractual arrangement | Date | 2025-12-05 |
|
| End date of the contractual arrangement | Date | 2028-12-05 |
|
| Reason of the termination or ending of the contractual arrangement | Closed set of options | |
|
| Notice period for the financial entity making use of the ICT service(s) | Natural number | 90 |
|
| Notice period for the ICT third-party service provider | Natural number | 90 |
|
| Country of the governing law of the contractual arrangement | Country | |
|
| Country of provision of the ICT services | Country | eba_GA:US |
|
| Storage of data | [Yes/No] | eba_BT:x29 |
|
| Location of the data at rest (storage) | Country | eba_GA:qx2007 |
|
| Location of management of the data (processing) | Country | eba_GA:qx2007 |
|
| Sensitiveness of the data stored by the ICT third-party service provider | Closed set of options | |
|
| Level of reliance on the ICT service supporting the critical or important function. | Closed set of options | eba_ZZ:x794 |
Note: the two data-location rows show eba_GA:qx2007. That is the code the export writes when no country applies — either storage of data is not set to yes, or the location field is empty. A filled location exports as a country code, like eba_GA:US.
RT_02.03 · B_02.03
Comes from: Contracts. Contracts in DORA scope flagged as intra-group.
This example produced no rows for this table, so the example column is empty. The columns themselves are read from the export definition.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | |
|
| Contractual arrangement linked to the contractual arrangement referred in RT.02.03.0010 | Alphanumerical | |
|
| Link | Fill with "true" for each populated row |
RT_03.01 · B_03.01
Comes from: Contracts. The entity that signed, per contract in scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | THC-49 |
|
| LEI of the entity signing the contractual arrangement | Alphanumerical | 984500CA0960470D7B49 |
|
| Link | Fill with "true" for each populated row | 1 |
RT_03.02 · B_03.02
Comes from: Contracts → third party. The provider on each contract in scope.
Note: the export does not declare data types for this table, which is why the type column reads —.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | — | THC-49 |
|
| Identification code of ICT third-party service provider | — | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the ICT third-party service provider | — | eba_qCO:qx2000 |
RT_03.03 · B_03.03
Comes from: Contracts. The providing entity, per contract in scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | THC-49 |
|
| LEI of the entity providing ICT services | Alphanumerical | 984500CA0960470D7B49 |
|
| Link | Fill with "true" for each populated row | 1 |
RT_04.01 · B_04.01
Comes from: Contracts. The entities that use the service, per contract in scope.
This example produced no rows for this table, so the example column is empty. The columns themselves are read from the export definition.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | |
|
| LEI of the entity making use of the ICT service(s) | Alphanumerical | |
|
| Nature of the entity making use of the ICT service(s) | Closed set of options | |
|
| Identification code of the branch | Alphanumerical |
RT_05.01 · B_05.01
Comes from: Third parties. Third parties in DORA scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Identification code of the ICT third-party service provider | Alphanumerical | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the ICT third-party service provider | Pattern | eba_qCO:qx2000 |
|
| Additional identification code of ICT third-party service provider | Alphanumerical | |
|
| Type of additional identification code of the ICT third-party service provider | Pattern | |
|
| Legal name of the ICT third-party service provider | Alphanumerical | DILIGENT SERVICES |
|
| Name of the ICT third-party service provider in Latin alphabet | Alphanumerical | DILIGENT SERVICES |
|
| Type of person of the ICT third-party service provider | Closed set of options | eba_CT:x212 |
|
| Country of the ICT third-party service provider’s headquarters | Country | eba_GA:US |
|
| Currency of the amount reported in RT.05.01.0070 | Currency | |
|
| Total annual expense or estimated cost of the ICT third-party service provider | Monetary | 250000 |
|
| Identification code of the ICT third-party service provider’s ultimate parent undertaking | Alphanumerical | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the ICT third-party service provider’s ultimate parent undertaking | Pattern | eba_qCO:qx2000 |
RT_05.02 · B_05.02
Comes from: Contracts → third party. The service supplied under each contract in scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | THC-49 |
|
| Type of ICT services | Closed set of options | eba_TA:S01 |
|
| Identification code of the ICT third-party service provider | Alphanumerical | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the ICT third-party service provider | Pattern | eba_qCO:qx2000 |
|
| Rank | Natural number | 1 |
|
| Identification code of the recipient of sub-contracted ICT services | Alphanumerical | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the recipient of sub-contracted ICT services | Pattern | eba_qCO:qx2000 |
RT_06.01 · B_06.01
Comes from: Organisation model — functions. Elements of type Function.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Function Identifier | Pattern | F1 |
|
| Licenced activity | Closed set of options | eba_TA:x185 |
|
| Function name | Alphanumerical | Claims Handler |
|
| LEI of the financial entity | Alphanumerical | 984500CA0960470D7B49 |
|
| Criticality or importance assessment | Closed set of options | eba_BT:x29 |
|
| Reasons for criticality or importance | Alphanumerical | |
|
| Date of the last assessment of criticality or importance | Date | 2026-08-17 |
|
| Recovery time objective of the function | Natural number | 4 |
|
| Recovery point objective of the function | Natural number | 1 |
|
| Impact of discontinuing the function | Closed set of options | eba_ZZ:x791 |
RT_07.01 · B_07.01
Comes from: Contracts → third party. The risk assessment of each service in scope.
Excel cell | CSV | Label | Type | Example value |
|---|---|---|---|---|
|
| Contractual arrangement reference number | Alphanumerical | THC-49 |
|
| Identification code of the ICT third-party service provider | Alphanumerical | 984500DF5DDA66AE1C40 |
|
| Type of code to identify the ICT third-party service provider | Pattern | eba_qCO:qx2000 |
|
| Type of ICT services | Closed set of options | eba_TA:S01 |
|
| Substitutability of the ICT third-party service provider | Closed set of options | eba_ZZ:x962 |
|
| Reason if the ICT third-party service provider is considered not substitutable or difficult to be substitutable | Closed set of options | |
|
| Date of the last audit on the ICT third-party service provider | Date | 2026-06-19 |
|
| Existence of an exit plan | [Yes/No] | eba_BT:x29 |
|
| Possibility of reintegration of the contracted ICT service | Closed set of options | eba_ZZ:x798 |
|
| Impact of discontinuing the ICT services | Closed set of options | eba_ZZ:x791 |
|
| Are there alternative ICT third-party service providers identified? | Closed set of options | |
|
| Identification of alternative ICT TPP | Alphanumerical |
Coverage
- 101 columns across 14 reporting tables, plus a terminology sheet the export adds for reference.
- 12 tables were checked against a real export run, column by column, with a worked example in each cell.
- 2 tables produced no rows in that run — RT_02.03, RT_04.01 — so their columns are listed from the export definition but no example value is shown. The column order and codes are still authoritative.
Known limitations
- This is what the platform exports, not what your supervisor requires. Column coverage is not the same as a compliant filing.
- Empty in, empty out. A column whose source field is blank exports blank; the export does not stop for it.
- Only records in DORA scope are exported, so a table can be legitimately empty.