Skip to content
DORA Validation
Try it free

Regulatory reporting • Commission Implementing Regulation (EU) 2024/2956

Stop wrestling with the DORA reporting templates. Get a validated xBRL-CSV package in five business days.

We audit your internal contract data against the validation rules the ESAs publish for Register of Information reporting[1], review the contractual terms DORA requires for ICT third-party arrangements, and convert your draft Register of Information into a validated xBRL-CSV container.

The engagement

Fixed price
€8,500
Flat fee, excl. VAT. No billable-hour surprises.
Timeline
Five business days
Deliverable
Executive defect map + validated xBRL-CSV package (.zip)
Book your 5-day audit sprint

The 5-day delivery playbook

  1. Day 1

    Ingestion and privacy isolation

    • Sign the NDA and receive your current draft Register of Information (Excel or CSV templates).
    • Your data is parsed through our private, offline validation suite. No third-party cloud transfer is involved.

  2. Day 2

    ESA validation and checksum run

    • Structural verification of every 20-character LEI, including the ISO 17442 MOD 97-10 check digits. Codes that are well formed but whose registry status we cannot confirm offline are flagged for you to check against GLEIF.
    • Foreign-key referential integrity testing across all 14 reporting templates, RT.01.01 through RT.07.01.[2]

  3. Day 3

    Contract and sub-outsourcing audit

    • Qualitative review of your critical provider arrangements as reported in RT.02.01 and RT.04.01.
    • Review of the contractual terms DORA requires for ICT third-party arrangements: audit rights, exit strategies, and multi-tier subcontractor visibility in RT.05.02.

  4. Day 4

    Defect map compilation and remediation guidance

    • A line-by-line remediation action plan: the exact missing field codes, broken service links, and identifiers that need re-checking.
    • A 45-minute working session with your compliance and risk team to resolve the discrepancies.

  5. Day 5

    Final xBRL-CSV compilation and package delivery

    • Generation of the UTF-8 encoded xBRL-CSV package, with the report package metadata the filing rules require.
    • Delivery of the executive summary sign-off memo for your management body.

What you receive

  • The executive defect map (PDF)

    A board-ready assessment of your register: where it stands, which mandatory data points are missing, and which concentration risks the data surfaces.

  • The line-by-line remediation log (Excel)

    Every validation warning and blocking error mapped to the exact template cell, with the correction each one requires.

  • The validated xBRL-CSV container (.zip)

    An archive formatted to the ESA taxonomy naming rules, validated against the published rule set before it reaches you.

  • The contract gap checklist

    The specific clause amendments your critical ICT providers need, listed per provider.

Registers are submitted to your national competent authority — in Luxembourg the CSSF, in France the ACPR, in Ireland the Central Bank of Ireland, in Germany BaFin, in Belgium the FSMA. Each authority runs its own submission channel and its own timetable; we format to the ESA taxonomy rules and hand the package to you to file.

Regulatory notice and allocation of responsibilities

Responsibility for the accuracy of the Register of Information, and for submitting it, rests with the financial entity’s management body. It does not transfer to us.

This service is an independent technical, structural and data quality assurance audit. We provide the diagnostic testing, the formatting engine and the remediation recommendations. The decision to submit, and the submission itself, remain yours.

We are not a supervisory authority and are not endorsed by, affiliated with or approved by one. A clean result in our validation run does not mean your submission will be accepted.

Frequently asked questions

Why not just use the Excel templates our authority published?

Submissions are made as xBRL-CSV report packages, not as raw spreadsheets. Exports from Excel commonly fail on encoding, on missing foreign-key links between service lines and contracts, and on identifiers that no longer resolve. The sprint closes that technical gap.

How is our confidential contract data protected?

We work under a signed non-disclosure agreement. Validation is executed locally, on isolated machines. Your data is not sent to an external AI API, and it is not loaded into a multi-tenant third-party SaaS database.

What if our draft register is only half complete?

That is the norm rather than the exception. The sprint identifies exactly what is missing, sets out the conventions to apply for the gaps, and gives your team a prioritised list of only the vendor data you still genuinely need to collect.

Secure your regulatory filing window early.

Each sprint is scheduled against a named delivery window, so the earlier we agree dates, the more of the timetable stays yours.

Schedule an intake briefing

Sources

  1. [1]The EBA publishes 120 checks for Register of Information reporting, in four categories: technical checks, DPM technical checks, DPM business validation rules, and LEI/EUID checks. Source ↩
  2. [2]The ESA reporting template carries 14 reporting templates, RT.01.01 to RT.07.01, plus RT.99.01, which is an options legend rather than a reportable template. spec/RegisterInformation.xlsx — Counted from the ESA reporting template held in /spec/. A public URL for that workbook is pending owner confirmation (spec/SOURCES.md). ↩
DORA Validation

DORA Validation is an independent tool. It is not endorsed by, affiliated with, or approved by any supervisory authority.