Skip to main content
E-invoicingยท6 min read

ZUGFeRD vs XRechnung: The Difference, Explained

By Clozo Teamยท

ZUGFeRD and XRechnung are both German e-invoice formats built on the same EU standard, EN 16931. ZUGFeRD is a hybrid PDF with XML embedded inside it; XRechnung is pure XML. Send XRechnung to public authorities (B2G) and ZUGFeRD to private business clients (B2B).

A German client emails you: "Please send this as an e-invoice." No format named, no instructions. They just expect you to know what they mean.

Plenty of freelancers hit this moment and freeze. You've heard two intimidating words, ZUGFeRD and XRechnung, you assume you need a tax advisor to tell them apart, and you end up sending a normal PDF anyway, hoping nobody complains. If you bill German companies from elsewhere in the EU, the wording is in German but the rules trace straight back to a single European standard, so the logic is the same everywhere.

Here's the short version, and then the part nobody tells you: for most business clients you only ever need one of these. Let's sort out which.

ZUGFeRD vs XRechnung: same standard, two builds

So what is ZUGFeRD, and what is XRechnung? Both formats follow the same European standard, EN 16931. That's the rulebook that defines what counts as a structured electronic invoice. The difference is in the packaging.

ZUGFeRD is a hybrid. It's a normal PDF (technically PDF/A-3) that also carries a machine-readable XML file embedded inside it. So one file does two jobs: you and your client can read it like any invoice, and your client's accounting software can pull the data out automatically. Open it and it looks like a regular invoice. Under the hood, the structured data is right there.

XRechnung is pure XML. Instead of a traditional PDF invoice, it's structured data that business software exchanges and processes automatically, with no PDF layer at all. Because it's all data and no decoration, an XRechnung file is usually just a few kilobytes; a ZUGFeRD file is larger because the full PDF rides along.

Same standard, two philosophies. ZUGFeRD says "keep it human-readable too." XRechnung says "data only, no decoration."

When do you actually need which one?

This is where the panic usually disappears.

XRechnung is the B2G e-invoice format in Germany. If you invoice a federal ministry, a state authority, a city, or a public university, they typically require XRechnung, and many of their portals accept only that format. So if you do B2G work, XRechnung is the choice that's made for you.

ZUGFeRD is the practical choice for business clients (B2B). Your average GmbH, agency, or startup doesn't run a strict government portal. They want a file their software can read and a document a human can check. ZUGFeRD gives them both. For the everyday "please send this as an e-invoice" request from a private company, ZUGFeRD is almost always the right answer.

So the honest decision tree is tiny:

  • Invoicing a public authority? XRechnung.
  • Invoicing a private business? ZUGFeRD (and your client will be happy).
  • Invoicing a private individual (B2C)? A plain PDF is still fine. The mandate is about B2B.

For a fuller rundown of which file goes where, the e-invoice formats guide lays out each option side by side.

"But isn't this all mandatory now?"

Partly. Let's be precise, because the dates get confused everywhere.

From 1 January 2025, every German business must be able to receive a structured e-invoice (XRechnung or ZUGFeRD). That part is already live. So even if you only send PDFs today, a client can legally send you a ZUGFeRD file, and you're expected to handle it.

Issuing is being phased in:

  • Until the end of 2026, you can still send plain paper or PDF invoices to B2B clients.
  • From 2027, businesses with more than EUR 800,000 in prior-year turnover must issue e-invoices.
  • From 2028, all B2B businesses must issue them, including solo freelancers.

If you're a freelancer earning EUR 40,000โ€“90,000, your hard deadline to issue is 2028. The catch: clients are already asking you to send e-invoices now, well ahead of their own deadlines, because they've upgraded their systems. So in practice the "mandate" arrives at your door whenever your most organised client decides it has. If you also need to get the tax treatment right on cross-border work, the EU VAT guide covers reverse-charge for B2B clients with a valid EU VAT-ID.

How to create a ZUGFeRD invoice without specialist software

This is the question behind every "how do I make a ZUGFeRD invoice?" search, and the usual advice is grim: buy a full accounting suite, learn it, or hand the job to a tax advisor.

You don't have to. The embedded-XML part is exactly the kind of thing software should do silently in the background. You fill in your invoice the way you always have (client, line items, amount), and the tool generates the valid structured file for you. You shouldn't have to think about XML at all, and you certainly shouldn't be hand-editing it.

A quick reality check before you pick any tool:

  • Does it output a valid EN 16931 file, not just a PDF you renamed? (A renamed PDF is not an e-invoice.)
  • Does it handle the VAT correctly, including reverse-charge when you invoice a business in another EU country with a valid VAT-ID?
  • Can it produce both formats, so a B2G job doesn't send you back to square one?

A tool that ticks all three lets you stop worrying about the format and get back to billing. If you want to compare what's included before you commit, the pricing page lays out the plans in plain terms.

Where Clozo fits

This is the part Clozo can help with. You write the invoice once, and Clozo produces a valid ZUGFeRD file (the hybrid PDF + XML) or a valid XRechnung file (pure XML): your choice, one click, in the German format โ€” see pricing for the plans that include structured e-invoice formats. The EU VAT is calculated automatically, reverse-charge included, so you're not double-checking rates against a private business in Vienna or Amsterdam. The whole flow runs in one place, from proposal to finished invoice, with a legally-binding e-signature and an audit trail along the way, no specialist accounting licence and no XML by hand. You can see the full set of Clozo features if you want the wider picture.

To be clear about what that means: Clozo generates the correct file format for you, and then you send or upload it yourself (or hand it to your accountant). It doesn't file your taxes and it isn't a transport network: it doesn't connect to or submit through any government portal, B2G platform, or transmission network on your behalf. It's the tool that turns a normal invoice into a valid German e-invoice format on demand; getting that file to your client or their portal is your step.

So the next time a client writes "send it as an e-invoice," you'll know the answer in five seconds: business client, ZUGFeRD; public authority, XRechnung. And making either one should take about as long as writing a normal invoice ever did.

Create your e-invoice with Clozo and send a valid ZUGFeRD or XRechnung today.

Frequently asked questions

What is the difference between ZUGFeRD and XRechnung?
Both follow the same European standard, EN 16931. ZUGFeRD is a hybrid file: a normal PDF (PDF/A-3) with machine-readable XML embedded inside it. XRechnung is pure XML with no PDF layer. ZUGFeRD stays human-readable; XRechnung is data only.
Which format should I send my German client?
Invoicing a public authority (B2G)? Send XRechnung; their portals often accept only that. Invoicing a private business (B2B)? ZUGFeRD is almost always the right answer, because it is both machine-readable and human-readable. Invoicing an individual (B2C)? A plain PDF is still fine.
Is a renamed PDF a valid e-invoice?
No. A standard PDF you simply saved or renamed is not a structured e-invoice. To count under EN 16931 it must carry valid structured XML data, either embedded (ZUGFeRD) or standalone (XRechnung).

Create your e-invoice with Clozo

Create your e-invoice with Clozo

Related articles

ZUGFeRD vs XRechnung: The Difference | Clozo