Key takeaways
- Peppol BIS Billing 3.0 is the invoice profile used on the Peppol network, not a format invented from scratch.
- It is a Core Invoice Usage Specification (CIUS) of the EN 16931 standard, built on the UBL 2.1 syntax.
- The profile covers two documents, the invoice and the credit note, and adds its own validation rules.
- For B2B in Belgium, a business is identified by its enterprise number through the 0208 scheme.
Peppol BIS Billing 3.0, the format that travels the network
When an invoice moves across the Peppol network, it does not travel in a free form: it follows a precise profile, Peppol BIS Billing 3.0. That profile dictates what information the invoice contains, how it is written and which rules it must pass to be accepted. Understanding it means understanding what is really at stake behind the B2B mandate.
BIS stands for Business Interoperability Specification. The profile is published and maintained by OpenPeppol, the association that governs the network. It does not come out of nowhere: it builds on the European standard and on an existing XML format, which it pins down for concrete use.
This article describes what the profile actually contains. For the structure of the XML file itself, read The UBL 2.1 format explained; for the network that carries it, Understanding the Peppol network in 5 minutes.
What Peppol BIS Billing 3.0 actually covers
The profile is officially a Core Invoice Usage Specification (CIUS) of the EN 16931 standard. In practice that means two things. First, any invoice compliant with Peppol BIS Billing 3.0 is also compliant with EN 16931: the profile never contradicts the standard, it specialises it. Second, it makes choices where the standard left room: it adopts a single syntax and tightens certain rules.
The syntax it adopts is UBL 2.1. EN 16931 allows two XML syntaxes (UBL 2.1 and UN/CEFACT CII); for billing on Peppol, UBL 2.1 is the one used in practice. A Peppol BIS Billing 3.0 invoice is therefore, technically, a UBL 2.1 file that follows the EN 16931 model and the rules specific to Peppol.
The three layers that make up the profile
The semantic model (EN 16931)
The list of information an invoice must or may contain: seller, buyer, lines, VAT breakdown, totals.
The syntax (UBL 2.1)
The concrete XML grammar that expresses that model, document by document.
The Peppol rules
Validation rules and code lists added by OpenPeppol, plus the identification of the parties on the network.
The two documents of the profile: invoice and credit note
Peppol BIS Billing 3.0 does not cover a single document type. The profile defines two messages, both in UBL 2.1: the invoice (Invoice) and the credit note (CreditNote). The credit note is not a technical detail: it is what lets you correct or cancel an invoice already sent, within the same structured frame and with the same processing reliability.
Both documents share the same logic: a header, the parties (seller, buyer, and where needed a payee), the lines, the VAT breakdown and the monetary totals. That symmetry is deliberate: the software that can read an invoice can read the matching credit note.
documents covered
the invoice and the credit note
syntax adopted
one of the two allowed by EN 16931
Belgian scheme
identifies a business by its CBE number
EN 16931 and Peppol BIS Billing 3.0: who does what
The most common confusion pits the standard against the profile as if you had to choose. In reality, the profile does not replace the standard: it stacks on top of it. The table below places each role.
| EN 16931 standard | Peppol BIS Billing 3.0 | |
|---|---|---|
| Defines what information the invoice contains | ||
| Mandates the XML syntax (UBL 2.1) | ||
| Adds validation rules specific to the network | ||
| Document ready to travel via a Peppol access point |
The rules added by Peppol carry a recognisable prefix in validation reports and complement those of EN 16931. They come with mandated code lists too: VAT categories, units of measure, currencies and countries follow standardised references, so that the same code means the same thing for the sender and the recipient.
Identifying the parties: the 0208 scheme in Belgium
One thing clearly sets Peppol apart from a plain file exchange: for an invoice to reach the right recipient, every business must be identifiable on the network. That identification rests on a scheme. In Belgium, the scheme used for B2B billing is the 0208 prefix, which designates the enterprise number (Crossroads Bank for Enterprises). It matches the Belgian VAT number without the "BE" prefix.
In practice, a business whose VAT number is BE0123.456.789 is reachable on Peppol at the address 0208:0123456789. That identifier is what your software writes into the invoice and what the network uses to route the document to the right access point. For how to connect, see Peppol access point: what it is for.
Compliant Peppol BIS Billing 3.0 invoices, without touching the XML
YouInv generates your invoices in the Peppol BIS Billing 3.0 profile, validates them and sends them over the Peppol network in a few clicks.
What it changes for your business
The good news is the same as for UBL: you do not have to handle the profile directly. Compliant software takes care of producing a valid Peppol BIS Billing 3.0 file, running it through the validation rules and routing it. Your job is limited to entering correct data.
What changes is the criterion for choosing your tool. Issuing a PDF no longer suffices in B2B: your software must be able to generate, validate and receive documents in the Peppol BIS Billing 3.0 profile, invoice as well as credit note. That is the first thing to check when choosing or updating your solution.
Further reading
- The UBL 2.1 format explained: the structure of the underlying XML file.
- Understanding the Peppol network in 5 minutes: the four-corner model and access points.
- Peppol in Belgium: the B2B mandate on 1 January 2026: who is in scope and from when.
The reference source is authoritative: the Peppol BIS Billing 3.0 documentation published by OpenPeppol.
What is Peppol BIS Billing 3.0?
Peppol BIS Billing 3.0 is the billing profile used on the Peppol network. It is a Core Invoice Usage Specification (CIUS) of the European standard EN 16931, built on the UBL 2.1 syntax, that covers the invoice and the credit note and adds validation rules specific to Peppol.
What is the difference between Peppol BIS Billing 3.0 and EN 16931?
EN 16931 defines the semantic model of the invoice, meaning the information it must contain. Peppol BIS Billing 3.0 is a profile built on that standard: it adopts the UBL 2.1 syntax, restricts certain options and adds the validation and identification rules needed to travel over the Peppol network.
Which documents does Peppol BIS Billing 3.0 cover?
The profile covers two documents: the invoice (Invoice) and the credit note (CreditNote), both expressed in UBL 2.1. The credit note is used to correct or cancel an invoice that has already been issued.
Does Peppol BIS Billing 3.0 use UBL or CII?
The Peppol BIS Billing 3.0 profile is built on the UBL 2.1 syntax. EN 16931 also allows the UN/CEFACT CII syntax, but the format exchanged in practice on the Peppol network for billing is UBL 2.1.
Do you need to master Peppol BIS Billing 3.0 to invoice?
No. Compliant invoicing software generates the Peppol BIS Billing 3.0 file from the data you enter, validates it and sends it through an access point. You never have to write the XML or learn the profile's rules.
