---
title: "ZUGFeRD or XRechnung? The Two Formats Compared | Billance"
description: "ZUGFeRD (hybrid PDF) or XRechnung (pure XML): differences in syntax, profiles and use cases, with guidance for B2B and B2G plus a free browser format check."
url: "https://billance.de/en/zugferd-and-xrechnung"
language: "en"
---

Format comparison

# ZUGFeRD or XRechnung: which format fits when?

Last updated: 31 October 2026

Both formats satisfy the same European standard and still look nothing alike: XRechnung is a pure XML file, ZUGFeRD a PDF with invoice data embedded inside it. This page compares them field by field, explains syntaxes and profiles, and answers the question of which format to send to which recipient.

[Start for free](https://billance.de/en/pricing) [Download Billance](https://billance.de/en/download)

## At a glance

- Shared basis

  EN 16931

- XRechnung

  pure XML (UBL/CII)

- ZUGFeRD

  PDF/A-3 with XML

- Format decided by

  the recipient

## ZUGFeRD and XRechnung: both formats in brief

XRechnung and suitable ZUGFeRD profiles carry the same structured invoice data under EN 16931. They differ in the packaging: in whether a human can read the file unaided, and in what the respective profile requires. The choice comes down to the statutory framework and your recipient’s requirements.

### ZUGFeRD and Factur-X: the hybrid format

ZUGFeRD is a hybrid invoice format: a visible PDF/A-3 file for people and an XML file embedded inside it for machines. Both parts describe the same invoice. The recipient opens the file like any other PDF, reads it and prints it, while their accounting software can pick up the structured data at the same time. ZUGFeRD is widespread in B2B mainly because it works even when the recipient is not technically ready. Factur-X is the jointly agreed German-French counterpart of the same format.

### XRechnung: the pure XML format

XRechnung is a purely structured XML file with no visual rendering, in either UBL or CII syntax. It contains no PDF component and cannot be read unaided; in a text editor it looks like program code. It was developed as the German application specification for exchanging invoices with federal, state and municipal authorities. To look at it as a document you need software or a [viewer](https://billance.de/en/view-e-invoice). In exchange the file is small and unambiguous, and it suits automated processing well.

### Read an XRechnung without installing anything

You do not need software to look inside an XRechnung. The free e-invoice viewer opens UBL and CII files locally in your browser and presents parties, line items, taxes and totals as a readable invoice.

## ZUGFeRD and XRechnung side by side

The comparison below covers the differences that matter in practice, from readability to the question of who expects which format.

| Criterion | ZUGFeRD / Factur-X | XRechnung |
| - | - | - |
| File format | Hybrid: PDF/A-3 with embedded XML | Pure XML, no PDF component |
| Human readable | Yes, in any PDF reader | No, requires software or a viewer |
| Machine processing | Yes, through the embedded XML file | Yes, directly |
| Syntax | CII (Cross Industry Invoice) | CII or UBL (Universal Business Language) |
| Profiles / variants | MINIMUM, BASIC-WL, BASIC, EN16931 (Comfort), EXTENDED, XRECHNUNG | One CIUS with version releases, e.g. 3.x |
| Typical use | B2B: retail, services, trades, freelancers | B2G: public authorities and public buyers |
| File size | Larger, because the PDF layout travels with it | Very small, data only |
| Retention | Preserve the structured original; keeping the complete PDF/XML file is advisable | Keep the XML file unaltered, render it when needed |
| In Billance | EN16931/Comfort, XRechnung and Extended profiles | CII and UBL, including the buyer reference (BT-10) |

## Strengths and limits of the two formats

Neither format is better in general; they suit different situations. The pros and cons below help you set up your invoicing process to fit.

### What ZUGFeRD is made for

- ### Nothing to relearn for the recipient

  The invoice looks the way it always has and can be checked, forwarded and printed without special software.

- ### Works both ways

  Recipients with modern accounting software pick up the XML data automatically; everyone else simply reads the PDF.

- ### High acceptance in B2B

  Because nobody has to change anything, there is virtually no adoption hurdle with business customers.

- ### Graded profiles

  From MINIMUM to EXTENDED the level of detail can be matched to the use case, though not every profile qualifies as an e-invoice for VAT purposes.

- ### Larger files

  The PDF component costs storage. For email that does not matter, but it adds up in bulk processing.

- ### Not accepted everywhere in B2G

  Some public bodies accept pure XML files only and reject hybrid PDFs.

### What XRechnung is made for

- ### Easy to automate

  A pure data structure with no layout that can be processed straight through.

- ### Very small files

  Economical in transmission and in long-term archiving.

- ### The administration’s standard

  The expected format for many public buyers; their specific requirements and exceptions still apply.

- ### Two syntaxes to choose from

  CII or UBL: which one you need is set by the recipient. Billance produces both.

- ### Unreadable unaided

  The file cannot be read directly by a person; for questions and approvals you need a rendering.

- ### Not yet established everywhere in B2B

  Smaller businesses often cannot process pure XML invoices yet and will ask for a PDF.

## Decision guide: which format for which recipient?

The choice almost always depends on the recipient. Because Billance produces both formats, you can follow what the other side needs.

- ### Business customers, trades, freelancers → ZUGFeRD

  The recipient reads the invoice as usual, while modern accounting software still picks up the embedded data automatically. This is the route with the fewest follow-up questions.

- ### Public buyers → XRechnung

  Public sector contracts generally call for an XRechnung, with the routing identifier the buyer gave you in the buyer reference. Central invoice receipt portals frequently reject hybrid PDFs.

- ### Large recipients with a supplier portal → ask first

  Corporations and retail chains usually prescribe format, profile and transmission channel precisely. A look at the supplier guidelines saves a rejected invoice.

- ### Cross-border in the EU → check Peppol

  UBL syntax is common for sending over the Peppol network. XRechnung and Peppol BIS Billing are different profiles, though: check the profile, the recipient and the access point before assuming a UBL file will pass everywhere.

- ### Running both in parallel is the norm

  Many businesses send ZUGFeRD to business customers and XRechnung to public authorities. This adds no extra work, since you enter the invoice once and export whichever format is needed.

## Technical detail: syntaxes, profiles and versions

EN 16931 describes the semantic invoice model and its business rules. XRechnung builds on it as the German application specification and tightens individual rules; ZUGFeRD offers several profiles with different levels of detail. Whether two systems fit together therefore depends on the specific profile and version they support.

### ZUGFeRD and Factur-X profiles

ZUGFeRD and Factur-X rest on a jointly agreed format. According to publications by the German Federal Ministry of Finance, ZUGFeRD formats from version 2.0.1 onwards generally meet the VAT requirements for an e-invoice. The exceptions are the MINIMUM and BASIC-WL profiles, which deliberately structure only part of the invoice. BASIC is a different thing and is not excluded. For EN 16931 use cases the EN16931/Comfort profile is available.

| Profile | Extent of structured data | Classification |
| - | - | - |
| MINIMUM | Header data and totals only, no line items | Excluded as a VAT e-invoice |
| BASIC-WL | Invoice without lines | Excluded as a VAT e-invoice |
| BASIC | Line items with a reduced field set | Not covered by the exclusion |
| EN16931 (Comfort) | The full core model of the standard | The default for EN 16931 use cases |
| EXTENDED | Core model plus industry-specific extensions | For complex billing, provided the recipient supports it |
| XRECHNUNG | Core model with the national XRechnung rules | Hybrid variant for recipients who expect XRechnung rules |

### XRechnung: CIUS, syntaxes and versions

XRechnung is a CIUS, a national restriction of the European standard for Germany. It makes fields mandatory that the standard only recommends and adds its own business rules with the prefix `BR-DE-`. It can be issued in CII syntax (UN/CEFACT Cross Industry Invoice) or in UBL syntax (OASIS Universal Business Language); both are equally admissible, and Billance supports both.

Version releases are updated regularly. Validation messages therefore always carry a rule reference such as `BR-DE-15`, which makes it possible to trace which release is meant.

### Settle format and profile before the first send

Find out which version and which profile your recipient accepts before you switch. Billance supports you with formal checks; those guarantee neither the absence of errors nor the professional and tax correctness of your invoice, and they do not replace a commitment from the recipient.

## Check format, profile and content yourself

If you want to know which format and profile a specific file actually uses, you do not have to read the XML. All three tools run locally in your browser, with no account and no upload.

- [Validate an e-invoice Detects syntax, profile and rule package and returns a report covering XML schema, EN 16931, XRechnung and Peppol.](https://billance.de/en/validate-e-invoice)
- [View an e-invoice Turns an XRechnung XML or ZUGFeRD PDF into a readable invoice with parties, line items and totals.](https://billance.de/en/view-e-invoice)
- [Extract XML from an e-invoice Pulls the embedded invoice XML out of ZUGFeRD and Factur-X PDFs, across several files in one go.](https://billance.de/en/extract-xml-from-e-invoice)

## Frequently asked questions about ZUGFeRD and XRechnung

The questions that most often remain open when choosing a format.

### Can I send ZUGFeRD invoices to public authorities?

That depends on the buyer. At federal level, XRechnung or another standard compliant with EN 16931, the German e-invoicing regulation and the terms of the invoice receipt platform is generally required, and the pure XML file may be mandatory. A hybrid ZUGFeRD PDF is not automatically accepted. States and municipalities may have their own rules, so ask first if in doubt.

### Which format suits small businesses better?

If you work mainly with other businesses, ZUGFeRD is usually more convenient: the invoice looks like a familiar PDF, so customers without e-invoicing software can read it without trouble. The structured data is included regardless and is ready for automation later.

### Do I need special software to receive ZUGFeRD?

Not to read it. ZUGFeRD invoices are sent as standard PDFs in the PDF/A-3 archive format and open in any PDF reader. Only when you want to import the structured XML data into your accounting automatically do you need software that reads the embedded attachment.

### How can I display an XRechnung in a readable way?

An XRechnung is a pure XML file and is barely legible in a text editor. A viewer turns it back into a readable invoice document. The free e-invoice viewer on this site does that locally in your browser, and the Billance app brings the same rendering with it.

### What is the difference between ZUGFeRD and Factur-X?

ZUGFeRD and Factur-X are the jointly agreed German-French counterparts of the same format. What is technically possible depends on version and profile, not on the name. National requirements and transmission channels still apply on top; the format name alone guarantees no unrestricted acceptance.

### Which ZUGFeRD profiles satisfy the mandate?

The German Federal Ministry of Finance names ZUGFeRD from version 2.0.1 as a format suitable as an e-invoice for VAT purposes, excluding the MINIMUM and BASIC-WL profiles. BASIC is not BASIC-WL and is therefore not excluded. The individual invoice must still contain all required information, and stricter profile or recipient requirements may call for EN16931/Comfort or another profile.

### Is XRechnung valid abroad?

Whether a foreign recipient accepts XRechnung depends on their requirements. XRechnung and Peppol BIS Billing are different profiles based on EN 16931, so a UBL file is not automatically usable in every Peppol process. Check the profile, the recipient and the access point.

### Where do I enter the Leitweg-ID?

The routing identifier your buyer gives you belongs in the buyer reference, BT-10. BT-24 is something else: the specification identifier, for example for XRechnung. The electronic recipient address BT-49 is a further, separate field.

### Can I convert an XRechnung into ZUGFeRD afterwards?

Yes. With Billance you can embed structured XML data into a hybrid ZUGFeRD PDF, or extract the pure XML file from a hybrid PDF. That keeps you flexible if a recipient later asks for a different format.

### Are there size limits for ZUGFeRD invoices?

The format itself imposes no hard limit. ZUGFeRD files are larger than pure XML invoices because of the PDF component, but ordinary invoices usually stay well below a megabyte, so email is unproblematic. Recipient portals may set their own ceilings.

### Must the PDF view match the XML data?

Yes. Both parts of a hybrid invoice are meant to describe the same invoice. If the visual rendering diverges from the structured data, that is a defect and can prompt questions from the recipient. Check the XML side of your hybrid invoices before sending.

## Sources and format specifications

The statements on profiles, syntaxes and versions rest on the following publications by the bodies responsible for them.

- [ZUGFeRD / Factur-X: specification and profiles](https://www.ferd-net.de/standards/zugferd) (FeRD (Forum elektronische Rechnung Deutschland))
- [XRechnung: standard and specification](https://xeinkauf.de/xrechnung/) (KoSIT (German coordination office for IT standards))
- [XRechnung: validator configuration and rule set](https://github.com/itplr-kosit/validator-configuration-xrechnung) (KoSIT on GitHub)
- [Peppol BIS Billing 3.0](https://docs.peppol.eu/poacc/billing/3.0/) (OpenPeppol)
- [E-invoicing: questions and answers on the B2B rollout](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html) (German Federal Ministry of Finance)

This article reflects publicly available information as of the date shown and is not tax or legal advice. What governs are the statutory rules, the letters issued by the German Federal Ministry of Finance and the requirements of your invoice recipient.

## Read on

### Step by step in the help centre

The help articles walk through the same workflow as step-by-step instructions, including all fields, buttons and special cases.

- [Required Data for an E-Invoice](https://billance.de/en/help/help-center/mandatory-e-invoice-fields-en-16931)
- [Leitweg ID / Buyer Reference](https://billance.de/en/help/help-center/leitweg-id-and-buyer-reference)
- [E-Invoice Output Format](https://billance.de/en/help/help-center/choose-zugferd-or-xrechnung-output)
- [Converter](https://billance.de/en/help/help-center/convert-pdf-invoice-to-e-invoice)

### Try it right away

- [Create e-invoices](https://billance.de/en/features/create-e-invoices)
- [Convert invoices](https://billance.de/en/features/convert-invoices)
- [Validation](https://billance.de/en/features/validation)

### Related guides

[E-invoice basics](https://billance.de/en/e-invoicing-basics) [E-invoicing mandate](https://billance.de/en/e-invoicing-mandate) [Features](https://billance.de/en/features)

## Ready for e‑invoices?

Start with Billance and create your first e-invoices in just a few minutes.

[Start for free](https://billance.de/en/pricing) [Download software](https://billance.de/en/download)
