E-invoicing in Estonia: A Complete Guide for Businesses
Overview
Estonia has operated a structured e-invoicing infrastructure since 2014, making it one of the earliest EU adopters of machine-readable invoice exchange. The system is built on open standards coordinated by the Estonian Tax and Customs Board (Maksu- ja Tolliamet, MTA). Invoices to government entities must be submitted electronically; the B2G mandate is fully in force and enforced.
Estonia uses the Peppol network as the primary transport layer for both B2G and cross-border B2B invoice delivery. The national e-invoicing standard (e-arve) predates the EN 16931 European norm but aligns with it; Peppol BIS Billing 3.0 is the externally facing format used for Peppol-network delivery. The MTA does not act as a clearance hub for domestic invoices — B2G invoices are delivered via Peppol to the contracting authority's registered endpoint.
The EAS (Electronic Address Scheme) identifier 0191 is the Estonian scheme used in the Peppol network. It is based on the Estonian company registry code (äriregistri kood), an 8-digit number assigned to every registered legal entity.
Mandate and Timeline
Estonia's e-invoicing obligations are structured as follows:
| Segment | Status |
|---|---|
| B2G — central government suppliers | Mandatory (e-invoicing law since 2019, earlier practice since 2014) |
| B2G — local government suppliers | Mandatory |
| B2B — domestic | Voluntary; widely adopted via operator networks |
| Foreign suppliers to Estonian government | Must issue structured e-invoices via Peppol |
Key dates:
- 2014: Estonian e-invoice standard (e-arve) introduced for public procurement
- 2019: E-invoicing Act (e-arve seadus) enacted — B2G mandatory for all government tiers
- 2020: Peppol AS4 transport mandatory for cross-border B2G invoice delivery under EN 16931
- Ongoing: B2B mandate not yet legislated; market adoption continues through operator networks (e.g. Telema, Omniva, Unifiedpost)
For B2B transactions between private companies, e-invoicing is voluntary but commercially well-established. The dominant domestic operators (Telema, Omniva, Merit Tarkvara) exchange e-arve XML natively; Peppol BIS 3.0 is used where the recipient is registered on the Peppol network.
Format and Network
Estonia uses Peppol BIS Billing 3.0 for Peppol-network delivery without a national CIUS extension. Key technical characteristics:
- Standard: Peppol BIS Billing 3.0 (EN 16931 CIUS of OpenPeppol)
- Syntax: UBL 2.1 (preferred for Peppol); domestic e-arve uses a national XML schema
- Participant identifier scheme:
0191(EAS — Estonian company registry code, 8 digits) - Endpoint format:
0191:<registry_code>(e.g.0191:10137025) - Currency: EUR (Estonia has used the euro since 2011)
- VAT: standard rate 22% (raised from 20% in January 2024); reduced 9% (accommodation, books, medicines); zero rate applicable for exports and intra-EU supply
- Authority: Maksu- ja Tolliamet (MTA) — Tax and Customs Board
- No clearance: invoices are not submitted to the MTA for pre-clearance; delivery via Peppol satisfies the B2G mandate
Participant lookup is performed against the Peppol SMP/SML infrastructure. Government entities are registered in the central Peppol directory under the 0191 scheme.
Required Fields
For a valid Estonian Peppol BIS Billing 3.0 invoice the following fields are required:
invoiceNumber— unique supplier-assigned identifierissueDate— ISO 8601 date (YYYY-MM-DD)dueDate— payment due datecurrency— must beEURbuyerReference— buyer's purchase order or reference number (required for B2G)supplier.taxId— Estonian company registry code (8 digits)supplier.taxIdCountry—EEsupplier.endpointId—0191:<registry_code>supplier.endpointSchemeId—0191buyer.taxId— buyer's registry code or VAT identifierbuyer.taxIdCountry—EEfor domestic buyersbuyer.endpointId—0191:<registry_code>buyer.endpointSchemeId—0191lines[].taxCode— EN 16931 tax category code (Sfor standard rate)lines[].vatRate—22for standard Estonian VAT
The buyerReference field maps to cbc:BuyerReference in UBL 2.1 and is mandatory for Estonian government buyers.
Integration Example
Send an Estonian invoice via the Clearvo API:
curl -X POST https://api.clearvo.io/v1/invoices \
-H "Authorization: Bearer $CLEARVO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"country": "EE",
"documentType": "invoice",
"invoiceNumber": "EE-INV-2026-001",
"issueDate": "2026-06-16",
"dueDate": "2026-07-16",
"currency": "EUR",
"buyerReference": "PO-2026-001",
"supplier": {
"name": "Clearvo Technologies Ltd",
"taxId": "10137025",
"taxIdCountry": "EE",
"address": { "street": "Narva mnt 5", "city": "Tallinn", "postalCode": "10117", "country": "EE" },
"endpointId": "0191:10137025",
"endpointSchemeId": "0191"
},
"buyer": {
"name": "Estonia Buyer AS",
"taxId": "BUYEREE001",
"taxIdCountry": "EE",
"address": { "street": "Buyer Street 1", "city": "Tallinn", "postalCode": "10117", "country": "EE" },
"endpointId": "0191:BUYEREE001",
"endpointSchemeId": "0191"
},
"lines": [
{ "description": "Software consulting services", "quantity": 5, "unitPrice": 1000, "taxCode": "S", "vatRate": 22 },
{ "description": "Platform subscription annual", "quantity": 1, "unitPrice": 3600, "taxCode": "S", "vatRate": 22 }
]
}'
Clearvo performs a live SMP lookup on the buyer's 0191 endpoint before transmission, packages the invoice as a Peppol AS4 message, and returns the AS4 delivery receipt and generated UBL 2.1 XML. No separate tax engine or authority registration is required — the API handles Peppol participant resolution, XML generation, and delivery in a single call.
Key Rules
- Scheme ID
0191is mandatory: all Estonian Peppol participants — including government bodies — are registered under scheme0191. Using an incorrect scheme ID will cause SMP lookup failure and delivery rejection. - VAT rate is 22% since January 2024: prior fixtures using 20% are invalid for invoices dated from 1 January 2024 onward.
buyerReferencerequired for B2G: government buyers require a purchase order reference incbc:BuyerReference; omitting it causes rejection at the contracting authority level.- Registry code vs VAT number: the
0191scheme uses the company registry code (äriregistri kood), not the VAT number. The Estonian VAT number format isEEfollowed by a 9-digit number; the registry code is 8 digits. Do not use the VAT number as the Peppol endpoint identifier. - No pre-clearance: there is no Estonian government hub to register invoices with before sending. A successful AS4 delivery to the buyer's registered endpoint constitutes compliance.
- Domestic B2B via e-arve operators: for domestic B2B delivery to companies not registered on Peppol, use the national e-arve operator network (Telema, Omniva). The Clearvo API routes accordingly based on buyer registration status.
- Developer-first, single API: Clearvo exposes one endpoint regardless of destination — B2G or B2B, Peppol or e-arve operator. No tax engine is bundled; VAT calculation and line-level amounts are the caller's responsibility. Clearvo validates, transforms, routes, and delivers.
Related country guides
- Latvia — Peppol BIS 3.0, B2G mandatory
- Lithuania — Peppol BIS 3.0, B2G mandatory
- Finland — Peppol BIS 3.0, Finvoice B2G mandatory
Ready to handle e-invoicing in Estonia?
One API, all 31 countries. Sign up and get your API key within 24 hours.
Get started free →