Peppol e-invoicing: how the network works and where AP automation connects

Peppol e-invoicing means sending and receiving invoices as structured data over an open network, through accredited service providers called Access Points. Connect to one provider and you can reach any buyer or supplier registered on the network. For accounts payable, an inbound Peppol invoice arrives as data instead of a PDF, so extraction goes away. Matching, fraud checks and approval stay.

#What Peppol is

Peppol is an interoperability framework, and OpenPeppol is the organization behind it. OpenPeppol calls itself a non-profit international association under Belgian law, and calls Peppol "an enabler" rather than a portal or an exchange service. The network started in 2008 as a pilot funded by the European Commission and its consortium members. OpenPeppol took over the services in 2012 when the project closed.

You don't join OpenPeppol to use the network. Its membership page says end users are not required to become members to send or receive Peppol-based messages. Members are the service providers that run Access Points, plus public bodies and others who help govern the standards. A business just picks a certified provider, which might be a standalone e-invoicing platform or the vendor of your ERP.

#How the four-corner model works

Older invoice networks were closed: buyer and supplier had to use the same provider. Peppol puts a provider on each side instead, and the two providers talk to each other. That gives four corners.

1. The supplier's accounting or billing software creates the invoice in a Peppol format and hands it to the supplier's Access Point (corner two).
2. That Access Point looks up the buyer's Peppol ID. Peppol's published specifications cover the Service Metadata Locator (SML) and Service Metadata Publishing (SMP) services for this step. In plain terms, the lookup tells the sender where the buyer's provider is and which document types it accepts.
3. The supplier's Access Point sends the invoice across the network to the buyer's Access Point (corner three). The mandatory transport is the Peppol AS4 profile, wrapped in a standard business message envelope.
4. The buyer's Access Point delivers the invoice to the buyer's AP system (corner four), which is where your automation picks it up.

The supplier never needs to know which provider you use, and no central hub holds the invoices. Each provider only handles its own customers' traffic.

#What a Peppol invoice contains

The invoice follows Peppol BIS Billing 3.0, a Core Invoice Usage Specification (CIUS) of the European standard EN 16931. The specification states that any compliant instance document is also compliant with the European standard. The file is XML in the UBL syntax. There is no page image.

BIS Billing 3.0 covers two documents, the invoice and the credit note. A credit note uses type code 381. A negative invoice (type 380 with negative amounts) is the alternative, and your receiving system has to handle both. A separate invoice response message lets the buyer accept, reject or query an invoice. Suppliers like that one, because it tells them why they haven't been paid.

#Mandate dates by country (as of October 2026)

Rules change often, so treat this as a snapshot and check the source for your own case. We list only what we could read on official pages.

A mandate doesn't mean Peppol. France routes invoices through accredited platforms, and the official guidance we read doesn't name Peppol. Germany's rules set a structured format, not a network. Belgium is the one clear Peppol-first case in this list.

The Gulf runs on different national models. We cover them separately on our pages for the UAE and Saudi Arabia's ZATCA program, so we won't repeat them here.

#Where AP automation connects

Take a team that receives 1,500 supplier invoices a month, as an example. Say 300 arrive over Peppol and 1,200 as PDFs. The Peppol 300 skip extraction. They still need every other control.

The pipeline for an inbound Peppol invoice looks like this:

1. Receive the invoice from your Access Point through its API, or from a file drop, and store the original XML.
2. Map the fields into your internal invoice record: supplier ID, invoice number, dates, PO reference, lines, tax categories, payment details and totals.
3. Run the same checks you run on PDFs. Test for duplicates, look the supplier up in the vendor master, and compare the bank account with the one on file.
4. Match to the purchase order and receipt. A structured invoice makes line-level matching cleaner because quantities and unit prices are separate fields. See our accounts payable automation guide for how matching tolerances work.
5. Suggest a GL code and cost center from history, then route approval.
6. Post to the ERP with the source XML attached.

Key point: Structured does not mean correct. A Peppol invoice can carry the wrong PO number or a changed bank account, and the network will deliver it perfectly. Keep duplicate checks, bank-detail verification and matching on every invoice, whatever channel it came through.

AI still earns its keep in the messy parts. It maps a supplier's free-text line description to a PO line, suggests coding for a new supplier, and handles the PDFs that keep arriving from suppliers who haven't connected. If your ledger is Xero, QuickBooks or NetSuite, posting works the same for either format (here is our Xero integration). Only the front of the pipeline differs.

#Choosing an e-invoicing provider

An e-invoicing platform usually means a certified Access Point plus tooling around it. When you compare providers, ask about these.

• Is the provider a certified Peppol service provider? OpenPeppol distinguishes certified service providers from candidates, and candidates are not yet authorized to offer services in a Service Domain.
• Does it handle both sending and receiving, and for which countries?
• Which formats does it support? Peppol BIS Billing 3.0 is the baseline, and some countries add local requirements.
• How does it deliver inbound invoices: API, webhook, file export, or only through its own screen?
• Does it keep an archive, and for how long, to meet the retention rules in your jurisdiction?
• How does it price: per document, per volume tier, per entity? Get a written quote against your actual volumes.
• Can it connect to your ERP, or will you build that link?

If you already own an ERP or AP tool, ask that vendor first. Some offer Peppol connectivity, and a second platform is a second contract to manage.

#Limits to plan for

Peppol only covers suppliers who have joined, so the PDF channel stays for the long tail. Credit notes, partial deliveries and invoices without a PO still need a person. An e-invoice that satisfies the network may also need extra fields for local tax. We'd rather say that now than promise one pipe for every country.

#Sources

Facts about Peppol and mandates in this article come from these pages, read in October 2026:

• OpenPeppol: About Peppol (opens in a new tab)
• OpenPeppol: Join (opens in a new tab)
• Peppol eDelivery specifications (opens in a new tab)
• Peppol BIS Billing 3.0 (opens in a new tab)
• European Commission: VAT in the Digital Age (opens in a new tab)
• Belgium e-invoice portal (opens in a new tab)
• impots.gouv.fr, Fiche 1 on e-invoicing (opens in a new tab)
• Germany, Federal Ministry of Finance e-invoice FAQ (opens in a new tab)
• Germany, § 27(38) UStG transition rules (opens in a new tab)

For a short definition, see our glossary entries on Peppol and e-invoicing. If you want to map how inbound e-invoices should feed your AP process, book a strategy call. Bring a sample of your current invoice channels and your ERP name, and we'll show you which checks to keep.

#Frequently asked questions

#What is Peppol e-invoicing?

It is the exchange of invoices as structured data over the Peppol network. Each party connects through an accredited Access Point, and the two Access Points pass the invoice to each other. The buyer's system receives data it can process directly, with no PDF to read.

#Is Peppol e-invoicing mandatory?

It depends on the country. Belgium requires structured B2B e-invoices from 1 January 2026, exchanged over Peppol. France and Germany have their own mandates and dates, and neither is described as Peppol-only in the official sources we read. Check the rules where you and your counterparties are established.

#Do we need to join OpenPeppol to send or receive Peppol invoices?

No. OpenPeppol says end users are not required to become members. You connect through a certified service provider, which handles the technical side and registers your Peppol ID.

#Is a Peppol invoice the same as a PDF invoice?

No. A PDF is a picture or text layer that software has to interpret. A Peppol invoice is structured XML following Peppol BIS Billing 3.0, with named fields for the invoice number, PO reference, lines, tax and totals. A PDF can be attached to it, but the data is the invoice.

#Do we still need AP automation if our suppliers send Peppol invoices?

Yes. You skip extraction, but you still need duplicate detection, supplier and bank checks, PO matching, coding, approval routing and posting. Most teams also keep receiving PDFs from suppliers who are not on the network, so the same pipeline has to take both.