Peppol BIS 3.0 Guide — What It Is, When to Use It & How to Create One

What Is Peppol BIS 3.0?

Peppol BIS 3.0 — formally known as Peppol Business Interoperability Specification for Billing 3.0 — is the most widely accepted e-invoicing format across Europe. It defines how an electronic invoice should be structured so that any business connected to the Peppol network can send and receive invoices seamlessly, regardless of what accounting software they use.

Think of it this way: Peppol is both a network (the infrastructure that delivers invoices between businesses) and a document format (the specification that defines what an invoice looks like). BIS 3.0 is the document format part — it tells you exactly which fields an invoice must contain, how they should be organised, and what values are allowed. The underlying syntax is UBL 2.1 (Universal Business Language), an international XML standard maintained by OASIS.

Peppol BIS 3.0 is fully compliant with EN 16931, the European standard for electronic invoicing. This means that any Peppol invoice automatically meets the baseline requirements set by the EU for all member states. Countries can add their own additional rules on top (called a CIUS — Core Invoice Usage Specification), but the Peppol BIS 3.0 format itself provides a pan-European default that works across borders.

When to Use Peppol BIS 3.0

Peppol BIS 3.0 is the default choice for EU e-invoicing when no country-specific format is mandated. It is required or strongly preferred in the following scenarios:

• Belgium: Mandatory for all B2B transactions from January 2026 — see our Belgium guide
• Netherlands: Mandatory for B2G since 2017, widely adopted for B2B — see our Netherlands guide
• Denmark: Europe's e-invoicing pioneer, Peppol BIS 3.0 via NemHandel — see our Denmark guide
• Sweden: Mandatory for B2G since 2019 — see our Sweden guide
• Finland: High adoption rate alongside Finvoice — see our Finland guide
• Luxembourg: B2G mandatory since 2022 — see our Luxembourg guide
• Norway: B2G mandatory since 2012, strong B2B adoption

For B2G (business-to-government) invoicing, Peppol BIS 3.0 is accepted or required in virtually all EU member states. For B2B (business-to-business), it is the format of choice in Scandinavia, the Benelux countries, and increasingly across the rest of Europe as countries implement their national e-invoicing mandates.

If you trade across multiple EU countries and want a single format that works everywhere, Peppol BIS 3.0 is your best bet. Some countries like Germany have their own national formats (XRechnung), and France prefers Factur-X, but Peppol remains accepted alongside these national standards in most cases.

Technical Structure

A Peppol BIS 3.0 invoice is an XML file following the UBL 2.1 schema. At a high level, the document contains these main sections:

• Invoice header: Invoice number, issue date, due date, currency code, and document type (invoice or credit note)
• Seller (AccountingSupplierParty): Company name, address, VAT number, and Peppol participant ID
• Buyer (AccountingCustomerParty): Recipient company name, address, VAT number, and Peppol participant ID
• Payment information: Payment means (bank transfer, direct debit, etc.), bank account details (IBAN/BIC), and payment terms
• Tax summary (TaxTotal): Breakdown of VAT by rate, taxable amounts, and tax amounts
• Line items (InvoiceLine): Individual products or services with descriptions, quantities, unit prices, and per-line tax information
• Monetary totals (LegalMonetaryTotal): Net amount, tax amount, and gross total

The file uses the namespace urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 and must validate against both the UBL 2.1 schema and Peppol's own business rules. These business rules enforce things like: "if the VAT category is reverse charge, then the tax amount must be zero" — practical checks that go beyond pure schema validation.

How Peppol BIS 3.0 Compares to Other Formats

Peppol BIS 3.0 is one of several e-invoicing formats that comply with EN 16931. Here's how it relates to the others:

• vs. XRechnung: XRechnung is Germany's national CIUS — it adds stricter rules on top of EN 16931. XRechnung can use either UBL 2.1 or CII syntax. A Peppol BIS 3.0 invoice is not automatically XRechnung-compliant (it may lack German-specific fields like the Leitweg-ID), but both share the same UBL foundation.
• vs. ZUGFeRD / Factur-X: These are hybrid formats that embed XML inside a PDF/A-3 file. They use CII (Cross Industry Invoice) syntax, not UBL. Peppol BIS 3.0 is pure XML — no PDF wrapper. The two approaches serve different needs: Peppol for fully automated processing, ZUGFeRD/Factur-X for scenarios where a human-readable PDF is also needed.
• vs. Credit Notes: Peppol BIS 3.0 supports both invoices and credit notes. A Peppol credit note uses a different root element (CreditNote instead of Invoice) but follows the same BIS 3.0 specification.

How InvoicePeppol Helps

InvoicePeppol converts your existing PDF invoices into fully compliant Peppol BIS 3.0 XML in seconds. Our AI extracts all invoice data — seller, buyer, line items, tax calculations — and generates validated UBL 2.1 XML that passes Peppol business rule checks. You can also create invoices from scratch using our invoice builder.

Frequently Asked Questions