Skip to content

ZUGFeRD: format, example and profiles of the German e-invoice

What ZUGFeRD is, what a ZUGFeRD invoice looks like (with an XML example), which profiles and versions exist, and how to create and check a ZUGFeRD invoice.

What is ZUGFeRD?

ZUGFeRD stands for "Zentraler User Guide des Forums elektronische Rechnung Deutschland", the central user guide of the German e-invoicing forum. It is published by the Forum elektronische Rechnung Deutschland (FeRD), where public administration, trade associations and businesses work together. ZUGFeRD is a hybrid invoice format: one file holds two layers with the same invoice data.

  • The PDF layer is a PDF/A-3, a PDF in archive format. It shows the invoice the way you know it, with letterhead, line items and totals, and any PDF reader opens it.
  • The XML layer is attached inside the PDF. It holds the same details in structured form, so accounting software can take over the invoice number, amounts and VAT rates without anyone retyping them.

The XML uses the Cross Industry Invoice (CII) syntax from UN/CEFACT and the data model of the European standard EN 16931. The standard defines which details an electronic invoice in the EU contains and gives each one a number (a business term, for example BT-1 for the invoice number). Since ZUGFeRD 2.1 the format is technically identical to the French Factur-X, so a ZUGFeRD invoice is also a Factur-X invoice.

For German VAT purposes the XML layer is what counts. An e-invoice is an invoice in a structured electronic format that allows electronic processing (§ 14 Abs. 1 sentence 3 UStG, German). The format has to comply with EN 16931 or convert to it without loss (§ 14 Abs. 1 sentence 6 UStG). ZUGFeRD meets this from version 2.0.1, except for the MINIMUM and BASIC WL profiles (BMF circular of October 15, 2025, section 14.1 para. 14 UStAE, German). According to the same circular, the structured part prevails if the PDF and the XML differ.

What does a ZUGFeRD invoice look like?

At first glance, like any other PDF invoice. The difference only shows in the attachments panel of your PDF program: an XML file sits there, in ZUGFeRD 2.x usually named factur-x.xml. Both layers carry the same values in different forms.

ZUGFeRD · One file, two layers
The same invoice for people and for software
PDF/A-3 (visible)for people
Invoice numberRE-2026-1047
Invoice date12.10.2026
2 × espresso beans 1 kg40,00 €
VAT 7 %2,80 €
Total42,80 €
factur-x.xml (embedded)for software
BT-1 invoice numberRE-2026-1047
BT-2 invoice date20261012
BT-131 line net amount40.00
BT-110 VAT amount2.80
BT-112 total42.80
Example with demo data. The XML part is what counts for tax purposes: if the two layers differ, the structured data set prevails.

ZUGFeRD example as an XML excerpt

This is what the embedded data set of a ZUGFeRD invoice in the EN 16931 profile looks like. The example is shortened and uses demo data. Addresses, VAT IDs, payment details and other mandatory fields are left out so the structure stays readable, which also means it is not a template for a real invoice. The comments are in German, as in the German original.

<?xml version="1.0" encoding="UTF-8"?>
<!-- Gekürztes Beispiel mit Demo-Daten, keine vollständige Rechnung -->
<rsm:CrossIndustryInvoice
    xmlns:rsm="urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100"
    xmlns:ram="urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100"
    xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:100">
  <rsm:ExchangedDocumentContext>
    <ram:GuidelineSpecifiedDocumentContextParameter>
      <ram:ID>urn:cen.eu:en16931:2017</ram:ID>  <!-- Profil EN 16931 -->
    </ram:GuidelineSpecifiedDocumentContextParameter>
  </rsm:ExchangedDocumentContext>
  <rsm:ExchangedDocument>
    <ram:ID>RE-2026-1047</ram:ID>             <!-- BT-1 Rechnungsnummer -->
    <ram:TypeCode>380</ram:TypeCode>          <!-- BT-3: 380 = Rechnung -->
    <ram:IssueDateTime>
      <udt:DateTimeString format="102">20261012</udt:DateTimeString>
    </ram:IssueDateTime>                      <!-- BT-2 Rechnungsdatum -->
  </rsm:ExchangedDocument>
  <rsm:SupplyChainTradeTransaction>
    <ram:IncludedSupplyChainTradeLineItem>    <!-- eine Rechnungsposition -->
      <ram:AssociatedDocumentLineDocument>
        <ram:LineID>1</ram:LineID>
      </ram:AssociatedDocumentLineDocument>
      <ram:SpecifiedTradeProduct>
        <ram:Name>Espressobohnen 1 kg</ram:Name>
      </ram:SpecifiedTradeProduct>
      <ram:SpecifiedLineTradeAgreement>
        <ram:NetPriceProductTradePrice>
          <ram:ChargeAmount>20.00</ram:ChargeAmount>
        </ram:NetPriceProductTradePrice>
      </ram:SpecifiedLineTradeAgreement>
      <ram:SpecifiedLineTradeDelivery>
        <ram:BilledQuantity unitCode="C62">2</ram:BilledQuantity>
      </ram:SpecifiedLineTradeDelivery>
      <ram:SpecifiedLineTradeSettlement>
        <ram:ApplicableTradeTax>
          <ram:TypeCode>VAT</ram:TypeCode>
          <ram:CategoryCode>S</ram:CategoryCode>
          <ram:RateApplicablePercent>7</ram:RateApplicablePercent>
        </ram:ApplicableTradeTax>
        <ram:SpecifiedTradeSettlementLineMonetarySummation>
          <ram:LineTotalAmount>40.00</ram:LineTotalAmount>
        </ram:SpecifiedTradeSettlementLineMonetarySummation>
      </ram:SpecifiedLineTradeSettlement>
    </ram:IncludedSupplyChainTradeLineItem>
    <ram:ApplicableHeaderTradeAgreement>
      <ram:SellerTradeParty>
        <ram:Name>Nordlicht Kaffee GmbH</ram:Name>  <!-- BT-27 Verkäufer -->
        <!-- Anschrift und USt-IdNr. gekürzt -->
      </ram:SellerTradeParty>
      <ram:BuyerTradeParty>
        <ram:Name>Café am Hafen GmbH</ram:Name>     <!-- BT-44 Käufer -->
      </ram:BuyerTradeParty>
    </ram:ApplicableHeaderTradeAgreement>
    <ram:ApplicableHeaderTradeDelivery>
      <ram:ActualDeliverySupplyChainEvent>
        <ram:OccurrenceDateTime>
          <udt:DateTimeString format="102">20261012</udt:DateTimeString>
        </ram:OccurrenceDateTime>             <!-- BT-72 Leistungsdatum -->
      </ram:ActualDeliverySupplyChainEvent>
    </ram:ApplicableHeaderTradeDelivery>
    <ram:ApplicableHeaderTradeSettlement>
      <ram:InvoiceCurrencyCode>EUR</ram:InvoiceCurrencyCode>
      <ram:ApplicableTradeTax>                <!-- Steueraufschlüsselung -->
        <ram:CalculatedAmount>2.80</ram:CalculatedAmount>
        <ram:TypeCode>VAT</ram:TypeCode>
        <ram:BasisAmount>40.00</ram:BasisAmount>
        <ram:CategoryCode>S</ram:CategoryCode>
        <ram:RateApplicablePercent>7</ram:RateApplicablePercent>
      </ram:ApplicableTradeTax>
      <ram:SpecifiedTradeSettlementHeaderMonetarySummation>
        <ram:LineTotalAmount>40.00</ram:LineTotalAmount>
        <ram:TaxBasisTotalAmount>40.00</ram:TaxBasisTotalAmount>
        <ram:TaxTotalAmount currencyID="EUR">2.80</ram:TaxTotalAmount>
        <ram:GrandTotalAmount>42.80</ram:GrandTotalAmount>
        <ram:DuePayableAmount>42.80</ram:DuePayableAmount>
      </ram:SpecifiedTradeSettlementHeaderMonetarySummation>
    </ram:ApplicableHeaderTradeSettlement>
  </rsm:SupplyChainTradeTransaction>
</rsm:CrossIndustryInvoice>

A few things stand out. The identifier urn:cen.eu:en16931:2017 at the top tells the recipient which profile to read the file by. Amounts use a dot as the decimal separator and no currency symbol, and dates use the format YYYYMMDD. Every detail has a fixed place, which is why software can book the invoice without text recognition.

In Rechnungskit you can download the PDF and the XML of every invoice separately, and the invoice view names the format and profile:

Rechnungskit in English, invoice SN-2026-1047 from a subscription: on the left the preview of the German-language invoice with service period 04.10.2026 to 04.11.2026, two lines and a total of 21,00 €, at the bottom the note "E-Rechnung: Enthält strukturierte Rechnungsdaten nach ZUGFeRD 2.5 (EN 16931)". On the right "ZUGFeRD 2.5 · Archived document, Hybrid: PDF/A-3 with embedded XML (EN 16931)", "Immutably locked until 01/01/2035", the buttons "Download PDF" and "Download XML" and the status history with "Created" and "Archived (GoBD)"

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

ZUGFeRD profiles at a glance

A profile sets how many details the XML contains. Each larger profile includes everything in the smaller ones. The two smallest do not count for the German e-invoicing mandate (section 14.1 para. 14 UStAE, German), because every mandatory VAT detail has to be in the structured part (section 14.5 para. 1 UStAE).

Profile What the XML contains E-invoice under § 14 UStG?
MINIMUM Header data only, such as invoice number, parties and totals, meant as a booking aid No
BASIC WL Header data and VAT breakdown, but no line items ("without lines") No
BASIC Header data with simple line items, a subset of EN 16931 Yes
EN 16931 (formerly COMFORT) Every detail of the European standard, line items included Yes
EXTENDED EN 16931 plus extra fields for more complex B2B cases Yes
XRECHNUNG EN 16931 with the German XRechnung rules, in CII syntax Yes

For online retail, services and subscriptions, EN 16931 is the usual choice. It covers every mandatory detail, and any software that understands EN 16931 can read it. You only need EXTENDED when your customer asks for details the standard does not provide for. The XRECHNUNG profile fits when a recipient requires XRechnung and accepts a hybrid file.

ZUGFeRD versions from 1.0 to 2.5

ZUGFeRD has been developed since 2014. The dates come from the FeRD version archive.

Version Published Notes
1.0 25.06.2014 First version, older than EN 16931. Not suitable for the e-invoicing mandate
2.0.1 15.10.2019 Based on CII and EN 16931, accepted as an e-invoice from here on
2.1 and 2.1.1 24.03.2020 and 01.07.2020 Technically identical to Factur-X, XRECHNUNG profile from 2.1.1
2.2 01.03.2022 Joint specification with Factur-X
2.3 to 2.3.3 18.09.2024 to 07.05.2025 Follow-up releases of the 2.x line
2.4 04.12.2025 Follow-up release of the 2.x line
2.5 10.06.2026 Current line, latest information package 2.5.2 of 04.08.2026

Which minor version a program writes rarely decides whether your customer can deduct input VAT. What matters is that the file is version 2.0.1 or later, uses an allowed profile and is valid under the rules of its version. Rechnungskit generates ZUGFeRD 2.5 in the EN 16931 profile.

ZUGFeRD or XRechnung?

Both formats comply with EN 16931 and count as e-invoices. They differ in form: ZUGFeRD is a PDF plus XML, while the XRechnung is pure XML without a visual part.

E-invoice formats · Quick comparison
ZUGFeRD and XRechnung side by side
ZUGFeRD
StructurePDF/A-3 with embedded XML
Readable without softwareYes, as a PDF
SyntaxCII
Typical useB2B and B2C, online retail
XRechnung
StructurePure XML
Readable without softwareNo viewer needed
SyntaxUBL or CII
Typical usePublic-sector buyers with a Leitweg-ID
Both formats comply with EN 16931 and count as e-invoices under § 14 UStG. For ZUGFeRD, only profiles from BASIC upward count.

For invoices to businesses and consumers, ZUGFeRD is usually the more practical choice because every recipient can open the file. Federal authorities, on the other hand, generally require the XRechnung with a Leitweg-ID (§ 4 and § 5 ERechV, German). Which format suits which recipient is covered in XRechnung or ZUGFeRD.

Is ZUGFeRD mandatory? The 2025 to 2028 timeline

The law requires the e-invoice for supplies between domestic businesses, not a specific format (§ 14 Abs. 2 sentence 2 no. 1 UStG, German). ZUGFeRD is one of several ways to meet that obligation. The deadlines are set in § 27 Abs. 38 UStG.

E-invoicing mandate · Domestic B2B
When you have to receive and issue e-invoices
  1. 01.01.2025Receiving, for all businessesAn email inbox is enough
  2. until 31.12.2026Issuing: paper and PDF still allowedPDF with the recipient's consent
  3. 01.01.2027Issuing, above 800,000 € prior-year revenueSmaller businesses may still use paper or PDF in 2027
  4. 01.01.2028Issuing, for all businessesZUGFeRD from BASIC, or XRechnung
Applies to supplies between domestic businesses (§ 14 Abs. 2 and § 27 Abs. 38 UStG). There is no e-invoicing mandate for consumers.

All deadlines, exceptions and special cases such as the small-amount invoice are covered in the guide to the e-invoicing mandate. You can keep sending paper or PDF invoices to consumers. A ZUGFeRD file does no harm there, since it opens like a normal PDF (B2C e-invoicing).

Creating a ZUGFeRD invoice

There are two basic ways. For every option, including single invoices without software, see creating an e-invoice.

By hand with invoicing software. Many invoicing and accounting programs export ZUGFeRD. You enter the customer and line items, and the program produces the PDF and XML. That works well as long as you write a few invoices a month. Check that the program writes at least version 2.0.1 and the BASIC profile or higher; a label like "ZUGFeRD-ready" tells you nothing about either. A Word document saved as a PDF is not a ZUGFeRD invoice, however tidy it looks.

Automatically from your shop and payment provider. If you sell online, the invoice data already exists: order, buyer, line items, VAT rate and payment sit in your shop and with your payment provider. Instead of copying them into an invoicing program, an integration builds the ZUGFeRD invoice straight from that data. You type less, and the order and the invoice cannot drift apart.

This is how it works in Rechnungskit:

  1. You connect your shop or payment provider, for example Shopify, WooCommerce or Stripe.
  2. Every order and payment produces a ZUGFeRD 2.5 invoice in the EN 16931 profile.
  3. Before sending, Rechnungskit checks the mandatory details under § 14 Abs. 4 UStG and the format. If a document fails the check, it is held back and you see what is missing.
  4. The XML is archived for eight years in immutable storage with a SHA-256 checksum (§ 14b Abs. 1 UStG, German).

Customers with a Leitweg-ID automatically get an XRechnung instead of ZUGFeRD. The feature page on e-invoicing in Rechnungskit has the details, and e-invoicing software gives the overview of all features.

Checking, opening and reading ZUGFeRD

Opening. Any PDF program shows the visual version. You find the embedded XML in the attachments panel, in Adobe Acrobat Reader for example behind the paper clip icon. From there you can save the file and look at it in a text editor. You only need a dedicated ZUGFeRD viewer if you want the XML laid out in readable form.

Checking. Validators tell you whether a ZUGFeRD file is valid. They check the XML against the schema and business rules of EN 16931, and some also check the PDF for PDF/A-3 conformance:

  • Mustangproject is an open-source library with a command-line tool that validates ZUGFeRD and Factur-X files, including the PDF/A part. Rechnungskit uses Mustang internally to check every document before it goes out.
  • The KoSIT validator is the reference tool of the German Coordination Office for IT Standards (KoSIT) for the XRechnung.
  • The KoSIT XRechnung visualization renders an XML data set as a readable document.

Common mistakes in ZUGFeRD invoices:

  • Wrong profile. The file uses MINIMUM or BASIC WL and is therefore not an e-invoice under § 14 UStG.
  • Totals don't add up. The sum of the line amounts must exactly match the total net amount (rule BR-CO-10). If a program rounds each line differently from the total, the check fails.
  • Missing exemption reason. For tax-exempt supplies or reverse charge the standard requires a reason in the XML; a note on the PDF alone is not enough.
  • PDF and XML differ. If someone edits the PDF afterwards but not the XML, the two layers no longer match. A validator usually won't notice, since it only checks the XML and the PDF format.

A green result means the format and rules are fine. No validator checks whether the content is right for tax purposes, such as the VAT rate, service date or recipient. That stays with whoever issues the invoice and, when in doubt, their tax advisor.

Receiving and keeping. When you receive ZUGFeRD invoices, you don't need to open them by hand. Accounting software with e-invoice import reads the XML directly. You have to keep the e-invoice in its electronic form; according to the BMF circular of October 15, 2025 (German), the PDF image alone is not enough.

FAQ

Is ZUGFeRD mandatory?
No, German law does not prescribe a specific format. What is mandatory in B2B between domestic businesses is the e-invoice, meaning a structured format under EN 16931 (§ 14 Abs. 1 and 2 UStG, German). ZUGFeRD from version 2.0.1 meets that in every profile except MINIMUM and BASIC WL, and so does the XRechnung. You have had to be able to receive e-invoices since 2025; the obligation to issue them starts in 2027 or 2028 depending on revenue (§ 27 Abs. 38 UStG, German).
Can a PDF be converted into an e-invoice?
Renaming a finished PDF or saving it as PDF/A does not make it an e-invoice, because the structured data set is missing (§ 14 Abs. 1 sentence 3 UStG, German). Some programs read the values out of a PDF and embed an XML file. In that case the XML has to be complete and correct: if the two parts of a hybrid invoice differ, the structured part counts.
Which ZUGFeRD version do I need?
The German tax authorities accept ZUGFeRD from version 2.0.1. The current line is 2.5, and the latest FeRD information package is 2.5.2 (August 4, 2026). The profile matters more than the minor version: EN 16931 (formerly COMFORT) covers every mandatory detail and is the usual choice.
Can I send ZUGFeRD invoices to consumers?
Yes. Consumers are not covered by the e-invoicing mandate, but they open a ZUGFeRD file like any PDF, and the embedded XML does not get in the way. As with any PDF invoice, sending it electronically to consumers needs their consent (§ 14 Abs. 1 sentence 5 UStG, German). More in B2C e-invoicing.
How do I open a ZUGFeRD invoice?
With any PDF program. You see the invoice as usual, and the XML file sits inside the PDF as an attachment (usually "factur-x.xml"). In Adobe Acrobat Reader, for example, you find it in the attachments panel (paper clip icon). Accounting software with e-invoice import reads the XML directly.
Is ZUGFeRD the same as Factur-X?
Yes. Since ZUGFeRD 2.1 the two are technically identical. ZUGFeRD is the German name and Factur-X the French name for the same standard of PDF/A-3 with embedded CII XML. A valid ZUGFeRD file is also a valid Factur-X file.
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