{"id":29260,"date":"2026-08-30T07:00:01","date_gmt":"2026-08-30T07:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/peppol-mandatory-estonia-invoicing\/"},"modified":"2026-08-30T07:00:01","modified_gmt":"2026-08-30T07:00:01","slug":"peppolin-pakollinen-viron-laskutus","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/peppolin-pakollinen-viron-laskutus\/","title":{"rendered":"Tarvitaanko Peppolia Viron julkisen sektorin laskuihin?"},"content":{"rendered":"
\n
\n
\n

No, Peppol isn’t a legal requirement for sending invoices to Estonian public-sector buyers. What’s mandatory is a structured e-invoice, a machine-readable invoice format that accounting and ERP systems can process without manual entry, when a registered buyer asks for one, and Peppol is just one technical channel for delivering it, not the only one. The amendment to the Estonian Accounting Act<\/a>, passed on 18 September 2024 and effective from 1 July 2025, scrapped the old rule that forced suppliers to send e-invoices to public bodies automatically, replacing it with a buyer’s right to request one instead. According to the Ministry of Finance<\/a>, every public-sector body is already registered as an e-invoice recipient, so in practice a structured e-invoice remains the default. But buyers can now grant exceptions and accept invoices in other formats too.<\/p>\n

What actually changed on 1 July 2025?<\/h2>\n

Estonia introduced a blanket e-invoice mandate for public-sector buyers back in 2019. Sellers had to send one no matter what. That mandate was replaced in 2025<\/a> with a “buyer decides” principle that now applies across the private sector as well: any accounting entity registered as an e-invoice recipient can require one from its suppliers. For public bodies, the practical outcome barely shifted, since they were already registered anyway. What did change is that they’re no longer barred from making exceptions and accepting invoices in other formats when it suits them.<\/p>\n

What’s the difference between Peppol, EN 16931 and Estonia’s own e-invoice format?<\/h2>\n

EN 16931 is the European e-invoice standard. It defines which data fields an invoice has to contain, not how the invoice actually gets delivered. Peppol, by contrast, is a network plus a set of technical specifications that move an invoice from a seller’s system into a buyer’s system through a certified gateway known as an Access Point. Peppol BIS Billing 3.0 is the invoice format built on top of that network, and it follows the EN 16931 requirements<\/a>. Estonia also has its own domestic e-invoice format, which was the common standard before EN 16931 took over. Estonian law treats an invoice as correctly issued<\/a> once it meets EN 16931, but the two parties are also free to agree on a different standard between themselves. None of this requires Peppol specifically.<\/p>\n

How do you find out whether a specific buyer needs Peppol?<\/h2>\n

Before you send an invoice, look up the buyer’s registry code and check which service provider or receiving channel<\/a> is listed against it in the Estonian Business Register. That tells you exactly where the invoice needs to land and in what format. It’s also worth asking the buyer directly for the contract reference, purchase order number and buyer-reference details. Many public bodies want these entered as separate fields on the invoice itself, regardless of which channel carries it.<\/p>\n

What do PDF invoices, ViDA and the deadlines actually require?<\/h2>\n

A plain PDF is not an e-invoice, because it isn’t machine-readable enough to process automatically<\/a>. A PDF can travel alongside a structured e-invoice as a courtesy copy, but it generally can’t replace one once a buyer has required it. The EU’s Directive 2014\/55\/EU<\/a> obliges public contracting authorities to accept invoices meeting EN 16931. It never names Peppol as a mandatory network. The VAT in the Digital Age package, known as ViDA, was adopted on 11 March 2025<\/a>, and its digital reporting obligation starts applying to cross-border B2B transactions, meaning invoices between businesses in different countries, from 1 July 2030. That has no effect on Estonia’s current business-to-government invoicing rules today. For companies already operating on the Peppol network, the newer BIS Billing 3.0 version becomes mandatory<\/a> from 17 August 2026, but that’s a technical version upgrade inside the network itself, not a new obligation created by Estonian law.<\/p>\n

FAQ<\/h2>\n

Kas Peppol on Eesti riigihankes kohustuslik?<\/h3>\n

Ei, Peppol ei ole kohustuslik. Kohustuslik on struktureeritud e-arve ostja n\u00f5udmisel \u2013 Peppol on vaid \u00fcks tehniline kanal selle kohaletoimetamiseks. Alates 1. juulist 2025 kehtib ostja valiku p\u00f5him\u00f5te.<\/p>\n

Mis muutus 1. juulil 2025?<\/h3>\n

Varasem \u00fcldine e-arve esitamise kohustus asendus ostja valib printsiibiga. Avaliku sektori ostjad on endiselt e-arve vastuv\u00f5tjana registreeritud, kuid n\u00fc\u00fcd v\u00f5ivad nad erandina muus vormingus arveid vastu v\u00f5tta.<\/p>\n

Mis vahe on Peppolil, EN 16931 ja Eesti e-arvel?<\/h3>\n

EN 16931 on Euroopa standard, mis m\u00e4\u00e4rab, milliseid andmeid arve peab sisaldama. Peppol on v\u00f5rgustik arve edastamiseks, Eesti e-arve on kohalik vorming. Seadus n\u00f5uab EN 16931 j\u00e4rgimist, kuid pooled v\u00f5ivad kokku leppida teises standardis.<\/p>\n