E-Invoice Finder
Guide
ZUGFeRD in plain English
ZUGFeRD is useful when people still want a readable PDF but systems also need structured invoice data.
Germany guide · formats
ZUGFeRD vs XRechnung explained
Simple comparison of ZUGFeRD and XRechnung for German e-invoicing readiness, with software questions and checklist.
Quick verdict:
- German invoice format choice is often customer-driven: confirm whether buyers, especially public-sector customers, require XRechnung or will also accept ZUGFeRD.
- ZUGFeRD can reduce friction where teams still review PDFs, while XRechnung is better suited to XML-first processing and stricter machine-readable workflows.
- Before rollout, test invoice creation, receipt, validation, archiving, and search in the accounting software with real sample invoices.
Last checked: 7 June 2026Based on official sourcesClear summaryBusiness guidance, not legal advice
Official sources prioritized
Last-checked dates visible
Free checker, no signup required
What you need to know
Guide
XRechnung in plain English
XRechnung is a structured XML invoice format designed for machine processing and commonly discussed in public-sector invoicing.
Guide
How to decide
Ask your customers what they accept, then ask your software provider whether both creation and receiving workflows are supported.
Guide
Choosing between formats
The format decision is usually driven by recipient requirements, public-sector expectations, software support and archive workflow. Do not choose based on name recognition alone.
Guide
Software validation
A useful tool should not only export a file. It should validate required fields, help users fix errors and preserve the invoice in a searchable archive.
Guide
Practical question summary
For ZUGFeRD/XRechnung: German businesses often ask whether a PDF is enough, what E-Rechnung means, how ZUGFeRD differs from XRechnung, whether small businesses must prepare, and how accounting software should receive, validate and archive structured invoices.
Guide
Decision framework for businesses
For ZUGFeRD/XRechnung: The safest path is to confirm customer format requirements, test receiving structured invoices, validate sample files, verify archive/search and involve the accountant before changing the invoice setup.
Guide
Format testing plan
Ask customers for their preferred format, generate one ZUGFeRD sample and one XRechnung sample if your software supports both, then test validation, readability, archive and accountant export. The goal is not just to create a file but to prove the full workflow works.
Guide
How to use this guide
Use this guide to decide whether ZUGFeRD/XRechnung affects your Germany workflow and which evidence is still missing. Start with E-Rechnung receiving, ZUGFeRD and XRechnung formats, validation rules, then test receive a structured invoice and generate ZUGFeRD before comparing software.
Guide
Data and terms to prepare
For ZUGFeRD/XRechnung, the important terms are ZUGFeRD/XRechnung, Germany, E-Rechnung receiving, ZUGFeRD and XRechnung formats, validation rules, archive search, tax advisor handoff. Clean these fields in customer, supplier, tax and accounting records before rollout; otherwise validation and support issues appear during daily invoicing.
Guide
Software proof to request
For ZUGFeRD/XRechnung, ask vendors to show show E-Rechnung receiving, ZUGFeRD/XRechnung generation, validation, archive and tax advisor export using your examples. The demo should cover receive a structured invoice, generate ZUGFeRD, generate XRechnung, simulate a validation error and explain who handles errors, corrections, archive access and accountant handoff for E-Rechnung receiving, ZUGFeRD and XRechnung formats, validation rules.
Guide
Evidence before rollout
Keep official links, screenshots, test invoices and the decision reason for ZUGFeRD/XRechnung. For ZUGFeRD/XRechnung, the implementation file should prove how E-Rechnung receiving, ZUGFeRD and XRechnung formats, validation rules, archive search were checked, not just that a tool was selected.
Guide
Decision checkpoint
Do not close ZUGFeRD/XRechnung until someone can explain ZUGFeRD/XRechnung in Germany, name the workflow owner, show one tested invoice scenario and describe how the team avoids choosing software for Germany before proving the real ZUGFeRD/XRechnung workflow.
Checklist
Ask customers for accepted format
Check software export/import
Validate sample invoices
Confirm archive/search
Train invoice team
FAQ
Is ZUGFeRD better than XRechnung?
Not universally. It depends on the recipient requirement and software workflow.
Do I need both?
Many businesses may need to handle more than one format depending on customer mix.
What is ZUGFeRD?
ZUGFeRD is a hybrid invoice format combining a readable PDF with structured invoice data.
What is XRechnung?
XRechnung is a structured XML invoice format widely associated with German public-sector invoicing.
Which format is easier for SMEs?
ZUGFeRD can feel easier because of the readable PDF layer, but the right format depends on recipient requirements.
Can one software support both?
Many tools can support both, but you should verify creation, receiving, validation and archive features.
Is a ZUGFeRD PDF still machine-readable?
Yes, if it is correctly generated with embedded structured data. A normal PDF is not enough.
What should I ask customers?
Ask which structured format they accept and whether they have validation or portal requirements.
What do German businesses usually ask first?
For ZUGFeRD/XRechnung: They usually ask whether PDFs are enough, what ZUGFeRD and XRechnung mean, and whether their software can receive structured invoices.
What is the biggest E-Rechnung mistake?
For ZUGFeRD/XRechnung: The biggest mistake is treating the change as only a new export format instead of testing receive, validation, archive and accountant workflows.
How do I test ZUGFeRD and XRechnung readiness?
Create sample invoices, validate them, receive them in accounting software, archive them and confirm your accountant can process the data.
What should I test first for ZUGFeRD/XRechnung?
For ZUGFeRD/XRechnung, start with receive a structured invoice, generate ZUGFeRD, generate XRechnung because those scenarios reveal whether the workflow is practical.
What is the main risk for ZUGFeRD/XRechnung?
The main risk is choosing software for Germany before proving the real ZUGFeRD/XRechnung workflow.
Key regulations, formats and terms
GermanyE-RechnungZUGFeRDXRechnungEN 16931structured invoiceB2B e-invoicingaccounting softwareinvoice archiveSMEEuropean CommissioneInvoicingDirective 2014/55/EUstructured electronic invoiceVAT automationcross-border tradeZUGFeRD/XRechnung
Germany — Country hub
Open country hub →
Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.
Continue reading
Official sources
We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.