·11 min read·Facturwise Team

ZUGFeRD Invoices in English: A Guide for Non-German Speakers

ZUGFeRDE-InvoicingGermanyExpatFreelancerEN 16931Cross-Border Invoicing
ZUGFeRD Invoices in English: A Guide for Non-German Speakers

Why German Clients Are Suddenly Asking for a Different Kind of Invoice

If you work with German businesses and you have noticed a change in how they talk about invoices recently, you are not imagining it. Since January 2025, every VAT-registered business in Germany has been legally required to be able to receive structured e-invoices — meaning invoices that contain machine-readable XML data, not just a visual PDF. The requirement to send them is rolling out in phases through 2027 and 2028, but the receiving obligation is already active for every German B2B client you have.

For English-speaking freelancers, consultants, and small businesses working with German clients — whether you are an expat living in Germany, a UK contractor post-Brexit, a remote worker in the US or Australia, or simply a non-German EU business with German clients — this creates a practical problem. Most of the tools and guides that explain ZUGFeRD are in German, aimed at German businesses, and assume you are already familiar with the German tax system. If you are not, the terminology alone can make it feel unapproachable.

This guide cuts through that. You do not need to understand German tax law in depth to send a compliant ZUGFeRD invoice. You need to understand what ZUGFeRD actually is, what your invoice must contain, and how to generate one without navigating German-only software. That is exactly what this article covers.

What ZUGFeRD Actually Is — Without the Technical Jargon

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid invoice format. The simplest way to understand it is this: a ZUGFeRD invoice looks exactly like a normal PDF invoice when you open it. But embedded inside the file is a second, invisible layer — a structured XML data file that accounting software can read automatically.

Your German client's accounting system can extract invoice number, amounts, VAT details, your bank account, and all other data from the XML without anyone having to type anything manually. At the same time, the PDF remains fully readable for any human who opens it. One file, two representations.

The XML inside a ZUGFeRD invoice follows the EN 16931 standard — the European standard for electronic invoicing published by the European Committee for Standardization (CEN). This is the common foundation that makes ZUGFeRD valid not just in Germany but across the EU. A ZUGFeRD invoice at the EN 16931 profile level is simultaneously a valid Factur-X invoice in France. If you invoice clients in both countries, one setup covers both.

The current version of the standard is ZUGFeRD 2.4 / Factur-X 1.0.8, released in January 2026. Any compliant invoicing software should be generating this version or the immediately preceding ones — they are backward compatible.

Note: ZUGFeRD is for B2B invoicing between private businesses. If you invoice German government entities — federal agencies, ministries, municipalities — they require XRechnung, which is a different format (pure XML, no PDF). For all private sector German clients, ZUGFeRD is the right format.

The German E-Invoicing Timeline — What It Means for You Specifically

The German e-invoicing mandate was introduced through the Wachstumschancengesetz (Growth Opportunities Act) of March 2024, which amended §14 UStG. Understanding the timeline helps you know exactly where you stand right now.

What is already in force

Since January 1, 2025, every VAT-registered business in Germany must be able to receive structured e-invoices. This applies to all of your German B2B clients regardless of their size. They cannot refuse a ZUGFeRD invoice from you — they are legally required to accept it. This also means their accounting systems should already be capable of processing the XML data layer.

What is coming for senders

From January 1, 2027, businesses with turnover above €800,000 in the previous year must send structured e-invoices for domestic German B2B transactions. From January 1, 2028, all remaining businesses must send structured e-invoices — no exceptions based on size.

As a non-German freelancer or small business invoicing German clients, the sending obligation applies to you for domestic German B2B transactions if you have a German VAT registration. If you are invoicing from outside Germany as a cross-border service provider, the mandate technically governs domestic German transactions, but your clients will increasingly expect structured invoices regardless — the practical pressure is building well ahead of the legal deadlines.

The Kleinunternehmer exception

If you operate as a Kleinunternehmer under §19 UStG — meaning you are established in Germany with turnover below the €25,000/€100,000 thresholds and benefit from the VAT exemption — you are exempt from the obligation to send ZUGFeRD invoices. This exemption is permanently confirmed beyond January 2028. You must still be able to receive e-invoices from suppliers.

What Your ZUGFeRD Invoice Must Contain

ZUGFeRD invoices must include all the mandatory fields defined by EN 16931. For a standard B2B invoice from a non-German freelancer to a German client, this means the following.

Your seller information

  • Your full legal business name
  • Your complete postal address including country code
  • Your VAT identification number — for EU-based businesses this is your home country VAT ID (e.g. GB for UK, FR for France, NL for Netherlands). Include it even if you are not charging VAT
  • Your electronic address — typically your email address

Your client's information

  • Their full legal company name
  • Their postal address including country code DE
  • Their German VAT number (USt-IdNr.) — this is required for B2B cross-border EU invoices where the reverse charge applies. Always verify this through the EU VIES system before issuing the invoice

Document-level fields

  • A unique sequential invoice number — every invoice must have a number that has never been used before and follows a consistent sequence
  • The invoice date (Rechnungsdatum) — the date you issue the invoice
  • The date of supply (Leistungsdatum) — the date the work was actually performed or goods were delivered. This is a separate field from the invoice date and is legally required under §14 UStG. Many freelancers omit it; do not
  • The currency code (EUR for euro invoices)
  • Your payment details — IBAN and optionally BIC

Line items

Each service or product line must include a description, quantity, unit of measure, and unit price. Be specific — "consulting services" is not sufficient. "UX design consultation, 8 hours, week of 7 April 2026" gives the client's accounts payable team everything they need to match your invoice to an approved budget.

VAT treatment

This is where non-German invoicers most frequently make mistakes. The correct VAT treatment depends on your situation:

If you are EU-based invoicing a German VAT-registered business: The reverse charge mechanism under Article 196 of the EU VAT Directive applies. You invoice with zero VAT, include both VAT numbers, and add a note stating that the reverse charge applies. Your client self-assesses the VAT in Germany. See the VAT reverse charge guide for the full details on how this works and what to write on the invoice.

If you are UK-based post-Brexit invoicing a German business: The reverse charge still applies for B2B services under the same principle — VAT liability shifts to your German client. Your invoice should show zero VAT with a reverse charge note and your client's German VAT number.

If you are based in Germany and VAT-registered: You charge German VAT at 19% (or 7% for reduced-rate services) as normal and include your German USt-IdNr. on the invoice.

If you are a Kleinunternehmer in Germany: You issue without VAT and include the mandatory exemption note: "Kein Ausweis von Umsatzsteuer gemäß §19 UStG." The XML must correctly encode the VAT exemption reason code.

Note: Getting VAT treatment wrong in the XML data — even if the PDF looks correct — can cause your invoice to fail validation in your client's accounting system. The XML is what the machine reads, and it must match the visual document exactly.

Choosing the Right ZUGFeRD Profile

ZUGFeRD defines several data profiles that determine how much structured information is included in the XML. For compliance with the German B2B mandate, you need at minimum the EN 16931 profile — this is the only profile that satisfies the legal requirement. The lower profiles (Minimum, Basic WL, Basic) do not contain all the mandatory EN 16931 fields and are not sufficient for B2B compliance in Germany.

When evaluating invoicing software, confirm it explicitly states ZUGFeRD 2.4 or ZUGFeRD 2.x at the EN 16931 profile level. Vague claims of "ZUGFeRD support" or "e-invoicing compatible" may mean the software generates a lower profile that does not meet the German legal requirement. This is one of the most common traps for non-German businesses selecting invoicing tools without knowing what to look for.

The Extended profile is a superset of EN 16931 — it includes all mandatory fields plus additional optional fields. It is also compliant. If your software generates Extended profile, you are covered.

For a deeper explanation of all five profiles and how they relate to compliance, see the Factur-X and ZUGFeRD compliance guide.

How to Generate a ZUGFeRD Invoice Without German Software

The practical challenge for English-speaking invoicers is that most ZUGFeRD-capable software is built primarily for the German market, meaning the interfaces, help documentation, and customer support are in German. This creates friction for anyone who does not read German.

The good news is that ZUGFeRD is a format standard, not a national one. Invoicing software that generates correctly structured EN 16931-compliant ZUGFeRD output works regardless of what language the interface is in — and several tools support English interfaces natively.

When selecting a tool, check for these four things specifically:

  • Generates ZUGFeRD 2.x at the EN 16931 profile or Extended profile — not just Basic or Basic WL
  • English-language interface and support
  • Handles reverse charge VAT correctly in the XML (not just on the PDF)
  • Allows you to specify the date of supply separately from the invoice date
  • Does not require a German tax number or German address to function

The date of supply and reverse charge XML handling are the two fields that English-language generic invoicing tools most often get wrong. A tool may produce a beautiful PDF with the correct reverse charge note, but if the XML encodes the VAT incorrectly, your German client's system will reject it or misbook it.

Validating Your Invoice Before You Send It

Before sending your first ZUGFeRD invoice to a German client, run it through a validator. This confirms the XML structure is correct and that all mandatory EN 16931 fields are present and properly formatted.

The free Facturwise ZUGFeRD validator checks invoices against the EN 16931 standard field by field and shows specific errors in plain language. You upload the invoice file and get immediate feedback — no account required.

The validator checks the XML data inside the PDF, so you need to upload the actual ZUGFeRD file (the PDF with embedded XML), not a screenshot or print version. If your invoicing software is generating correctly structured output, the validator will confirm it. If something is misconfigured — a missing mandatory field, incorrect VAT category code, arithmetic inconsistency — the validator will show you exactly what to fix before the invoice reaches your client.

Common Mistakes Non-German Invoicers Make

Sending a plain PDF and calling it an e-invoice. A standard PDF is not a ZUGFeRD invoice regardless of how it is formatted. Your German client's system cannot extract data from it automatically. If they have automated accounts payable processing, a plain PDF will require manual intervention or may be returned.

Correct PDF, wrong XML. Some tools generate a PDF with the reverse charge correctly stated in the visual document, but the embedded XML encodes standard VAT instead. The PDF looks right to a human. The machine reads the XML and misbooks it as a VAT-charged invoice. Always validate the XML, not just the PDF.

Missing the date of supply. The Leistungsdatum is a separate mandatory field from the invoice date. Many international invoicers omit it because their home market does not require it. German tax law requires it on every invoice under §14 UStG.

Using the wrong profile. Generating a Minimum or Basic WL profile ZUGFeRD invoice and calling it e-invoice compliant. These profiles do not meet the EN 16931 requirement. Your client's validation system may reject them or flag them for manual review.

Not verifying the German VAT number. If you apply the reverse charge without verifying your client's USt-IdNr. through VIES and that number turns out to be invalid, you may be liable for the VAT you should have charged. Verify before issuing, and keep a record of the verification.

For a full breakdown of the e-invoicing mandate and what it means across the EU, see the e-invoicing deadlines by country overview.

A Practical Checklist Before Sending Your First ZUGFeRD Invoice

Use this before sending any ZUGFeRD invoice to a German client:

  • Invoice generated at ZUGFeRD EN 16931 profile or Extended profile
  • Your VAT number or reverse charge basis clearly stated
  • Your client's German USt-IdNr. verified via VIES and included
  • Reverse charge note included if applicable — both on PDF and correctly encoded in XML
  • Date of supply (Leistungsdatum) present as a separate field from invoice date
  • Line item descriptions are specific and unambiguous
  • Invoice number is unique and follows your sequential numbering
  • IBAN and BIC included in payment details
  • Invoice validated through the ZUGFeRD validator before sending

Frequently Asked Questions

Do I need to send ZUGFeRD invoices to German clients if I am based outside Germany?

If your German client is a VAT-registered business in Germany, they have been legally required to accept structured e-invoices since January 2025. While there is currently no obligation for you to send ZUGFeRD until the sending mandate applies to your situation, many German businesses now expect or prefer it — and some larger companies will reject plain PDFs outright. Sending a ZUGFeRD invoice ensures your invoice is processed without friction.

Can I create a ZUGFeRD invoice in English even if my client is German?

Yes. ZUGFeRD is a technical format standard, not a language standard. The invoice can be in any language — English, German, French, or any other. What matters is that the embedded XML data is correctly structured according to the EN 16931 standard. Your German client's accounting software reads the XML data layer, not the visual PDF language.

What is the difference between ZUGFeRD and XRechnung?

ZUGFeRD is a hybrid format — a PDF with embedded XML. Your client can open it like a normal invoice. XRechnung is pure XML with no visual layer, designed exclusively for invoicing German government entities. For invoicing private German businesses, ZUGFeRD is the practical choice. You only need XRechnung if you invoice federal, state, or municipal government bodies in Germany.

Do I need a German tax number to issue a ZUGFeRD invoice?

Not necessarily. If you are based outside Germany and invoicing a German business, the reverse charge mechanism under Article 196 of the EU VAT Directive typically applies. You invoice without German VAT, include both VAT numbers, and add a reverse charge note. You do not need a German Steuernummer for this type of cross-border B2B invoice.

What happens if my German client rejects my plain PDF invoice?

German businesses with automated accounts payable systems may return plain PDFs because their system cannot extract the structured data automatically. From January 2027 for larger businesses and January 2028 for all businesses, the sending obligation means your invoice must be structured. Getting ZUGFeRD-ready now avoids this problem entirely.

Is ZUGFeRD the same as Factur-X used in France?

Yes, from version 2.1 onwards ZUGFeRD and Factur-X are technically identical — same XML structure, same EN 16931 profile, same PDF/A-3 container. If you invoice clients in both Germany and France, one compliant invoicing setup covers both markets simultaneously.

Can I validate my ZUGFeRD invoice before sending it?

Yes. You can upload your invoice to the free Facturwise ZUGFeRD validator which checks the embedded XML against EN 16931 field by field and shows specific errors. Running a validation before sending your first ZUGFeRD invoice to a German client confirms everything is correctly structured.

Does the ZUGFeRD sending mandate apply to Kleinunternehmer?

Kleinunternehmer — businesses operating under the §19 UStG VAT exemption in Germany — are exempt from the obligation to send ZUGFeRD invoices. This sending exemption is confirmed beyond January 2028 by the Jahressteuergesetz 2024. They must still be able to receive structured e-invoices from suppliers.


Facturwise generates ZUGFeRD 2.4 and Factur-X 1.0.8 compliant e-invoices automatically at the EN 16931 profile level — in English, with no German required. Every invoice includes correctly structured XML for reverse charge, Kleinunternehmer exemption, and standard VAT scenarios. The same account works for German and French clients. Create your first compliant invoice for free.

This article reflects the e-invoicing rules and mandate timelines in force as of April 2026. Tax and compliance regulations can change — if you are uncertain about your specific situation, consult a qualified tax advisor in your country of registration.