{"id":29570,"date":"2026-09-25T07:00:01","date_gmt":"2026-09-25T07:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/peppol-vs-accounting-software\/"},"modified":"2026-09-25T07:00:08","modified_gmt":"2026-09-25T07:00:08","slug":"peppol-vs-accounting-software","status":"publish","type":"page","link":"https:\/\/bilnex.io\/en\/peppol-vs-accounting-software\/","title":{"rendered":"Peppol vs accounting software: what do you actually need?"},"content":{"rendered":"
\n
\n
\n

The short answer: software is your workspace, Peppol is the channel<\/h2>\n

Peppol doesn’t replace accounting software. The two solve different problems. Your accounting software is the workspace: it’s where you create a sales invoice, approve a purchase invoice, keep the books and store the documents. Peppol is a network with a shared set of document specifications, not a program you install. OpenPeppol says it plainly: the network is made up of certified service providers, and an end user sends and receives documents through their own service provider<\/a>. So the content of the invoice is created in the software, and the channel moves it to the buyer. Most Estonian small companies need both. But they only need a Peppol connection once a buyer or a foreign client asks for that specific route. Since 1 July 2025, an accounting-obligated entity registered in the Estonian Business Register as an e-invoice recipient may demand an e-invoice from the seller<\/a>.<\/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 demand an e-invoice<\/td>\nAn accounting-obligated entity registered in the Estonian Business Register as an e-invoice recipient may require an e-invoice from the seller; an invoice conforming to EN 16931-1 is deemed compliant,<\/td>\n1 July 2025<\/td>\nriigiteataja.ee<\/a><\/td>\n<\/tr>\n
E-invoicing obligation in public-sector transactions<\/td>\nMandatory in all B2G transactions; all public-sector bodies are registered as e-invoice recipients<\/td>\n1 July 2019<\/td>\nec.europa.eu<\/a><\/td>\n<\/tr>\n
A PDF or image file is not an e-invoice<\/td>\nUnder the Directive guidance, a mere image file does not count as an electronic invoice; an e-invoice must be machine-readable and capable of automatic processing<\/td>\nas at 09.2026<\/td>\nec.europa.eu<\/a><\/td>\n<\/tr>\n
Estonian VAT return annex (KMD INF) reporting threshold<\/td>\nEUR 1,000 per invoice excluding VAT, for invoices issued to legal persons, sole proprietors and state, rural municipality or city institutions<\/td>\nas at 09.2026<\/td>\nemta.ee<\/a><\/td>\n<\/tr>\n
Member states’ right to impose domestic e-invoicing mandates<\/td>\nDirective (EU) 2025\/516 allows member states to make e-invoicing mandatory on their own terms<\/td>\n14 April 2025<\/td>\neur-lex.europa.eu<\/a><\/td>\n<\/tr>\n
ViDA cross-border digital reporting<\/td>\nDigital reporting of cross-border B2B transactions is based on e-invoices; the invoice must be issued within 10 days of the chargeable event<\/td>\n1 July 2030<\/td>\neur-lex.europa.eu<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Three layers that keep getting mixed up<\/h2>\n

Before you decide anything, pull three things apart: the format<\/strong>, the channel<\/strong> and the software<\/strong>.<\/p>\n

Format: what shape the data is in<\/h3>\n

A PDF invoice is a document a human can read, not a machine-readable data file. Under the guidance on the eInvoicing Directive, a mere image file is not considered an electronic invoice<\/a>. A structured e-invoice is a machine-readable file where every required field (invoice number, VAT rate, reference number, IBAN) sits in its own defined place. The European standard EN 16931 sets out that data model and the permitted syntaxes. Peppol BIS is a tighter specification used inside the Peppol network on top of it; it is based on UBL (ISO\/IEC 19845)<\/a>, a common XML invoice language, and the sender’s Access Point, which is the certified entry point into the network, checks conformance before the file goes out.<\/p>\n

Channel: how the file travels<\/h3>\n

The channel is how the file actually reaches the buyer: an operator (an e-invoice service provider), the Peppol network, a direct interface, or simply an agreed file exchange between two systems.<\/p>\n

Machine-readable doesn’t mean automatic<\/h3>\n

One misunderstanding is worth correcting right away. A machine-readable invoice can<\/em> land in the buyer’s system without anyone retyping it, but that doesn’t mean the accounting entries appear by themselves. The standard says nothing about how an invoice is processed, so the level of automation is the receiver’s own decision<\/a>, made in their software and their workflow.<\/p>\n\n\n\n\n\n\n\n\n
What it is<\/th>\nMachine-readable?<\/th>\nWorks for a registered buyer?<\/th>\nHow it gets there<\/th>\n<\/tr>\n<\/thead>\n
PDF invoice attached to an email<\/td>\nNo, essentially an image<\/td>\nNo, unless agreed otherwise<\/td>\nEmail<\/td>\n<\/tr>\n
E-invoice conforming to EN 16931<\/td>\nYes<\/td>\nYes, presumed compliant<\/td>\nOperator, Peppol, direct interface or an agreed channel<\/td>\n<\/tr>\n
Peppol BIS Billing invoice<\/td>\nYes, UBL-based<\/td>\nYes<\/td>\nOnly through the Peppol network, via a service provider<\/td>\n<\/tr>\n
Accounting software<\/td>\nNot a format<\/td>\nNot a format, it’s the tool<\/td>\nDoesn’t deliver anything on its own without a channel<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Which setup fits your company?<\/h2>\n

If you’re a one-person business sending a handful of invoices a month, start by checking the Business Register to see whether your buyer is registered as an e-invoice recipient. If they are, you need a structured invoice. You don’t have to buy a big integration for that. The Centre of Registers and Information Systems (RIK) offers a free tool for issuing e-invoices<\/a>.<\/p>\n

In a company that already has an accountant, the question isn’t “Peppol or not”. It’s “what can the software we’re paying for already do?”. Plenty of accounting and business software sends e-invoices through an operator, and Peppol is simply one of the routes that operator opens on your behalf.<\/p>\n

If you receive a lot of purchase invoices, receiving matters more than sending. Ask whether your solution accepts e-invoices from sellers who use a different<\/em> operator. The Estonian model is decentralised: public bodies and companies receive invoices through various service providers, and interoperability is ensured through roaming agreements and Peppol connectivity<\/a>.<\/p>\n

If you sell to the public sector or abroad, a provider with a Peppol connection is the most direct choice, because the same channel covers both Estonian state agencies and cross-border clients.<\/p>\n

In Estonia this is a buyer’s right, not a Peppol obligation<\/h2>\n

The logic of \u00a7 7\u00b9 of the Accounting Act is straightforward: the format and the conditions for submitting a machine-processable source document are something the parties to the transaction agree between themselves<\/a>, unless the law provides otherwise. The registration is the exception. If the buyer is listed in the Business Register as an e-invoice recipient, they may demand an e-invoice, and an invoice conforming to EN 16931-1 is deemed compliant. The parties can also agree on another suitable standard, and the domestic XML standard long used in Estonia remains permitted by agreement.<\/p>\n

In the public sector the obligation has been in force much longer: in B2G transactions since 1 July 2019<\/a>. And because every public-sector body is registered as an e-invoice recipient, the new buyer’s-choice principle covers them too. There is no e-invoicing obligation towards private individuals.<\/p>\n

What the law does not say<\/h3>\n

Three things. It names no mandatory network and no mandatory operator: Peppol is one route, operator roaming is another, a direct agreement is a third. It doesn’t turn a PDF into an e-invoice, not even when an XML file rides along in the attachment purely as a copy. And the primary sources set out no general fine for ignoring an e-invoice request. The practical consequence is that the buyer can ask you to reissue the invoice in the correct format.<\/p>\n

What may change next<\/h3>\n

What comes next in Estonia is still open. According to the European Commission’s country overview, the Ministry of Finance is considering amendments to the VAT Act that would make e-invoicing mandatory in all B2B transactions between VAT-registered businesses and remove the EUR 1,000 reporting threshold. That’s an intention, not a rule in force. For now the existing regime applies: the VAT return annex (KMD INF, the transaction-level appendix to the Estonian VAT return) must list invoices exceeding EUR 1,000<\/a> excluding VAT, and Estonia has no real-time reporting.<\/p>\n

Latvia and cross-border trade: the dates that shape the decision<\/h2>\n

If you have clients or suppliers in Latvia, the calendar is far more specific. According to Latvia’s Ministry of Finance, structured e-invoices are required in G2G, B2G and G2B transactions involving budget institutions from 1 January 2025, and those invoices must also be submitted to the tax authority (VID) from 1 January 2026. The domestic B2B obligation, together with submission to VID, starts on 1 January 2028. The original deadline was 1 January 2026, but amendments adopted on 5 June 2025 pushed it back to give smaller companies more time. During 2026\u20132027 data can be submitted to VID voluntarily.<\/p>\n

At EU level the rules come from the ViDA package, namely Directive (EU) 2025\/516<\/a>, adopted on 11 March 2025 and published in the Official Journal of the European Union on 25 March 2025. From 14 April 2025, member states may impose mandatory domestic e-invoicing on their own terms. Digital reporting of cross-border B2B transactions, built on e-invoices, applies from 1 July 2030, and for those transactions the directive requires the invoice to be issued within 10 days.<\/p>\n

One common misreading: ViDA does not make Peppol mandatory. The directive requires the European standard to be used in the cross-border reporting flow it covers, but it names no particular transport network. Peppol is simply the most widely used way of meeting that requirement.<\/p>\n

Five questions for your accountant or software provider<\/h2>\n