Frequently asked questions
Short answers on scope, pricing, privacy and validation. Still unsure? Email us.
It validates your DORA workbook, explains each finding in plain language and builds the xBRL-CSV package. Your team stays in Excel.
The workbook content, the decisions behind it, reviewing warnings, and submitting the package through the regulator's portal.
You buy one access code per reporting entity: the LEI in B_01.01 of the first workbook you validate. It includes unlimited validation runs and one package build, so re-runs cost nothing extra.
Email us with the reason "AFM rejected the package" and your payment ID. We reply within one business day and rebuild the package once, free of charge. The same free rebuild covers a download that expired before you saved it.
Workbooks are processed only for the active session and never stored in a database. The package is a temporary download that expires. An address you give for emailing the package is used once, not stored.
Yes. Email us before buying, before your first upload or while fixing findings. We reply within one business day.
No. We build and check the package; your team submits it through the regulator's own portal.
A package validator checks a finished xBRL-CSV file for technical conformance. We first check the data in your workbook (business rules, cross-template links, LEI and VAT evidence), say which field to fix, then build and re-check the package.
The AFM names four points: it produces xBRL-CSV, not iXBRL; it supports the EBA taxonomy; it runs data-quality checks straight away; and you know what the provider does with your data. Our checklist maps each point to what we do.
The ZIP of CSV files and report metadata that regulators expect for DORA submissions. We generate it from your workbook, so you need no XBRL tooling.
Yes. After building it, we check the ZIP against the EBA's structure rules: the file name, the folder, the required files, the filing indicators, the parameters and each template CSV. A package that fails is not offered for download.
All 15 templates, B_01.01 to B_07.01 plus B_99.01. Each is validated on its own and against the others, using the EBA Reporting Framework 4.0 taxonomy.
The service currently validates against EBA RF 4.0 / DORA module 4.0. Later EBA framework releases are adopted once they apply to DORA reporting.
58 published DORA business rules and 103 validation checks, including EBA FAQ clarifications. Each finding is labelled with its source.
Each finding names the template and field, says whether it blocks the package, and cites the official source it comes from, such as an EBA rule code or FAQ question. The converter also shows the ruleset it validates against.
Identifier formats, EUID and VAT country prefixes, placeholders, and name or country mismatches across templates. With online checks on, LEIs are verified with GLEIF and VAT numbers with VIES.
Warnings usually do not block the package build. Review them before you submit, especially those about registry checks.
.xlsx, .xlsm and .xlsb. Starting from our .xlsx template is the safest option.
The package is a temporary download in your session. You can also have it emailed: attached when small enough, otherwise as a temporary link.
CDCT, a company in Papendrecht, the Netherlands, registered with the KvK under number 87669234.