Skip to content

XRechnung vs ZUGFeRD: the XRechnung format explained

What is an XRechnung, who needs it and how does it differ from ZUGFeRD? A plain-English overview for online shops, freelancers and startups in Germany.

XRechnung vs. ZUGFeRD: the difference in one sentence

An XRechnung is XML only, while a ZUGFeRD invoice is a PDF with XML embedded in it. Both meet the same standard (EN 16931), and both count as an e-invoice under the German e-invoicing mandate, ZUGFeRD from version 2.0.1 and except in the MINIMUM and BASIC-WL profiles (section 14.1(13) and (14) UStAE, German). In practice, nobody can read an XRechnung without software, whereas a ZUGFeRD hybrid looks like a normal PDF invoice to the person who receives it. Which format to send to whom is covered in XRechnung or ZUGFeRD.

Comparison · same standard, two formats
XRechnung or ZUGFeRD: what the recipient gets
XRechnungB2G
FormatXML only
StandardEN 16931
Readable without softwareNo needs a viewer or software
Typical recipientAuthorities, municipalities, public institutions
Recipient addressLeitweg-ID
ZUGFeRDB2B and B2C
FormatPDF with embedded XML
StandardEN 16931
Readable without softwareYes like a normal PDF invoice
Typical recipientBusinesses and consumers
Both count as e-invoices. A printout or screenshot of an XRechnung, on the other hand, is not an e-invoice.
Rechnungskit Radar

Once a month: what changes for your online business.

Deadlines, law and tax, market news and what is new in Rechnungskit. Free, for shops, SaaS and digital products. Learn more

Who actually needs an XRechnung?

Among online shops, almost nobody does. XRechnung becomes relevant when you invoice public-sector buyers (authorities, municipalities, public institutions), that is, in B2G business. For federal contracts, the E-Invoicing Ordinance (ERechV) has required electronic invoices since November 27, 2020 (§ 3(1) ERechV, § 11(3) ERechV, German). In principle you use the XRechnung standard; another standard is allowed if it complies with EN 16931 (§ 4(1) ERechV). Invoices for direct awards up to €1,000 are among the exceptions (§ 3(3) ERechV). You submit through a public portal such as ZRE or OZG-RE (§ 4(3) ERechV), with a Leitweg-ID (the public buyer's routing ID) as the recipient address. German states and municipalities have their own rules; what your buyer requires is usually stated in the order.

For B2B business between companies, ZUGFeRD meets the same legal requirement (section 14.1(14) UStAE, German), with the advantage that consumers and business customers can read the same invoice.

What an XRechnung must contain

Besides all mandatory invoice details under § 14(4) UStG (the German VAT Act), the E-Invoicing Ordinance requires, for invoices to the federal government, among other things the Leitweg-ID, bank details, payment terms and an email address of the supplier (§ 5(1) ERechV, German). In an XRechnung, the Leitweg-ID goes into the buyer reference field, alongside machine-readable line item and tax data. The portal checks every invoice automatically for formal errors and rejects faulty ones (§ 4(3) ERechV) before any person has looked at it.

How Rechnungskit handles it

Rechnungskit creates standard invoices as ZUGFeRD 2.5 under EN 16931. A permitted small-amount invoice (Kleinbetragsrechnung) without a recipient address deliberately stays a reduced PDF/A document and does not get a made-up XML recipient.

For public-sector buyers, XRechnung 3.0 is created automatically: you store the customer's Leitweg-ID on the customer record, and every further invoice to that customer is generated as XRechnung XML, checked against the KoSIT rules, archived and sent by email together with a PDF copy for reading. In the Rechnungskit checkout and through the API, the Leitweg-ID can also be passed in directly with the order. The same works for orders from your shop: when a university buys from you, you enter its Leitweg-ID on the customer once, and every invoice to it created after that is an XRechnung, whether the order comes in through Shopify with Rechnungskit or through WooCommerce with Rechnungskit. Rechnungskit does not handle delivery via PEPPOL; if needed, you upload the XML to portals such as ZRE or OZG-RE. The create e-invoices page shows how the automated flow works today, and the e-invoicing software page lists all features.

FAQ

Is XRechnung "better" than ZUGFeRD?
No, both meet the same standard. For the federal government, XRechnung is the default standard, but other standards that comply with EN 16931 are allowed there too (§ 4(1) ERechV, German). For B2B and B2C, ZUGFeRD is more practical because people can still read the invoice.
Can I just print an XRechnung as a PDF?
No. An XRechnung is an XML file. A printout or screenshot is not an e-invoice, because an e-invoice has to be issued, sent and received in a structured format (§ 14(1) sentence 3 UStG, German). To read one, you need a viewer or software that displays the XML.
Does my online shop need to be able to send XRechnung invoices?
Only if you sell to public-sector buyers. For everything else, ZUGFeRD is enough, and Rechnungskit creates it for every invoice by default.
No tax or legal advice

Rechnungskit is not a tax advisory or law firm. This article explains general principles and does not replace advice from a tax advisor (Steuerberater, § 5 StBerG) or a lawyer (§ 3 RDG). Rechnungskit is built for businesses based in Germany and prepares documents, tax rates and bookings automatically. How your specific case is treated remains your decision, ideally together with your tax advisor or a lawyer.

Rechnungskit Radar

Once a month: what changes for your online business.

Deadlines, law and tax, market news and what is new in Rechnungskit. Free, for shops, SaaS and digital products. Learn more

Rechnungskit writes your e-invoices for you.

From every paid order, validated, archived and ready for DATEV. Set up for free, no credit card.

de en