What fakturai checks (the KoSIT-Accept-Gate)
Use the free validator when you need to technically check an existing XRechnung XML or ZUGFeRD/Factur-X PDF. Every invoice is validated in 4 layers before return:
- PDF/A-3b structure (GoBD archival)
- XSD schema (EN 16931 core rules)
- EN 16931 business rules (Schematron) + PDF/A-3b validation for ZUGFeRD/Factur-X
- Official KoSIT validator (German tax authority acceptance rules) — only “accept” passes.
Hard failures (EN 16931 core) vs. advisory notices (BR-DE/PEPPOL profiles for B2B). These profile notices are typically informational for B2B — KoSIT is the binding gate.
From free check to repeatable e-invoice generation
The upload is the fastest first step: submit the invoice, read the technical result, then fix XML/PDF errors. When invoices are generated repeatedly from a CRM, shop, ERP, n8n, Make, Zapier or an AI agent, the API/MCP route is steadier: the same technical checks, but with a reproducible input schema and automatable generation.
What fakturai does not replace (and does not promise)
fakturai enforces technical format compliance (EN 16931 + KoSIT). It does not replace your tax advisor or bookkeeping system and accepts no liability for content correctness (VAT, line-item accuracy, GoBD archiving duties). Legal and tax consequences remain 100% with the issuer. No legal guarantees or financial-penalty promises. (GHOA-1671)
Next step: Validate an existing invoice for free, then request an API key or read API & schema / MCP.
Deep dives: E-Rechnung Wissen — all 38 articles (mandate 2025/2027, ZUGFeRD/Factur-X, XRechnung, EN 16931, KoSIT validation, GoBD, VAT, create via API/MCP/n8n/Make/Zapier, receive). Selected entry points: German e-invoicing mandate · ZUGFeRD, XRechnung and EN 16931 · validation checklist · create e-invoices via API & MCP.
The validator is the entry point for the free compliance check. For recurring generation: API/MCP with the same KoSIT accept gate.