Peppol: the network that moves e-invoices

Peppol began in 2008 as the EU project Pan-European Public Procurement On-Line, built to make cross-border procurement documents flow between governments and their suppliers. Since September 1, 2012 the network has been governed by OpenPeppol, a member-driven non-profit association under Belgian law seated in Brussels, and its use has long outgrown procurement and Europe alike.

Countries participate through national Peppol Authorities that supervise the network locally; in Germany that role is anchored with KoSIT, the same standards body that operates XRechnung. The pairing is no accident: Peppol is infrastructure, and the documents it moves are the EN 16931 world XRechnung belongs to.

Peppol is a four-corner model. The sender hands the invoice to their certified Access Point, that Access Point looks up the receiver’s address in the network’s registry and delivers to the receiver’s Access Point, which passes the document on. Neither side builds a channel per business partner; each connects once and reaches everyone, which is the property email lacks the moment delivery must be provable and content must validate.

Addressing runs on Peppol participant IDs: a scheme prefix plus an identifier. For the German public sector the scheme is 0204 followed by the customer’s Leitweg-ID, so the buyer reference you already carry inside an XRechnung doubles, with its prefix, as the delivery address; for German federal receivers connected to the OZG-RE portal the Peppol receiver ID is exactly that construction. The invoice format on the network, Peppol BIS Billing 3.0, is itself a Core Invoice Usage Specification of EN 16931, so an invoice delivered over Peppol is a compliant E-Rechnung under § 14 UStG.

For low volumes, email delivery of XRechnung or ZUGFeRD files is legal and adequate, and public-sector suppliers can type invoices into the federal portals. Peppol starts paying for itself with volume and with the public sector: mass submission without portals, delivery confirmation instead of hope, validation at the network edge instead of rejection emails days later, and one connection that also reaches the growing set of countries standardizing on the network.

Connecting does not mean building infrastructure. Most businesses use a certified Peppol service provider whose Access Point is a web service or an API away; running your own Access Point is an option for those who want the network under their roof, via OpenPeppol membership. Issuing over Peppol and receiving over it are separate decisions, and many German businesses start with the issuing side because a public-sector customer demands it.

Whatever channel your suppliers choose, the receiving end still lands in the same place: an accounts-payable process that must read, validate, book, and archive the arriving data record. Talonic treats Peppol invoices, XRechnung files, ZUGFeRD hybrids, PDFs, and scans as one inflow, resolved into one schema-validated output with confidence and provenance per field. The free extractor below shows the BIS field model on a real e-invoice.

Reading about formats is one thing; an accounts-payable inbox full of them is another. Two free resources and one production path:

• Peppol e-Invoice Extractor: pull the seller, buyer, line items, VAT breakdown, and totals out of an e-invoice, free in the browser
• Peppol e-invoice extraction guide: the EN 16931 field model (Business Terms) explained field by field
• Invoice parsing with schema validation: process XRechnung, ZUGFeRD, Peppol invoices, PDFs, and paper scans into one validated output schema, with confidence and provenance on every value