Format choice
ZUGFeRD, Factur-X, XRechnung and EN 16931: which format fits?
For most German B2B companies ZUGFeRD 2.0.1+ (EN 16931 / Comfort or Extended profile) is the most practical choice: a hybrid format (human-readable PDF/A-3b + embedded XML) that meets EN 16931 and is generated + pre-delivery KoSIT-validated by fakturai. XRechnung is primarily relevant for the public sector (B2G) and often mandated there.
EN 16931 — the binding standard
The EU created EN 16931 as the semantic data model for electronic invoices. Structured formats per EN 16931 are required for the German B2B receive obligation since 2025.
ZUGFeRD / Factur-X vs XRechnung
ZUGFeRD / Factur-X: hybrid PDF/A-3b plus embedded CII XML. This is usually the pragmatic B2B choice because people can read the invoice while accounting and automation tools process the structured part.
XRechnung: pure XML, commonly required by German public-sector buyers. It is a strong fit for B2G portals, but less convenient when commercial customers still expect a readable PDF view.
Practical decision guide
Most B2B cases: choose ZUGFeRD/Factur-X in an EN 16931-capable profile. B2G/public: check the tender or portal rules — XRechnung is often required. Automation: hybrid files work well for n8n, Make, Zapier, backends and agents because the same invoice can be read by humans and machines. Tip: always test with a validator before productive sending. MINIMUM/BASIC-WL profiles do not meet the obligation.
What fakturai checks
fakturai applies a technical quality gate before delivery for generated hybrid invoices: XSD schema checks, EN 16931 Schematron rules, PDF/A-3b checks and official KoSIT validation. This does not replace tax or legal review of the underlying invoice content; it proves the file structure is technically usable.
Validate an existing e-invoice for free · API docs · Create an API key