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.

Tieke — 30+ accredited operators

The Finnish e-invoicing market is animated by a network of more than 30 operators accredited by Tieke (Tietoyhteiskunnan kehittämiskeskus) — a worldwide-unique mix of operating banks (OP, Nordea, Danske, Aktia, S-Pankki) and pure-players (Apix, Maventa, Procountor, Liaison, Pagero, Basware). Inter-operator routing goes through the OVT-tunnus, an alphanumeric identifier of 12 to 17 characters registered in the central directory.

Tieke — governance and role

Tieke ry (Tietoyhteiskunnan kehittämiskeskus — Finnish national centre for information society development) is a non-profit association founded in 1981, bringing together the main public and private stakeholders of Finnish digital transformation (administrations, banks, software vendors, telcos, universities).

For e-invoicing, Tieke fulfils three essential roles:

  1. Operator accreditation. Every operator wishing to send/receive Finvoice must sign the Tieke operator agreement (Verkkolaskuoperaattorisopimus). Conformance, traceability and interoperability commitments with other operators.
  2. OVT-tunnus directory maintenance. The central registry mapping every OVT-tunnus to a sender or recipient operator. Real-time updates by operators.
  3. Verkkolaskufoorumi. Quarterly technical committee governing the evolution of the Finvoice standard (with Finanssiala) and the interoperability rules.

Operating banks

A Finnish specificity: most large banks operate their own e-invoicing service themselves, integrated into their corporate banking offering. The main players:

BankE-invoicing serviceNotes
OP Bank (Pohjola)OP Verkkolasku#1 Finnish bank, e-invoicing leader in SMEs. Service integrated to OP-Yritysasiakkaat. BIC OKOYFIHH.
NordeaNordea VerkkolaskuPan-European Nordic bank. Offer integrated to Nordea Business. BIC NDEAFIHH.
Danske BankDanske VerkkolaskuStrong large-corporate presence. BIC DABAFIHH.
AktiaAktia VerkkolaskuHelsinki + Vaasa regional bank, strong coastal presence. BIC HELSFIHH.
S-PankkiS-VerkkolaskuS-Group cooperative bank. BIC SBANFIHH.
SäästöpankkiFederated savings banksRegional cooperative network.
POP-PankkiPOP VerkkolaskuFederated popular banks — cooperative.
HandelsbankenHandelsbanken VerkkolaskuFinnish subsidiary of Sweden's Handelsbanken.

Pure-play e-invoicing operators

Alongside banks, a dense ecosystem of pure-players also operates Finvoice and PEPPOL services, often white-label for ERP vendors or integrated with accounting suites:

OperatorGroupSpecialisation
ApixTelia Company#1 FI pure-player, SME + Large Account focus. Integrated Tikon, Talgraf.
MaventaVismaVisma's Nordic hub (Norway, Sweden, Finland, Denmark). Strong integration with Visma eAccounting + Procountor.
ProcountorProcountor International (Accountor Group)Accounting suite + integrated e-invoicing, dominant in SME accounting.
Liaison TechnologiesOpenTextMultinational EDI / e-invoicing, large-account cross-border focus.
PageroThomson Reuters (acq. 2024)Swedish origin, strong FI/SE/NO presence. Global network.
BaswareAccel Group (since 2022)FI origin (Espoo). Global enterprise reference. Basware Verkkolasku FI subsidiary.
ComarchComarch SA (Poland)Multi-country EDI VAN, FI presence via Comarch EDI.
TradeshiftTradeshift IncGlobal enterprise network, niche FI presence.
EdicomEdicom SL (Spain)Multi-country B2B/G, FI presence via partner-bank operators.
TikonAditro / VismaAccounting ERP + e-invoicing historically integrated.

OVT-tunnus — routing address

The OVT-tunnus (Organisaatioiden Välisen Tiedonsiirron tunnus — inter-organisational data exchange identifier) is the identifier used to route a Finvoice invoice across the inter-operator network. Its typical structure:

text ovt-tunnus-format.txt
OVT-tunnus — format
─────────────────────────────────────

Structure:
  003700ABBBBBBBCCCCC
  │     │       │
  │     │       └─> 5 optional chars (internal sub-identifier)
  │     └─────────> 8 chars (Y-tunnus PRH without dash, NNNNNNN-N)
  └───────────────> PEPPOL ICD prefix 0037 (Finland)

Example: 003712345678 (short — 12 chars)
         0037123456780000 (with sub-id — 16 chars)

Notes:
- Alphanumeric format, length 12 to 17 characters.
- Prefix 0037 = PEPPOL ICD for Finland (BusinessIDcode FI registries).
- The sub-identifier (last 5 chars) lets a large group route to a
  specific subsidiary or department.
- Published in Tieke's "verkkolaskuosoitteisto" (e-invoice directory)
  on tieke.fi/palvelut/verkkolaskuosoitteisto.

Inter-operator interoperability

A Finvoice sender at OP Bank can send to a Finvoice recipient at Maventa, and the invoice arrives without user intervention. The mechanism:

text routing-flow.txt
┌──────────────┐   1. Finvoice XML        ┌──────────────────┐
│  Sender      │ ───────────────────────> │  OP operator     │
│  (SME OP)    │   OVT 003700ABBBBBBBB    │  (Pankki)        │
└──────────────┘                          └────────┬─────────┘

                          2. Tieke lookup          │
                          (OVT-tunnus directory)   │

                                       ┌────────────────────────┐
                                       │ Tieke directory        │
                                       │ verkkolaskuosoitteisto │
                                       │ (api.tieke.fi)         │
                                       └────────────┬───────────┘
                                                    │ 3. Resolution
                                                    │    → target operator

                                       ┌──────────────────────┐
                                       │  Maventa operator    │
                                       │  (Visma)             │
                                       └────────────┬─────────┘

                                                    │ 4. Delivery

                                       ┌──────────────────────┐
                                       │   Recipient          │
                                       │   (SME on Maventa)   │
                                       └──────────────────────┘
  1. The sender composes the invoice in its ERP, sends it to its operator (OP in this example) with the recipient OVT-tunnus in MessageReceiverDetails / ToIdentifier.
  2. The operator looks up the Tieke directory via api.tieke.fi to resolve the OVT to a target operator (Maventa).
  3. OP forwards to Maventa via an inter-operator protocol — historically by bilateral agreement (REST, SFTP), increasingly AS4 PEPPOL for cross-border flows.
  4. Maventa delivers to the recipient in the format of its choice (raw Finvoice XML, or UBL conversion, or PDF preview).

Common pitfalls

  • Wrongly prefixed OVT-tunnus. An OVT-tunnus without the 0037 ICD prefix is not PEPPOL-routable. Always serve 003712345678 and not 12345678 in cross-border contexts.
  • Sub-identifier ignored. The last 5 chars (sub-id) let a large group route to a department. Operators deliver by default to the header (first 12 chars) if the sub-id does not exist. Misconfigured, internal routing is lost.
  • Thinking every bank does everything. Some banks (notably S-Pankki) outsource their Finvoice backbone to a third-party operator (often Apix or Maventa). The bank BIC does not always reflect the real operator.
  • Confusing BIC and OVT. The SWIFT BIC (8/11 chars) is used in FromIntermediator / ToIntermediator to designate the operator. The OVT-tunnus identifies the recipient organisation, not its operator. Both coexist in the MessageTransmissionDetails header.
  • Out-of-date directory. Operator changes are frequent in Finland (strong competition). Always query the Tieke API at each send instead of caching the target operator.