What Is a Peppol Access Point, and Do You Need One?

Most companies don’t need to build their own Peppol access point. To send and receive e-invoices on the Peppol network, a connection through a certified service provider or your accounting software is enough. And Peppol isn’t mandatory everywhere — it’s one possible route for delivering e-invoices, not the only one. In Estonia, a buyer’s right to demand an e-invoice has applied since 1 July 2025; Latvia is in a 2025–2028 transition; Lithuania’s public-procurement invoicing system supports Peppol; and cross-border B2B e-invoicing becomes the EU default only from 1 July 2030.

Two things get mixed up constantly, so let me separate them below: the network an invoice travels through, and the content of the invoice itself — its format. And a second confusion: „owning an access point” and „using an access point” are not the same thing.

The short answer: you need access, not a badge

In OpenPeppol’s terms, an access point is a certified service provider that is connected to other such providers and delivers invoices across the Peppol network through them. Under the Peppol interoperability framework, a provider may only offer Peppol services once it has signed a Peppol Service Provider agreement with a Peppol Authority and passed conformance testing — the checks that confirm its software behaves the way the network requires. That’s exactly why an ordinary company doesn’t build an access point itself. It’s a legal and technical role, not a switch the invoice sender flips on.

Think of it like a mobile network. To make a call, you don’t become a telecoms operator — you buy service from one. Peppol works the same way: the access point is the operator, and you’re the end user. The framework’s „connect once, reach everyone” logic means precisely that — one connection to one provider takes you to every recipient on the network.

There is no turnover threshold that would force an invoice sender to become an access point; the Peppol rules contain nothing of the sort. The practical trigger isn’t company size. It’s three other things: who the invoice recipient is, which national law applies, and which platform your partner uses.

Where does the access point sit on the invoice’s journey?

The Peppol network runs on a four-corner model. The four corners are simply four participants on one journey:

• C1 is the sender — the seller who creates the invoice in their own software;
• C2 is the sender’s access point, which delivers the invoice into the network;
• C3 is the recipient’s access point, which receives the invoice;
• C4 is the recipient — the buyer, in whose accounting system the invoice lands.

You and your partner are C1 and C4. The access points are C2 and C3 — two operators in the middle. According to the Peppol framework, the sender’s access point must validate every outgoing invoice before sending, so it meets the Peppol BIS requirements. That check happens in the background. You never see it, but it’s what stops broken invoices from going out.

How does the access point know where to send the invoice?

There’s a central address book for that. The same framework describes two components: the SML (Service Metadata Locator), a central register that says which SMP to contact, and the SMP (Service Metadata Publisher), which shows a specific recipient’s address and the document types they’re able to accept. In practice this comes down to one thing: to send an e-invoice to a foreign partner, you need to know their Peppol ID — the system handles the rest.

Peppol is a route, not an invoice

This is where the most confusion creeps in, so let it be plain: Peppol is the network the invoice travels through. It is not an invoice format. Format is a separate story, and three terms tangle together here.

What is EN 16931?

EN 16931 is the European semantic standard for e-invoices — a shared „dictionary” that defines which data fields an e-invoice must contain and what they mean. The standard came out of Directive 2014/55/EU, and according to the European Commission’s compliance roadmap, the EU’s central contracting authorities had to accept e-invoices conforming to EN 16931 from 18 April 2019. Sub-central contracting authorities got an optional extension until 18 April 2020.

What is Peppol BIS Billing 3.0?

Peppol BIS Billing 3.0 is one specific implementation of that standard — an agreed way of writing EN 16931 data into an actual file. The Peppol framework specifies that Peppol BIS builds on the UBL (Universal Business Language, ISO/IEC 19845) standards. UBL XML is the machine-readable file format the invoice data moves in. It’s structured text that software reads automatically — not something meant for the human eye.

Is a PDF invoice an e-invoice?

And then there’s the PDF. A PDF invoice, however neat and correct, is a picture for a person to read. It is not a structured e-invoice, even when you send it by email. A machine can’t pull the data out of a PDF without separate digitizing. A PDF attached to an email is not a Peppol e-invoice. In the Baltic rules, that difference is now legal, not cosmetic.

What changed in Estonia on 1 July 2025?

The amendment to Estonia’s Accounting Act took effect on 1 July 2025. The substance fits in one sentence: § 7¹ subsection 7 gives an accounting entity that is recorded in the commercial register as an e-invoice recipient the right to require an e-invoice from the seller. So if your buyer has registered as an e-invoice recipient, they can demand an e-invoice — and you have to provide one.

Note what this does not say. It does not make Peppol mandatory in Estonia, nor the only route. Estonia’s e-invoice market is distributed: an invoice can travel through several operators, and Peppol is one of them. The obligation is to hand over a structured e-invoice when an entitled buyer asks; which network you use for that is a separate technical choice. Peppol is a good choice for cross-border sending, and for when a partner specifically asks for it.

Latvia and Lithuania: the neighbours don’t share one rulebook

Here many people wrongly assume the three Baltic states run on one model. They don’t.

What are Latvia’s deadlines?

Latvia’s transition runs by fixed dates. According to the Latvian tax authority VID, structured e-invoices have been mandatory between the public sector and companies registered in Latvia — the G2G, B2G and G2B segments — since 1 January 2025. From 1 January 2026, reporting the e-invoice data to VID also becomes mandatory in those segments. And from 1 January 2028, the obligation extends to B2B: companies registered in Latvia must issue e-invoices in their mutual transactions and report them to VID. Between 1 January 2026 and 31 December 2027, B2B reporting to VID is voluntary.

On format, Latvia is clear: a structured e-invoice is XML that follows Latvia’s national standard and must conform to the Peppol BIS Billing 3.0 specification, based on EN 16931. The reporting deadline is fixed too: the e-invoice must be submitted to VID once, within five working days of the sending date at the latest, under Cabinet of Ministers Regulation No. 749 of 9 December 2025.

How does Lithuania’s SABIS work?

Lithuania uses SABIS, the public-procurement invoicing system. According to the SABIS FAQ, invoice data can be submitted to the system three ways: through the SABIS portal (data entered manually or imported as XML), through a universal interface from your business software, or through the Peppol network if the organisation is a member of it. Foreign suppliers who can’t access the SABIS portal directly can submit invoices precisely via Peppol, choosing an access point that suits them. The supported formats are Peppol BIS Billing 3.0 eInvoice and Peppol BIS Billing 3.0 Credit Note.

Three countries, three different patterns. In Estonia the obligation is triggered by the buyer’s choice; in Latvia by calendar-fixed stages with VID reporting; in Lithuania by several routes into one central system. If you trade across borders, you can’t carry one country’s logic over to the next.

How do you pick the right route?

Before you start choosing an operator or an access point, answer one question: who are you sending invoices to?

If you sell only to a single country’s public sector, a national portal may be enough. In Latvia, EDS clients with an official e-address can receive VID documents through both EDS and the official e-address; in Lithuania that’s the SABIS portal. For a small invoice volume, this is the cheapest route, with no separate operator.

If you send and receive invoices regularly, accounting software integrated with an e-invoice operator makes more sense. Then invoices move straight into your system and back out, with no retyping by hand.

If you do cross-border business, or your buyer requires Peppol, you need a Peppol service provider — a certified access point as a service, not your own access point. One connection takes you to every partner on the Peppol network.

What should you ask a service provider?

When choosing a provider, four things are worth checking. First, whether the solution covers both sending and receiving — some cover only one direction. Second, how identifiers are managed — the Peppol IDs by which you and your partners are found on the network. Third, whether outgoing invoices are validated before sending, as the Peppol rules require, because a broken invoice that bounces back costs time. And fourth, what it costs: whether the fee is per month, per invoice or per volume, and what’s included in the price.

Claims worth treating with caution

Three misconceptions spread especially easily.

Is Peppol mandatory for everyone in the EU?

No. Cross-border B2B e-invoicing becomes the EU default only from 1 July 2030, when — according to the Commission’s ViDA work programme — new Digital Reporting Requirements based on mandatory e-invoicing start to apply to cross-border B2B transactions. The ViDA package was adopted in March 2025 and enters into force in stages up to 2035. Countries that already run domestic real-time reporting must align their systems with the EU model by 1 January 2035 at the latest. That’s the future, not a universal obligation today. And even in 2030, we’re talking about a route — not about everyone having to become an access point.

To send e-invoices, do I have to become an access point myself?

No. As said above, the Peppol framework requires an access point to hold a separate agreement and pass conformance testing — that’s the operator’s role. An ordinary invoice sender buys the service; they don’t build the network.

Is Peppol a tax-reporting platform?

No. Peppol delivers invoices; tax-authority reporting is a separate obligation. Latvia’s case makes the difference visible: the Peppol network gets the e-invoice where it’s going, but reporting the data to VID within five working days is a step of its own, with its own rules. The two can meet in the same flow, but they aren’t one and the same.

So before anyone sells you „your own Peppol access point”, it’s worth asking what you actually need. Usually the answer is simple: a connection, not a network of your own. And the right route depends on who the invoices go to — Estonia’s buyer’s choice, Latvia’s calendar, or Lithuania’s SABIS.