Germany E-Invoicing 2027 vs 2028 Are You Above or Below the EUR 800,000 Threshold

Germany’s B2B e-invoicing rollout is no longer a future compliance topic it is already underway. 

Since 1 January 2025, businesses in Germany are required to receive structured electronic invoices. The next critical milestone focuses on issuing e-invoices, raising an important question: 

Will your business need to comply by 2027, or do you qualify for the extended transition period until 2028? 

The answer depends on one key figure: €800,000 annual turnover. 

• If your previous year’s turnover exceeds €800,000, your business must issue compliant B2B e-invoices starting 1 January 2027.  

• If your turnover is €800,000 or below, you may benefit from the extended transition period until 1 January 2028.  

For finance teams, ERP managers, and business owners, this is more than a regulatory update. It directly impacts how invoices are created, transmitted, validated, archived, and integrated across your systems. 

What Is the EUR 800,000 Threshold in Germany’s E-Invoicing Mandate? 

The €800,000 threshold determines when a business must begin issuing structured electronic invoices under Germany’s phased B2B e-invoicing rollout. 

In simple terms: 

• Above €800,000 annual turnover → mandatory B2B e-invoice issuing from 1 January 2027  

• €800,000 or below → transitional allowances may apply until 31 December 2027, with full compliance required from 1 January 2028 

This distinction is particularly important for businesses still relying on PDFs, paper invoices, email attachments, or partially manual ERP invoice workflows. 

During the transition phase, certain non-structured invoice formats may still be permitted under specific conditions. However, that flexibility is temporary and gradually disappearing as Germany moves toward fully structured electronic invoicing. 

One common mistake businesses make is assuming:
“We are below the threshold, so we still have time.” 

In practice, waiting can create operational and compliance challenges later. Customers, suppliers, and larger trading partners may begin requiring structured e-invoices well before the final legal deadline, especially as ERP integrations and automated invoice processing become standard across supply chains. 

Germany E-Invoicing Timeline: 2025, 2027, and 2028 

Germany’s B2B e-invoicing mandate is being introduced in stages. Understanding the timeline helps you plan implementation without rushing at the last minute. 

-> 2025: Receiving E-Invoices Is Already Required 

From 1 January 2025, German businesses must be able to receive structured e-invoices.  

This means your company should already have a process for handling compliant electronic invoices, even if you are not yet required to issue them in every case. 

A standard PDF invoice alone does not qualify as a structured electronic invoice under the new requirements. While a PDF may appear digital to humans, compliant e-invoicing requires invoice data that can be automatically processed by business systems. 

-> 2027: Businesses Above EUR 800,000 Must Issue E-Invoices 

From 1 January 2027, companies with turnover above EUR 800,000 in the relevant prior year must issue structured e-invoices for applicable domestic B2B transactions.  

This is the deadline that larger businesses cannot afford to ignore. By this point, invoice creation should not depend on manual formatting, PDF generation, or ad hoc email sending. 

-> 2028: Full B2B E-Invoicing Obligation Applies More Broadly 

From 1 January 2028, the issuing obligation applies more broadly to businesses that were previously covered by transition rules.  

This means businesses below the €800,000 threshold should also prepare well in advance rather than waiting until the final deadline approaches. 

By then, structured e-invoicing will be a standard part of B2B transactions in Germany. 

Above EUR 800,000? What You Should Do Before 2027 

If your business exceeds the €800,000 turnover threshold, the 2027 e-invoicing deadline is closer than it appears from an implementation perspective. 

Becoming e-invoicing-ready is not simply about installing a new tool. Businesses need to evaluate invoice workflows, ERP capabilities, customer requirements, invoice formats, validation processes, and long-term archiving procedures. 

Review Your Current Invoice Process 

Start by examining how invoices are currently created and exchanged. 

• Are invoices generated directly from your ERP?  

• Are they exported as PDFs?  

• Are invoices sent manually by email?  

• Do employees copy invoice data between systems?  

Every manual step increases operational risk. 

Under structured e-invoicing requirements, invoice data must be accurate, machine-readable, and processable by business systems. Workflows that rely heavily on manual entry, spreadsheet corrections, or PDF-based handling can become difficult to scale and maintain efficiently. 

Check ERP Readiness 

Your ERP system should be able to generate or exchange structured invoice data.  

For many businesses, the ERP already contains most of the required invoice information, but the challenge is transforming and transmitting it in the right format. 

This is where integration becomes critical.  

A good e-invoicing setup should connect your ERP with the required invoice format and delivery channel, instead of creating a separate process outside your core systems. 

Identify Required Invoice Formats 

Germany’s e-invoicing framework supports structured invoice formats compliant with the European standard EN 16931. 

Common examples include: 

• XRechnung  

• ZUGFeRD  

• Peppol BIS Billing 3.0  

• Certain EDI-based exchanges permitted under transitional arrangements  

Different customers and trading partners may require different formats or delivery channels. 

For example: 

• One customer may request XRechnung  

• Another may exchange invoices via Peppol  

• Others may rely on direct ERP-to-ERP integration  

Your invoicing setup should be flexible enough to support multiple invoice formats and communication channels. 

The following overview shows how modern e-invoicing ecosystems typically connect ERP systems, structured invoice formats, delivery channels, and trading partners.

Test Before the Deadline 

Do not wait until January 2027 to test your first structured invoice. 

Testing should include: 

• Invoice data extraction from ERP 

• Format conversion 

• Validation 

• Delivery 

• Error handling 

• Receiving confirmation 

• Archiving 

The earlier you test, the easier it is to fix gaps. 

Below EUR 800,000? Why Waiting Until 2028 can Still Be Risky 

If your turnover is EUR 800,000 or below, you may have more time before mandatory issuing applies. 

However, that does not mean businesses should postpone e-invoicing preparation until the final deadline approaches. 

There are several practical reasons why early preparation still matters. 

Your Customers May Require It Earlier 

Large customers, enterprise buyers, public-sector-related organizations, and international trading partners may require structured invoices before your final deadline. Even if transition rules allow you to wait, your customer’s procurement process may not. 

If a key customer asks for XRechnung or Peppol invoices in 2027, you need to be ready. 

Receiving E-Invoices Is Already Mandatory 

The 2028 deadline mainly concerns issuing for businesses under the threshold. Receiving compliant e-invoices has already been part of the rollout from 2025.  

This means finance and accounting teams should already have processes in place for: 

• Receiving structured invoices  

• Reading invoice data  

• Validation  

• Error handling  

• Secure storage and archiving 

E-invoicing projects often involve multiple departments, including: 

• Finance  

• IT  

• ERP administrators  

• Operations  

• Compliance teams  

• Customer onboarding teams  

Even smaller businesses can face delays when dealing with: 

• Customer-specific invoice requirements  

• ERP mappings  

• Validation rules  

• Approval workflows  

• Integration testing  

Waiting until late 2027 may create unnecessary implementation pressure and increase the risk of rushed onboarding or operational disruptions.

What Counts as a Valid E-Invoice in Germany? 

A common misunderstanding is that any digital invoice is an e-invoice. That is not correct. 

A simple PDF sent by email may be electronic in a basic sense, but it is not a structured e-invoice under Germany’s mandate. A valid e-invoice must be issued in a structured electronic format that allows automated processing and is compliant with the required standard. 

Common formats include: 

XRechnung 

XRechnung is a structured XML-based invoice format widely used in Germany, especially in public-sector and compliance-driven invoicing. 

ZUGFeRD 

ZUGFeRD combines a human-readable PDF with embedded structured XML data. It is useful for businesses that want both readability and machine processing. 

Peppol BIS Billing 3.0 

Peppol is widely used for standardized document exchange across business networks. It supports structured e-invoicing and is helpful for companies working across borders or with trading partners that already use Peppol. 

EN 16931-Compliant EDI 

Certain EDI processes may also be used when they meet the required standard. During transition periods, some EDI procedures have specific allowances, but businesses should still evaluate long-term compliance carefully. 

Common Mistakes Businesses Make with the 2027 and 2028 Deadlines 

Many businesses understand the deadline but underestimate the operational changes behind it. 

Mistake 1: Thinking PDF Is Enough 

PDF is familiar, easy to send, and widely used. But a standard PDF is not a structured e-invoice. If your process still depends on PDF-only invoicing, you need a conversion and automation plan. 

Mistake 2: Treating E-Invoicing as Only a Compliance Project 

Compliance is the trigger, but automation is the bigger opportunity. E-invoicing can reduce manual entry, speed up invoice processing, improve accuracy, and create better visibility across finance operations. 

Mistake 3: Not Connecting E-Invoicing with ERP 

If e-invoicing happens outside your ERP, your team may still need manual checks, uploads, downloads, and corrections. That weakens the value of automation. 

The better approach is to connect e-invoicing directly with ERP workflows. 

Mistake 4: Ignoring Customer-Specific Requirements 

The legal format is one part of the story. Customer requirements are another. Some customers may require invoices through Peppol, some may need specific fields, and some may reject invoices that do not pass validation. 

Mistake 5: Waiting Until the Deadline 

E-invoicing projects often involve mapping, testing, validation, user training, and supplier or customer coordination. A late start increases the risk of failed invoice delivery and payment delays. 

How HubBroker Helps You Prepare for Germany E-Invoicing 

HubBroker helps businesses move from manual invoice handling to automated, integrated e-invoicing workflows. Instead of treating e-invoicing as a separate finance task, HubBroker connects invoice data with your existing systems and trading partner requirements. 

With HubBroker, businesses can manage: 

• E-invoicing automation 

• Peppol connectivity 

• ERP integration 

• EDI document exchange 

• PDF, XML, and structured document conversion 

• Invoice validation 

• Document routing 

• Automated processing and reduced manual entry 

For companies above the EUR 800,000 threshold, HubBroker can help prepare for the 2027 issuing deadline. For companies below the threshold, HubBroker can help build a future-ready process before 2028 pressure begins. 

The goal is simple: make e-invoicing easier, faster, and less dependent on manual work. 

Germany E-Invoicing Readiness Checklist

1. Confirm Your Turnover Category

Check whether your business is above or below the EUR 800,000 threshold. This helps determine whether your issuing obligation starts in 2027 or 2028. 

2. Review Your Invoice Types

Identify which invoices are domestic B2B invoices, which are cross-border, which are B2C, and which may be exempt. The mandate mainly focuses on domestic B2B transactions between German-established businesses. 

3. Identify Required Formats 

Check whether your customers require XRechnung, ZUGFeRD, Peppol, EDI, or another compliant format. 

4. Check ERP Capabilities

Find out whether your ERP can generate structured invoice data or whether you need middleware to transform, validate, and send invoices. 

5. Review Receiving Workflow

Your business should already be able to receive structured e-invoices. Make sure your team can process them without manual confusion. 

6. Plan Validation and Error Handling

A structured invoice can still fail if required fields are missing or formatted incorrectly. Build validation into the process before sending. 

7. Prepare Archiving

E-invoices must be stored correctly for audit and tax purposes. Make sure your archiving process supports structured documents. 

8. Test with Real Scenarios

Use real customer and supplier flows to test invoice creation, delivery, receipt, and processing. 

9. Automate Where Possible

Manual work increases delays and errors. Automation helps finance teams stay compliant while improving day-to-day operations. 

Ready to Find Out Whether 2027 or 2028 Applies to You? 

Germany’s e-invoicing mandate is moving quickly. Whether your business is above or below the EUR 800,000 threshold, now is the right time to review your invoicing process and prepare your systems. 

Book a demo with HubBroker to see how your business can automate e-invoicing, connect with ERP systems, support Peppol and EDI workflows, and get ready for Germany’s 2027 and 2028 requirements.