B_04.01 — Entities using ICT services
Purpose
This template maps which entities or branches are the actual users of ICT services under each contractual arrangement. While B_03.01 identifies who signed the contract, B_04.01 identifies who consumes the services.
Each row links an entity (or branch) to a contract, specifying whether the user is the entity itself (NE_1) or a specific branch (NE_2). This distinction is critical for understanding the geographic and organizational scope of ICT service dependencies.
Business function owners and ICT teams maintain this template to ensure accurate mapping of service consumption across the organization.
Fields Reference
| Code | Field Name | Type | Req. | Description |
|---|---|---|---|---|
| c0010 | Contractual arrangement reference number* | text | Yes | Reference to the contractual arrangement Max length: 255 |
| c0020 | LEI of the entity making use of the ICT service(s)* | lei | Yes | LEI of the entity using the service Max length: 20 |
| c0030 | Nature of the entity making use of the ICT service(s)* | select | Yes | Whether the entity using the service is a branch or not Show 2 allowed values
|
| c0040 | Branch identification code | text | No | Branch code if the entity using the service is a branch Max length: 255 |
Relationships
Validation Rules
- Arrangement reference must exist in B_02.01. The contract under which services are consumed must be registered.
- Entity LEI must exist in B_01.02. The entity using the services must be part of the consolidated group (or B_01.01 for IND reporting).
- Branch code required for NE_2. If the nature of the user is
NE_2(branch), the branch code must be provided and must exist in B_01.03. - Branch code empty for NE_1. If the nature is
NE_1(entity), the branch code field must be empty.
Example
| Field | Value |
|---|---|
| Arrangement Reference | CA-2025-001 |
| Entity LEI | 529900T8B... |
| Nature | NE_1 (Entity) |
| Branch Code | (empty) |
Common Mistakes
- Selecting NE_2 (branch) without providing branch code. When the service user is a branch, the branch code is mandatory and must reference a valid entry in B_01.03.
- Providing branch code for NE_1 (entity). Entity-level users should not have a branch code. This field must be left empty for NE_1 entries.
- Missing service usage records. Every arrangement should have at least one entity or branch consuming its services. Contracts without B_04.01 entries suggest incomplete data.