Contentoren

Compliance & funding

Germany's E-Invoicing Mandate 2027/28: Automate with AI

Germany's e-invoicing mandate 2027: who must issue e-invoices from January, what changes in 2028, how ViDA fits in and how to automate invoicing with AI.

19 min readby Contentoren Editorial Team
Share
The bookkeeper of a roofing company sorts paper invoices early in the morning next to her laptop and a document scanner.

Key takeaways

In short:

  • From 1 January 2027, businesses established in Germany with more than €800,000 total turnover in 2026 must issue structured e-invoices for domestic B2B sales (section 27(38) UStG).
  • From 1 January 2028, every other German business follows, and the transition period for legacy EDI ends. Receiving e-invoices has been mandatory for all domestic businesses since 1 January 2025 (German Ministry of Finance FAQ).
  • Valid formats are XRechnung and ZUGFeRD/Factur-X (from version 2.0.1) based on the European standard EN 16931. A plain PDF is not an e-invoice.
  • There is no postponement: the Ministry's guidance letter of 15 October 2026 clarifies details but leaves the deadlines untouched.
  • Germany is part of a wider European shift: Belgium, Poland and France introduced mandates in 2026, and the EU's ViDA package brings e-invoice-based reporting for cross-border trade from 1 July 2030.

Most guides stop at deadlines and formats. This one goes further. As of 6 November 2026, it explains who is in scope in Germany, how the German rules fit into the EU picture, and how a mid-sized company can automate both outgoing and incoming invoices, with a workflow table, a comparison of solution types and worked examples.

What is an e-invoice under German law, and why isn't a PDF one?

Under section 14(1) of the German VAT Act (UStG), an e-invoice is an invoice "issued, transmitted and received in a structured electronic format that enables electronic processing". The format must follow the European standard EN 16931 (the same standard used for public procurement under Directive 2014/55/EU) or be agreed between the parties, as long as all mandatory VAT data can be extracted into an EN 16931-compatible format.

Everything else, whether paper, a plain PDF, a scan or a photo, has been an "other invoice" since 2025 (Ministry FAQ, question 2). A PDF is made for people to read; an e-invoice is made for software.

Format Structure E-invoice in Germany? Typical use
XRechnung (current version 3.0.2, KoSIT) Pure XML (UBL or CII), no visual layer Yes Public sector invoices, increasingly B2B
ZUGFeRD / Factur-X (current 2.5.2, FeRD) PDF/A-3 with embedded XML; Factur-X is the Franco-German twin Yes, from 2.0.1, except MINIMUM and BASIC-WL profiles B2B where recipients also want a readable PDF
EDI (e.g. EDIFACT) Structured messages under bilateral agreement Yes if all VAT data is extractable; otherwise only until 31 Dec 2027 Retail, manufacturing, automotive
Plain PDF, Word, scan Unstructured No ("other invoice") Only during transition periods and for exemptions

Two details that trip up many businesses:

  • With ZUGFeRD, the XML prevails over the PDF. If the visual and the data layer differ, the structured data is legally decisive (Ministry FAQ, question 12a). Checking only the PDF means checking the wrong document.
  • All mandatory VAT data must be in the XML. A reference to an attachment is not enough. Supporting documents such as timesheets may be embedded as attachments (Ministry FAQ, question 7a).

When does Germany's e-invoicing mandate apply? Timeline 2025–2035

From Who What applies
1 Jan 2025 All businesses established in Germany Must be able to receive e-invoices; an email inbox is sufficient (Ministry FAQ, question 8)
until 31 Dec 2026 Everyone Paper always allowed; PDF only with the recipient's consent
1 Jan 2027 Total turnover 2026 above €800,000 Domestic B2B invoices must be e-invoices (section 27(38) no. 2 UStG)
until 31 Dec 2027 Total turnover 2026 up to €800,000 Paper or PDF (with consent) still allowed
until 31 Dec 2027 Users of legacy EDI Non-EN 16931 EDI still allowed (section 27(38) no. 3 UStG)
1 Jan 2028 All businesses E-invoicing mandatory for domestic B2B (exemptions below)
30 Jun 2030 Special cases End of simplified treatment of final invoices with prior instalments (Ministry letter, 15 Oct 2026)
1 Jul 2030 Cross-border B2B within the EU ViDA digital reporting requirements (European Commission)
1 Jan 2035 Member states with domestic real-time reporting Must align their systems with the EU model (same source)

What matters is the date of supply, not the invoice date. Advance and instalment invoices issued before your mandate starts do not need to be e-invoices, even if delivery and payment happen later (Ministry FAQ, question 7b).

Who is in scope? The €800,000 threshold and the exemptions

The threshold refers to total turnover as defined in section 19(2) UStG: taxable supplies based on payments received, minus certain exempt supplies. Three points are often misunderstood:

  1. Consumer sales count too. A company with €500,000 in consumer sales and €400,000 in B2B sales is above the threshold.
  2. Turnover, not profit, and net of VAT.
  3. Last year's figure decides, not a forecast. For 2027, the relevant year is 2026.

The mandate applies only where a VAT invoice is required and both parties are established in Germany, i.e. have their registered office, management or a fixed establishment involved in the supply there (Ministry FAQ, question 3). For non-German companies this means:

  • VAT-registered in Germany without an establishment: you may state this on your invoice to explain why you do not issue an e-invoice; your customer may rely on it.
  • Invoicing German customers from abroad: outside the German mandate (but watch your own country's rules and, from 2030, ViDA).
  • With a German subsidiary or branch involved in the supply: in scope like any German business.

According to Ministry FAQ, question 4, "other invoices" remain allowed for:

  • Small invoices up to €250 gross (section 33 UStDV), permanently.
  • Travel tickets (section 34 UStDV).
  • Invoices from small businesses under the German small-business scheme (section 34a UStDV).
  • Supplies to consumers and to non-business legal entities.
  • Many VAT-exempt supplies under section 4 nos. 8–29 UStG, such as financial services or residential letting.

Cash payment is not an exemption. A business lunch or a hardware store purchase over €250 requires an e-invoice once the supplier can no longer use a transition rule (Ministry FAQ, question 10).

What changed in 2026? The rejected delay and the October guidance

On 22 June 2026, the German Confederation of Skilled Crafts (ZDH) called for the 2027 start to be moved to 1 January 2028 (ZDH; date as reported by ad-hoc-news). The ZDH reported that around two-thirds of surveyed businesses had problems receiving e-invoices and that the revised EN 16931 for B2B and a binding field mapping were still missing. The law was not amended.

Instead, the Ministry of Finance published its third guidance letter on 15 October 2026 (PDF). The key points:

  • Three types of error: a format error turns the file into an "other invoice". A business-rule error (failing an EN 16931 validation rule) generally leaves the file an e-invoice for VAT purposes. Only if it affects mandatory VAT data does it become a content error, which puts the customer's input VAT deduction at risk (paras. 22–23).
  • Grace period for content only: e-invoices issued until 31 December 2026 that meet the 2024 and 2025 guidance are accepted, including for input VAT deduction.
  • Gross-price invoices: until 31 December 2027, the XML may contain only totals per VAT rate, with line items in a readable attachment.
  • Construction: the XML may list trades with totals, with the bill of quantities embedded as an attachment.
  • No fine: issuing an "other invoice" instead of a mandatory e-invoice is not an administrative offence under section 26a UStG (para. 28). The customer, however, has a civil-law claim to receive an e-invoice (Ministry FAQ, question 12c).

For automation, this means a validator is essential but not the final judge. A red validation report is not automatically a reason to reject an invoice, and a green one does not prove it is correct for VAT purposes.

How does Germany compare with other EU mandates?

Since ViDA (Council Directive (EU) 2025/516) entered into force on 14 April 2025, member states can introduce domestic e-invoicing mandates without asking Brussels for a derogation (European Commission). Several have done so. Status as of November 2026, limited to mandates we could verify on official sources:

Country Model Key dates
Germany Decentralised exchange (email, Peppol, EDI), EN 16931; no clearance platform Receive since 1 Jan 2025; issue from 1 Jan 2027 (> €800k) and 1 Jan 2028 (all)
Belgium Structured e-invoices exchanged directly between businesses, typically via Peppol Mandatory for VAT-liable Belgian businesses since 1 Jan 2026, with a tolerance period in the first three months (einvoice.belgium.be)
Poland Central clearance via the national KSeF platform 1 Feb 2026 for businesses with 2024 sales above PLN 200m; 1 Apr 2026 for all others; until end-2026 relief for monthly invoiced sales up to PLN 10,000 (KSeF, Ministry of Finance)
France Exchange via approved platforms plus data transmission to the tax authority All businesses must receive since 1 Sep 2026; large and mid-sized companies issue from 1 Sep 2026, SMEs and micro-businesses from 1 Sep 2027 (Service Public Entreprendre)
EU (ViDA) E-invoice-based digital reporting Cross-border B2B from 1 Jul 2030; national systems aligned by 1 Jan 2035

For companies operating in several countries, the practical lesson is that the German model is the most flexible, while Poland and France route data through state or approved platforms. An invoice process built on EN 16931 data, with country-specific transmission at the end, covers all of them. The Commission expects the move to e-invoicing to cut VAT fraud by up to €11 billion a year and lower compliance costs for EU traders by more than €4.1 billion a year over ten years (European Commission).

How do you automate outgoing invoices?

Issuing e-invoices doesn't require AI. It requires clean master data and software that produces XRechnung or ZUGFeRD (EN 16931 profile or higher). Most invoicing and ERP tools on the German market now support this. The work is in the details:

  • Customer master data: full address, VAT ID or tax number, invoice email address and, if requested, a buyer reference (field BT-10; for B2B a placeholder such as "-" is sufficient, Ministry FAQ, question 6).
  • Description of supply: "Consulting as per contract" is not enough. Type, scope and period must be in the XML.
  • Validation before sending: KoSIT publishes an open-source validator. Validate every outgoing file automatically.
  • Transmission: German law does not prescribe a channel. Email is common; Peppol makes sense at volume and is one of the channels of the federal invoice platform OZG-RE. If you also invoice Belgian customers, you will need Peppol anyway.
  • Corrections and credit notes: where the mandate applies, corrections must also be e-invoices with a clear reference to the original.

How do you automate incoming invoices? A 7-step workflow

This is where the payoff is. The German ministry itself names the goal: recipients should no longer have to re-enter invoice data (Ministry FAQ, question 1). You are not obliged to process invoices electronically, but you can benefit greatly from doing so.

Step What happens Automation Where AI helps
1. Receipt Dedicated inbox (e.g. invoices@…), Peppol access point or supplier portal Inbox polled, attachments stored Separates invoices from reminders, newsletters and order confirmations
2. Format detection XRechnung, ZUGFeRD, EDI or other invoice? Rule-based (XML attached or embedded in PDF) –
3. Validation Format and business-rule checks against EN 16931 KoSIT validator or software module Turns validator messages into plain-language notes
4. Data capture Supplier, amounts, VAT rates, lines, bank details E-invoices: read the XML, no recognition needed PDF/paper: OCR plus language-model extraction with plausibility checks
5. Review Match against purchase order, delivery note, contract; check mandatory VAT data Two- or three-way match in the ERP Fuzzy line matching, flags discrepancies, suggests GL coding
6. Approval Approval by amount, cost centre, supplier Workflow with deputies and deadlines (early-payment discounts) Summarises the invoice for approvers
7. Posting and archive Transfer to DATEV, ERP or finance system; store the original Interface, tamper-proof archive –

Three points separate "receiving" from "processing" e-invoices:

  1. The XML is the original. At least the structured part must be stored unaltered in its original form (Ministry FAQ, question 13) for eight years under section 14b UStG and section 147(3) of the Fiscal Code. A re-rendered PDF does not replace it. Bookkeeping as a whole must also follow Germany's GoBD rules on electronic records.
  2. People still need a view. XRechnung has no visual layer. Your software should render it, or use the free ELSTER e-invoice viewer.
  3. Use AI for the remainder, not for everything. Small receipts, foreign suppliers and PDFs from smaller German suppliers until the end of 2027 stay unstructured. A pipeline that only handles XML covers just part of your volume. A language model can extract these documents into the same structure, with confidence scores and a human check when unsure, so errors are flagged instead of slipping through.

Our comparison of n8n, Make and Zapier shows how workflow tools can connect these steps.

Which approach fits? Three options compared

Option Best for Running costs (examples) Rollout Limits
Accounting/invoicing SaaS (e.g. Lexware Office, sevdesk) Small German businesses, few approvers Lexware Office €7.90–32.90/month excl. VAT (pricing); sevdesk €11.90–34.90/month excl. VAT (pricing), list prices without promotions, Nov 2026 Days Little room for approval chains, PO matching and edge cases
Document management / AP automation suite with DATEV or ERP connector Mid-sized firms with several sites or cost centres Usually priced by users and document volume, on request Weeks Standard processes; adapting to your own workflow can be costly
Custom automation (workflow platform plus AI extraction, connected to existing systems) Own ERP, high volumes, many PDF suppliers, multi-country set-ups Project fee plus operation, depending on scope and interfaces Weeks to a few months Needs clear process ownership and maintenance

The right choice depends less on company size than on three questions: how many invoices arrive each month, how many of them are still PDFs, and how far your approval process deviates from the standard. If off-the-shelf software covers your needs, it is almost always the cheapest option.

Three worked examples

Example 1: German electrical contractor, €1.2m turnover in 2026. In scope from 1 January 2027. The trade software produces ZUGFeRD; the open issues are customer data and construction invoices. Solution: describe the supply per trade in the XML, embed the measurement sheet as an attachment, and leave instalment invoices from 2026 as PDFs.

Example 2: Agency, €650,000 turnover in 2026. In scope from 1 January 2028. It may still send PDFs in 2027 with customer consent. Switching at the start of 2027 is wiser: larger clients will ask for e-invoices anyway, and the agency can test calmly instead of rushing in late 2027.

Example 3: Wholesaler with a Polish subsidiary, €18m turnover, about 1,500 incoming invoices per month. EDI with large suppliers can continue until the end of 2027; the Polish entity already issues through KSeF. Illustrative calculation: if manual capture and review takes six minutes per invoice (an assumption), that is 150 hours a month. If only exceptions are handled manually for 70% of invoices, a few dozen hours remain for clarifications. Measure your own times before the project, because they are the basis of any business case.

Checklist: 8 steps to e-invoicing readiness

  1. Check scope: determine total 2026 turnover with your tax adviser. Above €800,000 → 1 January 2027.
  2. Secure receipt: set up a central invoice inbox and tell suppliers.
  3. Check software: does it create XRechnung or ZUGFeRD in the EN 16931 profile (not MINIMUM/BASIC-WL)? Does it read incoming XML?
  4. Clean master data: customers, suppliers, tax numbers, invoice addresses, item texts.
  5. Define edge cases: instalment and final invoices, construction, gross prices, credit notes, corrections.
  6. Build in validation: on every outgoing and incoming invoice, with a rule for format, business-rule and content errors.
  7. Review your archive: original XML, eight years, unalterable; update your process documentation.
  8. Test with real invoices: ten outgoing to regular customers, ten incoming from different suppliers, before the deadline.

Common mistakes

  • Sending ZUGFeRD in the MINIMUM or BASIC-WL profile. It looks like an e-invoice but isn't one for VAT purposes.
  • Checking only the PDF. With hybrid invoices, the XML is what counts.
  • Discarding the XML. Archiving only the PDF breaches the retention rules.
  • Treating every validator warning as a rejection reason. Since the 2026 guidance, not every business-rule error invalidates an invoice for VAT.
  • Waiting for fines instead of customers. There are none; the pressure comes through input VAT and payment delays.
  • Forgetting the inbound side. Many projects focus on outgoing invoices, yet the time savings are in accounts payable.

Outlook: 2028, a German reporting system and ViDA

From 2028, e-invoicing will be the norm for domestic B2B in Germany. The ministry also plans a later transaction-based reporting system, with legislation to be proposed "in due course" (Ministry FAQ, question 1). At EU level, ViDA brings digital reporting for cross-border B2B from 1 July 2030 and convergence of national systems by 2035. Moving cleanly to EN 16931 now lays the groundwork for both.

Some German states subsidise digitalisation projects in accounting and document processing; see our guide to digitalisation and AI funding in Germany.

Conclusion: meet the mandate, take the efficiency gain

The deadlines are fixed: 2027 for German businesses above €800,000 turnover, 2028 for everyone else, with Belgium, Poland and France already live and ViDA following in 2030. For outgoing invoices, well-maintained standard software is usually enough. The real value is in accounts payable, when structured data is automatically validated, approved, posted and archived, and AI handles only the unstructured remainder. For more processes that benefit from the same approach, see our article on the benefits of AI automation.

If your invoice intake goes beyond what standard software handles, for example with your own ERP, many PDF suppliers or multi-step approvals, we can build the right pipeline with you: document automation for capture and review, and process automation for approvals and the hand-off to DATEV or your ERP. Book a no-obligation call: contact us.

This article is not tax or legal advice. Check your specific situation, especially the turnover threshold, with your tax adviser.

Sources

Accessed 6 November 2026

Frequently asked questions

Who has to issue e-invoices in Germany from 1 January 2027?

Every business established in Germany whose total turnover in 2026 exceeded €800,000, for invoices to other domestic businesses. The threshold refers to the whole company's turnover under section 19(2) of the German VAT Act, not just B2B sales. Businesses at or below €800,000 may keep sending paper or, with the customer's consent, PDF invoices until the end of 2027.

Has Germany postponed the 2027 e-invoicing deadline?

No, as of 6 November 2026. The German Confederation of Skilled Crafts asked in 2026 for a one-year delay, but the law was not changed. The Federal Ministry of Finance's guidance letter of 15 October 2026 still refers to the unchanged transition rules ending in 2027.

Does Germany's mandate apply to foreign companies?

Only if both supplier and customer are established in Germany, meaning a registered office, management or a fixed establishment involved in the supply. A foreign company that is only VAT-registered in Germany can state this on its invoice and issue a non-structured invoice. Invoices to customers abroad are outside the German mandate.

Is a PDF an e-invoice in Germany?

No. A German e-invoice must be issued, transmitted and received in a structured format that allows electronic processing, in practice XRechnung or ZUGFeRD/Factur-X following EN 16931. A plain PDF counts as an 'other invoice'. ZUGFeRD looks like a PDF but embeds an XML file and qualifies, except for the MINIMUM and BASIC-WL profiles.

What does ViDA change for e-invoicing in the EU?

The VAT in the Digital Age package, adopted on 11 March 2025, allows member states to introduce domestic e-invoicing mandates without EU derogation. From 1 July 2030, digital reporting based on e-invoices applies to cross-border B2B supplies within the EU. By 1 January 2035, national real-time reporting systems must be aligned with the EU model.

Do I need AI for e-invoicing?

Not for genuine e-invoices: XRechnung and ZUGFeRD already contain structured data that software reads directly. AI becomes useful for everything else, such as PDF and paper invoices from smaller or foreign suppliers, small receipts, coding suggestions, purchase-order matching and resolving discrepancies.