Skip to content
caadoo
de

E-invoice automation for XRechnung and ZUGFeRD

You can automate e-invoice intake in Germany from the inbox to the archive, because every supplier who switches to XRechnung or ZUGFeRD sends the invoice as finished data. This article goes through it step by step: what the software takes over, what stays with a person, and what no automation fixes.

By T. Krause16 min read

You can automate e-invoice intake in seven steps. Every invoice arrives at one address. Software works out whether the file is an XRechnung, a ZUGFeRD invoice or a plain PDF, validates the XML, matches it against the purchase order and the supplier master, and proposes the booking. It then sends the invoice to whoever may approve it and archives the original. What stays with a person is the approval, and any invoice where something doesn't add up.

Here is an invented example of the opposite: a machine builder with 120 people. One of its suppliers sends a ZUGFeRD invoice, which is a PDF with a machine-readable XML file tucked inside it. Someone in accounts opens the PDF, reads it on screen, and types the invoice number, the net amount, the VAT and the due date into the accounting system. The XML file, which already contains every one of those values, is never opened. Nobody at the company knows it is there.

The company breaks no rule by working this way. Since 1 January 2025, every domestic business in Germany has to be able to receive e-invoices. The Federal Ministry of Finance's e-invoice FAQ, in German, last revised October 2026, says an email inbox is enough, so a firm that changed nothing was compliant on day one.

Compliant, and missing the one useful thing the rule hands it. An e-invoice is a data record. The supplier has already done the data entry. If you are ever going to automate invoice intake, this is the cheapest moment you will get, and the rules explain why the volume is about to jump.

Photo: Unsplash

German e-invoice rules: what applies since 2025 and what starts in 2027

Receiving is already mandatory. Under section 14 of the German VAT Act, an e-invoice is an invoice in a structured electronic format that allows electronic processing. The format has to follow the European standard EN 16931. Sender and recipient may agree on another, such as EDI, if the mandatory data can be extracted correctly and completely into a format that meets the standard or is interoperable with it. Two formats dominate in Germany. XRechnung is pure XML, readable by software and close to unreadable for a person without a viewer. ZUGFeRD, from version 2.0.1, is the hybrid, a PDF with the XML embedded. Its MINIMUM and BASIC-WL profiles do not qualify.

Issuing is being phased in. Until 31 December 2026, under section 27(38) of the VAT Act, any business may still send paper, or a plain PDF if the recipient agrees, for supplies made by then. From 1 January 2027, businesses with more than €800,000 turnover in the previous year must issue e-invoices. From 1 January 2028, most of the rest must, and until then the extra year covers only supplies made in 2027. For your inbox, that means your larger suppliers switch in January. Invoices up to €250 gross stay exempt under section 33 of the VAT Implementing Regulation, and so do invoices from small businesses in the Kleinunternehmer scheme under section 34a. For your own invoices, read automating outgoing e-invoices.

A PDF attached to an email is not an e-invoice. The ministry calls it an "other invoice", because it has no structured format. While the sender is still allowed to issue one, it remains a valid invoice for input VAT deduction. Once the transition periods end, it no longer does the job between two German businesses.

The year of supply counts too, and that reaches your input VAT. Section 27(38) ties each period to when the supply was made. No. 1 allows paper and plain PDFs until 31 December 2026, for supplies made before 2027. No. 2, the longer period for suppliers at or below €800,000, runs until 31 December 2027, for supplies made in 2027. On that wording, a December 2026 delivery billed on paper or as a PDF in January 2027 falls under neither, even when the supplier is small. That's a reading, not settled law, because the ministry's FAQ doesn't address the case. Automating outgoing e-invoices lists who reads it which way. After 31 December 2027, section 27(38) no longer covers paper or plain PDFs at all.

Question 12b of the FAQ says an invoice in the wrong format in principle gives no input VAT deduction, then names three ways out, at least for now. The supplier can issue a later e-invoice that refers specifically to the original and corrects it retroactively. Without a correction, an accurate and complete invoice can serve as objective proof under a strict test. And the authorities won't object to the format alone if the information you had let you assume the supplier could use a transition rule. You needn't research beyond a prudent merchant's care, but what you know counts: last year's turnover with that supplier, its known size, anything you know through linked companies. Margin numbers 56 to 59 of the ministry's letter of 15 October 2024 say the same.

For your inbox, that gives two cases. If a supplier you know to be large sends a plain PDF for more than €250 in 2027, ask for the e-invoice. Question 12c gives you a civil claim to it. For a small supplier's December invoice arriving in January 2027, I read the third way out as your possible protection, because question 11 gives the end of 2027 without mentioning the year of supply. The ministry hasn't confirmed that, and the supply date is on the invoice. Ask your Steuerberater, your external tax adviser, what applies to you, and ask the supplier for the later e-invoice where the VAT amount is large enough to matter.

Processing XRechnung and ZUGFeRD automatically: read the XML, not the picture

The machine builder above treats a hybrid invoice like any other PDF and either retypes it or runs text recognition over the image. Both throw away what the supplier sent.

The XML is the invoice. For hybrid formats like ZUGFeRD, the ministry says the structured part is the leading one. If the PDF view and the XML disagree, the XML counts. Reading only the PDF means reading the half that loses the argument.

The XML can be checked by a machine. A scanned page can only be looked at. An XML file can be tested against rules before anyone touches it. Do the line items add up to the total? Is the VAT amount right? Are mandatory fields missing? KoSIT, the German public body that maintains XRechnung, publishes a free open source validator. An invoice that fails it goes back to the supplier before it costs your accounts team a minute.

The purchase order number has its own field. EN 16931 defines fields for the order reference and the delivery. When a supplier fills them, you stop hunting for the PO number in a free text line, and that single field is what makes the next step possible.

E-invoice automation in seven steps, from inbox to archive

Here is an intake process that a company with 20 to 250 people can put together without an enterprise platform. The article on what AI automation costs covers the price. Each step names the software's part and the person's.

1. Receipt. Every invoice goes to one mailbox, something like invoices@ at your domain. It is printed on every purchase order and stored in the supplier master data. The software collects every attachment from it. A person forwards invoices that land in a buyer's personal inbox and asks the supplier to update the address. Some suppliers only post invoices to a download portal, which the ministry accepts as a delivery route. A scheduled job or a person with a fixed slot collects them. If invoices still arrive through info@, shared inbox triage moves them over.

2. Format detection. The software tells XRechnung and ZUGFeRD apart from plain PDFs and scans. It reads the XML out of the first two and sends the rest through text recognition, which a person checks. Anything that isn't an invoice, a payment reminder for example, goes to that person too.

3. Validation. The software validates the XML against the format and the business rules of the standard, looks for duplicate invoice numbers, and stores the validation report. Under the ministry's letter of 15 October 2025, a file with format errors is not an e-invoice but an "other invoice". A person decides whether it goes back to the supplier. The same letter says validation does not replace your duty to check that the invoice is complete and correct. An invoice with the wrong VAT rate can still pass.

4. Matching. The software compares the bank details with the supplier master. A changed IBAN on an invoice is a classic fraud attempt. That invoice stops, and someone calls the supplier on the number you already had. Using the order number, the software pulls the purchase order from your ERP and the goods receipt next to it. If quantity and price match within a tolerance you set, the invoice has passed its factual check. If not, it goes to the person who ordered, with the exact gap: "Invoice says 120 units, goods receipt says 100."

5. Booking proposal. From the purchase order and earlier bookings for the same supplier, the software proposes the account, the cost centre and the tax code. Accounts confirms or corrects it. The first invoice from a new supplier gets booked by hand.

6. Approval. Write the approval rules down once. Who can approve up to which amount, on which cost centre? The software sends the invoice to the right person, reminds them, and records who approved and when. The approval itself stays with a person. It is one click in an email or in Teams. Nobody forwards a thread titled "please check". The approved invoice goes to your accounting software or to your tax adviser, together with the booking data. In Germany that often means DATEV, the software many tax advisers work in. Ask your adviser how and in what form they want the documents before you build anything. That one conversation saves you a rebuild.

7. Archive. Section 14b of the VAT Act requires you to keep every invoice for eight years, counted from the end of the calendar year in which it was issued. Section 147(3) of the Fiscal Code, the Abgabenordnung, sets the same eight years for accounting vouchers, the Buchungsbelege. Under its fifth sentence the period does not run out as far and as long as the documents matter for taxes whose assessment period has not expired. For an e-invoice, at least the structured part has to be kept intact in its original form. Since the amendment of 14 July 2025 to the GoBD, Germany's rules for digital bookkeeping and archiving, the XML alone is enough for hybrid invoices, unless the PDF part carries additional or deviating information that matters for tax, such as booking notes. The software stores the original file unchanged, with the validation report and the approval record. A preview it renders from the XML does not replace the original file. A person spot-checks that what reached the mailbox also reached the archive.

What automation does not fix

Wrong master data. If the supplier master holds an outdated IBAN, or the same supplier twice, the software stops correct invoices or lets wrong ones through. Clean it up before matching goes live.

Orders without an order number. A purchase made over the phone leaves nothing to match an invoice against. They all end up with the person who ordered.

Disputes about substance. Whether the goods arrived damaged or the contractor worked the hours on the invoice is not in any XML file. Two people sort that out on the phone.

Where to start on Monday

I would not start by choosing software. I would start with a list.

Sort your suppliers by format. Take the last three months of incoming invoices and note, per supplier, how they arrive: XRechnung, ZUGFeRD, plain PDF or paper. Add the count. One afternoon tells you how much of your intake is already structured and who sends the rest.

Start with the suppliers who send the most. Automation pays where the same sender produces many invoices every month. The electrician who services the building once a year can stay manual.

Write to the PDF senders now. Ask them to switch to XRechnung or ZUGFeRD today, with the order number in the field meant for it. The larger ones have to by January 2027 anyway. If they switch now, they test with you instead of in a panic.

Treat paper as the exception. Paper stays legal for everyone until the end of 2026 for supplies made by then, and for smaller suppliers until the end of 2027 for supplies made in 2027. Scan it in one place, where the post comes in, and push the scan into the same process. Text recognition reads it and a person checks it. From January 2027 that person also looks for two things on paper and plain PDF invoices: a 2026 supply date, and a supplier you know to be large. The rules section above covers both. That route is slow, and it can afford to be, because it keeps getting smaller.

Build the purchase order match first. Reading the XML is the easy part. The time in accounts goes into chasing who ordered something and whether it arrived. Automate that step and the chasing is what goes away.

The mandate forces your suppliers to send you data instead of pictures. What you do with that data is up to you. Print the XML so someone can retype it, and you have met the law and thrown away the only part worth having.

caadoo builds processes like this on a subscription. Send me a note on how your invoices arrive today, and I'll tell you which step I'd start with.

Frequently asked questions

Is e-invoicing mandatory in Germany?

Yes, for invoices between businesses established in Germany, and it arrives in stages. Every such business has had to be able to receive e-invoices since 1 January 2025. Issuing becomes mandatory on 1 January 2027 for businesses whose turnover in the previous year was above €800,000, and on 1 January 2028 for the smaller ones. Below that line the longer period covers only supplies made in 2027 on the wording of the law, so a December 2026 supply billed in January 2027 may already need an e-invoice. The ministry's FAQ doesn't address that case, so ask your tax adviser. The duty is in section 14(2) of the German VAT Act, the UStG, and the transition periods are in section 27(38). Invoices to consumers are outside it. The exemptions for small amounts and for the Kleinunternehmer scheme are in the rules section above.

Does the German e-invoice mandate apply to a foreign company?

Only if it is established in Germany. Section 14(2) UStG requires an e-invoice only when supplier and customer are both established in Germany. That means a seat, a place of management or a fixed establishment that takes part in the transaction. A German subsidiary is covered, and so is a branch for the transactions it takes part in. A foreign company registered for German VAT without a fixed establishment is not. The Finance Ministry's e-invoice FAQ, last revised October 2026, says it can state that on its invoice to explain why it sends no e-invoice. Have your tax adviser confirm which side your entity is on.

Is a PDF invoice still valid in Germany?

For now, yes, but it is no longer an e-invoice. Since 1 January 2025 a plain PDF counts as an "other invoice", like paper, because section 14(1) UStG defines an e-invoice by its structured format. Under section 27(38), a supplier may keep sending PDFs with the recipient's consent until 31 December 2026 for supplies made by then, or, for supplies made in 2027, until 31 December 2027 if its previous-year turnover was €800,000 or less. The Finance Ministry's FAQ says such an invoice still supports input VAT deduction while the supplier may issue it. ZUGFeRD from version 2.0.1 looks like a PDF but carries the XML inside, so it does count, except in its MINIMUM and BASIC-WL profiles.

XRechnung or ZUGFeRD: which one is easier to process automatically?

Neither. Both carry the invoice data as XML under the European standard EN 16931, and that XML is what software reads and validates. An XRechnung is the XML and nothing else, so a person needs a viewer to read it. ZUGFeRD puts the XML inside a PDF that anyone can open. That helps while people in your company still want to look at an invoice. If the PDF and the XML disagree, the German Federal Ministry of Finance, the BMF, says the XML counts. Ask suppliers for whichever format their system already produces, and for the purchase order number in its own field. The match against the order depends on it.

Do German e-invoices have to go through a government portal?

Between businesses, no. The Finance Ministry's FAQ says the law prescribes no transmission route. Email and a download from the supplier's portal are both accepted, and which one a supplier uses is a matter for the contract between you. For receiving, the ministry says an email inbox is enough. That is why the intake above starts with one dedicated mailbox that software empties. Invoices to federal authorities follow a separate regulation, the E-Rechnungsverordnung, with its own portal.

How long do e-invoices have to be kept in Germany, and where?

Eight years under section 14b(1) UStG, from the end of the calendar year of issue. Section 147(3) of the Fiscal Code, the Abgabenordnung, names the same period for accounting vouchers, the Buchungsbelege. Its fifth sentence keeps the period from ending while the invoice matters for a tax whose assessment period is still open. The e-invoice FAQ of the German Federal Ministry of Finance, the BMF, requires at least the structured part, the XML, intact in its original form. A printout doesn't replace it. Section 14b(2) has a business established in Germany keep its invoices there. An electronic archive may sit elsewhere in the EU if it allows full online access and download, and you must tell the tax office where. Outside the EU, section 146(2b) of the Fiscal Code applies.

Topics

  • E-invoicing
  • Accounts payable
  • Finance
  • Automation
  • German Mittelstand
All articles

Keep reading

  • 8 min read

    Shared inbox triage with AI: a person hits send

    Every company has an info@ or service@ address that someone sorts by hand each morning, with orders buried between newsletters and complaints waiting behind invoices. A language model can read, classify and draft replies there, as long as a person approves every send. This is how to set it up, what to log, and what data protection requires in Germany.

  • 7 min read

    What to automate first: count for one week

    Most companies pick their first automation by whatever sounds best in the management meeting. The better answer comes from a tally sheet your team keeps for one week. This piece covers how to count, how to choose, and how to fit the brief for the first build into a single paragraph.

  • 9 min read

    How to automate quote follow-up, and when to pick up the phone

    An open quote sits until someone remembers it. The CRM can track status, set reminders, create tasks and prepare follow-up emails, and a language model can draft the email from the last conversation. Calls and negotiation stay with sales. Here is a sample cadence to adapt and the setup in five steps.

End of call

You can hang up now.

Or book 15 minutes. I'll ask you the questions I'd ask on the phone, and tell you at the end whether it fits. If it doesn't, we've both lost a quarter of an hour instead of a month.

Or call. Cold, if you like. My AI assistant picks up and I call you back. +49 5136 9414999

Analytics

With your consent I use Google Analytics to see which pages get read. Without it, no analytics code loads. Your answer is stored locally in your browser.

Privacy notice