Do You Actually Need a Peppol Service Provider?

A Peppol service provider — also called an Access Point — is a certified company that connects your accounting or ERP software to the Peppol network, checks every outgoing invoice against the Peppol BIS format (Peppol’s business document interoperability specification) before it leaves, and delivers it securely to the recipient’s Access Point. The answer to “do I need one” is straightforward: you need a Peppol service provider only if the invoice route required by your customer, a public-sector platform, or the law is specifically Peppol. In every other case, a different e-invoicing channel does the job just fine. Most buyers and sellers are simply end users on the Peppol network, not operators, and end users carry no obligation to join OpenPeppol as members themselves. Estonia, Latvia and Lithuania each run their own rulebook here, which gives you three different answers. There isn’t one universal yes or no.

What an Access Point Actually Does

Peppol runs on a four-corner model: an invoice moves from the sender’s software to the sender’s Access Point, through the network’s address directory, to the recipient’s Access Point, and finally into the recipient’s own accounting system. Before anything is sent, the Access Point checks that the invoice matches the Peppol BIS specification. Becoming a provider yourself means signing a Peppol service provider agreement and passing conformance testing first. That obligation sits with the operators, not with your business as an invoice sender or receiver.

When You Actually Need Peppol — and When Another Channel Works

You only need a service provider contract if you decide to become an Access Point yourself. In practice, it’s usually enough that the provider behind your accounting software already runs a certified Access Point on your behalf. Whether Peppol is required at all comes down to what your specific customer, public-sector platform, or local law demands, and those demands differ substantially between Estonia, Latvia and Lithuania.

Estonia: Being a Registered E-Invoice Recipient Doesn’t Automatically Mean Peppol

An amendment to the Accounting Act in force since 1 July 2025 lets any company listed in the Business Register as an e-invoice recipient demand e-invoices from its suppliers. The law doesn’t say this has to travel over Peppol specifically. An e-invoice counts as compliant if it follows the EN 16931-1 standard, but the parties can also agree on a different suitable standard between themselves. The Business Register entry can point to a receiving channel other than Peppol, so being registered as a recipient signals an e-invoicing obligation, not a mandate to use the Peppol network specifically.

Latvia: A 2026 Reporting Duty, a 2028 B2B Mandate

In Latvia, structured e-invoices have been mandatory for G2G, B2G and G2B transactions since 1 January 2025. Starting 1 January 2026, those same transactions also need their invoice data reported to the State Revenue Service (Valsts ieņēmumu dienests, VID) within five working days of the invoice being sent. A separate B2B mandate between companies only takes effect on 1 January 2028; until then, submitting B2B data is voluntary.

And Peppol isn’t the only accepted route here. VID accepts invoice data from:

• the e-address service
• e-invoice service providers
• taxpayers themselves, including via API

Lithuania: SABIS Lets You Choose Peppol, a Universal Interface, or Manual Entry

Suppliers invoicing Lithuanian public-sector buyers have to go through the SABIS system, but SABIS doesn’t force a Peppol-only route. Three paths are supported:

• Peppol
• SABIS’s own universal data interface
• manual entry

All three carry the same requirement — the invoice format must comply with EN 16931-1:2017. If you already have a Peppol connection set up for another market, reusing it for SABIS is usually the path of least resistance. But the law itself doesn’t narrow your choice down to that.

ViDA and Peppol: Is a Mandate Coming?

The EU has adopted the VAT in the Digital Age directive, known as ViDA, but the directive text doesn’t name the Peppol network as a mandatory transmission channel. The requirement targets structured e-invoices in the EN 16931 format, not a specific network. How each member state implements this, and on what exact timeline, depends on national transposition. That part is still open.