Short answer: you need Peppol when your users’ market requires it, or when their trading partners are reachable only there – and that is a per-country question, not an EU-wide one. Peppol itself is a governed network for exchanging structured business documents: certified Access Points deliver UBL documents (invoices, credit notes, orders) between parties addressed by Peppol IDs. Two things get mixed up constantly, and telling them apart answers most requirement questions: the format mandate (invoices must conform to the European standard EN 16931) and the channel mandate – invoices must travel over a specific network or system. A country can require the first without the second.
Where do the Baltics actually stand?
| Market | Format rule | Channel rule |
|---|---|---|
| Estonia | EN 16931 primary format since 1 July 2025; registered buyers may demand e-invoices | Channel-neutral – operators, Peppol, state e-arveldaja all valid |
| Latvia | Structured e-invoices (LVS EN 16931): B2G mandatory since 1 Jan 2026, B2B from 1 Jan 2028 | Channel by agreement (e-adrese, operators, Peppol) |
| Lithuania | EN 16931 for public-sector invoices | B2G via SABIS, which accepts Peppol as a submission path |
Elsewhere the spread is wider: some EU states have made Peppol itself the default B2B rail, others only mandate the format. The EU-level direction is set by ViDA, which makes structured e-invoices mandatory for cross-border B2B transactions in 2030 – it prescribes the standard, not the network, but Peppol is the transport most implementations are converging on.
When do you need Peppol regardless of mandates?
Three practical cases. Your users invoice public-sector buyers in a country whose platform ingests via Peppol (Lithuania’s SABIS is the Baltic example). Your users trade cross-border – Peppol is usually the one channel both sides’ providers share. Or a tender or enterprise customer simply lists “Peppol support” as a requirement, which happens increasingly often because it is the safest common denominator.
What does “supporting Peppol” mean for your code?
Less than the specification’s size suggests. You do not implement AS4 transport or join OpenPeppol: a certified Access Point does that, and your application talks to its API: produce EN 16931-conformant invoice data, address recipients by Peppol ID, handle validation errors and delivery callbacks. If your invoices already conform to the standard, adding Peppol delivery is an integration task measured in days, not a compliance project measured in quarters.
Is Peppol mandatory in the EU?
Not as a blanket rule. Countries mandate the EN 16931 format, a channel, or both — e.g. Latvia mandates structured e-invoices B2B from 2028 with channel by agreement, while Lithuania’s B2G system ingests via Peppol. Check per market.
What is the difference between EN 16931 and Peppol?
EN 16931 is the European invoice-content standard; Peppol is a delivery network whose BIS Billing 3.0 profile implements that standard. A format mandate does not automatically mean a network mandate.
When does ViDA make e-invoicing mandatory?
The EU ViDA reform makes structured e-invoices mandatory for cross-border B2B transactions in 2030. It prescribes the standard, not a specific network.
Do I have to join OpenPeppol to support Peppol?
No. Certified Access Points hold the accreditation. Your application integrates with an Access Point’s API and works with EN 16931 data.