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.

EN 16931 vs Peppol BIS: Content Standard vs Network Specification

Side-by-Side Comparison

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

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 3.0

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.

Key Differences Explained

Content standard vs. network specification

EN 16931 defines the language — what words (data fields) exist and what they mean. Peppol BIS defines how to use that language on a specific network — which words are mandatory, what additional context is needed, and how the message gets delivered. Think of EN 16931 as the dictionary and Peppol BIS as the postal service’s addressing rules.

Optional vs. mandatory fields

EN 16931 marks many fields as optional. Peppol BIS makes some of those mandatory. The buyer reference (BT-10) is optional in EN 16931 but required by Peppol rule PEPPOL-EN16931-R010. The business process identifier is optional in EN 16931 but required by PEPPOL-EN16931-R001. This is the most common source of Peppol rejection errors.

Validation depth

EN 16931 has 65 base business rules. Peppol adds 80+ additional rules. A valid EN 16931 invoice might still fail Peppol validation because of these extra requirements. This is why validating against only EN 16931 isn’t enough when sending via Peppol.

When to Use 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

When to Use 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

Can You Use Both?

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.