DORA Compliance Checklist
Get the clarity you need to navigate DORA — and the structure to act on it — with our step-by-step checklist.
Drop your ICT contracts in. We map all 101 fields, flag exactly what is missing, and give you the verbatim proof for what is there. No guessing, no ChatGPT hallucinations, zero lock-in.
We do the work if the software fails. Upload one supplier’s contracts today and get your ranked gap report plus a formatted export file, free. If our software misses a required field that is clearly stated in your contract, our founders will manually audit your next three suppliers by hand, over the weekend, at no charge.
Your DORA register was filed. The contracts behind it did not stop moving. An amendment is signed, a renewal comes through, a new vendor is onboarded. Each one sends you back into master agreements, SLAs and order forms, hunting again for 101 columns spread over 15 ITS templates that have to reconcile with one another.
101 columns across templates B_01.01 to B_07.01. EBA annotated table layout, DORA reporting framework 4.0.Commission Implementing Regulation (EU) 2024/2956, Article 3(1). Templates and instructions at Annex I.Financial entities shall use the templates set out in Annex I to IV to maintain and update the register of information in accordance with Article 28(3) of Regulation (EU) 2022/2554, at entity level, or at sub-consolidated and consolidated level.
Maintain and update. Not file once. If you guess, or if you let a general purpose chatbot guess for you, the register drifts away from your contracts and the next file gets rejected. You lose months, and you attract supervisory attention you do not want.
After you file
Register filed
It reflects the contracts you held then.
Amendment signed
Service levels or exit terms change.
Contract renewed
A new term and a new order form.
New vendor onboarded
A new provider, with its own subcontractors.
Supervisor asks for the register
It has to match the contracts you hold today.
Every step in between means reading the master agreement, the SLAs and the order forms again.
Evidence
Click through a real LeDora run below. The gap report lists what is missing, and clicking any answer highlights the exact sentence in the original PDF that it came from.
Documents
This vendor’s contracts are uploaded. Read them, and LeDora fills its register.
Your documents
4 ready · 11 pages
An interactive demo built from a real LeDora run. The contracts are synthetic.
LeDora uses AI to read your contracts, then checks every answer against fixed DORA rules. Nothing is guessed: each finding links to the exact clause and page it comes from, so your team can verify it in seconds.
Process
You do not need a heavy GRC platform, and you do not need to change how you work.
Drop your supplier PDFs into LeDora.
We map your documents against the exact CSSF and EBA specifications.
We hand you a byte-faithful export file that plugs straight into the spreadsheet or compliance tool you already use.
Questions
No. Your documents are stored and processed in EU data centres in Frankfurt, Germany, isolated per tenant, and deletable on request.
Never. Your contracts are never used to train any AI model, by us or by any provider in our processing chain. That is contractual, not a setting.
No. LeDora is a secure web application. There is no software to deploy and no six-month onboarding cycle.
Pricing is deterministic and calculated strictly on the number of ICT vendor contracts reviewed, starting at €9,967 for up to 100 contracts. We do not charge variable fees based on your assets under management or firm headcount.
See the pricing matrixNo. LeDora provides a software-driven evidentiary audit trail. We extract verbatim contractual clauses and compare them against published ESA taxonomies. We never assert legal compliance on your behalf; we provide the definitive evidence layer for your internal compliance team or external counsel to act upon.
You do not need to move up an engagement if you slightly exceed your limit. You can expand capacity in fixed blocks of 10 contracts for €1,500 per block, giving you complete cost control without contract disputes.
A register that passes CSSF portal validation can still be materially inaccurate if the underlying vendor contracts lack mandatory Article 30 protections. We bundle the validator to ensure your register is both technically compliant and legally verifiable.
Yes. If your contracts have already undergone a thorough manual legal review, you can license the automated validation engine for €2,000 per year to verify formatting, GLEIF data, and cross-template consistency prior to submission.
Yes. If file validation reveals inconsistencies or if your team requires statutory contractual reconciliation, 100% of your €2,000 validator fee is credited directly toward a Core or Enterprise engagement.
You submit a single, non-critical ICT vendor contract under a mutual non-disclosure and data processing agreement. We run our statutory parsing engine and return a concrete gap report with verbatim clause citations within 24 hours, proving the engine's precision before any commercial commitment.
Run your free Gap AuditResources
Short, practical explainers on what DORA asks for and how to close the gaps.
Get the clarity you need to navigate DORA — and the structure to act on it — with our step-by-step checklist.
What the regulation means for CSSF- and CAA-supervised firms and their ICT providers, with practical guidance on where the gaps usually sit.
LeDora maps ICT contracts to the DORA register fields, flags what is missing, and cites the verbatim contract text for what is there.
Get absolute certainty on your DORA register today, without changing how you work.
Tell us a little about your setup. We reply within one business day.