B_02.02 — Contractual arrangements specific | DORA Register of Information

Purpose

This template captures detailed information on each specific service/function combination within a contractual arrangement. While B_02.01 records the contract itself, B_02.02 breaks it down into the individual services delivered under that contract.

Each row represents a unique combination of: arrangement reference, entity LEI, provider ID, function ID, and service type. This granularity allows regulators to understand exactly which ICT services support which business functions.

The ICT risk management team maintains this template in coordination with the vendor management and business function owners.

Fields Reference

Code	Field Name	Type	Req.	Description
c0010	Contractual arrangement reference number*	text	Yes	Reference to the contractual arrangement in B_02.01 Max length: 255 FK → B_02.01 (c0010)
c0020	LEI of the entity making use of the ICT service(s)*	lei	Yes	LEI of the financial entity using the ICT service Max length: 20
c0030	Identification code of the ICT third-party service provider*	text	Yes	Provider identification code as registered in B_05.01 Max length: 255 FK → B_05.01 (c0010)
c0040	Type of code to identify the ICT third-party service provider*	text	Yes	Type of identification code (LEI, EUID, or country-specific) Max length: 50
c0050	Function identifier*	text	Yes	Identifier of the function supported by the ICT service Max length: 255 FK → B_06.01 (c0010)
c0060	Type of ICT services*	select	Yes	Type of ICT services per Annex III classification Show 13 allowed values `ICT_1` — ICT consultancy `ICT_2` — ICT development `ICT_3` — ICT infrastructure operations & support `ICT_4` — ICT help desk and first level support `ICT_5` — ICT security `ICT_6` — ICT networks `ICT_7` — ICT data management (including data storage and processing) `ICT_8` — Cloud services – IaaS `ICT_9` — Cloud services – PaaS `ICT_10` — Cloud services – SaaS `ICT_11` — Software licensing `ICT_12` — ICT project management `ICT_99` — Other ICT services
c0070	Start date of the contractual arrangement*	date	Yes	Date when the arrangement became effective
c0080	End date of the contractual arrangement*	date	Yes	End date, or 9999-12-31 for open-ended arrangements
c0090	Reason for the termination or ending	select	No	Reason for arrangement termination (if applicable) Show 6 allowed values `TR_1` — Expiry of the contract `TR_2` — Mutual agreement `TR_3` — Terminated by the financial entity `TR_4` — Terminated by the ICT third-party service provider `TR_5` — Terminated by the competent authority/resolution authority `TR_6` — Other
c0100	Notice period for the financial entity (calendar days)	number	No	Notice period in calendar days for the entity to terminate
c0110	Notice period for the ICT third-party service provider (calendar days)	number	No	Notice period in calendar days for the provider to terminate
c0120	Country of the governing law of the contractual arrangement	country	No	Country whose law governs the arrangement
c0130	Country of provision of the ICT services	country	No	Country where the ICT services are provided from
c0140	Storage of data	select	No	Whether the arrangement involves storage of data Show 2 allowed values `Yes` — Yes `No` — No
c0150	Location of the data at rest (storage)	country	No	Country where data is stored
c0160	Location of management of the data (processing)	country	No	Country where data is processed
c0170	Sensitiveness of the data stored by the ICT third-party service provider	select	No	Sensitivity level of the data Show 3 allowed values `DS_1` — Low `DS_2` — Medium `DS_3` — High
c0180	Level of reliance on the ICT service	select	No	Degree of reliance on the ICT service for business operations Show 4 allowed values `RL_1` — Not significant reliance `RL_2` — Low reliance `RL_3` — Material reliance `RL_4` — Full reliance/dependency

Relationships

References (outgoing)

→

B_02.01(c0010 → c0010)

Contractual arrangements - General information

→

B_05.01(c0030 → c0010)

ICT third-party service providers

→

B_06.01(c0050 → c0010)

Functions identification

Validation Rules

Arrangement reference must exist in B_02.01. Every row must reference a valid contract from the general contractual arrangements template.
Provider must exist in B_05.01. The ICT provider referenced must be registered in the providers master list.
Function must exist in B_06.01. The function identifier must correspond to a function defined in the functions identification template.
Start date must be before or equal to end date. The service start date cannot be after the service end date.
Termination logic. If a termination reason is provided, the end date must not be 9999-12-31 (the sentinel value for ongoing services).

Example

Field	Value
Arrangement Reference	`CA-2025-001`
Entity LEI	`529900T8B...`
Provider ID	`PROV-001`
Provider Code Type	LEI
Function ID	`FN-001`
Service Type	`IS_1`
Start Date	2024-01-01
End Date	9999-12-31

Common Mistakes

Referencing nonexistent providers or functions. Ensure the provider exists in B_05.01 and the function exists in B_06.01 before creating rows in this template.
End date before start date. A common data entry error when dates are entered manually. Always verify the chronological order.
Terminated services with sentinel end date. When a service has been terminated (reason provided), the end date must reflect the actual termination date, not 9999-12-31.