Germany's B2B e-invoicing mandate requires all businesses to accept structured electronic invoices since January 2025. Large companies (over EUR 800,000 revenue) must issue e-invoices from January 2027, and all businesses must comply by January 2028. The two compliant formats are XRechnung (pure XML) and ZUGFeRD (hybrid PDF with embedded XML), both based on the European standard EN 16931.
Most guidance on Germany's e-invoicing requirements focuses on the sender's obligations: how to create, validate, and transmit compliant invoices. This guide addresses the other side of the transaction. If you receive an XRechnung XML file or a ZUGFeRD hybrid PDF from a German supplier, you need to know what those files contain, what your obligations are, and how to get that data into your accounts payable workflow. It covers the phased compliance timeline, how the two formats differ, what receiving these invoices looks like in practice, whether non-German businesses fall under the mandate, and how to extract structured data from both formats for AP processing.
Germany's E-Invoicing Timeline: Three Phases From 2025 to 2028
Germany's B2B e-invoicing mandate stems from the Wachstumschancengesetz (Growth Opportunities Act), passed in March 2024. The BMF (German Federal Ministry of Finance) oversees the rollout, which introduces mandatory e-Rechnung (e-invoicing) in three distinct phases.
The driving force behind the mandate is closing Germany's VAT compliance gap. The European Commission estimates Germany lost EUR 31.3 billion to its VAT compliance gap in 2023, equivalent to 9.7% of total VAT liability. Structured e-invoicing gives tax authorities machine-readable transaction data, making it far harder to underreport or fabricate invoices. The mandate also aligns with the EU's broader ViDA (VAT in the Digital Age) initiative, which aims to standardize digital tax reporting across member states.
Here is what the three-phase rollout looks like in practice:
| Phase | Effective Date | Obligation | Who It Applies To |
|---|---|---|---|
| Phase 1 | January 1, 2025 | Receive structured e-invoices | All businesses operating in Germany, no exemptions |
| Phase 2 | January 1, 2027 | Issue e-invoices for B2B transactions | Businesses with annual revenue exceeding EUR 800,000 |
| Phase 3 | January 1, 2028 | Issue e-invoices for B2B transactions | All businesses, regardless of size |
Phase 1 is already in effect. If your company receives invoices from German suppliers, you are required to accept structured e-invoices right now. This is the most commonly misunderstood part of the German e-invoicing requirements: Phase 1 is about reception capability, not issuance. Even if your business is not yet required to send e-invoices, it must be able to receive and process them. There are no revenue thresholds, no grace periods, and no exemptions for this obligation. Despite this, a Bitkom survey of 1,103 German companies found that only 45% could receive e-invoices in structured, machine-readable formats as of late 2024, highlighting a significant readiness gap even after the reception mandate took effect.
Phase 2 and Phase 3 then shift the focus to the sending side. From January 2027, larger businesses (above EUR 800,000 annual revenue) must issue compliant e-invoices for domestic B2B transactions. By January 2028, every business operating in Germany must do the same, completing the B2B e-invoicing mandate.
B2G (business-to-government) e-invoicing has been mandatory in Germany since November 2020, using the XRechnung standard. The current mandate extends that requirement to all B2B transactions. For a broader look at how Germany's mandate fits within worldwide adoption trends, see our global overview of e-invoicing requirements.
The next question for receivers is practical: which format do these e-invoices arrive in?
XRechnung vs ZUGFeRD: A Head-to-Head Format Comparison
Germany's e-invoicing mandate recognizes two compliant formats, and both conform to the European standard EN 16931. While that shared foundation might suggest they are interchangeable, the differences between XRechnung and ZUGFeRD are significant. Each format structures and delivers invoice data differently, which means your approach to data extraction and processing must account for whichever format your German suppliers choose to send.
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 the required format for invoices sent to German federal agencies since 2020. Under the new B2B e-invoicing mandate, it serves as the reference standard. Transmission typically occurs via the Peppol network or other electronic data interchange channels rather than through email attachments.
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.
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 technically identical to the Franco-German Factur-X standard. These are not merely compatible -- ZUGFeRD 2.x IS Factur-X. They share the same XML schema and the same PDF embedding approach, developed jointly by German and French standards organizations.
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: ZUGFeRD defines multiple conformance profiles -- Minimum, Basic, Comfort (EN16931), Extended, and XRechnung -- each representing a different level of structured data completeness within the ZUGFeRD format. Not all profiles satisfy the B2B mandate. Only the EN16931 profile and above are fully compliant with Germany's requirements. If a supplier sends a ZUGFeRD invoice using the Minimum or Basic profile, it does not qualify as a compliant e-invoice under the mandate.
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 | Peppol network or electronic channels | Email attachment or any file transfer channel |
| Data extraction approach | Parse XML directly | Extract embedded XML from the PDF container, then parse |
| Transitional value | Requires automated processing from day one | Can be read visually as a fallback while automation is implemented |
Which Format Will Your Suppliers Send?
The format you receive depends largely on who is sending the invoice. XRechnung is more common from larger enterprises and public sector entities that already operate within the Peppol network and have mature e-invoicing infrastructure. These organizations typically have no need for a visual PDF layer and favor the leaner XML-only approach.
ZUGFeRD is often preferred by SMEs and businesses transitioning to e-invoicing for the first time. The visual PDF component preserves the familiar invoice experience, reducing friction for both the sender and receiver during the transition period. For organizations that are automating financial document processing, ZUGFeRD's dual nature offers flexibility: staff can visually verify invoices while automated systems extract the structured data in parallel.
In practice, most receivers will encounter both formats. Your processing infrastructure needs to handle XRechnung's direct XML parsing and ZUGFeRD's two-step extraction (PDF container first, then embedded XML) with equal reliability.
What Happens When You Receive a German E-Invoice
An e-Rechnung has arrived — an XRechnung XML file or a ZUGFeRD PDF — and your AP team needs to process it. Here is what to expect from each format in practice.
An XRechnung arrives as an XML file via the Peppol network or email. Open it in a text editor and you see raw markup — no visual invoice layout. The XML must be parsed programmatically to extract fields and route them into your ERP or accounting system. An ZUGFeRD invoice opens as a standard PDF with a familiar visual layout, but the authoritative structured data sits in an embedded XML layer inside the PDF/A-3 container. For automated processing, extract that embedded XML rather than applying OCR to the visual layer.
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 VAT invoice fields defined under §14 UStG, which specifies all 14 data elements a German invoice must contain for the recipient to claim Vorsteuerabzug (input VAT deduction). Note that invoices subject to the §13b UStG reverse charge mechanism carry different requirements -- no VAT amount is shown, and the recipient bears the tax liability -- so the field expectations change when a reverse charge scenario applies. Field handling also differs depending on the type of German invoice being issued -- an Abschlagsrechnung (progress invoice) carries partial amounts and references to the overall contract, while a Schlussrechnung (final invoice) must reconcile all prior partial payments and adjust VAT accordingly.
Getting the Data Into Your Systems
The receiver's immediate task is straightforward in principle: extract this structured data and load it into your accounting system or pre-accounting and document processing workflows. In Germany, that accounting system is overwhelmingly DATEV, the platform underpinning most Steuerberater workflows, so the extracted fields need to map to DATEV's expected import formats. For a single invoice, that might be manageable with basic tools or even manual review of the PDF version.
For organizations handling invoices from multiple German suppliers, however, this quickly becomes a volume challenge. Your inbox will contain a mix of XRechnung XML files that require parsing and ZUGFeRD hybrid PDFs where the valuable data is locked inside an embedded XML layer. Each format requires different handling, and the volume compounds with every new German supplier that transitions to e-Rechnung under the mandate's phased timeline.
But does Germany's e-invoicing mandate apply to businesses outside of Germany?
Do Non-German Businesses Need to Comply?
Yes. If your business receives invoices from German suppliers, the e-invoicing mandate applies to you regardless of where your company is headquartered. Since January 1, 2025, every business operating in Germany must be able to accept structured e-invoices in EN 16931-compliant formats. This obligation extends to non-German recipients. You cannot refuse a compliant e-invoice and demand a paper or traditional PDF alternative instead.
For UK, US, and EU companies with German suppliers, the practical reality is straightforward: your invoice intake process is changing whether you initiated that change or not.
Under the phased rollout, German businesses are progressively required to issue e-invoices in XRechnung or ZUGFeRD format. By January 2028, all German businesses must issue structured e-invoices for domestic B2B transactions. The volume of XML-based invoices arriving in your AP inbox will increase steadily over the next two years. If your current workflow assumes every inbound invoice is a flat PDF, that assumption is already outdated.
This means your AP systems need to handle both formats. XRechnung invoices are pure XML files with no visual representation. ZUGFeRD invoices embed XML within a PDF, but the structured data layer is what matters for automated processing. Your accounts payable team needs tools and processes that can parse these formats, validate them against EN 16931, and route the extracted data into your ERP or accounting system. Manual re-keying from a PDF view defeats the purpose and introduces errors that structured invoicing was designed to eliminate.
If your organization has a subsidiary, branch office, or permanent establishment in Germany, that entity is directly subject to the mandate on both sides of the transaction. It must accept e-invoices now, and it must issue them according to the phased timeline. This is a legal requirement under the Wachstumschancengesetz, not an optional upgrade for local compliance teams.
The language dimension deserves specific attention. XRechnung and ZUGFeRD use standardized XML field structures that map to universal invoice data points (seller, buyer, line items, tax amounts), but the text content within those fields is often in German. Item descriptions, payment terms, and supplier notes may all arrive in German. For AP teams outside the DACH region, correctly interpreting and categorizing this data requires either German-language competency on the team or tools capable of processing multi-language and multi-currency invoices accurately. Misreading a field description can lead to incorrect GL coding or missed tax obligations.
Germany's mandate is part of the EU's broader VAT in the Digital Age (ViDA) initiative, with France, Poland, Belgium, and others implementing similar requirements on overlapping timelines. Companies that build German e-invoicing compliance into their AP infrastructure now are building the foundation to handle this wave of EU-wide mandates. For entities operating in Germany specifically, the retention obligation is governed by GoBD digital record-keeping rules, which dictate how e-invoices must be archived and made available for audit.
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.
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 particularly acute during the 2027 and 2028 mandate phases, when all German businesses must issue e-invoices and inbound volumes will increase significantly.
Purpose-Built Extraction Tools for Both Formats
Rather than maintaining separate workflows for each format, automated invoice data extraction tools handle both XRechnung XML and ZUGFeRD hybrid PDFs within a single processing pipeline. Invoice Data Extraction, for example, accepts mixed-format batches of up to 6,000 files per job, including both pure XML files and hybrid PDFs with embedded XML data. The platform supports all major languages, which is critical when processing German-language invoices with field labels, line item descriptions, and tax references in German.
Users specify extraction rules through natural language prompts. You can instruct the system to extract data from the embedded XML layer of a ZUGFeRD PDF rather than applying OCR to the visual layer, or define exactly which fields to pull and how to structure the output. The extracted data is delivered as structured Excel (.xlsx), CSV (.csv), or JSON (.json) files ready for direct import into your accounting software or ERP system.
Your Compliance Checklist as an E-Invoice Receiver
Reception requirements are already live. Here is a checklist of the actions that matter most.
1. Confirm reception capability now. Since January 2025, your organization must be able to accept XRechnung and ZUGFeRD invoices from German suppliers. Verify that your email systems can receive XML file attachments, that your AP portals do not reject unfamiliar file types, and that any Peppol access points you use are configured to handle EN 16931-compliant documents.
2. Assess your supplier base. Identify which of your current suppliers are incorporated in Germany or operate from German entities. These suppliers will be transitioning their invoicing to XRechnung or ZUGFeRD as the 2027 and 2028 issuance deadlines take effect. Understanding the scope of exposure lets you prioritize system upgrades where they will have the greatest impact.
3. Evaluate your extraction workflow. Determine whether your current accounts payable systems can parse raw XRechnung XML and extract the embedded XML layer from ZUGFeRD PDFs. If your team is handling these formats manually or your systems cannot process them at all, evaluate automated extraction tools that can read structured invoice data directly into your financial systems.
Related Articles
Explore adjacent guides and reference articles on this topic.
ZUGFeRD Invoice Format: Profiles, Compliance & Processing Guide
Guide to Germany's ZUGFeRD invoice format: all six profiles compared, B2B mandate compliance, and how to extract structured data from hybrid PDF/XML invoices.
Greece myDATA E-Invoicing Requirements 2026: Compliance Guide
Guide to Greece's myDATA B2B e-invoicing mandate: March and October 2026 deadlines, MARK validation, classification codes, penalties, and receiver compliance.
France E-Invoicing Mandate 2026: What Your Business Needs to Know
Guide to France's September 2026 e-invoicing mandate for non-French businesses. Covers the rollout timeline, invoice formats, penalties, and how to prepare.
Extract invoice data to Excel with natural language prompts
Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.