1. Who must keep it
The register applies to financial entities within the scope of DORA. It depends on the type of authorisation and the activity, so the first question is whether your organisation is included and at what level of obligation. The regulation applies proportionality in its application, but this is not an exemption: check with your adviser before considering the matter closed. Ask in writing before you decide.
The register covers contracts with ICT service providers, meaning those that supply infrastructure, software, data, connectivity or digital services supporting processes. It is not only an IT matter: even a contract managed by marketing or administration may fall within it. For this reason, collection cannot start only in the IT department; it must be built with every function that buys digital services.
2. What it contains
The register gathers standard information about each contract: who the provider is, which service it provides, which of the entity's functions it supports, where the data is located, who the subcontractors are and how the contract can be exited. The exact format and transmission methods are defined by technical standards linked to the regulation: check the current version before structuring the fields.
Not all fields are equally difficult. Identification data is straightforward, whereas the chain of subcontractors requires the supplier's cooperation and must be requested in writing. When the supplier does not respond, record the gap in the register: it is useful information for risk management. Record it as an open gap, with the name of the person who must request it. This is not a minor detail.
| Field | What it describes | Who provides it |
|---|---|---|
| Provider and identifier | Company name, references and the identifier used internally | Purchasing and compliance office |
| Service and functions supported | The ICT service purchased and the business process it supports | Process owner and IT manager |
| Criticality | Whether the service supports critical or important functions for the entity | Risk management function |
| Chain of subcontractors | Other parties the provider uses to deliver the service | Provider, through the contract |
| Data, location and exit | Where the data is held, how it is protected and how to exit the contract | Provider and IT manager |
3. Why the register matters more than expected
The register is the map that shows where dependencies are concentrated: if a single provider supports many critical functions, concentration risk rises, and the register is where this first becomes visible. Without this view, the exit plan and incident management start from incomplete data. The register also serves commercial decisions: before renewing or replacing a contract, whoever consults it knows which functions depend on the provider.
4. How to collect the data without losing track
Collection is easier if it proceeds in clear steps. Start from contracts and invoices, not from people's memory: contracts contain the binding information, and invoices help you find forgotten services. The steps below are a working order for the first version. Do not aim for perfection on the first pass. The work should be done calmly.
- Extract from purchasing archives and contracts all those concerning digital services, including those managed by business functions.
- Identify which services support critical or important functions, using the process impact assessment.
- For each provider, collect the identifier, the service, the subcontractors and the places where data is held.
- Request the missing information from the provider in writing and keep the response with the contract.
- Assign an internal owner to each line and set the date of the next review.
- Compare the list with recent payments and with the systems inventory: discrepancies point to contracts that are not recorded.
5. Evidence and maintenance
The register is only worth something if it is kept up to date. Every new contract, renewal, change of subcontractor and termination must produce an update. Establish who is responsible for this update and link it to the purchasing process, so that the register is updated when a contract is signed, not after an inspection. As evidence, keep dated versions, the linked contracts and the providers' written responses. Periodic reviews should also be minuted.
6. Frequent mistakes
The most common errors arise from haste and from fragmented data. The clearest symptom of a fragile register is a question with no answer: who uses this service and what happens if it stops working? If the register cannot answer that in a few minutes, it needs repairing, starting with the lines that have no owner, as these are the ones to assign first. Start there without hesitation.
- Compiling the register only with IT providers, forgetting digital services purchased by other functions.
- Considering a line complete when it does not report the chain of subcontractors.
- Keeping the register in a personal file of its creator, with no backup owner.
- Not linking providers to the criticality of processes, which makes the register useless for decisions.
- Updating it only before an inspection, instead of at every contractual change.
7. Points to clarify with your adviser
Some aspects require formal confirmation. Ask your adviser whether your entity falls within scope and at what level of obligation, which fields the current version of the technical standards requires, and in what format they must be transmitted to the competent supervisory authority. Also check how to handle providers that do not cooperate: the contract should include an obligation to supply the information requested.
8. How to get started
This week, identify the providers that support the most important processes, meaning those whose interruption would halt daily work. For each one, collect the contract and the service sheet. A partial but correct first version is worth more than a complete but unverified register. Then ask the most critical providers for their subcontractor chain and the places where data is held, with a written request stating the expected response date.
Frequently Asked Questions
Does the register also cover subscription software providers?
Yes, if the software provides an ICT service that supports the organisation's processes. Being on subscription, managed online or bought by another function does not exclude it. The criterion is the function performed, not the commercial model. Check borderline cases with your adviser, such as free tools used without a formal contract.
Who should update the register?
Usually a coordinating function, such as compliance or risk management, with input from IT and purchasing. Responsibility should, however, be assigned line by line: each service must have an internal owner who confirms the data and reports changes. The coordinating function's role is to verify that changes actually arrive.
Is the provider obliged to give me the information for the register?
It depends on the contract and the applicable regulatory framework. A good contract already includes an obligation to cooperate and to supply the information required by supervisors. If the contract is silent, renegotiate at the first suitable opportunity and, in the meantime, record the missing information as an open risk.
Is the register enough to demonstrate supplier management?
No. The register is an inventory, not an assessment. It must be supported by a risk assessment for each critical provider, by the contractual security clauses and by exit strategies. The register tells you what you have; the other parts show whether you manage it adequately.
Can I use a spreadsheet?
For a first version, often yes, provided it is protected against uncontrolled access, has an owner and records changes. As the number of contracts grows, the spreadsheet becomes difficult to maintain and verify. Evaluate with IT a dedicated tool once the lines increase or several functions need to update it.