Estonia

Estonia is one of Europe's most digitalised economies, and e-invoicing is already established in the public sector. B2G e-invoicing has been mandatory since 1 July 2019. Since 1 July 2025, the Accounting Act has also supported a "buyer's choice" model for private-sector invoicing. Under this model, any business registered as an e-invoice recipient in the Commercial Register can require its suppliers to send structured e-invoices.

It is not a blanket B2B mandate, and conventional invoices remain valid when no such request exists. The Ministry of Finance has proposed wider mandatory B2B e-invoicing linked to VAT reporting changes, with 2027 discussed as a target. This has not been enacted, so businesses should treat it as a planning scenario rather than a legal obligation.

Suppliers to Estonian public-sector entities must issue e-invoices, and public bodies must be able to receive them. In the private sector, the obligation is conditional. A supplier must send an e-invoice when the buyer is registered as an e-invoice recipient in the Commercial Register and has requested it, unless the parties agree another standard. The right applies to private and public buyers alike.

Businesses that have not registered as recipients cannot be forced to receive e-invoices, and suppliers to such customers are not generally obliged to issue them. Companies selling to many Estonian customers should be ready to check each buyer's status and support structured invoicing on demand.

Where an e-invoice is required, it must be a structured, machine-processable invoice. Since July 2025, the Accounting Act supports the European standard EN 16931, which applies by default unless the parties agree another relevant standard. A PDF or scanned invoice does not meet this definition. Recipients register their e-invoice reception details in the Commercial Register, including the e-invoice handler or reception channel. Suppliers need to send invoices to that channel.

Businesses can now register to receive e-invoices directly, not only through an operator. The current rules do not require tax authority pre-approval of each invoice. Separately, VAT-registered businesses must include invoice-level data in VAT returns above the EUR 1,000 threshold. That is a reporting duty, not an e-invoicing obligation. ERP systems should therefore support both structured invoice output and VAT data extraction.

Estonia's Accounting Act recognises EN 16931 as the e-invoice standard, and the same regime applies to B2G and B2B invoices. Peppol BIS Billing 3.0 is a widely used syntax, and Estonia also has an established national e-invoice XML format aligned with the European standard.

Exchange is decentralised. Rather than sending invoices through a single government portal, suppliers use e-invoice operators, direct connections or Peppol access points to reach the recipient's registered channel. The Commercial Register holds the recipient's reception details, so senders can find where to deliver an invoice. There is no mandatory clearance platform. Any future VAT reporting changes would be a separate layer from invoice exchange.

HubBroker can help Estonian trading partners meet buyer requests without replacing their ERP. Our integration platform maps invoice data from your ERP into EN 16931-based structured formats, including Peppol BIS Billing 3.0, and delivers it through Peppol connectivity or other supported channels.

For inbound invoices, we route supplier e-invoices into your ERP and use Intelligent Document Processing to convert remaining PDFs into structured data. Because Estonian obligations depend on each buyer's registration, we can design workflows that handle structured and conventional invoices side by side. Any register-based routing would be scoped during implementation.