Germany clarifies the structured data expected inside a valid e-invoice

Format claims need profile and content evidence

The BMF points to EN 16931 and identifies common German formats, but format names alone are not a validation result. A buyer needs the exact version and profile, the structured business terms, validation rules, readable rendering, attachments, and the relation between a correction and the original invoice.

The FAQ also distinguishes B2B from public-sector invoicing. A Leitweg-ID and B2G routing process should not be assumed for ordinary domestic B2B invoices. The source system needs a counterparty and transaction classification before selecting the document path.

Receiving is already a control

Even during issuance transition, recipients need a channel that can accept structured documents, retain the original structured component, render it for review, validate data, and move it into AP without losing evidence. An email inbox may meet a basic reception route, but it does not complete those controls.

Vendors should demonstrate XRechnung, qualifying ZUGFeRD, another agreed format, a correction, a complex attachment, and a document that fails business-rule validation. Tax and AP owners should compare how the system distinguishes legal sufficiency, technical validation, business approval, and accounting posting.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.