Guide

XRechnung or ZUGFeRD? The difference and which format applies

Updated November 2026

XRechnung or ZUGFeRD: what is the difference?

An XRechnung is a pure XML file; a ZUGFeRD invoice is a PDF with embedded XML. Both count as e-invoices, ZUGFeRD from version 2.0.1 onwards, except in the MINIMUM and BASIC WL profiles. To German federal authorities you generally send an XRechnung with a Leitweg-ID (the buyer's routing ID). Between businesses both are allowed, and you agree the format with your customer. For Umsatzsteuer (VAT) purposes, the XML is what counts in both cases.

What is XRechnung?

XRechnung is the German standard for e-invoices to public-sector buyers. KoSIT maintains it on behalf of the IT Planning Council (IT-Planungsrat). It implements the European standard EN 16931 and adds national rules. An XRechnung is a pure XML file in one of two syntaxes, UBL or UN/CEFACT CII. The current version is 3.0, with specification 3.0.2. Version 3.0 remains in force until at least 31 July 2027; version 4.0 so far exists only as a preliminary version (KoSIT, as of 16 October 2026). An XRechnung has no PDF view. So when a supplier sends you an XRechnung, you need a viewer that makes the XML readable (BMF FAQ, question 12a).

What is ZUGFeRD?

ZUGFeRD is published by the Forum elektronische Rechnung Deutschland (FeRD). A ZUGFeRD invoice is a PDF/A-3 file with an embedded XML in the UN/CEFACT CII syntax. The PDF displays the invoice; the accounting software reads the XML. Technically, ZUGFeRD is identical to the French Factur-X. The current version is 2.5.2 of 4 August 2026, which is also Factur-X 1.09.2. Whether a ZUGFeRD invoice counts as an e-invoice depends on the profile. The profile sets how much information the XML contains.

ZUGFeRD profiles according to the FeRD FAQ (as of 7 September 2026) and the BMF letter of 15 October 2024, para. 30
ProfileWhat the XML containsE-invoice under the UStGReceipt by the buyer
MINIMUMBuyer, seller, total amount and total tax, without a VAT breakdownno, a booking aidnot specified
BASIC WLAll details needed for bookkeeping, but no invoice linesno, a booking aidnot specified
BASICA subset of EN 16931, for simple invoicesyesbilateral agreement
EN 16931 (COMFORT)EN 16931-1 in fullyesmandatory
EXTENDEDMore than EN 16931, for example for several delivery locations in one invoiceyesbilateral agreement
XRECHNUNGAn XRechnung in the CII syntaxyesmandatory

The exception for MINIMUM and BASIC WL is stated explicitly in the BMF letter of 15 October 2024 (para. 30) and in the BMF FAQ (question 7). For VAT purposes, a PDF with an XML in either of these two profiles is not an e-invoice, even if it looks like a ZUGFeRD invoice. To create EU-compliant e-invoices, FeRD recommends the EN 16931 profile. On agreeing the format with the recipient, the FeRD FAQ contradicts itself: the profile overview says „bilaterale Vereinbarung“ ("bilateral agreement") for BASIC and EXTENDED, while elsewhere it says only EXTENDED has to be agreed in advance.

The difference between XRechnung and ZUGFeRD

XRechnung and ZUGFeRD compared (as of November 2026)
XRechnungZUGFeRD
Filean XML filea PDF (PDF/A-3) with embedded XML
XML syntaxUBL or CIICII
Readable without a viewernoyes, the PDF view
PublisherKoSIT on behalf of the IT Planning CouncilFeRD, together with FNFE-MPE in France (Factur-X)
Current version3.0.2, in force until at least 31 July 20272.5.2 of 4 August 2026
To federal authoritiesgenerally required (§ 4 ERechV)the federal FAQ only lists the XRECHNUNG profile, as pure XML without a PDF
Between businessesallowedallowed from version 2.0.1, in profiles from BASIC upwards

In our view, the choice between the two formats matters less than two standards from two publishers would suggest. Our test below shows why. In both formats, the XML is the invoice. If the PDF view and the XML of a ZUGFeRD invoice differ, the XML data takes precedence, and input VAT can only be deducted on the basis of the structured part (BMF letter of 15 October 2024, paras. 31 and 32). If you open a ZUGFeRD invoice only in a PDF program, you see the view. For VAT purposes, the embedded XML is what counts, and the BMF FAQ recommends making it visible yourself.

The same invoice as XRechnung and as ZUGFeRD: our test

On 11 November 2026 we ran a test invoice through our conversion, using a local copy of the program dated 10 November 2026. We generated the test PDF from invoice 01.02a of KoSIT's public XRechnung test suite: one line item at 7%, gross amount €12.60. Four details that an XRechnung requires were missing from the PDF or could not be used. The conversion asked for them, and we entered test values: the Leitweg-ID 04011000-12345-03 (check digit correct), a buyer email address, an IBAN and a tax number.

One PDF, three files from one run (test of 11 November 2026, KoSIT test invoice 01.02a)
XRechnung UBLXRechnung CIIZUGFeRD PDF
FileXML, 4,098 bytesXML, 5,598 bytesPDF/A-3b, 30,034 bytes, containing factur-x.xml with 5,552 bytes
SyntaxUBL (root element Invoice)CII (root element CrossIndustryInvoice)CII, line for line the same as the XRechnung CII except for BT-24
Specification identifier (BT-24)…#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0…#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0urn:cen.eu:en16931:2017
Leitweg-ID in BT-1004011000-12345-0304011000-12345-0304011000-12345-03
KoSIT validator 1.6.3, configuration of 31 August 2026Scenario „EN16931 XRechnung (UBL Invoice)“, 0 errors, 0 warningsScenario „EN16931 XRechnung (CII)“, 0 errors, 0 warningsScenario „EN16931 (CII)“, 0 errors, 0 warnings
Mustang validator 2.26.0not applicablenot applicablePDF part „isCompliant=true“ (PDF/A-3b); XML in the EN 16931 profile: 75 rules checked, 0 violated, result „valid“

The XML in the ZUGFeRD PDF and the XRechnung in CII each have 115 lines and differ in exactly one: the specification identifier in field BT-24. The XRechnung carries urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0, the ZUGFeRD XML only urn:cen.eu:en16931:2017. Amounts, names, IBAN and Leitweg-ID are identical character for character. At 30,034 bytes, the ZUGFeRD PDF is almost eleven times the size of the 2,812-byte test PDF. Among other things, PDF/A-3 requires the fonts to be inside the file (FeRD); in the test PDF, Helvetica is not embedded, in the ZUGFeRD PDF it is.

The specification identifier determines which rules a file is checked against. The KoSIT validator checked the XRechnung against the national XRechnung rules and the ZUGFeRD XML only against EN 16931. FeRD points out that a „valide ZUGFeRD EN16931 oder ZUGFeRD EXTENDED-Rechnung“ ("valid ZUGFeRD EN16931 or ZUGFeRD EXTENDED invoice") can produce error messages when checked only against XRechnung rules, „ohne dass die Rechnung deshalb fehlerhaft oder rechtlich unzulässig ist“ ("without the invoice being faulty or legally inadmissible as a result"). If a customer reports errors in your ZUGFeRD invoice, ask which rules they checked against. Our XRechnung validator also picks the rules based on the specification identifier: XRechnung 3.0 against the XRechnung rules, ZUGFeRD in the EN 16931 profile against EN 16931. It does not check the BASIC and EXTENDED profiles.

Which formats are allowed for an e-invoice

Between businesses there is no obligation to use XRechnung. The UStG requires a structured electronic format that complies with EN 16931 or has been agreed between the parties (§ 14 (1) UStG). The BMF names XRechnung and ZUGFeRD as the formats commonly used in Germany (FAQ, question 7). Other European formats that follow the standard are also allowed, such as Factur-X from France or Peppol BIS Billing (BMF letter of 15 October 2024, para. 26). An agreed format can be, for example, an EDI process such as EDIFACT, as long as all mandatory details can be transferred correctly and completely into an EN 16931 format (para. 33).

Which format for which recipient?

Which format each recipient expects (as of November 2026)
RecipientFormatBasis
Federal authorityXRechnung with the Leitweg-ID in field BT-10; for ZUGFeRD, the federal FAQ only lists the XRECHNUNG profile as pure XML§ 4 ERechV; FAQ on e-rechnung-bund.de
State or municipal authoritythe state's own rules; ask the office that placed the order with youthe ERechV only applies at federal level
Business in GermanyXRechnung, ZUGFeRD from 2.0.1 in profiles from BASIC upwards, or another permitted formatBMF letter of 15 October 2024, paras. 26, 27 and 33
Business abroadno e-invoicing obligation under the UStG; an e-invoice only with the recipient's consentBMF letter of 15 October 2024, para. 16
Private customersno e-invoicing obligationBMF FAQ, question 4

According to the BMF, which permitted format you use with another business is a civil-law matter between you and your customer (para. 27). ZUGFeRD is widespread in the skilled trades (Handwerk). Of the trade businesses that already issue e-invoices, around 75 per cent use ZUGFeRD, according to a survey by the ZDH (German Confederation of Skilled Crafts) (FeRD, 10 June 2026). We did not find a figure for all sectors. If your customer asks for „eine E-Rechnung“ ("an e-invoice") without naming a format, ask what their accounting software can import.

You only need a Leitweg-ID for public bodies. Between businesses, according to the BMF, a placeholder such as „-“ is enough in field BT-10 (FAQ, question 6). Our free Leitweg-ID tool shows you whether a Leitweg-ID is structured correctly. How to submit an XRechnung to the federal government is explained in the how-to Submitting an XRechnung via the OZG-RE.

What you need to be able to read as a recipient

Since 1 January 2025, businesses in Germany have to be able to receive e-invoices, and an email inbox is enough for that (BMF letter of 15 October 2024, para. 40). FeRD recommends that recipients be able to recognise and check ZUGFeRD in the EN 16931 and EXTENDED profiles as well as XRechnung. For an XRechnung you need a viewer. The tax authorities offer one at e-rechnung.elster.de (BMF FAQ, question 12a). Any PDF program opens a ZUGFeRD PDF but shows only the view. Our free XRechnung viewer shows the XML of both formats as a readable invoice, in the browser and without uploading.

More questions about XRechnung and ZUGFeRD

How can I tell whether a PDF is a ZUGFeRD invoice?

A ZUGFeRD invoice contains an attached XML file, under the current standard factur-x.xml or xrechnung.xml (FeRD). In Adobe Acrobat Reader you can see it via the paperclip icon. Drag the PDF into the XRechnung viewer: if it finds no invoice XML, it is an ordinary PDF.

Can I convert an XRechnung into a ZUGFeRD invoice?

In our test, the data differed only in the specification identifier. But for ZUGFeRD, an XRechnung lacks the PDF view, and its content must match the XML; FeRD recommends that issuers check this before sending. pdfvera creates both formats from your PDF invoice, not from an existing XRechnung.

Can I still use XRechnung 2.3?

KoSIT withdrew version 2.3 with effect from 1 February 2024. The current version is XRechnung 3.0; according to KoSIT it remains in force until at least 31 July 2027.

Should I send every invoice in both formats?

The UStG does not prescribe a specific format, as long as it is an e-invoice. The federal government explicitly asks suppliers, as a rule, not to issue and transmit invoices in different formats: „grundsätzlich darauf“ zu verzichten, „Rechnungen in unterschiedlichen Formaten auszustellen und zu übermitteln“ (FAQ e-rechnung-bund.de). For individual cases, your tax adviser can help.

Sources

  1. Bundesministerium der Finanzen: Fragen und Antworten zur Einführung der obligatorischen E-Rechnung (as of 29 October 2026, accessed 11 November 2026)
  2. Bundesministerium der Finanzen: BMF-Schreiben vom 15.10.2024, Einführung der obligatorischen E-Rechnung (copy at FeRD; amended by the BMF letter of 15 October 2025) (15 October 2024)
  3. Bundesministerium der Justiz: § 14 UStG, Ausstellung von Rechnungen (accessed 11 November 2026)
  4. Bundesministerium der Justiz: § 4 E-Rechnungsverordnung (ERechV), Anforderungen an das Rechnungsformat (accessed 11 November 2026)
  5. Beschaffungsamt des BMI: FAQ E-Rechnung Bund (accessed 11 November 2026)
  6. KoSIT / XStandards Einkauf: XRechnung (24 September 2026)
  7. KoSIT / XStandards Einkauf: XRechnung: Versionen und Bundles (16 October 2026)
  8. KoSIT: XRechnung-Testsuite (Apache-Lizenz 2.0) (accessed 11 November 2026)
  9. KoSIT: Validator (Prüftool) (accessed 11 November 2026)
  10. Forum elektronische Rechnung Deutschland (FeRD): FAQ zu ZUGFeRD (as of 7 September 2026, accessed 11 November 2026)
  11. Forum elektronische Rechnung Deutschland (FeRD): ZUGFeRD 2.5.2 (4 August 2026)
  12. Forum elektronische Rechnung Deutschland (FeRD): Laut Umfrage des ZDH: ZUGFeRD ist das meistgenutzte E-Rechnungsformat im deutschen Handwerk (10 June 2026)
  13. FNFE-MPE: Factur-X (accessed 11 November 2026)
  14. Mustangproject: Mustangproject: ZUGFeRD/Factur-X library and validator (accessed 11 November 2026)