XML is complex
CII, UBL, EN16931, code lists, Schematron rules — the specification spans hundreds of pages. One wrong field and the invoice gets rejected.
Back to overview E-invoicing
E-invoicing mandate? One API call.
Generate ZUGFeRD PDFs, create XRechnung XML, embed invoice data into existing PDFs and validate. All EN16931-compliant, all through a single REST API.
1 credit per operation. 100 credits/month free.
Why e-invoicing drives developers crazy
The mandate is here
Since 2025, businesses in Germany must be able to receive e-invoices. From 2027, sending will gradually become mandatory too. No more workarounds.
Existing tools don't fit
Accounting software generates e-invoices only for its own invoices. If you need e-invoicing in your own software, you have to implement it yourself — or use an API.
E-invoicing in three variants
1
Generate ZUGFeRD PDF
Send invoice data as JSON, receive a PDF with embedded XML data. Visually readable for humans, machine-readable for software.
2
Generate XRechnung
Pure XML in CII or UBL format. For German public sector clients that don't accept PDF.
3
Validate & convert
Check existing e-invoices against EN16931. Convert between CII and UBL. Extract structured data from PDFs.
What you can do with it
Generate ZUGFeRD PDF
PDF/A-3 with embedded XML. All profiles: Minimum, Basic, Comfort, Extended.
XRechnung as XML
Standalone XRechnung in CII or UBL format. Compliant with the German specification.
Embed into existing PDFs
Take an existing invoice PDF and add ZUGFeRD XML data to it.
Validation
Check against EN16931 Schematron rules. Detailed error messages for violations.
CII ↔ UBL conversion
Switch between the two XML formats without data loss.
Extract invoice data
Read structured data from existing ZUGFeRD PDFs or XRechnung XMLs.
Perfect for
ERP & accounting software
Integrate e-invoice generation as a feature in your software without implementing the specification yourself.
Public sector contracts (B2G)
XRechnung is mandatory for invoices to federal, state and municipal authorities. One API call instead of weeks of implementation.
B2B invoice workflows
ZUGFeRD as the standard for invoice exchange between businesses. Automatic processing on the recipient side.
E-invoicing mandate: deadlines & formats
Exactly what applies to companies in Germany from 2025, 2027 and 2028 — with code samples for implementation.
Read the mandate in detailRelated glossary terms
Standards and formats directly related to this feature — explained concisely.
CII (Cross Industry Invoice)
UN/CEFACT XML syntax for invoices — one of the two accepted formats for EN 16931-compliant e-invoices and the technical foundation of ZUGFeRD.
EN 16931
European standard defining the semantic data model of electronic invoices — the shared foundation for XRechnung, Peppol BIS, ZUGFeRD and Factur-X.
Leitweg-ID
Unique recipient identifier for e-invoices to German public authorities — mandatory in field BT-10 of every B2G XRechnung.
Peppol Access Point
Certified service provider that delivers documents into the Peppol network or receives them — the technical gateway between your software and the European e-invoicing transport network.
Peppol
European network for standardised, cross-border exchange of business documents — primarily e-invoices — via accredited Access Points.
UBL (Universal Business Language)
OASIS XML standard for business documents — the second accepted syntax for EN 16931 e-invoices and the default format in the European Peppol network.
XRechnung
The German XML invoice standard and mandatory format for invoices to public-sector buyers (B2G) in Germany.
ZUGFeRD
A German-French hybrid e-invoice format: a PDF/A-3 document with an embedded machine-readable CII XML file.