Turn your DORA workbook into a submission-ready xBRL-CSV package.
Your team completes the workbook in Excel. We take over template matching, DORA rule checks, FAQ clarifications, online registry checks, xBRL-CSV package assembly, and archive self-checks so you can get to a submission-ready ZIP without owning specialist XBRL tooling.
Currently validating against EBA RF 4.0 / DORA module 4.0 · release 4.0.0.0. Findings are source-backed, generated packages are re-checked before release, and workbook data is processed only for the active session. Built for teams that know their data, do not want to own the XBRL mechanics under deadline, and want the reporting mechanics handled for them.
Your team
Complete the workbook, review the findings, and decide the reporting content.
We handle
Validation logic, source-backed guidance, registry checks, and package generation.
You keep control
Download the final ZIP and submit it yourself through the regulator portal.
You can drag and drop your workbook anywhere on this page, or use the contact page if you want help before the first upload.
One workbook, one fee, one route to submission-ready output
For €799, one workspace carries one workbook from first upload through repeated validation to final package download. That includes unlimited validation reruns, one xBRL-CSV package build, optional online registry checks, package self-checks, traceable findings, and direct support when a filing needs review or a deadline gets tight.
Validation
Unlimited
Package build
1 included
Workbook retention
None
Support
Direct
Start with the supported workbook, keep your team in Excel, and let us handle template matching, official value lists, cross-sheet links, and DORA rule checks instead of rebuilding that logic in-house. Findings are written so a reporting team can review and act on them quickly.
Session-based processing, optional GLEIF and VIES evidence checks, package self-checks before release, and direct help when a filing needs judgment or a package needs to get over the line quickly. If the AFM rejects your submission, one free rebuild after a phone call with our team.
From workbook to package, without XBRL tooling
Keep the workbook workflow familiar for your team. You stay responsible for the reporting content in Excel; we take over the template matching, validation logic, and package-building work that usually consumes the most time and creates the most deadline pressure.
Download the supported workbook
Start with the supported .xlsx template. The sheets, columns, dropdowns, and field references already match the active DORA ruleset.
Complete it in Excel
Stay in a familiar Excel workflow. The template highlights required cells, explains tricky fields, and shows official dropdown values with both the plain-language label and the EBA code so your team can focus on the reporting content, not the package format.
Upload and review findings
Upload the workbook and we take over structure checks, required fields, official value lists, cross-sheet links, identifier hygiene, country consistency, published DORA rules, EBA FAQ clarifications, and optional online LEI and VAT checks. Each finding explains what is wrong, what to do next, and where the rule comes from so you can fix the workbook and re-run confidently.
Generate the package
When the workbook is ready, we assemble the xBRL-CSV package, re-check the archive and metadata, and return the ZIP for download in the active session. Your team keeps control of the final submission.
One review across the full DORA filing surface
Every upload is checked from workbook intake through package integrity. We cover the structure, relationships, rules, optional registry checks, and final archive quality in one run.
Template coverage
15
DORA templates checked in every run
Published rules
58
EBA business rules applied to the workbook
Enforceable checks
103
validation checks across structure, logic, and references
Package assurance
28
package checks before the archive is released
Each finding is grouped by template and field, linked back to its source, and written to tell reporting teams exactly what to fix next.
All 15 DORA templates in one run
We parse every sheet, match headers to the supported template, and catch missing or extra tabs before deeper validation begins.
Required fields, formats, and official value lists
We check required cells, dates, numbers, booleans, identifiers, max lengths, placeholder values, and official EBA code lists.
Cross-sheet links and key consistency
We trace identifiers and linked combinations so entities, providers, functions, contracts, and branches stay connected correctly across the filing.
58 published rules plus 103 enforceable checks
We combine the published DORA rule inventory, EBA FAQ clarifications, and locally enforceable checks in one review, with findings grouped by template and field.
Package and archive quality
Before the ZIP is offered, we validate 19 required files, 28 package checks, metadata, filing indicators, UTF-8 encoding, and archive integrity.
Optional online LEI and VAT checks
When enabled, we check LEIs against GLEIF for existence, status, legal name, and country consistency, and VAT numbers against VIES with mismatch and outage handling where relevant.
Everything traceable to official sources
We base validation decisions on EU and EBA materials so your team has a clear audit trail and a documented basis for review.
EBA DORA preparation page
Official EBA hub for filing rules, CSV guidance, FAQ updates, and supporting materials.
EBA Reporting Framework 4.0
Reporting Framework 4.0 source page with the validation workbook, taxonomy artifacts, and release materials.
AFM DORA register notice
AFM notice on the DORA register of information submission requirement, including the March 2026 deadline and the xBRL-CSV format obligation.
DNB reporting notice
Dutch supervisory context for institutions reporting DORA registers in the Netherlands.
GLEIF API
Public GLEIF documentation for the online LEI checks used in validation.
VIES technical information
Official EU VIES documentation for the online VAT checks used when identifier fields contain VAT numbers.
Technical conformance is the last 10%. We cover the other 90.
Arelle checks whether an xBRL-CSV package is technically valid: correct dimensions, datatypes, filing indicators. That matters, but it runs after the package already exists and says nothing about the data inside it. Business rules, cross-template references, identifier existence, required-field completeness, and country logic are invisible to Arelle. We validate all of that at the Excel level, generate the package, and re-check the archive before it reaches your team.
| Arelle-only tools | DORA V&C This product | |
|---|---|---|
| Starting point | Not included: Requires a finished xBRL-CSV package | Included: Upload an Excel workbook. Validation and package generation are handled for you |
| DORA business rules | Not included: Not checked | Included: All 58 published EBA rules applied to the data before the package is built |
| Cross-template links | Not included: Not covered | Included: Contract, entity, function, and branch references traced across all 15 templates |
| Identifier checks | Not included: Not covered | Included: LEIs verified against GLEIF (status, legal name, country), VAT numbers checked via VIES, format and cross-template consistency enforced |
| Required fields & value lists | Not included: xBRL datatype constraints only | Included: Required-cell completeness, max lengths, placeholder detection, and official EBA code lists checked at the Excel level |
| EBA FAQ clarifications | Not included: Not included | Included: 8 EBA FAQ clarifications applied as validation checks where they tighten or explain the published rules |
| Actionable findings | Not included: Technical xBRL error codes | Included: Findings grouped by template and field, labeled by source, with an explanation of what is wrong and what to fix next |
| Package generation | Not included: You assemble it yourself | Included: Full xBRL-CSV ZIP with 19 required files, filing indicators, report metadata, and 28 archive checks before release |
| Supported template | Not included: Not provided | Included: Downloadable .xlsx workbook with sheet structure, dropdowns, field references, and EBA codes already in place |
| Support & guarantee | Not included: Self-service or community | Included: Direct team access before and after purchase, deadline support, and a free rebuild if the AFM rejects your submission |
Clear ownership, direct support, visible accountability
We built this platform for reporting teams that want a clear owner, direct access to the team, and decisions that are easy to trace.
Public product domain: dora-convert.com.
Validation decisions are designed to be traceable to official EU and EBA sources.
Findings are grouped by template and field and labeled so teams can review them without a black-box workflow.
Generated packages are re-checked before release.
No separate XBRL toolchain is needed to get from workbook to package in this workflow.
Workbook data is processed for the active session and is not kept afterward.
Edge cases are treated as product work, not as exceptions to ignore.
When a filing needs a second pair of eyes, you can reach the team directly before purchase, before upload, or close to deadline.
Need help before upload or after validation?
We help with workbook blockers, difficult findings, deadline pressure, package questions, privacy reviews, and pre-purchase questions when a team wants to sanity-check the workflow first.
Contact page
Open contact pageIf the filing is complex, time-sensitive, or needs a second pair of eyes, contact us early so we can reduce risk before the deadline gets tight.
Frequently asked questions
What does the platform handle for us?
We handle workbook structure checks, official value lists, published DORA rules, FAQ clarifications, cross-template links, identifier hygiene, country consistency, package checks, and plain-language findings. Optional online GLEIF and VIES checks add live registry evidence where those identifier types are used. That means your team can stay in Excel while we take care of the validation and package mechanics that normally need specialist tooling.
How do we know what the platform is checking?
The active ruleset is shown in the product, findings are grouped by template and field, and each finding is labeled by source category so your team can review what was checked and why. The workflow is designed to be understandable, not opaque.
What still stays with our team?
Your team remains responsible for the workbook content, the business decisions behind the data, reviewing warnings, and submitting the final package through the regulator's portal. We take over the validation, explanation, and package-generation mechanics around that process.
When do we pay, and do we pay again for reruns?
The workspace is activated once per workbook. After that, you can upload fixes and validate again as often as needed. The workspace includes one xBRL-CSV package build. If the AFM rejects your submission, you get a free rebuild.
How do you handle privacy and GDPR / AVG expectations?
Uploaded workbooks are processed only for the active session. We do not keep workbook data in a database, and the workflow is designed around data minimization and storage limitation. The generated package is held only as a temporary, time-limited download and is removed when that link expires. If you ask us to email the package to you, that address is used only to send that one message and is not stored.
Can we get help from a real person?
Yes. Use the contact page if you want a quick go/no-go check before buying, help before upload, support after validation, or a second pair of eyes close to a filing deadline.
Ready to get started?
Loading service information...