What Is Peppol? ID, Access Point, BIS Explained
One term keeps coming up around the e-invoice: Peppol. What it actually means sounds more technical than it is. We explain in plain words what Peppol really is – a transport network, not a file format – and what Peppol ID, Access Point and Peppol BIS stand for.
June 5, 2026
In short
Peppol is a European transport network for electronic documents – the channel an e-invoice is sent through, not the format of the invoice itself. Each participant has a Peppol ID as their address and connects to the network through an Access Point. The content follows the Peppol BIS specification, which, like XRechnung and ZUGFeRD, is built on the EN 16931 norm. Format and transport channel are therefore two separate things.
What Peppol actually is
Anyone looking into the e-invoice runs into the term Peppol quickly – and just as quickly into the question of whether it’s a new format to learn alongside XRechnung and ZUGFeRD. It isn’t.
Peppol is a transport network. You can picture it as a postal network for digital business documents: it makes sure an invoice reaches one company from another in a secure, standardised way. What sits inside the “envelope” – the actual invoice format – is a separate question.
Why a dedicated network at all?
In everyday practice, many invoices still travel by email. That works, but it is neither standardised nor reliably auditable. Peppol solves a problem that grows with the number of business partners: instead of setting up a separate connection or agreement with each partner, every participant connects to the network once and reaches all the others through it.
It’s a bit like the telephone network: you don’t need a direct line to every person you call. You have one connection and one number – the network handles the rest.
The three terms that keep coming up
Peppol ID
The unique address of a participant on the network – comparable to a phone number. Others find and reach you through it.
Access Point
The entry point to the network – a certified service provider through which you send and receive. Often this is handled by your software or a provider.
Peppol BIS
The content specification for the document. It is built on the European norm EN 16931 – just like XRechnung and ZUGFeRD.
The 4-corner model – in plain terms
Behind Peppol sits a simple principle, often described as the 4-corner model. It names the four parties an invoice travels through:
The sender
The company that creates and sends the invoice – usually straight out of its own software.
Their Access Point
The sender’s entry point, which feeds the invoice into the Peppol network.
The recipient’s Access Point
The entry point on the other side, which receives the invoice from the network.
The recipient
The company that receives the invoice – discoverable through its Peppol ID.
The appeal of this model: each side only deals with its own Access Point. Sender and recipient don’t have to connect directly and don’t have to use the same provider. The network in between makes sure corners 2 and 3 understand each other.
A single connection to your own Access Point is enough to reach every other participant on the network. That is what lets Peppol scale – you no longer maintain a separate connection for each business partner.
Peppol BIS vs. the formats XRechnung and ZUGFeRD
This is where the relationship between format and network becomes clearer. As a reminder, an e-invoice is an invoice in a structured electronic format per the EN 16931 norm; a plain PDF is not an e-invoice in this sense. In Germany, two formats are common:
XRechnung
A purely structured XML format. Machine-readable, with no visible layout – the content sits in clearly defined data fields.
ZUGFeRD
A hybrid format: a PDF with embedded XML. People see a familiar PDF, machines read the structured data inside it.
Peppol BIS operates on a different level. It is the specification that defines how a document must be structured to be sent across the Peppol network. Peppol BIS is also built on EN 16931 – so it isn’t a competing format, but describes the form in which an EN 16931-compliant document travels through the network.
In short: the format (XRechnung, ZUGFeRD) describes what is in the invoice, and the transport channel (e.g. Peppol) describes how it reaches the recipient. The two can be considered independently of each other.
What role does Peppol play in Germany and Austria?
In Germany, receiving e-invoices in a structured format has been mandatory for all companies since 1 January 2025 – including small businesses. For issuing, the obligation applies in stages: from 1 January 2027 for companies with more than 800,000 euros in turnover, and from 1 January 2028 for all domestic B2B.
Peppol is one of the established ways to exchange these invoices and is already widespread in dealings with public administration. In Austria, the federal government also uses Peppol for invoices to the administration. Whether a specific case uses Peppol, an email with an attached structured format, or another channel depends on the business partner and the software in use.
In short
Peppol is not the next format you have to memorise. It is the network e-invoices travel through. The Peppol ID is the address, the Access Point is the entry point, and the 4-corner model describes how an invoice finds its way across two Access Points.
The key is to keep format and transport channel apart: XRechnung and ZUGFeRD say what is in the invoice, while Peppol BIS and the network behind it take care of how it arrives – all of it on the foundation of EN 16931.
Sources
- Bundesministerium der Finanzen – FAQ on the introduction of the mandatory e-invoice
- OpenPeppol – About Peppol: network, specifications and BIS
Related articles
With Orcha: The accounts payable agent takes in incoming e-invoices – whether as XRechnung, ZUGFeRD or via Peppol – and processes the structured data directly, without anyone having to retype it by hand.
FAQ
Is Peppol a file format like XRechnung or ZUGFeRD?
No. Peppol is a transport network for exchanging electronic documents – the channel an invoice travels through from A to B, not the format of the invoice itself. XRechnung (structured XML) and ZUGFeRD (a PDF with embedded XML) are the file formats. Both are built on the European norm EN 16931. For the content, Peppol uses the Peppol BIS specification, which is also built on EN 16931. Format and transport channel are two separate things.
What is a Peppol ID and an Access Point?
A Peppol ID is the unique address of a participant in the Peppol network – comparable to a phone number through which others can find and reach you on the network. An Access Point is the entry point to the network: a certified service provider through which you send and receive documents. So you connect to Peppol via an Access Point and are discoverable there through your Peppol ID. In practice, the software you use or a provider usually takes on this role.
How does the 4-corner model work in Peppol?
The 4-corner model describes four parties: the sender (corner 1), their Access Point (corner 2), the recipient’s Access Point (corner 3) and the recipient themselves (corner 4). The invoice travels from the sender through their Access Point into the Peppol network, on to the recipient’s Access Point and finally to the recipient. The benefit: each side connects only once to its own Access Point and reaches all other participants through it – without setting up a separate connection for every business partner.
Does Peppol matter in Germany and Austria?
Yes. In Germany, receiving e-invoices in a structured format has been mandatory for everyone since 1 January 2025, and from 1 January 2027 companies with more than 800,000 euros in turnover must issue such invoices in domestic B2B, then all from 1 January 2028. Peppol is one of the established ways to exchange these invoices and is already widespread in the public sector. In Austria, the federal government also uses Peppol for invoices to public administration. Which transport channel is used in a specific case depends on the business partner and the software in use.
New tips straight to your inbox
Subscribe to our newsletter and receive practical AI tips for your daily work.