E-Invoicing in Estonia — e-arve, PEPPOL & B2G Guide

Estonia is one of the EU's most advanced e-invoicing countries. B2G has been mandatory since 2019; B2B e-arve via banking channels is the de facto standard without a legal mandate. Two formats coexist: the domestic e-arve (Pangaliit) for local B2B/B2G and PEPPOL BIS 3.0 for cross-border EU invoicing.

Estonian e-invoicing timeline

2007

e-arve format introduced

Eesti Pangaliit (Estonian Banking Association) published the first e-arve XML format, enabling structured invoice exchange through banking channels (LHV, SEB, Swedbank). B2B adoption grew organically through the banking infrastructure — no legal mandate needed.

2015

Estonia joins PEPPOL

Estonia became one of the first EU members to join the PEPPOL network. PEPPOL access points operate across the country, enabling cross-border e-invoice exchange with other EU member states.

Jan 2019

B2G mandatory

All Estonian state bodies and most local authorities require e-invoices since January 2019. Both e-arve and PEPPOL BIS 3.0 are accepted depending on the buyer's preferred channel.

e-arve vs PEPPOL: which to use?

e-arve (Pangaliit format)

The Estonian domestic format published by Eesti Pangaliit. Root element <E_Invoice> without XML namespace. Two schema versions: 1.11 (dominant in banking channels) and 1.2 (newer, EN 16931-aligned). Transmitted through banking channels (LHV, SEB, Swedbank) and operators (Finbite, Telema, Omniva). Required for domestic B2G at most state bodies.

PEPPOL BIS 3.0

The EU-standard format for cross-border B2B and B2G invoicing. UBL 2.1 based, EN 16931 compliant. Use for invoices to buyers in other EU countries, and for Estonian state bodies that accept PEPPOL delivery. Many Estonian companies use both: e-arve for domestic partners and PEPPOL for cross-border.

e-arve operators

To receive e-arve, a business must register with at least one operator: Finbite (formerly Omniva finance), Telema, or connect directly via banking channels (LHV Connect, SEB Gateway, Swedbank Biznet). Most Estonian ERP and accounting software has built-in connectors to these operators.

aiDoks supports both

The aiDoks validator handles both formats from a single upload: e-arve XML (versions 1.11 and 1.2) and PEPPOL BIS 3.0. Format is auto-detected from the root element. The e-arve generator (Phase D in the roadmap) will produce e-arve XML for Finbite, Telema and Omniva output channels from the guided form.

E-invoicing in Estonia: FAQ

Is e-invoicing mandatory in Estonia?

B2G is mandatory: all Estonian state bodies and most local authorities have required e-invoices since 2019. For B2B, there is no legal mandate, but e-arve via banking channels is the de facto standard — most large Estonian companies and the banking system (LHV, SEB, Swedbank) exchange invoices in e-arve format. Estonia was one of the first EU members to achieve near-universal B2B e-invoicing adoption without a legal mandate.

What is the e-arve format?

e-arve is the Estonian domestic electronic invoice format published by Eesti Pangaliit (Estonian Banking Association). It uses a custom XML structure (root element <E_Invoice>, no XML namespace) that predates EU PEPPOL adoption. Two schema versions exist: 1.11 (dominant in banking channels) and 1.2 (newer, EN 16931-aligned). e-arve is separate from PEPPOL BIS 3.0 — Estonian cross-border invoices use PEPPOL while domestic invoices typically use e-arve.

What role does PEPPOL play in Estonian e-invoicing?

Estonia joined the PEPPOL network in 2015 and operates an active PEPPOL Access Point ecosystem. PEPPOL BIS 3.0 is the standard format for cross-border e-invoicing (to EU buyers/suppliers) and for invoices to Estonian state buyers that require PEPPOL delivery. For domestic B2B within Estonia, e-arve through banking channels remains dominant. Many Estonian businesses use both: e-arve for local partners and PEPPOL for cross-border.

Which operators handle e-arve in Estonia?

E-arve is transmitted through banking channels (LHV, SEB, Swedbank) and dedicated operators: Finbite (formerly Omniva finance), Telema, and Merit Aktiva, among others. To receive e-arve, a business must register with one or more operators who then route invoices to and from banking channels. Most Estonian ERP and accounting software has built-in connectors to these operators.

Which format should I use for Estonian B2G invoices?

For Estonian state bodies, both e-arve and PEPPOL BIS 3.0 are accepted — check with the specific buyer which channel they prefer. The state portal (rmp.fin.ee) accepts e-arve; many state entities also have PEPPOL access points. For cross-border invoices to EU buyers, always use PEPPOL BIS 3.0.

How does aiDoks help with Estonian e-invoicing?

aiDoks validates both Estonian e-arve XML (versions 1.11 and 1.2) and PEPPOL BIS 3.0 invoices — covering both domestic and cross-border Estonian e-invoicing. The validator auto-detects the format from the root element. The e-arve generator (Phase D in the roadmap) will produce e-arve XML from the guided form, targeting Finbite, Telema and Omniva as output channels.

Validate Estonian e-arve and PEPPOL invoices — free

Single validator, both formats auto-detected. No account required.