Vendor Register
Standards ยท DORA ITS 2024/2956

Commission Implementing Regulation (EU) 2024/2956, the register of information templates

Rendered when the buyer ticks "DORA financial entity", as a Level 2 instrument under DORA, beside the Regulation's own articles. The register cites 11 of its 16 clauses, behind 4 findings: single-source vendors with no fallback named, dora register-of-information fields missing, cloud services with no exit plan, sub-outsourcing chains longer than one hop, and on the obligation rows of every vendor it reaches.

Edition: Commission Implementing Regulation (EU) 2024/2956, OJ L, 2024/2956, 2.12.2024. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim. Framework page. What it attaches to a vendor: the DORA regime page.

Clauses cited

11 of 16
DORA ITS 2024/2956 Art. 3(1) and (2) Article 3(1) and (2): Maintaining the register at each level and what it must cover

Financial entities must use the templates in Annexes I to IV to maintain and update the register of information under DORA Article 28(3) at entity level and, where relevant, at sub-consolidated and consolidated level. The register must include the relevant information on all ICT services provided by direct ICT third-party providers, and information on all subcontractors that effectively underpin ICT services supporting critical or important functions or material parts of them.

Evidence an auditor accepts: Register of information at entity level and, for groups, at sub-consolidated and consolidated level; Reconciliation of the register to the contract repository and accounts payable vendor list; Subcontractor information for each ICT service supporting a critical or important function
Common gap: Register built only for critical services rather than all ICT services from direct providers
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 3(3) Article 3(3): Accuracy, consistency and regular review

The information in the templates must be accurate and consistent. The entity must review it regularly and correct errors or discrepancies promptly. In groups, the entity maintaining the sub-consolidated or consolidated register must ensure the entity-level information it includes is correct and consistent with the group level.

Evidence an auditor accepts: Register review schedule and completed review records; Error log with dates corrected; Group reconciliation between entity-level and consolidated registers
Common gap: Validation errors returned by the authority left uncorrected
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 4 Article 4: Data format

Unless the instructions say otherwise, each template is a table with a fixed set of columns and any number of rows. Each data element takes a single value; where more than one value is valid, an extra row is added for each. All data elements must be completed at entity, sub-consolidated and consolidated level as applicable.

Evidence an auditor accepts: Register files in the prescribed tabular structure; Examples of multi-value elements handled by additional rows; Submission package in the format required by the competent authority, such as xBRL-CSV
Common gap: Multiple values packed into one cell
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 5(1)(n) Article 5(1)(n): Template B_07.01 on assessment of ICT services supporting critical or important functions

The register must contain the assessment of each ICT service provided by a third-party provider that supports a critical or important function or a material part of one (B_07.01), covering substitutability of the provider and the reason where it is hard to substitute, the date of the last audit, whether an exit plan exists, whether the service could be reintegrated, the impact of discontinuing it, and whether alternative providers have been identified.

Evidence an auditor accepts: Completed B_07.01 template for every ICT service supporting a critical or important function; Substitutability and exit plan assessments behind the template entries; Dates of the last assessment for each service
Common gap: Exit plan field marked yes with no exit plan held
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 3(4) Article 3(4): Data quality principles

The register must meet the data quality principles of accuracy, completeness, consistency, integrity, uniformity and validity. The ESAs' 2024 dry run found missing mandatory information to be the most frequent failed check (86 percent of data errors), followed by invalid LEI codes.

Evidence an auditor accepts: Data quality rules mapped to the six principles; Pre-submission validation against the ESAs' data point model and validation rules; Data quality dashboard showing mandatory field completeness
Common gap: Mandatory fields left blank
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 3(5) Article 3(5): Identifiers for ICT third-party providers

Financial entities must identify every ICT third-party service provider that is a legal person with a valid and active legal entity identifier (LEI) or the European Unique Identifier (EUID) under Article 16 of Directive (EU) 2017/1132, and both where available. Individuals acting in a business capacity are excepted.

Evidence an auditor accepts: Provider master data showing LEI and or EUID for each legal person provider; GLEIF validation results showing LEIs are issued and not lapsed; Process to obtain identifiers from providers at onboarding
Common gap: Lapsed LEIs reported as valid
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 5(1)(d) to (f) Article 5(1)(d) to (f): Templates B_02.01 to B_02.03 on contractual arrangements

The register must contain general information on every contractual arrangement with a direct ICT third-party provider, each with a unique contractual arrangement reference number (B_02.01); specific information on each arrangement covering the ICT services in scope, the functions they support and other key terms such as notice period and governing law (B_02.02); and the links between intra-group arrangements and arrangements with providers outside the group where part of the supply chain is intra-group (B_02.03).

Evidence an auditor accepts: Completed B_02.01, B_02.02 and B_02.03 templates; Contract repository with unique reference numbers matching the register; Extracted contract terms such as start and end dates, notice periods and governing law
Common gap: One reference number reused for several contracts
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 5(1)(k) and (l) Article 5(1)(k) and (l): Templates B_05.01 and B_05.02 on providers and the supply chain

The register must contain information on the direct ICT third-party providers and their subcontractors (B_05.01) and on the ICT service supply chain with each provider's rank (B_05.02).

Evidence an auditor accepts: Completed B_05.01 and B_05.02 templates; Provider profiles including identifiers, ultimate parent and country; Subcontractor chain disclosures obtained from direct providers
Common gap: Ultimate parent undertaking of providers not identified
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 5(1)(m) Article 5(1)(m): Template B_06.01 on the identification of functions

The register must identify the functions of the financial entities that use the ICT services, with a unique function identifier for each combination of entity LEI, licensed activity and function, and information including whether the function is critical or important, as specified in template B_06.01.

Evidence an auditor accepts: Completed B_06.01 template; Approved critical or important function assessment; Link from each function to the ICT services in B_02.02 that support it
Common gap: Functions in the register differ from the entity's approved critical function list
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 2 Article 2: Ranking ICT third-party providers in the supply chain

The financial entity must give every ICT third-party service provider a rank, a natural number of 1 or more, where a lower number means closer to the entity. The direct provider is always rank 1 and every subcontractor has a rank above 1.

Evidence an auditor accepts: Supply chain table (B_05.02) showing the rank of each provider per ICT service; Subcontractor disclosures from direct providers used to set ranks; Validation check that direct providers are rank 1 and subcontractors above 1
Common gap: Subcontractors given rank 1 alongside the direct provider
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates
DORA ITS 2024/2956 Art. 3(6) Article 3(6): Identifiers for subcontractors behind critical services

Where an ICT service from a direct provider supports a critical or important function, the entity must ensure, through that direct provider, that every subcontractor in the register that effectively underpins the service uses a valid and active LEI or provides its EUID, and both where available, unless it is an individual acting in a business capacity.

Evidence an auditor accepts: Contract clauses or requests requiring direct providers to supply subcontractor LEIs or EUIDs; Subcontractor identifier list per critical ICT service; Follow-up records where identifiers were missing
Common gap: Direct provider unable or unwilling to disclose subcontractor identifiers
Source framework: Commission Implementing Regulation (EU) 2024/2956, the register of information templates

See which clauses your list engages

Paste the list and every vendor names the clauses behind it, filtered to the regimes that apply to you. Eight vendors free, no account.

Build my vendor register