Belgium: filing with the Autoriteit voor Financiële Diensten en Markten / Autorité des services et marchés financiers
xbrl-csv-or-manual. Example filename: 123456X7Y8Z9ABC0D123.IND_BE_DORA010100_DORA_2025-12-31_20260310101500000.zip.
| Accepted formats | xbrl-csv-or-manual Enum extended. Two routes: (1) manual completion of the 15 models in the DORA_ROI survey, after which 'zorgt de FSMA voor een rapportering in xBRL-CSV formaat naar EUCLID'; (2) upload of the complete ESA 'reporting package Zip file' (xBRL-CSV) via Import > Zip File. No Excel template: 'Er is geen Excel-template van het informatieregister voor conversie naar xBRL-CSV voorzien, zoals bij de dry run in 2024.' and the EBA dry-run conversion tool is not supported. Including an Excel version of the ROI inside the zip is listed as a common import error. 2026: entities with no changes 'can reload last year's data with one click and confirm that the situation is unchanged'; otherwise update manually or upload a zip in the ESA format ('een CSV-bestand met filling indicators en technische JSON-bestanden in één zip-bestand'); 'De technische specificaties van de FiMiS Survey blijven ongewijzigd.' Validation rules = ROI 2025 rules per ESA documentation. source high confidence |
|---|---|
| Portal | FiMiS (FSMA reporting platform) – tab 'My eDossier' > survey 'DORA_ROI – Register of Information (ROI) Reporting' (the survey is pre-created; entities do not create a new survey as they do for DORA_INCIDENT/DORA_CYBERTHREAT) login prerequisites The contact persons designated for reporting major ICT incidents and cyber threats are also the FiMiS contact persons for the register ('De contactpersonen die ... werden aangeduid ... werden ook opgenomen als contactpersonen in FiMiS voor het informatieregister'). Access works as for the DORA_INCIDENT/DORA_CYBERTHREAT surveys: FiMiS login with strong authentication per the FSMA 'User guide for strong authentication'; keep login details up to date; access removal via dora@fsma.be; technical login problems: servicedesk@fsma.be; content questions: dora@fsma.be. A test host 'fimis-test.fsma.be' appears in FSMA screenshots. source high confidence |
| File naming | ReportSubject.CON/.IND_Country_FrameworkCodeModuleVersion_Module_ReferenceDate_CreationTimestamp.zip – 'ReportSubject de LEI code van de rapporterende reporting financial entiteit is; CON/IND aangeeft of er geconsolideerd (CON) of individueel (IND) gerapporteerd wordt; Country de tweeletterige ISO code van het land van de financiële entiteit is; FrameworkCodeModuleVersion DORA 010100 is; Reference date de referentiedatum is ... geschreven als 2025-03-31; CreationTimestamp de tijdsaanduiding is wanneer het bestand gecreëerd werd.' FiMiS upload error text verbatim: 'To report DORA_ROI, you must provide a file with a filename following the pattern: <LEI>.<CON/IND>_BE_DORA010100_DORA_<report date: yyyy-MM-dd>_<timestamp: yyyyMMddHHmmssfff>.zip' Example 123456X7Y8Z9ABC0D123.IND_BE_DORA010100_DORA_2025-12-31_20260310101500000.zip (constructed from the FSMA pattern for the 2026 cut-off date 31 Dec 2025; the FSMA 2025 document itself only shows the 2025 reference date 2025-03-31) Notes ESA-standard naming (LEI-based), country token 'BE'. 'De LEI-code die gebruikt wordt in de benaming van de volledige reporting package Zip file moet overeenkomen met de LEI-code van het dossier (m.a.w. de onderneming waarvoor u rapporteert) en met de LEI-code die vermeld wordt in het bestand Parameters.csv'; otherwise the pattern error above is shown on 'upload'. For a consolidated upload the top entity's LEI must be in both the zip name and parameters.csv. ESA FAQ #24 referenced. source high confidence |
| Packaging | root folder must equal zip name yes meta inf location Root folder (named per the naming convention) containing sub-folder 'META-INF' with reportPackage.json and sub-folder 'reports' with report.json, Parameters.csv, fillingIndicator.csv and {table}.csv. Verbatim: 'Folder met naam volgens naamconventie – Sub-folder META-INF met ... reportPackage.json – Sub-folder reports met ... report.json, Parameters.csv, fillingIndicator.csv, {table}.csv'. 'Indien deze structuur niet aanwezig is in de Zip file zal de import geweigerd worden in FiMiS.' Most common error: 'Een incorrecte structuur van het reporting package (in Zip file), waarbij het eerste niveau (een folder met dezelfde benaming als de Zip file en die de folders Meta-inf en Reports bevat) vaak vergeten wordt'. wrapper None – zip uploaded directly in FiMiS (Import > Zip File > select survey 'Register of Information (ROI) Reporting', dossier, file, Upload). other rules
source high confidence |
| 2026 cycle (reference date 31 Dec 2025) | Notes FSMA news 17 Feb 2026 ('DORA-informatieregister ... beperkte update 2026'): 'De ROI moet uiterlijk op 20 maart 2026 worden ingediend.' 'De referentiedatum van de gegevens (cut-off date) is 31 december 2025.' Limited scope (only the entity types listed under sectors); unchanged entities confirm 'no change' with one click; FiMiS technical specifications and validation rules unchanged from 2025; FSMA_2025_02 remains valid 'tenzij anders vermeld'. No opening date, correction window or extension published for 2026. 2025 first cycle for comparison: FiMiS open 1–30 April 2025 (deadline initially announced as 10 April 2025 in Jan 2025), EUCLID forwarding from 14 April, ESA feedback and corrections until 15 May 2025, EUCLID closed 31 May 2025; collection declared closed on 9 Jul 2025 ('Nearly all financial entities under the FSMA's supervision successfully carried out this exercise'). reference date 2025-12-31 deadline 2026-03-20 source high confidence |
| 2027 cycle (reference date 31 Dec 2026) | reference date 2026-12-31 esa transmission deadline 2027-03-31 announced no changes Nothing published by the FSMA about 2027 as of 2026-10-31. Unless amended. source high confidence |
| Test window | 2025 FAQ 4.4: 'De FSMA zal niettemin haar uiterste best doen om een korte testperiode te voorzien, maar zij kan dit niet garanderen.' Entities interested in testing an xBRL-CSV upload were asked to e-mail dora@fsma.be. A test host fimis-test.fsma.be exists (screenshot). Nothing published on a 2026 test window. source high confidence |
| Sign-off | Workflow: 'Validate & Save' per section; when all sections are 'Ok' or 'Nihil', click 'Submit the Survey'; pop-up (from fimis-test.fsma.be): 'Once the survey has been submitted, if it's free of errors, the survey will become read only. Are you sure?'. Submission then goes automatically to EUCLID. FSMA re-opens the survey by e-mail request if the ESAs ask for corrections. No maker/checker. two user no roles FiMiS contact persons of the entity (same as for DORA_INCIDENT/DORA_CYBERTHREAT); a single user validates and submits. source high confidence |
| Feedback | format In FiMiS a 'validation report' per survey/section with errors (blocking: 'Errors zijn blokkerend. U moet ze verbeteren om de survey te kunnen indienen.') and warnings (non-blocking); section statuses Initial / Error / Warning / Ok / Nihil. ESA/EUCLID feedback is relayed by the FSMA by e-mail ('De FSMA zal de financiële entiteiten zo vlug als mogelijk per mail op de hoogte brengen indien de ESA's nog te corrigeren punten ontdekken'), naming the columns to fix, and the survey is re-opened. Upload result banner shows the file-name pattern error when the LEI does not match. timing FiMiS validation is immediate on upload/'Validate & Save'. 2025: ESAs sent a feedback report to the FSMA the day after submission (one check – EU-ID – is manual); corrections were due by 15 May 2025. resubmission Fix manually in the survey or upload a new reporting package zip that overwrites the previous one ('U kan ook een nieuwe reporting package ZIP file opladen die de vorige overschrijft'); after ESA feedback the FSMA re-opens the survey for correction and re-submission. EUCLID warnings that already existed at submission re-appear as warnings in FiMiS and should be cleared. source high confidence |
| LEI required | true Verbatim: 'Opgelet, als financiële entiteit heeft u een LEI-code nodig om het informatieregister te kunnen indienen. Er zijn verschillende verstrekkers van LEI-codes die u makkelijk online kan terugvinden.' (GLEIF). The LEI must match the FiMiS dossier, the zip name and parameters.csv. FiMiS also pattern-checks the LEI format ('Invalid LEI code' blocks submission; blanks around the LEI cause errors). No fallback published for an entity without LEI. source high confidence |
| Who files here | 2026 'limited update' scope: marktondernemingen (market operators), vennootschappen voor vermogensbeheer en beleggingsadvies (portfolio management and investment advice companies), beheervennootschappen van ICB en AICB (UCITS/AIF management companies), zelfbeheerde ICB's (self-managed UCIs); Not required to submit in 2026 (must still keep an up-to-date register the FSMA can request): verzekeringstussenpersonen (insurance intermediaries), instellingen voor bedrijfspensioenvoorziening (IORPs), crowdfundingdienstverleners; Entities also supervised by the NBB (e.g. intermediary that is also a credit/payment institution) file with the NBB, not the FSMA; groups: only the register at the highest (sub)consolidation level under FSMA supervision, covering only FSMA-supervised entities source high confidence |
| Quirks | Manual entry is a first-class route: the FSMA itself produces the xBRL-CSV for EUCLID, so small FSMA-only entities need no xBRL tooling at all.; 2026 was a 'limited update': only four entity types had to file; unchanged entities confirm last year's data with one click; insurance intermediaries, IORPs and crowdfunding providers were exempted from filing.; FSMA deadline (20 March 2026) is one week after the NBB deadline (13 March 2026); Belgian dual-status entities file with the NBB only.; B_99.01 definitions: entities must state their own interpretation of drop-down values used in B_02.01.0020, B_02.02.0170, B_06.01.0110, B_07.01.0050, B_07.01.0090, B_07.01.0100.; FSMA table of ESA instructions that deviate from the ITS text (B_01.02.0050 drop-down, B_01.02.0060 own LEI if no parent, B_02.01.0030 'Not Applicable', B_02.02.0050 one line per function, B_02.02.0130 country of provision, B_04.01.0040 'Not Applicable', B_05.01.0110, B_05.02.0010/0060, B_06.01.0040, B_07.01.0020).; ESA exceptional instruction: register the financial entity only in B_01.01 when its whole activity (incl. ICT) is performed by another entity (ITS recital 7); financial services with an ICT component provided by another financial entity are not ICT services (EIOPA Q&A 2999 DORA030). |
| Notes | Solid for process and packaging (FSMA_2025_02 read in full) and for the 2026 deadline/scope (FSMA news). Gaps: FiMiS production URL not stated verbatim in the sources read (only the test host fimis-test.fsma.be appears in a screenshot), 2026 opening date, size limit, 2027. The FSMA 'User guide for strong authentication' was not located. accepted_formats.value uses 'xbrl-csv-or-manual' (outside the given enum). |
Error codes this portal shows
| filename pattern | To report DORA_ROI, you must provide a file with a filename following the pattern: <LEI>.<CON/IND>_BE_DORA010100_DORA_<report date: yyyy-MM-dd>_<timestamp: yyyyMMddHHmmssfff>.zip |
| [Value should not be missing] | Value should not be missing |
| [Invalid LEI code] | Invalid LEI code |
| [Reference value not found] | Reference value not found (ESA equivalent: The reported data must follow the key-foreign key constraints defined in the DPM) |
| [The key value needs to be unique] | The key value needs to be unique (ESA equivalent: For open tables, you cannot have multiple rows with identical key values) |
| [Warning missing fields] | Warning missing fields |
| zip structure | Indien deze structuur niet aanwezig is in de Zip file zal de import geweigerd worden in FiMiS. |
The authority's own documents
- FSMA_2025_02 – Mededeling over het DORA-informatieregister (versions 05/03/2025, 24/03/2025, 15/04/2025, 02/05/2025; 22 pp.) (2025-03-05 (last updated 2025-05-02))
- DORA-informatieregister over derde aanbieders van ICT-diensten: beperkte update 2026 (news) (2026-02-17)
- DORA Register of Information on third-party ICT service providers: limited update in 2026 (EN stub) (2026-02-17)
- Nadere toelichting bij het opvragen van het informatieregister over derde dienstaanbieders en over meldingen van ernstige ICT-incidenten (news) (2025-01-21)
- DORA Regulation: collection of information registers on third-party service providers closed (news) (2025-07-09)
- Praktijkgids DORA – Melding van ernstige incidenten en significante cyberdreigingen (FiMiS access, surveys; version 12-01-26) (2026-01-12)
- FSMA FAQ – Beheer van de risico's verbonden aan derde aanbieders van ICT-diensten (undated)
- 2026 schematic overview image (2026-dora-schema.png, not read) (2026-02-17)
Compiled from the authority's published guidance on 31 October 2026, with a source and confidence per field. Low confidence means the authority has not published it in writing and the statement is an inference from standing rules or a third party. Check the authority's page before the window opens, and send corrections to hello@roifile.com.