Technical Rules for European Invoice Conversion
Technical invoice conversion is not only a file-format change. A valid conversion must preserve the invoice meaning across parties, taxes, line items, totals, payment data, currency, and country-specific validation requirements. This page summarizes the checks used when reviewing UBL, CII, Factur-X, ZUGFeRD, FatturaPA, PDF, and SKEF/KSeF-oriented conversion flows.
Semantic Data Rules
The source and target documents should describe the same business transaction. Supplier identity, buyer identity, invoice number, issue date, taxable amounts, tax categories, totals, allowances, charges, and payment terms must be carried into the target format without changing their business meaning.
- Supplier and buyer names, addresses, tax identifiers, and electronic addresses should remain traceable.
- Invoice number, issue date, due date, currency, and document type should map to the closest target fields.
- Line quantity, unit price, tax category, discount, charge, and line total values should reconcile with totals.
- Missing mandatory target fields should be reported before the converted document is used in production.
Format Validation Rules
Each invoice syntax has a different XML structure and validation model. UBL and CII can both represent EN 16931 invoices, but their element names, nesting, and identifiers differ. FatturaPA has Italian platform-specific expectations, while Factur-X and ZUGFeRD combine a PDF document with embedded structured XML.
| Format | Key Technical Checks |
|---|---|
| UBL 2.1 | Invoice namespaces, party data, tax totals, monetary totals, line items, and Peppol/EN 16931 fields. |
| CII | Trade transaction structure, header agreement, settlement, tax breakdown, and line-level trade data. |
| FatturaPA | Italian XML schema, transmission data, fiscal identifiers, payment blocks, tax details, and attachments. |
| Factur-X / ZUGFeRD | PDF/A profile, embedded XML payload, profile level, document metadata, and human-readable consistency. |
| Readable layout, invoice totals, tax summaries, parties, line items, and download/archiving usability. |
Production Review Checklist
Before sending converted invoices to a tax platform, customer portal, Peppol access point, ERP system, or archive, the output should be reviewed for both machine validation and business readability.
- Run schema or platform validation where the target format provides official validation rules.
- Compare source and target totals, including tax bases, VAT amounts, payable amount, and rounding.
- Confirm that mandatory identifiers are present for the target country or exchange network.
- Check whether optional source data was preserved, dropped, or moved into notes or attachments.
- Keep a copy of the source invoice and converted output for support and audit review.
Important Limits
A successful technical conversion does not replace legal, tax, accounting, or customer acceptance checks. Users should verify converted invoices against their contractual requirements and the current rules of the receiving platform before using the output in a live workflow.