PEPPOL and public sector invoices: is it mandatory?

The short answer: an Estonian public-sector buyer expects a machine-readable e-invoice, but PEPPOL, the pan-European invoice delivery network, isn't itself a legal requirement. Since 01.07.2025 the Accounting Act follows a “buyer decides” rule: an accounting entity registered as an e-invoice recipient in the e-Business Register may require an e-invoice from the seller (§ 7¹ (7)), and an invoice meeting the European e-invoicing standard EN 16931-1 counts as compliant. The parties may agree on another relevant standard instead. The Ministry of Finance says every public-sector unit is registered in the business register as an e-invoice recipient, although a buyer can now grant exceptions. So emailing a PDF to a ministry, a city government or a university is not a safe default. PEPPOL is one common channel for delivering that invoice. It is not a rule of its own.

Why isn't an emailed PDF the safe default?

The Ministry of Finance puts it plainly: an e-invoice isn't a picture of an invoice, it's a machine-readable file built on a single standard that moves from the seller's software into the buyer's software with no manual typing in between. A PDF doesn't do that. Public-sector accounting is waiting for a structured file, and the PDF ends up beside it, there for a human to read.

Yes, since 2025 a public-sector buyer May make an exception. But that's their call, not yours. If the agreement really is PDF, get it somewhere you can point to, such as the contract or an email thread. Under § 7¹ (1) the format remains a matter for the parties to agree only where no other legal act says otherwise.

PEPPOL, EN 16931, e-invoice: what's what?

EN 16931 is the European e-invoicing standard: it defines which data fields an invoice carries and what each one means. PEPPOL (Pan-European Public Procurement Online) is the network and the technical agreement for moving that invoice from one operator to another. Between the two sits a specification: Peppol BIS Billing 3.0 is an implementation guide for EN 16931, a Core Invoice Usage Specification. An invoice that matches it therefore matches EN 16931 as well.

That's why people in Estonia say "Peppol invoice" when they mean an invoice in the European standard. The Ministry stresses at the same time that both the Estonian and the European e-invoice standard are allowed — the principle of format freedom applies.

Does the invoice amount change anything?

The register entry holds the e-invoice recipient and the identifier of its processor or other receiving-channel details (§ 7¹ (3)). Nothing in the reviewed provisions sets a money limit: no minimum invoice value, no turnover threshold, no procurement-contract threshold. A €120 invoice and a €120,000 invoice follow the same rule. So the thing to check is the buyer, not the total.

Some background. In 2019, Estonia introduced a general obligation to submit e-invoices to public-sector buyers; in 2025 that was replaced by the buyer's right to choose, and extended to the private sector too. On the EU side, Directive 2014/55/EU obliges public contracting authorities to accept e-invoices that comply with the European standard.

What to check before you send

• The legal buyer and its registry code: the invoice goes to the institution, not to a department or a project manager. You'll need the registry code for the next step.
• The registry entry: the e-Business Register e-invoice recipient query, available since 01.05.2017 and needing no contract, returns the registry code, the name, the service provider identifier and a status. "OK" means the link is live.
• References: contract number, procurement or purchase-order reference. None of the sources reviewed set a single nationwide mandatory reference field, so ask the buyer for these before your first invoice.
• The sending channel: your own accounting software or an e-invoice operator. The Ministry lists E-invoicing among Estonian operators. You don't need your own PEPPOL Access Point, which is the entry point that connects an operator to the network.

Example: a €1,200 invoice to three public-sector customers

Same training service, same €1,200, three buyers: a ministry, a rural municipality government and a university. All three are registered e-invoice recipients, but their service providers may well differ. You don't pick that. Your operator or your software routes the invoice into the channel shown in the register.

One nuance is worth keeping in mind. If the contract says you use the Estonian e-invoice standard, the invoice goes out in that format, because the agreement comes before PEPPOL. And if the query doesn't return status "OK" for that buyer, it isn't automatic permission to send a PDF. Ask the buyer which format they want and which channel it should arrive in.

What's already happened, and what's still coming?

Peppol BIS Billing version 3.0.21 was published on 20.05.2026 and is mandatory from 17.08.2026. Validation rules and code lists changed, but that's your operator's or your software's job, not yours. If you send invoices through a direct interface, ask the provider to confirm the version has been updated.

The next big marker is cross-border: Council Directive (EU) 2025/516 sets e-invoicing and digital reporting rules for intra-EU transactions from 01.07.2030.

There is no general B2B e-invoicing obligation in Estonian law. The "buyer decides" principle applies, and registering as a recipient is the company's own decision. If someone tries to sell you a solution on the grounds of an "obligation taking effect right now", ask them for the section number.

Also available in: in Estonian

Last reviewed: September 14, 2026

FAQ

Is the use of PEPPOL mandatory when submitting invoices to Estonian government agencies?

No, PEPPOL itself is not a direct legal requirement, but a technical delivery channel. According to the Accounting Act, the public sector must be provided with a machine-readable e-invoice that complies with the EN 16931 standard or the Estonian standard.

Can I send an invoice to a government agency as a PDF file by email?

By default, it is not allowed, because public sector institutions expect a machine-readable file and are registered as recipients of e-invoices. Sending a PDF invoice is legally permitted only if the buyer has made an exception and the parties have clearly agreed to it.

Does the monetary amount of the invoice affect the requirement to submit an e-invoice?

No, there are no minimum transaction amounts or procurement limits in the law. You need to check the buyer's status in the e-business register, not the invoice amount, because the rule applies equally to invoices of any size.