The DORA register, field by field
The Register of Information is seven EBA reporting templates and 51 fields. Rather than tell you it is "automated", here is exactly how much of it fills itself from data your team already maintains, and which fields it cannot.
Where the work actually goes
Two templates carry almost the whole burden and fill themselves. Two need you, and we would rather show that than average it away.
Two templates, in full
Not a mock-up of a register: these are the field names as the product defines them.
RT.02.01 — Contractual arrangements
- AUTOContract reference number
- AUTOContract type
- AUTOContract status
- AUTOStart date
- AUTOEnd date
- AUTOAnnual cost (EUR)
- YOUGoverning law
- AUTOParent contract reference
Governing law is the only field here we will not infer. A contract can be silent on it, and guessing the governing law of an agreement you are about to file with a regulator is not a favour.
RT.03.01 — ICT third-party providers
- AUTOIdentifier type
- AUTOProvider LEI
- AUTOProvider legal name
- AUTOCountry of head office
- AUTOUltimate parent LEI
- YOUDesignated as CTPP
CTPP designation is a determination by the European Supervisory Authorities, not a property of your data. It stays yours to set.
What does not fill itself
RT.03.02, the subcontractor chain
Nought of six fields derive, and no tool can honestly claim otherwise. Your provider has to disclose who sits behind them. Altisium gives you the structure to record it and the assessment to ask for it, then that answer is a supplier conversation, not a calculation.
RT.05.01, the CIF assessment
One of seven. Whether an ICT service supports a critical or important function is a judgement your business makes, and a register that guessed it for you would be worth less, not more.
See it filled with your own suppliers.
Bring a vendor list and we will show you what derives and what is left.