ZUGFeRD or XRechnung: which format fits when?

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. What decides the choice in the end is the statutory framework and your recipient’s requirements — not technical elegance.

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, prints it — and their accounting software can pick up the structured data at the same time. That dual path is exactly why ZUGFeRD is so widespread in B2B: 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 — in exchange the file is small, unambiguous and ideal for automated processing.

ZUGFeRD and XRechnung side by side

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

Strengths and limits of the two formats

Neither format is better than the other — they are built for different situations. An honest look at both sides helps 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 is irrelevant; in bulk processing it shows.

• Not accepted everywhere in B2G

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

What XRechnung is made for

• Maximum automation

  A pure data structure with no layout ballast 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, not on your own software. Because Billance produces both formats, you can simply 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. That is no extra work: 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 is therefore decided not by the format name but by the specific profile and version supported.

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 — except 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.

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.

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-invoiceDetects syntax, profile and rule package and returns a report covering XML schema, EN 16931, XRechnung and Peppol.
• View an e-invoiceTurns an XRechnung XML or ZUGFeRD PDF into a readable invoice with parties, line items and totals.
• Extract XML from an e-invoicePulls the embedded invoice XML out of ZUGFeRD and Factur-X PDFs — across several files in one go.

Frequently asked questions about ZUGFeRD and XRechnung

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

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 — FeRD — Forum elektronische Rechnung Deutschland
• XRechnung: standard and specification — KoSIT — German coordination office for IT standards
• XRechnung: validator configuration and rule set — KoSIT on GitHub
• Peppol BIS Billing 3.0 — OpenPeppol
• E-invoicing: questions and answers on the B2B rollout — 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