DORA Register of Information
5999 EUR / yearv2.2.3
Every EU financial entity must maintain a Register of Information on all its ICT third-party arrangements and file it annually through its supervisor — 15 interlocking templates, submitted as a machine-readable xBRL-CSV package against the EBA's reporting framework. In the ESAs' dry run, 93.5% of submissions had at least one data error, and 86% of those were missing mandatory information. The data the register needs is exactly what your EA repository already holds.
DORA Register of Information turns Turbo EA into your register. Legal entities, providers, contractual arrangements, per-service details, subcontracting chains, and critical-or-important functions are maintained as a live register inside your workspace — with provider identity (LEI, EUID, person type, country) captured on the Provider cards your architects already keep, behind a checksum-validating LEI field. The extension walks your Provider → Application → Capability graph to propose function mappings and criticality classifications with evidence, so the register starts from your landscape instead of an empty spreadsheet — and every proposal is reviewed by a human before it lands.
When the reporting cycle comes, freeze a reference-date snapshot, run the validation engine (structural checks, closed-list membership against the transcribed DPM domains, cross-template referential integrity, and the EBA's own rule inventory with honest coverage reporting), fix what it finds, and download the submission package: the official xBRL-CSV report package for the EBA framework 4.0 DORA module, byte-reproducible and hash-pinned for audit, plus an Excel review workbook for your compliance team. Finalized snapshots are immutable — your register history is your audit trail.
The regulatory shape (templates, columns, member codes, validation rules) ships as versioned data transcribed from the official EBA artifacts, so a new EBA framework release is a data update, not a migration.
What’s new
2.2.32026-09-05
- This extension now ships a changelog. Every release from here on documents what changed for you in this file, and it travels inside the signed bundle so it is on disk wherever the extension is installed.
2.2.22026-09-05
- The French interface calls a card «fiche» rather than «carte», matching Turbo EA's own vocabulary.
2.2.12026-09-01
- The logo inside the bundle matches the one on the store listing.
2.2.02026-08-28
- The register workbench moved into the GRC menu, where the rest of your compliance work already lives, instead of taking its own place in the top bar.
2.1.02026-08-27
- The suggestions left stranded by the 2.0.0 pivot. They referred to a register that no longer exists and could not be acted on.
2.0.42026-08-27
- One convention for member codes throughout, and the validator now covers the card types 2.0.0 introduced — it had been skipping them.
2.0.32026-08-27
- Two dashboard figures that were read before the data they summarise had been written.
2.0.22026-08-27
- A register page that failed to render.
2.0.12026-08-27
- The database migration shipped in 2.0.0 was empty, so an upgrade left the schema behind.
2.0.02026-08-27
- The register is the metamodel. Register entries were their own tables alongside your landscape; they are now ordinary cards, so an entity appears once, is related to the rest of the inventory, and is governed by the same permissions and history as everything else. > This is a breaking change. The four register tables from 1.x are dropped and pre-2.0.0 > register rows are not migrated. Export anything you need before upgrading.
1.3.22026-08-27
- Findings land on the card they concern, and every register grid uses the same template.
1.3.12026-08-27
- The content pack now fills every column the metamodel requires, so the install no longer fails part-way.
1.3.02026-08-27
- A guided cockpit: register grids, findings you can act on, a readiness score, and surveys to collect what is missing from the people who know it.
1.2.02026-08-27
- Cards-first pivot — the register is projected from the metamodel rather than maintained beside it.
1.1.32026-08-27
- Demo data refresh, and a much faster dashboard.
1.1.22026-08-27
- An invalid business-criticality value that made the demo data fail to load.
1.1.12026-08-27
- A content row that blanked columns the metamodel requires.
1.1.02026-08-26
- One-click demo data — load a sample register, tagged «Demo Dora», and remove it again with one click.
1.0.02026-08-26
- First release. The DORA Register of Information: the ITS Annex II templates, the EBA's existence and non-negativity rules executed offline against your own data, and the exports the submission needs.