An e-invoice travels from Estonia to a Finnish customer with three things: the customer’s verkkolasku address (Finland’s e-invoicing address), the name of their operator, and a provider on your side that supports the Finland route. The Finnish e-invoicing address is usually an OVT code: built from the tax administration prefix 0037, the company’s business ID (Y-tunnus) and up to five extra characters – or an IBAN-based address. Any Finnish recipient’s address and operator can be verified in TIEKE’s public registry at verkkolaskuosoite.fi. You do not need a separate contract with a Finnish operator: Estonian operators maintain bridges to their Finnish counterparts, and the invoice moves through the operator cooperation network or Peppol.
Step by step: your first e-invoice to Finland
- Ask the customer for their verkkolasku address and operator (Finnish companies print these on invoices and websites) or look them up in the TIEKE registry.
- Confirm with your operator or software that the Finland route is supported: either a direct Finvoice bridge or via Peppol.
- Enter the customer’s OVT code and operator ID exactly as the registry shows them – most delivery failures are address typos.
- Send, and for the first invoice verify with the customer that it landed in their system with correct data.
Finvoice or Peppol: which route?
Finland’s local format is Finvoice and the domestic network runs between operators; at the same time many Finnish operators also support the Peppol network. In practice your customer’s channel decides: if their operator is on Peppol, Peppol is the simplest common path; if not, your operator’s Finvoice bridge handles the conversion. On either route it helps that your invoice complies with EN 16931 – Estonia’s primary e-invoice format since 1 July 2025, and the same standard Finland’s act 241/2019 refers to.
Can a Finnish customer demand an e-invoice?
Yes. Finland’s act 241/2019 gives contracting entities and businesses the right to receive, on request, an e-invoice conforming to the European standard. If your Finnish customer exercises that right, a PDF will not do, because the act refers to an e-invoice conforming to the European standard – similar to Estonia’s own buyer’s right. An exporter has two solid reasons to set the Finland route up properly: invoices arrive faster, and a formal demand will not catch you unprepared.
Also available in: eesti keeles
Last reviewed:
What do you need to send an e-invoice to Finland?
You need the customer’s verkkolasku address (usually an OVT code), the name of their operator, and your operator or software supporting the Finland route. You don’t need a separate contract with Finland.
What is an OVT code?
It’s the Finnish e-invoicing address: the prefix 0037 plus the company’s business ID (Y-tunnus, 8 digits) plus up to five extra characters. You can verify addresses in TIEKE’s registry at verkkolaskuosoite.fi.
Can a Finnish customer demand an e-invoice?
Yes – under Finland’s act 241/2019, a business has the right to receive, on request, an e-invoice conforming to the EN 16931 standard. A PDF does not satisfy this requirement.
Should you use Finvoice or Peppol?
It depends on which channel your customer’s operator supports: Peppol is the simplest path if both operators are on the network; otherwise your operator’s Finvoice bridge handles the conversion. Either way, the invoice must comply with the EN 16931 standard.