How to create a private client-side ZUGFeRD 2.2 EN 16931 e-invoice
A hybrid e-invoice wraps a human-readable PDF/A-3b page and a machine-readable XML file into a single .pdf download. Your browser builds both layers inside a Web Worker with 0 bytes sent over the network, making it easy to create a compliant bill (E-Rechnung erstellen) without exposing client financials.
Developed jointly by German and French forums, the FNFE-MPE Factur-X and ZUGFeRD 2 Specification defines identical schemas and profile rules under both names. For domestic German billing without embedded XML requirements, you can also create German EUR invoices with 19% or 7% USt using the same local workspace.
Embedding factur-x.xml with AFRelationship Alternative metadata
During export, the generator embeds factur-x.xml (formatted in UN/CEFACT CII D16B) with an AFRelationship value of Alternative and writes the urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0# XMP extension schema. Automated ERP importers inspect that XMP block to extract structured totals without OCR.
Why human readers and ERP systems see identical totals
Because the PDF layout and the XML tree render from the exact same BusinessDoc state, line quantities, net subtotals, and VAT amounts never drift apart. Clients without e-invoice software still open a clean invoice in any PDF viewer.
Traditional invoicing workflows that attach a separate XML file next to a manually typed PDF often suffer from mismatched invoice dates or rounding differences. Embedding factur-x.xml directly inside the PDF/A-3b container eliminates that split-file risk permanently.
ZUGFeRD PDF/A-3 vs XRechnung XML comparison for B2B and B2G
Choosing between a hybrid PDF and pure XML depends on whether your buyer is a private company or a public agency. Under the Library of Congress PDF/A-3 (ISO 19005-3) specification, PDF/A-3b preserves visual appearance while carrying attached XML data.
German federal and state agencies often demand pure XRechnung 3.0 XML for public portals routed by a Leitweg-ID, whereas commercial B2B buyers in Germany and France widely prefer hybrid PDF/A-3 files sent by email. Knowing which format your recipient’s accounting intake expects avoids delayed payment cycles.
| E-invoice format | File extension | Visual PDF included | Underlying XML | Best suited for |
|---|---|---|---|---|
| ZUGFeRD 2 / Factur-X | .pdf (PDF/A-3b) |
Yes | UN/CEFACT CII D16B | German and French B2B billing |
| XRechnung (CII) | .xml |
No | UN/CEFACT CII D16B | German B2G portals (ZRE, OZG-RE) |
| XRechnung (UBL) | .xml |
No | OASIS UBL 2.1 | German B2G and Peppol-connected buyers |
| Peppol BIS 3.0 | .xml |
No | OASIS UBL 2.1 | EU and Belgian Peppol networks |
| Standard PDF invoice | .pdf |
Yes | None | Non-mandated B2C or local receipts |
Why are net prices required on ZUGFeRD line items?
EN 16931 calculates tax at the VAT-category summary level rather than summing gross line items. Consequently, the Prices include VAT toggle stays disabled in e-invoice mode so line totals (BR-CO-10) and tax totals (BR-CO-14) match within a 0.01 currency tolerance.
Under the German VAT Act § 14 UStG, electronic invoices must accurately reflect net consideration, applicable tax rates, and seller identification. Once downloaded, you can verify embedded XML line items before emailing clients to confirm every field extracted cleanly.
Preventing rounding drift across EN 16931 VAT categories
When a user enters gross prices, reverse-calculating net unit amounts per row can introduce half-cent discrepancies against the invoice-level VAT sum. Entering net unit prices directly guarantees deterministic BR-S-09 tax math across every line item.
Inspecting the embedded XML and pre-download checklist
The live checklist beside the preview flags missing seller tax IDs (BR-S-02), missing payment terms (BR-CO-25), and invalid IBAN check digits under ISO 13616. Resolving red error badges before export prevents buyer accounting rejections.
Each warning names the exact EN 16931 business rule and points to the missing field, such as a due date or buyer street address. Fixing those items takes seconds and saves days of back-and-forth with a client’s accounts payable team.
Tip: Always test-open your first hybrid PDF in an e-invoice viewer to confirm your buyer’s accounting system can read both the visual PDF and the attached
factur-x.xml.
Small-business VAT rules and compliance boundaries
Even businesses exempt from charging VAT may need to issue structured e-invoices when billing commercial buyers. Under the German VAT Act § 19 UStG small-business exemption, qualifying small businesses omit VAT and state the statutory exemption reason on the invoice.
Understanding how exemption categories interact with EU cross-border reverse-charge rules helps prevent automated accounting holds. Always keep your local PDF/A-3 archives backed up alongside your bookkeeping records for the full statutory retention period.
Handling VAT exemptions under § 19 UStG
When selecting a VAT-exempt category (E) or reverse-charge category (AE), EN 16931 requires an explicit exemption reason (BR-E-10 or BR-AE-10). Enter the statutory reference in the exemption note field so the XML passes category validation.
For German Kleinunternehmer invoices, citing § 19 UStG clearly inside the exemption note explains why no output tax is charged while keeping the factur-x.xml tax breakdown structurally valid for corporate buyers’ accounting software.
Informational scope versus certified tax advice
This generator builds PDF/A-3b files and runs common EN 16931 checks for operational convenience rather than certified tax, legal, or accounting advice. Because European e-invoicing timelines, archival rules, and VAT exemptions change periodically, verify your setup with a qualified accountant or tax authority. If you want a scannable SEPA payment code on standard PDFs, stamp SEPA GiroCode QR blocks onto PDF invoices.