Finland: filing with the Finanssivalvonta (Financial Supervisory Authority, FIN-FSA)

xbrl-csv-only

The RoI is uploaded as an xBRL-CSV report package (zip) per FIN-FSA's transmission description v5.0 (examples use module DORA, framework code DORA010100); FIN-FSA states DORA reporting “uses the 4.0 reporting framework” while other EBA modules moved to 4.2/DPM 2.0. Reports can in general be submitted by file upload (XBRL/XML/CSV), via SFTP (A2A), or via web forms (recommended only for a small number of forms; Excel import into forms exists generically), but FIN-FSA has not been seen stating that web forms or an Excel template exist for the DORA RoI. The DORA page points firms to the EBA annotated templates (Excel) as a way to build the register.

source high confidence

FIN-FSA Reporter Portal (Raportoijan portaali / Rapportörsportalen) for official submissions, plus the separate Validation Service (Validointipalvelu) for test submissions; both are part of the “system for reporting the financial standing and risks of supervised entities”. “Rapporteringen ska göras via Finansinspektionens rapportörsportal.”

url https://reporting.finanssivalvonta.fi/

login prerequisites Suomi.fi e-Identification plus a Suomi.fi e-Authorizations mandate. The mandate theme is “Reporting of financial standing and risks” (“The mandate of the FIN-FSA’s Reporting Portal is entitled ‘Reporting of financial standing and risks’”), and “granting Reporting Portal authorisations always requires the enabling of an authorisation specifier”; for the RoI “The Suomi.fi mandate specifier is DORA. Reporting is also possible under specifier ALL.” Mandates are granted by a person with signing rights for the entity (authorised signatory) in Suomi.fi, either as a transaction mandate to an employee or service provider or as a right to grant mandates; foreign persons/companies are authorised via a foreigner's UID or the officials' mandate service. Portal URLs: Reporter Portal https://reporting.finanssivalvonta.fi/ (also https://raportointi.finanssivalvonta.fi/), Validation Service https://validointipalvelu-raportointi.finanssivalvonta.fi/. Suomi.fi login problems: Digital and Population Data Services Agency.

source high confidence

<reportingentityid>_<typeofid>_<frameworkcodemoduleversion>_<module>_<period>_<creationdatetime>.zip

Example 7437007ALEZNCJGTGA67.201_RS_DORA010100_DORA_2025-03-31_20250406084300000.zip (FIN-FSA's DORA example); without LEI the TK code is used, e.g. 0000002.201_RS_COREP040100_COREPOF_2026-03-31_20260418124000000.zip

Notes <reportingentityid> = “reporting entity’s ID and dot-separated reporting level” (LEI, or the 7-digit TK-tunnus for reporters without an LEI, followed by “.” and the reporting-level / regulatory-reporting-group code such as 201, 205, 260 — the document does not explain which code applies to the RoI); <typeofid> “type of reporting entity’s ID (always RS)”; <frameworkcodemoduleversion> “reporting framework code with module version with 6 characters (e.g. DORA 1.1.0 → DORA010100)”; <module> “name of taxonomy module (DORA)”; <period> stated as yyyymmdd in the text but all examples use YYYY-MM-DD; <creationdatetime> “YYYYMMDDhhmmssfff (e.g. 20250406084300000)”. The portal guide: “The report files must meet the technical specifications … The specifications include e.g. the file name and identifier.”

source high confidence

other rules

• parameters.csv: “Notice that entityID requires rs as the typeofid. The end requires the reporting level.” Example: name,value / entityID,rs:7437007ALEZNCJGTGA67.201 / refPeriod,2025-03-31 / baseCurrency,iso4217:EUR / decimalsInteger,0 / decimalsMonetary,-3. Without LEI: entityID,rs:0000002.201.
• “A report must be a whole entity, i.e. the Portal is not able to combine several files into one report.” Several report files may be uploaded together by zipping them (for XBRL-XML: <module>_<id>.zip wrapper); for xBRL-CSV the report package itself is the zip.
• Reports with integration errors are deleted from the Load file list at the end of the day; the Load file screen shows only reports uploaded the same day plus earlier accepted ones.
• FIN-FSA otherwise follows the EBA xBRL-CSV report-package rules (“EBA technical documentation for version 4.0 includes specifications for producing xBRL-CSV reports”).

source high confidence

Notes CONFLICTING REGULATOR STATEMENTS. Supervision release 19/2025 (10 Mar 2025): “År 2026 sker rapporteringen per ställningen den 31 december 2025 senast den 31 mars 2026.” (reference 31 Dec 2025, by 31 March 2026) and firms should “räkna med korrigering av eventuella problem”. The later supervision release 6/2026 (28 Jan 2026) states: “Tänä vuonna tietorekisterin raportointi tehdään 2.3.2026 mennessä.” / Swedish “senast den 2 mars 2026” (this year the register is reported by 2 March 2026), referring to instructions in the DORA section of the website. The later, cycle-specific statement is recorded as the deadline; no opening-date notice, corrections window or extension for 2026 was found, and no 2026 reporting release mentions DORA. 2025 cycle as run: reference date 31 March 2025; original deadline 30 April 2025; the DORA data collection was actually published in the Validation Service and Reporter Portal on 13 May 2025 with the deadline reset to 26 May 2025 (“The reports should deliver the report by 26.5.2025”); FIN-FSA stated it “does not initiate supervisory measures as a result of reporting delays” caused by technical problems in the reporting system.

reference date 2025-12-31

deadline 2026-03-02

source high confidence

reference date 2026-12-31

esa transmission deadline 2027-03-31

changes Nothing for 2027 found as at 2026-10-31 (2026 supervision-release and reporting-release listings checked). Release 6/2026 describes the register as one of “kolme uutta vuotuista raportointivelvoitetta” (three new annual obligations). FIN-FSA keeps DORA on EBA framework 4.0 (“An exception is DORA reporting, which uses the 4.0 reporting framework”) while migrating other EBA ITS modules to xBRL-CSV/DPM 4.2 from Q1 2026; EBA framework 4.3 is to be phased in from 12/2026 for other modules. FIN-FSA issued amended regulations and guidelines due to DORA in force 1 June 2026 (release 31/2026) without reporting-deadline content.

source medium confidence

Permanent Validation Service: “The Validation Service is a test environment for reporters. It is recommended that reports are sent to the Validation Service for checking before they are submitted as official reports to the FIN-FSA. These reports will not be used for supervisory purposes.” Q&A: “The test environment can and should be used to validate a report before the report is submitted.” The DORA data collection was published in both the Validation Service and the Reporter Portal on 13 May 2025. No dated dry-run window.

available yes

source high confidence

Portal guide v4.0: a file upload is validated automatically on upload and proceeds (status Extracting); for form-based reports the same user clicks “Approve and submit” (“If you are satisfied with the results of the checks, you can send the report to the FIN-FSA by clicking the Approve and submit button”). No maker/checker step is described; “false” reflects that absence.

two user no

roles Authorised signatory grants Suomi.fi mandates (transaction mandate or right-to-grant); the mandated reporter uploads/approves. No approver role is defined.

source medium confidence

format “The system always sends validation feedback, which also states whether the report has been accepted or not. The system does not send a separate acknowledgment of submission.” In the Reporter Portal Load file screen: File status (Extracting = accepted; Integration error = check the Report column), File validation icons, Feedback report download in Excel, HTML and XML, Ticket status (FIN-FSA internal), Ticket workflow icons for external feedback (ECB / EBA / EIOPA) coloured grey = no external feedback, green = no validation errors, “Red ECB or EBA feedback = Report contains warning or error level errors”. For form-based reports, status “Approved and submitted”, then “Pending feedback report” until external feedback arrives (permanently for reports with no external feedback). Discussion (messaging) functionality in the portal is the primary contact channel; reporting-release 10/2026 reminds entities to review validation feedback reports for ECB/EBA/EIOPA/ESMA submissions and fix errors promptly.

timing “Files are validated immediately after they are submitted. Feedback on a report comes after its validation.” External (EBA) feedback timing is not stated.

resubmission “It is not possible to resubmit a report without the invalidation of the previous report.” After the deadline, contact FIN-FSA via the Reporter Portal discussion function with a clarification of why the report is being resubmitted. Warning-level results may alternatively be explained to FIN-FSA; FIN-FSA “may impose an administrative fine” for neglected submission obligations.

source high confidence

true

Supervision release 19/2025: “rapporteringsskyldiga finansiella företag behöver en LEI-kod” (reporting financial firms need an LEI code) and new reporters should allow time to apply. DORA page: “Företagen under tillsyn ska ha en LEI-kod och den ska anmälas till Finansinspektionen per e-post.” (supervised companies must have an LEI and notify it to FIN-FSA by email). Technical fallback in the transmission description: “Reporters not having LEI use TK code” (7-digit TK-tunnus) in the filename and entityID.

source high confidence

“Förordningen gäller alla Finansinspektionens tillsynsobjekt, förutom arbetspensionsbolagen …” (DORA applies to all FIN-FSA supervised entities except employee pension insurance companies and certain small operators defined in the regulation); microenterprises face lighter requirements. Significant (SI) banks report contractual arrangements to the ECB under ECB instructions rather than to FIN-FSA (“SI-bankerna rapporterar om avtalsarrangemang till ECB enligt ECB:s anvisningar”).

source high confidence