Electronic invoice in Estonia

Buyer’s choice principle with e‑Invoice Operator Network – Flexible mandate

Select a country

Overview

Estonia is regularly listed as a country with a B2B e-invoicing mandate. That is a shorthand, and it hides the mechanism that actually matters. Since 1 July 2025 Estonia runs on a buyer's choice principle: an accounting entity that has publicly registered itself as an e-invoice recipient in the Business Register can require a structured e-invoice from its supplier, and the supplier must comply unless the parties have agreed otherwise. No registration, no obligation.

The same reform did something counter-intuitive that most summaries miss entirely: the general obligation that had applied since 2019 when the buyer was a public body was replaced by that same right. In practice nothing changed for the public sector, because every public entity is a registered recipient — but the legal construction is now a right exercised by the buyer, not a duty imposed on the seller. There is no clearance, no central platform and no real-time reporting.

0191 and 9931

the registry code and the VAT number — support both, never only the VAT number

~15,000

companies registered as e-invoice recipients when the reform was announced

7 years

retention for source documents — and electronic invoices stay electronic

Timeline

One reform is done and in force. The one everyone asks about — the general B2B mandate — is still a plan.

Already in force

1 July 2019

E-invoicing to the public sector becomes obligatory

A general obligation to issue an e-invoice where the buyer is a public sector body. Sub-central authorities followed in 2020.

19 September 2024

The Riigikogu adopts the Accounting Act amendments

Bill 428 SE. Two narrow changes with wide consequences — self-registration as an e-invoice recipient, and statutory support for the European standard only.

14 April 2025

ViDA enters into force

Directive (EU) 2025/516, adopted on 11 March 2025, allows member states to mandate domestic B2B e-invoicing without a derogation.

1 July 2025

Buyer's choice takes effect

The 2019 obligation is replaced by the buyer's right to choose the invoice format, and that right is extended to the private sector. See The buyer's choice principle.

Still ahead

2027 — planned

A general B2B mandate and the end of the €1,000 threshold

The Ministry of Finance has proposed making e-invoicing obligatory for VAT-registered businesses and removing the €1,000 reporting threshold. This requires an amendment to the VAT Act, which has not been adopted.

1 July 2030

ViDA digital reporting for intra-EU B2B

Structured e-invoicing and near-real-time digital reporting become mandatory for cross-border B2B inside the EU. See ViDA and 2030.

1 January 2035

Alignment of domestic reporting systems

Member states with pre-existing domestic transaction reporting must align it with the EU model. Estonia's KMD INF annex is periodic rather than real-time, and how it will be treated is a matter for the implementing legislation.

2027 is a policy target, not a statutory deadline. The Accounting Act changes that are in force were adopted in 2024; the general B2B mandate needs a separate amendment to the VAT Act, and that amendment has not been passed. The proposal is also contested domestically — the Estonian Chamber of Commerce and Industry has publicly opposed both removing the €1,000 threshold and making e-invoices mandatory. Writing "Estonian B2B e-invoicing becomes mandatory on 1 January 2027" as settled law would be wrong.

The buyer's choice principle

This is the whole Estonian regime in one mechanism, and it is worth being exact about because "Estonia has a B2B mandate" and "Estonia has no B2B mandate" are both wrong.

The buyer registers

An accounting entity publicly registers itself as an e-invoice recipient in the e-Business Register. Since the 2025 reform it can do this itself, rather than depending on an e-invoicing operator to do it — which is what made the register meaningful rather than a by-product of choosing a vendor.

The buyer can then require an e-invoice

Registration confers the right to demand a structured e-invoice from the seller. By default — unless the parties have agreed otherwise — the seller must issue one.

EN 16931 is the default

Where no other standard has been agreed, the European standard applies. The parties remain free to agree a different format — format freedom was expressly preserved.

The Ministry of Finance framed it plainly when the reform passed: Estonia applies maximum format freedom for accounting documents, and the buyer should be able to choose the form in which it wants to receive an invoice. That is the design intent — not a mandate, a default that the buyer switches on.

The practical consequence for a supplier is that the obligation is counterparty-specific and discoverable. Before invoicing an Estonian customer, check whether it is a registered e-invoice recipient. That check, not a turnover threshold or a sector rule, is what determines your obligation.

Who is in scope

Public sector buyersAll are registered e-invoice recipients, so in practice they receive e-invoices by default and the pre-2025 regime continues unchanged

Registered private buyersMay require a structured e-invoice. The seller must comply unless another arrangement is agreed

Unregistered buyersNo statutory right to demand one. The parties invoice as they agree

B2CNo mandate. In many ordinary consumer sales a standard VAT invoice is not even required

KMD INF reportingApplies to VAT-registered persons on transactions above the threshold, independently of how the invoice was delivered

One boundary worth stating carefully: the Accounting Act defines Estonian accounting entities — Estonian legal persons, sole proprietors and registered branches of foreign companies. It should not be read as giving a registered Estonian buyer a direct statutory claim against a supplier established in another member state simply because the customer is Estonian. See B2B and B2C for how that plays out in practice.

B2G

E-invoicing to Estonian public bodies has been the norm since 1 July 2019, and it remains the norm. What changed on 1 July 2025 is the legal route to the same result: the standalone obligation was replaced by the buyer's right, and public entities exercise that right because they are all registered recipients.

In practiceSend a structured e-invoice. Paper and PDF are not the working assumption in this channel

StandardEN 16931 by default, in practice Peppol BIS Billing 3.0 over the Peppol network

ChannelNo mandatory government platform. Any e-invoicing operator or Peppol Access Point that reaches the recipient

Small suppliersA free e-invoicing tool is available through the Centre of Registers and Information Systems for those without their own solution

Because the mechanism is now a right rather than a duty, the correct question before an unusual public-sector engagement is the same one you would ask of a private buyer: is this entity registered, and has it asked?

B2B and B2C

Domestic B2B is governed entirely by the buyer's choice mechanism. If the buyer is registered and asks, the seller issues a structured e-invoice; if the parties have agreed a different format, that agreement governs; if the buyer is not registered, ordinary invoicing rules apply.

Cross-border inside the EU

Today there is no separate Estonian cross-border e-invoicing mandate, and a registered Estonian buyer's statutory right should not be assumed to reach a supplier established elsewhere in the EU. A foreign seller looks instead to its own invoicing law, the VAT place-of-supply rules, the contract, and public procurement rules where the buyer is an authority.

That said, an Estonian buyer can perfectly well require a structured e-invoice as a condition of its purchasing process — a commercial requirement rather than a statutory one, and Peppol is the natural channel for meeting it. Separately, for intra-Community supplies and certain B2B services the invoice must be issued by the 15th day of the month following the supply, and the monthly recapitulative statement is due by the 20th.

Exports outside the EU

No Estonian rule requires an export to be invoiced as an EN 16931 e-invoice. VAT invoicing rules, zero-rating evidence and customs documentation apply; a structured format is used where the trading partner supports it. The ViDA intra-EU regime does not extend to third-country trade.

B2C

No mandate of any kind. PDF, a consumer receipt or another permitted form is fine under the ordinary VAT and accounting rules, and in many consumer sales a standard VAT invoice is not required at all — the usual exceptions being distance selling, supplies of new means of transport and certain tax-free export sales to third-country individuals.

Formats and PDF

Since the 2025 reform the Accounting Act supports the European standard only — while leaving transaction and format freedom intact, so other formats remain permitted where the parties agree. That combination is deliberate and it is what makes Estonia easy: one statutory default, no national CIUS, no local extensions.

Statutory defaultEN 16931, where the parties have not agreed otherwise. Estonia adds no national CIUS on top

SyntaxesBoth EN 16931 syntaxes — OASIS UBL 2.1 and UN/CEFACT Cross Industry Invoice

Over PeppolPeppol BIS Billing 3.0, which binds the EN 16931 model to UBL Invoice and Credit Note. CII is not an alternative syntax inside this profile

National XMLThe Estonian e-arve XML (EVS 923) is not prohibited and remains in use by agreement, though it is expected to give way to EN 16931 over time

Where the PDF sits

Two different questions get confused here. Under VAT law an invoice may be on paper or in electronic form with the recipient's acceptance — so a PDF can be a lawful electronic invoice. Under the Accounting Act an e-invoice is a document in a structured format allowing automatic processing — so a PDF is not a structured e-invoice.

Which means: a PDF is fine where no registered buyer has exercised its right; a PDF is not enough the moment one has. A PDF, an image or a spreadsheet does not become an e-invoice by being sent electronically.

The model

Estonia runs a decentralised, non-clearance model. Private operators exchange invoices among themselves through roaming arrangements and through Peppol. The state does not designate a single platform and does not mandate a particular service provider.

Operator to operator

Seller → seller's operator or Access Point → buyer's operator or Access Point → buyer. Peppol is an important interoperability rail within this, not the only one.

The tax authority is not in the flow

The Tax and Customs Board does not pre-validate invoices, does not assign an authorisation identifier and does not receive a copy at the moment of exchange.

What Estonia does not have

Centralised clearance in the manner of the Italian SdI

A five-corner model with the tax administration as a fifth corner

Real-time or invoice-by-invoice reporting

A national licensing regime for e-invoicing operators or Access Points

OpenPeppol is developing five-corner concepts at network level, but no Estonian decision to adopt a national C5 architecture has been published. Describing Estonia today as "a Peppol five-corner CTC country" would be inventing a system that does not exist.

Identifiers

Two schemes are active for Estonia, and an Access Point that supports only one of them will fail on real traffic.

0191Estonian company registry code, issued by the Centre of Registers and Information Systems. Eight digits, with defined format and check-digit rules. Written as 0191:

9931Estonian VAT number

Do not hard-code the assumption that an Estonian participant is addressable by VAT number. The registry code is the more universal identifier — every accounting entity has one, whether or not it is registered for VAT, and the buyer's-choice register keys off accounting entities rather than VAT payers.

Peppol in Estonia

Peppol is an important interoperability channel, not the sole national delivery network. Domestically, a network of private operators exchanges invoices through roaming arrangements as well as through Peppol; for cross-border traffic Peppol is the natural and strategically obvious rail.

No separate national Peppol Authority

No dedicated Estonian Peppol Authority appears on the OpenPeppol list, and Estonian certified providers are listed under OpenPeppol as their Peppol Authority. OpenPeppol performs the role in jurisdictions without a national one — so the Service Provider Agreement is with OpenPeppol, and there is no Estonian body to apply to.

KMD INF reporting

Estonia has invoice-level VAT reporting, but it is periodic and after the fact — it is not a continuous transaction control. The KMD INF annex accompanies the VAT return and lets the tax administration match what a seller declared against what the buyer claimed.

Tax periodCalendar month

DeadlineBy the 20th day of the month following the tax period, with the VAT return

Part A / Part BSales invoices and purchase invoices respectively

ThresholdInvoice data are declared where the total per transaction partner, excluding VAT, reaches €1,000 in the period

HowElectronically through the e-MTA portal — online entry, XML or CSV upload, or machine-to-machine through X-tee

Pre-filled returnsNot offered. The taxpayer still compiles and files its own return

Filing this electronically, even through an API, does not make it continuous transaction control. That distinction matters when comparing Estonia with clearance jurisdictions — and it is the reason the planned removal of the €1,000 threshold is a reporting change, not a change of model.

Penalties

No fixed statutory fine for breaching the e-invoicing rules was identified in the Accounting Act — there is no "€X for sending a PDF instead of an e-invoice". The EU country profile likewise records no dedicated monitoring mechanism for the e-invoicing regime. Figures circulating as "the Estonian e-invoicing penalty" are not traceable to a specific provision, and we would rather say so than publish one.

What the actual exposures are

—Breach of the buyer's right under the Accounting Act — a civil and commercial matter between the parties

—Breach of contractual or procurement terms requiring an e-invoice — rejection, delayed payment, breach of contract

—Breach of VAT invoicing content requirements — the ordinary VAT consequences

—Failure to submit returns or required data, or supplying false information — the general tax sanction regime under the Taxation Act, including sanctions for obstructing the tax authority

—Accounting record-keeping failures — general accounting law consequences

VAT deduction

A structured e-invoice is not the exclusive basis for deducting input VAT in Estonia. The ordinary basis is an invoice meeting the VAT Act requirements, received from the supplier — the tax authority's rules do not require it to be an EN 16931 document. In some reverse-charge situations, such as certain intra-Community acquisitions and acquisitions from a foreign business, other evidence such as a contract or delivery note can support the deduction. For import VAT the basis is the customs declaration.

So a PDF invoice can still support a deduction where the structured form was not required — even though that same PDF is not an e-invoice for the purposes of the Accounting Act.

Archiving

Accounting source documents — invoices among them — must be retained for seven years. Invoices issued and received are preserved in chronological order for seven years from the date of issue or receipt, and records may be kept electronically for the whole period provided they remain legible, tamper-evident and backed up.

The information on an invoice must be preserved in its original form — so an electronic invoice is retained electronically. Printing an XML and filing the paper does not discharge the obligation

Keep the XML, not only a rendered visualisation. The structured document is the invoice

Documents must be producible on request by the Tax and Customs Board throughout the period

Nothing is archived on your behalf. There is no clearance platform holding a copy, and an operator's retention service is a commercial arrangement rather than a statutory archive — worth confirming when a client changes provider.

ViDA and 2030

Directive (EU) 2025/516 was adopted on 11 March 2025, published in the Official Journal on 25 March 2025 and entered into force on 14 April 2025. From 1 July 2030 intra-EU B2B transactions come under digital reporting requirements based on mandatory structured e-invoicing and near-real-time reporting. By 1 January 2035 member states with pre-existing domestic transaction reporting must align it with the EU model.

Keep the two reforms apart. The Estonian 2027 proposal is a domestic plan requiring a VAT Act amendment that has not passed. ViDA is EU law already in force with fixed dates. They point in the same direction, but only one of them is certain.

Sensible architecture: build for EN 16931, keep Peppol capability live, support both Estonian identifier schemes, and design the reporting side so that removing a threshold is a configuration change rather than a rebuild. Do not hard-code an Estonia-specific five-corner tax model until the Ministry of Finance or the Tax and Customs Board publishes one.

Requirements for providers

Nothing beyond Peppol certification. No Estonian national accreditation or licensing scheme for e-invoicing providers or Access Points — no equivalent of the Slovak digitálny poštár — was identified in the current primary sources.

The government has stated expressly that a business may, but need not, use an e-invoicing operator located in Estonia

A Peppol Access Point certified in another EU country can onboard Estonian clients directly

No Estonian legal entity, branch, local office or local data centre is required as a condition of providing the service

No state-issued "official electronic mailbox" exists in the Estonian model — what matters is the buyer's registration in the Business Register

No local representative is required specifically for Access Point activity. General corporate, VAT, permanent establishment and GDPR rules of course still apply on their own terms

What does apply is the ordinary OpenPeppol layer: the Service Provider Agreement, certification, AS4 messaging, PKI and certificate security, the relevant BIS profiles, addressing and capability discovery, and SMP registration for receiving.

How we help

Estonia needs no licence and no local entity. It needs correct addressing, a real EN 16931 implementation, and a system that knows when the obligation switches on:

Peppol BIS Billing 3.0 and EN 16931 in both syntaxes — UBL 2.1 and UN/CEFACT CII

Addressing on both 0191 and 9931, so registry-code-only participants are reachable

Mapping from the legacy Estonian e-arve XML where a client's existing flows still use it

Capability lookup before sending, so you know whether a counterparty can actually receive

Delivery to Estonian public sector recipients without a local entity or accreditation

Structured invoice data clean enough to feed KMD INF, and resilient to the threshold being removed

PDF visualisation alongside the XML for partners who still work on paper

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Does Estonia have a B2B e-invoicing mandate?

A conditional one. Since 1 July 2025 an accounting entity registered in the Business Register as an e-invoice recipient can require a structured e-invoice, and the seller must comply unless the parties agreed otherwise. It is not a universal obligation to issue e-invoices to everyone. The EU country fiche marks the B2B mandate "yes" while explaining the buyer's choice mechanism — without that explanation the "yes" is misleading.

How do I know whether my Estonian customer can require an e-invoice?

Check whether it is publicly registered as an e-invoice recipient in the e-Business Register. That registration is what confers the right — not size, sector or turnover. Since the 2025 reform a company can register itself directly, rather than depending on its e-invoicing operator to do it, so the register is a more reliable signal than it used to be.

Is e-invoicing to the Estonian public sector still mandatory?

In substance yes, in construction no. The general obligation that applied from 2019 where the buyer was a public body was replaced on 1 July 2025 by the buyer's right to choose the invoice format. Because every public sector entity is among the registered e-invoice recipients, the practical regime continues unchanged — sellers issue e-invoices to them by default.

Will B2B e-invoicing become mandatory in 2027?

It is proposed, not enacted. The Ministry of Finance has put forward making e-invoicing obligatory for VAT-registered businesses and abolishing the €1,000 KMD INF threshold, with 2027 as the target. That requires an amendment to the VAT Act which has not been adopted, and the proposal is contested — the Chamber of Commerce and Industry has opposed both elements. Treat 2027 as a policy target with no confirmed statutory effective date.

Can I still send a PDF invoice in Estonia?

Where no registered buyer has exercised its right, yes — VAT law permits an electronic invoice with the recipient's acceptance, and a PDF qualifies as an electronic document. Where a registered buyer has required an e-invoice, no: a plain PDF is not a structured e-invoice under the Accounting Act, because it does not permit automatic processing. A PDF, image or spreadsheet does not become an e-invoice by being emailed.

Which identifier should I register for an Estonian participant?

Support both. EAS 0191 is the Estonian company registry code issued by the Centre of Registers and Information Systems — eight digits with defined format and check-digit rules. EAS 9931 is the Estonian VAT number. Do not build on the assumption that an Estonian participant is addressable only by VAT number; the registry code is the more universal one, since every accounting entity has one whether or not it is VAT-registered.

Can a German or other EU Peppol Access Point serve Estonian clients directly?

Yes. The government has stated expressly that a business may but need not use an operator located in Estonia, and Peppol's architecture lets sender and receiver choose their providers independently. No Estonian provider licence, mandatory local establishment, official mailbox or local representative for Access Point activity was identified. The Service Provider Agreement is with OpenPeppol, which acts as Peppol Authority for Estonia.

Does Estonia have real-time reporting or clearance?

No to both. Invoices are not sent to the Tax and Customs Board for approval, are not assigned an authorisation identifier and are not copied to it at the moment of exchange. Reporting is the monthly KMD INF annex, filed with the VAT return by the 20th of the following month, covering transactions where the total per partner reaches €1,000 excluding VAT. Filing it through an API does not make it continuous transaction control.

What is the penalty for not issuing an e-invoice when required?

No fixed statutory e-invoicing fine was identified in the Accounting Act, and the EU country profile records no dedicated monitoring mechanism for the regime. The real exposures depend on what was actually breached: the buyer's right is a matter between the parties; contractual or procurement terms carry contractual consequences; VAT invoicing errors carry ordinary VAT consequences; and failures to file returns or data, or supplying false information, fall under the general tax sanction regime. Quoting a single "Estonian e-invoicing penalty" figure would not be accurate.

How long must invoices be kept, and in what form?

Seven years. Invoices issued and received are preserved in chronological order for seven years from issue or receipt, and electronic retention is permitted throughout provided records stay legible, tamper-evident and backed up. Importantly the information must be preserved in its original form — so an electronic invoice is kept electronically, and printing the XML does not discharge the obligation. Keep the XML rather than only a rendered visualisation.

Summary

Estonia is best described as a decentralised, non-clearance country with a conditional e-invoicing obligation. Registered buyers can require structured e-invoices; EN 16931 is the default where nothing else was agreed; format freedom survives. The tax administration validates nothing in real time, designates no platform and licenses no providers.

The most useful correction to the common summaries is the direction of the duty. Since July 2025 the public-sector obligation from 2019 is not a duty on the seller at all — it is a right the buyer exercises, and it continues in practice only because every public body is registered.

Which makes the operational question refreshingly concrete: is this counterparty registered? Support both identifier schemes, implement EN 16931 properly, keep the XML for seven years — and build the reporting side so that when the €1,000 threshold goes, nothing has to be rewritten.

Resources

Ministry of Finance — the Accounting Act reform announcement The primary source for buyer's choice, self-registration and the replacement of the 2019 obligation by a right Riigikogu — Accounting Act amendment bill 428 SE The legislative file behind the reform that took effect on 1 July 2025 Ministry of Finance — source documents, invoices and e-invoices The policy page for accounting documents, where changes to the regime are published Estonian Tax and Customs Board — VAT accounting and invoices Invoice content, retention in original form, and the obligations of taxable persons Estonian Tax and Customs Board — filing VAT returns and reports Deadlines, the KMD INF annex, and the submission channels including X-tee European Commission — eInvoicing in Estonia The country profile, including the buyer's choice explanation behind the "B2B mandate: yes" marking Peppol BIS Billing 3.0 The UBL-based profile used for Estonian public sector and cross-border delivery Peppol Electronic Address Scheme code list Where 0191 for the registry code and 9931 for the VAT number sit OpenPeppol — Peppol Authorities Confirm that Estonia has no separate national authority and that OpenPeppol fills the role European Commission — VAT in the Digital Age (ViDA) The 2030 and 2035 obligations, which are the dates that are actually fixed Peppol Directory Check that an Estonian participant is reachable, and on which identifier scheme

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial