EN 16931 Explained: What the EU E-Invoicing Standard Means for Your Business

EN 16931 is the European standard for electronic invoicing. Its full title is "Electronic invoicing — Semantic data model of the core elements of an electronic invoice." It was developed by the European Committee for Standardization (CEN) and published in 2017.

Despite the technical name, the concept is straightforward: EN 16931 defines what information an electronic invoice must contain and how that information should be structured so any system can read and process it. It is a semantic data model — a specification of fields, their meanings, and their relationships — not a file format itself.

Think of it as a blueprint for what a machine-readable invoice looks like. It specifies that an invoice must include fields like seller name, buyer name, invoice date, line items with descriptions and amounts, VAT information, and payment terms. It defines how these fields relate to each other (e.g., line amounts must sum to the invoice total, VAT must be broken down by rate).

The standard is syntax-independent: it defines what information exists, not how it is encoded in a file. Two specific file formats (UBL and CII) are approved for encoding EN 16931 invoices, but the semantic model is the authority.

Before EN 16931, electronic invoicing in Europe was fragmented. Different countries used different formats, different standards, and different networks. A French company's e-invoicing system could not necessarily read a German company's electronic invoices. This created barriers to cross-border trade and forced businesses to maintain multiple formats or rely on intermediaries.

The European Commission addressed this through Directive 2014/55/EU, which required all public authorities in EU member states to accept electronic invoices in a common format for public procurement (business-to-government, or B2G). CEN was tasked with creating this common standard, resulting in EN 16931.

The directive's B2G mandate became effective in April 2019 for central government contracting authorities. Sub-central contracting authorities had until April 2020 to comply. Since then, any business supplying goods or services to EU public sector entities must be capable of issuing invoices that comply with EN 16931 if the public buyer requires it.

The standard was originally focused on B2G, but its scope is expanding. An updated version, EN 16931-1:2025, has been approved by CEN with specific adaptations for B2B transactions. This update supports the EU's VAT in the Digital Age (ViDA) initiative, which will make structured e-invoicing mandatory for all cross-border intra-EU B2B transactions by July 2030.

EN 16931 defines what an invoice must contain. UBL and CII define how to write it in a file.

UBL (Universal Business Language) is an OASIS standard that expresses business documents in XML. The Peppol BIS Billing specification uses UBL as its primary syntax, making UBL the dominant format for cross-border e-invoicing in Europe.

CII (Cross-Industry Invoice) is a UN/CEFACT standard, also XML-based. CII is used in the French Factur-X and German ZUGFeRD hybrid formats, which embed structured invoice data inside a PDF.

Both syntaxes are fully approved under EN 16931 and are considered equally compliant.

The EN 16931 core model is designed to be universal, but individual countries and sectors may need additional rules. CIUS (Core Invoice Usage Specification) is the mechanism for this.

A CIUS narrows the EN 16931 standard for a specific context — it can make optional fields mandatory, restrict allowed values, or add validation rules. A CIUS cannot contradict the core standard. Any system that can process a full EN 16931 CORE invoice can also process any compliant CIUS (though not necessarily the other way around).

EN 16931 defines the content standard. Peppol defines the delivery network.

Peppol (Pan-European Public Procurement Online) is an international framework for exchanging electronic business documents. It consists of a network (connecting access points that route documents between sender and receiver), a set of document specifications (based on EN 16931), and a governance model (managed by OpenPeppol).

When you send an invoice via Peppol, you are sending an EN 16931-compliant invoice (specifically, Peppol BIS Billing 3.0, which is a CIUS of EN 16931) through the Peppol network. The network ensures delivery; the standard ensures the content is machine-readable.

Peppol is mandatory for B2G e-invoicing in several countries (including Norway, Belgium, and the Netherlands for certain transactions) and is becoming the default delivery channel for cross-border e-invoicing in Europe. It is also increasingly adopted for B2B transactions, especially in the Nordics and Benelux.

For a small service business, Peppol matters when your client requires electronic invoice delivery via the Peppol network. This is most common with large corporate buyers and public sector entities.

If you are a consultant, designer, developer, or other service professional, here is the practical reality:

Today, your clients most likely accept PDF invoices. EN 16931 does not require you to stop sending PDFs. What it requires (when applicable) is that the invoice data exists in a machine-readable structured format.

Hybrid formats like Factur-X and ZUGFeRD bridge this gap — they embed structured EN 16931 data inside a normal-looking PDF. The recipient sees a PDF they can read; their accounting system extracts the structured data automatically. This is increasingly the practical standard for European e-invoicing.

The most important thing you can do today is ensure your invoice data is clean and complete. EN 16931 compliance is easy when your invoices already have proper seller/buyer details, validated VAT numbers, correct tax breakdowns per line, and accurate totals. It is painful when your data is scattered across notes fields, VAT numbers are unvalidated, and line items are vague.

Software that captures clean, structured invoice data from day one — with proper VAT handling, validated identifiers, and consistent formatting — makes the transition to EN 16931 compliance straightforward when required.

VAT in the Digital Age (ViDA) is an EU initiative that will reshape invoicing requirements for all businesses operating within the EU.

The most significant change for invoicing: from 1 July 2030, all cross-border intra-EU B2B transactions will require structured electronic invoices compliant with EN 16931 (or the updated version current at that time). This replaces the current system where businesses can choose their own invoice format.

ViDA also introduces Digital Reporting Requirements (DRR): businesses will need to report transaction data to their national tax authorities in near-real-time, using structured invoice data. This is intended to close the VAT gap by giving tax authorities visibility into cross-border transactions as they happen, rather than relying on periodic VAT returns and EC Sales Lists.

The updated standard, EN 16931-1:2025, has been approved by CEN specifically to support ViDA's B2B requirements. It adds data elements needed for B2B contexts that were not necessary in the original B2G-focused standard.

What this means practically: by 2030, every EU service business that invoices clients in other EU countries for cross-border B2B supplies will need to issue EN 16931-compliant structured invoices. Starting with clean, structured invoice data today means you will not face a painful migration later.

You do not need to implement EN 16931 tomorrow if your clients are not requiring it yet. But you can prepare now so the transition is seamless when it comes.

Ensure your invoices contain all the data EN 16931 expects: seller and buyer details with VAT numbers in proper fields (not in notes), line items with individual descriptions and amounts, VAT broken down by rate per line, and totals that add up correctly.

Use invoicing software that stores this data in structured fields rather than free-text. This is the difference between a tool that helps you create a nice-looking PDF and a tool that maintains structured invoice data that can be expressed in any format — including EN 16931.

Validate your clients' VAT numbers via VIES and keep the results. EN 16931 requires buyer VAT identifiers in specific fields; having validated, correctly formatted numbers makes this automatic.

If any of your clients already require Peppol or structured invoices, start the conversation with them about their requirements now. Understanding their specific CIUS or delivery channel expectations early prevents surprises later.