Receiving E-Invoices in Germany

Updated On : -- | -- min read

Receiving E-Invoices in Germany: Compliance Obligations, Accepted Formats, Transmission Channels, and Archiving Requirements in 2026

Germany's e-invoicing mandate is no longer a forthcoming obligation. It is an active legal requirement that has been in force since 1 January 2025 and is progressing through its phased implementation with defined milestones approaching in 2027 and 2028. As of 2026, every VAT-registered business conducting domestic B2B transactions in Germany is legally obligated to be capable of receiving structured, machine-readable electronic invoices. That obligation carries no exceptions based on company size, annual turnover, or sector. It applies uniformly across the business population, and non-compliance is not a technicality. It is a compliance failure with direct consequences for VAT deductibility and audit exposure.

Understanding what receiving an e-invoice actually requires in legal and operational terms, which formats are accepted, which transmission channels are available, how validation must be conducted, and how invoices must be archived under Germany's GoBD rules is the foundation on which a compliant 2026 reception infrastructure must be built.

The Legal Framework Governing E-Invoice Reception in Germany

Germany's e-invoicing mandate draws its authority from several intersecting legislative instruments. The primary domestic legal basis is Section 14 of the Umsatzsteuergesetz, which defines what constitutes a valid electronic invoice for German VAT purposes. The Growth Opportunities Act, passed by the Bundestag and Bundesrat in early 2024, established the phased mandatory B2B e-invoicing timeline and confirmed the EN 16931 European standard as the compliance benchmark for invoice format. The Federal Ministry of Finance's administrative guidance, issued in draft form in June 2024 and anticipated in final form thereafter, provides operational detail on format requirements, transmission methods, and the treatment of edge cases including hybrid formats and transitional EDI arrangements.

The GoBD regulations, which govern the principles for the proper keeping and storage of books and records in electronic form, establish the archiving obligations that apply to received e-invoices. These regulations operate independently of the e-invoicing mandate itself but are directly relevant to how received invoices must be stored and maintained to remain audit-ready throughout the mandatory retention period.

Together, these instruments create a layered compliance framework in which format compliance, transmission compliance, validation practice, and archiving discipline are each independently required and each independently auditable.

The 2026 Compliance Position: Where Businesses Stand Now

The phased timeline of Germany's <a href='[Link to Blog 6]'>e-invoicing mandate</a> places 2026 in a critical transitional position. The reception obligation, which requires all VAT-registered businesses to be capable of accepting EN 16931-compliant structured invoices, has been in force since 1 January 2025. Any business that has not yet built this capability is operating outside the mandate's requirements in the current period.

On the issuance side, 2026 remains a transitional year. Businesses that have not yet reached the EUR 800,000 annual turnover threshold that triggers mandatory issuance from 1 January 2027 may still issue paper and PDF invoices to trading partners who consent to receive them. However, this transitional permission for issuance does not affect the reception obligation, which is absolute and unconditional for all B2B transactions. A business may still issue paper invoices to its customers in 2026 while simultaneously being legally required to accept structured electronic invoices from its suppliers.

The 1 January 2027 deadline, at which point all businesses with turnover exceeding EUR 800,000 must issue exclusively in compliant structured formats, is now within the normal business planning horizon. Businesses approaching that threshold should treat 2026 as the preparation year for full issuance compliance rather than a continuation of the status quo. The 1 January 2028 deadline, which extends mandatory structured issuance to all remaining businesses regardless of size, means that even smaller enterprises have a defined and finite window before paper and PDF issuance becomes prohibited entirely.

What Receiving an E-Invoice Actually Means in Legal Terms

The concept of receiving an e-invoice carries a specific legal meaning under Germany's mandate that extends well beyond simply having an email address capable of accepting file attachments. For a business to satisfy the reception obligation, it must be able to accept a structured data file in a compliant format without modifying or degrading that file, perform technical validation to confirm that the received file meets EN 16931 requirements and applicable national standards, and import the validated invoice into internal financial processing workflows in a manner that allows the structured data to be used for automated processing rather than requiring manual re-entry.

This three-part requirement has a direct implication for what constitutes adequate reception infrastructure. A business whose only capability is to receive a PDF attachment by email and manually enter its contents into an accounting system is not meeting the mandate's requirements if that PDF does not contain embedded structured XML data. A plain PDF invoice, however detailed and accurately prepared, does not qualify as a compliant electronic invoice under Germany's current rules. Reception capability means the ability to handle the structured data layer, not merely the visual document.

Who Bears the Reception Obligation

The reception obligation applies to all VAT-registered businesses conducting domestic B2B transactions in Germany. This scope is deliberately comprehensive and includes businesses of every size, businesses operating under the small business scheme established by Section 19 UStG, and foreign businesses with a German fixed establishment generating revenue from domestic B2B transactions.

The small business exemption under Section 19 UStG is worth addressing explicitly because it is a common source of confusion. This exemption relieves qualifying small businesses from the obligation to issue structured e-invoices. It does not relieve them from the obligation to receive them. A small business that receives an invoice from a supplier who has issued it in XRechnung or ZUGFeRD format must be capable of accepting and processing that invoice in its structured form.

Several categories of transaction fall outside the mandate's scope. Business-to-consumer invoicing is not covered by the B2B mandate. Cross-border intra-community supplies are currently excluded from the domestic German requirement, though the EU's ViDA reforms are expected to address cross-border electronic reporting requirements through a separate framework. Non-resident businesses without a German fixed establishment are not subject to the domestic B2B rules.

Accepted Formats for E-Invoice Reception in 2026

Germany's e-invoicing mandate accepts invoices that comply with 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. In practice, three primary formats dominate the German market in 2026.

XRechnung

XRechnung is Germany's national Core Invoice Usage Specification built on the EN 16931 data model. It is a purely XML-based format with no embedded visual document component. Every data element in an XRechnung invoice corresponds to a defined field in the EN 16931 semantic model, and the format includes German-specific mandatory fields, most notably the Leitweg-ID routing code used for business-to-government invoicing. XRechnung has been mandatory for B2G transactions since November 2020 and serves as the reference format for Germany's B2B mandate. Its purely structured nature makes it optimal for automated processing but requires that receiving systems are configured to handle XML files directly, since no human-readable layer is embedded.

ZUGFeRD 2.3

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. Version 2.3, released in May 2025, is the current standard version and is fully compliant with EN 16931. ZUGFeRD's hybrid architecture makes it particularly practical during the transitional period because recipients can open and read the visual PDF while automated systems extract and process the embedded XML. The Federal Ministry of Finance's guidance confirms that in any hybrid invoice, the structured data layer takes precedence over the visual document where the two differ, placing the compliance burden on the accuracy of the XML component rather than the PDF presentation.

PEPPOL BIS 3.0

PEPPOL BIS 3.0 applies the UBL 2.1 syntax to the EN 16931 data model and is transmitted through the <a href='[Link to Blog 10]'>PEPPOL four-corner network</a> rather than by direct email or portal submission. It is fully EN 16931-compliant and is increasingly used for B2B invoicing by businesses that have invested in PEPPOL connectivity for B2G purposes and wish to extend that infrastructure to their private sector trading relationships. For cross-border EU invoicing, PEPPOL BIS 3.0 provides the most straightforward path to format consistency across multiple jurisdictions.

Other EN 16931-Compliant Structured Formats

Additional structured formats are permissible in B2B contexts where both parties agree, provided the format can be fully mapped to the EN 16931 data model. These include UN/CEFACT CII used independently outside the ZUGFeRD hybrid context, and certain EDI formats such as EDIFACT INVOIC where the exchanged data is mapped to all EN 16931 mandatory elements. EDI arrangements that meet these conditions are permitted under transitional provisions through 31 December 2027, after which full EN 16931 compliance without transitional relief becomes mandatory for all formats.

Transmission Channels Available for Receiving E-Invoices

The mandate does not prescribe a single transmission channel for e-invoice delivery. Several channels are recognised as legally compliant, each with different characteristics relevant to different business scales and operational contexts.

Email transmission remains the minimum viable reception channel under the mandate. A business that maintains a dedicated email address capable of receiving XML attachments or ZUGFeRD PDF files satisfies the basic legal reception requirement for B2B purposes. This channel is accessible to businesses of all sizes without significant technical investment and is appropriate for lower transaction volumes. However, it provides no automated validation, no delivery confirmation, and limited scalability for high-volume invoicing environments. A dedicated invoice receipt address, separate from general business correspondence, is a practical baseline configuration.

The PEPPOL network provides the most robust transmission channel for businesses handling significant invoice volumes or operating across multiple EU jurisdictions. Receipt through PEPPOL requires the business to obtain a PEPPOL ID and connect to a certified access point, through which incoming invoices are delivered to the business's ERP or processing system. The four-corner model provides delivery confirmation, identity authentication, and format validation before the invoice reaches the recipient's system, reducing the exception handling burden on the accounts payable function. For B2G transactions, the Peppol Receiver ID in Germany uses the scheme code 0204 combined with the Leitweg-ID to route invoices to the correct public authority.

Web portal submission is used primarily in B2G contexts through the ZRE federal portal and the OZG-RE state-level portal, but some larger private sector buyers also operate supplier portals for invoice receipt. This channel is practical for low-volume suppliers but is not scalable for high-frequency invoicing relationships.

ERP-to-ERP interfaces, SFTP file transfers, and REST API integrations represent the most automated transmission channel available for enterprise-scale invoice receipt. These channels enable straight-through processing from invoice generation at the supplier to posting in the buyer's ERP with minimal human intervention, delivering the full operational efficiency benefit of structured e-invoicing. They require IT investment in integration development and maintenance but are the appropriate solution for businesses processing hundreds or thousands of invoices per period.

Physical media including USB drives and optical discs are explicitly prohibited as transmission channels under the ministerial guidance, regardless of whether the files they carry would otherwise be format-compliant.

Validation Requirements Before Posting

Receipt of a structured invoice file does not in itself satisfy the business's compliance obligation. Before a received e-invoice is posted to the financial records, it must be validated for both technical and substantive compliance. This validation requirement flows from the broader GoBD obligation to maintain internal controls that assure the authenticity of origin, the integrity of content, and the legibility of every invoice in the accounting record.

Technical validation confirms that the received XML file conforms to the applicable schema, that all mandatory EN 16931 fields are present and correctly formatted, and that the file structure is error-free. For XRechnung invoices, this validation can be performed against the official XRechnung validator published by the KoSIT, the coordination office for IT standards in German public administration. For ZUGFeRD invoices, validators capable of assessing both the PDF/A-3 layer and the embedded XML are required.

Substantive validation goes beyond schema conformance to confirm that the invoice's financial data is internally consistent. Tax amounts must be mathematically consistent with the stated taxable amounts and applicable rates. Totals must equal the sum of their constituent line items. VAT identification numbers must be present and correctly formatted where required. These checks mirror the validation rules embedded in EN 16931 itself and can be automated within e-invoicing processing software.

Where validation identifies errors, the invoice cannot be posted. A corrected invoice must be requested from the issuer. The original non-compliant file should be retained in the records with documentation of the error identified and the correction requested, providing an audit trail that demonstrates the business applied appropriate controls rather than processing non-compliant invoices.

Archiving Under GoBD: The Ten-Year Retention Requirement

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

The invoice must be stored in its original received format without modification. A ZUGFeRD invoice received as a PDF/A-3 file with embedded XML must be archived in that exact form. Converting the file to a different format, extracting only the XML component, or storing only the PDF presentation layer while discarding the XML data does not satisfy the archiving obligation. The original file, as received, is what must be retained.

The archived invoice must remain machine-readable throughout the retention period. This means the archiving environment must be capable of retrieving and presenting the structured data in a readable form at any point during the ten-year period, not merely storing the bytes of the original file. This requirement has implications for the technology choices made for archiving infrastructure, particularly as software and format standards evolve over a decade.

The retention period is a minimum of ten years from the end of the calendar year in which the invoice was created. An invoice received in 2026 must therefore be retained until at least the end of 2036. Archiving systems must be configured to prevent deletion or modification before the retention period expires and must maintain access controls that prevent unauthorised alteration while ensuring authorised access for audit purposes.

Validation logs and processing records, where available, should be retained alongside the invoices themselves as evidence of the internal controls applied. In the event of a tax audit, the ability to demonstrate not only that invoices were received and archived but that they were validated before posting provides a materially stronger compliance position than archived invoices alone.

Building a Compliant E-Invoice Reception Infrastructure for 2026 and Beyond

The technical requirements for compliant e-invoice reception in Germany in 2026 are well-defined, and the path from current practice to full compliance is navigable with deliberate planning. The businesses most exposed to compliance risk are those that have not yet moved beyond email receipt of PDF invoices and have made no investment in validation or structured archiving infrastructure.

A practical approach to building compliant reception capability in the current period begins with establishing a dedicated channel for structured invoice receipt, whether through a dedicated email address, <a href='[Link to Blog 10]'>PEPPOL connectivity</a>, or both, and communicating that channel to the supplier base. It continues with configuring processing software to extract, validate, and import structured invoice data from received XRechnung and ZUGFeRD files without manual data re-entry. It extends to implementing validation logic that checks EN 16931 compliance and mathematical consistency before invoices are posted. And it concludes with establishing an archiving environment that stores original files unmodified, maintains machine-readability, enforces the ten-year retention period, and produces retrievable records for audit purposes.

Each of these steps can be delivered through a combination of ERP configuration, dedicated e-invoicing software, and access point services. The right combination depends on transaction volumes, existing system capabilities, and the scope of the business's cross-border invoicing relationships. For organisations managing e-invoice reception and compliance obligations across Germany and other European jurisdictions, platforms such as Accqrate provide the integrated infrastructure and regulatory expertise needed to meet these requirements accurately and efficiently as Germany's mandate continues through its phased implementation toward full deployment in 2028.