Validate ZUGFeRD 2.1 hybrid invoice PDF/XML before submission to a German B2B recipient

domain: ecosio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Generate the invoice in ZUGFeRD 2.1 format: embed a CII D16B XML file named ZUGFeRD-invoice.xml as an attachment in a PDF/A-3 document
  2. Validate the embedded XML against the EN 16931 CII schematron using the ConnectingEurope artefacts (current release v1.3.16)
  3. Validate against the ZUGFeRD 2.1 EXTENDED or COMFORT profile schematron provided by the FeRD organization for profile-specific rules
  4. Use the Mustang Project open-source library or an equivalent validator to run combined PDF/A-3 structural and XML schematron checks in one pass
  5. Archive the validated ZUGFeRD file for the GoBD-required 10-year retention period, preserving the original binary without alteration

Known gotchas

Related routes

Submit XRechnung e-invoices to German B2G portals via OZG-RE
e-rechnung.gv.at · 6 steps · unrated
Plan Germany's phased B2B e-invoice issuance mandate rollout for 2027 and 2028
bundesfinanzministerium.de · 5 steps · unrated
Validate an e-invoice against EN 16931 schematron rules before transmission
github.com/ConnectingEurope/eInvoicing-EN16931 · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans