Norway: filing with the Finanstilsynet

xbrl-csv-or-excel

Primary: “Formatet for rapporteringen er XBRL-CSV.” / “For å konvertere registeret til riktig format vil man ha behov for et konverteringsverktøy.” (a conversion tool is needed). Alternative: e-Reg web forms — “Som alternativ tilbyr e-Reg webforms, der man kan føre inn registeret manuelt” — where the user can “Export blank Excel templates”, fill them offline and import them one sheet at a time (“Deretter må man importere en arkfane om gangen. Det gis feilmeldinger her hvis det er noe, men de er vanskeligere å tolke enn om innsending er en fil.”). Finanstilsynet “primært anbefaler” generating an XBRL-CSV file. The Excel templates are generated inside e-Reg, not published by Finanstilsynet.

source high confidence

e-Regulatory (e-Reg), Finanstilsynet's reporting portal (Regnology platform). RoI is submitted via “Load Files” (zip upload) or entered manually via “Reporting Forms” (web forms). Landing page: rapportering.finanstilsynet.no.

url https://eregulatory-prod-prod-nofsa.apps.prod.regnology.cloud/eRegulatory/cgi/InvSingleSignOn.exe/init?oidccode=OIDC2

login prerequisites Login via ID-porten with the user's Norwegian personal ID number (“Man logger seg på via ID-porten med sitt personnummer”). The user must hold the Altinn role “Utfyller/Innsender” (filler/submitter) for the entity (“må brukeren være registrert som ‘Utfyller/innsender’ for foretaket i Altinn”); the entity must have a reporting obligation configured in e-Reg (“1) Foretaket må ha en rapporteringsforpliktelse 2) Personen som skal sende inn må ha rollen «utfyller/innsender»”). The Altinn role is being phased out: it cannot be delegated after 31 May 2026, existing holders may use it for e-Reg through 2026, and it is unavailable from 2027; Finanstilsynet recommends the Altinn single service (enkelttjeneste) “Finanstilsynet e-Reg” instead. First login asks for an email address. Supported browsers: Edge, Chrome, Safari. Login problems: eReg-rapportering@finanstilsynet.no.

source high confidence

Organisasjonsnr.Konsolideringsnivå_Modulnavn_Periode_Timestamp.zip (presentation wording: “Orgnr.konsolideringsnivå_DORA_Rapporteringsperiode_CreationTimestamp”). English: OrgNumber.ConsolidationLevel_Module_Period_Timestamp.zip

Example 987999999.CON_DORA_2025-12-31_20260110123005000.zip (Finanstilsynet presentation 16 Jan 2026); 999888777.IND_DORA_2025-12-31_20260102013221100.zip (e-Reg user guide)

Notes Components: 9-digit organisation number from Brønnøysundregistrene; CON (konsolidert) or IND (ikke-konsolidert); module name “DORA” (module name as in e-Reg/EBA); period = reference date YYYY-MM-DD; timestamp 17 characters YYYYMMDDHHmmssSSS = time the file was generated, the last 3 digits “vilkårlige 3 sifre, som kan brukes til versjonering av rapportører” (arbitrary, usable for reporter versioning). “Dersom filnavn har feil struktur vil filen avvises med feilmelding ‘integration error’.” The reference date and org number in parameters.csv must match the filename (“Disse opplysningene må samsvare med innholdet i filnavnet”).

source high confidence

root folder must equal zip name yes

meta inf location Zip must contain two directories: “META-INF” holding exactly one file reportPackage.json with {"documentInfo":{"documentType":"https://xbrl.org/report-package/2023"}}, and “reports” holding report.json (documentType https://xbrl.org/2021/xbrl-csv, extends http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/dora/4.0/mod/dora.json), parameters.csv, FilingIndicators.csv and one csv per table (e.g. b_02.01.csv). “NB: Stor B inne i denne filen, liten b i filnavnet” (capital B in FilingIndicators.csv template IDs, lower-case b in csv filenames).

timestamp uniqueness No explicit uniqueness rule; the final 3 digits of the 17-character timestamp are arbitrary and may be used to version successive uploads.

other rules

• “Mappen etter utpakking og zip-filen må ha samme navn.” — the folder after extraction and the zip must have the same name; mismatch gives error “invalidSingleTopDirectoryName”.
• parameters.csv example (verbatim): name,value / entityID,rs: 987999999.CON / refPeriod,2025-12-31 / baseCurrency,iso4217:NOK / decimalsInteger,0 / decimalsMonetary,-4 — entity identified by organisation number + consolidation level with the rs: prefix.
• FilingIndicators.csv: templateID,reported / B_01.01,true / … / B_99.01,true.
• Checks run on every upload: correct filename; reporting matches the entity's obligations; zip contains expected sub-directories and files; content correctly defined per the right taxonomy version; filing rules met; formulas flagged as Error met; nothing not validly defined. If all pass the file gets a “Ticket number” and counts as a valid submission.
• Two error families: “Integration error” (file rejected outright; short reason in the “Report” column, and if several integration errors exist often only the first is shown) and formula errors (Error vs Warning, downloadable via “Feedback report”; “ikke så aktuelt for DORA RoI”).
• EBA Filing Rules warning “missingOrIncorrectSoftwareInformation” can be cleared by adding eba:generatingSoftwareInformation to report.json (EBA Filing Rules pp. 23–24).
• Register should preferably be reported in English (“Informasjonsregisteret skal fortrinnsvis rapporteres på engelsk”).

source high confidence

Notes “Produksjonssystemet for å rapportere informasjonsregisteret åpner 2. februar 2026.” / “Fristen for å rapportere er 13. mars 2026.” Test system open in parallel with production. Notice of ~6 March 2026: Finanstilsynet forwards files to the ESAs by 31 March 2026; the final answer on acceptance comes after that date; firms should check status after 31 March and “setter av ressurser til oppfølging av eventuelle rettelser” from 31 March to 30 April 2026; “rapporteringene må sendes inn i produksjonsmiljøet i e-Reg for å bli gyldig” (only production submissions are valid). Post-deadline notice: Finanstilsynet “har mottatt en rekke innsendinger”, forwarded to EBA, and “flere er kommet i retur som avvist” (several returned as rejected); affected firms must correct and resubmit “så snart som mulig” and monitor whether EBA accepts the new submission. DORA Q&A: “For kommende år vil Finanstilsynet publisere datoer for rapportering på våre nettsider.”

reference date 2025-12-31

opens 2026-02-02

deadline 2026-03-13

corrections until 2026-04-30

source high confidence

reference date 2026-12-31

esa transmission deadline 2027-03-31

announced yes

opens 2027-02-01

deadline 2027-03-15

changes Main RoI page (undated; observed 2026-10-31) now states: “Produksjonssystemet for å rapportere informasjonsregisteret åpner 1. februar 2027.” / “Foretakenes frist for innrapportering er 15. mars 2027.” / “Fristene gjelder på årlig basis.” Access change: the Altinn role “Utfyller/Innsender” is unavailable from 2027 — reporters must be granted the Altinn single service “Finanstilsynet e-Reg” (delegation of the old role stopped 31 May 2026). Format unchanged (XBRL-CSV, EBA DORA framework 4.0 entry point); Finanstilsynet “tar sikte på å tilby” the web-form alternative. Test system “vil være åpent kontinuerlig”.

source high confidence

Permanent e-Reg test (pre-prod) environment: https://eregulatory-preprod-nonprod-nofsa.apps.prod.regnology.cloud/eRegulatory/cgi/InvSingleSignOn.exe/init?oidccode=OIDC2 (ID-porten login, same Altinn role). “Testsystemet vil være åpent kontinuerlig.” Only reporting-obligated firms can test; vendors must test through a client (“leverandører som ønsker å teste må gjøre dette gjennom et rapporteringspliktig foretak”). Test phase for DORA/RoI started before the 10 Nov 2025 information meeting; test env returns validation results like production but data is not used; future reference dates are opened in test so firms can test with upcoming taxonomy versions.

available yes

source high confidence

File upload: a single authorised user uploads via “Load Files”; a passing file receives a Ticket number and counts as submitted — no second approver is described. Web forms: the same user clicks “Run validation” then “Approve and submit” (“Er brukeren fornøyd med valideringsresultatene, klikk på knappen ‘Approve and submit’”). No maker/checker step appears in any Finanstilsynet guide or Q&A; “false” reflects that absence.

two user no

roles Altinn role “Utfyller/Innsender” (through 2026) or Altinn single service “Finanstilsynet e-Reg”; assigned in Altinn by the entity's daily manager (Daglig leder, DAGL) or Altinn admin. One person may report for several entities.

source medium confidence

format In e-Reg “Load Files”: File status (“Integration pending” → “Extracting”/“Levert” in green = accepted by e-Reg; “Integration error” = rejected, short reason in “Report” column); File validation icons (green = no errors, yellow = warnings, red = blocking errors, by category: XBRL types, schema, formulae, filing rules, unexpected/missing tables, etc.); “Feedback report” download = zip with 3 files (HTML, Excel, XML) plus, once the ESA has answered, a 4th element — the ESA feedback as its own zip. “Ticket Workflow” column shows ESA status: grey = no ESA feedback yet, green = approved without errors/warnings, yellow = warnings, red = rejected for blocking errors. In Reporting Forms the DOR symbol is green (Godkjent/Accepted) or red (Avvist/Not accepted). For a rejected RoI: click the red symbol → “Ticket” tab → download the file in “Original format” → open “instance-status” → the message is under “feedbackText,Business validation rules triggered”. Communication module (tag messages with entity + module; optional email notifications) carries questions and Finanstilsynet messages; automatic “Manglende rapportering” messages flag missing reports.

timing e-Reg validation: status refresh is manual; larger reports take minutes. ESA validation: “Deretter gjennomfører ESA (EBA eller EIOPA) egne valideringskontroller, normalt dagen etter innsending” (normally the day after submission) — but for the RoI the 2026 notice said the final answer comes only after Finanstilsynet's bulk transmission to the ESAs by 31 March 2026.

resubmission “Feilene må rettes opp og ny rapport må sendes i e-Reg.” Resubmit a corrected zip (new timestamp) and watch whether EBA accepts it; corrections window for 2026 ran 31 March–30 April 2026. Financing companies and NUF branches are not forwarded to EBA and get no external EBA validation.

source high confidence

false

The submitting entity is identified by its 9-digit Norwegian organisation number in both the filename and parameters.csv (entityID rs: 987999999.CON); no LEI is needed to file. Providers and relevant subcontractors must be identified by LEI or EUID — “Har leverandøren både LEI-nummer og EUID skal begge føres i registeret” (if both exist, both must be entered); “Alle foretak har en EUID” and EUIDs can be looked up in BRIS. (The ESA templates separately require the financial entity's own LEI in B_01.01; this is an ESA-level rule.)

source high confidence

“Foretak som er omfattet av DORA art. 2 nr. 1 bokstav a til t er rapporteringspliktige.” (Entities covered by DORA Art. 2(1)(a)–(t) are reporting entities.) Stand-alone entities and entities whose parent has no licence report individually; group members report at the highest consolidated level in the EEA; groups whose top parent is outside the EEA with no EEA parent report individually; cooperating groups/alliances are not DORA groups, so each member reports separately. Norway's DORA Act took effect 1 July 2025 (DORA is applied via the EEA Agreement).

source high confidence