E‑Invoicing & E‑Reporting Explained: X‑Rechnung Invoices in Germany

Germany’s official electronic invoicing standard, detailing its definition, legal framework, technical specifications, implications for businesses, and its place within the broader European e-invoicing landscape. X-Rechnung is not merely a technical specification; it is “a key enabler of compliance with VAT requirements and the ongoing digital transformation of invoicing.”

1. What is X-Rechnung? Definition and Core Characteristics

X-Rechnung (literally “X-Invoice”) is “the official electronic invoicing format for public sector transactions in Germany.” It is a structured, XML-based invoice format that strictly adheres to the European e-invoicing standard EN 16931. Designated as Germany’s national CIUS (Core Invoice Usage Specification), its primary purpose is to enable automated processing and ensure compliance across systems.

Key characteristics include:

• XML-Only Model: Unlike hybrid formats like ZUGFeRD, X-Rechnung is “an XML-only model with no PDF component,” designed purely for machine-readability and data integration. Recipients requiring a human-readable format must use an invoice viewer or converter.
• EN 16931 Compliance: It contains all legally required invoice data in a standardized structure that is interoperable across EU countries and supports seamless processing by ERP and accounting systems.
• Purpose: To facilitate efficient, accurate electronic invoicing by replacing unstructured formats (PDFs or paper) with a machine-readable standard, thereby reducing manual data entry, minimizing errors, speeding up payment cycles, and improving VAT compliance.

2. Legal and Regulatory Framework

X-Rechnung’s foundation lies in both European Union directives and German national laws, signifying a significant shift towards mandatory digital invoicing.

• EU Directive 2014/55/EU: This directive mandated all EU public entities to accept electronic invoices conforming to a common European standard (EN 16931). X-Rechnung was developed as Germany’s response, translating these EU requirements into a national format.
• German E-Invoicing Legislation (E-Rechnungsgesetz and E-Rechnungsverordnung – ERechV): Germany implemented the EU directive, specifying X-Rechnung as the default data exchange standard.
  • Mandatory B2G (Business-to-Government) Invoicing: Since November 27, 2020, “all invoices sent to the direct federal administration (and to many state-level authorities) must be in X‑Rechnung format (or another EN 16931-compliant XML format).” Unstructured formats like PDF or paper are effectively disqualified.
• Mandatory B2B (Business-to-Business) E-Invoicing Rollout (2025–2028): Germany’s “Growth Opportunities Act 2024” introduces a phased mandate for domestic B2B e-invoicing:
  • January 1, 2025: All taxable businesses must be able to receive EN 16931-compliant e-invoices (e.g., X-Rechnung or ZUGFeRD) upon request.
  • January 1, 2027: Large companies (annual turnover > €800k) must issue B2B invoices electronically.
  • January 1, 2028: All businesses, regardless of size, must issue invoices in a structured electronic form.
  • During the transition, paper or PDF invoices may still be used only if the recipient explicitly agrees. This “post-audit” model for B2B e-invoicing is intended to align with upcoming EU-wide digital reporting systems.

3. Technical Structure of X-Rechnung

The robust technical design of X-Rechnung ensures VAT compliance and interoperability:

• EN 16931 Semantic Model: X-Rechnung fully adheres to EN 16931, defining a core set of invoice information and business rules. This ensures all mandatory data fields (e.g., supplier/buyer details, VAT IDs, invoice date, line items, tax details) are present and standardized.
• Permitted XML Syntaxes: It can be expressed using either UBL 2.1 (Universal Business Language) or UN/CEFACT Cross Industry Invoice (CII) schemas, both approved for EN 16931. KoSIT maintains and updates the specification, including XML schemas and Schematron validation rules, typically twice a year.
• Key Data Elements: X-Rechnung captures all information required for a German VAT invoice, mapped to the EN 16931 model. Important groups include:
  • Seller and Buyer details: Full legal name, address, tax identifiers, and for B2G invoices, a unique Leitweg-ID (routing code).
  • Invoice metadata: Invoice number, date, type, currency, payment terms.
  • Line item details: Description, quantity, unit price, net amount, and VAT category code/rate for each item.
  • Tax totals and VAT breakdown: Summary of taxes, including taxable base and VAT amount for each distinct rate or exemption, crucial for VAT reporting.
  • Payment information: IBAN, BIC, payment due date, discount terms (optional but commonly included).
  • Reference documents: Purchase Order numbers, contract references, delivery note IDs.
• Validation Rules and Compliance Checks: X-Rechnung includes a “built-in validation framework” using official schema definitions and Schematron business rules. These rules enforce syntactical correctness and business logic constraints. Invoices failing validation (e.g., missing mandatory fields, incorrect calculations) “may be automatically rejected by the receiving platform.” The federal OZG-RE portal, for example, performs automated checks and notifies senders of errors, making pre-validation essential.

4. X-Rechnung vs. ZUGFeRD

Germany recognizes two authorized e-invoice standards, X-Rechnung and ZUGFeRD, both EN 16931-compliant but with fundamental differences:

• Structured XML vs. Hybrid PDF/XML:X-Rechnung: A pure XML data format, optimized for full automation.
• ZUGFeRD: A hybrid model that embeds an XML file inside a human-readable PDF/A-3. This allows visual readability while still providing structured data for processing.
• Primary Use Cases:X-Rechnung: Originally mandated for B2G invoicing, and becoming dominant for B2B due to the upcoming mandate.
• ZUGFeRD: More commonly used in B2B transactions where a human-readable PDF is valued.
• Both formats are acceptable for the upcoming B2B mandate. Since they share the same EN 16931 data core, “converting between them is feasible,” allowing businesses flexibility based on recipient preferences. Public entities generally require X-Rechnung via official channels, while private customers might accept ZUGFeRD.

5. Transmission Channels and Submission of X-Rechnung

Generating a compliant X-Rechnung file requires using the correct delivery channels:

• Central Invoice Submission Portals: For federal and many state governments, suppliers use designated online portals like the OZG-RE (Online Access Act-compliant Invoice Submission Portal), which is becoming the primary platform. A unique Leitweg-ID must be included in the X-Rechnung to route it to the correct public authority.
  • Accepted Transmission Methods:Direct portal upload (web interface).
  • Secure web services (APIs).
  • Email (XML attachment to a specific portal address).
  • PEPPOL Network: The federal OZG-RE is PEPPOL-enabled, allowing X-Rechnung files to be sent via PEPPOL by addressing them to the recipient’s PEPPOL ID.
• Structured Submission Requirements: Regardless of the channel, invoices must remain in a structured electronic form. “Typically only the XML file (or a ZIP containing the XML and any supplemental attachments) is to be transmitted – there is no need to include a PDF, and including one (or other non-XML content) may cause the invoice to be rejected.” Pre-validation using official tools is highly recommended.

6. Business and VAT Implications

Adopting X-Rechnung necessitates significant changes to finance processes, IT systems, and VAT compliance:

• ERP and Accounting System Updates: Businesses must upgrade or configure their systems to “support X‑Rechnung generation and processing” (e.g., natively, via add-on modules, or third-party services). This includes ensuring systems can capture all required data fields and output valid XML.
• Process Changes and Training: Redesigning invoice workflows, establishing processes for sending and monitoring e-invoices, and training staff on new procedures (e.g., handling validation errors) are crucial. Companies may need to communicate new requirements to smaller suppliers/customers.
• Audit Trail and VAT Compliance: X-Rechnung enhances VAT compliance but also introduces responsibilities. Businesses must ensure “authenticity and integrity of e‑invoices… throughout their lifecycle.” Electronic invoices must be archived “in their original electronic form” for the legally required retention period (6 to 10 years in Germany); printing an X-Rechnung is not compliant.
• Error Handling and Rejection Risks: Automated validation means “invoices with errors are more likely to be rejected or require re-issuance.” Common pitfalls include missing mandatory information, incorrect formatting, or arithmetic discrepancies. Rejected invoices are not considered “issued” for VAT purposes, impacting cash flow and compliance. Prompt resolution of errors is essential. This demands a “culture of ‘right-first-time’ data quality.”

7. X-Rechnung in the Broader EU E-Invoicing Landscape

Germany’s move towards X-Rechnung is part of a larger EU trend towards digital VAT reporting:

• Alignment with EU Digital Strategy (ViDA): The “VAT in the Digital Age” (ViDA) reform package, adopted in March 2025, will gradually introduce pan-European requirements for e-invoicing and digital VAT reporting for cross-border B2B transactions. Germany’s “post-audit” model with X-Rechnung is “largely consistent with the direction of the EU reforms.” Companies embracing X-Rechnung now will be well-prepared for future EU-wide obligations.
• Interoperability Challenges and Solutions: While EN 16931 provides a common standard, different national implementation models (e.g., Germany’s decentralized model vs. Italy’s clearance model) exist. However, X-Rechnung’s data is “fundamentally compatible with other EN 16931-based formats” (e.g., Peppol BIS Billing 3.0, Factur-X). The European Commission and national bodies are working to standardize these processes to enhance interoperability.
• Lessons for Future Mandates: Germany’s experience highlights the importance of “stakeholder readiness and phased implementation,” promoting standardization without overly restricting transmission methods, and providing robust validation and support infrastructure. X-Rechnung’s development offers a blueprint for how a country-specific format can be rooted in a global standard, aiding interoperability across Europe.

---

Your advertisement here? Contact us on [email protected]

 

---

Article: E‑Invoicing & E‑Reporting Explained: X‑Rechnung Invoices in Germany

Introduction: X‑Rechnung – The Official XML E‑Invoice Standard for Germany
X‑Rechnung (literally “X‑Invoice” in German) is the official electronic invoicing format for public sector transactions in Germany. It is a structured, XML-based invoice format that strictly follows the European e-invoicing standard EN 16931, enabling automated processing and compliance across systems. Unlike hybrid formats such as ZUGFeRD (which include a PDF for human readability), X‑Rechnung is an XML-only model with no PDF component, designed purely for machine-readability and data integration. This makes X‑Rechnung a cornerstone of Germany’s digital invoice compliance framework, especially for Business-to-Government (B2G) invoicing where a consistent, standardized data format is critical. [invoice-portal.de], [e-rechnung-bund.de]

X‑Rechnung plays a pivotal role in Germany’s broader e‑invoicing and digital compliance strategy. It was introduced as part of Germany’s implementation of EU Directive 2014/55/EU, which requires all EU public administrations to accept standard electronic invoices. The format was developed by the Coordination Office for IT Standards (KoSIT) in 2017–2018 to meet these requirements. Since November 2020, X‑Rechnung (or an equivalent EN 16931-compliant format) has been mandatory for invoices issued to federal and state authorities in Germany, ensuring that invoices to the public sector can be automatically processed and validated. Moreover, with Germany’s recent policy changes, X‑Rechnung is set to become increasingly significant in the B2B arena as the country phases in mandatory electronic invoicing for domestic business-to-business transactions between 2025 and 2028. In short, X‑Rechnung is not just a technical specification; it is a key enabler of compliance with VAT requirements and the ongoing digital transformation of invoicing. [juston.com] [e-rechnung-bund.de] [ec.europa.eu]

Summary – Three key takeaways for businesses and financial leaders:

• Germany’s official e‑invoice format: **X‑Rechnung is the standard electronic invoice format mandated for all invoices sent to German public authorities, aligning with EU law. In the coming years (2025–2028), it will also become mandatory for domestic B2B invoicing, meaning German companies must use structured e‑invoices for business transactions. [ec.europa.eu]
• XML-only, EN 16931-compliant format: X‑Rechnung invoices are purely XML-based (no PDF file attached), containing all legally required invoice data (supplier, customer, tax details, etc.) in a standardized structure compliant with EN 16931, the European semantic data model for e-invoicing. This ensures interoperability across EU countries and enables seamless, automated processing by ERP and accounting systems. [invoice-portal.de], [e-rechnung-bund.de]
• Impact on ERP and compliance processes: Traditional PDF or paper invoices will no longer meet legal requirements for many transactions in Germany. Businesses must update their ERP/financial systems and processes to generate, transmit, receive, and archive X‑Rechnung invoices. Proper implementation of X‑Rechnung can improve VAT compliance (by including all mandated data and validation rules) and streamline invoice processing, but companies need to plan for systems integration, staff training, and robust error-handling to avoid invoice rejections and ensure audit-proof archiving. [e-rechnung-bund.de]

1. What is X‑Rechnung?

Executive Summary: X‑Rechnung is a standardized XML invoice format designated by German law for electronic invoicing, particularly in public procurement. It provides a structured data model (with no PDF) that enables automated invoice processing and ensures compliance with both German VAT requirements and European standards.

Legal Definition & Purpose: “X‑Rechnung” refers to the Core Invoice Data Exchange Standard of Germany’s public e-invoicing system – essentially, it is Germany’s national CIUS (Core Invoice Usage Specification) of the European e-invoice standard EN 16931. Legally, an X‑Rechnung is defined as an invoice issued, transmitted, and received in a structured electronic format enabling automatic processing. In practical terms, an X‑Rechnung invoice is a data file (XML) that contains all the essential invoice information in a standardized structure, allowing it to be read and processed by software without manual intervention. The purpose of X‑Rechnung is to facilitate efficient, accurate electronic invoicing in both the public and private sectors by replacing unstructured formats (PDFs or paper) with a machine-readable standard. By eliminating the reliance on paper or PDF, X‑Rechnung helps businesses and government agencies reduce manual data entry, minimize errors, speed up payment cycles, and improve VAT compliance through built-in validation of invoice data. [gesetze-im…nternet.de], [e-rechnung-bund.de]

Origins and Development: X‑Rechnung was developed in response to EU Directive 2014/55/EU, which aimed to standardize e‑invoices in public procurement across Europe. Germany transposed this directive into national law via the E‑Rechnungsgesetz and the E‑Rechnungsverordnung (E‑Invoicing Ordinance) of 2017. The Ordinance tasked the German IT Standards Coordination Office (KoSIT) with publishing a national e‑invoice format meeting the new European Norm. The first version of X‑Rechnung was released in 2017 as a collaborative effort between federal and state authorities, aligning closely with EN 16931’s core model. Since November 2020, X‑Rechnung has been compulsory for invoicing federal ministries and agencies (with only limited exceptions, such as low-value invoices under €1,000 for certain direct procurements). Many state (Länder) and local authorities in Germany have also adopted X‑Rechnung as the required format for supplier invoices, leading to widespread uptake of the standard among businesses serving the public sector. Initially, X‑Rechnung’s use was encouraged – but not mandated – in B2B transactions. However, with the passage of the Growth Opportunities Act 2024 (Wachstums­chancengesetz), Germany set out a timetable to make structured e‑invoicing the default for domestic B2B sales. This law (contingent on EU authorization) requires all German businesses to be able to receive electronic invoices from 1 January 2025, with large companies (annual turnover > €800k) obligated to issue only e-invoices from 1 January 2027, and a full mandate for all businesses by 1 January 2028. In summary, X‑Rechnung has evolved from a B2G-focused standard into an integral part of Germany’s national VAT compliance infrastructure, now underpinning mandatory e‑invoicing in both public and private sectors. [e-rechnung-bund.de] [ec.europa.eu], [juston.com]

2. Legal and Regulatory Framework

German businesses must understand the legal foundation of X‑Rechnung to ensure they comply with current requirements and prepare for upcoming mandates. The legal and regulatory framework for X‑Rechnung spans European Union directives and German national laws:

• EU Directive 2014/55/EU (Public Procurement E‑invoicing) – This EU directive laid the groundwork for X‑Rechnung. It required all EU Member States’ public entities to accept electronic invoices conforming to a common European standard. In response, the European Committee for Standardization (CEN) developed EN 16931, a standardized core data model and syntax for e‑invoices across the EU. The directive, effective since April 2019 for central government and April 2020 for sub-central authorities, ensures that a supplier in any EU country can send an invoice in a format that any public authority in another Member State must be able to process. X‑Rechnung was created as Germany’s implementation of this European standard, translating the EU requirements into a national format and guidelines. [juston.com]
• German E‑Invoicing Legislation (E‑Rechnungsgesetz and E‑Rechnungsverordnung) – Germany implemented the EU directive via national law and regulations commonly referred to as the E‑Rechnungsgesetz (E-Invoicing Act) and E‑Rechnungsverordnung (ERechV). The ERechV, adopted in October 2017, specified the use of X‑Rechnung as the default data exchange standard for electronic invoices to public bodies. The regulation mandates that an e‑invoice must be issued and received in a structured electronic format that allows automatic processing, effectively disqualifying unstructured formats like PDF or paper from being considered “electronic invoices” under German law. The requirement to use e‑invoicing for B2G (Business-to-Government) transactions was phased in over 2018–2020: since **27 November 2020, all invoices sent to the direct federal administration (and to many state-level authorities) must be in X‑Rechnung format (or another EN 16931-compliant XML format). Exceptions are limited (e.g. low-value invoices, state secrets, and certain foreign transactions), but in general, if you do business with the German government today, you are required to submit invoices as X‑Rechnung XML files. [gesetze-im…nternet.de], [e-rechnung-bund.de] [e-rechnung-bund.de]
• Mandatory B2B E‑Invoicing Rollout (2025–2028) – While B2B electronic invoicing has so far been voluntary in Germany, this is now changing. In March 2024, the German government passed the Growth Opportunities Act as a step towards modernizing tax administration. Backed by a special EU Council authorization, this law amends the VAT Code (UStG) to gradually make structured e‑invoicing the default method for domestic B2B invoices. The rollout schedule is phased by company size: starting 1 Jan 2025, all taxable businesses must be able to receive EN 16931-compliant e‑invoices (e.g. in X‑Rechnung or ZUGFeRD format) on request. Then from 1 Jan 2027, large companies (exceeding €800k annual turnover) must issue their B2B invoices electronically only, and finally by 1 Jan 2028 all businesses – regardless of size – will be required to issue invoices in a structured electronic form. During the transition, paper or PDF invoices may still be used only if the recipient explicitly agrees; otherwise, the electronic format will take precedence. Notably, B2C and purely cross-border invoices remain outside the domestic mandate (consumer invoices can still be sent in traditional formats, and foreign businesses not established in Germany are not obliged to use X‑Rechnung to invoice German buyers). The German Ministry of Finance has issued detailed guidance and FAQs to help businesses prepare, emphasizing that the new B2B e‑invoicing rules follow a “post-audit” model (no real-time clearance reporting to authorities) and are intended to dovetail with upcoming EU-wide digital reporting systems. [eur-lex.europa.eu] [ec.europa.eu] [ec.europa.eu], [juston.com] [vatupdate.com], [vatupdate.com]

In summary, the regulatory environment makes X‑Rechnung a must-know for any company dealing with German invoicing. The combination of EU-wide standards and German legislation means that adopting X‑Rechnung not only satisfies public-sector requirements but also positions businesses for the broader trend toward mandatory e‑invoicing in the private sector.

3. Technical Structure of X‑Rechnung

To comply with its legal mandates, X‑Rechnung is built on a rigorous technical foundation. Its design ensures that every invoice carries the data required for VAT compliance in a format that can be validated automatically and understood across different IT systems. Key technical aspects include:

• EN 16931 Semantic Model: X‑Rechnung adheres fully to EN 16931, the European e-invoice standard that defines a core set of invoice information (Business Terms) and business rules. Being EN 16931-compliant means an X‑Rechnung invoice must contain all mandatory data fields required by EU law for a VAT-compliant invoice (for example, supplier and buyer addresses and VAT IDs, invoice date and number, line item details, tax rates and amounts, totals, etc.) in a structured manner. By following EN 16931, X‑Rechnung ensures that the essential VAT information (as required by laws like Germany’s §14 UStG on invoice content) is present and standardized, facilitating both cross-border interoperability and domestic tax compliance. [e-rechnung-bund.de], [juston.com]
• Permitted XML Syntaxes (UBL and CII): The X‑Rechnung format is essentially syntax-neutral within the bounds of the European standard. It can be expressed using either of the two approved XML schemas for EN 16931: UBL 2.1 (Universal Business Language) or UN/CEFACT Cross Industry Invoice (CII). In practice, this means a supplier can issue an X‑Rechnung either as a UBL XML file (commonly used in the Peppol network) or as a CII XML file – both are acceptable as long as they meet the X‑Rechnung schema and business rules. The X‑Rechnung standard is maintained by KoSIT, which updates the specification (including XML schemas and Schematron validation rules) typically twice per year to incorporate new requirements, align with EN 16931 updates, and improve compatibility. For example, X‑Rechnung version 3.0 (2023) introduced new required fields (e.g. buyer/seller contact points) to harmonize with Peppol BIS Billing 3.0, making cross-border use of X‑Rechnung easier and nearly fully interoperable with the Peppol format. [invoice-portal.de] [e-rechnung-bund.de] [e-rechnung-bund.de], [e-rechnung-bund.de]
• Key Data Elements: An X‑Rechnung invoice captures all the information that a German VAT invoice must contain, mapped to the EN 16931 data model. Important data groups include:
  • Seller and Buyer details – Full legal name and address of the supplier and the customer, and tax identifiers for each (e.g. the supplier’s German VAT registration number, and the buyer’s VAT ID if they have one). In B2G invoices, the buyer is a public authority identified by a unique Leitweg‑ID (routing code) to ensure correct delivery to the specific government entity.
  • Invoice metadata – Key invoice reference information such as a unique invoice number, the invoice date, the type of invoice (e.g. credit note if applicable), the currency, and payment due dates and terms. These fields align with legal requirements; for instance, German VAT law mandates a consecutive invoice number and issue date on every invoice. The structured format of X‑Rechnung helps guarantee these appear correctly.
  • Line item details – Each billed item or service is described in a dedicated <InvoiceLine> section. Mandatory line-level fields include an item description, quantity and unit of measure, unit price, and the net line amount. If applicable, each line also specifies its VAT category code and tax rate (e.g. “S” for standard 19% German VAT, “AA” for reduced 7% VAT, “E” for VAT exempt transactions, etc.), so the tax treatment of each line is explicit.
  • Tax totals and VAT breakdown – X‑Rechnung provides a summary of taxes at the invoice level. For each distinct VAT rate or exemption used in the invoice, the XML must include a tax subtotal indicating the total taxable base amount and the total VAT amount for that rate category. This ensures clarity for VAT reporting: e.g. the invoice will clearly show how much of the total is taxed at 19% vs 7%, etc., along with any exemptions (with reference to the legal basis for exemption, as required). The grand total (invoice amount with VAT) and the total VAT amount are also encoded in their own fields. This detailed breakdown is critical for VAT compliance, as it mirrors the information needed for VAT returns and audits.
  • Payment information – While not strictly mandated by all tax laws, X‑Rechnung can include payment and bank details. Suppliers often provide their IBAN, BIC, and payment terms in the invoice so that customers know how to pay. The XML supports specifying the payment due date, discount terms, bank account details, etc. in structured form.
  • Reference documents – X‑Rechnung supports multiple references to related documents or business processes. Common examples are Purchase Order numbers, contract references, delivery note IDs, or project codes that link the invoice to earlier documents. Public-sector invoices typically must include a Leitweg-ID or a purchase order number to pass the buyer’s validation rules. These references, when present in the structured data, allow buyers (and their IT systems) to automatically match invoices to corresponding orders or contracts, improving processing efficiency.
  • Additional notes – The format allows free-text remarks or notes (at both header and line-item level) for any extra information that doesn’t fit into the predefined structured fields. For example, a note might indicate a tax relief clause, provide a short comment to the buyer, or include statutory declarations. While useful, such unstructured notes are generally for supplementary information only – all critical details required for compliance or processing should be recorded in the proper structured fields to ensure they are not overlooked by automated systems. [e-rechnung-bund.de] [vatupdate.com]
• Validation Rules and Compliance Checks: An essential aspect of X‑Rechnung is the built-in validation framework. Because it is crucial that every invoice meets the format’s specifications (otherwise, it may be rejected by the recipient’s system or a government portal), X‑Rechnung comes with official schema definitions and Schematron business rules published by KoSIT. These rules enforce both the syntactical correctness of the XML and various business logic constraints derived from EN 16931 and German requirements. For example, the rules will check that all mandatory fields are present (such as the VAT identification numbers, invoice date, totals, tax breakdowns), that numerical calculations (like totals and tax sums) are correct, and that certain codes (like country codes, currency codes, VAT category codes) are valid. If an invoice fails these validations, it is considered “formally incorrect” and may be automatically rejected by the receiving platform. In fact, the federal OZG-RE platform (described below) performs an automated check for formal errors upon submission and will reject an e-invoice that does not meet the schema or mandatory field requirements, sending a failure notification to the supplier. This makes it imperative for businesses to thoroughly validate their X‑Rechnung files (using test tools or built-in ERP validations) before sending, to avoid processing delays or rejected invoices. [gesetze-im…nternet.de], [e-rechnung-bund.de]

4. X‑Rechnung vs. ZUGFeRD

Germany has two authorized e-invoice standards: X‑Rechnung and ZUGFeRD (the German implementation of the Franco-German Factur‑X hybrid format). While both are designed to be EN 16931-compliant and serve the goal of facilitating digital invoicing, they differ fundamentally in form and use case:

• Structured XML vs. Hybrid PDF/XML: X‑Rechnung is a pure data format: an XML file meant to be read by software. It does not include a PDF rendering of the invoice. ZUGFeRD, by contrast, is a hybrid e-invoice model that embeds an XML file inside a human-readable PDF (specifically a PDF/A-3 file). In a ZUGFeRD invoice, the buyer can open and read the PDF visually, while an accounting system can extract the embedded XML for processing. With X‑Rechnung, the invoice is delivered as an XML file alone; a recipient who wants to view it as a traditional invoice must use either an invoice viewer tool or convert the XML to a PDF using compatible software. This makes ZUGFeRD attractive for scenarios where one party may not have sophisticated IT systems (e.g. small businesses or foreign partners), since it provides a familiar PDF copy. X‑Rechnung, on the other hand, is optimized for cases where both sender and receiver are ready for full automation, which is often true in B2G contexts or among larger companies. [vatupdate.com] [invoice-portal.de]
• Primary Use Cases: X‑Rechnung’s original realm is B2G invoicing, and it remains mandatory for invoices to German public authorities. ZUGFeRD has been more commonly used in B2B transactions, particularly in Germany’s domestic market and in France (as Factur‑X), to encourage e-invoicing adoption without disrupting businesses’ preferences for PDF documentation. However, with the upcoming B2B e-invoicing mandate, both formats are now recognized for domestic B2B compliance – the German law specifically lists X‑Rechnung and ZUGFeRD 2.1 (or later) as acceptable structured invoice formats for the mandate. Many companies may choose ZUGFeRD during the transition if they value the embedded PDF for internal or customer use, but over time X‑Rechnung is expected to dominate in purely automated B2B exchanges, especially as trading partners gain e-invoicing capability. [e-rechnung-bund.de] [vatupdate.com], [juston.com]
• Public Sector vs. Private Sector Requirements: In the public sector, X‑Rechnung’s advantages are clear: it strictly enforces the data needed by government financial systems and auditors, and it avoids any ambiguity by relying on a single machine-readable source of truth. German federal invoice portals historically did not accept PDF invoices at all – even a ZUGFeRD file, if sent with its PDF wrapper via email, would be rejected unless the XML met the X‑Rechnung standard and was transmitted via the proper channels. (To bridge this gap, the ZUGFeRD 2.2 specification introduced an “XRECHNUNG profile” – essentially an option to produce a ZUGFeRD where the embedded XML is 100% X‑Rechnung-compliant, allowing it to function like a plain X‑Rechnung when needed.) In the private sector, there is more flexibility: companies can agree bilaterally to use ZUGFeRD for their B2B invoices to benefit from the PDF+XML format. But notably, because X‑Rechnung and ZUGFeRD share the same data core (EN 16931), converting between them is feasible. Businesses can thus choose a format based on practical needs without losing the standardization; for instance, an incoming ZUGFeRD invoice can often be converted into an X‑Rechnung XML for automated processing, since the underlying information (the EN 16931 data fields) are equivalent. The choice between X‑Rechnung and ZUGFeRD may therefore depend on the recipient: Public entities will insist on X‑Rechnung via official channels, whereas a private customer might accept a ZUGFeRD invoice via email. Going forward, however, the trend – especially under the new mandate – is toward using fully standardized XML invoices (like X‑Rechnung) for maximum automation and consistency.

5. Transmission Channels and Submission of X‑Rechnung

Implementing X‑Rechnung not only involves generating a compliant XML file; businesses must also use the correct delivery channels and protocols to ensure the invoice reaches the buyer (especially a public-sector buyer) in a compliant manner. Key aspects of X‑Rechnung transmission include:

• Central Invoice Submission Portals (ZRE and OZG-RE): To send an X‑Rechnung to the federal government (and many state agencies), suppliers typically use designated online portals. Germany established the Zentrale Rechnungseingangsplattform (ZRE) for federal invoice reception and later the OZG-RE (Online Access Act-compliant Invoice Submission Portal) as a unified platform for electronic invoice submission. As of 2026, the OZG-RE is becoming the primary portal for federal invoices, consolidating earlier systems. Through these portals, invoices can be uploaded via a web interface or sent through automated channels. Notably, each public-sector customer is identified by a unique code (Leitweg-ID) that must be included in the X‑Rechnung (as a routing identifier) to direct the invoice to the correct recipient department. [e-rechnung-bund.de], [e-rechnung-bund.de] [e-rechnung-bund.de]
• Accepted Transmission Methods: Germany’s e-invoicing infrastructure supports a range of delivery methods, all of which ultimately route into the central platforms: direct portal upload, secure web services (APIs), email, and the PEPPOL network. For example, a supplier can submit an X‑Rechnung by uploading it manually to the OZG-RE web portal, or send it via email (as an XML attachment) to a specific address provided by the portal after registration. Many German public entities also accept X‑Rechnung via the PEPPOL e-delivery network, which allows cross-border and business-to-business exchanges using Access Point providers. In fact, the federal OZG-RE is PEPPOL-enabled; suppliers can send X‑Rechnung files through PEPPOL by addressing them to the recipient’s PEPPOL ID (often derived from the Leitweg-ID) and the OZG-RE Access Point. Regardless of the channel, the invoice must remain in a structured electronic form – printing and mailing an invoice or sending an unstructured PDF will not satisfy the requirement for e-invoicing. [e-rechnung-bund.de]
• Structured Submission Requirements: When using these channels, there are specific requirements to observe. For instance, if sending via email or web upload, typically only the XML file (or a ZIP containing the XML and any supplemental attachments) is to be transmitted – there is no need to include a PDF, and including one (or other non-XML content) may cause the invoice to be rejected. The portals and PEPPOL network also enforce size limits and technical validation. As noted, the OZG-RE portal will automatically check each incoming X‑Rechnung file for compliance with the schema and required fields (such as presence of a valid purchase order number or Leitweg-ID for B2G invoices) and will reject the invoice if it fails these checks, notifying the sender of the errors. This means senders should use the official X‑Rechnung validator or other compliant software to pre-validate invoices before transmission. Once submitted and accepted, the invoice is forwarded to the appropriate government agency or business recipient for processing. In a B2B context without a central platform, transmission of X‑Rechnung is more flexible – companies may exchange the XML invoices via email, EDI networks, secure FTP, or even physical media – but large buyers often require using specific channels or platforms (for example, some companies have set up supplier portals or use PEPPOL for trading partner exchanges). It’s important for businesses to clarify with each partner or customer which channel and format version of X‑Rechnung to use, and ensure their systems can send/receive accordingly. [e-rechnung-bund.de]

6. Business and VAT Implications

The adoption of X‑Rechnung has far-reaching implications for businesses’ finance processes, IT systems, and VAT compliance procedures. Key considerations for companies include:

• ERP and Accounting System Updates: Businesses will need to upgrade or configure their ERP, billing, and accounting systems to support X‑Rechnung generation and processing. Many modern ERP solutions (such as SAP, Microsoft Dynamics, etc.) already offer X‑Rechnung or EN 16931 format options, either natively or via add-on modules. Companies should ensure that their software can capture all required data fields (as outlined above) and output a valid X‑Rechnung XML. On the accounts receivable (AR) side, this might involve installing a module to export invoices in X‑Rechnung or using a third-party e-invoicing service provider. On the accounts payable (AP) side, businesses need the ability to receive incoming X‑Rechnung invoices – either through an integrated solution that automatically imports and converts the XML into the ERP’s internal format, or through a service that provides a readable PDF rendering plus data import. IT departments, together with financial controllers, should plan for these changes ahead of the mandate deadlines, including any necessary testing with trading partners and adjustments to master data (e.g. ensuring that VAT IDs and other codes are correctly stored to populate the XML).
• Process Changes and Training: Moving to X‑Rechnung may require redesigning invoice workflows. Instead of printing or emailing PDFs, invoices will be delivered via digital channels and possibly through new middleware. Companies must establish processes for sending e-invoices and monitoring their delivery status (e.g. checking if an invoice was accepted or if a rejection notice was received). Likewise, receiving and processing an e-invoice requires an incoming workflow for XML files – potentially integrating with scanning solutions, invoice approval workflows, and accounting entries. Staff in finance and compliance departments should be trained on the new procedures, such as how to handle validation errors or how to extract/view an X‑Rechnung for review. Many firms conduct pilot projects or phased rollouts to iron out issues before the obligation dates. In engaging with smaller suppliers or customers, businesses may also need to communicate new requirements or even offer support (for instance, some large companies have provided suppliers with web portals or tools to submit X‑Rechnung invoices easily).
• Audit Trail and VAT Compliance: One of the benefits of X‑Rechnung is enhanced VAT compliance, but it also introduces responsibilities. Authenticity and integrity of e‑invoices must be ensured throughout their lifecycle. German regulations do not require electronic invoices to carry an electronic signature or digital seal; instead, companies can rely on internal controls or business process audits to guarantee authenticity of origin and integrity of content (for example, ensuring only authorized systems/users issue invoices, and using access controls and checksums to detect tampering). However, if a company chooses, X‑Rechnung XML files can be electronically signed at the file level or delivered via secure networks, which provides additional assurance. For audit trail purposes, businesses must also adapt their record-keeping: electronic invoices must be archived in their original electronic form for the legally required retention period (generally 6 to 10 years in Germany). Simply printing an X‑Rechnung and storing a paper copy is not compliant, as that would strip away the XML’s structured data and metadata. Instead, companies should store the XML file (and any associated attachments or confirmation receipts) in a tamper-proof electronic archive. During a tax audit, you may be asked to produce both human-readable invoices (which can be generated from the XML on demand) and the original XML files for verification. The structured nature of X‑Rechnung can actually aid audits: tax authorities can automatically cross-verify calculations and VAT declarations using the data in the XML, provided the company can supply the files and demonstrate their integrity. [vatupdate.com]
• Error Handling and Rejection Risks: In a world of automated validation, invoices with errors are more likely to be rejected or require re-issuance. Common pitfalls include missing mandatory information (such as a tax number or purchase order reference), incorrect formatting (e.g. dates not in the required YYYY-MM-DD format), or arithmetic discrepancies. Under the X‑Rechnung system, if an invoice fails validation—whether by a customer’s AP system or a government portal—the invoice is typically rejected and not considered “issued” for VAT purposes. This can impact cash flow and even VAT compliance (since a buyer cannot deduct VAT from an invalid invoice). Therefore, businesses must implement robust validation checks in their invoicing process. Many companies test their X‑Rechnung files with official tools (for example, the public KoSIT validator or cloud-based validation services) before sending. If an error is found post-issuance, the correction process under German VAT rules generally involves issuing a corrected invoice or credit note referencing the original invoice, also in electronic format. It’s important to note that the corrected invoice must itself be an e‑invoice – errors cannot be fixed by reverting to a paper credit note. Companies should also monitor acknowledgments from transmission portals (such as delivery receipts or error messages from OZG-RE/Peppol) so that any issues can be resolved promptly. In short, a culture of “right-first-time” data quality is essential when adopting X‑Rechnung. [e-rechnung-bund.de] [vatupdate.com]

By proactively addressing these system and process implications, businesses not only comply with the law but can also unlock efficiency gains – speeding up invoice processing, reducing payment times, and minimizing the risk of VAT errors.

7. X‑Rechnung in the Broader EU E‑Invoicing Landscape

Germany’s move toward X‑Rechnung and mandatory e‑invoicing is part of a wider European trend to digitize VAT reporting and harmonize invoice formats across the EU. Several key points put X‑Rechnung in context within the European landscape:

• Alignment with EU Digital Strategy (ViDA): In March 2025, EU finance ministers formally adopted the “VAT in the Digital Age” (ViDA) reform package, which will gradually introduce pan-European requirements for e‑invoicing and digital VAT reporting. Under ViDA, structured electronic invoicing will become the default for cross-border B2B transactions within the EU by the end of this decade, accompanied by near real-time digital reporting of invoice data to tax authorities to help combat fraud. The German approach with X‑Rechnung – focusing on standardized content (EN 16931) and a post-audit model (where invoices are exchanged directly and reported later, rather than cleared by government upfront) – is largely consistent with the direction of the EU reforms. Notably, ViDA removes the need for special derogations to mandate e‑invoicing (as previously required under EU law) and encourages Member States to ensure their national systems converge towards common standards. Germany’s early adoption of X‑Rechnung, alongside France’s Factur-X and the use of Peppol in many countries, reflects the EU’s broader goal of interoperability. Companies embracing X‑Rechnung today will be well-prepared for future EU-wide obligations, as the format’s core is aligned with what will likely become a Europe-wide norm for invoice content and format.
• Interoperability Challenges and Solutions: Even with a common standard (EN 16931), European e‑invoicing still features diverse implementation models. Germany’s X‑Rechnung represents a decentralized, post-audit model – invoices flow directly from supplier to buyer (or through open networks/portals) and can be checked later. In contrast, countries with clearance models (like Italy, with its FatturaPA system) require all invoices to pass through a government platform for approval in real time, using country-specific formats. Other nations emphasize network-based exchange, such as the Peppol framework used in parts of Scandinavia and beyond, relying on standardized UBL documents and certified service providers. These different models must coexist and interoperate as we move toward a more unified EU system. The good news is that X‑Rechnung’s data is fundamentally compatible with other EN 16931-based formats – for example, the latest X‑Rechnung update (v3.0.1) was designed to closely align with Peppol BIS Billing 3.0, making a German X‑Rechnung invoice and a Peppol UBL invoice essentially equivalent in content. Likewise, Factur-X (France’s e-invoice format) is technically the same as ZUGFeRD, sharing the EN 16931 core. Still, challenges remain: businesses operating across multiple EU states will need to juggle different platforms and transmission requirements (for instance, connecting both to Germany’s decentralized model and France’s upcoming central Y‑Platform/PDP network for e-invoices, or managing Italy’s unique clearance process). The European Commission and national standard bodies are actively working on standardizing these processes, so that an invoice created in one format can be more easily converted or transmitted for compliance in another country. In the coming years, we expect further harmonization – potentially through updated EU standards or infrastructure – reducing fragmentation. X‑Rechnung’s development demonstrates how a country-specific format can still be rooted in a global standard, offering a blueprint for interoperability. [e-rechnung-bund.de]
• Lessons for Future Mandates: Germany’s experience with X‑Rechnung provides valuable lessons for future EU-wide e‑invoicing mandates. One lesson is the importance of stakeholder readiness and phased implementation: Germany’s phased B2B rollout (2025–2028) gives companies time to adapt, which could serve as a model for other countries transitioning to mandatory e‑invoicing. Another lesson is that promoting standardization without overly restricting transmission methods can spur adoption; Germany allows various compliant formats (X‑Rechnung or ZUGFeRD) and open networks (like email or Peppol) rather than forcing a single platform, which encourages businesses to participate while using solutions that fit their scale and systems. At the same time, Germany’s approach highlights the need for robust validation and support infrastructure – clear specifications, testing tools, and government portals or networks – to make e‑invoicing effective. As the EU moves toward broader digital reporting, the X‑Rechnung story underscores the value of an open, collaborative approach (public-private partnerships in developing standards) and the necessity of aligning with international standards. Ultimately, X‑Rechnung’s rollout is helping to lay the groundwork for a future where electronic invoicing is the norm across Europe, and real-time data exchange helps tax authorities and businesses alike. Companies that invest now in compliant e‑invoicing processes will not only meet Germany’s current requirements but also position themselves advantageously for the next wave of EU VAT modernization under the ViDA framework. [e-rechnung-bund.de]

Sources:

1. Directive 2014/55/EU – European Union Directive on electronic invoicing in public procurement, mandating Member States’ contracting authorities to accept e-invoices aligned with the European Standard EN 16931. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0055
2. German E‑Invoicing Ordinance (E‑Rechnungsverordnung, ERechV) – German Federal Regulation of 13 Oct 2017 (as amended) establishing electronic invoicing requirements for federal contracts, including the adoption of XRechnung as the required standard for e-invoices. (Official key points – German Federal E‑Invoicing Portal)
3. Coordination Office for IT Standards (KoSIT) – XRechnung Standard – Official website providing the XRechnung specifications (XML schemas, schemas, and validation rules) and updates (e.g. XRechnung Version 3.0.1, harmonized with Peppol BIS). https://github.com/itplr-kosit/validator-configuration-xrechnung
4. Germany’s “Growth Opportunities Act” (2024) – Legislation amending the VAT Act (§14 UStG) to introduce mandatory B2B e‑invoicing from 2025, with phased implementation through 2028. https://bundesfinanzministerium.de/Content/EN/Standardartikel/Topics/Taxation/Articles/2023-08-17-Mandatory-e-invoicing-in-Germany.html
5. European Commission – VAT in the Digital Age (ViDA) Package – EU policy initiative adopted on 11 March 2025, which enables mandatory e‑invoicing in the EU and introduces harmonized digital reporting requirements for VAT (including cross-border e-invoice data reporting by 2028).
   (European Commission – Taxation & Customs Union)-

---

See also

E-Invoicing & E-Reporting Explained: ZUGFeRD Invoices in Germany – VATupdate

---

 

---

---