ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

Valtiokonttori B2G — EU pioneer since 2010

Valtiokonttori (Finnish State Treasury) is the first EU public body to have mandated structured electronic invoicing for all its vendors — as early as 1 December 2010, nearly eight years before Directive 2014/55/EU. The mandate relies on Finvoice + PEPPOL BIS Billing 3.0 and the national Handi platform.

History — 2010 B2G pioneer

Finland required its public vendors to issue structured e-invoices as early as 1 December 2010 — nearly a decade before Directive 2014/55/EU (transposable by 18 April 2019). The country leveraged the Finvoice standard (already widespread in B2B since 2003) to start quickly, without inventing a new format. This precedence remains one of the European records — shared with Denmark (NemHandel optional 2005, mandatory 2011).

text b2g-fi-timeline.txt
2008       | Valtiokonttori (State Treasury) launches a pilot
           | "Verkkolaskutus valtiolla" — e-invoicing for ministries.
           | 18-month pilot with 12 pilot agencies.
           |
1 Dec 2010 | B2G mandate — all central-state agencies (ministries + 60+
           | agencies) must receive their invoices in Finvoice format.
           | Primary format Finvoice 1.3, 2.0 accepted.
           | Decision ratified by the Council of State (Valtioneuvosto).
           |
2014       | EU Directive 2014/55/EU adopted — Finland is already 4 years
           | ahead of the European obligation (2018-2020).
           |
2017-2018  | Gradual migration to Finvoice 3.0 + PEPPOL BIS Billing 3.0.
           | Valtiokonttori officially becomes the PEPPOL Authority for
           | the public side in July 2018.
           |
2019       | Handi platform (State invoice manager) goes into production,
           | operated by Valtiokonttori on the Valtori sovereign cloud
           | (State ICT Service Centre).
           |
1 Apr 2020 | Act 241/2019 enters force — extends the right to receive
           | EN 16931 to all B2B. Valtiokonttori aligns and publishes a
           | joint recommendation with Vero.fi.
           |
2024-2026  | Gradual onboarding of municipalities (Kunnat) onto Handi
           | in "consolidated tracking" mode. Bill in discussion to
           | extend the B2G obligation to the 309 municipalities (with
           | exemptions).

Scope — who is mandated?

  • All Finnish ministries (Ministerit), ~13 ministries with their operational units. Paper invoices are refused outright since 1 April 2011 (except force majeure).
  • ~60 central-state agencies (virastot): Vero, Kela, Tulli (Customs), Maahanmuuttovirasto (Migration), Senaatti (Property), Liikenne- ja viestintävirasto Traficom, Maanmittauslaitos (Land Survey), etc.
  • Universities and public funds operating under ministerial oversight (but not municipalities/Kunnat per se, which follow a separate regime).
  • Partial exclusion: 309 municipalities (Kunnat) and 21 regions (Hyvinvointialueet — regional health authorities since 2023) — not covered by the 2010 mandate, but 80% voluntarily use Handi in 2024.
  • Threshold: none — any invoice, whatever the amount, must be structured. A paper invoice received by a ministry is returned to the sender with a mandate notice.

Architecture — Handi + Tieke operators

The core of the system is Handi, the national platform for receiving and managing state invoices, operated by Valtiokonttori on the Valtori sovereign cloud. Routing happens either via an accredited Tieke operator (classic Finvoice) or via a PEPPOL Access Point (BIS Billing 3.0). Handi performs validation, contract → purchase order → invoice matching, then pushes the ticket into the approval workflow at the destination ministry or agency.

text handi-flow.txt
┌──────────────┐    1. Finvoice 3.0 or       ┌──────────────────────┐
│   Vendor     │       PEPPOL BIS Billing 3.0│  Tieke operator      │
│  (Sender)    │ ───────────────────────────>│  (OP / Maventa /     │
└──────────────┘    via OVT-tunnus           │   Apix / Procountor) │
                    or ICD 0037              └──────────┬───────────┘

                                                        │ 2. AS4 routing
                                                        │    or banking network

                                          ┌──────────────────────┐
                                          │  HANDI               │
                                          │  (Valtiokonttori +   │
                                          │   Suomen             │
                                          │   Tilaajavastuu Oy)  │
                                          │  Reception + valid.  │
                                          │  Finvoice validation │
                                          │  + contract matching │
                                          └──────────┬───────────┘

                                                     │ 3. Approval workflow

                                          ┌──────────────────────┐
                                          │  Ministry / Agency   │
                                          │  Approver ↔ ERP      │
                                          │  Sepa / RT payment   │
                                          └──────────────────────┘

Accepted formats

FormatStatusNotes
Finvoice 1.3Accepted (legacy)Still accepted for backward compatibility of historical vendors. Gradual migration to 3.0.
Finvoice 2.0 / 2.01AcceptedTransitional format 2010-2017.
Finvoice 3.0RecommendedEN 16931 aligned — directly answers the right-to-receive of Act 241/2019.
PEPPOL BIS Billing 3.0RecommendedUBL 2.1 + PEPPOL CIUS. AS4 routing via international SMP/SML.
Generic UBL (no CIUS)RefusedRequires PEPPOL CIUS alignment or migration to Finvoice 3.0.
Factur-X / ZUGFeRDRefusedNot in the Finnish ecosystem — Franco-German formats.
PDF / paperRefused outrightReturned to sender without payment, except documented force majeure.

Penalties — refusal of payment

The Finnish setup does not impose financial penalties in the sense of criminal fines — the sanction is operational:

  • Immediate refusal of the invoice. A non-structured paper or PDF invoice sent to a ministry is returned to the sender without processing.
  • Payment suspension. As long as the compliant invoice is not received, the 30-day SEPA B2G clock does not start — so no late interest is due.
  • Operational notification. An automatic reminder letter is sent to the sender citing the Valtiokonttori regulation and a link to the list of accredited operators.
  • Contractual reference. Standard Hansel (Finnish public procurement centre) clauses have included the Finvoice obligation since 2012 — non-compliance may justify framework contract termination.

Common pitfalls

  • Wrong recipient OVT-tunnus. Each ministry and agency has its own OVT-tunnus, usually listed on handi.valtiokonttori.fi. An error (wrong agency code) puts the invoice in the "unknown recipient" queue for 48 hours before return to sender.
  • Forgetting the purchase order number. Handi runs automatic contract → purchase order → invoice matching. Without a valid PO number in the OrderIdentifier field, the invoice falls into the manual queue (~5 additional business days).
  • Confusing Handi and Hansel. Handi = invoicing platform. Hansel = procurement centre. The PO issued by Hansel must be referenced in the invoice sent to Handi.
  • Encoding a Finvoice 1.3 in UTF-8. Old flows are validated against ISO-8859-15. A Finvoice 1.3 invoice sent as UTF-8 without explicit declaration fails XSD validation in Handi.
  • Believing municipalities are covered. The 2010 mandate covers central state only. To invoice a Finnish municipality (Kunta), check its preferred channel individually — most accept Finvoice but via their own operator (often OP, Aktia or KuntaPro).