E-Invoice Creation API
Generate Factur-X, ZUGFeRD, XRechnung, UBL and CII invoices from structured JSON. Totals and VAT computed automatically, every document validated against the official rules before it leaves the API.
Create
Build compliant e-invoices with PDF/A-3b conformance from structured data.
Create Factur-X
Build a Factur-X PDF/A-3b invoice from structured JSON input.
Create ZUGFeRD
Generate ZUGFeRD 2.x hybrid PDFs at all conformance levels.
Create XRechnung
Build XRechnung CII or UBL XML for German B2G submissions.
Create UBL
Generate EN 16931 compliant UBL 2.1 invoice XML.
Create CII
Generate UN/CEFACT Cross Industry Invoice D16B XML.
Why create e-invoices via API?
Validated before delivery
Every generated document passes its full official rule set before you receive it, and the stamped CustomizationID always matches the rules it was checked against. Bad input gets you rule-level findings, never a non-compliant file.
Totals and VAT computed
Send line items and the API derives the invoice totals and the per-rate VAT breakdown, allowances and charges included, exactly as the EN 16931 arithmetic rules demand.
Profiles and versions built in
Pick the CIUS per invoice: Peppol BIS 3.0 by default, or EN 16931, NLCIUS, EHF, XRechnung and PINT via options.profile. Rule updates and version transitions are handled server-side on the official effective dates.
Hybrid PDFs, your way
Factur-X and ZUGFeRD outputs are PDF/A-3 hybrids: use the built-in template (English, German or French, with your brand color) or supply your own PDF via options.pdfUrl and the API embeds the XML into it.
Frequently asked questions
Which e-invoice formats can I create with the API?
Factur-X and ZUGFeRD hybrid PDFs, XRechnung 3.0 in CII syntax, UBL 2.1 with selectable profiles (Peppol BIS 3.0 by default, plus EN 16931, NLCIUS, EHF, XRechnung and PINT), and standalone UN/CEFACT CII D16B.
Is the generated invoice validated before delivery?
Yes. Every document is validated against its full official rule set before it leaves the API, and the CustomizationID stamped into the document always matches the rules it was validated with. If the input cannot produce a compliant invoice, the API returns the violated rules as structured findings instead of a broken file.
Do I need to calculate totals and VAT myself?
No. The invoice totals and the VAT breakdown are computed from your line items, including allowances and charges, exactly as EN 16931 arithmetic rules require. You can still supply your own values to override the computed result.
Can the hybrid PDF use my own invoice design?
Yes. Supply options.pdfUrl and the API embeds the generated XML into your own PDF. Without it, the built-in template is used, localizable in English, German or French and brandable with your primary color.
What happens when a standard publishes new rules?
The validation artifacts are updated server-side and switched on the authority's official effective dates, so generated invoices keep passing without any integration change. Version transitions (such as a future XRechnung 4.0) follow a published lifecycle: opt-in during the transition window, default flip on the effective date, and the outgoing version pinnable until sunset.
Ready to automate your invoices?
Validate, convert and embed compliant e-invoices through one API. Start your 30-day free trial. No credit card required.