E‑Rechnungs-StudioXRechnung vs ZUGFeRD: which e‑invoice format should you use?
Both terms are common in Germany’s e‑invoice landscape. Both build on EN 16931—yet they solve different workflow needs.
In short
- XRechnung is typically XML only.
- ZUGFeRD is a hybrid PDF with embedded XML.
Quick comparison
| Topic | XRechnung | ZUGFeRD |
|---|---|---|
| File | XML | PDF (with embedded XML) |
| Human readable | needs a viewer | readable as a normal PDF |
| System processing | yes | yes |
| Typical use | often public sector / strict automation | often B2B where PDF is still needed |
| “One file for everything” | no | yes |
| Common pitfall | recipient requires a specific variant | PDF and XML differ |
When XRechnung is the better fit
- explicitly requires XRechnung
- expects XML via a portal/API
- doesn’t need a PDF representation
When ZUGFeRD is the better fit
- you still need a PDF for humans
- the recipient wants automation but keeps PDF workflows
- you want a single file that covers both use cases
What they have in common
Both aim to provide structured invoice data so systems can import, validate VAT and totals, and reduce manual work—based on EN 16931.
How E‑Rechnungs‑Studio helps
- generate structured invoice data from a PDF
- validate and understand issues
- apply fixes via plain language
- export XML (for XML‑only workflows)
- export ZUGFeRD PDF (hybrid workflow)
FAQ
Is ZUGFeRD “better” than XRechnung?
Not universally. The best choice depends on your recipient’s requirement and your delivery process.
Can I send ZUGFeRD to public sector recipients?
It depends on the portal/recipient rules. Some require XRechnung XML. Always check the specific requirement.
Do I need to support both formats?
Many companies start with ZUGFeRD (because it includes a familiar PDF) and add XRechnung when required.
Next step
If you’re unsure, generate a clean e‑invoice from your PDF and then export XML or hybrid PDF depending on your recipient.