EN 16931, UBL, and the structured invoice
EN 16931 defines what a European e-invoice means semantically. UBL is a common syntax. Peppol BIS Billing ties them together for network exchange.
Updated
Three layers that are often confused
When people say “structured e-invoice”, they usually mix three related ideas:
- Semantics (EN 16931) — which business information an invoice must carry (seller, buyer, lines, VAT, totals, payment means, etc.)
- Syntax (often UBL) — how that information is encoded in XML
- Transport (Peppol) — how the file is addressed and delivered to the counterparty
All three matter. A valid XML file that never reaches the buyer, or a Peppol message that fails EN 16931 validation, is not a working e-invoice process.
EN 16931 in plain language
EN 16931 is the European standard that defines the core elements of an electronic invoice. It answers: what does “invoice” mean as data, so that software in different countries can interpret the same document consistently?
It is deliberately syntax-neutral at the semantic level: the standard describes the information model. In practice, Europe commonly implements it with UBL or UN/CEFACT CII. Peppol Billing in Belgium uses the UBL path.
UBL (Universal Business Language)
UBL is an XML vocabulary for business documents. A UBL invoice is a tree of elements: AccountingSupplierParty, InvoiceLine, TaxTotal, and so on. Accounting platforms map these fields into their ledgers.
Because UBL is verbose and strict, validation tools can reject invoices that miss mandatory fields or break cardinality rules. That strictness is a feature: it prevents silent data loss between systems.
Peppol BIS Billing
Peppol BIS Billing 3.0 is a Peppol Business Interoperability Specification. It profiles EN 16931 for use on the Peppol network: which document type identifiers to use, which code lists apply, and how implementations should behave.
In Belgium’s B2B mandate context, “send a Peppol invoice” almost always means: produce an EN 16931-compliant UBL invoice and submit it through a Peppol Access Point using the BIS Billing profile.
Structured data versus human layout
A structured invoice is optimised for machines. Many products still generate a PDF presentation for humans. Both can coexist, but the structured file is the authoritative e-invoice for automated processing and mandate compliance.
Practical checklist for implementers
- Populate mandatory EN 16931 / BIS fields (VAT category, identifiers, totals consistency)
- Use correct party identifiers (Belgian enterprise numbers where required)
- Validate before send
- Archive the XML (or equivalent structured original), not only the PDF