Mandatory structured electronic invoicing for domestic business-to-business transactions in Germany is introduced in phases. Since 1 January 2025, businesses established in Germany must be able to receive e-invoices. The transition rules for issuing e-invoices run until the end of 2027, with broad mandatory issuance applying from 1 January 2028.
This guide explains the deadlines, accepted formats and practical steps for preparing your finance systems. It is based on the current guidance from the German Federal Ministry of Finance (BMF).
Germany e-invoicing implementation timeline
The German B2B mandate is being introduced through the following stages:
| Phase | Requirement | Date |
|---|---|---|
| Mandatory receipt | Businesses established in Germany must be able to receive a structured e-invoice. A dedicated transmission method is not prescribed. | From 1 January 2025 |
| General transition period | All issuers may continue to use paper invoices or, with the recipient’s consent, other electronic invoices such as PDFs. | Until 31 December 2026 |
| Extended transition | Issuers with prior-year turnover of no more than €800,000 may continue using other invoices. Non-conforming EDI procedures may also continue during 2027. | Until 31 December 2027 |
| Broad mandatory issuance | Structured e-invoices become mandatory for in-scope domestic B2B transactions after the transition periods end. | From 1 January 2028 |
Scope: The rules generally apply to taxable transactions between businesses established in Germany. Exceptions include certain VAT-exempt transactions, small-value invoices of up to €250 and tickets. Small businesses under the German small-business VAT regime are exempt from the issuance obligation but must still be able to receive e-invoices.
Enforcement: Germany applies its existing VAT invoicing and record-retention rules. Section 26a of the German VAT Act provides fines of up to €5,000 for certain failures to issue or retain invoices. The consequences depend on the specific breach.
Accepted German e-invoice formats
An e-invoice must be issued, transmitted and received in a structured electronic format that enables automated processing. A simple PDF is not an e-invoice under the German rules introduced in 2025.
Common compliant formats include:
- XRechnung: Germany’s structured XML specification based on EN 16931. It can use UBL or UN/CEFACT CII syntax.
- ZUGFeRD: A hybrid PDF/A-3 document with embedded CII XML. Versions from 2.0.1 can qualify, except the MINIMUM and BASIC-WL profiles.
- Other structured formats: Formats that comply with EN 16931, or an agreed structured format from which the required VAT data can be extracted correctly and completely.
For hybrid invoices, the structured data is decisive if it differs from the visual PDF representation. Businesses must retain at least the structured part in its original form for eight years.
How invoices can be exchanged
German law does not prescribe one delivery network. Businesses may exchange compliant files by email, portal, system interface or a network such as Peppol. The selected channel must preserve the structured invoice and support reliable processing.
Peppol is not mandatory for German B2B invoicing, but it provides a standardised delivery route for EN 16931-based documents. A certified Peppol Access Point can connect the sender and recipient without a bilateral transport integration.
Your e-invoicing readiness in four steps
1. Determine which transactions are in scope
Map your German entities, transaction types and customer relationships before changing systems.
- Identify domestic B2B transactions. Confirm that both parties are established in Germany and that the transaction is not covered by an exception.
- Review your turnover threshold. The €800,000 prior-year turnover threshold affects whether an issuer may use the extended transition during 2027.
- Separate B2B and B2G requirements. Public-sector invoicing follows federal and state-specific rules and may require XRechnung, a Leitweg-ID and a designated portal or delivery channel.
- Confirm retention requirements. Make sure the original structured data can be stored, retrieved and audited for the required period.
2. Choose formats and delivery channels
Agree on the operational formats and channels your organisation will support. XRechnung is suitable for machine-to-machine processing, while ZUGFeRD may help workflows that also require a readable PDF representation.
- Set a preferred format. Choose XRechnung, ZUGFeRD or another compliant structured format for each relevant workflow.
- Define your channel strategy. Decide where email, portal, API or Peppol delivery is appropriate.
- Check customer requirements. Large buyers and public authorities may specify routing references, validation rules and submission channels.
- Plan exception handling. Define how rejected files, invalid VAT data and duplicate invoices will be investigated and corrected.
3. Configure and test your systems
Update your ERP, billing or accounting environment so invoice data is created and processed as structured data rather than rendered only as a PDF.
- Map mandatory fields. Confirm that all VAT invoice data is present in the structured component.
- Validate before delivery. Test syntax, EN 16931 rules and the applicable XRechnung or network validation rules.
- Test inbound processing. Verify that received XML can be displayed, approved, posted and archived without manual re-entry.
- Run end-to-end tests. Include customer addressing, delivery status, rejection handling and original-format storage.
4. Go live and monitor compliance
Move supplier and customer groups in controlled stages and monitor the first production flows closely.
- Track transition dates. Update your rules when the general transition ends on 31 December 2026 and the extended transition ends on 31 December 2027.
- Monitor validation errors. Use structured error information to correct recurring data and mapping problems.
- Maintain master data. Keep VAT identifiers, legal names, addresses, payment data and customer references current.
- Review regulatory updates. Follow the official BMF e-invoicing FAQ for changes and clarifications.
Get started with Qvalia
Qvalia is a certified Peppol Access Point and lists Germany as an accredited market. Qvalia supports Peppol delivery and XRechnung through the Invoicing API. Available web-based and integration capabilities depend on the selected service scope.
- Choose a service model. Review Qvalia’s plans for web-based sending and receiving, API access and sandbox testing.
- Configure your invoice data. Map ERP or billing data to the required structured format and validation rules.
- Test with trading partners. Confirm addressing, delivery and automated processing before moving invoice volumes to production.
- Maintain more than one route where required. Combine Peppol with other compliant delivery channels according to customer and public-sector requirements.
Review Qvalia’s Peppol and e-invoicing country coverage or contact us to define your German e-invoicing setup.