PDF or e-invoice in Estonia 2026: what can a buyer demand?

The short answer: only in one specific situation

A PDF attached to an email is not an e-invoice. According to the Ministry of Finance, an e-invoice is a machine-readable file built to a single standard, not a picture of an invoice. But there is no general ban on PDF invoices in Estonia in 2026, and other invoice formats remain perfectly legal. A buyer can require a machine-readable e-invoice from you in three cases:

• You agreed to it: the contract or the purchase order specifies the e-invoice form.
• The register says so: the buyer is listed in the e-business register as an e-invoice recipient — and then the Accounting Act gives that buyer the right to demand one.
• Public sector: every public sector entity is a registered e-invoice recipient.

If no other standard has been agreed, an e-invoice is presumed compliant when it conforms to the European standard EN 16931-1.

A PDF invoice is not the same thing as an e-invoice

What actually differs between the two files

This is where most of the confusion lies, because both are "electronic". A PDF is a human-readable document: your client enters the amount, the date and the IBAN code, but software still has to extract the data, or someone retypes it by hand. An e-invoice is a structured data file that travels from the seller's software into the buyer's software, so nobody has to key the invoice data in again.

Take a €1,200 service invoice to a client in Tallinn. As a PDF it's a fully valid invoice, as long as the required details are in order. As an e-invoice it's the same transaction expressed in machine-readable fields: seller, buyer's registry code, amount, VAT, due date. The content is identical; the form is not.

	PDF invoice by email	Machine-readable e-invoice
What is the file?	A document meant for human eyes	A data file built to a single standard
Is it a valid invoice?	Yes, if the required details and VAT rules are met	Yes
Does it satisfy a registered buyer's demand	Not on its own	Yes
Format	Free	Estonian e-invoice standard or the European standard (Peppol); in a dispute, EN 16931-1 conformity is presumed
Work on the buyer's side	Data has to be entered or digitized	Data lands in the software automatically
Public sector	An exception is possible if the authority agrees	Standard practice

The two formats Estonia allows

The Ministry of Finance names two formats in use in Estonia: the Estonian e-invoice standard and the later European standard, also known as the Peppol invoice. It recommends the European standard to businesses, because its reach keeps growing. Estonia follows the principle of format freedom: both standards are allowed.

When does a buyer actually have a legal right to demand an e-invoice?

The default rule: the parties agree

Section 7¹ of the Accounting Act starts from freedom. The format of a machine-processable source document, and the conditions for submitting it, are agreed between the transaction partners unless another law says otherwise. So by default the invoice form is a matter of agreement, not a state order.

The exception: a registered e-invoice recipient

Then comes the exception. If an accounting entity wants to receive only e-invoices, it passes that information to the business register, which lists it as an e-invoice recipient and adds the receiving channel or the operator's details (§ 7¹ (3)). It is precisely that registered buyer who, under § 7¹ (7), has the right to require an e-invoice from the seller in order to pay for the goods or service. The Ministry of Finance guidance states the practical consequence plainly: unless the parties have agreed otherwise, sellers must issue them an e-invoice, and there are roughly 18,000 registered companies in Estonia.

There are no thresholds here. Turnover, invoice value and headcount don't matter. The only thing that matters is whether the buyer is a registered e-invoice recipient. The changes took effect on 1 July 2025 and replaced the earlier blank e-invoicing obligation for the public sector with a buyer's-choice principle that now extends to the private sector too.

No separate fine for sending a PDF appears in the current sources. The practical risk is simpler and more painful: if the buyer is waiting for a machine-readable file, your invoice may sit unprocessed in their system and the payment runs late.

What a seller should check before hitting send

Three steps, a couple of minutes in total.

• Registration status: check whether the client's registry code is listed in the business register as an e-invoice recipient. The open data service has a dedicated e-invoice recipient lookup called arireg.earveRegistriParing_v1, in use since 01.05.2017, and you don't need to sign a contract to use it. You feed in registry codes and get back a status: OK means a valid link exists, MR means the code was not found or there is no active link.
• Channel and service provider: the same lookup also returns the service provider identifier, meaning the operator through which your client receives invoices. That tells you where to send the invoice.
• Contract and order: check whether you've already agreed a format. Agreement is the default rule in § 7¹, so a written agreement on a different format is a perfectly sound basis.

If there is no agreement and the client is a registered recipient, send an e-invoice. If no other standard has been chosen, the safe pick is a file that meets EN 16931-1 — that's exactly the conformity for which the law presumes the e-invoice is compliant.

PDF is allowed, but the rule on issuing invoices is a separate question

Keep three things apart: the content of the invoice, the VAT rules, and the invoice form. The VAT Act requires a taxable person to issue an invoice as a rule within seven calendar days of dispatching the goods or making them available, or of supplying the service. Under § 37 (6) of the same act, the invoice may be issued on paper or, with the buyer's consent, electronically.

That "electronically" does not automatically mean an e-invoice in the sense of the Accounting Act. A PDF can be a fully compliant invoice for VAT purposes and still fall short of a registered buyer's e-invoice requirement. Two sets of rules, two separate questions.

Public sector, exemptions, and what's still open to agreement

In 2019, Estonia introduced a general obligation to submit e-invoices whenever the buyer was a public sector body. In 2025 that obligation was replaced by the buyer's right to choose the invoice form. Since all public sector entities are already listed in the business register as e-invoice recipients, the regime for them continued essentially as before. But unlike before, they are no longer barred from making an exception and accepting an invoice in another form where needed. In short: send an e-invoice to a state authority, but the absolute "e-invoice only" prohibition is gone.

The Accounting Act also lists, in § 7¹ (8), the situations where the e-invoice recipient register and the right to demand do not apply: among others, documents submitted to a security authority, documents containing state secrets or classified foreign information, documents covered by professional or official secrecy, and cases where another law prescribes a different procedure.

What ViDA changes later, and what it still doesn't change in 2026

ViDA, the EU's “VAT in the Digital Age” package, is the single biggest source of timeline confusion. Council Directive (EU) 2025/516 was adopted on 11 March 2025 and published in the Official Journal of the European Union on 25 March 2025. It lets member states impose domestic mandatory e-invoicing under certain conditions, but the EU-wide digital reporting requirements only touch cross-border B2B transactions from 1 July 2030.

So ViDA creates no new invoice-form obligation for an Estonian company in 2026. And as of 21 September 2026, the verified sources contain no Estonian legal act imposing a general e-invoicing obligation on all domestic B2B transactions. The same logic still holds: the format is agreed between the parties, a registered buyer can demand an e-invoice, and everything else is between you and your client.

Also available in: in Estonian

Last reviewed: September 21, 2026

FAQ

Will sending PDF invoices be banned in Estonia in 2026?

There is no general ban on PDF invoices in Estonia in 2026, and the invoice format is a matter of default agreement between partners. The seller is only obliged to send an e-invoice if the buyer is entered in the commercial register as an e-invoice recipient or if the buyer is a public sector institution.

When does a buyer have the legal right to request an e-invoice from a seller?

According to the Accounting Act, the buyer can request an e-invoice if he is registered in the commercial register as an e-invoice recipient and the parties have not agreed otherwise in writing. In addition, the right to request applies if the provision of an e-invoice has been separately agreed in the contract or order terms.

How do I check if a customer accepts machine-readable e-invoices?

To check, you can use the free open data query of the commercial register arireg.earveRegistriParing_v1 or the e-commercial register information system. The query shows the current status based on the client's registry code and the e-invoice operator channel to which the invoice should be sent.