Peppol BIS 3 E-Invoice Standard
OpenPeppol AS (non-profit) · Version 3.0
Peppol BIS 3.0 is a set of structured document specifications built on UBL 2.1, implementing the EN 16931 semantic model. It is the format used on the Peppol Network — a global e-delivery infrastructure connecting businesses, governments, and ERP systems across 40+ countries.
Peppol BIS 3.0 is the most widely adopted e-invoicing specification globally. It combines UBL 2.1 syntax with EN 16931 semantics, creating a format that is both technically structured and legally relevant across multiple jurisdictions. The Peppol Network provides the routing infrastructure — a "network of networks" that connects access points globally. To use Peppol, a business needs a Peppol ID (obtained via a Peppol Registration Authority) and an access point provider.
Grounded in official sources listed below. Not a substitute for legal or tax advice.
Quick Answers
- 01 What is Peppol BIS Billing 3.0?
- Peppol BIS Billing 3.0 is a set of structured document specifications built on UBL 2.1 XML, implementing the EN 16931 semantic model. It is the invoice format used on the Peppol Network — a global e-delivery infrastructure connecting businesses, governments, and ERP systems across 40+ countries.
- 02 Do I need to use Peppol to send a Peppol BIS 3 invoice?
- Technically no — Peppol BIS 3 is a UBL-based format that can be sent outside Peppol. But Peppol is the primary delivery mechanism and provides routing, delivery confirmation, and cross-border interoperability.
- 03 How many countries support Peppol?
- Peppol has active presence in 40+ countries across Europe, Asia-Pacific, and the Americas. Coverage varies by country.
- 04 What is the difference between Peppol BIS 3.0 and EN 16931?
- EN 16931 defines the semantic invoice data model — what fields an invoice must contain. Peppol BIS Billing 3.0 implements EN 16931 as a UBL 2.1 XML specification with additional Peppol-specific validation rules. Think of EN 16931 as the dictionary and Peppol BIS 3 as a specific grammar book that follows it.
- 05 How is Peppol BIS 3.0 different from XRechnung or Factur-X?
- XRechnung (Germany) and Factur-X (France) are national format profiles that also implement EN 16931. Peppol BIS 3 is a network-focused specification used globally. They share the same EN 16931 data semantics but differ in XML structure, validation rules, and delivery mechanism. An invoice valid in one format is not automatically valid in another.
Peppol invoice format: BIS 3.0, EN 16931, and UBL explained
Search results for "Peppol format", "Peppol invoice", and "Peppol standard" often surface different terms — sometimes interchangeably. This table clarifies what each query phrase usually means and how it relates to the precise Peppol BIS Billing 3.0 specification.
Peppol BIS Billing 3.0: what the format is, how it relates to EN 16931, and what ERP teams need to know
Peppol BIS Billing 3.0 is the invoice specification used on the Peppol Network — a global e-delivery infrastructure connecting businesses, governments, and ERP systems across 40+ countries. The specification is published by OpenPeppol AS and combines two layers: the EN 16931 semantic model (what data an invoice must contain) and the UBL 2.1 XML syntax (how that data is structured and transmitted). To use Peppol BIS Billing 3.0, a business needs a Peppol ID (obtained through a Peppol Registration Authority) and a Peppol Access Point subscription. The format is particularly relevant for businesses operating across borders or sending to Peppol-connected government procurement systems. Key ERP integration considerations include exporting invoices as valid UBL 2.1 XML, mapping ERP fields to EN 16931 BT codes, and configuring Peppol Access Point routing. Peppol BIS Billing 3.0 is not itself a country mandate — it is a specification relevant where Peppol network exchange is used, and it is one of several EN 16931-based formats alongside XRechnung (Germany), Factur-X (France), and ZUGFeRD (Germany B2B).
Key Data Fields
The following data elements are central to the Peppol BIS 3 specification. Mandatory fields are required for compliance; optional fields add detail.
UBL Invoice Structure
cbc:ID Invoice number Yes cbc:IssueDate Invoice issue date Yes cac:AccountingSupplierParty Seller party Yes cac:AccountingCustomerParty Buyer party Yes cac:InvoiceLine Invoice lines Yes Validation Requirements
Invoices using this standard must pass the following validation checks before transmission. Rejections typically occur due to missing mandatory fields or incorrect data types.
- Must conform to UBL 2.1 XML schema
- Must include all mandatory EN 16931 BT elements
- Peppol-specific rules: document type codes, process IDs, Peppol participant IDs
- Signature requirements for Peppol transport
Key Advantages
- Global coverage across 40+ countries
- Open standard with no vendor lock-in
- Built-in routing and delivery confirmation via Peppol network
- Strong ERP ecosystem support
Implementation Considerations
- Requires access point subscription
- Additional Peppol-specific validation rules beyond standard UBL
- Some countries have national formats that differ slightly from Peppol BIS 3
Also Known As
Also searched as: Peppol format, Peppol invoice format, Peppol invoice, Peppol standard, Peppol standards, Peppol BIS, Peppol BIS 3, Peppol BIS 3.0, Peppol BIS Billing 3.0, Peppol invoice specification.
How It Connects
- Peppol BIS Billing 3.0 — formal billing specification built on UBL 2.1 with EN 16931 semantics
- Peppol Access Point — certified routing service that sends and receives Peppol documents
- EN 16931 — European semantic model that Peppol BIS 3.0 implements; defines what data fields an invoice must contain
- UBL 2.1 — XML syntax layer that Peppol BIS 3.0 uses as its document format
- XRechnung / Factur-X / ZUGFeRD — national formats that share EN 16931 semantics but may use different XML profiles
- Peppol BIS 3.0 is not itself a country mandate — it is a specification relevant where Peppol network exchange is used
Official Sources
All information on this page is based on the sources listed below. Always verify current requirements with the issuing authorities.
- OpenPeppol — BIS 3.0 Specification Standard Body
Official Peppol organisation; BIS 3.0 specifications and policy documents
- Peppol BIS 3.0 Document Set Standard Body
Technical specification for Peppol BIS 3.0 invoice, credit note, and related documents
- Peppol Network — About Standard Body
Overview of the Peppol network infrastructure and global coverage