AiStaffo

Germany e-invoices from 1 January 2027: a readiness checklist

Stock photo: desk, printed invoices, laptop
Photo: Cup of Couple / Pexels

Germany has two separate e-invoice dates. Since 1 January 2025, every business established in Germany must be able to receive structured e-invoices for domestic B2B sales. From 1 January 2027, a business whose total turnover in the previous calendar year exceeded €800,000 must issue them. Everyone else must issue them from 1 January 2028. A plain PDF does not count as a structured e-invoice. The practical route is to confirm your 2026 turnover, choose XRechnung or ZUGFeRD in your billing system, map the mandatory VAT fields from your existing billing data, test with your largest customers, and keep a person reviewing rejected or flagged invoices. The Federal Ministry of Finance letter of 15 October 2026 adds rules on corrections, validation errors and attachments.

In short

  • Receiving structured e-invoices has been required since 1 January 2025, and issuing is required from 1 January 2027 only above €800,000 prior-year turnover.
  • XRechnung and ZUGFeRD are the formats to plan for, and a PDF without structured data does not count.
  • Manual invoice handling costs roughly $13 to $21 per invoice on public US benchmarks from 2025, so measure your own volume before you decide.
  • Validation messages and corrections need a person to decide whether the VAT position changed.
  • Test with your largest German customers before 1 January 2027, not after it.

Two dates, one threshold

Many owners read 'e-invoice 2027' as a single switch. It is two switches. The receiving duty has applied to every German business since 1 January 2025. You must be able to take in a structured invoice, and an ordinary inbox that accepts XML attachments is enough to start. The issuing duty is different. It starts on 1 January 2027 for businesses whose total turnover in the previous calendar year was above €800,000, which means the 2026 turnover decides the 2027 date. Businesses at or below that figure have a transition year in 2027, when they may keep sending paper or PDF invoices, and in most cases they must move to structured invoices from 1 January 2028.

Turnover is measured for the whole business, not per product line. A sole trader with an online shop and a consulting practice adds both figures together. If you run several German companies, each legal entity is tested on its own turnover, and that is a point to confirm with your tax adviser before you plan the cutover.

There is also a small-value exemption. Invoices up to €250 do not have to be issued as e-invoices, and travel tickets are outside the duty. Most business-to-business invoices above that amount are in scope, so do not build your plan around the exemption.

Why this costs money even before the deadline

The cost of the 2027 change is mostly labour and rework, not software. The clearest public benchmarks are from the United States and are quoted in US dollars, so treat them as an orientation, not a German price list. Ardent Partners' 2025 AP Metrics report puts the average manual processing cost at about $12.88 per invoice for organisations without best-in-class automation. The APQC benchmarking data for 2024 to 2025 gives a median of $21.40 for the same activity. The two sources disagree, and the spread is wide, so the honest basis is a range of roughly $13 to $21 per invoice before any error correction.

To make that concrete, take a business that sends 300 invoices a month. At the two benchmark points, manual handling would sit between about $3,900 and $6,400 a month. That is arithmetic on public benchmarks, not a measure of your own figures. Your real number depends on how many invoices need a person to re-key, correct or chase them. The free automation audit measures this with your own volumes.

The larger risk is timing. A structured invoice that a buyer's system rejects is not paid until it is fixed. If your receivables depend on a few large German customers, one rejected format can hold up cash for a whole payment run.

The manual way and the automated way

The table below compares how the same monthly billing run looks before and after the change. The automated column describes what a system does; the last column names what a person still signs off.

TaskManual wayAutomated wayWhat a person still checks
Creating the invoiceStaff type the buyer, lines and VAT into a PDF templateThe billing or ERP system builds the invoice from the order or contract recordBuyer identity, unusual terms, credit limits
Output formatPDF emailed as a letter-style fileXRechnung (XML) or ZUGFeRD (PDF with embedded XML) generated from the same dataA sample file for each new customer group
Mandatory VAT dataChecked by eye on each invoiceRequired fields checked before the file is releasedVAT rate, tax treatment and exemption wording
SendingEmail with attachment, copy saved in a folderEmail or a network route, with delivery status loggedFailed deliveries and bounced addresses
Incoming supplier invoicesTyped in from PDFsStructured files read directly; PDFs read with OCR and checkedAny invoice the system could not read or match
CorrectionsCredit note as a PDFCorrection issued as a structured invoice from the same systemReason for the correction and the link to the original

Step-by-step: from billing data to a compliant invoice

Start with the threshold, not the software. The order below is the sequence that avoids rework. Only the first two steps are needed by every business. The rest depends on how your invoices are produced today.

  1. Confirm your 2026 total turnover and write down your issuing date, 1 January 2027 or 1 January 2028. Keep the calculation on file, because the buyer and the tax adviser may ask for it.
  2. List every place an outgoing invoice is produced. This usually means the ERP, an accounting programme such as DATEV, Lexware Office, sevDesk or Odoo, a spreadsheet template, and any shop or booking system that issues invoices. Ask each provider, in writing, whether its current version produces XRechnung or ZUGFeRD and which profile it uses. Use the provider's current documentation as the source, not a sales page.
  3. Map your billing data to the mandatory fields. In most German setups these include the seller and buyer names and addresses, the VAT identification numbers, the invoice date and number, the description of the supply, quantities, unit prices, VAT rates and amounts, and the payment reference. Build this as a spreadsheet table first. Each row is a field, each column is a source system, and each cell names where the value comes from.
  4. Clean the customer master data. Structured invoices fail when a buyer's name, VAT number or routing address is wrong or missing. Check the German buyers in your active customer list against the data they have given you, and record the routing route for each corporate buyer that uses one.
  5. Connect the data to the format. If your ERP can produce XRechnung or ZUGFeRD natively, switch it on and test it. If not, a workflow tool such as Power Automate or Zapier can pick up an approved invoice from your billing system and pass its fields to a generator that writes the structured file. Use a language model only for free-text parts, such as turning a job description into a clear line item. Do not let it set VAT rates or buyer details.
  6. Validate every file before it leaves your system. KoSIT, the German coordination office for IT standards, publishes an open-source validation tool that checks XRechnung files against its rules. Run a sample of every invoice type through it, and block sending when a file fails.
  7. Test with your largest customers. Send one structured test invoice to each of them and ask whether their system took it. Keep a record of the result. Do this before 1 January 2027, not on the first working day of the year.
  8. Set up receiving. Confirm that your invoice inbox accepts XML files, and that incoming ZUGFeRD files have their XML read, not only the PDF. Route any PDF without structured data to a person, because a PDF from a supplier is not an e-invoice.
  9. Use messaging for reminders, not as the invoice itself. A WhatsApp Business API flow can tell a buyer that a structured invoice has been issued and where to find it. Whether a messaging channel can carry the invoice file in a compliant way is a question for your tax adviser, so do not assume it.

What the 15 October 2026 letter changes

The Federal Ministry of Finance issued a further letter on 15 October 2026, reference III C 5 - S 7287-a/00019/021/017. It supplements the letters of 15 October 2024 and 15 October 2025 and changes the VAT Application Decree, the UStAE. The official letter text was not retrieved for this guide. The points below come from tax-adviser summaries that cite the letter and its reference number, so check the wording against the ministry's publication before you rely on it.

Three points matter for the checklist. First, all mandatory VAT information must sit in the structured part of the file. Supporting details, such as a detailed timesheet, may be attached in a separate file if they are not needed for the VAT assessment. Second, an error reported by a validation tool does not always make the invoice invalid for VAT. The letter separates format errors from business-rule errors, and the consequence depends on which one it is and whether it affects mandatory VAT data. Third, corrections must themselves be issued as e-invoices. The letter leaves some room in how a correction is made, so agree the method with your accountant.

The letter also says that issuing a non-electronic invoice where an e-invoice is required does not by itself count as an administrative offence. Summaries read this as a non-penalty point only. The duty to issue an e-invoice still applies. Invoices issued until 31 December 2026 that follow the 2024 and 2025 guidance are not challenged solely because they miss the new points.

What breaks, and how to prevent it

The most common failure is a missing or wrong mandatory field. A buyer VAT number that is out of date, or a VAT rate typed as text, will stop the file or create a disputed invoice. Prevent this with a required-field check that blocks the send, and by refreshing the customer list before the first 2027 run.

The second failure is over-trusting the validator. A tool can flag a business-rule issue on a file that remains valid for VAT. The opposite also happens: a file passes the format check but has a wrong VAT treatment. A person should review the flagged list each week and decide which messages are format faults and which change the VAT position.

The third failure is an accounts payable system that rejects valid invoices. Check whether your incoming invoice tool treats every validation message as a fatal error. If it does, configure it to route those files to a person rather than discard them.

The fourth failure is extraction errors on incoming invoices. A language model or OCR reader can misread a line total or a VAT rate from a scanned PDF. Keep a match step against the purchase order or contract, and never post an extracted total without that match.

The fifth failure is the threshold itself. A business near €800,000 can cross it in the middle of a year. The 2027 duty depends on the previous year's total, so keep a monthly turnover record and do not assume the 2028 date without checking.

When not to automate

Automation is not worth building if you send only a handful of invoices a month. In that case, a compliant output option in your existing accounting programme, combined with a manual check, may be cheaper to run than a workflow you must maintain. The same applies if most of your invoices are below €250 or are travel tickets, which are outside the duty.

Do not automate an invoice that needs judgement on each job. Projects with changing terms, partial deliveries, advance payments and final invoices need a person to decide what is billed and when. Automation can produce the file once those decisions are recorded, but it cannot make them.

Do not automate on top of messy master data. If customer names, VAT numbers and addresses are inconsistent across three systems, a workflow will send the errors faster. Clean the data first, then connect it.

Finally, no system decides VAT treatment for you. The letter leaves more of that responsibility with the business than some newer e-invoicing regimes do, so the VAT decision stays with a trained person.

What it typically takes

The work is mostly sequencing and testing, not buying licences. Plan it in stages. The threshold check and the list of invoice producers take a short exercise with the finance lead. Mapping fields and cleaning customer data usually takes longer, because someone has to check records that nobody has looked at for years. Test sends to large customers depend on how quickly those customers reply, so start them early. A parallel run, where you issue both the old PDF and the new structured file for one billing cycle, is a useful last check before the cutover.

The time needed depends on the number of billing systems, the number of German buyers, and how many invoice types you issue. The free automation audit at AiStaffo measures those counts with your own data, so the plan rests on your figures and not on a generic estimate.

This explains the rule in general terms; it is not legal or tax advice for your case.

How AiStaffo would automate this

AiStaffo would start by connecting the billing system, the customer master list and the invoice inbox, so the fields that the structured file needs are read from one place. A workflow would then build each XRechnung or ZUGFeRD file from an approved invoice, run the validation check before anything is sent, and log each delivery. Incoming structured invoices would be matched to orders, and PDFs from suppliers would be read and queued for review. The owner or finance lead would still set the threshold date, approve the VAT treatment for unusual invoices, review every flagged validation message, and sign off the test results with the largest customers. To see what this would look like with your own invoice volumes and systems, book a free automation audit.

Questions people ask

Do I have to issue e-invoices in 2026?
For most businesses, no. The issuing duty starts on 1 January 2027 for businesses whose total turnover in 2026 was above €800,000, and on 1 January 2028 for the rest. Receiving structured e-invoices has been required since 1 January 2025, so your inbox and accounting setup must already accept them.
How is the €800,000 threshold counted?
The test uses the total turnover of the business in the previous calendar year, so the 2026 total decides the 2027 date. Several activities of one person or company are added together. Each legal entity is tested on its own turnover, and a tax adviser should confirm how your group is structured.
Is a PDF invoice still allowed in Germany?
A plain PDF is not a structured e-invoice. A ZUGFeRD file is a PDF with an XML file inside, and the XML is the legally relevant part, so that format can qualify. Printing an XRechnung to PDF and keeping only the PDF does not meet the rule.
What happens if I send a normal invoice when an e-invoice is required?
The Federal Ministry of Finance letter of 15 October 2026 states that issuing the wrong format does not by itself constitute an administrative offence. That does not remove the duty, which still applies. Check the letter text and your tax adviser's view on your own position.
Can I send e-invoices through WhatsApp?
Messaging apps are useful for telling a buyer that an invoice is ready, but the structured file must meet the format rules. Whether a messaging channel can carry the file compliantly is a question for your tax adviser. Most businesses send the file by email or through a network route and use messaging for reminders.
Do corrections to an invoice also have to be e-invoices?
Yes. The October 2026 letter says corrections to e-invoices must themselves be issued as e-invoices. The letter allows some flexibility in how a correction is made, so agree the method with your accountant and keep a clear link to the original invoice.

Book a free automation audit

Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.

We use these details only to reply to this request and prepare your audit, and keep them for up to two years. We send no marketing unless you tick the box above. Privacy policy

e invoicinginvoice automationerp integrationdocument processinggermany