Peppol vs accounting software: what do you actually need?

The short answer: software is your workspace, Peppol is the channel

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. 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.

Three layers that keep getting mixed up

Before you decide anything, pull three things apart: the format, the channel and the software.

Format: what shape the data is in

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 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 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.

Channel: how the file travels

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.

Machine-readable doesn’t mean automatic

One misunderstanding is worth correcting right away. A machine-readable invoice can 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, made in their software and their workflow.

What it is	Machine-readable?	Works for a registered buyer?	How it gets there
PDF invoice attached to an email	No, essentially an image	No, unless agreed otherwise	Email
E-invoice conforming to EN 16931	Yes	Yes, presumed compliant	Operator, Peppol, direct interface or an agreed channel
Peppol BIS Billing invoice	Yes, UBL-based	Yes	Only through the Peppol network, via a service provider
Accounting software	Not a format	Not a format, it’s the tool	Doesn’t deliver anything on its own without a channel

Which setup fits your company?

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.

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.

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 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.

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.

In Estonia this is a buyer’s right, not a Peppol obligation

The logic of § 7¹ 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, 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.

In the public sector the obligation has been in force much longer: in B2G transactions since 1 July 2019. 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.

What the law does not say

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.

What may change next

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 excluding VAT, and Estonia has no real-time reporting.

Latvia and cross-border trade: the dates that shape the decision

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–2027 data can be submitted to VID voluntarily.

At EU level the rules come from the ViDA package, namely Directive (EU) 2025/516, 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.

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.

Five questions for your accountant or software provider

• Format: which syntax does the solution issue, an e-invoice conforming to EN 16931, Peppol BIS Billing, or the Estonian XML? And which version of Peppol BIS Billing does the provider support right now?
• Sending and receiving: are both directions covered, or only sending? For a company with a lot of purchase invoices, receiving is the more important half.
• Peppol connection: is the provider a certified Peppol service provider itself, or does it resell someone else’s connection? A certified provider may only offer the service once it has signed the service provider agreement and passed conformance testing.
• Address and registration: will your company get an address in the Peppol network, and will you be marked in the Business Register as an e-invoice recipient? On the buyer’s side, that entry is exactly what decides whether they may demand an e-invoice from you.
• Proof and archive: can you see that an invoice was delivered, and can you export the files with their attachments later? Ask too whether sending, receiving, the Peppol channel and the archive are priced separately. On a price list they’re often four different lines.

If the answer to any of these is “we’ll look into that”, ask for it in writing. Format and channel are the two places where things actually break, not the features of the software itself.

Also available in: eesti keeles · latviski · lietuviškai

Last reviewed: 22 September 2026

FAQ

Kas Peppol asendab raamatupidamistarkvara?

Ei asenda, sest need lahendavad erinevaid ülesandeid. Raamatupidamistarkvara on töölaud arvete koostamiseks ja finantsarvestuseks, samas kui Peppol on standardiseeritud võrk ja edastuskanal dokumentide vahetamiseks.

Millal peab Eesti ettevõte saatma masinloetava e-arve?

Alates 01.07.2025 võib äriregistrisse e-arve vastuvõtjaks märgitud ostja nõuda müüjalt struktureeritud e-arvet vastavalt standardile EN 16931. Avalikule sektorile (B2G) on e-arve esitamine kohustuslik juba alates 01.07.2019.

Kas EL-i ViDA direktiiv muudab Peppoli kasutamise kohustuslikuks?

Ei, direktiiv (EL) 2025/516 nõuab Euroopa standardile EN 16931 vastavat e-arveldamist piiriüleses aruandluses alates 01.07.2030, kuid ei määra kindlat võrku. Peppol on vaid üks levinumaid ja mugavamaid transpordikanaleid selle nõude täitmiseks.