EN 16931, CIUS and PINT

EN 16931 is the semantic foundation of European e-invoicing. This article explains the standard, including the 2026 revision, CIUS variants and the international PINT profile.

EN 16931 is the semantic foundation of e-invoicing in Europe. The standard defines what information an e-invoice must contain, regardless of technical format. Country-specific implementations (CIUS) refine this model; PINT extends the scope beyond Europe.

What is EN 16931?

EN 16931 is the European standard for electronic invoicing, developed by CEN (the European standardisation body) on behalf of the European Commission. The standard is legally anchored in EU Directive 2014/55/EU and describes the semantic model: which data an e-invoice must or may contain, such as supplier, buyer, invoice number, invoice date, amounts and VAT rates.

It is exclusively about content, not technical format. Every e-invoice considered valid in Europe must comply with this model.

EN 16931-1:2026 -- the current version

On 13 March 2026, CEN formally approved the revised version EN 16931-1:2026. This version replaces EN 16931-1:2017+A1:2019 and is not backward-compatible.

Instances complying with the new standard use urn:cen.eu:en16931:2026 in BT-24 (Specification identifier). The old identifier urn:cen.eu:en16931:2017 remains valid only for instances conforming to the previous version.

The revision broadens the scope from a primarily B2G-focused standard to full B2B support and aligns with the ViDA package for automated VAT reporting.

New Business Groups and Business Terms
CodeNamePurposeBG-33PAYMENT TERMS (0..n)Multiple payment terms for partial paymentsBG-34CHARGES ON BEHALF OF A THIRD PARTY (0..n)Amounts payable to third parties alongside the invoice (BT-179 amount, BT-180 specification)BG-35EARLY PAYMENT DISCOUNT (0..n)Early payment discount with end date (BT-170), percentage (BT-171) and/or amount (BT-172)BG-36LATE PAYMENT PENALTY (0..n)Late payment penalty with start date (BT-181), annual rate (BT-182) and/or fixed amount (BT-183)BG-37INVOICE LINE DELIVERY INFORMATION (0..1)Delivery information at invoice line levelBG-38INVOICE LINE DELIVER TO ADDRESS (0..1)Delivery address per invoice lineBG-39LINE-LEVEL PRECEDING INVOICE REFERENCE (0..n)Reference per invoice line to preceding invoices

New Business Terms include: BT-166 (Invoice issue time), BT-167 (VAT accounting currency exchange rate), BT-197/198 (Delivery note reference at document and line level), BT-188/132 (Invoice line purchase and sales order references), BT-211/212 (Item attribute code and value with unit of measure, including CO2 reporting), and BT-215/216 (payment service provider identifiers).

Changed cardinality and mandatory scheme identifiers
  • BT-10 Buyer reference: from 1..1 to 0..n, with optional scheme identifier (UNTDID 1153).
  • BT-29 Seller identifier and BT-46 Buyer identifier: from 1..n to 0..n, with mandatory (1..1) scheme identifier from ISO/IEC 6523.
  • BT-60 Payee identifier also receives a mandatory scheme identifier.
  • New business rules BR-69 through BR-76 mandate scheme identifiers and regulate payment account verification for intra-community transactions.
Multiple orders and deliveries per invoice

The standard explicitly confirms that an invoice may reference multiple purchase orders and multiple deliveries, both at document level and at line level. Document-level and line-level identifiers are mutually exclusive (BR-CO-28 through BR-CO-46).

Permitted attachment MIME types (BT-125)

EN 16931-1:2026 restricts BT-125 (Attached document) to: application/pdf, image/png, image/jpeg, text/csv, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet (XLSX), application/vnd.oasis.opendocument.spreadsheet (ODS) and application/xml.

Note -- future, not currently valid for BIS Billing V3. application/xml as an attachment MIME type belongs to EN 16931-1:2026 and a future Peppol version (possibly BIS Billing 4.0). The current Peppol BIS Billing 3.0 production validation (BR-CL-24) does not allow application/xml; see the article on BIS Billing V3.

Removed business rules

Annex A.4 removes, among others, BR-CO-17 (simple VAT calculation formula), BR-S-10/Z-10/IG-10/IP-10 (prohibited exemption reason for certain VAT rates) and BR-O-2 through BR-O-14 (old restrictions around "Not subject to VAT"). Existing validators must disable or replace these rules.

Impact on Peppol and CIUS variants

Peppol BIS Billing V3 will be updated to support the new standard; a new Peppol version is expected in 2026-2027, possibly as BIS Billing 4.0. Until then, the existing restriction of one OrderReference per invoice applies to BIS instances. National CIUS variants (NLCIUS, XRechnung, ebInterface) follow at their own pace; NLCIUS is coordinated for the Netherlands via NEN.

Syntax bindings

EN 16931 has two officially recognised syntax bindings:

SyntaxFull nameOriginUsageUBL 2.1Universal Business LanguageOASIS (ISO/IEC 19845)Most used in Peppol and EuropeCIICross-Industry InvoiceUN/CEFACTBasis for Factur-X/ZUGFeRD, used in Germany and France

Both syntaxes express the same semantic information in a different XML structure.

CIUS: country-specific implementations

Countries may refine the European model via a CIUS (Core Invoice Usage Specification). A CIUS adds country-specific rules but may never conflict with the underlying EN 16931 model. An invoice that complies with a CIUS automatically complies with EN 16931.

CountryCIUSNotesNetherlandsNLCIUSG-account extension, OIN requirement for government, KvK identifierGermanyXRechnungLeitweg-ID for government recipients, UBL and CIIFranceFrance CIUSSIREN identifier, multiple variantsSwedenSvefakturaBased on Peppol BISAustriaebInterfaceOwn XML schema alongside UBL
PINT: international extension

PINT (Peppol International Invoice) extends the reach of EN 16931 beyond Europe. It is a separate profile based on EN 16931, with region-specific variants:

VariantRegionPINT EUEuropePINT A-NZAustralia and New ZealandPINT JapanJapanPINT MalaysiaMalaysiaPINT SingaporeSingaporePINT AEUnited Arab EmiratesPINT-SKSlovakiaPINT OMOman

PINT is the successor to BIS Billing for international Peppol invoicing. The eConnect PSB supports PINT Singapore (PINT-SG) and PINT-SK as production-ready variants. The other PINT variants are on the roadmap. See the article on PINT for the current status per region.

The standards hierarchy
EN 16931  (semantic model)
    |
    +-- Syntax bindings
    |     +-- UBL 2.1
    |     +-- CII (UN/CEFACT)
    |
    +-- Profiles
    |     +-- Peppol BIS Billing 3.0
    |     +-- PINT (international)
    |           +-- PINT EU
    |           +-- PINT A-NZ
    |           +-- ...
    |
    +-- CIUS (country-specific)
          +-- NLCIUS (Netherlands)
          +-- XRechnung (Germany)
          +-- Svefaktura (Sweden)
          +-- ...

The EN 16931 series includes, alongside Part 1, CEN/TS 16931-2 (syntax list), CEN/TS 16931-3-1 through -3-4 (syntax bindings UBL 2.1 and UN/CEFACT CII), CEN/TR 16931-4 (transmission interoperability) and CEN/TS 16931-7 (CIUS development). New in 2026: CEN/TS 16931-8 (e-receipt and simplified e-invoice), CEN/TR 16931-9 (VAT reporting and gap analysis) and FprCEN/TR 16931-10 (extension to B2B).

Frequently asked questions
What changes in practice because of EN 16931-1:2026?

The new standard adds support for multiple payment terms (BG-33), early payment discounts (BG-35) and delivery information at line level (BG-37). Validators must be updated to remove deprecated business rules. For daily use, little changes as long as you work with BIS Billing V3: that profile will only be updated to the new standard when Peppol publishes a new version (possibly BIS Billing 4.0), expected in 2026-2027.

Do I need to adapt my invoices for EN 16931-1:2026?

Not immediately. BIS Billing V3 is currently still based on EN 16931-1:2017. Once Peppol publishes an updated version of BIS, eConnect will communicate the necessary steps. For invoices sent directly via the API: check whether your validator has been updated for the removed business rules.

What is the difference between EN 16931 and NLCIUS?

EN 16931 is the European semantic model describing what data an invoice must contain. NLCIUS is a Dutch refinement (CIUS) that adds supplementary requirements, such as the OIN number for government invoices and the G-account extension. An invoice that complies with NLCIUS automatically complies with EN 16931, but not the other way around.

Can we as a recipient already process invoices based on EN 16931-1:2026?

The eConnect PSB processes invoices based on the Peppol validation rules in effect at that time. Invoices that specify urn:cen.eu:en16931:2026 as the specification identifier (BT-24) but fall within the current BIS Billing V3 profile are processed correctly. Entirely new BG/BT fields from the 2026 revision will be supported once the updated Peppol profile is available.