PDF vs e-invoice
Why a PDF is not an e-invoice (and what counts instead)
A normal PDF is not an e-invoice. A valid e-invoice must comply with the European standard EN 16931 and contain structured data — either as a hybrid (ZUGFeRD/Factur-X with embedded XML) or pure XML (XRechnung). PDF-only files count as "other invoices" during the transition period and do not meet the requirements for receiving structured e-invoices.
Why PDF-only is not sufficient
Structured data mandate: EN 16931 requires machine-readable details on parties, line items, VAT rates, payment terms etc. A plain PDF does not provide these in structured form. Receive obligation since 1 Jan 2025: Domestic German B2B must be able to receive and process structured e-invoices. Issuing from 2027: Phased by turnover. PDF will no longer suffice. Risks include VAT deduction issues and rejections.
Common e-invoice formats (short)
ZUGFeRD / Factur-X (hybrid): PDF/A-3b + embedded CII XML. For most B2B the most practical (COMFORT / EN 16931 / EXTENDED). XRechnung: Pure XML, primarily mandated for B2G. MINIMUM/BASIC-WL do not meet the obligation.
What fakturai checks (KoSIT-Accept-Gate)
Generates ZUGFeRD/Factur-X and validates before delivery: XSD + Mustang + veraPDF + official KoSIT ACCEPT. For existing invoices use the free validator.
What fakturai does not replace (GHOA-1671)
The substantive and tax correctness of the invoice remains fully with the issuer. No accounting/ERP functions, no tax or legal advice, no complete GoBD archival process beyond the file format. No hard guarantees or financial promises.