EN 16931 Standard Germany: Format, Example & Specification

The EN 16931 Standard is the standard for electronic invoices in Europe, issued by CEN in 2017, according to EU Directive 2014/55/EU. The standard contains the definition of the semantic data model containing all mandatory data for an electronic invoice, its structure, and meaning for the automated exchange and processing of electronic invoices in the EU Member States.

Key Takeaways

• It is a standard used within Europe to establish a framework for the invoicing process electronically.
• EN 16931 standard specifies a basic data model that consists of critical information about suppliers, buyers, taxation, and payment terms.
• XML-supported format: UBL 2.1 and UN/CEFACT CII.
• Allows national adaptations like Germany’s XRechnung and ZUGFeRD formats..
• EN 16931 enables automation, faster processing, reduced errors, and easier VAT compliance under the EU’s digital tax reforms.

What is the EN 16931 Standard in Germany?

EN 16931 is like a “universal language” for electronic invoices across Europe. The EN 16931 standard establishes the required and optional elements of an invoice that must be contained in an electronic invoice. These involve supplier and buyer information, invoice number, tax, line items and payment instructions. It aims to ensure that e-invoices are compatible with the EU, so that an invoice issued in one country can be processed in another through the machine without manual modifications.

Imagine you and your supplier speak different languages, your accounting system says “Invoice Date,” theirs says “Billing Date.” EN 16931 steps in and says: “Let’s all agree to call it Invoice Issue Date, and here’s how it must be written and structured in the file.”

So instead of everyone creating their own way of listing invoice details, EN 16931 defines a standardised set of data fields and meanings like the sender’s name, buyer’s VAT number, invoice number, prices, taxes, and payment details so that every computer system across the EU can read and understand it without confusion.

Timeline & Origin of EN 16931

This document did not come out of nowhere; it is a fruit of years of cooperation on EU level aimed at standardisation of the invoicing processes in 27 member states.

• 2014 – European Parliament passed Directive 2014/55/EU, which obliges public authorities in all EU member states to accept electronic invoices. The outcome was Directive 2014/55/EU, requiring the creation of a harmonised e-invoicing format in the European Union.
• 2017 – European Committee for Standardisation (CEN/TC 434) published EN 16931-1 for the data semantic model of electronic invoices. It was combined with the complementary Technical Specification (CEN/TS 16931-2:2017), indicating the potential use of XML-based formats like UN/CEFACT CII and UBL 2.1.
• April 18, 2019 – The central government bodies (e.g., at the federal/national level) were made mandatory for the competence to handle EN 16931 compliant electronic invoices according to Directive 2014/55/E
• April 18, 2020 – The deadline was pushed forward till sub-central governments (i.e., at the state/regional/local level) in those member states
• 27 November 2020 - Germany adopted the mandate requiring the use of XRechnung in B2G relationships with the central government authorities. All invoices of all suppliers which charged the federal authorities over €1,000 should be submitted in the form of structured XML invoices via the ZRE portal. Individual mandates were issued by each Bundesland from 2020 through 2023.
• March 2024 – The Growth Opportunities Act regulated electronic invoicing in B2B relations in Germany. It provided for the following amendment of §14 UStG (VAT Act) obliging the invoice to have an EN 16931 compatible layout. Implementation is planned for 2025 till 2028 years.
• 2025 - Businesses registered under VAT legislation in Germany will be able to send/enrich EN 16931-compliant e-invoices. E-invoicing will be compulsory as from 2027 in case of annual turnover higher than €800,000 for all other business organisations till 2028.

EU & German E-Invoicing Mandate for Structured Data

E-invoicing refers to the digital submission of invoices through a machine-readable format (for example, XML or UBL), thus allowing for the automatic processing of the documents in question. The requirement for machine-readability means that e-invoices must include standardised data elements such as supplier, purchaser, value-added tax information, and totals.

In order to reduce VAT fraud and reduce costs associated with administrative processes, European countries have started using electronic invoices instead of the traditional paper/PDF invoices. In Germany, from January 2025, invoice receive mandate has come into effect, while the send mandate applies in 2027 and 2028 in phases.

Why “Structured Data” Matters

An XML-based electronic invoice contains data stored in specific fields such as vendor VAT number, date, taxable amount, tax rate, and payment terms, among others. Such structured data allows for computer processing, including automated entry into accounting systems, thereby reducing errors that might arise from manual entry.

Interoperability on a Shared Protocol

EN 16931 acts as Europe’s interoperability backbone. It defines a standard semantic model and maps it to universally accepted syntaxes. Since each valid invoice is created using the identical format and lists (currency, VAT classification, country codes), it will be easily understood by all platforms approved by the EU, German ZRE/OZG-RE websites, French Chorus Pro system, or Peppol network.

This shared protocol ensures that:

• An invoice issued in Germany can be processed in France or Italy without format changes.
• Businesses use one data model for all public-sector and, increasingly, B2B invoicing.
• Tax authorities gain a consistent dataset for digital VAT reporting under the EU’s upcoming VAT in the Digital Age (ViDA) reforms.

Features of EN 16931

EN 16931 defines a structured data model and strict validation rules to maintain consistency and accuracy in electronic invoices across the EU.

1. Core Data Model: 

The core invoice data model (EN 16931-1) is set out in the standard and consists of all the necessary components of an invoice, such as the identities of both the seller and the buyer, VAT identification number, invoice number, date, description of line items, quantity, price, tax rates, totals, and payment conditions.

2. Validation Rules: 

The standard enforces mathematical and logical consistency. Totals must equal the sum of line items, tax values must match taxable amounts and rates, and standardised codes must be used for currencies, countries, and tax categories. These checks ensure accuracy and allow automated validation and processing.

3. Syntax Independence with Mappings: 

EN 16931 defines data requirements independently of any specific format. It maps the data model to two recognised XML syntaxes:

• UBL (Universal Business Language) 2.1
• UN/CEFACT Cross Industry Invoice (CII)

Countries and industries can use either syntax while maintaining interoperability. Peppol BIS 3.0 applies UBL, and ZUGFeRD/Factur-X uses a PDF file with embedded CII XML. Both follow EN 16931 rules.

4. Extensibility – CIUS and Extensions:  

The standard allows localised adaptations through Core Invoice Usage Specifications (CIUS). A CIUS refines the core model for specific national or sector needs without breaking compatibility. Germany’s XRechnung is a CIUS that adds routing fields for public sector invoicing. Extensions can include extra optional data agreed upon between trading partners, provided they do not alter mandatory elements.

5. Interoperability and Automation:  

The invoice that is based on EN 16931 can be accepted by any software in the European Union. This provides opportunities for interoperability, automation, and avoids manual data entry. The process of matching, validating, and posting the invoice can be automated, and it saves time and money.

Mandatory Data Fields of EN 16931 Format 

The EN 16931 norm defines mandatory invoice components that ensure completeness and clarity.

Note: Buyer VAT ID is conditional - mandatory for cross-border and reverse-charge transactions. 

EN 16931 Format and Examples in Germany

EN 16931 does not dictate one single file format. Instead, it defines what information an electronic invoice must contain and how that information should be structured. To make this work in practice, the European Commission recognises a few standard file types that can carry this data.

1. UBL (Universal Business Language):

The UBL standard is extensively employed in exchanging business documents electronically, like invoices and purchase orders in Europe. When an invoice, which is composed in the UBL standard, includes all information fields set out in EN 16931 standard, such as the invoice number, invoice date, vendor, customer, price, taxes, etc., then such an invoice may be described as EN 16931-compliant. The bottom line is that a UBL invoice is simply an XML file (.xml/.ubl).

2. UN/CEFACT Cross Industry Invoice (CII):

This is another XML format developed by the United Nations. It contains the same kind of structured information but follows a slightly different layout. In Germany, the ZUGFeRD 2.0 and above format uses this CII XML data, but adds a convenient twist - embedding the XML file inside a regular PDF. This means a person can open and view the invoice as a normal PDF, while accounting software can read the structured XML data hidden inside it.

Example

Think of receiving an invoice from your vendor. You can choose either of the following:

• You may view it just like any other PDF file in which you will be able to see details such as vendor name, invoice date, invoice total, etc., or
• You can use your accounting software to automatically pull out the XML data contained within that particular document.

The PDF and XML both contain the exact same details.

How EN 16931 is Implemented in Germany

The standard for e-invoicing in Germany is the EN 16931 standard. Germany has introduced two types of formats, XRechnung and ZUGFeRD, which are based on the models defined in EN 16931.

B2G Invoicing (XRechnung): Since 2020, all suppliers who send invoices to any body of the German government will have to use the XRechnung invoicing.

From 1 January 2025, all businesses registered for VAT in Germany will have to accept e-invoices in compliance with EN 16931 from other VAT-registered businesses. Starting from 2027, structured e-invoicing will be mandatory for enterprises with turnover exceeding €800,000, and from 2028 for all other enterprises. 

All invoices issued between German businesses will need to be in a form that follows the standards of the EN 16931, in either XML (XRechnung) or PDF+XML (ZUGFeRD). Only PDFs and paper-based invoices won’t be treated as valid invoices, unless under some special circumstances.  

Permitted Formats: Either the invoices may be issued in compliance with the EN 16931 data model, or else another structure agreed between the parties should be used, which can be mapped to EN 16931.

  Infrastructure: Germany supports EN 16931 implementation through:

• ZRE and OZG-RE portals for submitting government invoices
• Peppol network access, enabling standardised cross-border e-invoicing

XRechnung vs. EN 16931

EN 16931 is the documentation of electronic invoicing in the EU, whereas XRechnung is a national implementation of this documentation in Germany. The EN 16931 norm establishes the general rules and XRechnung uses it with national adjustments in order to comply with the needs of the German government and tax authority.

In Layman's terms

Think of EN 16931 as a recipe book for making a standard European invoice. It lists the ingredients (data fields like seller name, invoice date, VAT, and totals) and the steps (how the data should be structured) so that anyone in Europe can make a compliant “invoice dish.”

Now, XRechnung is like Germany’s local version of that recipe. The process uses the same components as in EN 16931, but it also includes some additional components and processes as mandated by the German government, including Leitweg-ID (routing ID of public offices).

So if EN 16931 says, “Every invoice must have flour, sugar, and butter,” XRechnung says, “Yes, and in Germany, you must also add a pinch of salt and bake it at our local temperature.”

In other words:

• EN 16931 = The European e-invoice recipe everyone must follow.
• XRechnung = The German version of that recipe, customised to meet local rules.

How Does EN 16931 Relate to Peppol? 

Peppol is a network and delivery framework - not a data standard. EN 16931 is a data standard - not a delivery network. The two are complementary and work together in the following way:

EN 16931 defines what the invoice contains. Peppol defines how it is delivered.

When a business sends an invoice over the Peppol network, the invoice content must comply with Peppol BIS Billing 3.0, which is a CIUS (Core Invoice Usage Specification) built directly on top of EN 16931. This means every Peppol BIS 3.0 invoice is automatically EN 16931-compliant.

Here is how the relationship works in practice:

In Germany specifically:

• Businesses can send XRechnung invoices via the Peppol network to public authorities, as an alternative to the ZRE/OZG-RE portal.
• Peppol is increasingly being used for B2B e-invoicing as Germany rolls out its 2025–2028 mandate.
• Both XRechnung and Peppol BIS 3.0 are EN 16931-compliant, meaning a business using either format meets the German legal requirement.

Who Must Comply with EN 16931 Standard in Germany?

E-invoicing regulations are being introduced in Germany according to the EN 16931 standard for achieving standardised invoicing. The implementation of these regulations varies based on whether the invoices are made to a public body or in certain transactions.

1. Public Sector Suppliers (B2G):  

Suppliers invoicing federal or state authorities must send EN 16931-compliant invoices, mainly in XRechnung format. This has been mandatory since November 2020 for all invoices, submitted through the ZRE or OZG-RE portals.

2. Private Businesses (B2B): 

• From 1 January 2025, all VAT-registered businesses must be able to receive e-invoices in EN 16931 format.
• From 1 January 2027, companies with a turnover above €800,000 must issue only structured e-invoices.
• From 1 January 2028, the rule applies to all businesses, regardless of size.

3. Transitional Arrangements: 

Until 31 December 2026: All businesses may still issue paper or PDF invoices with the recipient's consent. From 1 January 2027: Only businesses with annual turnover below €800,000 may continue to use paper/PDF invoices (with consent), until 31 December 2027. From 1 January 2028: Structured e-invoices are mandatory for all businesses, with no transitional exceptions. 

4. Exemptions:  

Invoices under €250, Small businesses qualifying under §19 UStG (turnover ≤ €25,000 in the previous year and ≤ €100,000 in the current year) are exempt from issuing e-invoices, but must still be able to receive them from 2025, transport tickets, parking receipts, and certain B2C or real-estate-related services are exempt.

Benefits of Adopting the EN 16931 Standard

The application of the EN 16931 standard will enable the companies in Germany to adapt to more advanced practices in invoice processing as well as be compliant with legal standards.

• Regulatory Compliance: All invoices will comply with EU Directive 2014/55/EU and German e-invoicing legislation for both B2G and B2B communications to avoid non-compliance issues.
• Operational Efficiency: Streamlines invoice generation and processing, saves time on manual labour, and helps save money through reduced paperwork, printing, and mailing costs.
• Faster Payment Processing: Machine-readable invoices lead to faster validation and payments, resulting in improved cash flow and lower receivables.
• VAT Reporting: Makes invoice data available for easy validation and detection of any mistakes; makes future compliance with real-time reporting systems possible.
• European Interoperability: Allows seamless transmission of electronic invoices between different systems and jurisdictions using formats such as XRechnung, ZUGFeRD, and Peppol BIS 3.0.

Conclusion

The European electronic invoicing standard is EN 16931. Businesses can be compliant, efficient and interoperable by using the formats like EN 16931 XRechnung, ZUGFeRD or Peppol BIS. With the B2B e-invoicing requirement coming into effect in 2025 in Germany, EN 16931-compliant e-invoicing is no longer optional for businesses operating in Germany. Structured formats XRechnung, ZUGFeRD, or Peppol BIS 3.0 are now a legal requirement, with full compliance expected across all domestic B2B transactions by 2028, but a necessity to ensure digital compliance in future.