Skip to main content
Complyance is Officially Listed as a UAE Approved Accredited Service Provider
Electronic Invoice in Germany: What Is It? Simply Explained

Electronic Invoice in Germany: What Is It? Simply Explained

Swathy
Published on Jul 23, 2026
Electronic Invoice in Germany: What Is It? Simply Explained

Here is what most people get wrong about electronic invoices.

They think sending a PDF by email counts as one. It does not.

Not in Germany. Not under EU law. And not under the regulations that took effect in January 2025.

That single misunderstanding is costing businesses time, money, and compliance headaches right now. This guide covers exactly what an electronic invoice in Germany actually is, how it works, and what you need to do about it.

Key Takeaways

  • An electronic invoice (e-invoice) is a structured, machine-readable data format — not a PDF, not a scan, not a Word document.
  • Germany uses two main formats: XRechnung (pure XML) and ZUGFeRD (PDF with embedded XML, EN 16931 profile or higher).
  • Since January 1, 2025, all B2B businesses in Germany must be able to receive e-invoices.
  • Mandatory sending follows in 2027 (for businesses above EUR 800,000 revenue) and 2028 (for all businesses).
  • The transition is manageable, but it requires preparation.

What Is an Electronic Invoice? The Definition

The electronic invoice definition under EU Directive 2014/55/EU and Germany's Growth Opportunities Act (Wachstumschancengesetz) is clear:

An electronic invoice is an invoice that is issued, transmitted, and received in a structured electronic format that enables automatic and electronic processing.

The key criterion is automatic and electronic processing: a computer must be able to read the invoice, interpret the data fields, and process the information without human intervention.

That means the following documents do not qualify:

  • PDF files (not structured data)
  • Scanned paper invoices
  • Image files (JPG, PNG)
  • Word or Excel documents

And the following formats do qualify:

  • XRechnung — pure XML format, mandatory for public sector invoicing
  • ZUGFeRD (EN 16931 / Comfort profile or higher) — hybrid format combining PDF with embedded XML
  • Other formats compliant with the European standard EN 16931
Callout: An e-invoice is not a document you look at. It is a dataset your software understands. The visual representation is just the surface layer.

E-Invoice Explained: How It Actually Works

Consider a typical scenario. You order goods from a supplier. They create the invoice in their accounting system. In the past, they generated a PDF and emailed it to you.

With e-invoicing, the process changes:

  1. Creation: The supplier creates the invoice in their ERP or accounting software. The system automatically generates a structured XML file.
  2. Transmission: The e-invoice is sent through a secure channel — via email, a portal, or through the Peppol network.
  3. Receipt: Your software receives the file and automatically imports the data. Invoice number, amounts, tax rates, due date — everything captured instantly.
  4. Processing: The invoice lands directly in your system, ready for approval and payment, with no manual data entry.

How Transmission Works: The 4-Corner Model

When an e-invoice travels over the Peppol network, it moves through the 4-corner model:

Step 1 — Supplier generates the invoice (Corner 1)

The supplier creates the invoice in their ERP. The output is a structured XML file.

Step 2 — Sender's Access Point transmits it (Corner 2)

The supplier's Peppol Access Point picks up the invoice, validates it, and routes it through the Peppol network.

Step 3 — Receiver's Access Point delivers it (Corner 3)

The buyer's Access Point receives the invoice, applies any format conversion, and pushes it into the buyer's system.

Step 4 — Buyer processes the invoice automatically (Corner 4)

The buyer's accounting or ERP system receives the structured data directly.

Where Complyance fits in

Complyance operates as a certified Peppol Access Point, covering both Corner 2 (sending) and Corner 3 (receiving):

  • You send your invoice data to the Complyance API once
  • Complyance generates the compliant XRechnung or ZUGFeRD XML
  • Complyance transmits it through the Peppol network
  • On the receiving side, Complyance validates incoming invoices and routes them into your accounts payable workflow

The Main E-Invoice Formats in Germany

FeatureXRechnungZUGFeRD (EN 16931 or higher)
Format typePure XMLPDF/A-3 with embedded XML
Human-readableNoYes
Primary use casePublic sector (B2G)B2B and B2G
EN 16931 compliantYesYes (EN 16931 profile and above)
Best forGovernment invoicesBusinesses bridging both worlds
ZUGFeRD profile note: Only the EN 16931 (Comfort), Extended, and XRechnung profiles meet the mandate requirements.

If you invoice public authorities, XRechnung is mandatory. For B2B transactions, ZUGFeRD offers the practical advantage that recipients can open the invoice as a normal PDF.

PDF vs. E-Invoice: The Critical Difference

CriteriaPDF InvoiceElectronic Invoice
Machine-readableNoYes
Structured dataNo (visual only)Yes (XML-based)
Automatic processingOnly via OCR (error-prone)Direct processing
Legally recognized as e-invoiceNoYes
Media breakYesNo
Tamper resistanceLowHigh
GoBD-compliant archivingLimitedYes

A PDF is a picture of an invoice — not an invoice in the data sense.

Your computer sees pixels when it opens a PDF. It does not know where the invoice number is. It cannot identify the tax rate. It cannot automatically post the amount to the correct account.

An e-invoice is like a spreadsheet your software instantly understands. Every field has its place.

Germany is not acting alone here. The push for e-invoicing traces back to EU Directive 2014/55/EU, which mandated electronic invoicing in public procurement.

With the Growth Opportunities Act (Wachstumschancengesetz), enacted in March 2024, Germany extended the obligation to cover the entire B2B sector.

Key deadlines:

  • January 1, 2025: All businesses must be able to receive e-invoices.
  • January 1, 2027: Businesses with annual revenue above EUR 800,000 must send e-invoices.
  • January 1, 2028: All businesses must send e-invoices.

5 Benefits of Electronic Invoicing

1. Faster Processing Times

No more manual data entry. What used to take 10 to 15 minutes per invoice now happens in seconds.

2. Fewer Errors

Typos in amounts, wrong account numbers, swapped tax rates — these disappear when data transfers are automated.

3. Improved Cash Flow

When invoices are processed faster, payments happen faster.

4. Full Legal Compliance

You meet current requirements and are prepared for upcoming deadlines.

5. Lower Costs and Environmental Impact

Less paper, lower postage costs, reduced CO2 emissions.

How to Get Started: 5 Steps

Step 1: Assess Your Current Setup

Review your existing invoicing and accounting software. Can it receive and process e-invoices in XRechnung or ZUGFeRD format?

Step 2: Choose Your Format

For B2B, ZUGFeRD is often the most practical choice. For public sector, XRechnung is mandatory.

Step 3: Update or Switch Your Software

If your current solution does not support e-invoicing, now is the time to upgrade.

Step 4: Adapt Your Processes

Train your team. Update your internal workflows.

Step 5: Test Everything

Create test invoices. Verify that receiving and processing work smoothly end to end.

Do's and Don'ts

Do's

  • Start early. The receiving obligation has been in effect since January 2025.
  • Train your team. The best software is useless if your staff does not know how to use it.
  • Test both formats. Make sure your systems can handle XRechnung and ZUGFeRD.
  • Review your archiving. E-invoices must be stored in compliance with GoBD requirements.
  • Communicate with partners.

Don'ts

  • Do not assume PDF is enough. A PDF sent by email does not count as an e-invoice.
  • Do not focus only on receiving. The sending obligation is approaching.
  • Do not print e-invoices. That defeats the entire purpose.
  • Do not forget archiving. The original XML must be preserved.
  • Do not go it alone if you are unsure.

The Bottom Line

The electronic invoice in Germany is fundamentally changing how businesses handle their invoicing processes.

The difference between a PDF and an e-invoice might seem small at first glance. It is not. Structured data instead of visual documents. Automatic processing instead of manual entry. Legal certainty instead of compliance risk.

The transition is manageable. With the right format, the right software, and a clear plan, you can be fully compliant in a matter of weeks.

Share

Frequently Asked Questions

An electronic invoice is an invoice in a structured, machine-readable data format (such as XML). It is created, sent, and received digitally. Unlike a PDF, it can be automatically read and processed by software without any manual data entry.

No. Under the Growth Opportunities Act and the EU standard EN 16931, a plain PDF does not qualify as an electronic invoice. The exception: ZUGFeRD invoices at the EN 16931 / Comfort profile or higher are PDFs with embedded XML — these do qualify.

The two main formats are XRechnung (pure XML) and ZUGFeRD (PDF with embedded XML at EN 16931 profile or higher).

Since January 1, 2025, all B2B businesses must be able to receive e-invoices. Mandatory sending: from 2027 for businesses with revenue above EUR 800,000, and from 2028 for all businesses.

Costs depend on your current infrastructure. Many accounting software packages already include e-invoicing features. The investment typically pays for itself through reduced processing time and fewer errors.

For receiving: yes, since January 2025. The sending obligation kicks in based on revenue thresholds in 2027 and 2028.

Your business partners may be unable to deliver valid invoices to you. This can jeopardize your input tax deduction (Vorsteuerabzug) and create problems during tax audits.

E-invoices must be archived in accordance with GoBD. The original XML file must be stored in a tamper-proof, unalterable format for at least 10 years.

About the Author

Swathy

Swathy

Content Marketer

I’m a Content Marketer at Complyance, focused on e-invoicing. Over the years, I’ve created a wide range of content, including blog posts, whitepapers, and product guides, which have supported Complyance’s growth across markets such as the UAE and EU regions. My goal is to deliver content that is comprehensive, clear, accurate, and easy to understand, no matter how complex the topic.

Related Posts

Complyance Logo

One API for Global E-invoicing