PEPPOL explained: what it is, how it works, and why your clients will ask about it
PEPPOL is the network EU e-invoices travel over. With ViDA making structured invoicing mandatory, understanding the network is becoming a practical necessity for accounting firms.
If your clients are asking about ViDA and the EU e-invoicing mandate, the next question is usually "so how does the invoice actually get there?" The answer is PEPPOL.
What PEPPOL is
PEPPOL (Pan-European Public Procurement On-Line) is a network and a set of standards that let businesses exchange electronic documents — invoices, orders, credit notes — through a common infrastructure. Think of it as a postal system for structured business documents, where every participant connects through an accredited access point rather than sending files directly to each other.
The network was originally built for government procurement (B2G), where it's already mandatory across much of the EU. ViDA extends the same infrastructure to intra-EU B2B transactions.
The four-corner model
PEPPOL uses what's called a four-corner model:
- Sender — your client's accounting system
- Sender's access point — an accredited PEPPOL provider that transmits on their behalf
- Receiver's access point — another accredited provider that receives on the other side
- Receiver — the buyer's accounting system
Your clients don't connect to PEPPOL directly. They connect to an access point provider (sometimes their accounting software vendor, sometimes a specialist), and that provider handles the network routing. The invoice travels from access point to access point using the AS4 transport protocol, then lands in the receiver's system.
What goes inside the envelope
The document format matters. PEPPOL carries invoices built to the EN 16931 semantic standard — the European standard for e-invoicing that ViDA makes mandatory. EN 16931 defines what data elements a compliant invoice must contain, in machine-readable form. A PDF image of an invoice does not meet this; the data has to be structured so a system can process it automatically.
The most common serialisations are UBL 2.1 and UN/CEFACT CII, both of which satisfy EN 16931. Your access point provider typically handles the conversion from whatever format your client's system produces.
Why this matters for firms now
National mandates are arriving before the 2030 EU-wide deadline. Germany's B2B e-invoicing requirement, France's phased rollout, Romania and Poland rolling out their own PEPPOL frameworks — firms with cross-border clients are effectively managing multiple PEPPOL deployments on different timelines.
The practical advice: don't wait for 2030 to understand what access point your clients are using (or need). The onboarding process for PEPPOL isn't instantaneous — getting registered, testing the connection, and confirming the invoice format is correct takes time. Firms that build this into their client onboarding now avoid a scramble later.
Greenstamp validates every invoice against the EN 16931 rules before it goes out over PEPPOL, so errors get caught before they reach the receiver's access point — where rejections are harder to fix quickly.
This post is general information, not tax or legal advice. Confirm specifics with your tax advisor and access point provider.