Germany’s 2025 E-invoicing mandate requires all VAT-registered businesses to receive structured, machine-readable invoices (e.g., XRechnung, ZUGFeRD). Companies must ensure compliant reception, validation, workflow integration, and long-term archiving to meet EN 16931 and GoBD rules.
Key takeaways
- From 2025, all German B2B recipients must accept EN 16931-compliant e-invoices; PDFs alone no longer qualify.
- Mandatory issuance begins in phases: reception in 2025, issuance for large companies in 2027, and full issuance for all businesses in 2028.
- Accepted formats include XRechnung, ZUGFeRD, Peppol BIS 3.0, and other compliant XML structures.
- Email, Peppol, EDI, portals, and ERP interfaces serve as transmission channels.
- Recipients must validate syntax and tax data before posting and archive the original XML/PDF-XML for 10 years under GoBD.
The transition from manual invoicing to e-invoicing is structured into three key phases:
Phase | Date | Requirement |
Immediate Reception | Jan 1, 2025 | All businesses must be able to receive and archive e-invoices. No size or turnover exceptions. Issuing remains voluntary. |
Large Business Issuance | Jan 1, 2027 | Mandatory e-invoice issuance for companies with turnover > €800,000. Smaller companies may still issue paper/PDFs. |
Full Implementation | Jan 1, 2028 | Mandatory e-invoice issuance for all businesses. Transitional EDI relief ends. |
Receiving an e-invoice means accepting an invoice in a fully structured, machine-readable format not just as a visual document. Unlike paper or unstructured PDF invoices, a true e-invoice contains embedded data fields (XML/UBL) that can be automatically validated and processed by your financial systems.
To “receive” an e-invoice in the legal sense, a company must be able to:
All businesses conducting domestic B2B transactions in Germany must be able to receive e-invoices there are no exemptions, transition periods, or company size thresholds for reception.
Out of Scope
German B2B recipients must be able to receive structured EN 16931-compliant e-invoices with the following requirements.
Receiving an e-invoice can be broken down into a few clearly defined steps.
The simplest method is email, since XML or ZUGFeRD files can be sent directly as attachments to a dedicated address. Alternatively or additionally, companies can be reachable via the Peppol network, use an ERP connector, or centralize receipt through an e-invoice platform such as ClearTax.
This can be a standardized email address such as invoice@company.com or a Peppol ID that uniquely identifies the company.
The received e-invoices must be opened or automatically imported into the software in use. Modern systems recognize the format, extract structured data, and check whether all required fields are included.
When an e-invoice is sent, it arrives via the chosen channel.
The system checks whether the invoice complies with the technical EN 16931 schema, whether the XML structure is error-free, and whether all tax-relevant information is present.
If the file contains errors, a corrected e-invoice must be requested. Once validation is complete, the invoice can be routed through the internal workflow (approval process, accounting, payment release).
The original XML file must be stored unchanged for at least ten years. Platforms like ClearTax automate this step, so companies do not need to build their own archiving structures.
Germany accepts two main formats for e-invoicing: XRechnung and ZUGFeRD, both compliant with the European EN 16931 standard.
This is Germany’s official e-invoice format for public-sector invoicing and the reference format for B2B. XRechnung is an XML-based format strictly aligned with the semantic model of EN 16931, a structured text file not intended for direct human reading. It contains all invoice elements in a hierarchical data structure.
The advantage is complete, standardized data everything from VAT IDs to line-item details and tax rates is uniformly labeled, enabling automatic validation and processing.
The “Central User Guide of the Forum Elektronische Rechnung Deutschland” (ZUGFeRD) is a hybrid format. A ZUGFeRD invoice is essentially a PDF/A-3 file that contains an embedded XML file. It combines a human-readable PDF with machine-readable XML data representing the invoice.
ZUGFeRD is particularly popular among SMEs because recipients can open the PDF while accounting software extracts the XML for automated processing. It bridges the old and the new PDF readability plus structured e-invoice data.
Other structured XML and EDI based formats may also be accepted in Germany when they fully comply with the European standard EN 16931, which defines the mandatory semantic data model for e invoices.
These formats include UN/CEFACT CII (Cross Industry Invoice), a highly structured XML standard used in many international supply chain environments, and UBL (Universal Business Language), a widely adopted XML syntax for procurement and invoicing documents.
Certain EDI (Electronic Data Interchange) message types such as EDIFACT INVOIC can also qualify if the exchanged data is mapped to the EN 16931 core elements.
In B2G, e-invoices must follow strict rules: they must be submitted in a structured format (e.g., XRechnung/EN 16931) and routed through official channels such as ZRE, OZG-RE, email (XML-only), or PEPPOL. These channels ensure validation, routing via the Leitweg-ID, and compliance with federal/public-sector requirements.
In B2B, companies have greater flexibility and may use PEPPOL, ZUGFeRD, EDI, email, or ERP/API integrations, as long as the format complies with EN 16931.
Transmission Channel | Description (Short) | Supported Formats | Ideal Use Case & Key Notes |
Email Transmission | Standard SMTP email delivery with invoice as attachment | XML (XRechnung, UBL), ZUGFeRD PDF | Minimum legal requirement; easy for SMEs; limited automation; not suitable for high-volume scenarios |
Peppol Network | Structured 4-corner model via certified Access Points; automated, secure exchange | PEPPOL BIS 3.0 (UBL), EN 16931 | Best for scalable B2B/B2G transmission; supports APIs, polling, webhooks; includes automatic validation & delivery confirmation; uses Peppol Receiver ID (Germany: 0204 + Leitweg-ID) |
Web Portal Upload | Manual upload or browser-based entry into recipient’s portal | XRechnung XML, EN 16931-compliant formats | Ideal for low-volume senders; typical for B2G via OZG-RE; simple but manual; not scalable |
Electronic Interfaces (EDI / APIs / SFTP) | Direct machine-to-machine integration using EDI, SFTP file drops, or REST APIs | EDIFACT, XML, UBL, custom APIs | Best for enterprises and high invoicing volumes; enables automation; traditional EDI networks supported; requires IT integration |
Shared Access | Secure shared cloud folders or internal shared storage for invoice exchange | XML, PDF/XML hybrids | Useful within corporate groups; controlled access; requires governance; Physical media (USB/CDs) are prohibited |
Validation and archiving of B2B e-invoices in Germany must follow GoBD rules so invoices stay audit-proof and support VAT deduction.
ClearTax offers a powerful all-in-one solution for receiving, validating, and archiving e-invoices . Here is how ClearTax helps
The transition to e-invoicing is not optional for companies in Germany it is mandatory starting in 2025. Companies that can receive and process e-invoices not only meet legal requirements but also benefit from more efficient processes, fewer errors, and faster invoice handling.
Critical steps include choosing the right reception channels, ensuring proper validation, and archiving the original structured file unchanged. Platforms like ClearTax handle all of these tasks centrally, automatically, and fully compliantly, helping companies transition smoothly into the digital invoicing world.