What is register logic?
What register logic means in the context of DORA reporting, how Copla Registry encodes it, and why it matters as your register grows and changes over time.
Covered on this page:
What register logic means in the context of DORA reporting
Register logic refers to the rules defined by the EBA reporting framework that govern how your register must be structured — the required fields, the coded values, and the relationships between entities, functions, providers, contracts, and supply chains.
These rules come from two sources: the ITS on registers of information (EU 2024/2956), which defines what must be reported and in what structure, and the EBA DORA RoI data model, which specifies every field in detail — its type, whether it is mandatory, whether it is a key value, and how it links to other fields across templates.
A key value is a field that cannot be left empty and must be unique and consistent across all templates where it appears.
A contract reference used in one template must appear identically in every other template that references that contract.
An identifier for a provider must match across every row that names that provider.
When these links break — because a value was changed in one place but not another, or because a key was left empty — the register fails validation at the supervisory level, regardless of how complete and accurate the surrounding data is.
How Copla Registry encodes and enforces register logic
Copla Registry encodes the register logic into the platform so you do not have to interpret and apply it manually.
Contract references and provider identifiers are treated as controlled values rather than free text, so they are reused consistently wherever they are referenced across the register rather than typed independently each time.
Plain-language answers in the form are automatically mapped to the EBA classifier codes required in the submission file. You see human-readable options; the platform handles the code translation.
Validation runs before export to catch missing required fields, broken links between records, and format errors before they reach your NCA.
Why register logic matters as the register grows and changes
As the number of providers, contracts, and functions in your register grows, so does the number of cross-record relationships — functions linked to contracts, contracts linked to providers, providers linked to supply chains. Maintaining those relationships manually becomes progressively harder to do without introducing inconsistencies.
The register is also a living document. Contracts change, providers are added or removed, functions are reassessed. Each change creates the risk of inconsistency if the underlying relationships are not tracked carefully.
Copla Registry logs every change with a user and timestamp, giving you a full audit trail and making it easier to identify and explain any modifications if questions arise during supervisory review.