fakturai blog

Validation checklist

German e-invoice validation checklist before sending or booking

Short answer: do not validate a German e-invoice visually. The structured XML part must be EN 16931-compatible, the ZUGFeRD/Factur-X or XRechnung encoding must be correct, and the technical KoSIT result should be checked before sending or booking.

Quick pre-flight checklist

  1. Is it actually an e-invoice? A plain PDF is not enough. ZUGFeRD/Factur-X needs embedded XML; XRechnung is structured XML.
  2. Does the format fit the recipient? B2B often uses ZUGFeRD/Factur-X; B2G often uses XRechnung. EN 16931 is the common technical core.
  3. Are mandatory fields structured? Seller, buyer, invoice number, date, line items, VAT categories, totals and payment data must be machine-readable.
  4. Does technical validation pass? Schema, business rules, PDF/A for hybrids and the official German KoSIT result should be checked before delivery or booking.
  5. Can the original be archived? GoBD processes depend on preserving the original structured file, not only a printout or screenshot.

What the fakturai validator checks

The free validator is the fastest entry point for received and self-generated invoices. It focuses on format and structure:

Common errors to catch early

What fakturai does not replace

fakturai checks technical format and structure. Content correctness, VAT rates, service descriptions, tax classification, GoBD process documentation and booking decisions remain with the issuer or recipient. fakturai is not tax advice and makes no legal, tax or penalty promises.

Next step

Validate an existing ZUGFeRD, Factur-X or XRechnung file for free. If it fails technically, fix the generation source before sending or booking it.

Free German e-invoice validator

Related: KoSIT validator · Technical validation · Why PDF is not an e-invoice · API & MCP generation

Free validator · Create API key · API docs