Compare · EN 16931 vs Peppol BIS 3.0
EN 16931 vs Peppol: The Standard vs the Network Specification
EN 16931 is the European content standard — it defines what data an e-invoice must contain. Peppol BIS 3.0 is a CIUS that adds rules for how invoices are structured and delivered on the Peppol network. They’re layers, not alternatives: every Peppol invoice is EN 16931 compliant, but not every EN 16931 invoice is Peppol-ready.
TL;DR
- Use EN 16931 if: EN 16931 is the baseline. Use it when discussing general EU e-invoicing compliance — all country formats (XRechnung, Factur-X, Peppol BIS) build on it.
- Use Peppol BIS 3.0 if: Peppol BIS 3.0 is the network-ready specification. Use it when sending invoices via the Peppol network — it adds the rules needed for Peppol delivery.
- Use both if: You always use both. Peppol BIS 3.0 is a superset of EN 16931. When you create a Peppol invoice, it automatically meets EN 16931 requirements plus additional Peppol rules.
| Feature | EN 16931 | Peppol BIS 3.0 |
|---|---|---|
| What it is | European content standard (CEN) | Network specification (CIUS of EN 16931) |
| Defines | ~180 business terms (BT-1 through BT-180+) | EN 16931 terms + 80 Peppol-specific rules |
| Syntax | Syntax-agnostic (UBL 2.1 or CII D16B) | UBL 2.1 (primary) or CII |
| Transport | No transport defined | AS4 via Peppol Access Points |
| Validation rules | BR-01 through BR-65 (base rules) | BR-* + PEPPOL-EN16931-R001 through R080 |
| Scope | All EU e-invoicing | 39+ Peppol member countries |
| Buyer reference (BT-10) | Optional | Required (PEPPOL-EN16931-R010) |
| Business process ID | Optional | Required (PEPPOL-EN16931-R001) |
| Country CIUS | Allows country-specific extensions | Allows country CIUS on top of Peppol rules |
| Who maintains it | CEN (European Committee for Standardization) | OpenPeppol |
EN 16931 is the European standard that defines the semantic data model for electronic invoices. Published by CEN and mandated by EU Directive 2014/55/EU, it specifies ~180 business terms that an e-invoice can contain: invoice number, issue date, seller/buyer information, line items, tax breakdowns, payment details, and more.
EN 16931 is format-agnostic — it defines what data must exist, not how it’s encoded. The standard supports two XML syntaxes: UBL 2.1 and CII D16B. Country-specific formats (XRechnung, Factur-X, etc.) build on EN 16931 by adding national rules.
Peppol BIS Billing 3.0 is a CIUS (Core Invoice Usage Specification) of EN 16931. It takes the European base standard and adds Peppol-specific rules needed for network delivery: a mandatory buyer reference (BT-10), business process identifier, currency constraints, and additional data validation.
Peppol BIS is primarily UBL 2.1 based. It’s maintained by OpenPeppol and updated regularly. The current specification adds 80+ rules on top of EN 16931’s base rules, making it a strict superset of the standard.
Content standard vs. network specification
Optional vs. mandatory fields
Validation depth
EN 16931
- Discussing general EU e-invoicing compliance requirements
- Building a format-agnostic validation layer
- Working with non-Peppol formats (ZUGFeRD, Factur-X, standalone CII)
- Understanding the base rules that all EU e-invoices must follow
Peppol BIS 3.0
- Sending invoices via the Peppol network
- Belgian B2B invoicing (Peppol mandatory since January 2026)
- Cross-border EU e-invoicing where both parties are on Peppol
- Building Peppol Access Point integrations
You always use both — they’re layers. A Peppol BIS 3.0 invoice passes EN 16931 base rules (it must, by definition) plus the additional Peppol-specific rules. When you validate a Peppol invoice, you check EN 16931 rules first, then Peppol rules on top. Our validator runs all layers automatically.
EN 16931 base rules, Peppol rules, and country CIUS — checked in one pass.
Checking is free. The first verified download every 30 days is free. After that €1.90 per invoice, or €9 a month for all of them.
Frequently Asked Questions
- Is every Peppol invoice EN 16931 compliant?
- Yes. Peppol BIS 3.0 is a CIUS (usage specification) of EN 16931. By definition, a valid Peppol invoice must pass all EN 16931 base rules. Peppol adds rules on top — it never removes or contradicts EN 16931 requirements.
- Is every EN 16931 invoice valid on Peppol?
- No. An EN 16931-compliant invoice might lack fields that Peppol requires. The most common gap: buyer reference (BT-10) is optional in EN 16931 but mandatory for Peppol. You need to pass both rule sets.
- What are the extra Peppol rules?
- Peppol adds ~80 rules (PEPPOL-EN16931-R001 through R080) covering mandatory buyer reference, business process identifier, currency constraints, tax category requirements, and network-specific data formatting.
- Which should I validate against?
- Both. If you’re sending via Peppol, validate against EN 16931 base rules AND Peppol rules AND any country CIUS rules that apply. Our validator handles all layers in a single pass.
- Can I use CII syntax on Peppol?
- Technically yes — Peppol supports CII D16B. In practice, most Peppol implementations use UBL 2.1 as the default syntax. Check with your Access Point whether they support CII delivery.