Message IconCustomer SupportUser IconContact SalesLock IconLogin
Arratech logo
Peppol Country Guide · Finland

Build for Finland’s mature invoice market.

Prepare for July 2030.

Finland combines high structured invoice adoption with national formats and a growing Peppol network. There is no domestic tax clearance platform, but vendors must handle exact format, address and buyer requirement rules.

4Network corners
0216OVT scheme
3Core format families
6 yearsInvoice retention
Scope and Legal Basis

Act on Electronic Invoicing 241/2019

Finland implemented Directive 2014/55/EU through the Act on Electronic Invoicing by Contracting Entities and Traders, 241/2019. It took effect for central government on 1 April 2019 and expanded to other contracting entities on 1 April 2020. The Act defines a compliant invoice as structured and aligned with European standard EN 16931.

From 1 April 2020, a contracting entity or trader covered by the Act can require another contracting entity or trader to send a compliant electronic invoice. The European Commission country sheet states that the business right applies where annual turnover exceeds €10,000. This is a buyer right, not a universal obligation to issue every domestic business invoice electronically.

Vendor implication: Do not model Finland as a clearance mandate. Build recipient capability discovery, EN 16931 validation, OVT routing and national format conversion. A buyer request can make structured delivery commercially essential even without a universal mandate.

B2GB2BB2C
Public contracting entities must receive and process EN 16931 compliant invoices. Central government will not accept email attachments as invoice delivery.No general mandate. A qualifying trader can demand a compliant structured invoice from another trader.Outside Act 241/2019. Consumer invoices remain subject to general Finnish VAT and consumer rules.

The Act excludes cases where electronic invoicing could disclose confidential information or endanger national security. It does not create sector phases or supplier size phases beyond the turnover condition for the business buyer right.

Implementation Timeline

From public receipt to European reporting

1 April 2019

Act 241/2019 applied to central government authorities and central purchasing bodies.

1 April 2020

The Act expanded to other contracting entities. Traders gained the right to request a compliant structured invoice.

1 April 2024

Central government introduced Peppol Advanced Ordering through procurement contracts.

31 Aug 2026 → Now

Current position. Finland has no announced general domestic business mandate or clearance platform.

1 July 2030

ViDA digital reporting starts for covered cross border business transactions across the European Union.

Architecture

A straightforward four corner model

Peppol exchange in Finland uses the standard four corner model. The sender and receiver each connect to a certified Service Provider. The Access Points discover capabilities and exchange the validated document over the network.

Corner 1SenderBusiness or ERP
Corner 2Sender Access PointArratech AP
Corner 3Receiver Access PointCertified provider
Corner 4ReceiverBusiness or public body
No government clearance corner: The invoice travels between service providers. It is not approved by the Finnish Tax Administration before delivery. Finnish VAT control remains based on records and returns, while ViDA introduces reporting for covered cross border transactions from July 2030.
Invoice Format Requirements

One semantic model, several syntaxes

Public buyers must support the European semantic standard. State Treasury guidance identifies UBL 2.1 and UN/CEFACT Cross Industry Invoice D16B as Commission syntaxes. Finland also uses national Finvoice 3.0 and TEAPPSXML 3.0 mappings, while Peppol BIS Billing 3 is common for Peppol exchange.

Accepted structured paths
  • Peppol BIS Billing 3
  • UBL 2.1 compliant with EN 16931
  • UN/CEFACT CII D16B compliant with EN 16931
  • Finvoice 3.0 European standard profile
  • TEAPPSXML 3.0 European standard profile
Not sufficient by itself
  • PDF or image invoice
  • Email attachment
  • Paper invoice
  • Unstructured XML
  • EDIFACT without compliant conversion

For Finnish Peppol participants, use the OVT code with scheme 0216. An OVT code begins with 0037, followed by the Finnish Business ID without punctuation and an optional organisational suffix. Resolve the participant and supported document type before sending.

Reporting Obligations

Separate invoicing from tax reporting

Finland currently has no continuous transaction control report tied to each domestic electronic invoice. Businesses continue to meet ordinary Finnish VAT return and sector reporting duties independently of Peppol delivery. Construction industry information reporting, for example, remains a separate process where applicable.

Finnish VAT guidance sets a specific issue deadline for intra Community supplies of goods and certain cross border services: by the fifteenth day of the calendar month following the supply month. The guidance does not state one equivalent universal issue window for every domestic invoice.

ViDA transition: From 1 July 2030, covered cross border business transactions enter the European digital reporting regime based on structured electronic invoices. The new reporting replaces recapitulative statements for those transactions. Keep reporting events separate from the invoice transport event in your product model.

Received invoices are not reported through a Finnish invoice clearance platform today. Retain invoice authenticity, integrity, readability and required VAT data. VAT invoices are generally stored for at least six years, measured under the rules explained by the Finnish Tax Administration.