All countries

E-Invoicing in Finland

B2G MandatoryPeppol

Finland has mandatory B2G e-invoicing and a unique legal mechanism: companies with >€10K turnover can demand e-invoices from any supplier, who must comply. The country uses a decentralized operator model with national formats (Finvoice, TEAPPSXML) alongside Peppol. Voluntary B2B adoption is already very high (~99% of B2G invoices are electronic). Finland is preparing for EU ViDA (2028-2030).

Mandate Status

PhaseStatusScope
B2GLive (Apr 2020)All public authority suppliers
B2G sendingLive (Apr 2021)All B2G suppliers must send EN 16931
Right to demandLive (Apr 2020)Companies >€10K turnover can demand e-invoices
Peppol Advanced OrderingLive (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

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.

Common Rejection Patterns

#CodeDescription
1FI-R-001Finnish Business ID requiredFix guide
2FI-R-002Finvoice format for Finnish B2BFix guide

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

View all Finland error codes

Ship compliant Finland invoices

Validate, fix, and route Finland e-invoices through a single API. No XML editing required.

Get API Access