Germany E-Invoicing Requirements (2026): B2B Timeline & Rules

Germany's e-invoicing requirements apply primarily to domestic B2B transactions between domestic businesses. Since January 1, 2025, a domestic business must be able to receive an e-invoice, but transitional rules still let many suppliers issue paper or other electronic invoices during 2026 and 2027. An e-invoice must contain structured data that enables electronic processing; a plain PDF does not meet that definition.

The German Federal Ministry of Finance (BMF) e-invoice FAQ, updated in March 2026, is the primary authority for the current scope and transition. The rules at a glance are:

Question	Current rule
Which transactions are covered?	Generally, taxable B2B transactions between domestic businesses; B2C and B2G follow different rules.
Who must receive?	Domestic businesses have needed reception capability since January 1, 2025, including small businesses.
What may suppliers issue in 2025-2026?	Paper invoices, or another electronic format such as PDF with the recipient's consent, remain permitted under the general transition.
What changes in 2027?	Suppliers whose prior-year revenue exceeds EUR 800,000 must issue e-invoices for covered transactions. Smaller suppliers and certain noncompliant EDI arrangements retain a transition through year-end.
What changes in 2028?	E-invoicing becomes the general rule for covered domestic B2B transactions after the transitions expire.
Which formats qualify?	EN 16931-compliant structured formats and other agreed interoperable formats that allow complete, correct extraction of the required VAT data.
How may an e-invoice be delivered?	Germany does not mandate one B2B channel; an email inbox is sufficient for reception.
How long must it be retained?	Eight years, with at least the structured component preserved intact in its original form.

The legal minimum is only one part of readiness. Receivers still need to visualize, validate, route, and retain structured invoices reliably. This guide therefore pairs the mandate rules with the practical XRechnung and ZUGFeRD processing work that accounts payable teams face.

---

Germany's E-Invoicing Timeline From 2025 to 2028

Germany's B2B mandate stems from the Wachstumschancengesetz (Growth Opportunities Act), passed in March 2024. The timeline separates the ability to receive from the obligation to issue:

• Since January 1, 2025: domestic businesses must be able to receive e-invoices. This reception rule has no revenue threshold, and small businesses are not exempt from it.
• Through December 31, 2026: any supplier may continue to issue paper invoices. Other electronic formats, such as a plain PDF, remain possible with the recipient's consent.
• During 2027: that transition continues only for suppliers whose total prior-year revenue is no more than EUR 800,000. Certain EDI procedures that do not yet satisfy the e-invoice definition may also continue through year-end.
• From January 1, 2028: an e-invoice is generally required when a VAT invoice must be issued for a covered domestic B2B transaction.

The distinction matters: being able to receive a compliant e-invoice in 2026 does not mean every supplier is already required to send one. Despite the reception rule, a Bitkom survey of 1,103 German companies found that only 45% could receive structured, machine-readable e-invoices in late 2024, showing how much readiness work remained at the start of the mandate.

Which Businesses and Transactions Are in Scope?

For these rules, a domestic business has its registered office, management, or a fixed establishment involved in the transaction in Germany. A foreign company's headquarters or German VAT registration alone does not automatically make it a domestic business; a foreign company registered for German VAT but without a German fixed establishment can fall outside the domestic e-invoice obligation.

The B2B mandate therefore does not apply merely because a foreign buyer receives an invoice from a German supplier. Check whether both parties are domestic businesses for the transaction and whether the German VAT rules require an invoice. A German subsidiary, or a German fixed establishment involved in the supply, can be in scope even when the wider group is headquartered abroad.

The domestic B2B rules are also separate from B2G requirements. Suppliers to German public authorities may have obligations under federal or state e-invoicing rules, including channel requirements that do not apply to ordinary B2B delivery. For context on other country regimes, see the global overview of e-invoicing requirements.

Exceptions Apply to Issuing, Not Receiving

Domestic businesses still need to receive e-invoices even when they are small businesses. The main exclusions and exceptions concern whether an e-invoice must be issued. They include B2C transactions, many VAT-exempt supplies, invoices with a gross total up to EUR 250, qualifying tickets, and supplies made under Germany's small-business VAT regime. A permitted paper or plain-PDF invoice during the transition is also not an e-invoice; it is treated as another type of invoice.

With the legal perimeter clear, the next question for receivers is practical: which structured formats might arrive?

---

XRechnung vs ZUGFeRD: A Head-to-Head Format Comparison

XRechnung and ZUGFeRD are the two common German e-invoice choices, but they are not the only legally possible formats. The governing principle is that the invoice must satisfy EN 16931 or use another agreed interoperable format from which the VAT-required data can be extracted correctly and completely. A qualifying EDI format, for example, can meet that test.

The distinction between XRechnung and ZUGFeRD still matters operationally. One delivers structured XML directly; the other packages structured XML with a human-readable PDF.

XRechnung: Germany's Pure XML Standard

XRechnung is a pure XML format. It contains only structured, machine-readable data with no visual component -- no PDF, no human-friendly layout, just raw data fields organized according to a strict schema.

XRechnung is Germany's national implementation of EN 16931, specifically the CIUS-DE (Core Invoice Usage Specification for Germany). This specification defines the mandatory and optional fields required for German compliance, building on the European standard with country-specific rules for tax reporting, payment terms, and buyer/seller identification.

Originally developed for B2G (business-to-government) invoicing, XRechnung has been used for invoices to German federal agencies since 2020. In B2B transactions it is a common format, not a mandatory channel choice. An XRechnung may be sent by email, Peppol, a portal, or another channel agreed by the parties.

Because XRechnung files contain no visual representation, they cannot be opened and read like a traditional invoice. They require software capable of parsing XML to access the invoice data, and teams that need a practical walkthrough can follow this German guide to opening XRechnung XML files.

ZUGFeRD: The Hybrid PDF+XML Format

ZUGFeRD (version 2.x) takes a fundamentally different approach. It is a hybrid format that embeds structured XML data inside a human-readable PDF document, specifically a PDF/A-3 file. This means a single ZUGFeRD invoice is two things at once: a standard PDF that any finance professional can open, view, and print, and a machine-readable XML payload that automated systems can extract and process.

ZUGFeRD 2.x is aligned with the Franco-German Factur-X standard. They share the same hybrid PDF/XML approach and are designed for cross-border interoperability.

This hybrid nature gives ZUGFeRD particular value as a transitional format. Organizations that have not yet adopted fully automated invoice processing can still open and read the invoice visually, exactly as they would a traditional PDF. Meanwhile, the embedded XML is ready for automated extraction whenever the receiving organization upgrades its capabilities.

One critical detail: not every ZUGFeRD file qualifies. The BMF says ZUGFeRD from version 2.0.1 generally meets the VAT requirements except for the MINIMUM and BASIC-WL profiles. The different ZUGFeRD profiles contain different levels of structured data, so validate the actual file rather than assuming that any PDF with embedded XML is compliant.

Side-by-Side Comparison

Dimension	XRechnung	ZUGFeRD 2.x
Format type	Pure XML	Hybrid PDF/A-3 + embedded XML
Visual readability	No -- requires XML parsing software	Yes -- opens as a standard PDF
Standard/specification	EN 16931 CIUS-DE	Factur-X / EN 16931
Transmission method	Email, Peppol, portal, or another agreed channel	Email, Peppol, portal, or another agreed channel
Data extraction approach	Parse XML directly	Extract embedded XML from the PDF container, then parse
Human review	Requires a viewer or parser to create a readable display	The PDF provides a readable display alongside the XML

Which Format Will Your Suppliers Send?

German VAT law does not assign one format by company size. A supplier can choose XRechnung, qualifying ZUGFeRD, or another interoperable format that meets the legal test, unless a contract or a separate regime such as B2G imposes narrower requirements.

Ask suppliers which formats and channels they plan to use, then test representative files before volume increases. In practice, a robust financial document automation workflow should handle XRechnung's direct XML parsing and ZUGFeRD's embedded XML without treating the visual PDF as a substitute for the structured record.

---

Receiving, Processing, and Retaining a German E-Invoice

German B2B law does not prescribe one transmission channel. An email inbox is enough to establish reception capability; Peppol, a portal, EDI, and direct system connections are options rather than a universal legal default. The parties can agree on a suitable route.

An XRechnung arrives as an XML file. Open it in a text editor and you see raw markup rather than a visual invoice layout, so a viewer or parser is needed for human review. A ZUGFeRD invoice opens as a familiar PDF, but its structured XML component is authoritative if it differs from the visual layer.

The invoice must enable electronic processing, but the recipient is not legally required to automate every downstream AP step. Visualization and manual review can satisfy an immediate operational need. At volume, however, parsing and routing the structured data avoids re-keying information that the supplier has already provided in machine-readable form.

Key Data Fields in Both Formats

Regardless of whether you receive an XRechnung XML file or a ZUGFeRD hybrid PDF, the structured data contains a consistent set of fields:

• Invoice number and invoice date
• Seller name and address
• Buyer name and address
• VAT identification numbers for both parties — Germany uses several distinct tax identifiers including the Steuernummer, USt-IdNr, and W-IdNr, and knowing which number appears on an invoice determines how it should be validated and processed
• Line item details including description, quantity, unit price, and line total
• Tax category and rate per line item
• Invoice totals broken down into net amount, tax amount, and gross amount
• Payment terms and bank details
• Currency code

These fields correspond to the mandatory German VAT invoice fields. Reverse-charge invoices and other special cases can change which tax fields should appear, so schema validity alone does not prove that the tax treatment is correct.

Validation and Eight-Year Retention

Before posting, validate the XRechnung or ZUGFeRD structure and business rules, then route valid data into the accounting system and isolate exceptions for review. Validation is a useful control, although the BMF notes that passing a technical validator is not by itself a condition for VAT recognition.

Keep each incoming and outgoing e-invoice for eight years. At minimum, preserve the structured component intact in its original form; converting it into a PDF or spreadsheet is not a replacement for retaining the original structured record. The wider archive and audit trail should follow GoBD digital record-keeping rules.

---

How to Extract and Process Data From German E-Invoices

Receiving a German e-invoice is only the first step. The real operational task is extracting the structured data from these files and routing it into your accounting system, ERP, or AP workflow. Because XRechnung and ZUGFeRD present fundamentally different file structures, each format demands its own extraction approach.

Extracting Data From XRechnung (Pure XML)

XRechnung files are fully structured XML, which means the data is already machine-readable. In principle, extraction is straightforward: parse the XML elements and map each field to the corresponding input format your accounting system expects.

In practice, this is more involved than it sounds. You need a working understanding of the XRechnung XML schema, including how mandatory and optional fields are structured, how field variations between suppliers are handled, and how to convert the extracted values into the exact format your downstream systems require -- whether that is Excel, CSV, or a proprietary import template. For organizations receiving a handful of German invoices per month, manual XML parsing or a basic script may be sufficient. Once volumes increase or invoices arrive from multiple German suppliers with slightly different field usage, automated extraction becomes a practical necessity.

Extracting Data From ZUGFeRD (Hybrid PDF)

Opening a ZUGFeRD file in a standard PDF reader shows a normal-looking invoice. The structured data you actually need for automated processing, however, sits underneath that visual layer. It is embedded as an XML attachment inside a PDF/A-3 container, invisible through the normal viewing interface.

Accessing that embedded XML requires tools capable of parsing the PDF/A-3 container and reading the attached XML stream. This is not an OCR task. The data is already structured and machine-readable; it is simply embedded rather than directly accessible. While both the visual PDF layer and the embedded XML should contain identical information, the XML layer is the authoritative source for automated processing and should be treated as such when feeding data into your systems. Teams using spreadsheets can follow the same principle when extracting ZUGFeRD XML for Excel import.

Handling Mixed-Format Batches

Most organizations will not receive exclusively one format. Different German suppliers will send XRechnung XML files, ZUGFeRD hybrid PDFs, or a mix of both. Processing these mixed batches manually -- parsing standalone XML from one set of suppliers and extracting embedded XML from another -- creates operational friction that compounds as invoice volumes grow. This friction becomes more acute as the 2027 and 2028 deadlines bring more covered suppliers into mandatory issuance.

Match the Tool to the Source Format

Standalone XRechnung XML and the embedded XML inside ZUGFeRD require an e-invoice parser, accounting platform, or ERP integration that supports those structured formats. That workflow should preserve and use the authoritative XML rather than convert it to an image and apply OCR.

For conventional invoice PDFs or images that accompany the wider AP workload, automated invoice data extraction tools can convert the visible documents into spreadsheet-ready data. Invoice Data Extraction accepts batches of up to 6,000 PDF, JPG, and PNG files, uses natural-language prompts to define the fields and output structure, and produces Excel, CSV, or JSON. It does not accept standalone XML, so it should complement rather than replace the system used to parse XRechnung or embedded ZUGFeRD data.

---

Germany E-Invoicing Compliance Checklist

Use the following checks to separate legal scope from implementation work:

1. Confirm which German entity and transactions are in scope. Identify the registered office, management, or German fixed establishment involved in each transaction. Do not treat foreign headquarters, German VAT registration, or a German supplier relationship alone as proof that both parties are domestic businesses.

2. Confirm reception capability now. Ensure at least one monitored email inbox can receive XML attachments and that portals or mail filters do not reject unfamiliar structured files. Add Peppol or another network when it solves an operational need, not because German B2B law universally requires it.

3. Map the issuing timeline and exceptions. Record each issuer's prior-year revenue for the 2027 threshold and distinguish covered B2B supplies from B2C, qualifying exempt supplies, small invoices, tickets, and small-business-regime supplies.

4. Test the full intake path. Visualize and validate sample XRechnung and ZUGFeRD files, map the structured fields into the accounting system, and define an exception queue. A format test should include tax logic and required business data, not only whether a file opens.

5. Preserve the original structured record. Retain the structured component intact for eight years and document access, audit trail, and change controls under GoBD. For channel, validation, ERP routing, and archiving detail, use the German e-invoice intake process.