Denmark: filing with the Finanstilsynet

xbrl-csv-only

“For EBA-indberetninger vil der være krav om et nyt format til indberetningerne: XBRL-CSV.” Load Files guide: “Indberetningsfiler, der forberedes til EBA … skal være i filformatet xBRL-CSV”. e-Reg also has a generic “Forms” route (guide 5, “Indberetninger via Forms”) and the Load Files guide describes upload as an alternative to keying data “direkte i e-Reg”, but Finanstilsynet's DORA page does not state whether web forms or Excel import are offered for the RoI; Finanstilsynet publishes no Excel RoI template.

source high confidence

e-Regulatory (e-Reg), Finanstilsynet's portal for ESA-related reporting (Regnology platform), entered from Finanstilsynets Selvbetjeningsportal (e-Reg / OAM). RoI module name in e-Reg: “DORA” (comment “DORA (ROI)”), reporting level CON or IND. “Selve indberetningen skal foretages via systemet e-Reg.” (The reporting itself must be made through the e-Reg system.) In 2025 the register was filed via FIONA Online (last FIONA reference period 31-03-2025).

url https://portal.finanstilsynet.dk/

login prerequisites 1) Create a personal account in the Selvbetjeningsportal with MitID Erhverv (strongly recommended, “ikke privat MitID”, set up “fra dag til dag”) or, for those without MitID, the “Log ind som udenlandsk bruger” MFA route (slower; an extra emailed code may be required). At MitID login choose “Log på som erhvervsbruger”. 2) Obtain e-Reg reporting rights: either request them under “Mine rettigheder” in the portal and have the company's e-Reg brugeradministrator approve, or — if the company has no administrator — submit the Word application form signed by a “tegningsberettiget” (authorised signatory) to e-Reg@ftnet.dk with the user's stamdata; Finanstilsynet then assigns rights. Company-run user administration launches in H2 2026; until then Finanstilsynet assigns rights. Existing FIONA users were not migrated (“Det er desværre ikke muligt for os at migrere eksisterende indberetter-brugere i FIONA til e-Reg”). After login choose application “e-Reg”, then “Gå til e-Reg” (production, “prod” in the URL) or “Gå til e-Reg træningsmiljø” (“pre-prod”). Users without rights see: “Du har ikke adgang til e-Reg. På vores hjemmeside finder du en brugeroprettelsesformular…”.

source high confidence

Danish (verbatim): “Identifier.rapporteringsniveau_modul_referenceperiode_tidsstempel.zip”. English: Identifier.ReportingLevel_Module_ReferencePeriod_Timestamp.zip

Example 549300D6BJ7XOO03RR69.CON_DORA_2025-12-31_20251017105200055.zip (Finanstilsynet's own example)

Notes “I eksemplet ovenfor er der brugt en LEI-kode som identifier, da indberettende virksomheder i udgangspunktet forventes at have en LEI-kode. Har man ikke en LEI-kode, kan man for EBA-indberetningerne få særlig tilladelse til at anvende et CVR-nummer eller anden virksomheds-ID som identifier.” (LEI is the identifier by default; without one, special permission may be given to use a CVR number or other company ID for EBA reports.) Timestamp = 17 digits: year 4, month 2, day 2, hour 2, minute 2, second 2, millisecond 3. Reporting level CON or IND. The file content must match the module named in the file (“Det nytter altså ikke noget, at man klargør … en fil med RESOL1-indberetningsdata, men at man i filens navn har angivet, at det er en DORA-indberetning”) and the entity must actually hold that obligation. After upload e-Reg renames the file to “den interne navnestandard, der er aftalt mellem Finanstilsynet og ESA'erne”, so the name shown under “File submitted” differs from the uploaded name.

source high confidence

other rules

• Four background validations on every upload: “reporting obligation validation” (no obligation, or too many sheets filled, → automatic rejection), “technical validation” (file unreadable or wrong name → rejected), “filing rules validation” (EBA Filing Rules), “business rules validation” (semantics, e.g. a non-LEI value in an LEI field).
• Errors are red and block forwarding to the ESA until fixed and re-uploaded; warnings are orange/yellow, should be fixed, but a file “kan dog som regel godt godkendes fra Finanstilsynets side og sendes videre til ESA’en, selv hvis der er et par warnings”.
• “man kan ikke slette en indberetning i e-Reg, når man først har godkendt og indsendt den” — submissions cannot be deleted; upload a new one; “Den senest indsendte indberetning vil altid overskrive og ugyldiggør tidligere indberetninger.”
• The Load Files table shows “Size (KB)”; no maximum size is stated.
• Finanstilsynet's RoI page gives no root-folder, META-INF or parameters.csv guidance; it points to the EBA preparation page and Regulation (EU) 2024/2956 Annex I.

source high confidence

Notes RoI page (updated 09-03-2026): “Finanstilsynet forventer, at der vil blive åbnet for at indberette d. 10. marts 2026” and submission “senest den 31. marts 2026”. e-Reg FAQ: phase 1 production opened 10 Mar 2026 for DORA, RESOL1, RESOL2 with first deadline 31 Mar 2026 (“DORA, RESOL1 og RESOL2 skal indberettes for første gang i e-Reg med deadline 31. marts 2026”); training environment opened 3 Mar 2026; notification letters sent early March. Deadlines overview (10-08-2026): “DORA … Første referenceperiode er 31-12-2025 med indberetningsfristen den 31. marts 2026”. During phase 1 communication was by email; the communication module and automated ESA feedback came with phase 2 (late March 2026). No Finanstilsynet notice on corrections, extensions or rejection rates for 2026 was found. Previous cycle: filed in FIONA Online (last FIONA reference period 31-03-2025); DLA Piper reported the Danish deadline as 31 March 2025 with a separate FIONA user created via a registration form (secondary source).

reference date 2025-12-31

opens 2026-03-10

deadline 2026-03-31

source high confidence

reference date 2026-12-31

esa transmission deadline 2027-03-31

changes Nothing 2027-specific found as at 2026-10-31. The deadlines overview dated 10-08-2026 lists DORA as “Indberettes årligt” (reported annually) but only gives the 2026 dates. Known changes in train: company-run e-Reg user administration launching H2 2026; e-Reg phases 3 (EIOPA, June 2026) and 4 (ESMA, Oct 2026) do not affect the RoI.

source high confidence

Permanent “træningsmiljø” (pre-prod), opened to reporters 3 March 2026, initially EBA reporting only: “Træningsmiljøet er til prøveindberetninger”; “Intet af det, der bliver indberettet i træningsmiljøet, vil blive brugt i tilsynsmæssig sammenhæng”; it is an identical copy of production (check “pre-prod” vs “prod” in the top-right corner or URL) and stays open for repeated practice. Guide 8 covers moving a submission from the training environment to production. Production “må ikke anvendes til prøve-indberetninger”.

available yes

source high confidence

The Load Files guide describes one reporter uploading and the file proceeding automatically through validation to the ESA; there is no second-user approval step. “false” reflects the absence of any such step in Finanstilsynet's guides.

two user no

roles “e-Reg brugeradministrator” (appointed by form signed by an authorised signatory, assigned/revoked only by Finanstilsynet; assigns and removes reporting rights per obligation, also to external people such as data-centre staff) and “indberetterbruger” (reporting user). No approver role is described.

source medium confidence

format In e-Reg Load Files: File status (“Integration pending” → “Extracting” → “Extracted”), File validation (green tick, or orange warnings / red errors), Ticket status (“None” → “Extracting” → “Accepted”, or other = not accepted by the ESA), Ticket workflow box (grey = no ESA feedback yet, green = accepted, red = not accepted), Report column (ESA ticket number; on rejection “typisk også … en fejlbeskrivelse”), Communication column (link to comments from the ESA or Finanstilsynet). “Feedback report” download = zip with 4 elements: the ESA feedback as a further zip, plus Finanstilsynet's feedback in Excel, HTML and XML. “Feedback på indberetninger fra ESA'erne kommer direkte ind i e-Reg.” From phase 2, communication is attached to each report with email notifications.

timing Finanstilsynet validation “typisk få minutter”; ESA feedback timing not stated.

resubmission Red error → rejected; fix and upload again. A submission cannot be deleted; the latest approved-and-submitted file is always the valid one and overrides earlier ones.

source high confidence

true

LEI is the default identifier in the e-Reg filename and “indberettende virksomheder i udgangspunktet forventes at have en LEI-kode”; an entity without an LEI “kan … for EBA-indberetningerne få særlig tilladelse til at anvende et CVR-nummer eller anden virksomheds-ID som identifier” (must obtain special permission to use a CVR number or other ID). Finanstilsynet's general LEI page does not mention DORA.

source high confidence

Entities covered by DORA Art. 2(1) as listed by Finanstilsynet: kreditinstitutter; betalingsinstitutter (incl. PSD2-exempt); kontooplysningstjenesteudbydere; e-pengeinstitutter (incl. EMD-exempt); investeringsselskaber; udbydere af kryptoaktivtjenester og udstedere af aktivbaserede tokens; værdipapircentraler; centrale modparter; markedspladser; transaktionsregistre; forvaltere af alternative investeringsfonde; administrationsselskaber; udbydere af dataindberetningstjenester; forsikrings- og genforsikringsselskaber; forsikringsformidlere, genforsikringsformidlere og accessoriske forsikringsformidlere; arbejdsmarkedsrelaterede pensionskasser; kreditvurderingsbureauer; administratorer af kritiske benchmarks; udbydere af crowdfundingtjenester; securitiseringsregistre; tredjepartsudbydere af IKT-tjenester. Group rule: “skal indberetningen ske på højest konsolideret niveau for gruppen”; subsidiaries/branches of another DORA entity “skal således ikke foretage indberetningen”; entities outside a financial group report “på virksomhedsniveau”.

source high confidence