A completed Register of Information is the starting point for preparing a reporting submission.
The next step is to turn that information into the files required by the receiving authority. This involves checking the reporting scope, reference date, technical format, naming conventions and submission process.
The European reporting framework provides a common foundation. Firms also need to follow the instructions issued by their competent authority.
Understand the reporting framework and destination
The EBA publishes resources supporting DORA Register reporting, including the data model, technical package, validation rules, permitted values and sample reporting files. These help explain how Register information should be structured for reporting.
The submission route and file requirements should then be checked against the instructions of the authority receiving the firm’s Register.
This distinction matters because a common regulatory framework does not mean that every authority collects the information in an identical file format.
Confirm the scope and reference date
Before generating an export, establish which entity or group the submission covers and the date to which the information relates.
A working Register may have changed since the reporting reference date. New arrangements may have been added, existing services amended or contracts terminated.
A practical preparation process should establish which records belong in the submission and preserve a clear record of the information used to produce it.
The team preparing the files should also know who will review the export, who can submit it and who will monitor the feedback.
Prepare the reporting package and filenames
Where the destination requires an EBA reporting package, preparation involves more than saving individual tables as CSV files.
The relevant technical instructions explain the required package structure, supporting files and reporting conventions. The EBA preparation resources include sample files and material explaining how to prepare the CSV reporting package.
Check that the files belong to the same reporting scope and period, that required components are present and that names follow the applicable instructions.
An Excel workbook used for internal review should be clearly distinguished from the package intended for submission.
Ireland: preparing the package for the Central Bank
For the 2026 collection, the Central Bank of Ireland required an XBRL OIM CSV reporting package in accordance with EBA DPM 4.0, saved as a ZIP file and submitted through the Central Bank Portal.
Its guidance also addresses package naming requirements and the preparation steps needed for successful upload. Firms should use the latest instructions relevant to their reporting cycle.
The practical task is to prepare the required package and check that it can be submitted through the Portal in accordance with those instructions.
Austria: using the FMA template
For its 2026 collection, Austria’s FMA required its prescribed Excel template to be submitted through the Incoming Platform.
The FMA also permitted EBA codes in the template instead of the corresponding descriptive text. This illustrates how information based on the common European framework can be collected through a different national format.
Teams preparing an Austrian submission should therefore check the required template and its instructions rather than assume that a ZIP package prepared for another authority can be submitted unchanged.
Review feedback after submission
Submission is part of a process that can include technical checks, data quality feedback and resubmission.
For the 2026 cycle, the Central Bank of Ireland explained that additional EBA data quality checks could generate further feedback after the initial technical validation stage.
Keep the submitted files, feedback and subsequent corrections connected. This helps the team understand what was submitted, which issues were identified and what changed in a later version.
Where a finding reveals an issue in the underlying Register, addressing that source information also helps future reporting.
Make export preparation part of the Register workflow
Maintaining information, reviewing validation findings and preparing an export work best as a connected process.
Confirm the destination. Review the information. Prepare the submission.