E-Invoicing 2026: What Online Shops Need to Know

Germany's e-invoicing mandate is fundamentally transforming B2B commerce. Since January 1, 2025, all businesses must be able to receive structured e-invoices — and the transition period for paper invoices ends on December 31, 2026. For online shops, this means: those who don't switch to ZUGFeRD or XRechnung in time risk compliance violations and operational disadvantages. In this article, you'll learn which deadlines apply, which format suits your shop, and how to implement the transition step by step.

Why the E-Invoicing Mandate Affects E-Commerce

Approximately 32 billion invoices are issued annually in Germany — over 90 percent still on paper (eco). This equates to roughly 144,000 tons of paper per year, the equivalent of about 48 freight train loads (eco). At the same time, a Bitkom survey shows that 58 percent of companies still operate predominantly paper-based (Bitkom). For e-commerce businesses, this situation is not only ecologically questionable but also economically inefficient.

Germany's Growth Opportunities Act (Wachstumschancengesetz) reformed §14 UStG, setting the course for structured e-invoices based on the European standard EN 16931 to become the new norm. According to IMARC Group, the German e-invoicing market is expected to grow from $713.6 million in 2024 to $2.91 billion by 2033 — an annual growth rate of 16.91 percent (IMARC Group). Online shops that transition early secure operational advantages and avoid last-minute pressure.

The Legal Timeline: All Deadlines at a Glance

The introduction of mandatory e-invoicing occurs in several stages. The Growth Opportunities Act and the amendment to §14 UStG define clear milestones that e-commerce merchants must follow:

ZUGFeRD vs. XRechnung: Which Format Fits?

The two prevalent e-invoicing formats in Germany differ significantly in structure and use case. According to Bitkom, 71 percent of companies that already send e-invoices use EDI formats, 27 percent use ZUGFeRD/Factur-X, and 5 percent use XRechnung (Bitkom). For most online shops, ZUGFeRD and XRechnung are the relevant formats — and both meet the requirements of the Growth Opportunities Act. A detailed comparison is available on our ZUGFeRD and XRechnung page.

For most online shops, ZUGFeRD 2.x is the pragmatic choice: the hybrid format delivers a human-readable PDF invoice while simultaneously containing the structured XML data for machine processing. Integration with existing interfaces and ERP systems such as DATEV or SAP is possible with both formats.

ZUGFeRD Profiles: What Level of Detail Does Your Shop Need?

ZUGFeRD 2.x offers several profiles that differ in the depth of embedded XML data. The choice of profile directly impacts the level of automation and compliance capability of the e-invoice:

For most online shops, the EN 16931 (Comfort) profile or higher is the right choice, as it contains all mandatory fields of the European standard. Those who also serve public sector clients should implement the XRechnung profile directly — this is a subset of the ZUGFeRD standard and fully covers German B2G requirements. E-invoicing awareness in Germany stands at 48 percent, already above the European average of 39 percent (IT-Matchmaker), underscoring growing market maturity.

Decision Guide: ZUGFeRD or XRechnung for Your Use Case

The format choice depends on three factors: your recipients, your level of automation, and your international ambitions. Globally, e-invoice volume is predicted to reach 550 billion invoices by 2025 (Billentis 2024) — a clear sign that structured formats are becoming the worldwide standard.

• Pure B2B commerce without public sector clients: ZUGFeRD 2.x with EN 16931 profile — your customers receive a readable PDF with machine-readable XML data. Ideal for SME shops and trade businesses
• Mixed B2B and B2G: ZUGFeRD 2.x with XRechnung profile — you cover both recipient groups with a single format, eliminating the need for parallel processes
• Purely machine-based processing (high volumes): XRechnung as pure XML — minimal file size, maximum processing speed. Practical for more than 1,000 invoices per month
• International B2B customers: ZUGFeRD 2.x / Factur-X — the German-French hybrid format is also used in France, Belgium, and Switzerland, facilitating cross-border invoicing

Current Status: How Far Has the Economy Progressed?

The level of digitalization varies considerably by company size. While 96 percent of large enterprises with more than 500 employees already use e-invoicing, the figure for mid-sized companies (100-499 employees) is 82 percent, and for small businesses (20-99 employees) only 52 percent (Bitkom). Among the self-employed, only 36 percent have created an e-invoice according to a sevdesk survey (sevdesk).

The good news: 55 percent of German companies already send e-invoices (Bitkom), and of those who made the switch, 86 percent rated it as "easy or very easy" (sevdesk). The technical barriers are therefore lower in practice than feared — provided the implementation is approached in a structured manner.

Practical Implementation for Online Shops

The transition to e-invoicing affects multiple areas of an online shop: from checkout through invoice generation to archiving and ERP connectivity. A structured approach typically avoids redundant work and compliance gaps.

1. Assessment: What invoice formats does your shop currently use? How many B2B invoices are generated monthly? Which ERP systems and accounting solutions are connected?
2. Format decision: ZUGFeRD 2.x or XRechnung? For most e-commerce scenarios, ZUGFeRD with the XRechnung profile is recommended — see the format comparison section above for details
3. Technical integration: Implement an e-invoicing module in the shop system. The XML structure must conform to EN 16931 and contain all mandatory fields per §14 UStG
4. Set up validation: Every outgoing e-invoice should be validated against the EN 16931 schema. Invalid invoices can be rejected by the recipient
5. Adapt ERP connection: The DATEV interface or SAP integration must be able to import structured e-invoices and correctly process the XML data
6. Ensure archiving: E-invoices must be stored in their original format (XML) in accordance with GoBD — at least 10 years, audit-proof
7. Testing and go-live: Test parallel to the existing process, gather feedback from B2B customers, and transition gradually

Automation: From Manual Processes to Straight-Through Processing

The real value of e-invoicing lies not in the mere format change but in automating downstream processes. Paper invoices take an average of 11 days from receipt to approval — digital invoices only 4 days (Bundesverband Materialwirtschaft). The manual error rate of approximately 5 percent can be reduced by over 90 percent through automated processing (Haufe).

For online shops with high transaction volumes, this translates to significant efficiency gains: incoming B2B orders are automatically linked with their corresponding e-invoice, payment receipts are matched directly, and booking data is passed to the ERP system or DATEV interface without media breaks. According to Capgemini, automated processing saves up to 75 percent of previous processing costs (Capgemini).

Technical Integration into Shop Systems

The technical implementation of e-invoicing requirements depends on the shop system in use. Fundamentally, the development must cover three core areas: creating e-invoices in the correct format, validating against the EN 16931 schema, and connecting to downstream systems.

• Invoice generation: The shop system must be able to produce XML data in ZUGFeRD or XRechnung format. With ZUGFeRD, the XML file is embedded within a PDF/A-3 document
• Schema validation: Outgoing e-invoices should be automatically checked against the EN 16931 schema. Invalid invoices can be rejected by the recipient
• Reception capability: Incoming e-invoices (e.g., from suppliers) must be accepted and processed in structured format
• Interface connectivity: DATEV, SAP, or other ERP systems must be able to import e-invoice data in XML format — existing integrations need to be extended accordingly
• Audit-proof archiving: The original format (XML or ZUGFeRD PDF) must be stored GoBD-compliant for at least 10 years

Especially for WooCommerce shops and other open-source systems, integration via dedicated plugins or middleware solutions that fully cover the EN 16931 standard is recommended. Professional consulting ensures the implementation fits your existing infrastructure.

Shopware: Integrating E-Invoicing in the Ecosystem

Shopware offers flexible options for e-invoicing integration through its plugin architecture. Extensions for ZUGFeRD and XRechnung are available through the Shopware Store, mapping the invoicing process directly in the admin backend. Key considerations for implementation include:

• Plugin selection: E-invoicing plugins should support the XRechnung profile within ZUGFeRD 2.x and include built-in validation against the EN 16931 schema
• Leverage Flow Builder: Shopware's Flow Builder enables automatic rules — for example: automatically generate ZUGFeRD invoices for B2B orders while continuing to send standard PDFs for B2C
• Customer group controls: B2B customers can automatically receive e-invoices via customer groups, while end consumers receive the familiar PDF format
• API integration: For custom solutions, the Shopware Admin API provides endpoints for programmatic invoice creation — useful when connecting to external ERP systems like SAP Business One

WooCommerce: E-Invoicing with Open-Source Tools

WooCommerce shops benefit from a broad plugin ecosystem. Both free and commercial extensions are available for e-invoice creation. Since WooCommerce is built on WordPress, e-invoicing functionality can be precisely integrated into existing workflows via hooks and filters:

• Extend PDF invoice plugins: Existing invoice plugins like WooCommerce PDF Invoices can serve as a foundation — ZUGFeRD XML embedding is handled through an additional library such as php-zugferd
• REST API for external systems: The WooCommerce REST API enables passing order data to external e-invoicing services and embedding the finished e-invoice back into the order
• Automatic format detection: Custom checkout fields allow customers to specify whether they prefer ZUGFeRD, XRechnung, or standard PDF
• Cron-based validation: A scheduled WordPress cron job can retrospectively validate outgoing invoices against the EN 16931 schema and flag defective documents for manual review

ERP Integration: DATEV, SAP, and Other Systems

Seamless ERP connectivity is the decisive factor for the degree of automation in e-invoice processing. Companies processing more than 1,000 invoices monthly can save up to 70 percent of their processing costs through full automation (GoCOMET). Requirements vary significantly by system:

DATEV Connectivity for E-Invoices

DATEV Unternehmen online and DATEV Rechnungswesen can directly process incoming e-invoices in ZUGFeRD and XRechnung formats. Your online shop's DATEV interface must meet the following requirements:

• DATEV Format Service: The DATEV Format Service enables automatic import of e-invoices and assignment to the correct booking accounts — without manual intervention
• XML mapping: The mapping of EN 16931 fields to the DATEV chart of accounts (SKR03/SKR04) must be correctly configured so that tax rates, general ledger accounts, and cost centers are automatically recognized
• Document image linking: With ZUGFeRD invoices, the PDF is stored as a document image in DATEV and linked to the accounting entry — significantly simplifying review by the tax advisor
• Batch processing: For high-volume shops, DATEV batch import enables processing hundreds of e-invoices in a single run

SAP Business One Integration

SAP Business One supports e-invoice receipt and dispatch through various channels. For online shops, integration via the Service Layer API or through middleware like the SAP Business One Integration Framework (B1IF) is typical:

• Document Parsing Framework: SAP B1 can automatically convert incoming ZUGFeRD/XRechnung XML files into accounts payable invoices via the Document Parsing Framework
• UDF extensions: User Defined Fields allow storing e-invoice metadata such as routing IDs or order references directly within the invoice document
• Outgoing invoices: SAP B1 can automatically generate outgoing invoices in ZUGFeRD format via add-ons or the DI API and send them to customers by email
• Intercompany scenarios: For corporate groups with multiple SAP instances, e-invoicing enables seamless document flow between entities without media breaks

Costs and Benefits: What Does the Transition Deliver?

The transition to e-invoicing is not just a legal obligation — it offers measurable economic benefits. Initial implementation costs typically pay for themselves quickly through operational savings and efficiency gains.

An online shop sending 500 B2B invoices monthly can typically save €4,000 to €6,500 per month by switching to e-invoicing — from reduced processing costs alone. Additional savings come from printing, postage, and archiving. The European e-invoicing market is projected to grow from $2.03 billion (2025) to $5.93 billion (2033) according to IMARC Group (IMARC Group) — a clear signal of economic significance.

Challenges and Obstacles in the Transition

Despite the clear advantages, many companies face practical hurdles. According to Bitkom, 75 percent of respondents cite transition costs as an obstacle, and equally 75 percent mention the skills shortage in implementation (Bitkom). Both factors play a particularly significant role for small and medium-sized online shops.

• Legacy systems: Older shop and ERP systems don't natively support EN 16931 — extensions or a system change may be required
• Lack of expertise: Correct implementation requires know-how in XML schema validation, PDF/A-3 generation, and ERP interfaces
• Supplier dependency: Incoming invoices from suppliers must also be processable in e-invoice format
• Parallel operation: During the transition phase, paper and e-invoice processes must run in parallel — this temporarily increases workload
• Training needs: Staff in accounting and order processing need training on the new processes

Common Mistakes When Implementing E-Invoicing

Practice reveals recurring mistakes that jeopardize the success of e-invoicing rollouts. E-invoicing adoption in Germany has grown from 19 percent (2018) through 30 percent (2020) and 45 percent (2022) to 59 percent in 2023 (Bitkom) — yet the same pitfalls continue to appear during implementation:

1. Misunderstanding PDF as e-invoice: A plain PDF without embedded XML data does not qualify as an e-invoice under the law. Even a PDF with an attached XML file is insufficient — with ZUGFeRD, the XML must be embedded within the PDF/A-3 container
2. Choosing the wrong ZUGFeRD profile: The Minimum profile does not contain sufficient data for EN 16931 compliance. Only the EN 16931 (Comfort), Extended, and XRechnung profiles fully meet the legal requirements
3. Skipping validation: Outgoing e-invoices are not checked against the official EN 16931 schema. Invalid invoices can be rejected by recipients, delaying payment receipts
4. Archiving in the wrong format: E-invoices must not be archived exclusively as printouts or converted PDFs. GoBD requires retention in the original format (XML/ZUGFeRD PDF) for at least 10 years
5. Not separating B2C and B2B: The e-invoicing mandate applies exclusively to B2B transactions between domestic businesses. A common mistake is issuing consumer invoices in e-invoice format, causing confusion
6. Not testing ERP imports: The XML data is generated correctly, but the import into DATEV or SAP was never tested. Field mappings, tax rate assignments, and chart of accounts must be validated upfront
7. Forgetting the routing ID: For invoices to public sector clients (B2G), the Leitweg-ID (routing ID) is a mandatory field. Without it, the invoice is rejected — a point frequently overlooked during implementation

Validation and Testing: Verifying and Securing E-Invoices

A robust validation process is the backbone of a functioning e-invoicing infrastructure. Defective e-invoices not only lead to rejections by recipients but can also have tax consequences — for instance, when input tax deduction is denied due to formal defects. Validation should occur at multiple levels:

Several validation tools are available for technical implementation: KoSIT (Coordination Office for IT Standards) provides the KoSIT Validator, an open-source tool that checks e-invoices against official Schematron rules. For automated workflows, this validator can be integrated into CI/CD pipelines or as middleware in the invoice dispatch process. Additionally, services like the ZRE portal (Central Invoice Receipt) offer online validation for XRechnung documents.

• Syntax validation against EN 16931 XSD schema configured
• Schematron rules for business logic activated
• PDF/A-3 conformity check for ZUGFeRD implemented
• Test dispatch to at least three different recipient systems completed
• Automatic error notification for validation failures configured
• Regular checks against updated Schematron versions scheduled

EU Perspective: ViDA and Cross-Border E-Invoicing

Germany's e-invoicing mandate is part of a larger European trend. With the VAT in the Digital Age (ViDA) initiative, the EU Commission plans to introduce mandatory cross-border e-invoicing from July 2030 (EU Commission). For online shops with international B2B customers, this means: the infrastructure built now for ZUGFeRD and XRechnung forms the foundation for Europe-wide compliance.

The European e-invoicing market is growing from $2.03 billion (2025) to a projected $5.93 billion (2033) (IMARC Group). Countries like Italy, France, and Spain have already introduced national e-invoicing mandates. Germany is catching up with these pioneers through the Growth Opportunities Act. For internationally operating shops, looking beyond national borders is therefore worthwhile.

What ViDA Specifically Means for Online Shops

The ViDA initiative encompasses three pillars that directly affect cross-border e-commerce: first, mandatory electronic invoicing for intra-Community supplies from July 2030; second, a digital real-time reporting system for cross-border B2B transactions; and third, modernization of VAT registration through a unified EU platform.

For online shops with EU-wide shipping, this specifically means: invoice data must be reported to a central EU system within two business days after invoicing. This requires a fully automated invoicing infrastructure that operates without manual intervention. Those investing in ZUGFeRD and XRechnung today are building the technical foundation for these Europe-wide requirements.

Checklist: E-Invoicing Compliance for Your Online Shop

• Reception capability for e-invoices (EN 16931) confirmed
• Format selected: ZUGFeRD 2.x or XRechnung
• Shop system extended with e-invoicing module
• Schema validation for outgoing invoices implemented
• ERP/DATEV interface adapted for structured XML data
• GoBD-compliant archiving in original format set up
• Parallel operation paper/e-invoice tested during transition
• Accounting and order processing staff trained
• B2B customers informed about new invoice format
• Monitoring for validation errors and delivery issues activated

Frequently Asked Questions About E-Invoicing in E-Commerce