Difference between ZUGFeRD, Factur-X, XRechnung & EN 16931

What is the difference between ZUGFeRD, Factur-X, XRechnung and EN 16931?

General

Around electronic invoicing (e-invoice), you will encounter various terms: EN 16931, ZUGFeRD, Factur-X and XRechnung. They describe different things: a European base standard, two hybrid formats (PDF with embedded XML data) and a pure XML format. This article explains the differences and shows what this means for your invoices from timeSensor LEGAL 365.

How to set up and create e-invoices in timeSensor LEGAL 365 can be found in the article How do I create invoices in the ZUGFeRD or FacturX format?

The terms at a glance

EN 16931 – the European base standard

EN 16931 is the overarching European standard for electronic invoicing. It defines which data an e-invoice must contain at a minimum (e.g. invoice number, tax number, invoice items) and how this data is structured. EN 16931 is not a file format itself but the common basis for ZUGFeRD, Factur-X and XRechnung.

ZUGFeRD – the German hybrid format

ZUGFeRD was developed by the Forum elektronische Rechnung Deutschland (FeRD). A ZUGFeRD invoice consists of a familiar PDF file, which is readable by humans, and an embedded XML file that can be automatically processed by accounting systems. ZUGFeRD is mainly used between companies (B2B).

ZUGFeRD has different profiles with varying data scope:

ProfileConsidered an e-invoice in Germany?
MINIMUMNo (booking aid only)
BASIC-WLNo (without invoice items)
BASICYes
EN 16931 (COMFORT)Yes, recommended standard profile for B2B
EXTENDEDYes
XRECHNUNGYes, contains the data of an XRechnung in the ZUGFeRD PDF

Factur-X – the French counterpart

Factur-X is the French counterpart to ZUGFeRD. From ZUGFeRD version 2 onwards, both formats are technically identical. A ZUGFeRD invoice is therefore automatically also a Factur-X invoice.

XRechnung – the pure XML format

XRechnung is a pure XML format without PDF. It is intended exclusively for machine processing and is not readable by humans without special display software (viewer). XRechnung is also based on EN 16931 but supplements it with national business rules. This makes information that is optional in EN 16931 mandatory, e.g. contact details of the invoicer or a buyer reference. Public clients (B2G) usually require an XRechnung, often with a routing ID.

Comparison

CriterionEN 16931ZUGFeRDFactur-XXRechnung
TypeEU standardHybrid (PDF + XML)Hybrid (PDF + XML)Pure XML
Readable by–Human and machineHuman and machineMachine only (or with viewer)
Main applicationBasis of all formatsB2B in GermanyB2B in France / internationalInvoices to authorities (B2G)

What is relevant in Germany?

In Germany, all four terms overlap (presentation without guarantee):

  • EN 16931 is the standard for what an e-invoice must contain.
  • ZUGFeRD from version 2.0.1 is considered an e-invoice, except for the MINIMUM and BASIC-WL profiles. For invoices to companies, the EN 16931 (COMFORT) profile is the usual choice.
  • XRechnung is usually required by authorities and public clients.
  • Factur-X is identical to ZUGFeRD and requires no separate settings.

timeSensor LEGAL 365 creates e-invoices in the hybrid format ZUGFeRD/Factur-X in the profile EN 16931 (ZUGFeRD COMFORT). These invoices meet the requirements for an e-invoice according to EN 16931.

When invoice recipients expect an XRechnung

Some invoice recipients, including companies that are not authorities, expect invoices that meet the requirements of XRechnung. Often, these recipients have aligned their invoice processing to XRechnung and therefore require the additional mandatory information of XRechnung.

In the case, timeSensor LEGAL 365 shows in the e-invoice tab in the XRechnung area (display only) which information is included in the invoice and which is still missing for an XRechnung: e-Invoice in the area XRechnung (display only), which information is included in the invoice and which is still missing for an XRechnung:

InformationOrigin in timeSensor LEGAL 365
Contact seller (BT-41)Account Manager
Seller e-mail address (BT-34)Account Manager's e-mail
VAT ID seller (BT-31)VAT ID of the entity
Routing ID buyerContact 'Routing ID' of the invoice recipient
Routing ID (BT-10)Routing ID, otherwise mandate ID
Buyer e-mail address (BT-49)Sticky note of the mandate, field 'To'
Contract reference (BT-12)Mandate ID, otherwise invoice reference
IBAN of the deposit account (BR-DE-23-a)Chart of accounts, Ledger tab, IBAN field


How to add missing information can be found in the section "Check mandatory information for e-invoices" in the article How do I create invoices in the ZUGFeRD or FacturX format?

Info
If there are uncertainties, clarify directly with your invoice recipient which format they require: a ZUGFeRD invoice (PDF with XML) in the EN 16931 profile, a ZUGFeRD invoice with XRechnung-compliant details, or a pure XRechnung (XML only). Also ask if they need a specific buyer reference or routing ID.