For many accounts payable teams in Germany, invoice processing has traditionally involved opening a PDF, reading its contents and manually entering the relevant details into an ERP or accounting system. That workflow is already changing on the receiving side and will change further on the issuing side as Germany’s e-invoicing mandate phases in through 2027 and 2028. e-Invoicing in Germany has moved beyond a compliance checkbox. It is changing how invoice data is validated, how invoices enter accounts payable workflows and how exceptions and rejections are handled.
Germany’s shift from conventional invoices to structured e-invoices
The legal framework for Germany’s B2B e-invoicing requirements is set out in Section 14 of the German Turnover Tax Act (UStG), following the changes introduced through the Wachstumschancengesetz in 2024. Since January 1, 2025, every business in Germany has needed to receive and process a structured e-invoice even if it is not yet required to issue one itself. During the transition period, suppliers can continue using paper, PDF and other permitted invoice formats, subject to the applicable requirements for non-EN-compliant electronic invoices. The structured e-Invoice issuance obligation begins in 2027 for businesses above the applicable turnover threshold and expands to all remaining businesses in 2028. As these requirements phase in, businesses should also assess whether their Germany e-Invoicing solution can support structured invoice receipt, processing, and future issuance requirements.
From January 1, 2027, companies with turnover greater than 800,000 euros in the previous year must issue structured e-Invoices for domestic B2B transactions. From January 1, 2028, the requirement extends to all businesses irrespective of size. A plain PDF, however well formatted, does not meet the legal definition of an e-invoice Germany recognizes by itself because it is not machine-readable structured data a receiving system has to process automatically. E-invoicing in Germany is moving from an optional efficiency upgrade to a dated legal requirement and AP teams that wait until 2027 or 2028 to prepare are doing so under time pressure not by design.
Where XRechnung and ZUGFeRD fit into the invoicing process
Germany’s mandate does not lock businesses into one file format. XRechnung is a structured XML-based invoice format aligned with Germany’s implementation of EN 16931 and designed for automated processing. It does not include a human-readable visual layer in the way a conventional PDF invoice does. ZUGFeRD is a hybrid format that engulfs structured XML data inside a standard PDF. This allows a person to open and read the invoice while the system extracts the same data programmatically. Both approaches can comply with the European EN 16931 standard, while other structured syntaxes and profiles are also supported within the German and Peppol environment.
The practical choice between them is usually one of the audiences. XRechnung is particularly suited to recipients whose systems process invoices electronically without requiring a human-readable document for routine review.
ZUGFeRD provides a hybrid option for organizations that need both machine-readable invoice data and a human-readable document for review or downstream business processes.
Germany does not currently require domestic B2B invoices to pass through a central government clearance platform. Instead, B2B e-invoicing follows a decentralized four-corner model, with Peppol supporting interoperable exchange between businesses and their service providers. B2G follows a separate model, with federal public-sector invoices handled through the OZG-RE platform, while Peppol can also be used for submission. There is currently no mandatory real-time submission of B2B invoices to the tax authority.
How structured invoice data moves through accounts payable workflows
Once an invoice is genuinely structured, the way it enters an AP workflow changes fundamentally. Instead of a person reading a PDF and typing values into a system, the structured XML, whether standalone in an XRechnung file or embedded inside a ZUGFeRD PDF, can be parsed directly and mapped into the ERP’s invoice fields automatically. This removes a major source of manual entry error, but only if the receiving system is built to extract and validate that data correctly rather than falling back on the same OCR-based scanning used for conventional PDFs.
Most AP departments will not receive one consistent format from every supplier. A mix of ZUGFeRD hybrid PDFs, XRechnung XML files, and conventional invoices is the realistic near-term picture. An AP workflow built for structured e-Invoicing needs to route each format correctly. The workflow must extract authoritative XML rather than converting a ZUGFeRD PDF to an image and re-scanning it. This approach discards the accuracy for which the structured format was designed.
Why supplier, purchase-order, tax, and duplicate checks become important
Structured invoice data makes automated validation possible in ways manual review never reliably achieved, but only if the underlying reference data is accurate. Supplier records need correct identifiers and banking details so an incoming e invoice Germany’s system receives can be matched to the right vendor without ambiguity. Purchase order matching becomes more precise as well, since a structured invoice carries line-item detail in a consistent format that can be checked against the original PO automatically rather than approximately.
Tax data matters just as much, since VAT treatment needs to be correctly represented in the structured fields for the invoice to pass validation and for downstream tax reporting to stay accurate. Detecting duplicate invoice also becomes simpler and more reliable with a structured data. This is because supplier identifiers and regular invoice numbering makes it simpler for a system to catch a double-processed invoice might not have caught an eye of a manual reviewer. Getting these four data categories on point is necessary for better invoice processing automation.
Common reasons for invoice corrections, rejections, and payment blocks
Certain issues recur predictably as businesses transition to structured invoicing. Format non-conformance is among the most common, particularly early on, when a supplier’s system generates XML that does not fully meet EN 16931 requirements, causing the receiving system to reject or flag the invoice before it reaches an approver. Missing mandatory fields, such as a tax identifier or a required reference number, produce a similar outcome.
Purchase order and quantity mismatches remain a familiar cause of payment blocks, structured invoicing or not, but a system can now catch these discrepancies immediately and precisely rather than relying on a person to notice a variance during manual review. When there is a correction, it is generally the supplier who reissues a correct structured invoice and not the AP team that is editing the received file; altering a structured invoice after receipt breaks the format. If businesses can make a choice on when to return rejected invoices to their suppliers they can avoid having to deal with the backlog of unknown and unpaid invoices that build up early on.
How e-invoicing affects financial controls, process visibility, and audit records
In addition to the delivery of individual invoices, structured e-invoicing can also change financial controls and audit trails. Structured data can be easily validated and matched and finance teams have a better sense of what is wrong with a purchase order or a tax coding error before payment as opposed to a long-term, ongoing reconciliation process. But this cuts down the time between error and someone catching it. And archiving requirements also matter: e-invoices need to be kept in their original structured electronic format for up to 10 years so audit records retain the same machine-readable data that was originally validated, rather than a scanned image that has lost that structure.
For businesses preparing for the 2027 and 2028 deadlines, establishing this level of process visibility and control now will determine whether a German e-Invoicing solution genuinely strengthens financial controls or simply adds a new file type to an otherwise unchanged process.