Peppol BIS 3 E-Invoice Standard

Universal Peppol-based

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.

7 Countries
52+ Data fields
Yes Structured format
Peppol Delivery network
AI Summary

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 compliant 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
02
03

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

Code Field name Mandatory
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

Common Mistakes to Avoid

  • Using Peppol BIS 2.x syntax instead of 3.0 — formats are not backward compatible
  • Not registering a Peppol ID before attempting to send
  • Confusing Peppol BIS 3 with plain UBL 2.1 — Peppol has additional constraints

Need implementation help?

Tell us your ERP, countries of operation, and transaction volume. We'll match you with vetted providers familiar with Peppol BIS 3.

Request Provider Shortlist

Tell us about your requirements and get matched with vetted e-invoicing providers. We'll recommend options based on your country, ERP, and route preferences.

By submitting this form, you agree to receive a response to your inquiry. We do not sell or share your information. This service is provided as-is for informational purposes.

Official Sources

All information on this page is based on the sources listed below. Always verify current requirements with the issuing authorities.

  • OpenPeppol AS Last verified: 2026-05-01

    Official Peppol organisation; BIS 3.0 specifications and policy documents

  • OpenPeppol AS Last verified: 2026-05-01

    Technical specification for Peppol BIS 3.0 invoice, credit note, and related documents

  • OpenPeppol AS Last verified: 2026-05-01

    Overview of the Peppol network infrastructure and global coverage