Invoices and spend

E-invoices: XRechnung, ZUGFeRD and what changes for checks

Updated 6 min readMarkdown
In short

An e-invoice is an invoice issued, transmitted and received in a structured electronic format that can be processed automatically; a plain PDF is not one. In the EU the common model is the standard EN 16931, written as XML in the UBL or the CII syntax. XRechnung, ZUGFeRD, Factur-X and Peppol BIS Billing are profiles of it. German businesses have had to be able to receive e-invoices for domestic B2B supplies since 1 January 2025, and the duty to issue them is phased in. E-invoices remove reading errors. They do not remove the checks on price, duplicates and bank details.

An e-invoice is an invoice that is issued, transmitted and received as structured data, so that software can process it without reading a picture. A PDF sent by email is electronic, but it is not an e-invoice in this sense. In the EU the common definition of the data is the European standard EN 16931, and the formats named in this article are all ways of writing it.

EN 16931: one data model, two syntaxes

EN 16931 defines which pieces of information an invoice can carry, such as the invoice number, the seller's VAT identifier, each line's quantity and net price and the totals, together with rules that tie them to each other, for example that the invoice total without VAT is the sum of the line amounts less allowances plus charges. The standard names two XML syntaxes in which this model may be written: UBL and UN/CEFACT Cross Industry Invoice (CII). Directive 2014/55/EU obliges public contracting authorities in the EU to receive and process invoices that comply with it.

Countries and networks narrow the standard for their own use. That is where the familiar names come from.

FormatSyntaxWhat arrivesWho is behind it
XRechnungUBL or CIIAn XML fileThe German public sector's standard, run by KoSIT
ZUGFeRD and Factur-XCIIA PDF with the XML embedded (a hybrid)A German and a French initiative; in current versions the same format under two names
Peppol BIS BillingUBLAn XML file sent through the Peppol networkOpenPeppol, used across many countries

ZUGFeRD comes in profiles. The profiles MINIMUM and BASIC WL carry no line items and are not full invoices under the standard.

What German VAT law requires

The rules are in § 14 of the German VAT Act (UStG), as amended by the Growth Opportunities Act (Wachstumschancengesetz) with effect from 1 January 2025.

  • Definition. An e-invoice is issued, transmitted and received in a structured electronic format and allows electronic processing. The format must comply with EN 16931 and the list of syntaxes under Directive 2014/55/EU, or it may be agreed between the parties if the required details can be extracted correctly and completely into a compliant or interoperable format. Every other invoice, on paper or in another electronic format, is an "other invoice".
  • Obligation. For a supply from one business to another, where both are established in Germany, the invoice has to be an e-invoice.
  • Receiving. Where that obligation exists, the recipient's consent is no longer needed. Domestic businesses have therefore had to be able to receive e-invoices since 1 January 2025.
  • Transition for issuing. Under § 27 (38) UStG, an invoice for a supply carried out in 2025 or 2026 may still be sent on paper, or with the recipient's consent in another electronic format, until 31 December 2026. For supplies carried out in 2027 the same holds until 31 December 2027 if the issuer's total turnover in the previous calendar year was no more than 800,000 euros; invoices exchanged by EDI have a transition to the same date.
  • Small amounts. An invoice whose total does not exceed 250 euros may always be issued as an other invoice (§ 33 UStDV).

The Federal Ministry of Finance states that XRechnung and ZUGFeRD from version 2.0.1, except the profiles MINIMUM and BASIC WL, meet the requirements, and that in a hybrid format the structured part prevails over the picture if they differ.

This section describes the rules as published on the linked pages in November 2026. It is no legal or tax advice; check the current text and ask your tax adviser.

The EU beyond Germany

Other member states have mandates of their own, with their own formats and platforms, and EN 16931 is their common reference. Council Directive (EU) 2025/516, part of the "VAT in the Digital Age" package, allows member states to require e-invoices for domestic supplies and introduces structured e-invoicing and digital reporting for cross-border supplies between businesses within the EU in stages. The dates are in the directive. For a company that receives invoices from several countries, the practical consequence is to accept both syntaxes of the standard.

What changes for invoice checks

CheckPDF or paperE-invoice
ReadingTyped or read by software; can be misreadThe figures arrive as data
Formal detailsLooked for on the pageA field is filled or it is not
ArithmeticOnly as good as the readingThe same sums, run on exact figures
Price per itemLines have to be recognised firstArticle number, quantity, unit code and unit price per line
DuplicateThe number may be mistypedThe number is a field
Billing periodOften in free textPeriod fields for the invoice and for each line
Bank detailsAn IBAN somewhere in the footerThe payee's account as a field
Delivery siteWhere the layout prints itA delivery address next to the buyer's address

The checks themselves are the six of the invoice audit checklist. What changes is that the first two run without a person and the other four start from clean data.

What does not change

A valid e-invoice is a well-formed statement by the supplier. It is not a true one by virtue of its format.

  • A unit price above the agreed price validates without complaint.
  • The same delivery billed under two numbers gives two valid files; see detecting duplicate invoices.
  • A fraudster can produce a flawless XML file with their own IBAN in the payee field. The check for changed bank details matters as much as before.
  • With a hybrid file, the person approving sees the picture while the system books the data. Show the reviewer a rendering of the structured part.

Getting accounts payable ready

  1. Name one address for incoming e-invoices and tell your suppliers.
  2. Recognise the format from the file's content: the XML root element, or an XML attachment inside a PDF. File names and declared types are unreliable.
  3. Validate against the standard's rules, and return files that fail to the supplier.
  4. Run the same arithmetic and audit checks as on every other invoice.
  5. Keep the structured part unchanged in your archive. According to the Federal Ministry of Finance, at least that part has to be retained.
  6. Keep a path for PDFs and paper. Foreign suppliers, small amounts and the transition periods will send them for years.
  7. Ask your larger suppliers for e-invoices now. Clean lines are also what a spend analysis is built from.

How Cureman does it

Cureman parses XRechnung and Peppol invoices in the UBL syntax and ZUGFeRD and Factur-X in the CII syntax without a model. In a ZUGFeRD PDF it finds the embedded XML and reads that. What a document is, is decided from its first bytes and never from its name. It takes the supplier with its VAT identifier, invoice number, dates, currency, order reference, cost centre, billing period, the payee's IBAN, payment terms with early-payment discount, the buyer's and the delivery address, and each line with article number, quantity, unit code, unit price, tax rate and period. Credit notes are recognised by their type code.

The same arithmetic checks then run as on every invoice. A parsed invoice that passes them is accepted, and it carries no "read by model" label, because no model read it. An invoice whose totals do not follow from its lines, for example because of a document-level allowance that the parser does not read yet, waits for a person. Cureman checks arithmetic and compares with earlier invoices and agreed prices; it is not a validator for the full rule set of the standard. PDFs without embedded data are read by a model and labelled until a person has reviewed them. The module is described under invoice audit and spend analysis.

Questions and answers

Is a PDF invoice an e-invoice in Germany?

No. Under § 14 (1) of the German VAT Act an e-invoice is issued, transmitted and received in a structured electronic format that allows electronic processing. A PDF, a scan or a photo is an "other invoice". A ZUGFeRD file is different, because it is a PDF that carries the structured XML inside it, and that XML is the invoice. This is a description of the rule and no legal or tax advice.

Since when do German businesses have to accept e-invoices?

Since 1 January 2025 a business established in Germany must be able to receive e-invoices for supplies from other domestic businesses, and the supplier no longer needs the recipient's consent to send one. The transition periods in § 27 (38) of the VAT Act concern issuing, not receiving. According to the Federal Ministry of Finance an email inbox is enough for receipt.

What is the difference between XRechnung and ZUGFeRD?

Both follow the European standard EN 16931. XRechnung is a pure XML file in the UBL or the CII syntax, with nothing for a person to read without a viewer. ZUGFeRD, called Factur-X in France, is a PDF with the XML in the CII syntax embedded, so it carries a readable picture and the data in one file. Where the two parts differ, the structured part counts.

Do e-invoices make invoice checks unnecessary?

No. They make reading exact, because the supplier's system wrote the figures as data, and they make formal and arithmetic checks automatic. Whether the price is the agreed one, whether the delivery was billed before and whether the bank account is the supplier's cannot be seen from the file. A technically valid e-invoice can be wrong in each of these respects.