Workflow
DORA / CSSF Register of Information package
How OneComply prepares explicit EBA table source rows, validates the official RoI table set, and generates the plain XBRL-CSV ZIP package for CSSF/eDesk upload.
Official tables
15
EBA DORA RoI table set B_01.01-B_99.01
Package format
ZIP
Plain XBRL-CSV layout with report metadata
Tenant scope
Org
Source rows and export packages are org-scoped
Submission
External
CSSF/eDesk receipt evidence is recorded separately
What OneComply Generates
OneComply generates the DORA Register of Information package using the EBA plain XBRL-CSV structure: metadata, filing indicators, parameters, and all 15 official data table CSV files. The output is a ZIP package for customer upload through the competent-authority channel, such as CSSF eDesk in Luxembourg.
The generator uses explicit source rows keyed by official EBA table IDs and column IDs. It does not infer regulator-controlled values from generic vendor fields.
Dashboard Workflow
- Confirm the organization LEI and CSSF eDesk readiness in
Settings. - Open
Dashboard → CSSF → ROI Submission. - Paste or import official EBA source rows in the source-row panel.
- Review validation errors by table.
- Generate the official-format ZIP package when validation is clean.
- Upload the package through CSSF/eDesk and record receipt/reference evidence externally in OneComply.
Validation Boundary
- Unknown official table IDs are rejected.
- Unknown table columns are rejected.
- Required official cells must be present for populated rows.
- Date and boolean cells use strict formats.
- Package generation fails closed if required source tables are empty.
No automatic authority submission