Skip to main content

Comparison · 2026-06-22

Markdown export

XRechnung vs ZUGFeRD: choosing the right format

Choose XRechnung when the recipient expects pure XML; choose ZUGFeRD or Factur-X when a validated hybrid PDF/XML invoice is accepted.

First decision: recipient channel before file type

XRechnung and ZUGFeRD can both carry EN 16931 invoice data, but they solve different operational problems. XRechnung is a structured XML file for channels that want machine-readable data only. ZUGFeRD and Factur-X combine a human-readable PDF/A-3 document with embedded structured XML.

Start with the buyer, portal, or network requirement. If the recipient names XRechnung, do not send a hybrid PDF instead. If the recipient accepts a hybrid invoice and your workflow still needs a readable PDF, ZUGFeRD or Factur-X is usually the lower-disruption choice.

Interactive chooser

Two questions, one answer. The recipient decides the format, not your preference.

1Who receives the invoice?

2Does the recipient want a readable PDF too?

Send

PDF/A-3CII XML insideProfile EN 16931 or higher

One file: people read the PDF, software reads the embedded XML. MINIMUM and BASIC WL do not count as e-invoices in Germany.

How it travels: Any channel you agree with the buyer, email included.

A plain PDF is not an e-invoice. Whatever the answer, the structured XML is what counts. In Germany a PDF by email is a “sonstige Rechnung”; in France it is not an e-invoice under the reform.

Which e-invoice format to send, by recipient. German public authority: XRechnung (UBL or CII) with the Leitweg-ID in BT-10. German business: ZUGFeRD in the EN 16931 profile or higher if a readable PDF is wanted, otherwise XRechnung or another EN 16931 XML format. Business in another EU country via Peppol: Peppol BIS Billing 3.0 in UBL 2.1. Business in France, between businesses established in France: Factur-X, or UBL or CII, through a Plateforme Agréée. A plain PDF is not an e-invoice. Sources: BMF e-invoicing FAQ, KoSIT XRechnung, Peppol BIS Billing 3.0, DGFiP. Status: October 2026. Invoice Converter creates and validates these files; it does not deliver them.

Choose the format by workflow fit

Use XRechnung for strict XML channels

Best for German public-sector workflows, portals, and buyers that explicitly request XRechnung or reject PDF wrappers.

Use ZUGFeRD / Factur-X for hybrid delivery

Best when the buyer accepts a PDF/A-3 invoice with embedded XML and teams still need a readable invoice document.

Validate before sending either format

The format choice does not replace review. Totals, buyer references, VAT data, payment terms, and line details still need validation.

Practical format decision table

QuestionPrefer XRechnungPrefer ZUGFeRD / Factur-X
What did the recipient request?They asked for XRechnung, XML, a portal upload, or a public-sector format.They accept a hybrid PDF/XML invoice or name ZUGFeRD or Factur-X.
Does the invoice need a readable PDF?No. The recipient processes the structured XML directly.Yes. The PDF view remains part of the handoff or archive process.
Will a portal or network reject wrappers?Use this when the channel only accepts XML payloads.Use this only when the channel accepts PDF/A-3 with embedded XML.
What still needs review?Mandatory fields, routing references, VAT IDs, totals, payment terms, and line data.The same invoice data plus PDF/A-3 embedding, profile fit, and attachment metadata.

Before you send

  • Confirm the buyer or portal accepts the chosen format and profile.
  • Check that all required invoice facts are present before conversion.
  • Review the extracted data instead of assuming a PDF has enough structure.
  • Run validation on the final reviewed output, not only on the initial extraction.

Related resources

Official references