E-Invoicing in 2027: The Roles of XRechnung and ZUGFeRD

Germany's first general e-invoice transition period ends on December 31, 2026. For covered domestic B2B transactions performed in 2027, issuers with more than €800,000 in total revenue during the prior calendar year generally may no longer use paper or an ordinary PDF. Smaller issuers receive another transition year.

The receiving requirement began earlier, on January 1, 2025, and has no corresponding extension.

Section 14 of Germany's Value Added Tax Act defines an e-invoice as a structured electronic format that enables electronic processing. The format may comply with the EN 16931 family of standards. Business partners may agree on another format if the VAT information can be extracted accurately and completely into a standards-compliant or interoperable format. A regular PDF without structured invoice data falls into the German statutory category of a ‘sonstige Rechnung,’ or other invoice, rather than an e-invoice.

XRechnung and ZUGFeRD

The Federal Ministry of Finance identifies XRechnung and ZUGFeRD version 2.0.1 or later as qualifying examples. The ZUGFeRD MINIMUM and BASIC-WL profiles do not meet the VAT requirements. XRechnung contains structured XML without an additional PDF invoice rendering, so human review requires a visualization. ZUGFeRD combines PDF/A-3 with embedded XML. If the visual and structured records conflict, the structured component controls. All required VAT information must also appear in the structured component; a reference to an unstructured attachment generally does not replace it.

For implementation, the parties should agree on the version, syntax, profile, and transport method and test the files that the recipient actually processes. Those details are implementation guidance, not an additional statutory file format.

Transmission and Assignment

The Finance Ministry does not prescribe a particular transmission channel for e-invoices. Email may be sufficient, and the receiving duty does not require every subsequent processing step to be performed electronically.

The business still needs to determine where files arrive, who handles technical failures, and how the invoice is linked to the purchasing transaction. Those organizational decisions follow from its workflow, not from a mandated software architecture. A German routing ID, or Leitweg-ID, is generally not required for B2B invoicing. Field BT-10 can instead contain an internal buyer reference. Whether a format technically requires a field and whether VAT law requires that particular information are separate questions. A file may therefore fail a format rule even when both parties clearly understand the underlying supply. Supplier coordination should establish which reference value is expected and where the recipient processes it.

Transition Rules and Exceptions

Through the end of 2026, issuers may still use paper or, with the recipient's consent, other electronic formats. For transactions performed in 2027, that option generally remains if the issuer's prior-year revenue did not exceed €800,000. Certain EDI processes that are not already compliant may also continue through 2027 under the transition. The revenue threshold disappears for covered domestic B2B issuance in 2028.

Statutory exceptions remain. They include low-value invoices up to €250 gross, passenger tickets, and supplies by small businesses under the applicable German tax rule. Consumer transactions and many VAT-exempt supplies listed in Section 4(8) through (29) are not subject to the same issuance duty. The year and file extension alone therefore do not determine whether a particular invoice is covered.

Technical Validation and Content Review

Successful technical validation does not confirm that every invoice detail is factually correct. The Finance Ministry's October 15, 2025, guidance distinguishes format errors from content errors. For example, a file may satisfy the technical rules being checked while containing the wrong VAT rate. The validation report may be retained as evidence of the check; review of the supply, amount, and tax treatment remains a separate task. This distinction suggests two separate results for an operational test: can the agreed format be processed, and does the invoice correctly represent the actual business transaction? A schema error requires a different handling path from a question about the invoiced supply. That difference should also appear in the error status so that a resubmitted invoice is not treated as substantively approved solely because it was technically accepted.

Corrections require another distinction. Where an e-invoice is mandatory, a required invoice correction generally must also be structured and identify the original invoice unambiguously; transition rules still apply. Under the tax administration's interpretation, a change in the taxable amount, such as a cash discount, is treated differently from a change in the scope or substance of the supply. A price reduction therefore does not automatically require a new invoice.

Display, validation, and retention serve different purposes on receipt. The Finance Ministry recommends validation but does not require a particular validator. A rendering supports human review and does not replace the original record.

German VAT law requires a copy of each incoming and outgoing invoice to be retained for eight years; for an e-invoice, at least the structured component must remain intact in its original form. Issuers above the revenue threshold should test that workflow before their first covered transaction in 2027. Under Section 14b of the Value Added Tax Act, the eight-year period begins at the end of the calendar year in which the invoice was issued. Section 147(3) of the Fiscal Code remains unaffected. Eight years therefore does not authorize blanket deletion based simply on a file's age. A retention policy must account for the start of the period, the original file, and any additional grounds for retention.

Note: This assessment is not a substitute for a review of the specific case.