What are Finland's e-invoicing requirements?

Finland mandates B2G e-invoicing since April 2020 and has over 80% voluntary B2B adoption — among the highest in Europe. The Finnish market uses Finvoice format alongside Peppol BIS Billing 3.0, with the banking network playing a central role in invoice delivery.

What is the Finvoice format?

Finvoice is Finland's national e-invoice standard, widely used for B2B and B2G transactions. It is delivered primarily through the Finnish banking network. While Peppol BIS Billing 3.0 adoption is growing, Finvoice remains the dominant format for domestic Finnish e-invoicing.

All countries

Country Guide

🇫🇮 E-Invoicing in Finland

B2G MandatoryPeppol

Finland has one of the EU's most mature e-invoicing ecosystems, with B2G e-invoicing mandatory since April 2020 and widespread voluntary B2B adoption. The Finnish market primarily uses the Finvoice format alongside Peppol BIS Billing 3.0. Finland's approach relies on market-driven adoption backed by strong digital infrastructure rather than punitive mandates.

B2G invoices must be sent electronically to Finnish government entities, with TEAPPS (the Finnish e-invoice standard) and Finvoice as the primary formats. The Finnish banking network plays a central role in e-invoice delivery, with most business banks offering Finvoice routing. Peppol adoption is growing alongside the established Finvoice ecosystem.

Finland's e-invoicing adoption rate exceeds 80% for B2B transactions — among the highest in Europe — driven by banking integration and strong digital culture rather than legal mandates. Invoice Navigator validates Finnish e-invoices against EN 16931 business rules and supports both Finvoice and Peppol BIS format validation.

While Finland does not currently impose penalties for B2B paper invoicing, government suppliers face payment delays if invoices are not submitted electronically. Finland is expected to align with EU-wide mandates under ViDA by 2028-2030.

TL;DR

Finland mandates B2G e-invoicing and has 80%+ voluntary B2B adoption via Finvoice and Peppol. One of Europe's most mature e-invoicing markets, driven by banking integration.

Last updated: January 2026

Quick Facts

Format

finvoice_3_0, teappsxml_3_0, peppol_bis_3_0

Peppol

Connected

Compliance

Mandate Status

Phase

Status

Scope

B2G

Live (Apr 2020)

All public authority suppliers

B2G sending

Live (Apr 2021)

All B2G suppliers must send EN 16931

Right to demand

Live (Apr 2020)

Companies >€10K turnover can demand e-invoices

Peppol Advanced Ordering

Live (Apr 2024)

Central government purchase orders

Technical Specifications

Validation engineDecentralized via operators (Telia, Basware, etc.)

Required CIUSFinvoice 3.0 / TEAPPSXML 3.0 (both EN 16931 compliant)

Routing identifierE-invoice address (registered in Verkkolaskuosoite directory)

PeppolYes — Peppol for cross-border and central government ordering

Accepted formatsfinvoice_3_0, teappsxml_3_0, peppol_bis_3_0

Practical

Common Rejection Patterns

#1FI-R-002Finvoice format for Finnish B2BFix guide

#2FI-R-001Finnish Business ID requiredFix guide

Invoice Navigator auto-remediates these at pipeline speed. See how →

View all Finland error codes

Implementation Notes

Finland's decentralized model means there's no single API to integrate with — you connect through operators.

Operator model. Finland uses private operators (banks and service providers) for e-invoice transmission. Your pipeline connects to an operator who handles routing via the Verkkolaskuosoite directory. This is similar to Peppol's Access Point model but predates it. If your customer already has a Finnish bank connection, they likely already have an e-invoicing channel.

Format duality. Finvoice 3.0 (bank network format) and TEAPPSXML 3.0 (industry format) are both EN 16931 compliant but structurally different. Most operators handle both, but your mapping logic needs to account for the format your customer's counterparties expect. Peppol BIS 3.0 is used for cross-border.

Right to demand. The legal right to demand e-invoices (Act 241/2019) means your customer's suppliers can be legally compelled to send structured invoices. This is a selling point for AP automation but also means your system must handle inbound invoices from suppliers who may be sending for the first time with minimal format compliance.

Stay Current