ZUGFeRD is the hybrid German e-invoice format: a normal-looking PDF with an embedded XML file that carries the invoice data in a structured form. Together with XRechnung, a pure XML file, it is one of the two formats German businesses mostly use for the e-invoices that German VAT law is phasing in for domestic B2B invoicing. You do not create either in Word. You create them in software that writes the structured file: your invoicing tool once the e-invoice feature is switched on, a free tier such as sevDesk's free plan with three e-invoices a month or Accountable's free invoicing plan, a free online generator such as PDF24's, or, for invoices to German federal authorities only, the government's web entry form on its invoice platform. Developers can use the open source library Mustangproject. Then you validate the file and send it by email (as of November 2026, according to the providers).
Who has to send e-invoices and from when is covered in German E-Invoicing: Dates and Exemptions; this article is only about the how, under German law. In my business no invoice starts as a loose PDF. It starts in the invoicing tool: Anton, my AI employee for quotes and invoices, creates it as a draft in Lexware Office after a client says yes, and the e-invoice format comes from Lexware Office, not from Anton. This is not tax advice.
Why a Word or PDF invoice no longer counts
German VAT law (section 14 (1) UStG) now separates two kinds of invoice. An electronic invoice is one "issued, transmitted and received in a structured electronic format" that allows electronic processing. Everything else, including a PDF saved from Word, is an "other invoice".
The Federal Ministry of Finance (BMF) adds a second point: every mandatory detail has to be in the structured part. Pointing to an attached PDF is not enough. Your old template is not useless, though. For private customers, for small businesses under the German small business scheme and for invoices up to 250 euros you may keep using it; the Free German Invoice Template and German Small Business Invoices: The Rules cover those cases.
ZUGFeRD or XRechnung: which format to create
According to the BMF, both formats meet the legal requirements, ZUGFeRD from version 2.0.1 and excluding the MINIMUM and BASIC-WL profiles. Which one you use is something you agree with your customer. In practice this rule of thumb works:
ZUGFeRD is published by the Forum elektronische Rechnung Deutschland (FeRD) and corresponds to the French Factur-X; the current version is 2.5.2 of 4 August 2026. XRechnung comes from the German Coordination Office for IT Standards (KoSIT), and version 3.0 stays in force until at least 31 July 2027. Lexware Office, for example, needs a routing ID and a supplier number on the contact for an XRechnung according to its help pages, and neither for a ZUGFeRD invoice.
How to create a ZUGFeRD invoice in six steps
This is how it works in the common German invoicing tools; the menu names come from their help pages.
- Switch the feature on. Lexware Office: Settings, E-Rechnung tab, admin rights required, from plan M. sevDesk: the E-Rechnung toggle on the invoice or on the contact. Papierkram: Settings, document templates, E-Rechnung tab, format "PDF/A und E-Rechnung".
- Complete your company data. sevDesk requires your VAT ID, Lexware Office your tax number or VAT ID, and Papierkram also your phone number for XRechnungen to authorities. Add your bank details and an email address too.
- Set the customer up as a company. E-invoices go to businesses; Lexware Office does not create them for private persons. The buyer reference field (BT-10) does not need a routing ID between businesses: the BMF says a placeholder such as "-" is enough, and sevDesk fills it in for you. Only authorities need the routing ID there.
- Describe each line clearly. The structured part has to show what was supplied, so that VAT rate, place of supply and input tax deduction can be checked. Time sheets and other details may travel as an embedded attachment. Work with net prices, more on that below.
- Generate and validate the file. Create the XML file or the ZUGFeRD PDF and run it through a validator before it leaves (see the validation section below).
- Send and archive. Between businesses the law does not prescribe a channel, email is fine. Public authorities take invoices through their own platform; for the federal administration that is the OZG-RE, which needs a one-time free registration. You keep the invoice for eight years (section 14b (1) UStG), and what counts is the structured part. How a filing system for that looks is in Digital Receipt Filing That Holds Up.
Free ways to create a German e-invoice
If you only send a few invoices to business customers, you can do without a subscription. All details are provider statements as of November 2026, not from my own testing.
An online generator leaves three jobs with you: the sequential invoice number, the eight-year archive, and the fact that customer data goes to someone else's server; PDF24 states servers in Germany and deletion after one hour. Once you invoice regularly, software pays off: Lexware Office plan M costs 12.90 euros and sevDesk's invoicing plan 11.90 euros a month plus VAT on monthly billing. The wider comparison, including accountant access and export formats, is in Accounting Software for Small Businesses.
How to validate the file before it goes out
Validation checks whether a file meets the format of the EN 16931 standard and its business rules. According to the BMF it is not a condition for the invoice to count for tax purposes, but it is sensible and recommended at the point of creation. The ministry does not recommend any particular tool. These exist:
- KoSIT Validator: the official validation engine for XRechnung, open source under the Apache licence. It runs in Java from the command line with the matching validation configuration, so it suits technical users.
- PDF24 e-invoice check: according to the provider it checks XRechnung, ZUGFeRD, Factur-X and Peppol files "with the official rules" and explains errors in the browser.
- Mustangproject: reads, writes and validates, as a command line tool or library.
The tax administration's e-invoice viewer at e-rechnung.elster.de displays XRechnung and ZUGFeRD files. With ZUGFeRD, compare the result with your PDF: if the two differ, the BMF says the structured part prevails. What a format error means for tax purposes, compared with a business rule error, is answered in the FAQ of the obligation article.
Common mistakes when creating e-invoices
- Gross prices. Invoices built on prices including VAT can produce rounding differences. For e-invoices issued until 31 December 2027, the tax authorities accept a structured part with only the totals per VAT rate if the individual lines are in a readable attachment that the structured part refers to. Simpler: work in net prices.
- Mandatory details only in the attachment. What is mandatory belongs in the XML data, not in the attached PDF.
- Wrong ZUGFeRD profile. MINIMUM and BASIC-WL are not enough. If your software offers a profile choice, pick neither.
- Corrections on paper. Where the obligation applies, a correction has to be an e-invoice too, using the invoice type for a correction.
- Payments on account in the final invoice. Until 30 June 2030 you may deduct received instalments as a total in the "Paid amount" field and list the details in the invoice note, or put them in an embedded attachment that the structured part refers to. How such an invoice is structured is shown in Contractor Invoice: Template, Final Invoice.
Where AI helps, and where it should not
The e-invoice itself should come from the invoicing software, not from an AI: number sequence, immutability and format all live there. What AI can take over is the work before it. In my business Anton builds the quote from an evaluated first call and, once the client agrees, creates contact, quote and invoice as drafts in Lexware Office. He never sets a price without a source, nothing is finalised without my clear yes, and approval and sending stay with me. The full picture is in Writing Quotes and Invoices with AI, the API side in Lexoffice Integration: The Main Routes.
Whether your setup needs extra fields differs from business to business. For your individual case, that's something we'll look at together.
Frequently asked questions
Can I create an e-invoice in Word or Excel?
No. Neither writes a structured format under EN 16931; a PDF saved from them is an "other invoice".
Can I convert a PDF invoice into a ZUGFeRD invoice?
With tools, yes: according to the provider, PDF24 reads a PDF invoice with AI and pre-fills its e-invoice form. Check every recognised field, because from then on the XML data counts, not your PDF.
Do I need a routing ID (Leitweg-ID)?
Only for invoices to public authorities. Between businesses, the BMF says a placeholder such as "-" in field BT-10 is enough. As the issuer you never need a routing ID of your own.
Can Kleinunternehmer (VAT-exempt small businesses) create e-invoices voluntarily?
Yes, with the same tools as above, if the customer agrees. There is no obligation; the rules for Kleinunternehmer are in German E-Invoicing Mandate: Dates, Exemptions.
Do I have to validate every e-invoice?
It is not required, but it is recommended. Lexware Office, for instance, shows which details are still missing before you finalise, according to its help pages; with online generators and in-house tools it pays to run every new template and every new customer through a validator.
Where to go from here
Write down whom you will invoice next year: authorities, business customers, private customers. Get the routing ID for each authority and ask your business customers whether they need a particular format or reference. Then switch on e-invoicing in your software, send a test invoice to yourself and run it through a validator.
I collect more workflows like this under process optimisation. Anton is available as a ready-made package with a course in my community, the AI Employee Framework.
Your first AI employee up and running within an hour
Join the community$5/month founding price, first 50 members