Electronic invoice in Finland

Operator network with Finvoice and TEAPPSXML – B2G mandatory, B2B partially mandatory

Select a country

Overview

Finland is one of the most thoroughly digitalised invoicing markets in Europe, and it got there almost entirely without a mandate. There is no clearance, no continuous transaction control and no real-time VAT reporting. What exists instead is a mature national operator network, a well-drafted right for buyers to demand a structured invoice, and a central government that simply refuses anything else.

For a foreign provider the important distinction is not legal but infrastructural. Finland runs two parallel networks: the domestic operator network built on the Finvoice and TEAPPSXML formats, and Peppol. Being certified for one does not give you the other. That single fact decides how much of the Finnish market you can actually reach — see The national operator network.

EAS 0216

the Finnish OVT code — required, not merely available, for Finnish participants

€10,000

the turnover above which a business may demand a European-standard e-invoice

6 and 10 years

retention for invoices and vouchers, and for accounting books and statements

Timeline

Finland's own milestones finished in 2021. What has happened since is assessment, not legislation.

Already in force

1 April 2019

Act 241/2019 takes effect for central government

The Act on Electronic Invoicing of Contracting Entities and Traders (Laki hankintayksiköiden ja elinkeinonharjoittajien sähköisestä laskutuksesta) obliges central government contracting authorities to receive and process EN 16931 invoices.

1 April 2020

The right to demand an e-invoice appears

The statutory framework extends to the contracting authorities covered by the Act, and businesses in scope gain the right to require a European-standard e-invoice from their suppliers.

1 April 2021

The State accepts European-standard invoices only

Finnish central government stops accepting anything that is not a compliant European-standard e-invoice. Invoices are validated, and a non-compliant one can be discarded. See B2G and the State.

14 April 2025

ViDA enters into force

Directive (EU) 2025/516, Regulation (EU) 2025/517 and Implementing Regulation (EU) 2025/518 were published in the Official Journal on 25 March 2025.

Still ahead

1 July 2030

ViDA digital reporting for intra-EU B2B

Mandatory structured e-invoicing and digital reporting for the cross-border B2B transactions in scope. This is the one hard deadline Finland has. See ViDA and 2030.

1 January 2035

Alignment of domestic reporting systems

Member states with existing domestic real-time reporting must align it with the EU model. Finland has no such system, so this does not automatically oblige it to introduce one.

There is no date for a general Finnish B2B mandate. Claims that one has been approved do not survive contact with the primary sources: the most recent regulatory step is an assessment memorandum whose consultation closed in March 2026, and the State Treasury stated expressly that it was not part of an ongoing legislative project.

Who is in scope

Central governmentAccepts European-standard e-invoices only. Paper, PDF and images attached to email are not e-invoices in this channel

Other contracting authoritiesMust be able to receive and process EN 16931 invoices. Individual receiving arrangements — address, operator, Peppol endpoint, order reference — still need checking per authority

Businesses above €10,000 turnoverMay demand a European-standard e-invoice from a supplier. If they do, the supplier must provide one

Everyone else in B2BNo obligation. Format is a matter of agreement, and ordinary VAT invoicing rules apply

B2CNo mandate. The right to demand does not extend to invoices issued to private persons

The Finnish design is worth appreciating on its own terms. Rather than compelling every issuer, the law made the demand side enforceable and let the market do the rest — and the market did. High adoption here is a consequence of infrastructure and commercial pressure, not of statutory compulsion.

B2G and the State

The legal construction of Act 241/2019 is a receiver capability obligation plus a right to demand — it is not the Italian model in which an invoice is invalid unless it has passed a central platform. But for Finnish central government the operational rule is unambiguous, and stricter than the legal text alone suggests.

What is acceptedStructured e-invoices compliant with the European standard, since 1 April 2021

What is notAn invoice attached to an email, a PDF invoice, or an image of an invoice. None of these is an e-invoice

ValidationEuropean-standard invoices are validated. A non-compliant invoice can be discarded, and the sender must correct and resend it

ChannelsThe national operator network, Peppol, or a state-provided free invoicing portal for particular scenarios

Build for the discard path. Validation failure in this channel is not a rejection notice with a helpful explanation arriving in your inbox — it is an invoice that quietly never became payable. Validate before sending rather than discovering it in the ageing report.

B2B and B2C

There is no universal domestic B2B mandate. Finnish businesses exchange Finvoice, TEAPPSXML, Peppol BIS Billing or whatever else they have agreed. What the law adds is a floor: a business above the €10,000 turnover threshold can require a European-standard e-invoice, and once it does, the supplier must deliver one. Government materials for the Act note that parties would normally agree formats contractually — the statutory right matters most where no such agreement exists.

Cross-border inside the EU, until 2030

Being an intra-EU transaction does not by itself create a Finnish structured-invoicing obligation. Format and transport follow the applicable VAT rules, the counterparty country's requirements, the contract and each side's technical capability. Finnish law does not require Peppol for intra-EU invoices, even though Peppol is the practical channel. For intra-Community supplies and certain B2B services the invoice must be issued by the 15th day of the following calendar month.

Exports outside the EU

No Finnish rule requires a structured e-invoice merely because a transaction is an export. Finnish VAT invoicing provisions apply where relevant; the format follows the destination country's law, the agreement with the buyer and the networks available. The ViDA intra-EU reporting regime should not be applied to third-country trade.

B2C

Voluntary. The Act's right to demand a European-standard invoice does not extend to private persons, and the Tax Administration treats invoicing individuals separately. Consumer e-invoicing is nonetheless widely used through the national infrastructure — again, adoption without obligation.

Formats and PDF

Finland is oriented on EN 16931 throughout, but with two national formats that remain the working currency of domestic trade.

UBL 2.1European standard syntax, supported

UN/CEFACT CII D16BThe second European standard syntax, supported

Peppol BIS Billing 3.0EN 16931-aligned, the profile used over the Peppol network

Finvoice 3.0The principal Finnish national format. Capable of carrying a European-standard compliant invoice

TEAPPSXML 3.0The other Finnish national format, likewise capable of European-standard compliance

A file being called Finvoice 3.0 does not mean that particular invoice satisfies every EN 16931 business rule. The version supports compliance; it does not guarantee it in a given document. For central government the invoice is validated, and failing that validation is what gets it discarded.

Where the PDF sits

Two questions, two answers. For VAT purposes an invoice may be on paper or in electronic form, so a PDF can be a valid VAT invoice in ordinary B2B and B2C where no structured invoice was required. Under Act 241/2019 and EN 16931 a PDF is not a structured e-invoice.

So a PDF does not become an unlawful invoice merely because the transaction is Finnish domestic B2B. It does fail in three specific places: where a buyer has exercised the right to demand a European-standard invoice, in the central government channel, and — from 2030 — for intra-EU B2B under ViDA.

The model

Finland is a decentralised, non-CTC, post-audit market. The Tax Administration is not in the invoice delivery chain at any point.

What Finland does not have

Prior authorisation of invoices by the tax administration, or a government clearance code

A compulsory central platform through which invoices must pass

An invoice-level real-time VAT reporting obligation — the EU country factsheet records Finland as having no VAT real-time reporting system

A five-corner model. The Tax Administration is not a mandatory fifth corner and receives no real-time copy

When an invoice travels over Peppol, the standard four-corner model applies — supplier, sending Access Point, receiving Access Point, buyer — using AS4 and PKI certificates under the OpenPeppol service requirements. The State Treasury describes Peppol operation in exactly those terms.

The national operator network

This is the part of Finland that surprises foreign providers, and it is the single most important commercial fact on this page. Finland has been building its own e-invoicing ecosystem for over twenty-five years. The great majority of domestic invoices travel through a network of interconnected national e-invoicing operators, carrying Finvoice and TEAPPSXML — not through Peppol.

The domestic network

Bilateral connections between Finnish e-invoicing operators, with Finvoice and TEAPPSXML as the working formats. Routing and agreements are operator-to-operator.

Peppol

A separate four-corner network with its own governance, addressing and profiles. Strategically promoted, especially for cross-border trade and procurement messages.

Peppol certification does not connect you to the Finnish Finvoice network. A certified Access Point elsewhere in the EU can register a Finnish company in Peppol and reach every Peppol-reachable participant — but recipients that are only addressable through domestic operator routing need a separate interoperability or partnership arrangement with the Finnish operator infrastructure. For invoicing the State through its domestic operator channel, the State Treasury points to routing via a provider holding the relevant agreement with the government's operator.

Identifiers and OVT

Finland is unusually prescriptive here, and getting it wrong is a common onboarding failure. The Finnish Peppol Authority Specific Requirements state that Finnish end users must be identified by the Finnish OVT code under scheme 0216.

Scheme0216 — the Finnish OVT code

OVT structure0037 + the Finnish Business ID without its hyphen + an optional qualifier of up to five characters

Worked exampleBusiness ID 1234567-8 → OVT 003712345678 → participant identifier 0216:003712345678

VAT number as an alternativeNo. Registering a Finnish end user under a VAT-number scheme instead of the OVT is not the ordinary alternative — the requirement is the OVT

If your platform defaults to "identify EU participants by VAT number", Finland is where that assumption breaks. Build the OVT derivation from the Business ID into onboarding rather than asking clients for a code they may not know they have.

Peppol in Finland

The Finnish Peppol Authority is the State Treasury (Valtiokonttori), a government agency under the Ministry of Finance, which took the role in 2022. Unlike countries where OpenPeppol fills the gap, Finland has a real national authority with real national requirements — set out under Requirements for providers.

Peppol's position in Finland is strategic rather than dominant. It is promoted for cross-border invoicing, international procurement, eOrdering, eDelivery and the wider harmonisation of electronic business documents — while the bulk of domestic invoice traffic continues to run on the national operator network.

Requirements for providers

There is no Finnish accreditation comparable to the Slovak digitálny poštár. The State Treasury describes the ordinary OpenPeppol operating model: a Service Provider is an OpenPeppol member, signs the Service Provider Agreement with the Peppol Authority of the jurisdiction where it mainly operates, may have customers in any country, and applies the Authority Specific Requirements of each customer's jurisdiction. A German-certified Access Point can therefore onboard a Finnish customer directly.

What is not required

A separate Finnish Peppol licence, or re-registration as a Finnish Access Point because a customer is Finnish

A Finnish company, branch, office, employee or Finland-only hosting

A local representative appointed specifically for Access Point activity

A state-issued official electronic mailbox — routing is by participant identifier and SMP discovery

What is required for Finnish end users

Business ID checkVerify the Finnish end user's Business ID against the official registration infrastructure — the Patent and Registration Office and the Business Information System

Authority to representVerify that the person or entity acting for the organisation is entitled to do so, for example by Trade Register extract or equivalent evidence. In effect, a Peppol KYC requirement

Identifier schemeOVT under 0216, without exception for Finnish end users

National ACLFinnish public sector addresses must be maintained in the national Address and Capability Lookup. Providers may also maintain Finnish private organisations there. Using it requires accepting the Terms of Use — which include having at least one Finnish customer and not being subject to EU or UN sanctions

Change handlingParticipant identifier and service provider changes must be processed within three working days

ISO 27001Recommended, not stated as an unconditional national certification requirement

None of this is a barrier — but all of it is checkable, and a provider that has not implemented the OVT rule and the onboarding verification will be non-conformant on its first Finnish customer.

The 2026 assessment

The State Treasury prepared an assessment memorandum on electronic business vouchers — e-invoices, Peppol procurement messages and eReceipts — describing regulatory options and their likely effects, as part of its role in the Real-Time Economy ecosystem. Three options were put forward for e-invoices:

Extensive obligation — e-invoicing always mandatory in invoicing between organisations

Limited obligation — where an e-invoice is used, it must comply with the standard

Market-based development — current legislation remains in force

The consultation ran from 2 February to 13 March 2026 and drew 47 opinions. On e-invoices, 24 respondents favoured developing e-invoicing through legislation and 11 opposed it — but the split by sector is the interesting part. Public sector respondents were 18 in favour to 3 against; private sector respondents were 6 in favour to 8 against. Respondents generally agreed that a European-standard invoice was the right technical answer, and pressed for realistic transition periods, an assessment of the burden on small businesses, and coordination with the entry into force of ViDA.

Where it stands

On 27 May 2026 the State Treasury confirmed the work was complete and stated plainly that the assessment memorandum and the opinion procedure are not related to the ongoing legislative project. The material was handed to the ministries, which will decide whether to take it into legislative drafting or add it to the next Government Programme. That is the honest status: a well-documented policy input, not a mandate in preparation.

ViDA and 2030

The ViDA package — Directive (EU) 2025/516, Regulation (EU) 2025/517 and Implementing Regulation (EU) 2025/518 — was published in the Official Journal on 25 March 2025. From 1 July 2030 the cross-border B2B transactions in scope move to mandatory e-invoicing with digital transaction reporting built on it, with EN 16931 as the semantic base. The Directive also changes invoicing timing for those transactions, introducing a ten-day issuance deadline after the chargeable event.

ViDA does not make Peppol the mandatory transport channel. Finland has not published a final national CTC specification, has not selected a five-corner model, a central tax gateway, a national reporting API or mandatory reporting through Finnish Peppol Service Providers. Hard-coding "Finland ViDA = mandatory Peppol reporting" would be building against a requirement that does not exist.

The defensible architecture is EN 16931 semantic data, a ViDA-compatible structured invoice, and a reporting and transport layer that can be adapted when the national implementation is specified.

Archiving

Finland has two retention periods, and mixing them up is the usual error. Under the Accounting Act (1336/1997), vouchers — including sales and purchase invoices — and correspondence relating to business transactions are retained for at least six years after the end of the financial year. Financial statements, the annual report, the accounting books and the chart of accounts are retained for at least ten years.

The six years run from the end of the financial year, not from the invoice date — which is why the period is often described in practice as six years plus the run-out of the current year

Retain the XML — the Finvoice, TEAPPSXML or UBL document is the invoice; a rendered visualisation is a convenience copy

Electronic storage is normal and expected here. Legibility and integrity must hold across the whole period, and the records must remain producible on request

Nothing is archived on your behalf by the state. An operator's archiving service is a commercial arrangement, which is worth confirming explicitly when a client moves between providers — the six-year clock does not restart because the vendor changed.

Consequences and VAT deduction

No dedicated administrative fine or per-invoice penalty for breaching the e-invoicing requirement was identified in Act 241/2019. The Act is built as a receiver capability obligation, a statutory right to request, and a European standard compliance framework — not as a fiscal penalty regime. The government proposal discusses formats being agreed between the parties and the consequences of that contractual relationship, rather than establishing a national fine table.

What actually happens

—In the central government channel the invoice is validated, and a non-compliant one can be discarded. It must be corrected and resent

—An invoice with insufficient VAT or invoice data can be returned and will not be paid until corrected

—Payment delay, contractual consequences, delivery disputes, and breach of procurement or contract terms

—Where the invoice is wrong as a matter of VAT law, the ordinary Finnish VAT consequences apply — not a special e-invoicing penalty

VAT deduction

A structured e-invoice is not the exclusive basis for deducting VAT in Finland. The Tax Administration treats the invoice as the key evidence of the right to deduct and the VAT Act sets invoice-related conditions, but nowhere is an EN 16931 XML made the only admissible form. A purchaser should normally hold the original invoice and should request a corrected one where it is wrong; an incorrect invoice can obstruct the deduction. Even so, the Tax Administration may in certain circumstances accept the right to deduct where the invoice does not fully meet the formal content requirements, if the taxpayer can demonstrate entitlement by other means, and minor errors do not automatically destroy the right.

So the absence of a Finvoice, TEAPPSXML or Peppol BIS XML does not by itself cost the buyer its deduction — provided a structured invoice was not required for that scenario and the ordinary VAT conditions are met.

How we help

Finland needs no licence and no local entity — it needs the national requirements implemented properly and an honest answer about reach:

Peppol BIS Billing 3.0 and EN 16931 in both syntaxes — UBL 2.1 and UN/CEFACT CII D16B

Addressing on 0216 with the OVT derived from the Business ID, rather than assuming a VAT-number scheme

Onboarding that verifies the Business ID and the authority to represent, as the Finnish requirements demand

Validation against the European standard before sending to central government, so nothing is silently discarded

Conversion between Finvoice, TEAPPSXML and UBL, so a Finnish source system can reach a Peppol-only counterparty and vice versa

A clear answer on which Finnish recipients are reachable over Peppol and which require domestic operator routing

Preparation of intra-EU B2B flows for the ViDA requirements, including the shorter issuance deadline

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Is e-invoicing mandatory in Finland?

Not generally. There is no universal domestic B2B mandate and none for B2C. Contracting authorities must be able to receive and process EN 16931 invoices, central government accepts only European-standard e-invoices, and a business with turnover above €10,000 may demand a European-standard e-invoice from its suppliers — in which case the supplier must provide one. That is a floor with an enforcement mechanism, not a blanket obligation.

Has Finland approved a general B2B mandate?

No, and there is no date. The most recent development is the State Treasury's assessment memorandum on electronic business vouchers, consulted between 2 February and 13 March 2026 with 47 opinions received. On 27 May 2026 the State Treasury stated that the memorandum and the opinion procedure are not related to the ongoing legislative project, and handed the material to the ministries to decide whether to begin drafting or add it to the next Government Programme.

Does Peppol certification let me reach the whole Finnish market?

No — this is the most important practical limitation in Finland. The domestic market runs largely on a network of national e-invoicing operators exchanging Finvoice and TEAPPSXML, which is a separate infrastructure from Peppol. A certified Access Point can register Finnish companies in Peppol and reach every Peppol-reachable participant, but recipients addressable only through domestic operator routing require a separate interoperability or partnership arrangement with the Finnish operator ecosystem.

Which identifier do I use for a Finnish participant?

The Finnish OVT code under EAS 0216. The OVT is formed as 0037 plus the Finnish Business ID without its hyphen, with an optional qualifier of up to five characters. So Business ID 1234567-8 becomes OVT 003712345678 and participant identifier 0216:003712345678. Registering a Finnish end user under a VAT-number scheme instead is not the ordinary alternative — the Finnish requirements specify the OVT.

Can a foreign EU Peppol Access Point serve Finnish clients?

Yes, directly. Under the OpenPeppol model the provider signs its Service Provider Agreement with the Peppol Authority where it mainly operates, may have customers in any country, and applies the Authority Specific Requirements of each customer's jurisdiction. No Finnish licence, legal entity, branch, office, local representative or official mailbox is required. What is required is compliance with the Finnish requirements for Finnish end users — chiefly the OVT scheme and the onboarding verification.

What does Finland require at onboarding?

Verification of the Finnish end user's Business ID against the official registration infrastructure, and verification that the person or entity acting for the organisation has authority to do so — for example by Trade Register extract. Beyond that: the OVT identifier scheme, maintenance of Finnish public sector addresses in the national ACL under its Terms of Use, and processing of participant or provider changes within three working days. ISO 27001 is recommended rather than stated as an unconditional requirement.

Can I send PDF invoices in Finland?

In ordinary B2B and B2C, yes — for VAT purposes an invoice may be on paper or in electronic form, and a PDF can be a valid VAT invoice. But a PDF is not a structured e-invoice under Act 241/2019 or EN 16931, so it fails where a buyer has exercised the right to demand a European-standard invoice, and it is not accepted by central government at all: an invoice attached to an email, a PDF invoice or an image of an invoice are expressly not e-invoices.

Does Finland have real-time reporting or clearance?

Neither. Invoices are not sent to the Tax Administration for prior authorisation, receive no clearance code, are not validated by the tax authority before delivery and need not pass through a central government platform. The EU country factsheet records Finland as having no VAT real-time reporting system. There is no five-corner model and no mandatory tax reporting corner.

How long must invoices be kept?

Two periods apply under the Accounting Act. Vouchers — including sales and purchase invoices — and correspondence relating to business transactions: at least six years after the end of the financial year. Financial statements, the annual report, accounting books and the chart of accounts: at least ten years. Because the six years run from the end of the financial year rather than the invoice date, the effective period is often described as six years plus the remainder of the current year. Retain the XML rather than only a rendered copy.

What is the penalty for not sending an e-invoice?

No dedicated fine under Act 241/2019 was identified — the Act is not built as a penalty regime. The real consequences are operational and contractual: in the central government channel a non-compliant invoice can be discarded and must be corrected and resent; an invoice with insufficient data can be returned and will not be paid until fixed; and payment delay or breach of contract terms may follow. Where the invoice is wrong under VAT law, the ordinary VAT consequences apply.

Summary

Finland shows what high e-invoicing adoption looks like when it is built rather than imposed. No clearance, no continuous transaction control, no real-time VAT reporting, no general B2B mandate — but a central government that accepts only European-standard invoices, and a statutory right that lets any business above €10,000 turnover insist on one.

The two facts a foreign provider must internalise are structural rather than legal: Finnish participants are addressed by OVT under scheme 0216, not by VAT number; and Peppol is not the domestic network. Reaching the whole market means dealing with the Finvoice and TEAPPSXML operator ecosystem as well.

One firm date sits on the horizon, and it is not Finnish: 1 July 2030, when ViDA makes structured invoicing and digital reporting mandatory for intra-EU B2B. Everything else here is still a question the ministries have not answered.

Resources

State Treasury — invoicing the State The operational rules for central government: accepted formats, channels, validation and what is not an e-invoice State Treasury — government e-invoices The Finnish Peppol Authority's service area, including the national requirements and ACL State Treasury — opinions on the assessment memorandum, 27 May 2026 The primary source on the three regulatory options, the 47 opinions and the statement that this is not part of the legislative project State Treasury — the consultation launch, February 2026 Background to the assessment and its place in the Real-Time Economy programme Finnish Tax Administration — VAT invoice requirements Invoice content, electronic form, cross-border rules and the evidential basis for deduction Accounting Act 1336/1997 (English translation, PDF) The statutory basis for the six-year and ten-year retention periods European Commission — eInvoicing in Finland The country profile: the €10,000 threshold, the B2G position and the absence of real-time VAT reporting Peppol BIS Billing 3.0 The profile used over Peppol for Finnish public sector and cross-border delivery Peppol Electronic Address Scheme code list Where 0216, the Finnish OVT code, sits alongside every other addressing scheme European Commission — VAT in the Digital Age (ViDA) The 2030 obligations and the changed invoicing deadlines — the only fixed dates on Finland's horizon Peppol Directory Check whether a Finnish participant is reachable over Peppol before assuming it is

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial