Belgium: filing with the Nationale Bank van België / Banque Nationale de Belgique

xbrl-csv-xbrl-xml-csv-or-manual

Enum extended. DORA_ROI accepts: (1) xBRL-CSV report package (zip) upload, (2) xBRL-XML upload (OneGate XML envelope, no naming convention), (3) regular OneGate CSV import per form (no headers, ';' separator, 'Dora#' prefix for enumerated values), (4) manual data entry in the OneGate forms. 'all formats can always be exported from an empty or completed form (the Excel is restricted to output and not upload though)' – there is NO Excel upload/template. 'New = mandatory XBRL-CSV reporting from the NBB to the EBA (EUCLID system)'; 'EBA conversion tool of the dry-run not updated/supported for the steady-state'. Taxonomy: EBA Reporting Framework 4.0 (schemaRef http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/dora/4.0/mod/dora.xsd / .json); 'Submissions with other schemaRefs are rejected.'

source high confidence

OneGate – domain 'DOR' (Digital Operational Resilience Act), report 'DORA_ROI – DORA Register of Information' (other DOR reports: DORA_MIR, DORA_SCT, DORA_CONTACT, DORA_MIR_TEST)

url https://onegate.nbb.be

login prerequisites Access via CSAM (eID/itsme; MyGov added as CSAM option 8 Jul 2026) or an electronic certificate (GlobalSign, Isabel, QuoVadis, LuxTrust SmartCard). 'Access management has become the full responsibility of the declarer -> Administrator(s)'; roles per NBB certificate guide: administrator (needs the OneGate Admin Delegation Form), standard user, third party, auditor. First login asks for the KBO/CBE enterprise number; access confirmed by e-mail. The declarer is identified by KBO number with a '.IND' or '.CON' qualifier: 'identification and reporting are done using your unique company number (CBE) followed by an .IND/.CON extension' – switch the 'Active declarer' in OneGate (e.g. MCBIC1 [BIC-MCBIC1.CON] / [BIC-MCBIC1.IND]). Test/UAT environment needs its own credentials; 'You may use only one certificate per environment (test and production)' – a different certificate is needed for OneGate TEST and PROD; the test environment also offers username/password login. Contacts: access.onegate@nbb.be, +32 2 221 49 39 (access); BankRep@nbb.be (credit institutions, stockbrokers, PIs, EMIs, CSDs) / AssuRep@nbb.be (insurers) for OneGate; it.supervision@nbb.be for DORA content.

source high confidence

OneGate naming convention for xBRL-CSV zip-files (parameters separated by underscores): DeclarerType_DeclarerID.IND|CON_RecipientInstitution_OneGateDomain_OneGateReport_FreeText.zip, i.e. KBO_<10-digit CBE number>.<IND|CON>_NBB_DOR_DORA_ROI_<free text without underscores or special characters>.zip. Verbatim illustration: 'KBO_0123456789.IND_NBB_DOR_DORA_ROI_FreeText.is allowed.zip'

Example KBO_0123456789.IND_NBB_DOR_DORA_ROI_FreeText.is allowed.zip (protocol illustration); kbo_0123456789.con_nbb_dor_dora_roi.zip (NBB sample package file name)

Notes Differs from the ESA default: the NBB zip name is KBO/CBE-based and routes the file (recipient NBB, domain DOR, report DORA_ROI); the LEI appears inside parameters.csv ('entityID,rs:<identifier>.IND'). DeclarerType is 'KBO' (BIC or LEI are possible declarer types in OneGate generally). Free text: '! do not use special characters or underscores'. For xBRL-XML 'there is no naming convention'. 'HINT: a valid and representative xBRL-CSV document can be obtained by exporting an empty report from OneGate control panel.'

source high confidence

meta inf location Standard xBRL report package (Report Package 1.0 / https://xbrl.org/report-package/2023): FolderName/META-INF/reportPackage.json and FolderName/reports/{report.json, parameters.csv, FilingIndicators.csv, {table}.csv}. The protocol diagram shows a root 'FolderName' but does not state that it must equal the zip name.

wrapper None for xBRL-CSV (zip uploaded directly via 'Upload a file' / 'Choose XML/XBRL'). xBRL-XML must be wrapped in the OneGate XML envelope <XbrlDeclarationReport xmlns='http://www.onegate.eu/2010-01-01'> with <Administration><From declarerType='KBO'>0123456789.IND</From><To>NBB</To><Domain>DOR</Domain>... and <Report action='replace|update' code='DORA_ROI'>.

other rules

• 'In the context of DORA_ROI reporting, ALL tables must be submitted and reported. Therefore, positive filing indicator elements must be present for all tables, without exception.' Empty tables with a positive indicator get status 'nihil'; resulting warnings are not a concern (protocol v1.2).
• Entity identifier: scheme https://eurofiling.info/eu/rs with '.CON'/'.IND' qualifier (KBO, BIC or LEI based); for xBRL-CSV it sits in parameters.csv ('entityID,rs:CGYP50QBGGR6NCHTSN68.IND', 'refPeriod,2025-03-31', 'baseCurrency,iso4217:EUR', decimalsInteger 0, decimalsMonetary -3, decimalsPercentage 4, decimalsDecimal 2).
• CSV: first line = column codes (c0010,c0020,...), comma separator, escape the separator with double quotes ('"National Bank of Belgium , NBB"'), UTF-8.
• Typed dimensions (keys) may not be left empty – e.g. B_02.03 columns 0010 and 0020 both required (use '0' if not relevant).
• Do not report zero values unnecessarily; monetary unit iso4217:EUR; numeric values with '.' decimal separator; percentages as fractions (150% -> 1.5).
• Text keys are compared exactly ('abcd ' != 'abcd'); a validation rule against leading/trailing spaces was announced.
• action='replace' re-initialises the whole report; action='update' (default) only overwrites supplied values.

source high confidence

Notes NBB DOR-domain notice of 28 Jan 2026: DORA_ROI for reference date 31/12/2025 available in the TEST environment from 2 February 2026 and in PRODUCTION from 16 February 2026; 'The reporting deadline is March 13, 2026.' Entities should 'first submit their register in the OneGate TEST/UAT environment' and 'only submit their register in the PRODUCTION environment if it passes all validation checks'. No correction window or extension published; reports must be 'closed' in production. 2025 first cycle for comparison: test 20 Feb 2025, production 1 Apr 2025, deadline 30 Apr 2025 (reference date 31/03/2025), ESA dissemination from 15 Apr 2025. Production outage 19–22 Jun 2026 (unrelated to RoI).

reference date 2025-12-31

opens 2026-02-16

deadline 2026-03-13

source high confidence

reference date 2026-12-31

esa transmission deadline 2027-03-31

announced no

changes Nothing about 2027 on the NBB DOR-domain page as of 2026-10-31 (latest notice 3 Jun 2026). Webinar: 'Frequency: normally yearly'. Unless amended.

source high confidence

OneGate TEST/UAT environment: DORA_ROI (ref. 31/12/2025) available from 2 February 2026 (production 16 February 2026); NBB asks entities to submit in TEST first and only go to PRODUCTION once all validation checks pass. 'Attention: a different certificate is needed for OneGate TEST and OneGate PROD.' Test submissions are not kept. 2025: test opened 20 Feb 2025 (about 2 months before the reference date).

available yes

source high confidence

Submission is completed by closing the report ('Close and send'): 'Each report must be officially closed; this is only possible when no initial or erroneous forms are left. An institution that closes the report is assumed to have approved the figures and its comprehensiveness. The closing event is registered with a time stamp, after which all report forms become read-only'. 'A report can only be closed in OneGate in case no errors are left in both validation reports.' 'Finally, don't forget to close the report (in production environment).' Re-opening after closing requires contacting the prudential supervisor.

roles OneGate declarer users (administrator / standard user / third party / auditor); no four-eyes approval described.

source high confidence

format OneGate 'Uploads' / file-exchange log per ticket: 'Exchange status' (e.g. Accepted - OK), 'Dissemination status' (EBA/EUCLID result: Refused or Accepted - OK) and 'Feedbacks' files feedback.xml and disseminationFeedback.xml; in the control panel per form: validation.xml, dissemination.xml, validation.html via 'Validation report'; form statuses Initial / Open - OK / Open - Warning / Closed; EBA feedback e-mail optional via the XML envelope <Response feedback='true'><Email>.

timing NBB validation immediate on upload; EBA dissemination feedback 'is not in real-time available because of these EU-ID checks' – 'EBA estimates that the validation process on their side can take up to one day'. Data-quality feedback on third-party LEI/EUID was only available in OneGate after 15 April 2025 in the first cycle. Nightly maintenance 02:00–04:00 and Sundays 08:00–12:00: no validation/processing.

resubmission Upload again (xBRL action 'update' keeps unsent values, 'replace' re-initialises); fix in TEST first, then PROD; reopen a closed report via the supervisor. Validation rules come from both NBB and the ESAs (checked in TEST/UAT).

source high confidence

true

Webinar (10 Dec 2024): 'Identification of financial entity with LEI-code will be mandatory for both reportings' (RoI and incidents). 'OneGate is checking the syntax-structure (pattern) of LEI-codes and EU-IDs'; 'EBA will check the existence of LEI-codes and EU-IDs' (GLEIF, BRIS). Note the declarer itself is identified in OneGate/file name by KBO number, the LEI goes in the data (B_01.01/B_01.02, parameters.csv when LEI-based). No published fallback for an entity without LEI.

source high confidence

Less significant credit institutions, stockbrokers, (re)insurance undertakings, payment institutions, e-money institutions, CSDs (webinar: 'Scope: LSIs, stockbrokers, (re)insurance undertakings, PIs, EMIs and CSDs'); Significant institutions via the ECB collection ('SIs via ECB collection'); Registers requested at the highest level of consolidation under NBB supervision; disseminated to EUCLID only if no higher EU consolidation level elsewhere; Out of scope examples: third-country branches, insurance undertakings exempted from Solvency II

source high confidence