B_01.02 — Entities in consolidation | DORA Register of Information

Purpose

This template lists all financial entities included in the consolidated group scope. It is only applicable for CON (consolidated) reporting and must not be filled for IND (individual) reporting.

Each entity in the group receives one row with its LEI, legal name, country, entity type, hierarchy level, and parent entity reference. This template establishes the group structure that other templates reference when identifying which entity is using or providing ICT services.

The group compliance team or the parent entity's ICT risk function is responsible for maintaining this template whenever entities join or leave the group.

Fields Reference

Code	Field Name	Type	Req.	Description
c0010	LEI of the entity*	lei	Yes	Legal Entity Identifier of the entity within the scope of consolidation Max length: 20
c0020	Name of the entity*	text	Yes	Legal name of the entity Max length: 255
c0030	Country of the entity*	country	Yes	Country of authorisation (ISO 3166-1 alpha-2)
c0040	Type of entity*	select	Yes	Type of financial entity per DORA classification Show 26 allowed values `FE_1` — Credit institution `FE_2` — Payment institution `FE_3` — Account information service provider (exempt under Art.33 PSD2) `FE_4` — Electronic money institution `FE_5` — Investment firm `FE_6` — Crypto-asset service provider `FE_7` — Issuer of asset-referenced tokens `FE_8` — Central securities depository `FE_9` — Central counterparty `FE_10` — Trading venue `FE_11` — Trade repository `FE_12` — Manager of alternative investment funds `FE_13` — Management company `FE_14` — Data reporting service provider `FE_15` — Insurance undertaking `FE_16` — Reinsurance undertaking `FE_17` — Insurance intermediary `FE_18` — Reinsurance intermediary `FE_19` — Institution for occupational retirement provision `FE_20` — Credit rating agency `FE_21` — Administrator of critical benchmarks `FE_22` — Crowdfunding service provider `FE_23` — Securitisation repository `FE_24` — Issuer of significant asset-referenced tokens `FE_25` — Other financial entity within the group `FE_26` — Non-financial entity within the group
c0050	Hierarchy of the entity within the group*	select	Yes	Position in the group corporate structure Show 5 allowed values `H_1` — Ultimate parent undertaking in the EU `H_2` — Parent undertaking in the EU (not ultimate) `H_3` — Subsidiary `H_4` — Entity maintaining the register on a sub-consolidated basis `H_5` — ICT intra-group service provider
c0060	LEI of the direct parent undertaking*	lei	Yes	LEI of the entity that is the direct parent Max length: 20
c0070	Date of integration in the register*	date	Yes	Date when entity was added to the register
c0080	Date of last update*	date	Yes	Date of the last update of entity information
c0090	Date of deletion from the register*	date	Yes	Date removed from the register, or 9999-12-31 if still active
c0100	Currency	currency	No	Currency for total assets reporting (ISO 4217)
c0110	Total assets	monetary	No	Total assets value of the entity

Relationships

Referenced by (incoming)

←

B_01.03(c0020 → c0010)

List of branches

←

B_03.03(c0020 → c0010)

Financial entities providing ICT services

←

B_04.01(c0020 → c0010)

Entities making use of ICT services

Validation Rules

Unique LEIs. Every entity must have a distinct LEI. Duplicate LEIs within this template will cause a validation error.
Valid hierarchy structure. The hierarchy type must correctly reflect the entity's position: HI_1 (parent), HI_2 (joint subsidiary), HI_3 (subsidiary), etc. The parent LEI field must reference another entity listed in this same template.
Parent LEI referential integrity. When a parent LEI is provided, it must correspond to an existing row in this template. Orphaned parent references are invalid.
Deletion date logic. Active entities should use 9999-12-31 as the deletion date. Entities removed from the group must have a real past or current deletion date.

Example

Field	Value
LEI	`529900ABC...`
Entity Name	Subsidiary Bank
Country	LV
Entity Type	`FE_1`
Hierarchy	`HI_3` (Subsidiary)
Parent LEI	`529900T8B...`
Integration Date	2024-01-15
Last Update	2025-12-31
Deletion Date	9999-12-31

Common Mistakes

Duplicate LEIs. Accidentally entering the same entity twice with the same LEI. Each entity must appear exactly once.
Using 9999-12-31 for deletion of departed entities. Entities that have left the group should have a real deletion date, not the sentinel value.
Wrong hierarchy type. Assigning HI_1 (parent) to a subsidiary entity or vice versa. The hierarchy must accurately reflect the corporate structure.