Electronic invoicing is becoming the default invoicing method in Germany, with a phased mandate covering business-to-business and business-to-government transactions. From 1 January 2025, every business must be able to receive EN 16931-compliant structured e-invoices, while the obligation to issue them is introduced gradually between 2027 and 2028 based on turnover.
Key takeaways
- 1 January 2025: the ability to receive e-invoices is mandatory; paper or PDF invoices are allowed only with recipient's consent during 2025–2026
- 1 January 2027: businesses with a turnover greater than 800,000 euro in the prior year must issue e-invoices for B2B transactions
- 1 January 2028: all businesses must issue B2B e-invoices, except for clearly defined exemptions
- Officially accepted formats are XRechnung, ZUGFeRD version 2.0 or later, and Peppol BIS Billing 3.0, all compliant with EN 16931
- Key exemptions include micro-businesses under 22,000 euro turnover for issuing, and invoices below 250 euros using simplified rules
An e-invoice is a digitally structured invoice issued and received in an electronic format that is machine-readable and can be automatically processed without human intervention. Unlike a PDF or paper invoice, an e-invoice contains data in a standardized format (such as XML) that allows software systems to interpret, validate, and process the invoice automatically.
This differs from simply emailing a PDF invoice, which requires manual processing. E-invoices must comply with the European standard EN 16931 to be considered legally valid electronic invoices in Germany.
The German government is implementing mandatory e-invoicing as part of the Growth Opportunities Act (Wachstumschancengesetz) to achieve several objectives.
All German resident businesses and foreign businesses with a permanent establishment in Germany must comply with e-invoicing rules. This includes:
Non-residents of Germany without a fixed establishment are not covered by the domestic mandate but must still accept e-invoices from German trading partners when they make intra-EU supplies.
The mandate applies to both goods and services. The e-invoicing requirements under German law are technology-neutral and apply to all B2B transactions involving the supply of goods, services, or a combination of both.
The type of supply (good, service, or mixed) does not change the obligation to issue or receive compliant e-invoices.
Yes, several specific situations are exempt:
The German e-invoicing mandate is phased in over four stages:
The January 1, 2025 deadline applies to the ability to receive e-invoices, not the obligation to issue them. From this date, all businesses must have systems capable of accepting and processing structured e-invoices.
However, the obligation to issue e-invoices is phased in later (2027 for large companies, 2028 for all). During the transition period (2025-2026), paper invoices and PDF invoices may continue to be issued, but only if the invoice recipient has given their consent.
During this transition period:
As of the latest BMF guidance (October 2025), no further postponements have been announced for the stated deadlines. However, the German government has indicated it may provide additional clarifications and guidance as implementation progresses.
The integration of ZRE and OZG-RE platforms (scheduled for 4 2025) may require technical adjustments, but the core mandate deadlines remain unchanged. Businesses should monitor BMF communications for any updates.
Before the Growth Opportunities Act (March 2024), Germany's original plan was to implement B2B e-invoicing mandates more gradually, with pilots and sector-specific phases.
The accelerated timeline in the current law reflects the government's commitment to faster digital transformation and alignment with EU-wide ViDA requirements that will require near-real-time reporting starting in 2030.
These are three different formats for structuring e-invoice data, each with distinct characteristics:
XRechnung:
ZUGFeRD:
Peppol BIS Billing 3.0:
All three formats comply with the EN 16931 European standard and are acceptable in Germany.
The choice depends on your business context:
You may use multiple formats depending on your business needs. There is no requirement to use a single format for all invoices. In practice:
Standard PDF invoices alone will not meet the e-invoicing mandate requirements from January 1, 2025, onwards. While PDF invoices can still be used during the transition (with recipient consent until 2026), they do not qualify as structured e-invoices because:
You must transition to software that generates one of the compliant formats (XRechnung, ZUGFeRD, or Peppol BIS). This may involve upgrading your invoicing system or adopting new software.
Yes, significant differences exist between versions:
For compliance purposes, you must use ZUGFeRD 2.0 or later. Older versions are not compliant and will not satisfy legal requirements. When upgrading software, verify that your new system supports at least ZUGFeRD 2.0.
All B2B e-invoices in Germany must comply with EN 16931 and must include these mandatory data elements:
Seller/Invoice Issuer Information:
Buyer/Invoice Recipient Information:
Invoice Details:
Payment Information:
Delivery Information:
VAT Treatment:
All these elements enable automatic validation and processing by accounting systems.
Yes, significant differences apply:
Domestic B2B (Germany-to-Germany):
Intra-EU B2B (Germany-to-other EU):
International B2B (Germany-to-non-EU):
Starting January 1, 2025, this situation is significantly limited because:
However, practical considerations apply:
Best practice: Communicate with customers in advance, confirm their e-invoice processing capability, and allow a reasonable transition period if they are still upgrading systems.
Limited exemptions in Germany e-invocing apply as follows:
Micro-businesses (under €22,000 annual turnover):
Invoices under €250:
Reverse charge / VAT-exempt transactions:
Self-employed persons and freelancers (under VAT registration threshold):
German law permits simplified invoices (containing less data than standard invoices) for any single invoice not exceeding €250 (gross, including VAT). These simplified invoices may be issued in paper or PDF format without full e-invoicing compliance.
However:
Practical implication: Many businesses would choose to issue all invoices (including small amounts) as e-invoices for consistency and to avoid manually tracking which invoices fall below the threshold. This is a valid and simpler approach.
B2G invoicing is the most mature and strictly regulated segment of the German e-invoicing ecosystem.
Germany B2G e-invoicing has stricter rules than B2B. Federal authorities require XRechnung and automatic validation on submission. You must include the Leitweg-ID in the Buyer Reference (BT-10) so the invoice routes correctly.
Submission is typically via ZRE / OZG-RE portals or Peppol. You receive portal delivery confirmation, and while authorities retain copies, suppliers should also archive invoices for audit and recordkeeping.
Requirement | What you must do |
|---|---|
Format | Use XRechnung |
Routing | Add Leitweg-ID in BT-10 |
Submission | Portal upload (ZRE/OZG-RE) or Peppol |
Checks | Pass automated validation |
Proof | Keep receipt confirmation + archive |
A Leitweg-ID is a unique routing ID used by German public authorities to ensure your e-invoice reaches the correct agency/department. It typically includes a prefix (often 991/992/993), institution/cost-center digits, and a check digit.
You don’t generate it yourself—the contracting public authority provides it in tenders, contracts, or ordering documents, or you can request it from them. Enter it in Buyer Reference (BT-10); wrong IDs can cause misrouting or rejection.
ZRE and OZG-RE are federal invoice submission portals, moving toward a single platform. ZRE has been used mainly for direct federal administration (often Leitweg-ID “991”) but is being phased out, with suppliers expected to migrate.
OZG-RE is the unified/target portal (often “992”) and supports portal upload and Peppol. If you currently use ZRE, register on OZG-RE and test submissions early to avoid disruption when ZRE is retired.
Portal | Typical use | Status / Action |
ZRE | Direct federal admin (often 991) | Being phased out → migrate |
OZG-RE | Wider federal scope (often 992) | Unified portal → use going forward |
Email may be legally possible in some cases, but it’s risky: processing may fail and you may not get reliable proof of receipt. Peppol is increasingly accepted (and sometimes expected for larger suppliers) because it routes invoices automatically using the Leitweg-ID and provides delivery confirmations.
Portal upload remains the safest option for most suppliers due to clear validation and immediate receipt confirmation. Use email only if the authority explicitly approves it.
Peppol is a Europe-wide secure network for exchanging e-documents (including e-invoices). For German B2G, you connect to a Peppol Access Point provider, send your XRechnung, and Peppol routes it automatically using the Leitweg-ID.
You then receive delivery confirmations, enabling automation and high-volume invoicing without manual portal uploads. Germany supports Peppol as a preferred delivery channel alongside portals like OZG-RE.
Step | What happens |
1 | Supplier connects to a Peppol Access Point |
2 | XRechnung is sent from invoicing system to Access Point |
3 | Peppol routes using Leitweg-ID |
4 | Delivery confirmation is returned |
5 | Enables scalable, automated B2G invoicing |
E-invoices are validated at several stages. The supplier’s system checks mandatory fields, data formats, calculations, and consistency. For B2G, portals like ZRE/OZG-RE and the Peppol network validate the XML schema, VAT data, and Leitweg-ID.
The buyer’s system then checks structure, duplicates, and business rules. Finally, tax authorities run automated audits and consistency checks against VAT returns. Using invoicing software with built-in validation helps prevent rejections and resubmissions.
The Buyer Reference (BT-10) is a text field used for invoice routing and matching. For B2G invoices, it must contain the Leitweg-ID exactly as provided by the public authority and may include cost center details.
For B2B, it usually includes a purchase order number or customer reference. XRechnung requires BT-10 for B2G invoices. Missing or incorrect references can cause invoice rejection or misrouting.
Non-compliant e-invoices are often rejected. B2G portals reject invoices with errors, requiring correction and resubmission, which delays payment. In B2B, buyers’ systems may reject or fail to process invoices.
Missing VAT data can prevent tax validation, leading to denied input tax deductions and possible penalties. Business impacts include payment delays, reissued invoices, extra administration, and strained relationships. Automated validation before sending is the best prevention.
Yes. E-invoices must use UTF-8 encoding (XRechnung, ZUGFeRD, Peppol). XRechnung uses XML files, ZUGFeRD embeds XML in PDF/A-3, and Peppol uses UBL or CII XML. Digital signatures are optional but recommended for B2G.
Transmission is encrypted via portals or Peppol. Invoices must be archived in original or PDF/A format for 10 years, with integrity-preserving metadata.
Choose software based on supported formats (XRechnung, ZUGFeRD, Peppol), invoice volume, and scalability. Ensure it integrates with your accounting or ERP systems and supports automation such as batch processing and validation.
Ease of use, staff training needs, support quality, and security certifications are key. Compare costs against time savings and compliance benefits. For most German SMEs, cloud-based SaaS solutions offer the best balance of affordability, features, and compliance.
Testing involves validating the invoice structure with official tools (XRechnung or ZUGFeRD validators), then checking business rules such as VAT calculations and mandatory fields using Schematron rules.
Many invoicing tools automate this. Optional test transmissions to trusted partners or portals help confirm real-world processing. Always verify encoding, identifiers, totals, and file size. Repeated testing before go-live reduces rejection risk and ensures smooth processing.
Costs vary by solution. SMEs typically spend €20–100 per month for SaaS tools, with one-time setup costs of €500–2,000. Additional expenses may include Peppol access, training, archiving, or signatures.
Enterprise or custom ERP integrations cost significantly more. As of 2025, Germany offers no direct e-invoicing subsidies, but general SME digitalization grants may apply. Most costs are tax-deductible as business expenses.
German law requires e-invoices to be archived for 10 years in original or PDF/A format, including metadata for integrity and traceability. Storage must be secure, tamper-proof, and quickly accessible for audits.
Cloud, on-premise, or specialist archiving solutions are allowed, with backups strongly recommended. Documents must not be altered, and audit trails should track access. Proper documentation of the archiving process is essential.
Germany applies layered penalties based on severity and frequency of non-compliance. Fines are issued per invoice and can escalate rapidly when violations repeat. Beyond direct fines, VAT penalties and loss of input tax deduction materially increase financial risk, with additional exposure under future ViDA rules.
Area | Key Penalties |
|---|---|
General non-compliance | €200–€5,000 per invoice; cumulative fines possible |
VAT penalties | Up to 10% of VAT due (cap €1m/year); €25,000 per return |
Intentional breaches | 5–50% surcharge |
Input VAT | Deduction denied on non-compliant invoices |
B2G delays | Administrative fees, delayed payments |
ViDA (future) | €100–€5,000 per transaction |
German tax authorities rely heavily on automation and data reconciliation. E-invoice data submitted through government portals is cross-checked against VAT returns, with algorithmic risk profiling to detect inconsistencies. Audits now routinely include e-invoicing controls, and enforcement will tighten further under ViDA.
Monitoring and enforcement tools include:
From 2030, near-real-time reporting will allow faster detection and penalty issuance.
Buyer liability is limited but not eliminated. While suppliers carry primary responsibility, buyers cannot benefit from non-compliant invoices and must take corrective action.
Key implications for buyers:
Best practice: use automated validation, document rejections, and only process corrected invoices.
Example: A B2G invoice missing a Leitweg-ID must be rejected; once corrected, no penalty applies to the buyer.
The supplier is responsible for correct transmission and must retain proof such as Peppol delivery receipts, portal confirmations, or email server logs (read receipts where possible). Once received, the customer must process the invoice and fix any system-side rejection issues.
If non-receipt is claimed, the supplier should provide transmission evidence, verify recipient details, and resend if needed. Invoices remain VAT-valid if properly issued, and suppliers must retain proof for 10 years to avoid disputes.
Yes, enforcement is phased. From 1 Jan 2025 to 31 Dec 2026, paper invoices are allowed with recipient consent, except for mandatory B2G e-invoicing. In 2027, large companies (>€800k turnover) must issue e-invoices, while smaller firms get limited flexibility.
From 1 Jan 2028, e-invoicing is mandatory for all, with no grace period. Authorities provide guidance and tools, and no further postponements are planned.
Yes, compliance applies even to small businesses, but obligations vary by turnover. Micro-businesses under €22,000 don’t need to issue e-invoices but must be able to receive them from 2025.
Businesses earning €22,000–€800,000 must receive e-invoices from 2025 and start issuing them by 2028. Invoices under €250 can use simplified formats. Affordable cloud tools (€20–50/month) are usually sufficient, with minimal setup required.
Micro-businesses below €22,000 turnover are exempt from issuing e-invoices indefinitely and may continue paper invoicing. However, receiving e-invoices becomes mandatory from January 1, 2025, and refusal is not allowed.
Practical steps include choosing low-cost software (€10–20/month), testing receipt with suppliers, documenting processes for audits, and tracking revenue growth—crossing the threshold triggers future issuing obligations.
The €22,000 threshold applies to annual gross turnover per calendar year, calculated before expenses and excluding VAT deductions. It includes all business income.
If exceeded for one year, exemption still applies; exceeding it for two consecutive years moves the business into the regular regime. Issuing e-invoices then becomes mandatory by January 1, 2028. No special filing is required—clear revenue records in tax returns are sufficient.
Preparation should start as soon as possible with turnover assessment, software selection, and testing invoice receipt. Gradual issuance before deadlines reduces disruption.
Businesses should document processes, set up 10-year archiving, and stay updated on BMF guidance. By 2028, systems and staff should be fully ready. Typical investment is €300–800 and 10–20 staff hours, with quick ROI through time and efficiency savings.
Germany's mandatory e-invoicing implementation represents a significant digitalization milestone for European commerce. The phased timeline (beginning January 2025 with mandatory receipt capability, escalating to universal issuance by January 2028) provides businesses with adequate transition time while maintaining regulatory clarity and compliance expectations.
Key success factors for compliance:
For the latest updates, consult official sources:
E-Rechnung Bund: https://e-rechnung-bund.de/ – Federal portal information and updates