Startup Guide

The Complete Guide to E-Invoicing in Finland: Verkkolaskutus, Finvoice 3.0, Peppol & Statutory B2B Billing

VerkkolaskuE-Invoicing FinlandFinvoicePeppolB2B InvoicingStartups FinlandMaventaApix

The Modern Invoicing Landscape in Finland

Finland is an international pioneer in digital business integration. While many European markets still rely heavily on PDF invoices attached to emails, Finland's B2B ecosystem operates almost exclusively on structured electronic invoicing (verkkolaskutus).

In Finland, an e-invoice is not a digital image or PDF document. It is a structured XML data file transmitted electronically between software systems via secure transmission operators or banking networks.

Under the Finnish E-Invoicing Act (Laki sähköisestä laskutuksesta 241/2019), buyers have a statutory right to demand invoices in a structured electronic format from suppliers. If your startup attempts to bill corporate clients or public sector organizations using manual PDF attachments, you risk delayed payments, manual processing rejections, or damaged commercial credibility.

This guide provides a step-by-step walkthrough of Finnish e-invoicing standards, operator setup, OVT addressing, and legal invoice requirements.


1. Technical Standards: Finvoice, TEAPPSXML, and Peppol

Electronic invoicing in Finland is built on three interoperable data standards:

  1. Finvoice 3.0: The primary domestic banking standard developed by the Federation of Finnish Financial Services (Finanssiala ry). Widely used by commercial banks and domestic accounting platforms.
  2. TEAPPSXML 3.0: An industry-standard format maintained by Tietoevry, commonly used in enterprise supply chains.
  3. European Standard EN 16931 & Peppol (Pan-European Public Procurement On-Line): The international e-delivery network standard required for public procurement across the EU and increasingly adopted by multinational tech corporations.

Most modern Finnish accounting platforms (Netvisor, Procountor, Fennoa) automatically convert outgoing invoice data into the recipient's required XML standard without manual developer intervention.


2. Anatomy of a Finnish E-Invoice Address

To exchange e-invoices, a company does not use an email address. Instead, every Finnish business is assigned a two-part digital routing identity:

Part A: The E-Invoicing Address (Verkkolaskuosoite / OVT-tunnus)

For Finnish limited companies, the e-invoicing address is almost universally formatted using the OVT identifier standard: $$\text{OVT-tunnus} = 0037 + \text{Business ID (8 digits without hyphen)} + [\text{Optional Sub-Department}]$$

  • Example: If your company's Business ID (Y-tunnus) is 1234567-8, your primary OVT address is 003712345678.
  • If routing through a commercial bank, some institutions issue an IBAN-based e-invoicing address (e.g., FI2112345678901234).

Part B: The Operator Identifier (Välittäjätunnus)

The operator identifier tells the transmission network which specialized gateway or bank routes your files.

Transmission Operator Operator Code (Välittäjätunnus) Common Platform Pairings
Maventa (Visma) 003721291126 Netvisor, Severa, Visma software suites
Apix Messaging Oy 003723327487 Fennoa, Briox, independent accounting portals
Accountor / Procountor 003710948874 Procountor, Tikon
Basware BAWCFI22 Enterprise ERPs, global corporate networks
Nordea Bank DABAFIHH (or bank-specific EDI) Direct commercial banking integrations
OP Financial Group OKOYFIHH Cooperative banking e-invoice channels

3. Statutory Mandatory Invoice Fields Under Finnish VAT Law

Under Section 209b of the Finnish Value Added Tax Act (Arvonlisäverolaki 1501/1993 / AVL), every B2B invoice issued by a Finnish business must contain specific statutory elements to remain valid for tax deductions:

  1. Date of Issue: The date the invoice was generated.
  2. Sequential Invoice Number: A unique, sequential numbering sequence based on one or more series.
  3. Seller Information: Full registered corporate name, registered address, and official Business ID (Y-tunnus).
  4. Seller VAT Number: Formatted with the international prefix FI followed by the 8 digits without hyphen (e.g., FI12345678).
  5. Buyer Information: Full legal corporate name, address, and VAT ID (for EU cross-border B2B sales).
  6. Date of Supply: The date goods were delivered or services completed, or prepayment date.
  7. Description & Quantity: Clear description and volume of goods delivered or services rendered.
  8. Tax Base per VAT Rate: Net amount broken down by applicable VAT rate (e.g., 25.5%, 13.5%, 10%, 0%).
  9. VAT Amount Payable: Total VAT due in Euros.
  10. Reverse Charge Reference: If billing an EU business under reverse charge, must state: "Reverse charge / Käännetty verovelvollisuus (AVL 65 § / Directive 2006/112/EC Article 196)".
  11. Prepayment Register Note: A formal statement: "Kuuluu ennakkoperintärekisteriin" (Registered in the Prepayment Register).

4. Payment Terms & Late Payment Interest (Korkolaki)

Commercial payment conditions in Finland are strictly regulated under the Act on Commercial Payment Terms (Laki kaupallisten sopimusten maksuehdoista 30/2013):

  • Standard B2B Payment Terms: Typically 14 to 30 days. Payment terms exceeding 30 days must be explicitly agreed upon in writing between the commercial parties. Terms exceeding 60 days are generally prohibited unless specifically justified.
  • Late Payment Interest: Governed by the Finnish Interest Act (Korkolaki 633/1982). For commercial transactions, the statutory penalty interest rate is the European Central Bank reference rate plus 8 percentage points.
  • Standard Recovery Compensation: Under Finnish law, a business creditor has an automatic statutory right to charge a fixed €40 standard recovery fee (vakiokorvaus) immediately once a commercial invoice becomes overdue, without requiring prior reminders.

To discover how electronic invoicing links directly with automated bank reconciliation and VAT accounting, explore our master guide: Financial Management for Startups in Finland.

Ready to Turn Your Expertise Into a Product?

Pomegroup becomes your second co-founder — we handle the code, you handle the domain.

Explore Financial Management Hub →