Peppol e-invoicing in Europe, explained without the jargon.
Peppol is the network most European countries now use to move structured invoices between businesses. This guide covers what it is, what a compliant invoice actually contains, who has to comply and when, and where implementation projects usually go wrong.
What Peppol actually is
Peppol is a set of agreements, not a piece of software. It defines how a business is identified on the network (a Peppol identifier, usually derived from a VAT or company number), how access points exchange documents, and what a valid invoice looks like. In practice, you connect once to an access point; that access point finds your customer's access point in the Peppol directory and delivers the invoice as structured data, not as a PDF attachment.
The content standard behind it is EN 16931, the European e-invoicing semantic model. National formats are built on top of it: Peppol BIS Billing 3.0 in Belgium, XRechnung and ZUGFeRD in Germany, Factur-X in France. Because they share the same semantics, a single well-built mapping usually covers several countries — which is exactly why the order of work matters.
Not every country uses peer-to-peer Peppol. Slovakia, for example, runs a central platform through its Financial Administration, and Poland operates a national system with state-assigned identifiers. Those are clearance models: the invoice is submitted, validated and registered by the state before it reaches the buyer, so the integration is an API against a central service rather than a message to a counterparty.
Who has to comply, and when
Timetables differ per country and some have already been revised more than once. The table below is our working summary of the European markets we are asked about most — confirm the current position with your advisor before planning a go-live.
| Country | Network | Format | Status | Since |
|---|---|---|---|---|
Belgium Domestic B2B invoices must be structured e-invoices exchanged over Peppol, using the BIS Billing 3.0 specification. Paper and PDF stop being valid invoices between Belgian VAT-registered businesses. | Peppol | BIS Billing 3.0 (EN 16931) | Mandatory | 1 Jan 2026 |
France The French reform moves to a state-linked clearance model, rolling out in waves from the largest companies downwards. Factur-X is the hybrid format used in practice today. | Chorus Pro / state platform | Factur-X · UBL · CII | Phasing in | 1 Sep 2026 |
Germany Receiving structured e-invoices has been mandatory for domestic B2B since 2025. Issuing becomes mandatory in 2027 for businesses above EUR 800,000 turnover and in 2028 for everyone, with paper and PDF only allowed by consent until then. | Peppol or direct exchange | XRechnung · ZUGFeRD 2.1.1 | Phasing in | 1 Jan 2025 |
Netherlands No general B2B mandate yet. Peppol is widely used in practice and effectively required for suppliers to central government. | Peppol | BIS Billing 3.0 | Voluntary | 1 Jan 2019 |
Poland Structured invoices are issued through KSeF, the national e-invoicing system, with a state-assigned identifier. Rollout started with the largest taxpayers and extends in later waves. | KSeF (state platform) | FA(2) XML | Phasing in | 1 Feb 2026 |
Slovakia B2B invoices are issued through the Financial Administration's IS EFA platform: a central clearance model where the invoice is submitted, validated and delivered to the buyer by the state system. | IS EFA (state platform) | e-Faktúra (EN 16931 extension) | Mandatory | 1 Jan 2025 |
What a compliant flow looks like
Compliance is the easy part to buy. The flow that keeps working after go-live is the part that has to be built.
- 01
Receive invoices on a Peppol access point that is registered for each of your legal entities.
- 02
Map your ERP or billing system to EN 16931 so line items, VAT categories and rounding survive the trip.
- 03
Validate before sending: missing buyer references and wrong VAT identifiers are the two most common rejections.
- 04
Automate the inbound side — validation, booking and a queue for anything that fails.
- 05
Keep the payload, the delivery status and the response together for the full retention period.
Not sure which rules apply to you?
We map your invoice flows against the countries you invoice in and tell you what is actually required — and what is not.