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?
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 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:
| Profile | Considered an e-invoice in Germany? |
|---|---|
| MINIMUM | No (booking aid only) |
| BASIC-WL | No (without invoice items) |
| BASIC | Yes |
| EN 16931 (COMFORT) | Yes, recommended standard profile for B2B |
| EXTENDED | Yes |
| XRECHNUNG | Yes, contains the data of an XRechnung in the ZUGFeRD PDF |
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 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.
| Criterion | EN 16931 | ZUGFeRD | Factur-X | XRechnung |
|---|---|---|---|---|
| Type | EU standard | Hybrid (PDF + XML) | Hybrid (PDF + XML) | Pure XML |
| Readable by | – | Human and machine | Human and machine | Machine only (or with viewer) |
| Main application | Basis of all formats | B2B in Germany | B2B in France / international | Invoices to authorities (B2G) |
In Germany, all four terms overlap (presentation without guarantee):
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.
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:
| Information | Origin 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 buyer | Contact '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?
