A DORA Register of Information tool has one practical job: keep a financial entity’s ICT third-party arrangements accurate in the standard structure required by Commission Implementing Regulation (EU) 2024/2956. The difficult part is usually connecting signed arrangements, services, users, functions and relevant provider chains without contradictory identifiers. A spreadsheet can do this if ownership and validation are disciplined. Software becomes useful when changes, group entities or supply chains make that discipline difficult to sustain. The choice should follow a trial with your own contracts, not a vendor’s promise that an export button makes the register compliant.
Under DORA Article 28(3), financial entities maintain and update a register covering all contractual arrangements for ICT services from third-party providers. They distinguish services supporting critical or important functions from those that do not. The register is maintained at entity level and, where applicable, at sub-consolidated and consolidated levels. The same provision requires annual information to the competent authority about new arrangements, provider categories and the corresponding functions and makes the full register available to the competent authority on request. A particular supervisor may separately organise a collection of complete registers; check its current instructions and reporting channel. Keeping the register current is a continuing duty regardless of a collection window. For the legal purpose of the record, start with the DORA Register of Information guide.
Start with the legal template, then choose the tool
Regulation 2024/2956 establishes the standard templates in its Annexes I–IV. Annex I names the tables and describes their relationships; Annex II supplies field-by-field instructions; Annexes III and IV support controlled values and classification. This is more precise than an informal supplier list. A product that stores contract PDFs but cannot represent the prescribed rows and relationships leaves the hard work for a later conversion. Conversely, a maintained workbook using the official columns can be adequate if the responsible team checks its accuracy and can provide the required information.
The register is a data model, not one document per supplier. Its core relationships include:
| Information to connect | Why it matters |
|---|---|
| Financial entities and branches | Shows who maintains the register and which entity signs or uses a service. |
| Contractual arrangements | Provides a stable reference for the signed agreement and its services. |
| Direct and relevant other providers | Distinguishes the contracting provider from group providers, relevant subcontractors and ultimate parents. |
| ICT services and users | Connects the service to the arrangement and to entities actually using it. |
| Functions and criticality | Shows which business functions the ICT service supports and where enhanced DORA duties apply. |
| Supply chains | Links direct providers with subcontractors that effectively underpin relevant services. |
For example, a bank may buy cloud hosting under one agreement, while two group entities consume different parts of the service. A useful register preserves one arrangement reference, identifies the signing entity, associates each user with the ICT service, and links the service to the functions it supports. Treating the vendor name as the only key would hide these differences. The regulation’s template names include B_02.01 for arrangements, B_04.01 for users, B_05.01 for providers and B_05.02 for supply chains. Read the Annex II instructions before deciding how to represent these relationships in a workbook or database.
Which providers and identifiers belong in it?
Article 3(2) of Regulation 2024/2956 calls for relevant information on all ICT services supplied by direct providers. It also requires information on subcontractors that effectively underpin ICT services supporting critical or important functions, or material parts of them. That is more nuanced than entering every remote subcontractor of every supplier without regard to the service. The standard templates also distinguish intra-group providers and ultimate parent undertakings where their rows are required. A provider’s marketing name is not enough: identify the legal counterparty and connect it consistently to the agreement.
Article 3(5) permits a valid active LEI or European Unique Identifier (EUID), and both where available, to identify ICT third-party providers that are legal persons; the rule excepts individuals acting in a business capacity. Article 3(6) addresses identifiers for the included subcontractors supporting critical or important functions. Annex II, template B_05.01, further specifies that a legal-person provider not established in the Union must use an LEI, rather than an EUID. The exact field and conditional instructions matter. Do not assume every vendor must buy an LEI, or fill a missing value with an invented code to satisfy a spreadsheet validation rule. Ask the contracting provider for its legal identity, check the official identifier where applicable, record the source and resolve ambiguity before export.
Supply-chain mapping needs its own review. Article 2 of the implementing regulation assigns the direct provider rank 1 and a subcontractor a higher rank. A chain can branch: the relevant question is which subcontractor actually supports the particular ICT service and function, not how many vendors appear in a generic supplier list. DORA ICT third-party risk management explains the separate due-diligence decisions that this inventory should inform. For contracts supporting a critical or important function, assess subcontracting permissions and monitoring against DORA’s enhanced rules rather than treating a completed register row as a contractual safeguard.
The data-quality checks a useful tool should perform
Regulation 2024/2956 Article 3(3) requires accurate, consistent information, regular review and prompt correction of errors. Article 3(4) names accuracy, completeness, consistency, integrity, uniformity and validity as data-quality principles. This gives buyers a better test than asking whether a product advertises “DORA-ready.” Load a representative set of real arrangements and see whether the tool detects the following issues before an authority or group reviewer does:
- Broken references. Does a service row point to an existing arrangement, provider and user? Can a function be traced back to the service supporting it?
- Duplicate entities. Does the same legal provider appear twice because procurement used a trading name in one agreement and the legal name in another?
- Missing classifications. Can the business owner explain whether the supported function is critical or important, and does the classification match related rows?
- Contradictory dates and terms. Did a renewed agreement supersede an old one, or was the old service still used after the supposed end date?
- Supply-chain gaps. Where a relevant subcontractor is reported, does the chain identify its relationship to the direct provider and service?
- Group inconsistency. Do entity-level arrangements and users reconcile with the applicable consolidated view?
These are examples of practical validation, not a claim that every regulator runs an identical error test. A good workflow also stores who made a classification, when the underlying contract or supplier response was checked, and what remains unresolved. Those notes help a reviewer distinguish a genuine uncertainty from an omitted field. They should be accessible to the relevant owners, with suitable access controls for confidential contracts and provider data.
The four connecting keys described in the implementing regulation’s recitals are the arrangement reference, identifiers for entities and providers, the function identifier and ICT service type. The legal Annex instructions govern the actual fields; a tool should import and export those fields without quietly changing their meaning. Ask for a sample export with multiple services under one agreement and the same provider serving several entities. A clean-looking dashboard can conceal a broken underlying relationship.
Spreadsheet or software: make the decision on your data
There is no DORA rule that prohibits spreadsheets or sets a contract-count threshold for buying software. A small institution with few arrangements may maintain the official tables in a controlled workbook. It needs an owner, field instructions, version control, a review log and checks for cross-table references. Save signed agreements and supplier evidence separately and reference them from the workbook. The practical limit arrives when updates cannot be reliably reconciled, not at an arbitrary number of providers.
A tool becomes more valuable when procurement, operational risk and ICT teams maintain different parts of the data; one contract covers several ICT services; a group needs entity and consolidated views; or material supply chains change between review dates. The advantage is controlled input and reliable reconciliation, provided the software actually supports the current Annex fields. Automation cannot decide whether a function is critical, obtain a truthful subcontractor list or interpret an unclear contract. Those are business and legal decisions that need accountable owners.
In a procurement demonstration, use three representative records: a straightforward direct service, a contract covering several functions and users, and a critical-function service with an included subcontractor. Ask the vendor to show the source document, edit history, linked rows, validation messages and resulting export for each. Repeat after changing a renewal date and replacing one provider identifier. If a change must be copied manually into unrelated screens, estimate that work in the evaluation. Compare the result with a well-maintained workbook before attributing a price premium to “compliance.” The DORA compliance software buyer’s guide covers broader selection criteria, while enterprise DORA software addresses group-scale integration. A broader DORA software comparison can help assemble a candidate list, but verify each register feature with a live export.
Check commercial terms separately from legal capability. Ask what is included in data import, supplier questionnaires, group reporting, validation, schema updates, export, support and access for reviewers. Obtain a written demonstration of the current 2024/2956 template version. A vendor’s claim that it supports an “EBA format” is not enough to establish which fields and controlled values it implements. If your competent authority prescribes a particular submission package or technical channel, test that requirement against the authority’s instructions rather than extrapolating from the EU regulation.
Build the register from contracts and service ownership
Begin with the signed arrangement inventory from procurement. Reconcile it with invoices, ICT asset/service catalogues and the systems actually in use. The goal is to find missing agreements and obsolete entries, not to assume that every discovery-tool hit is automatically an ICT service contract. Assign one stable reference per contractual arrangement; keep amendment and renewal history intelligible. Confirm the legal entities that signed and those that use the services. A group procurement team may contract centrally while a regulated subsidiary uses the service, and the template distinguishes these roles.
Next, ask the ICT service owner to identify the service type and supported business function. The function owner should make or confirm the critical-or-important classification under DORA’s definition and the institution’s method. Record the reason and the decision date. For a function that changes classification after a new product launch or outsourcing change, update the linked arrangements and any enhanced third-party controls. The DORA compliance guide places this decision alongside ICT risk management and resilience duties; the register is an input to that work, not a substitute for it.
Then collect provider details from the agreement and a documented supplier response. Check identifiers, headquarters and relevant parent relationship against the Annex instructions. For services supporting critical or important functions, ask the direct provider which subcontractors effectively underpin the service and how changes will be disclosed. Do not paste a broad public subprocessor page into the DORA supply-chain table without checking whether each entity is relevant to the particular service and function. Review whether exit arrangements and substitution options are credible where Article 28(8) applies.
Finally, perform a cross-table review before providing information to a supervisor or group parent. One person should test references and required values; another should compare a sample against signed agreements and service-owner confirmation. Document unresolved fields and seek correction promptly. Keep a dated extract so that later changes can be explained, while continuing to update the live register. This workflow works with a spreadsheet or a database. Its reliability depends more on clear ownership and source evidence than on interface polish.
Reporting is related to, but distinct from, maintenance
The financial entity maintains and updates the register continuously. Article 28(3) also speaks of annual reporting to the competent authority on new ICT arrangements, provider categories, arrangement types and supported functions, as well as producing the full register on request. The European Supervisory Authorities use register data for their separate critical-provider oversight work. These are related obligations, but they do not mean every institution has an identical annual full-register filing date or that pressing “export” satisfies all supervisor instructions.
Check the competent authority’s current request, scope, reference date, file format, validation process and submission channel. A cross-border group may need to coordinate entity and consolidated data with more than one supervisor. Keep an internal record of what version was supplied and which follow-up questions were answered. If a format validator rejects a package, correct the underlying register and regenerate the extract rather than hand-editing only the submitted file. Such a correction should also flow through to the live control record.
The register does not replace a GDPR Article 30 record of processing activities. A DORA row records an ICT service arrangement and its financial-service dependencies; a GDPR ROPA records personal-data processing with different fields and roles. A provider may appear in both, and shared legal-entity identifiers can reduce duplicate typing, but the two records answer different questions. If the ICT provider processes personal data for the institution, assess the applicable controller–processor relationship separately. Neither regulation turns every ICT contract into a processor contract.
Questions to settle before purchasing
Do we need dedicated software? DORA prescribes the register content and data quality, not a named application. Try the official template with your real arrangements. If owners can maintain, validate and provide it reliably, a controlled workbook may suffice. If reconciliation or group roll-up repeatedly fails, software may reduce that operational risk.
Does every supplier need an LEI? No. Regulation 2024/2956 Article 3(5) allows LEI or EUID for legal-person ICT providers, and both where available; it excepts individuals acting in a business capacity. Annex II B_05.01 requires an LEI for a legal-person provider not established in the Union. Field instructions and the provider’s actual status determine what you enter. Resolve identity questions with evidence rather than inventing a value.
Must all subcontractors appear? The implementing regulation specifically requires information on those that effectively underpin ICT services supporting critical or important functions or material parts. Follow the Annex supply-chain instructions for included providers. A blanket upload of every unrelated subcontractor is neither a reliable map nor a substitute for assessing the relevant chain.
How often should we update it? Update it as arrangements, services, entities, functions or relevant supply chains change, and review accuracy regularly. The law does not make an annual spreadsheet refresh enough by itself. Check the competent authority’s current collection instructions for any separate submission deadline.
What should a vendor demonstrate? A trace from agreement to service, user, function and relevant supply chain; correct current Annex fields and controlled values; detection of missing or conflicting data; and an inspectable export. Ask who can correct an error and whether the correction persists in the maintained register. Those demonstrations are stronger evidence than a generic DORA-ready badge.