Last reviewed: September 3, 2026

Short answer

XRechnung is structured XML. It is the established choice for invoices to German public authorities and works well in automated accounting flows.

ZUGFeRD combines structured XML with a human-readable PDF/A-3 document. For German B2B invoicing, a ZUGFeRD file can qualify as an e-invoice when it uses an EN 16931-compatible profile and satisfies the applicable tax rules.¹²

Choose the format your recipient can process. If a public-sector buyer specifies XRechnung or a particular transmission route, follow that requirement. For B2B, do not assume that every file labelled “ZUGFeRD” is compliant: the selected profile, business data and validation result matter.

Important: a conventional PDF with no structured invoice data is not an e-invoice under Germany's post-2025 definition.¹

XRechnung vs ZUGFeRD at a glance

Decision point	XRechnung	ZUGFeRD
Container	XML only	PDF/A-3 with embedded XML
Human-readable view inside the file	No; a viewer renders the XML	Yes; the PDF is visible
Typical fit	German B2G, public procurement, automated exchange	B2B workflows needing both visual review and structured data
EN 16931 relationship	German CIUS based on EN 16931	Multiple profiles; use an EN 16931-compatible profile when compliance with that semantic model is required
Main risk	Sending valid XML through the wrong route or without buyer-specific identifiers	Selecting a profile that does not contain all data required for an EN 16931 e-invoice
Before sending	Validate the XML and check the buyer's routing rules	Validate both the embedded XML and the PDF/XML relationship; confirm the profile with the recipient

What is XRechnung?

XRechnung is Germany's Core Invoice Usage Specification (CIUS) for structured electronic invoices. The file contains machine-readable invoice data rather than a visual PDF. A receiving system can render that data for a person.

XRechnung supports the syntaxes documented by the specification, including UBL and UN/CEFACT Cross Industry Invoice (CII). Syntax alone is not enough: the document must also satisfy the XRechnung business rules.

When XRechnung is usually the safer choice

Your customer is a German federal, state or municipal authority.
Tender documents or the buyer explicitly require XRechnung.
Your workflow is designed for structured, automated processing.
Your customer has provided a routing identifier or portal requirement.

Public-sector acceptance and submission routes can vary by authority. Check the buyer's instructions instead of treating “B2G Germany” as one universal delivery workflow.³

What is ZUGFeRD?

ZUGFeRD is a hybrid invoice format. It places structured invoice XML inside a PDF/A-3 document, so the same file supports visual review and machine processing. ZUGFeRD and the French Factur-X standard are developed in close coordination.²

ZUGFeRD offers different profiles. They do not all carry the same semantic detail. If your goal is an EN 16931-compliant e-invoice, use a profile documented for that purpose and validate the result. A “Minimum” or other reduced profile should not be presented as universally EN 16931-compliant.

When ZUGFeRD is usually the practical choice

Your recipient wants a readable PDF and structured invoice data in one file.
Staff still review invoices visually while accounting software imports XML.
You exchange invoices with German or French partners using compatible ZUGFeRD/Factur-X workflows.
The recipient confirms the profile it can process.

Germany's B2B timeline: receiving and issuing are different

Germany changed the domestic B2B invoice framework on January 1, 2025. Businesses generally need to be able to receive e-invoices from that date, while transitional rules allow issuers to use other invoice forms for a limited period.¹

Period	Practical rule for domestic B2B issuing
Through December 31, 2026	Transitional alternatives remain available, subject to the statutory conditions
During 2027	An additional transition applies to issuers whose prior-year turnover does not exceed €800,000
From January 1, 2028	The general structured e-invoice requirement applies, subject to the law's scope and exceptions

This is not a blanket rule for every transaction. Small-value invoices, certain tax-exempt transactions and cross-border cases can follow different rules. Use the German Federal Ministry of Finance FAQ for the current scope and obtain professional advice for your own case.¹

For a deadline-focused explanation, read Germany B2B E-Invoicing: 2025–2028 Timeline.

How to choose in five checks

1. Is the customer a public authority?

Start with the authority's procurement or invoicing instructions. XRechnung is commonly required, but the accepted syntax, portal and routing information still need to match the buyer.

2. Which formats and profiles can the recipient import?

Ask for an explicit answer. “We accept electronic invoices” does not tell you whether the system accepts XRechnung UBL, XRechnung CII, ZUGFeRD, a specific profile or a particular transport network.

3. Does a person need to read the original file as a PDF?

If yes, ZUGFeRD may reduce operational friction. If the workflow is fully automated, XML-only XRechnung may be simpler.

4. Are all mandatory business fields available?

Gather seller and buyer identifiers, tax data, payment details, line-level quantities and prices, allowances or charges, and any buyer reference before generating the structured invoice. Missing or inconsistent data cannot be fixed by changing the filename.

5. Has the final file been validated?

Validate the exact artifact you will send. A PDF preview, an XML schema check or an “export successful” message alone does not prove that all applicable business rules are satisfied.

Common mistakes

Treating every PDF as an e-invoice

A PDF becomes part of a structured e-invoice workflow only when the required machine-readable data is present in a supported format. Emailing an ordinary PDF does not meet Germany's definition of an e-invoice.¹

Treating every ZUGFeRD profile as equivalent

Profiles have different data coverage. Match the profile to the legal and recipient requirements, then validate it.

Confusing format with transport

XRechnung and ZUGFeRD describe invoice artifacts. Peppol, a government portal, email and direct integrations are delivery channels. A valid format can still fail if sent through an unsupported route.

Relying on a version number copied from an old article

Specifications and validation bundles change. Before implementation, check the current XRechnung documents from KoSIT/XStandards Einkauf and the current ZUGFeRD package from FeRD.²⁴

Assuming software makes the transaction compliant automatically

Software can generate and validate data, but the supplier remains responsible for accurate invoice content, the correct tax treatment and the recipient-specific process.

Frequently asked questions

Is XRechnung mandatory for every German B2B invoice?

No. German rules require a qualifying structured format within their scope; XRechnung is one important option. An EN 16931-compatible ZUGFeRD profile can also be suitable for B2B. Recipient requirements and statutory exceptions still apply.¹

Is ZUGFeRD just a PDF?

No. It is a PDF/A-3 container with embedded structured XML. An ordinary PDF without that structured data is not ZUGFeRD.

Can I rename a PDF or XML file to make it compliant?

No. Compliance depends on the file structure, profile, invoice data and applicable business rules—not the extension or filename.

Can my customer request one specific format?

Operationally, customers and public buyers can specify formats and channels their systems support. Confirm these requirements before sending rather than assuming that every EN 16931-derived artifact is interchangeable.

Which version should I implement?

Use the release currently documented by the official maintainers and supported by your recipient. KoSIT publishes XRechnung documents and FeRD publishes ZUGFeRD packages; both can change after this article's review date.²⁴

Prepare the invoice data before structured export

Compliant Invoice can help you prepare and retain ordinary invoice data, create a professional PDF and check country-specific fields. It does not currently claim to generate or validate an XRechnung or ZUGFeRD artifact. Use a specialist structured e-invoicing tool or your recipient's portal for the final format and validation step.

Free keeps invoice data in this browser's local storage. Pro adds account-based cloud backup, multi-device access, premium templates and dashboards. The subscription does not turn a PDF into XRechnung or ZUGFeRD. Use the choices below to prepare an invoice with German field guidance or compare the annual SaaS plan.

Official sources

German Federal Ministry of Finance (BMF), Questions and answers on mandatory e-invoicing from January 1, 2025. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶
Forum elektronische Rechnung Deutschland (FeRD), ZUGFeRD / Factur-X standard and current downloads. ↩ ↩² ↩³ ↩⁴
Federal e-invoicing service, XRechnung FAQ. ↩
KoSIT / XStandards Einkauf, current XRechnung documents. ↩ ↩²

XRechnung vs ZUGFeRD: Which German E-Invoice Format?