Peppol gets described as "an e-invoicing standard", which is close enough to be useful and wrong in a way that causes real confusion. It is three things at once, and most misunderstandings come from collapsing them into one.
First, what counts as an e-invoice
Not a PDF. This is worth being blunt about, because a great many organisations believe they have already solved e-invoicing by emailing PDFs.
A PDF is a picture of an invoice. Somebody at the other end still opens it, reads it and enters the data into a system — which is precisely the manual work, and the cost, that the exercise was meant to remove. Automated capture helps, and it is still reading an image and guessing.
An e-invoice is the automated exchange of invoice data directly between a supplier's system and a buyer's, with no manual entry or re-keying at either end. The machine-readable data is the invoice, rather than something recovered from a document.
The three things Peppol actually is
1. A set of specifications
For documents to move between organisations that have never spoken before, they need a shared structure. The Peppol Business Interoperability Specifications define what a Peppol document looks like, built on ISO/IEC 19845 — Universal Business Language.
This is the layer that national variations sit on top of. Singapore's PINT-SG and the Australia–New Zealand PINT A-NZ are both specifications in this family, and a document valid under one is not automatically valid under another. That distinction causes more rejections than anything else →
2. A network
The delivery infrastructure. You connect to an access point, your trading partner connects to theirs, and documents route between them — a four-corner model, with the useful property that both ends are verified rather than merely addressed.
Some jurisdictions add a fifth corner so the tax authority receives a copy. Whether yours does changes what you are building →
3. A governance framework
The part that makes the other two trustworthy. OpenPeppol is a not-for-profit, member-led international organisation, established under Belgian law in 2012 and based in Brussels. It maintains the specifications and the agreements that access points sign.
Within each country a Peppol Authority administers the framework locally — the ATO in Australia, IMDA in Singapore, the Digital Agency in Japan, MDEC in Malaysia. This is why "certified access point" means something: it is an accreditation against a published framework, not a self-description.
How it got here
Peppol began in 2008 as a European Commission pilot — PEPPOL, Pan-European Public Procurement OnLine — aimed at cross-border public procurement. The first live transaction followed in 2010, Norway mandated it for e-invoicing in 2011, and OpenPeppol took over governance in 2012.
The capitalisation change is the interesting part. PEPPOL became Peppol as it stopped being an acronym for a European public-sector project and became a network used domestically, by private companies, well outside Europe.
The scale, as of now
As of June 2026, more than 4.4 million participants are registered in the OpenPeppol directory across over 100 countries.
The distribution says more than the total. Belgium alone accounts for over 2 million — roughly 47% of the global figure — after its B2B mandate took effect. It had 940,354 registrations in December 2025, passed a million on 30 January 2026, and had more than doubled to 2.13 million by June. France follows at around 890,000 and Australia at around 430,000.
That is what a mandate does to a network, and it is the clearest available answer to whether these obligations change behaviour.
One caveat worth carrying: the directory counts published receivers — organisations that have declared they can receive documents. Senders who have not published a receiving capability are not counted, so actual adoption runs ahead of the registry figure rather than behind it.
Why this matters for a decision
If you are choosing how to meet an e-invoicing obligation, the three-part distinction is the practical one. You need a specification your documents conform to, a route onto the network, and a provider accredited under the governance framework. A vendor can be excellent at one and weak at another.
And if someone tells you their PDF-by-email process already covers it, they have solved a document delivery problem rather than an invoicing one.
Our Peppol access point → · Compliance across APAC → · Europe and ViDA →