Skip to content
caadoo
de

Automate outgoing e-invoices before Germany's 2027 deadline

German businesses with more than €800,000 in prior-year turnover must issue e-invoices to domestic business customers from 1 January 2027, and most others from 2028, though on the wording of the law a December 2026 supply billed in January 2027 can catch smaller firms too. A foreign parent doesn't change that. This piece covers who is caught, which file counts, and how to automate sending without letting a bad invoice out.

By T. Krause13 min read

To automate outgoing e-invoices in Germany, have your ERP or billing system generate an XRechnung or ZUGFeRD file from each posted invoice, run an automatic check against the rules of the standard, and send whatever passes. A person handles what the check holds back, plus corrections. The obligation starts on 1 January 2027 for businesses whose total turnover exceeded €800,000 in the previous year, and on 1 January 2028 for most of the rest. Those stages come from section 27(38) of the German VAT Act and the Federal Ministry of Finance's FAQ, dated October 2026.

Two limits apply to that second date. Small businesses under section 19 of the VAT Act are exempt, because section 34a of the VAT implementing ordinance lets them always send another kind of invoice. And below €800,000, the longer period covers only supplies made in 2027 on the wording of the law, so a December 2026 supply billed in January 2027 would already need an e-invoice. The FAQ doesn't address that case, so I treat it as an open reading in the traps below.

I read the FAQ and the ministry's letters in German, so the question and margin numbers below refer to the German text.

This is written for finance leads who read English first: the controller of a German GmbH inside an international group, or a managing director who inherited the German entity. If your questions are about invoices coming in, read e-invoice intake instead.

Photo: Unsplash

Does the rule catch your entity?

Three tests decide it, and a parent company abroad isn't one of them.

Is the seller established in Germany? Question 3 of the FAQ counts a business as domestic if it has its registered office, its management or a permanent establishment involved in the sale in Germany. A GmbH is in, even when its invoices are produced by a shared service centre in another country. A foreign business that is only VAT-registered in Germany, with no fixed establishment, is out, and the ministry says it can state that on its invoice to explain why no e-invoice is coming.

Is the customer a domestic business? Sales to consumers fall outside the rule. So do customers abroad. Public bodies that don't act as businesses fall outside the VAT rule, but they have their own e-invoicing law, and for federal bodies that means a separate portal and a routing ID. Keep those on their own track.

Does an exception apply? Invoices up to €250 gross don't need to be e-invoices, and many VAT-exempt sales, such as financial services and residential letting, aren't covered at all. A seller using the small-business exemption in section 19 of the VAT Act is exempt too, under section 34a of the implementing ordinance. It must still be able to receive e-invoices, and the rule reaches it from the day it moves to standard VAT.

For 2027 the turnover that counts is calendar year 2026. A company with 20 staff stays under €800,000 only if it turns over less than €40,000 per head, so most firms of that size or larger should plan for January 2027. Firms under the line should still read the December trap below.

If your entity is in a German VAT group (an Organschaft), don't test it alone. Margin number 64 of the ministry's letter of 15 October 2024 says to go by the turnover of the whole group ("auf den Umsatz des gesamten Organkreises abzustellen"), so a small company can be over the line because of the others in its group. Section 2(2) no. 2 of the VAT Act limits a VAT group's effects to the parts in Germany, so I read a foreign parent's own turnover as staying out of that count. The letter doesn't say so. Have your tax adviser confirm both whether your entity is in a VAT group and what counts.

What counts as an e-invoice

A PDF sent by email doesn't, whatever it looks like. The file must follow the European standard EN 16931, which is XML underneath. Question 7 of the FAQ names XRechnung and ZUGFeRD from version 2.0.1 as meeting the requirements, except for ZUGFeRD's MINIMUM and BASIC-WL profiles. Check which profile your software writes, because the name ZUGFeRD alone proves nothing.

ZUGFeRD is a PDF with the XML embedded, so a customer's clerk can still read it. XRechnung is XML alone, and your customer needs a viewer. For most commercial customers, I'd start with ZUGFeRD.

The XML is what counts. Question 7a requires every mandatory VAT detail to sit in the structured part, and a pointer to an attachment isn't enough. The ministry's letter of 15 October 2026 adds in margin number 12 that the type, scope and nature of the service, and its place where relevant, must be clear from those fields. Supporting detail such as timesheets can travel as an embedded attachment.

How the file reaches the customer is up to the two of you. Question 8 says the law prescribes no route, and lists email, an interface and portal download among the options. Peppol is one more option. Nothing in the VAT rules forces you onto it.

If you already use EDI

Some large customers already take invoices by EDI. Question 7 says the format can also be agreed between the two parties, as long as the mandatory details can be extracted correctly and completely. An EDIFACT link that meets that condition counts as an e-invoice, so the transition date below doesn't affect it.

If your link doesn't meet it, section 27(38) no. 3 still allows it until 31 December 2027, with the recipient's consent. So EDI customers can usually wait until 2027 is under way. One gap: no. 3 names only supplies made in 2027, while margin number 65 of the ministry's letter of 15 October 2024 is wider and covers any supply made by then. Ask your adviser about December 2026 supplies. Ask each one in writing which case applies, and put the answer on file.

How to wire it, starting from your billing system

Your route depends on what the system can produce. A native feature is the cheapest one to run. As one example, Microsoft's German e-invoicing page, dated 9 October 2026, says Business Central supports XRechnung, Peppol BIS 3 and ZUGFeRD from version 26.3, and that each Document Sending Profile holds one format. Its page on sales e-documents (25 September 2025) says that with service integration on, posting the invoice sends the file to the configured access point, and a failed send shows an error status that someone then has to clear and resend by hand. Ask your vendor the same questions: which version, which profiles, and where do failures appear?

If the system can export the data but can't write a valid file, a small converter between the export and the send step does the job. Someone then owns that converter when the standard changes, so settle who that is first. Automations that outlive the builder covers what to agree. A group ERP run from abroad can land here if it has no German add-on.

Whichever route you take, put the check before the send. The ministry recommends validating at creation and sending, in question 7, while saying validation isn't a legal condition and declining to recommend a tool. The KoSIT validator is open source under the Apache 2.0 licence and has public rule sets for XRechnung. Treat any failure as a stop. Margin numbers 22 and 23 of the October letter draw a line here. A broken business rule doesn't necessarily stop the file being an e-invoice for VAT purposes, but technically it no longer meets the standard, and your customer's system may refuse it.

None of this needs a language model. The data is already in your system and a fixed mapping writes it to the right field, so a model could only add errors to this step. AI earns its place around the edges, such as drafting clearer service descriptions for a person to approve or sorting customer replies in a shared inbox.

An invented example

This company doesn't exist. Picture a 70-person German subsidiary of a Dutch packaging group. Its invoices come out of the group ERP, run from a shared service centre in Rotterdam. It issues 1,100 invoices a month, of which 900 go to German business customers and 200 go to customers elsewhere in the EU.

The Rotterdam team first assumes the German rule doesn't reach them, because the system sits in the Netherlands. It does reach them, because the seller is the GmbH. Of the 900, 300 already go by EDI to twelve retail customers, and 600 go as PDFs by email.

They start with the 600. The ERP's German add-on writes ZUGFeRD, and the validator sits in the send step. A test batch shows that many lines say only "as per contract", so the German sales team rewrites those item texts. The twelve EDI customers get a letter asking whether the link meets the extraction condition, and until there's an answer the team relies on the transition to the end of 2027. The 200 cross-border invoices stay as they are.

Traps worth a calendar entry

December deliveries. Section 27(38) no. 1 allows paper and plain PDFs only until 31 December 2026, and only for supplies made before 2027. No. 2, the longer period for firms at or below €800,000, covers only supplies made after 31 December 2026. On that wording, a December delivery you bill in January 2027 falls under neither, so a firm below the line would need an e-invoice for it too.

That's a reading, not settled law. The FAQ doesn't address the case. Question 11 says only that the period runs to the end of 2027 at up to €800,000, and that a PDF needs the recipient's consent, and margin numbers 63 and 64 of the ministry's letter of 15 October 2024 repeat the two conditions without mentioning the year end. The tax advisory group ETL, opened on 3 November 2026, and the tax service Steuernaut, dated 26 October 2026, read it as I do. The Magdeburg chamber of commerce, dated March 2026, goes by the supply date alone and says the rule is extended to the end of 2027 for firms up to €800,000. You're safe if those invoices go out in December, or as e-invoices in January. Ask your tax adviser which applies to you.

Advance payments. Under margin number 2 of the October letter, a down-payment invoice issued before your obligation starts needn't be an e-invoice, even if delivery comes later. The final invoice then must be one. Until 30 June 2030 you may deduct the earlier payments as a total in field BT-113, with details in BT-22.

Corrections. Once the obligation applies, a correction must also be an e-invoice, says margin number 20, which adds that the invoice type for each kind of correction isn't technically settled yet. Keep corrections with a person who knows the case.

Retention. Question 13 requires a copy of every issued and received invoice for eight years, with the structured part intact. Section 147(3) of the Fiscal Code names the same period for accounting vouchers, and its fifth sentence keeps the period from ending while the invoice matters for a tax whose assessment period is still open. If your shared service centre archives only the PDF, fix that.

No fine, but a customer problem. Margin number 28 says that issuing another kind of invoice instead isn't an administrative offence. But question 12c gives your customer a civil claim to an e-invoice, and question 12b says the wrong format in principle doesn't support input VAT deduction. The same question gives three ways out, at least for now. You 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 format alone draws no objection where your customer could assume you were entitled to a transition rule. Expect their accounts team to ask anyway.

Where to start

Count one month of invoices by the three tests above, and find out which ZUGFeRD profile your system writes. What to automate first shows how to do the counting, and what AI automation costs shows what moves the price. This article summarises German law and administrative guidance. It isn't tax advice.

caadoo is a monthly subscription, and how it works explains the setup. A job like this one means I set up the output, put the check before the send, and leave your finance team with a list that shows only the exceptions. Tell me which system writes your invoices, and I'll say which route I'd take.

Frequently asked questions

When do German companies have to issue e-invoices?

From 1 January 2027 if total turnover in the previous year exceeded €800,000, and from 1 January 2028 otherwise, except that small businesses under section 19 of the VAT Act are exempt. Below €800,000, 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 rule applies to invoices between businesses established in Germany. Every domestic business has had to be able to receive e-invoices since 1 January 2025.

Does a German subsidiary of a foreign group have to issue e-invoices?

Yes, if the subsidiary is the seller and its customer is a domestic business. The test is where the seller is established, not where the ERP runs or who owns the company. A foreign business that is only VAT-registered in Germany, with no fixed establishment there, is outside the rule. A VAT group can move the date, though. If the subsidiary is in a German VAT group, the €800,000 test uses the whole group's turnover, under margin number 64 of the ministry's letter of 15 October 2024.

Is a PDF invoice an e-invoice?

No. A plain PDF has no structured data. ZUGFeRD looks like a PDF but carries embedded XML, and it counts from version 2.0.1, except in the MINIMUM and BASIC-WL profiles. Email itself remains an allowed route, as long as the attachment is a valid e-invoice.

Can I keep using EDI after 2027?

Yes, if the format lets the mandatory details be extracted correctly and completely, because the two parties may agree their own format. An EDI link that doesn't meet that condition can continue only until 31 December 2027, with the recipient's consent.

Do I have to use Peppol in Germany?

No. German VAT law prescribes no transmission route for invoices between businesses. Public bodies can set their own requirements.

Topics

  • E-invoicing
  • XRechnung
  • Accounts receivable
  • Automation
  • German Mittelstand
All articles

Keep reading

  • 11 min read

    How to automate quoting, and where a person still signs off

    Automated quoting rarely means one tool that does everything. It means price rules and templates in the CRM or ERP you already run, an AI draft where requests arrive as free text, and a named person who approves anything unusual before it reaches the customer. Here is how that splits across the quoting process.

  • 19 min read

    Microsoft 365 Copilot rollout checklist: 8 steps

    Copilot can find anything a person is allowed to open in Microsoft 365, and in most tenants nobody knows exactly what that is. This checklist puts the work before the first licence in order: permissions, data protection, works council, training, policy, pilot and measurement.

  • 12 min read

    Process documentation template: how to document a process

    Process documentation that people use fits on one page and describes the work as it is done today. Here is a template you can copy, seven steps for documenting a business process, a worked example from a 120-person manufacturer and the mistakes that leave these documents unread.

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