{"id":29397,"date":"2026-09-15T07:00:08","date_gmt":"2026-09-15T07:00:08","guid":{"rendered":"https:\/\/bilnex.io\/en\/peppol-public-sector-invoice\/"},"modified":"2026-09-15T07:00:17","modified_gmt":"2026-09-15T07:00:17","slug":"peppolin-julkisen-sektorin-lasku","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/peppolin-julkisen-sektorin-lasku\/","title":{"rendered":"PEPPOL ja julkisen sektorin laskut: onko se pakollinen?"},"content":{"rendered":"
\n
\n
\n

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<\/a> (\u00a7 7\u00b9 (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<\/a>, 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.<\/p>\n

\n

Key facts<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nValid from<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
Buyer’s right to require an e-invoice<\/td>\nAn accounting entity registered as an e-invoice recipient in the e-Business Register may require an e-invoice from the seller (Accounting Act \u00a7 7\u00b9 (7))<\/td>\napplies from 01.07.2025<\/td>\nriigiteataja.ee<\/a><\/td>\n<\/tr>\n
Compliant format<\/td>\nAn invoice meeting the EN 16931-1 standard counts as compliant; the parties may agree on another relevant standard<\/td>\napplies from 01.07.2025<\/td>\nriigiteataja.ee<\/a><\/td>\n<\/tr>\n
Public sector in the register<\/td>\nEvery public-sector unit is registered in the business register as an e-invoice recipient; the 2019 obligation was replaced in 2025 by the “buyer decides” principle<\/td>\npage updated 12.01.2026<\/td>\nfin.ee<\/a><\/td>\n<\/tr>\n
Checking the recipient<\/td>\nThe e-Business Register’s e-invoice recipient query (arireg.earveRegistriParing_v1) returns the registry code, service provider and status; no contract needed<\/td>\navailable since 01.05.2017<\/td>\navaandmed.ariregister.rik.ee<\/a><\/td>\n<\/tr>\n
Peppol BIS Billing 3.0.21<\/td>\nPublished 20.05.2026, mandatory to use from 17.08.2026<\/td>\n17.08.2026<\/td>\ndocs.peppol.eu<\/a><\/td>\n<\/tr>\n
EU cross-border digital reporting<\/td>\nCouncil Directive (EU) 2025\/516 sets e-invoicing and digital reporting rules for cross-border transactions from 01.07.2030<\/td>\n01.07.2030<\/td>\neur-lex.europa.eu<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Why isn’t an emailed PDF the safe default?<\/h2>\n

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.<\/p>\n

Yes, since 2025 a public-sector buyer may<\/strong> 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 \u00a7 7\u00b9 (1) the format stays a matter for the parties to agree only where no other legal act says otherwise.<\/p>\n

PEPPOL, EN 16931, e-invoice: what’s what?<\/h2>\n

EN 16931<\/strong> is the European e-invoicing standard: it defines which data fields an invoice carries and what each one means. PEPPOL<\/strong> (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<\/a>. An invoice that matches it therefore matches EN 16931 as well.<\/p>\n

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 \u2014 the principle of format freedom applies.<\/p>\n

Does the invoice amount change anything?<\/h2>\n

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

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<\/a>.<\/p>\n

What to check before you send<\/h2>\n