EN 16931 Explained

The Standard for Electronic Invoicing in Europe

EN 16931 at a Glance

With the introduction of mandatory electronic invoicing in Germany and numerous other European countries, one term has become increasingly important: EN 16931. This European standard provides the technical and semantic foundation for electronic invoices, ensuring that invoice data can be created, exchanged, and processed consistently across Europe.

Many organisations first encounter EN 16931 in connection with formats such as XRechnung, ZUGFeRD, or PEPPOL. It is often assumed that EN 16931 is itself an invoice format. In reality, however, EN 16931 does not define a file format. Instead, it specifies which information an electronic invoice must contain and how that information must be structured.

As a result, the standard plays a key role in the digitalisation of finance processes, compliance with legal requirements, and the implementation of future EU initiatives such as VAT in the Digital Age (ViDA).

In this guide, you will learn:

• what EN 16931 is and why it matters for businesses
• which requirements EN 16931 defines for electronic invoices
• why EN 16931 serves as the foundation for XRechnung and ZUGFeRD
• which mandatory information an electronic invoice must contain
• how EN 16931 can be implemented in SAP and other ERP systems
• which benefits businesses gain from standardised electronic invoices
• which common implementation pitfalls should be avoided

---

Table of Contents

---

Fundamentals – What is EN 16931?

EN 16931 is the European standard for electronic invoicing. It defines a common semantic data model for invoices, ensuring that electronic invoices can be processed consistently regardless of the country, industry, or ERP system involved.

The standard was developed by the European Committee for Standardization (CEN) on behalf of the European Commission and serves as the foundation of EU Directive 2014/55/EU on electronic invoicing in public procurement.

It is important to distinguish between a standard and an invoice format.

EN 16931 is not an invoice format. Instead, it is a business specification that defines which information an electronic invoice must contain and how that information should be structured.

Based on this standard, several technical formats have been developed, including:

• XRechnung
• ZUGFeRD (from the EN 16931 / Factur-X profile onwards)
• PEPPOL BIS Billing
• Other national XML-based invoice formats

As a result, EN 16931 provides the common foundation for virtually all modern electronic invoice formats used across Europe.

---

Why Was EN 16931 Introduced?

Before EN 16931 was introduced, Europe used numerous different invoice formats and national specifications.

For businesses, this often resulted in:

• inconsistent data structures
• different technical interfaces
• high integration effort
• limited automation
• complex cross-border invoicing processes

With EN 16931, the European Union aims to harmonise electronic invoicing across Europe.

The objective is to enable businesses to create, send, receive, and process electronic invoices in a consistent manner, regardless of the country involved.

At the same time, the standard supports:

• higher data quality
• fewer manual process interruptions
• more efficient finance processes
• improved interoperability
• greater digitalisation of invoicing

Together with national e-invoicing mandates, EN 16931 therefore represents a key building block of Europe’s digital transformation strategy.

---

Legal Framework of EN 16931

The importance of EN 16931 is derived directly from both European and national legislation.

The key legal foundations include:

• EU Directive 2014/55/EU on electronic invoicing in public procurement
• European Standard EN 16931
• National e-invoicing regulations implemented by individual Member States
• Germany’s mandatory B2B electronic invoicing requirements
• Future requirements arising from VAT in the Digital Age (ViDA)

The EU Directive requires public authorities to accept electronic invoices provided they comply with the European standard.

Many Member States have since extended these requirements to additional sectors or, like Germany, are gradually introducing mandatory electronic invoicing for B2B transactions.

As a result, EN 16931 is increasingly becoming the common standard for electronic invoices throughout Europe.

---

What Requirements Does EN 16931 Define?

The standard defines the business structure of an electronic invoice.

Its primary focus is on standardised business information that can be processed automatically.

This includes, among other things:

• Supplier information
• Buyer information
• Invoice number
• Invoice date
• Delivery or service period
• Tax information
• Payment terms
• Currency information
• Invoice line items
• Invoice totals

This information is organised within a clearly defined structure, enabling ERP systems to interpret and process invoice data automatically.

As a result, invoices can be validated, posted, and archived without manual data entry.

For organisations handling high invoice volumes, this creates significant efficiency gains.

---

Which Mandatory Information Does EN 16931 Require?

An electronic invoice compliant with EN 16931 must contain a comprehensive set of mandatory business information.

This includes:

Supplier Information

The invoice must clearly identify the supplier.

Typical information includes:

• Company name
• Address
• VAT Identification Number (where applicable)

---

Buyer Information

The recipient of the goods or services must also be clearly identifiable.

---

Invoice Identification

Mandatory information includes:

• Invoice number
• Invoice date
• Delivery or service date

---

Tax Information

The standard defines detailed requirements covering:

• VAT amounts
• VAT rates
• VAT exemptions
• Tax categories

---

Payment Information

Payment terms and payment methods must also be included.

This standardised structure enables automated validation of invoice data and significantly reduces errors throughout the invoicing process.

Modern ERP solutions and SAP systems particularly benefit from this clearly defined data model, enabling invoices to be processed efficiently without manual intervention.

---

EN 16931 XML – What Role Does XML Play?

When discussing EN 16931, the term XML inevitably comes up.

XML (Extensible Markup Language) is the technical format used to exchange structured invoice data.

While EN 16931 defines the business content and semantic structure of an electronic invoice, XML provides the technical syntax that enables systems to exchange and process this information automatically.

Several XML-based invoice formats have been developed based on EN 16931, including:

• XRechnung
• PEPPOL BIS Billing
• Factur-X / ZUGFeRD (from the EN 16931 profile onwards)

This distinction is particularly important:

• EN 16931 defines what information an invoice must contain.
• XML defines how this information is technically represented.

Together, they enable invoices to be validated, exchanged, and processed automatically across different ERP systems and countries.

---

EN 16931 Example – What Does an EN 16931-Compliant Invoice Look Like?

Many organisations search for an EN 16931 example because they want to understand how the standard is applied in practice.

However, an EN 16931-compliant invoice is usually not intended for human reading. It consists primarily of structured XML data that can be interpreted by ERP systems.

A typical invoice includes information such as:

• Supplier
• Buyer
• Invoice number
• Invoice date
• VAT information
• Invoice line items
• Payment terms
• Total amount
• Currency

The XML file follows a clearly defined data model that allows systems to process invoice information consistently.

For hybrid invoice formats such as ZUGFeRD, the XML data is embedded within a PDF document, allowing both machine processing and human readability.

---

EN 16931, XRechnung and ZUGFeRD – What Are the Differences?

One of the most common questions is how EN 16931, XRechnung, and ZUGFeRD differ.

Although the terms are often used interchangeably, they describe different concepts.

EN 16931

EN 16931 is the European semantic standard that defines the business data model for electronic invoices.

---

XRechnung

XRechnung is a German XML invoice format that fully complies with EN 16931.

It is primarily used in the German public sector and increasingly in B2B invoicing.

---

ZUGFeRD

ZUGFeRD combines:

• a human-readable PDF document
• embedded XML invoice data

From version 2.x onwards, the EN 16931 profile of ZUGFeRD is fully compliant with the European standard.

---

PEPPOL BIS Billing

PEPPOL BIS Billing is another XML-based invoice specification that complies with EN 16931 and is widely used for international electronic invoicing.

---

As a result, EN 16931 serves as the common foundation, while XRechnung, ZUGFeRD, and PEPPOL BIS represent different technical implementations of the standard.

---

Implementing EN 16931 in SAP and ERP Systems

Implementing EN 16931 requires more than simply generating an XML file.

Businesses must ensure that their ERP systems are capable of creating, receiving, validating, and processing structured invoice data in accordance with the standard.

In SAP environments, this typically involves:

• SAP S/4HANA or SAP ERP
• SAP Document and Reporting Compliance (SAP DRC)
• SAP Integration Suite or middleware solutions
• Invoice management and workflow solutions
• Archiving systems
• Validation mechanisms

The objective is to establish a fully integrated, end-to-end invoicing process that supports both compliance and automation.

👉 Learn more about SAP e-invoicing

---

The Role of SAP Document and Reporting Compliance (SAP DRC)

For many organisations, SAP Document and Reporting Compliance (SAP DRC) plays a central role in implementing EN 16931-compliant invoicing processes.

SAP DRC supports businesses by enabling them to:

• Generate compliant electronic invoice formats
• Validate invoice data
• Support country-specific regulatory requirements
• Integrate with government platforms
• Manage electronic reporting obligations

As electronic invoicing regulations continue to expand worldwide, SAP DRC provides a scalable framework for managing compliance across multiple countries.

👉 Learn more about SAP DRC

---

The Role of SAP Invoice Management by OpenText (VIM)

While SAP DRC focuses primarily on compliance and electronic invoicing requirements, SAP Invoice Management by OpenText (VIM) automates the processing of incoming invoices.

Its capabilities include:

• Intelligent workflow management
• Invoice validation
• Approval workflows
• Exception handling
• Integration with SAP finance processes
• Secure invoice archiving

Together, SAP DRC and SAP VIM create an integrated platform for compliant and highly automated invoice processing.

👉 Learn more about SAP Invoice Management by OpenText

---

Benefits of EN 16931 for Businesses

Implementing EN 16931 offers significant advantages beyond regulatory compliance.

Greater Automation

Structured invoice data eliminates manual data entry and enables end-to-end automated processing.

---

Improved Data Quality

Standardised invoice structures reduce inconsistencies and minimise processing errors.

---

Better Interoperability

A common European standard enables businesses to exchange invoices seamlessly across countries and ERP systems.

---

Stronger Compliance

EN 16931 helps organisations meet national and European electronic invoicing requirements more consistently.

---

Lower Processing Costs

Automated invoice processing reduces administrative effort and lowers the cost per invoice.

---

Future-Proof Digital Processes

EN 16931 provides the foundation for future initiatives such as VAT in the Digital Age (ViDA), real-time reporting, and continuous digital tax compliance.

---

Common Challenges When Implementing EN 16931

Although EN 16931 establishes a common European framework for electronic invoicing, its implementation often presents practical challenges.

Many organisations underestimate that compliance involves much more than simply generating an XML file. Successful implementation requires coordinated adjustments to business processes, ERP systems, master data, integrations, and governance structures.

Typical challenges include:

• Inconsistent master data
• Non-standardised invoice processes
• Legacy ERP landscapes
• Country-specific regulatory requirements
• Missing or incomplete validation mechanisms
• Media disruptions caused by PDF- or paper-based workflows
• Insufficient integration between finance, procurement, and IT systems

Companies operating internationally must also consider national implementation guidelines that complement the European standard.

---

Best Practices for Implementing EN 16931

Successful implementation projects typically follow several proven principles.

Standardise Business Processes

Before introducing EN 16931, existing invoicing processes should be reviewed and harmonised wherever possible.

Standardised processes simplify implementation and reduce long-term maintenance efforts.

---

Prioritise Standard SAP Functionality

Whenever possible, organisations should rely on standard SAP solutions instead of developing custom interfaces or proprietary invoice formats.

This simplifies future updates and ensures better compatibility with evolving regulatory requirements.

---

Improve Master Data Quality

Structured electronic invoices rely on accurate business data.

Supplier records, customer master data, tax codes, and material information should therefore be reviewed and cleansed before implementation.

---

Take an End-to-End Perspective

EN 16931 is not just about invoice creation.

The entire process should be considered—from invoice generation and transmission to validation, approval, posting, reporting, and legally compliant archiving.

---

Integrate Compliance from the Beginning

Regulatory compliance should not be treated as a separate downstream activity.

Instead, compliance requirements should be embedded directly into business processes, workflows, and system architecture.

Further reading:

👉 SAP DRC Roadmap

👉 SAP Invoice Management

👉 ZUGFeRD and SAP DRC

---

Step-by-Step Guide to Implementing EN 16931

A structured implementation approach helps organisations minimise project risks and accelerate time to value.

Step 1 – Analyse Current Invoice Processes

Begin by assessing existing invoicing workflows, systems, and document formats.

Identify manual activities, integration gaps, and compliance risks.

---

Step 2 – Define the Target Architecture

Determine which ERP systems, invoice formats, integration platforms, and compliance solutions will be part of the future landscape.

---

Step 3 – Implement EN 16931-Compliant Formats

Introduce invoice formats that comply with EN 16931, such as:

• XRechnung
• ZUGFeRD (EN 16931 profile)
• PEPPOL BIS Billing

---

Step 4 – Integrate ERP and Compliance Solutions

Connect ERP systems with SAP DRC, invoice management solutions, integration platforms, and archiving systems to establish an automated end-to-end process.

---

Step 5 – Validate and Test

Thoroughly test all invoice scenarios, including:

• XML validation
• Business rule validation
• Tax calculations
• Cross-border scenarios
• System integrations

---

Step 6 – Go Live and Continuously Optimise

Following a successful rollout, continuously monitor invoice quality, compliance, and process performance to identify optimisation opportunities.

---

Costs and Implementation Effort

The cost of implementing EN 16931 depends on several factors, including:

• Company size
• Existing ERP landscape
• Number of invoice formats
• International business operations
• Integration complexity
• Desired level of automation

Implementation projects typically range from several weeks to several months, depending on organisational complexity and project scope.

---

The Future of EN 16931

EN 16931 forms the foundation of Europe’s digital invoicing strategy and will continue to gain importance in the coming years.

Future developments will increasingly focus on:

• VAT in the Digital Age (ViDA)
• Real-time tax reporting
• Continuous Transaction Controls (CTC)
• AI-supported invoice processing
• Digital tax audits
• Cross-border electronic invoicing

Companies that establish EN 16931-compliant processes today will be well positioned to meet future European and international compliance requirements.

---

Conclusion

EN 16931 is much more than a technical specification for electronic invoices. It provides the common European foundation for secure, standardised, and interoperable electronic invoicing across countries, industries, and ERP systems.

As electronic invoicing requirements continue to expand, organisations should view EN 16931 not merely as a compliance obligation but as a strategic opportunity to modernise finance operations.

When combined with solutions such as SAP S/4HANA, SAP Document and Reporting Compliance (SAP DRC), and SAP Invoice Management by OpenText, EN 16931 enables highly automated, compliant, and future-ready invoicing processes.

Companies that invest early in standardised electronic invoicing will benefit from greater efficiency, improved data quality, lower processing costs, and stronger long-term compliance.

---

FAQ