# 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.

## 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

| Question | Prefer XRechnung | Prefer 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

- [XRechnung standard guide](/resources/compliance/xrechnung-standard)
- [ZUGFeRD format guide](/resources/compliance/zugferd-format)
- [ZUGFeRD EN 16931 profile](/resources/zugferd/profiles/en16931)
- [Convert and validate an invoice](/convert)

## Official references

- [European Commission eInvoicing in Germany profile](https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467108886/eInvoicing%2Bin%2BGermany)
- [BMF FAQ on mandatory e-invoicing](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html)