Switzerland and Germany are close trading partners, share a language in most of the country, and both operate within the broader European e-invoicing ecosystem. But their approaches to e-invoicing are meaningfully different — different mandates, different timelines, different accepted formats, and different infrastructure. If your company operates in both markets, or if you are a Swiss business with significant German customers or suppliers, understanding those differences matters.
The regulatory starting point
Germany began its e-invoicing journey with the EU public procurement directive (2014/55/EU), which required all EU member states to accept structured electronic invoices for public procurement above certain thresholds. Germany implemented this for federal procurement with XRechnung — a pure XML format based on the UN/CEFACT CII syntax — and PEPPOL as the delivery channel. For state (Länder) and municipal procurement, implementation timelines varied by state, but most German public sector buyers can now accept structured invoices.
In late 2024, Germany announced a B2B e-invoicing mandate — one of the most significant developments in European e-invoicing in years. Under the Wachstumschancengesetz, German domestic B2B invoicing becomes mandatory for structured electronic formats in phases:
- From 1 January 2025: all German businesses must be able to receive structured e-invoices
- From 1 January 2027: businesses with revenue above €800,000 must send structured e-invoices
- From 1 January 2028: the mandate applies to all German B2B businesses
The accepted formats for German B2B e-invoicing are XRechnung and ZUGFeRD (from version 2.0 onwards, which complies with EN 16931). Simple PDF invoices — even those with structured data attached in non-compliant ways — will not satisfy the mandate.
Switzerland has a narrower and more recent mandate. The revised Federal Finance Ordinance (Bundesfinanzverordnung) requires suppliers to the Swiss federal administration to submit invoices electronically from 2026. The accepted channels are eBill and PEPPOL, using the SwissDIGIN extension of PEPPOL BIS Billing 3.0. There is currently no Switzerland-wide B2B e-invoicing mandate — the requirement applies only to federal government suppliers. Some cantonal authorities are introducing their own requirements on different timelines, but these vary significantly.
Accepted formats: what each country expects
In Germany, the landscape has two main formats:
XRechnung is pure XML — UN/CEFACT CII or UBL 2.1 — with no visual PDF component. It is required for federal government invoicing and is increasingly the expected format for state procurement. Recipients need a system that can process XML directly; there is no embedded PDF for human reading.
ZUGFeRD (from version 2.x) is the hybrid PDF/XML format — the same standard as Factur-X. The PDF/A-3 file contains both a human-readable invoice and an embedded XML payload. ZUGFeRD is widely accepted in German B2B invoicing, especially for the transition period, because the PDF component means the invoice can be read by any recipient regardless of their system capabilities.
In Switzerland, the picture is:
PEPPOL BIS Billing 3.0 with the SwissDIGIN extension is the standard for B2G invoicing via the PEPPOL channel and for structured B2B invoicing between companies that have connected to the PEPPOL network.
eBill is the Swiss consumer and SME channel — invoices delivered through the payer's e-banking. It uses a proprietary SIX format internally, but what matters to billers is what their service provider accepts, not the internal protocol.
ZUGFeRD and QR-Rechnung are also used in Switzerland, particularly ZUGFeRD for companies invoicing German counterparts (where the format is native) and QR-Rechnung for domestic payment references. Neither is formally required by the Swiss mandate, but both are widely used in practice.
The key structural difference: mandatory receiving vs mandatory sending
Germany's 2025 requirement that all businesses must be able to receive structured e-invoices is a significant policy choice that Switzerland has not made. It means that from the start of 2025, a German SME with annual revenue of CHF 200,000 must have a system capable of processing an XRechnung XML file — even if that SME has no obligation to send structured invoices until 2028.
Switzerland has no equivalent receiving mandate. A Swiss supplier who receives an invoice — even from a PEPPOL-connected sender — has no legal obligation to process it as structured data rather than printing the PDF.
This asymmetry matters for cross-border trade. A Swiss company selling to a German business buyer needs to send a structured e-invoice if that buyer requires it — and from 2025 they have an incentive to require it. A German company selling to a Swiss business buyer faces no equivalent pressure, because the Swiss recipient has no obligation to demand structured invoices.
VAT treatment and reporting differences
Swiss VAT operates at a single federal level — three rates (8.1%, 2.6%, 3.8%), reported to the ESTV quarterly or annually. German VAT is also federal — two main rates (19% and 7%) with a more complex system of exemptions — but the move to mandatory e-invoicing in Germany is partly driven by plans for a future transaction-based reporting system (similar to Italy's SDI or Portugal's AT) where invoice data is reported to the tax authority in real time or near real time.
Switzerland has no plans for transaction-based VAT reporting at the time of writing. The Swiss mandate is about invoice delivery and format, not about reporting invoice data to a government system.
This is an important distinction: Germany's B2B e-invoicing mandate is in part infrastructure for future real-time tax control. Switzerland's mandate is primarily about administrative efficiency in federal procurement. The underlying goals are different, which explains some of the structural differences in approach.
What this means if you trade in both markets
If you are a Swiss company that invoices German B2B customers, the practical implications are:
You should be able to generate ZUGFeRD or XRechnung invoices for your German B2B customers. From 2025, your German customers have the right to request a structured format, and from 2027 for larger customers, you may have no choice. Setting up ZUGFeRD generation now — either through your ERP or a conversion layer — means you are ready rather than reactive.
If you are already registered as a PEPPOL participant in Switzerland for Swiss B2G invoicing, you can use the same PEPPOL connection to reach German PEPPOL-registered buyers. The network is shared; Switzerland's PEPPOL access points connect to German ones.
If you are a German company invoicing Swiss customers, you do not face a Swiss mandate for B2B invoicing, but offering structured formats (ZUGFeRD is native to you) may be appreciated by Swiss customers who are modernising their AP processes.
Format compatibility: where they overlap
ZUGFeRD 2.x / Factur-X is the main point of practical overlap. It is accepted in Germany, increasingly used in Switzerland, and based on EN 16931, which means a ZUGFeRD invoice generated for a German customer uses the same underlying standard as a SwissDIGIN PEPPOL invoice. The difference is the Swiss-specific extensions — UID, Swiss VAT codes, Swiss payment references — which are required for the SwissDIGIN profile but not relevant for a German recipient.
A company that implements EN 16931-compliant invoice generation can serve both markets with relatively modest configuration differences rather than two entirely separate implementations. The comparison of ZUGFeRD and XRechnung covers the format-level choices in more detail.