Peppol vs UBL: What's the Difference? Two terms, two different things — here's the simple explanation

TL;DR: UBL is the file format — a specific XML structure for invoices. Peppol is the network — the secure delivery channel businesses use to exchange those files. A Peppol invoice is a UBL file sent over the Peppol network, the same way an email is text content sent over SMTP. You can have one without the other, but together they form the European e-invoicing backbone.

If you’ve started looking into e-invoicing, you’ve probably seen “UBL”, “Peppol”, “e-invoice” and “XML invoice” used as if they’re the same thing. They aren’t — and the difference actually matters when you’re choosing software, talking to suppliers, or trying to comply with mandates.

Here’s the simple version.

UBL is the file format

UBL stands for Universal Business Language. It’s a standard that defines how a business document — like an invoice, purchase order or credit note — should be structured as an XML file.

Think of it as the rulebook for what an invoice looks like as data:

• The supplier’s name goes in <cac:AccountingSupplierParty>
• The invoice date goes in <cbc:IssueDate>
• Each line item is a <cac:InvoiceLine> with quantity, price, VAT
• Bank details live in <cac:PaymentMeans>

Any UBL invoice — anywhere in the world — uses these same field names. That’s the whole point: it’s a shared language so that your accounting software can read an invoice produced by my accounting software, even if they’re completely different systems.

UBL is maintained by OASIS, an open standards body. It’s free to implement.

Peppol is the network

Peppol stands for Pan-European Public Procurement Online. Despite the name, it’s not just for governments and not just European anymore — Australia, Singapore, Japan, New Zealand and several US pilots all use Peppol now.

Peppol is the secure network that businesses, governments and accounting systems use to exchange e-invoices (and other documents) with each other directly. Think of it as the email system of e-invoicing — except that messages are validated, authenticated, and delivered to the right inbox automatically.

Each participant gets a unique Peppol ID (also called a Peppol address — typically your country code + your VAT number). When you send an invoice, your access point looks up the recipient’s Peppol ID, validates the document, and routes it through the network to their access point.

For Peppol to work, the documents flowing through it must follow a strict format. That format is — surprise — UBL (specifically the Peppol BIS Billing 3.0 profile, which is a tightened-up subset of UBL).

The relationship: how they fit together

	UBL	Peppol
What is it?	A file format	A delivery network
Analogy	A .docx Word file	Email/SMTP
Owner	OASIS (open standard)	OpenPeppol (non-profit)
Cost	Free	Free for users; access points charge a small fee per document
Required for compliance?	Often, as the base format	Required in some country mandates (e.g. Belgium 2026)
What you see	An XML file	A document arriving directly in your accounting software

So the relationship is:

A Peppol invoice is a UBL file delivered over the Peppol network.

You can have UBL without Peppol — for example, a supplier emailing you a UBL XML attachment. That’s still a valid UBL invoice; it just travelled by email instead of through the network.

You can also have Peppol with formats other than UBL — Peppol can technically carry other document types — but in practice the overwhelming majority of Peppol traffic is UBL.

Why the confusion?

Several reasons people mix the terms up:

1. Both became mainstream around the same time. The EU directives that pushed e-invoicing also pushed Peppol adoption, and UBL was the format chosen for those mandates.
2. Marketing collapses the distinction. Software vendors say “we support Peppol” when they mean “we can produce Peppol-compliant UBL and connect to a Peppol access point.”
3. Country mandates often require both. Belgium’s 2026 rule, for example, requires both the format (Peppol BIS UBL) and the channel (Peppol network). So in practice you do them together.
4. The end-user experience is the same. Whether the UBL arrived via email or via Peppol, you still see “an XML invoice came in.”

Practical implications

If you’re choosing software

Ask vendors two separate questions:

• “Can you produce and read UBL (Peppol BIS 3.0)?” → format support
• “Are you connected to a Peppol access point?” → network support

A tool that does both is fully Peppol-ready. A tool that only does UBL means you’ll need an external access point to send and receive over the network.

If you’re a recipient

You don’t necessarily need to be on Peppol to receive a UBL invoice. A supplier can email you a UBL XML, and a viewer like UBL Buddy opens it on your Mac, iPhone or iPad like you’d open a PDF. To send invoices over Peppol you do need access point connectivity, usually via your accounting software.

If you’re complying with a mandate

Check whether your country’s mandate requires the format (UBL) only, or also the channel (Peppol). For Belgium 2026, Germany 2025-2027 and most EU countries, Peppol is the recommended (or required) channel — but specifics vary.

Frequently asked questions

Is every UBL invoice a Peppol invoice?

No. A UBL file emailed to you is still UBL but isn’t a “Peppol invoice” until it actually travels through the Peppol network. In practice the format and the network are usually paired, so most UBL invoices in 2026 are Peppol invoices, but not all.

Is every Peppol invoice a UBL invoice?

Almost always, yes. Peppol can technically carry other document formats, but the standard for invoices on the network — Peppol BIS Billing 3.0 — is built on UBL. So in practice: yes.

Do I need a Peppol ID to read invoices?

No. A Peppol ID is needed to receive invoices over the network. To open and read a UBL XML file you’ve received by any other means (email, file transfer), you only need a viewer.

What’s “Peppol BIS”?

BIS stands for Business Interoperability Specification. It’s a profile that picks specific UBL fields and rules to ensure invoices can be exchanged across the Peppol network without ambiguity. Peppol BIS Billing 3.0 is the current standard for invoices.

Is XRechnung the same as UBL?

XRechnung is a German variant of e-invoicing that builds on UBL (or alternatively, the UN/CEFACT Cross Industry Invoice). All XRechnung documents are valid UBL or CII XML, but not every UBL is XRechnung — it has additional German-specific rules. See our Germany e-invoicing guide.

What about ZUGFeRD?

ZUGFeRD is a German hybrid format: a PDF with embedded XML data (UBL or CII). The PDF is human-readable; the embedded XML is machine-readable. So a ZUGFeRD file contains UBL or CII, but it’s a different “container” than a pure XML file.

Further reading

• What is a Peppol invoice? — full explanation of the standard and network
• How to open an XML invoice on Mac — practical viewer comparison
• E-invoicing mandates by country — when do you need to be Peppol-ready?
• E-invoicing in Belgium 2026 — first major EU mandate to require Peppol channel by law