Use case · E-invoicing
One invoice. Two layers
Create one PDF/A-3 invoice for people and systems. The readable page carries an embedded XML payload targeting EN 16931 through ZUGFeRD or Factur-X.
Container model
The PDF and XML travel together
1b693d0a51d20bb1249b06ff63f8473810c5894e8adc3db9193518dacb219697Download PDFA ZUGFeRD or Factur-X invoice combines two layers inside one PDF/A-3 container.
- The PDF presents the invoice for a person to read.
- The embedded XML carries structured invoice data for a recipient system.
NextPDF Enterprise builds the attachment and container. The same engine renders the visible invoice.
The downloadable sample carries factur-x.xml, a CrossIndustryInvoice payload with the EN 16931 profile identifier. Business-rule and Schematron validation is a separate check you run with the recipient’s ruleset.
Profiles
Match the profile to the recipient
ZUGFeRD and Factur-X define the same profile family. The profile determines which structured invoice data the XML carries.
| Profile | Invoice lines | EN 16931 core |
|---|---|---|
| MinimumBooking and accounting aid | No | No |
| BasicInvoices with line items | Yes | Subset |
| EN 16931 (Comfort)EU core-invoice model | Yes | Full core |
| ExtendedCross-industry invoices | Yes | Superset (CIUS) |
Profiles per ZUGFeRD 2.x / Factur-X 1.0 include BASIC WL for document totals. NextPDF Enterprise targets these profiles; Minimum is a reduced booking aid, and acceptance of any invoice is the recipient validator's verdict.
Scope
Your data completes the invoice
NextPDF Enterprise produces output that targets the EN 16931 model and the named ZUGFeRD and Factur-X profiles.
Recipient acceptance depends on your invoice data, the requested profile, and the recipient’s validator. Those checks remain part of your workflow.
Build the invoice workflow
Review Enterprise for the hybrid container, or render the human-readable invoice in the free trial.