Finland and Sweden remain the last major Nordic countries not to have imposed periodic SAF-T filings on all their businesses. While Norway mandated its first SAF-T Financial exports in 2020 and Denmark is preparing its own mandatory rollout for 2027, Helsinki has pursued a different path.
Different does not mean lighter. Finland has chosen two parallel levers with concrete implications for any group managing a Finnish subsidiary on its central ERP: mandatory iXBRL reporting for financial statements filed with the PRH (Patent and Registration Office), starting in July 2027, and a B2G e-invoicing regime already in place since 2019. For CIOs and CFOs of groups operating in Finland, mapping this regulatory landscape is an essential prerequisite before opening an ERP localisation project.
SAF-T in the Nordic Region: The Finnish Exception
SAF-T (Standard Audit File for Tax) is a standardised XML format defined by the OECD for the exchange of accounting data between businesses and tax authorities. Its adoption across Europe is accelerating: at least ten European countries had an active SAF-T mandate at the start of 2026, including Norway (mandatory since 2020), Portugal (2019), Austria (2022), Poland (via its JPK formats since 2016), Lithuania, Romania and Bulgaria (since 2026) (saft-validator.com, 2026).
Finland is not among them.
Verohallinto, the Finnish Tax Administration, can request structured accounting data during a tax audit (the so-called “on-demand” approach). However, there is no obligation in Finland to submit periodic SAF-T files, unlike in Norway. The OmaVero portal collects VAT returns and standard social declarations, but not a regularly submitted OECD-standardised accounting file.
This is not a delay: it is a deliberate fiscal policy choice. Finland has concentrated its digital accounting effort on the reporting of annual financial statements, via an iXBRL mandate managed by the PRH. For groups that have already implemented SAF-T for their Norwegian or Polish entities, this means that the SAF-T module deployed on the group ERP does not automatically cover Finland: the two obligations are fundamentally different and require separate workstreams.
The PRH Mandate: Mandatory iXBRL for Financial Statements (2027-2028)
The transformative change for CIOs of groups with Finnish subsidiaries is the PRH iXBRL mandate. For financial years opened on or after 1 July 2027, Finnish companies subject to statutory audit will be required to file their financial statements, management reports and audit reports in Inline XBRL (iXBRL) format — a structured format readable by both humans (XHTML) and machines (embedded XBRL tags) (XBRL.org).
Which Companies Are Affected from July 2027?
The first wave covers companies required to appoint a statutory auditor. Under Finnish law, a company must designate a KHT-tilintarkastaja (certified auditor) if it exceeds at least two of the following three thresholds:
- Balance sheet total exceeding EUR 100,000
- Turnover exceeding EUR 200,000
- More than 3 employees
In practice, this covers the vast majority of subsidiaries of international groups operating in Finland (ez-xbrl.com).
Extension to All Limited Liability Companies from July 2028
The second wave applies to financial years opened on or after 1 July 2028. It extends the obligation to virtually all Finnish limited liability companies (Osakeyhtiö / OY) and Finnish partnerships (vicosight.com). The goal is for all annual accounts filed with the Finnish trade register to be available in structured digital format by 2028 (XBRL.org).
Format and Taxonomy
Filings must comply with the iXBRL format using the Finnish national SBR (Standard Business Reporting) taxonomy, which covers both FAS (Finnish Accounting Standards) accounts and IFRS standards. For small entities without a digital accounting system, the PRH plans to provide a free conversion tool.
Late Filing Penalties
Since 2025, the PRH has applied progressive penalties for late financial statement filings (svalneratlas.com):
- Delay under 2 months: EUR 150
- Delay of 2 to 4 months: EUR 300
- Delay exceeding 4 months: EUR 600
- Penalties doubled for two consecutive years of late filing
From 2027 onwards, the PRH will also require annual verification of registered information, with a EUR 300 penalty for non-compliance from 2028.
E-Invoicing in Finland: Finvoice for B2G, Not Yet B2B
On the e-invoicing front, Finland is ahead of the curve in the B2G segment. Public sector suppliers have been required to issue electronic invoices since April 2019. Two formats are accepted: Finvoice 3.0 (a standard developed by the Federation of Finnish Financial Services, FK) and TEAPPS XML 3.0, both aligned with the European standard EN 16931. The Peppol network is used for public sector exchanges, even though Finvoice remains the dominant format in the Finnish ecosystem (dddinvoices.com).
B2B e-invoicing is not yet mandatory in Finland. Finland will align with the EU ViDA (VAT in the Digital Age) schedule, which provides for digital VAT reporting on cross-border transactions from 1 July 2030 (DG TAXUD, European Commission, 11 March 2025).
For groups with a Finnish subsidiary acting as both a public sector supplier and a private sector service provider, the e-invoicing workstream is therefore partial: the obligation applies only to outbound B2G flows.
Finland’s Bilingual Requirement
Finland is officially bilingual: Finnish (suomi) and Swedish are the two national languages. For financial statement filings, documents may be prepared in either language. Subsidiaries located in Swedish-speaking regions (Ostrobothnia, Åland) must ensure that their chart of accounts labels and XBRL tags are available in Finland-Swedish. Group ERPs sometimes have gaps on this point: verify the availability of Swedish-language taxonomies in your vendor’s iXBRL module.
What ERPs Need to Deliver
The Finland localisation workstream on a group ERP breaks down into two distinct dimensions: iXBRL for annual financial statements and Finvoice for B2G invoicing.
SAP S/4HANA. SAP offers SAP Disclosure Management and an iXBRL add-on for structured financial statement reporting. The right question to put to SAP support or your integrator is precise: “Is the PRH/SBR Finnish taxonomy available in your version of SAP Disclosure Management? What is the minimum S/4HANA version that supports it?” The Finnish Finvoice 3.0 localisation (B2G) is available in SAP Document and Reporting Compliance.
Oracle Fusion Cloud. Oracle Fusion Cloud Finance provides Oracle Tax Reporting Cloud for tax reporting obligations. The availability of the Finnish FAS taxonomy for PRH iXBRL is a point to confirm with Oracle as part of a pre-project assessment. Regulatory updates in Oracle Cloud are deployed automatically via quarterly release cycles, which is a structural advantage for groups consolidating multiple countries on a single Oracle instance.
Microsoft Dynamics 365 Finance. Dynamics 365 Finance uses the Electronic Reporting (ER) framework to generate regulatory reporting formats. Finland has a Finvoice localisation via ER configurations published in Microsoft’s global library. For PRH iXBRL, ER configurations dedicated to the Finnish SBR taxonomy are in development or available through Microsoft-certified partners for Finland. Verify availability with your local Microsoft partner before launching the project.
Native Finnish ERPs. Companies running their Finnish subsidiary on a local ERP generally have nothing specific to do: Netvisor (Visma Group), Procountor and Lemonsoft are built for the Finnish market and will incorporate PRH regulatory changes in their updates. For a group whose Finnish subsidiary uses one of these tools and whose group consolidation requirements are met by an export to the central ERP, iXBRL compliance will be handled by the local vendor without any specific group workstream.
Odoo. Odoo has no native iXBRL module for Finland. A custom development or a third-party module will be required for groups managing their Finnish subsidiary on Odoo. This gap should be flagged in the scoping document if Odoo is the group ERP under consideration for Finland.
The SaaS Cloud ERP Advantage. For multi-tenant SaaS cloud ERPs (Workday, NetSuite, Oracle Fusion Cloud, SAP S/4HANA Cloud Public Edition), regulatory updates are automatically deployed by the vendor within release cycles. This model provides a structural compliance advantage in markets like Finland where obligations evolve regularly.
Roadmap for Group CIOs with Finnish Operations
The horizon is July 2027 for companies subject to statutory audit. If your fiscal year follows the calendar year (1 January – 31 December), financial years opened on or after 1 July 2027 are the 2027 fiscal years: the first iXBRL financial statements will be due in early 2028 (within 6 to 8 months after the December 2027 year-end close).
T-12 months (Autumn 2026): Scoping and inventory. Identify Finnish entities in your perimeter and check whether they are subject to statutory audit (two of three thresholds exceeded). Map their current ERP: group ERP or local Finnish ERP? If the entity is on the group ERP, raise the question of Finnish iXBRL module availability with your vendor or integrator now.
T-9 months (Early 2027): Chart of accounts audit. The Finnish chart of accounts (FAS, based on the Kirjanpitolaki) differs from standard international charts on several line items, particularly in the treatment of provisions, financial assets and intra-group transactions. A mapping between your central ERP accounts and the FAS account codes expected in the Finnish SBR taxonomy is mandatory. This work is conducted with your local Finnish accounting firm, ideally a KHT-tilintarkastaja with international group experience.
T-6 months (Spring 2027): Configuration and testing. Activate or procure the iXBRL module for Finland in your ERP. Run a test export against a closed fiscal year and validate it with your local auditor. Verify that bilingual labels (Finnish/Swedish) are correctly covered if your subsidiary operates in a Swedish-speaking region.
T-1 month before first filing deadline: Pilot submission. Perform a test filing on the PRH portal before the production submission. Involve your KHT-tilintarkastaja to validate the iXBRL file before any official submission.
Multi-instance groups. For groups consolidating multiple countries on a single ERP instance (single-instance approach), the Finnish workstream sits within the global localisation programme. Avoid creating a fork of the ERP instance for Finland: prefer deploying the localised module within the centralised instance, which simplifies consolidation and future regulatory updates.
Key Considerations for International Groups
Beyond the iXBRL workstream, several points deserve attention for international groups operating in Finland.
Finnish Accounting Standards differ from IFRS and local GAAP. The Finnish chart of accounts (Kirjanpitolaki) follows FAS norms that differ from IFRS and from the national GAAP of many home countries on certain line items, notably the treatment of provisions, financial assets and intra-group transactions. Groups that impose their central chart of accounts on subsidiaries must plan a chart-of-accounts mapping validated by a local Finnish accountant.
X-Road and Finland’s Digital Administration Maturity. Finland is a founding member of the NIIS (Nordic Institute for Interoperability Solutions) and uses X-Road — the interoperability infrastructure originally developed in Estonia — for data exchanges between public systems. This has no direct impact on a private subsidiary’s ERP, but it illustrates the digital expectation of the Finnish administration, which wants structured data, not PDFs.
Local Accounting Firm Partnership Is Non-Negotiable. Finnish regulatory complexity justifies working with a local accounting firm that is a partner of an international network. The KHT-tilintarkastaja plays a central role in validating iXBRL financial statements before PRH filing and in interpreting FAS standards for internationally-owned entities in Finland.
The Road to 2030 and the ViDA Horizon. Finland is not a permanent exception to digital tax reporting. ViDA will require all EU member states to implement digital VAT reporting for cross-border transactions by 2030, and a national adaptation of existing declaration systems by 2035. Groups investing today in Finnish ERP localisation are building a foundation they will reuse for the next wave of obligations.
To situate Finland’s obligations within a broader Nordic picture, read our analysis of mandatory SAF-T Financial v1.40 in Norway from 2027 and our ERP guide for the Baltic States in 2026. For the European VAT digital trajectory that will also affect Finnish subsidiaries on B2B invoicing, our ViDA and ERP analysis covers the 2030 horizon.
