Netherlands: filing with the Autoriteit Financiële Markten
xBRL-CSV only. Example filename: DUMMYLEI123456789012.IND_NL_DORA010100_DORA_2025-12-31_YYYYMMDDHHMMSSsss.zip.
| Accepted formats | xbrl-csv-only 'Nee. Vanaf 2026 moeten de informatieregisters bij de AFM worden aangeleverd in het xBRL-CSV-formaat. Excel wordt niet geaccepteerd.' The 2025 Excel-to-xBRL-CSV conversion was a one-time service. Converter must produce xBRL-CSV (not iXBRL) and support the EBA taxonomy; the AFM is vendor-neutral and sees paid and free open-source converters. source high confidence |
|---|---|
| Portal | AFM Portaal - 'rapportageverplichting' (reporting obligation) for the register of information url https://portaal.afm.nl/ login prerequisites AFM Portal account; the formal information request (December 2025) explained the submission route. source high confidence |
| File naming | ESA convention: <LEI>.IND|.CON_NL_DORA010100_DORA_<yyyy-mm-dd>_<YYYYMMDDHHMMSSsss>.zip Example DUMMYLEI123456789012.IND_NL_DORA010100_DORA_2025-12-31_YYYYMMDDHHMMSSsss.zip (AFM Q&A, with entityID 'rs:DUMMYLEI123456789012.IND') Notes AFM checks only two things at upload: that the LEI matches its records and the naming convention. Each resubmission must have a different file name: 'adjust the last digits of the file name (timestamp)'. source high confidence |
| Packaging | root folder must equal zip name yes meta inf location ESA structure (AFM points to the EBA sample DUMMYLEI123456789012.CON_FR_DORA010100_DORA_2024-12-31_20241213174803429 in sample_documents.zip 'instances xBRL-CSV') timestamp uniqueness new timestamp per resubmission other rules
source high confidence |
| 2026 cycle (reference date 31 Dec 2025) | Notes Q&A session March 2026 (two hours); EBA acceptance rate rose from 40% (2025) to 94% (2026) (AFM DORA update 7, Aug 2026). AFM configured automatic forwarding to the EBA and automatic retrieval of feedback so firms could resubmit as often as needed. reference date 2025-12-31 opens Formal request issued December 2025 (announced 4 Nov 2025) deadline 2026-03-31 (originally 22 March 2026; extended by one week on 12 Mar 2026: 'De eerste aanlevering dient uiterlijk 31 maart 2026 afgerond te zijn in het AFM-portaal') corrections until 2026-04-30 ('Correcties ... (resubmissions) zijn welkom tot 30 april'; only if a first version was filed by 31 March) extension 22 Mar -> 31 Mar 2026 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 on 2027 in AFM's RoI page (last modified 6 Oct 2026) or DORA update 7 (Aug 2026). AFM and DNB participate in European working groups evaluating the annual request (proportionality signals passed on). source medium confidence |
| Test window | No test environment; AFM's answer is iterate: 'U kunt zo vaak mogelijk aanleveren als u wil'. source high confidence |
| Sign-off | Upload in the rapportageverplichting -> AFM forwards unchanged to the EBA -> EBA feedback posted back as a .txt in the same obligation -> obligation reopened for a new submission. roles AFM Portal user; no second-user sign-off described. source high confidence |
| Feedback | format .txt file in the AFM Portal reporting obligation (EBA feedback relayed) timing 'normaliter binnen 1 werkdag', exceptionally 2 days; contact dora@afm.nl if longer resubmission unlimited; obligation reopened once feedback uploaded; new file name (timestamp) required source high confidence |
| LEI required | true AFM validates that the reporting entity's LEI matches its system; mismatch -> contact DORA@afm.nl. Providers without LEI/EUID: legal persons may use another identifier (flagged as DQ issue, not rejected); natural persons KVK/tax/passport number. source high confidence |
| Who files here | Entities for which the AFM is the competent DORA supervisor: investment firms, UCITS/AIF managers, trading venues, data reporting service providers, crowdfunding service providers, CASPs (conduct), and others not prudentially supervised by DNB; entities file individually unless the group parent is supervised by another EU authority source high confidence |
| Quirks | Hierarchy of authority when feedback contradicts the ITS: EBA FAQ first, then the DORA Data Point Model, then the ITS.; Resubmitting the 2025 package unchanged 'will most likely lead to error messages'; use it only as a basis. No DPM changes versus 2025.; B_06.01: a function identifier cannot be repeated for different licensed activities; create a unique identifier per (LEI B_06.01.0040, function B_06.01.0030, licensed activity B_06.01.0020).; Scope answers: intra-group ICT services are recorded like any other; subcontractors included where their failure would endanger security/continuity; digital advertising platforms with a contract are in scope; free services without a contract are not. |
| Notes | Contact dora@afm.nl. AFM forwards registers unchanged to the ESAs and uses the data for its own data-driven supervision. |
Error codes this portal shows
| AFM: LEI mismatch / naming check | De enige validatie die de AFM doet bij aanlevering is of de LEI-code van de rapporterende entiteit overeenkomt met wat in ons systeem staat en een controle op de naamgevingsconventie. (The only validation the AFM performs on submission is whether the reporting entity's LEI matches our records, and a check of the naming convention.) |
The authority's own documents
- Q&A-sessie DORA-informatieregister (March 2026) incl. table of frequent error codes (2026-03)
- Q&A after Q&A session March 2026 (English) (2026-03)
- Register of information DORA (web page) (2026-10-06)
- News: Request for DORA Register of Information in December 2025 (2025-11-04)
- News: Q&A session DORA register of information (deadline extended to 31 March 2026) (2026-03-12)
- DORA update 7 (Aug 2026): 40% -> 94% EBA acceptance (2026-08)
- Instruction template register of information (2025 Excel route, superseded) (2025)
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.