Sweden: filing with the Finansinspektionen

xbrl-csv-only

“Reporting module DORA (RoI) in framework 4.0 is submitted as XBRL-CSV Reporting Package (zip)”. FIDAC guide: in EBA XBRL reporting “all reporting modules listed may only be submitted by uploading a report”; the initial format check accepts XBRL-XML or XBRL-CSV, and FI's page states XBRL-CSV for the RoI. FI publishes no Excel template and no web form for the RoI (an Excel template is mentioned only for DORA incident reporting).

source high confidence

FIDAC (Finansinspektionen Data Collection), reached through FI's Reporting Portal (Rapporteringsportalen). The RoI is uploaded under the data collection “Scheduled” > “EBA XBRL reporting” (Swedish menu: Schemalagd > EBA XBRL-rapportering); the reporting module is “DORA (RoI)” in EBA framework 4.0.

url https://fi.se/en/applying-and-reporting/reporting2/report-in-fidac/

login prerequisites 1) Register a personal account in the Reporting Portal: Swedish residents use a Swedish personal ID number with BankID / Mobilt BankID; non-residents create a username/password account verified by email and log in with the “One Touch” mobile app. 2) The company must be registered in the Reporting Portal; the Company Administrator (auto-assigned to the representative who registered the company) or the Signatory (auto-assigned from Bolagsverket data, refreshed at 06:00, 10:00, 13:00, 16:00 and 19:00) delegates reporting authorisations in “Authorisation Administration”. 3) For the RoI the required authorisation is “Periodisk rapportering”: “A registered profile in the Reporting Portal and authorization ‘Periodisk rapportering’ is needed to submit the report.” FIDAC guide: “users must register for an account in the Reporting Portal and be delegated authorisation from a registered signatory.” Access path: fi.se > E-services and forms > Reporting to FI.

source high confidence

No FI-imposed pattern. Swedish (verbatim): “FI har inget krav på namngivning av fil i XBRL-CSV-format förutom att namn på mapp (root folder) i fil ska ha samma namn som själva zip-filen (utan ändelsen ".zip").” / “Tänk på att mappens och zip-filens namn inte får innehålla å, ä eller ö.” English: FI has no requirement on naming of the XBRL-CSV file except that the root folder inside the zip must have the same name as the zip file itself (without the “.zip” extension); folder and zip names must not contain å, ä or ö.

Example Any name without å/ä/ö works, e.g. 12345_DORA_20251231.zip containing the single top-level folder 12345_DORA_20251231/ (illustrative only; FI prescribes no pattern). The entity and period are read from reports/parameters.csv, not from the filename.

Notes English page wording: “FI does not have requirements for file naming in XBRL-CSV format”; the only rule is root folder name = zip name and the root folder name must not end in “.zip”. FI defers to EBA Filing Rules (page cites “senaste version=5.7”; the XBRL-CSV section of the same page links v5.8 of 2026-02-25).

source high confidence

root folder must equal zip name yes

meta inf location Not addressed by FI; FI only specifies that parameters.csv sits in a folder named “reports” and otherwise defers to the EBA XBRL-CSV report-package rules (EBA Filing Rules 5.7/5.8).

other rules

• parameters.csv (in folder “reports”): “Identifierare, referensdatum, valuta och decimaler (för avrundning) anges i filen "parameters.csv".” FI example lines: entityID,rs:XXXXX.IND | refPeriod,2025-12-31 | baseCurrency,iso4217:SEK | decimalsMonetary,-3.
• entityID = prefix “rs:” + FI institute number (institutnummer) + “.IND” (individual) or “.CON” (consolidated), using the consolidation scope shown for the obligation in FIDAC. (FI's incident/XBRL-XML modules use scheme http://www.fi.se/instnr; for XBRL-CSV the rs: prefix is used.)
• baseCurrency must be iso4217:SEK or iso4217:EUR.
• First DORA reference date was 2025-03-31 (English page); the Swedish page's current example uses refPeriod 2025-12-31.
• IND vs CON: “För många finansiella entiteter (FE) visas ett rapporteringskrav både på individuell (IND)- och konsoliderad (CON)-nivå …”; “Den konsoliderade rapporteringen bör användas om den omfattar hela gruppens informationsregister.”; “I annat fall ska informationsregistret lämnas för varje enskild entitet i den individuella rapporteringen i Fidac.”; “Observera att endast ett av ovanstående alternativ ska användas, eftersom det annars innebär att informationsregistret lämnas in två gånger.” (Use consolidated only if it covers the whole group's register; otherwise each entity reports individually and no consolidated filing is made; never both, or the register is submitted twice.)
• A file must match an active reporting obligation (module/schema reference, reporting entity ID, reference date); otherwise it is placed under “Unexpected” with status “Submitted: Invalid” and “is not considered received”.
• Folder and zip names must not contain å, ä or ö.

source high confidence

Notes Deadline is the standing annual rule in FFFS 2024:20 4 § (not a cycle-specific notice): “En finansiell entitet ska ge Finansinspektionen tillgång till sitt fullständiga register … genom att årligen senast den 28 februari lämna in registret till Finansinspektionen. … Den version av registret som lämnas in ska avse förhållandena vid utgången av föregående kalenderår.” (annually by 28 February; version as at the end of the preceding calendar year). FI's register of FFFS lists no amendment to FFFS 2024:20 as at 2026-10-31, so 28 Feb 2026 applied unless amended. FI's decision memo (2024-12-18) explains 28 Feb was chosen so FI can forward to the ESAs by 31 March. 28 Feb 2026 fell on a Saturday; FI's general Fidac page says “the actual deadline will automatically be the next weekday” when a deadline falls on a weekend, but FI was not seen stating this specifically for the RoI. No FI news item, Fidac opening date or corrections window for the 2026 RoI cycle was found on fi.se. For context, the first cycle ran under transitional rule 2: first submission by 15 April 2025 for the position at end of March 2025; FI's English DORA page (still online, last reviewed 2026-10-27) says “Reports will be deployed to production on Tuesday 1st of April” and “Any changes to the schedule will be communicated continuously.”

reference date 2025-12-31

deadline 2026-02-28

source high confidence

reference date 2026-12-31

esa transmission deadline 2027-03-31

announced no

deadline 2027-02-28

changes No 2027-specific announcement found on fi.se as at 2026-10-31. The deadline shown is the standing FFFS 2024:20 4 § rule (annually by 28 February, position at end of preceding calendar year) and applies unless amended; FI's FFFS register page lists no amendments. FI's Fidac page keeps the RoI on EBA framework 4.0 and has updated its EBA Filing Rules reference to v5.7/v5.8 (2026-02-25); the FIDAC instructions were re-issued 24 April 2026 (v1.3).

source medium confidence

Permanent test module “FIDAC Test Reporting” in the Reporting Portal: “Submit test files in FIDAC Test Reporting to find errors before production.” FIDAC guide: “The method for test reporting is the same as for live reporting. The difference is that the test report is not sent to FI for analysis.” No dated dry-run window is announced.

available yes

source high confidence

FIDAC instructions v1.3 (24 April 2026) describe a single-user flow: select data collection “EBA XBRL reporting”, click “Upload Report”, attach the zip, fill in contact name/phone/email, submit. No maker/checker or second-user approval step is described anywhere in the guide; “two_user: false” reflects that absence rather than an explicit FI statement.

two user no

roles Company Administrator or Signatory (firmatecknare) delegates; a rapporteur holding the “Periodisk rapportering” authorisation uploads. Other roles are not described.

source medium confidence

format (1) FIDAC emails the contact address given at upload once the file is fully validated, stating whether the report is approved or not approved; details are in FIDAC under the reporting obligation (tabs Submission History / Validation Results; columns severity, validation type, rule ID, message; severities include Warning and Info). (2) EBA-side rejections are relayed by FI (“Bolag som, i feedback från Finansinspektionen, fått utfall på någon av nedanstående koder …”); FI's PDF “Dora felkoder informationsregister” lists the most common EBA codes. (3) A submitted report can be viewed via “View Templates” and downloaded as XLSX/CSV.

timing FIDAC email after full validation of the upload (no fixed SLA stated). EBA feedback arrives after FI forwards the file to EBA; FI states no timeframe.

resubmission “For a submitted reporting obligation that needs to be corrected via file: update the information in the file and upload it.” The most recently submitted version is the valid one. Error-code PDF: correct the file and “skicka om filen på nytt” (resend the file). Files that do not match an obligation land in “Unexpected” and are not treated as received, so check for the confirmation email.

source high confidence

false

FI identifies the submitting entity by its FI institute number (entityID rs:XXXXX.IND / .CON), not by LEI, and FI's RoI pages state no LEI requirement for the filer. (The ESA templates themselves require the financial entity's LEI in B_01.01; that is an ESA rule, not an FI one, and FI's error-code PDF does not list an LEI-related rejection.)

source high confidence

All financial entities within the scope of Article 2 of DORA that are under Finansinspektionen's supervision. FFFS 2024:20 2 §: “Dessa föreskrifter gäller för sådana finansiella entiteter som omfattas av tillämpningsområdet för artikel 2 i Dora-förordningen och som står under tillsyn av Finansinspektionen.” (These regulations apply to financial entities within the scope of Article 2 of the DORA Regulation that are supervised by Finansinspektionen.)

source high confidence