Germany E-Invoicing Framework

Updated On : -- | -- min read

Germany's E-Invoicing Framework Explained: Legal Obligations, Accepted Formats, and What Businesses Must Do Before 2028

Germany's transition to mandatory electronic invoicing represents one of the most consequential structural shifts in the country's tax administration in recent years. The e invoicing framework, introduced through the Growth Opportunities Act enacted in March 2024 and implemented through amendments to Section 14 of the German VAT Act, establishes a phased, legally binding obligation for businesses to exchange invoices in structured, machine-readable formats for domestic business-to-business transactions. The German tax authority released its official e invoicing guidelines on 25 October 2025, providing detailed operational parameters for implementation. For finance, tax, and technology functions operating in Germany, understanding the full scope of the einvoicing mandate, its timeline, its format requirements, its exemptions, and its archiving obligations is no longer optional preparation. It is an active compliance requirement with defined deadlines and measurable consequences for non-compliance.

What E-Invoicing Means in the German Context

Electronic invoicing, or einvoicing, in Germany is not the digital transmission of a PDF file by email. That model, which has been common practice for years, does not satisfy the mandate's requirements because a standard PDF is not a structured, machine-readable document. It is a visual representation of invoice data that requires human reading and manual re-entry into accounting systems. The e invoicing regulations enacted through the Growth Opportunities Act require something fundamentally different: an invoice whose data is encoded in a structured format that software systems can read, validate, and process automatically without human intervention at the data entry stage.

For domestic B2B transactions, this means invoices must conform to the EN 16931 European standard, either through formats that directly implement the standard or through formats that can be demonstrably mapped to its core data model. The mandate applies where both the supplier and the recipient are established in Germany and the transaction falls within the scope of German VAT law. It does not apply to cross-border transactions, business-to-consumer sales, or transactions involving businesses without a German fixed establishment.

Germany's einvoicing framework is architecturally different from the clearance models adopted by France and Poland. In those jurisdictions, all invoices must pass through a central government portal before reaching the recipient, giving the tax authority real-time visibility into every transaction. Germany has adopted a decentralised, post-audit model in which invoices are exchanged directly between businesses through channels of their choosing, including email, EDI networks, the Peppol network, or direct ERP-to-ERP integration. The tax authority does not receive invoices in real time but retains the right to request them for audit purposes. This approach prioritises operational flexibility and interoperability while establishing the structured data foundation that future EU-wide real-time reporting under the VAT in the Digital Age initiative may build upon.

The Einvoicing Timeline in Germany: Phase by Phase

The einvoicing timeline in Germany is structured across three defined phases that progressively extend the mandatory issuance obligation to the full business population while maintaining a universal reception requirement from the first phase.

From 1 January 2025, all VAT-registered businesses conducting domestic B2B transactions in Germany must be capable of receiving structured electronic invoices in compliant formats. This reception obligation carries no size threshold, no turnover exception, and no transitional relief. It applies to every business within scope regardless of whether the business itself is yet required to issue structured invoices. Simultaneously, voluntary issuance of compliant e invoices became permissible without requiring buyer consent, and paper and PDF invoices remained permissible for issuance during this initial phase.

From 1 January 2027, mandatory issuance becomes obligatory for businesses with annual turnover exceeding EUR 800,000. From this date, paper and standard PDF invoices are prohibited for these larger businesses in domestic B2B transactions. Businesses below the turnover threshold retain the ability to issue paper or PDF invoices with trading partner agreement through this period.

From 1 January 2028, the mandatory issuance obligation extends to all remaining businesses regardless of turnover. At this point, the einvoicing mandate reaches full implementation across the entire domestic B2B business population, and paper and PDF invoices become prohibited for all in-scope transactions. EDI arrangements that do not natively conform to EN 16931 must by this point be capable of producing or extracting EN 16931-compliant structured data to remain within the compliant framework.

For business-to-government invoicing, structured electronic invoicing has been mandatory since 2020, predating the B2B mandate. Suppliers to federal and state public administrations must submit invoices through official government portals, specifically the E-Rechnungsportal Bund for federal invoices and state-specific platforms including the OZG-RE for state-level submissions. Both portals are Peppol-enabled and accept XRechnung and compatible ZUGFeRD files.

Who Must Comply and Who Is Exempt

The einvoicing requirements apply to a defined scope of transactions and entities, and understanding both the inclusion criteria and the exemptions is essential for accurate compliance assessment.

All domestic B2B transactions where both the supplier and the recipient are established in Germany and the supply is taxable under German VAT law fall within the mandatory scope. Foreign businesses with a fixed establishment in Germany, such as a physical office or warehouse, are equally subject to the mandate for transactions conducted through that establishment. Business-to-government suppliers have been within scope since 2020.

Several categories are explicitly excluded from the einvoicing mandate. Small-amount invoices with a gross total of EUR 250 or less are exempt from the structured format requirement and may continue to be issued in simplified form. Passenger transport tickets are exempt from structured invoice requirements regardless of their value. Transactions that are VAT-exempt under specific provisions of the German VAT Act, such as those involving healthcare services, education, or financial services, fall outside the scope. Cross-border transactions, whether intra-EU B2B or export and import flows, are excluded from the domestic German mandate. Business-to-consumer sales remain outside scope entirely, allowing paper receipts and PDFs to continue for consumer transactions indefinitely.

Small businesses operating under the small business scheme established by Section 19 UStG, with annual turnover up to EUR 22,000, are exempt from the obligation to issue structured e invoices. However, they retain the obligation to receive them. A small business within this threshold may continue issuing paper or PDF invoices with an appropriate small business VAT note, but its own suppliers who are within the mandatory issuance phases must provide structured invoices that the small business must be capable of accepting.

Accepted E Invoice Formats for German Compliance

Germany's einvoicing regulations recognise several structured formats as compliant, each with distinct technical characteristics and practical use cases.

XRechnung

XRechnung is Germany's national Core Invoice Usage Specification, built directly on the EN 16931 data model. It is a purely XML-based format with no embedded visual component. Every data field in an XRechnung invoice corresponds to a defined element in the EN 16931 semantic model, and the format includes German-specific mandatory fields, most notably the Leitweg-ID routing code that directs invoices to the correct public authority in B2G transactions. XRechnung has been mandatory for business-to-government invoicing since 2020 and is widely accepted for B2B transactions. Its purely structured nature means it is optimised for automated system-to-system processing but requires that receiving systems are configured to handle XML files directly, as there is no human-readable visual layer within the standard file.

ZUGFeRD

ZUGFeRD is a hybrid format that embeds structured CII XML data within a PDF/A-3 file, producing a document that is simultaneously human-readable and machine-processable. For compliance with Germany's B2B mandate, only the EN 16931-aligned profiles, specifically version 2.0.1 and above at the COMFORT or EXTENDED profile level, should be treated as mandate-ready. The XML component embedded within the file is the legally relevant record. The PDF layer is a visual rendering only, and where the two layers carry conflicting information, the XML governs. Version 2.3, released in May 2025, is the current standard version of ZUGFeRD and represents the most up-to-date implementation of the format.

Peppol BIS Billing 3.0

Peppol BIS Billing 3.0 applies the Universal Business Language 2.1 syntax to the EN 16931 data model and is transmitted through the Peppol four-corner network. It is a strong option for businesses that require interoperability across a large number of trading partners, particularly those with cross-border European invoicing relationships, as the Peppol network operates across multiple EU member states using consistent protocols. Peppol BIS 3.0 is compliant with EN 16931 provided the content mapping to the standard's mandatory data fields is correctly implemented.

Legacy EDI Arrangements

Existing EDI setups may continue during the transitional period between 2025 and 2027 where they are already established and agreed between both parties. From 2028, any EDI arrangement that remains in use must be capable of producing or extracting EN 16931-compliant structured data. EDI formats that cannot be mapped to the EN 16931 core data model will not satisfy the mandate's requirements beyond the transitional period.

General XML

It is important to note that XML as a file format is not itself a compliance indicator. What determines compliance is whether the XML file follows an accepted EN 16931 implementation such as XRechnung XML, ZUGFeRD embedded XML, or EN 16931-mapped UBL. An XML file that does not conform to one of these implementations does not satisfy the einvoicing requirements regardless of its general technical quality.

Mandatory Data Fields in a Compliant E Invoice

Every structured e invoice issued under Germany's mandate must contain a defined set of mandatory data fields drawn from the EN 16931 standard. These fields fall into six principal categories that together provide the complete invoice information required for VAT compliance and automated processing.

Invoice identification requires a unique invoice number and the invoice issue date. Seller details must include the supplier's full name, address, and VAT identification number. Buyer details must carry equivalent identification information for the recipient. Line item detail requires a description of each good or service supplied, along with quantity, unit price, and the applicable tax rate for each line. VAT information must clearly state the applicable tax rate and the total VAT amount for the invoice. Totals and payables must present the net total, the tax amount, the gross total, and the payment terms and destination including IBAN and BIC where applicable.

Where any of these mandatory fields are absent or incorrectly populated, the invoice fails EN 16931 validation and does not constitute a compliant e invoice under the mandate. Format compliance and data content compliance are equally necessary conditions, and both must be met consistently across every invoice issued.

How E Invoice Transmission Works in Germany

Germany's decentralised transmission model gives businesses flexibility in how they deliver compliant structured invoices to their trading partners, provided the invoice itself remains in a structured format throughout the exchange.

Email transmission of structured XML or hybrid file attachments is the most accessible channel and satisfies the basic transmission requirement for B2B purposes. A dedicated invoice receipt email address is a practical minimum configuration for businesses managing incoming e invoice flows. EDI networks remain available under the transitional rules described above. The Peppol network provides the most robust transmission infrastructure for businesses with high invoice volumes or cross-border European relationships, offering delivery confirmation, identity authentication, and format validation through its certified access point model. Direct ERP-to-ERP integrations and supplier or customer portal channels are equally valid where the structured file can be downloaded and processed by the recipient.

For B2G invoicing, the transmission model is more prescriptive. The E-Rechnungsportal Bund is the mandatory submission channel for invoices to federal authorities, and state-level submissions are directed through the OZG-RE portal or equivalent state platforms. These portals are Peppol-enabled and accept XRechnung and compatible ZUGFeRD files. Businesses invoicing public sector entities must be connected to or capable of submitting through these official channels.

Archiving and GoBD Compliance

Germany's GoBD regulations establish specific requirements for how e invoices must be archived that go beyond simply saving a copy of the file. Three principles govern compliant archiving.

The original file must be preserved without modification. An XRechnung invoice must be archived as the XML file received. A ZUGFeRD invoice must be archived as the complete PDF/A-3 hybrid file with its embedded XML intact, not merely as the PDF visual layer with the XML discarded. Converting an invoice to a different format for archiving purposes, even if the conversion is technically accurate, does not satisfy the GoBD requirement to retain the original received format.

The archived invoice must remain machine-readable throughout the retention period. The archiving environment must be capable of retrieving and presenting the structured data in a readable form at any point during the mandatory retention window, which is generally ten years from the end of the calendar year in which the invoice was created, though specific circumstances may affect the applicable period.

The integrity and authenticity of the archived invoice must be demonstrable. Any corrections to archived invoices must be traceable and logged rather than applied silently. The audit readiness requirement means invoices must remain searchable and exportable in the event of a tax authority audit during the retention period.

Preparing for Full E Invoicing Compliance: A Structured Approach

The path to full compliance with Germany's einvoicing mandate requires action across technology, process, and governance dimensions that cannot be addressed through a single system update.

Mapping current invoice flows is the diagnostic starting point. Documenting how invoices are currently created, approved, transmitted, received, and archived identifies the gaps between present practice and mandate requirements. Businesses that have not yet done this mapping are likely operating with incomplete visibility into the compliance work ahead of them.

ERP and accounting system capability must be assessed against the structured format requirements. Systems that cannot natively generate XRechnung or ZUGFeRD output at the required EN 16931 profile level require either software upgrades, integration modules, or a third-party e invoicing provider to produce compliant output. Equivalent assessment is required for inbound invoice processing, confirming that the system can receive, validate, and automatically import structured invoice data without manual re-entry.

Selecting a compliant e invoicing provider or confirming the adequacy of existing infrastructure should be completed well in advance of the applicable mandatory issuance deadline. For businesses approaching the EUR 800,000 turnover threshold, this means treating 2026 as the preparation year for the 2027 obligation rather than waiting for the deadline to approach.

Testing the full invoice exchange workflow, covering both outbound issuance and inbound receipt across all relevant trading partners and formats, before the mandatory deadline is a prerequisite for operational confidence rather than an optional validation exercise. Format errors, data mapping gaps, or routing failures discovered during testing are resolved without compliance impact. The same issues encountered after the mandatory deadline creates compliance exposure that is more costly to address.

For organisations managing Germany's einvoicing mandate alongside equivalent obligations in France, Belgium, and other European jurisdictions, the technical and regulatory complexity of maintaining compliant invoice infrastructure across multiple frameworks simultaneously is a substantial operational challenge. Platforms such as Accqrate provide the integrated infrastructure, regulatory intelligence, and multi-jurisdictional expertise needed to navigate Germany's e invoicing regulations and the broader European einvoicing landscape with operational confidence and consistent compliance accuracy.