Germany’s e-invoicing mandate mentions two format names — ZUGFeRD and XRechnung — and most explanations don’t make clear that these solve different problems for different clients. Getting this wrong means either sending the wrong format to a government agency, or overbuilding for a requirement you don’t actually have.
The core difference
ZUGFeRD (and its French/EU twin, Factur-X) is a hybrid format: a normal-looking PDF with a machine-readable XML file embedded inside it. Open it and a human sees an invoice; feed it to accounting software and it reads the structured data automatically. It’s built for B2B and B2C invoicing — any client, human or software, can use the same file.
XRechnung is pure XML — there is no visual PDF layer at all. It’s not something a person opens and reads; it exists purely to be processed by software. It was built specifically for B2G (business-to-government) invoicing in Germany and has been mandatory for invoicing most federal and many state public sector bodies since 2020.
Both use EN 16931 as a foundation, but the difference is not just the container. XRechnung has additional requirements and validation rules. ZUGFeRD EXTENDED is a separate profile, not another name for XRechnung. ZUGFeRD also defines a distinct XRECHNUNG reference profile. See FeRD’s profile documentation and KoSIT’s XRechnung FAQ.
ZUGFeRD’s profiles
ZUGFeRD defines multiple profiles, each carrying more data than the last:
| Profile | What it carries |
|---|---|
| Minimum | Payment data only, no line items |
| Basic WL | Header-level totals, no full itemization |
| Basic | Partial line-item detail |
| EN 16931 (Comfort) | Full line-item tax detail, full payment terms, full addresses |
| Extended | Additional business data beyond EN 16931 for more complex processes; not XRechnung |
Billino uses the EN 16931 / Comfort profile for its hybrid PDFs. That does not automatically make them XRechnung invoices: the required profile and validation rules must match what the recipient accepts.
When you actually need XRechnung
Use XRechnung when your recipient requires it. It is widely used in German B2G (business-to-government) invoicing and can also be used for B2B invoices. For public-sector invoices, check the authority’s specific instructions:
- Confirm the accepted format. Federal guidance allows XRechnung and certain other compliant standards; an ordinary ZUGFeRD EN 16931 PDF is not automatically sufficient
- You need a Leitweg-ID from the agency — a routing code that tells the receiving system which department the invoice belongs to
- Use the required submission channel, which may be a portal, Peppol or an approved email channel
The federal e-invoicing FAQ explains accepted standards and submission channels. Requirements at state and local level can differ; confirm them with the recipient.
The practical rule
- Business client → agree the accepted format; ZUGFeRD / Factur-X at EN 16931 and XRechnung are both options
- Public-sector client → follow its format, buyer-reference and submission requirements; do not assume EXTENDED means XRechnung
For the broader picture on what the e-invoicing mandate requires and by when, see our e-invoicing guide.
In Billino
Every invoice Billino generates is automatically a ZUGFeRD / Factur-X file at the EN 16931 (Comfort) profile — the format that covers the overwhelming majority of freelancer and small-business B2B invoicing, and satisfies the private-sector mandate without you doing anything differently. If you need to check whether a specific file — yours or one a client sent you, including an XRechnung XML — actually meets the EN 16931 standard, use the free e-invoice validator for a field-by-field compliance report.