Invoice Format Conversion Matrix: Every Supported Source and Target Path
This page lists every conversion path this tool supports. Use it to find your source format, confirm the available targets, and then open the converter to run the conversion. Each path description explains what the converter preserves and what you should check in the output.
Conversion Matrix at a Glance
A filled cell means the conversion is supported. Each row is a source format; each column is a target format.
UBL 2.1 as Source — 5 Target Formats
UBL is the most flexible source format in this tool. Starting from a valid UBL 2.1 file you can reach five different targets, covering Italy, France, Poland, and readable output:
UBL → Factur-X
The converter extracts all EN 16931 fields from UBL and writes a CII XML file, then embeds it in a PDF/A-3 envelope. The output uses the EN 16931 Factur-X profile by default. Use this path when your French or German trading partner expects a PDF with embedded data. Check that the resulting PDF renders correctly if the buyer reads it manually.
UBL → FatturaPA
Maps UBL party identifiers (BT-31, BT-48) to Italian CodiceFiscale and IdFiscaleIVA fields. EN 16931 VAT category codes are converted to FatturaPA natura codes. The output is ready for SDI submission. Verify that the CodiceDestinatario or PEC field in your source data is populated — the converter cannot generate a routing code that does not exist in UBL.
UBL → Human Readable PDF
Generates a clean, print-ready PDF from the UBL data. No embedded XML. This output is for operational use — sending to a partner who cannot process XML, attaching to an email, or keeping a readable archive copy. It carries no legal force in jurisdictions that require structured format submission.
UBL → CII
Produces a UN/CEFACT CII XML file. The field mapping follows the official EN 16931 UBL-to-CII equivalence tables. Use this path when the receiving system processes CII rather than UBL, or when you need the CII XML layer independently from a Factur-X file.
UBL → SKEF
Maps UBL fields to Poland's KSeF FA(2) schema. EN 16931 VAT categories are converted to Polish stawkaPodatku codes. NIP numbers are extracted from the UBL VAT identifier fields. Use this path when a Polish entity requires KSeF-ready invoice files. The converter flags any mandatory KSeF fields that your UBL source did not include.
FatturaPA as Source — 3 Target Formats
FatturaPA → CII
Maps Italian XML structure to UN/CEFACT CII. Natura codes are converted to EN 16931 VAT categories. Party identifiers are reformatted to CII BuyerTradeParty / SellerTradeParty elements. Use this path when the downstream system or partner expects CII, or as a stepping stone before converting to UBL.
FatturaPA → UBL 2.1
Full field-by-field mapping from FatturaPA to UBL including VAT nature codes, party legal identifiers, payment terms, and line items. The output is EN 16931-compliant UBL suitable for Peppol delivery or further conversion. This is the most common path for teams processing Italian supplier invoices in a non-Italian ERP.
FatturaPA → Human Readable PDF
Renders the FatturaPA content as a clean, readable PDF. Useful when a non-Italian recipient needs to review the invoice visually without accessing the Italian SDI system.
Factur-X as Source — 2 Target Formats
Factur-X → FatturaPA
Extracts the embedded CII XML from the PDF, then maps CII fields to FatturaPA. The PDF wrapper is discarded. Use this path when a French supplier invoice needs to be rerouted through the Italian SDI for a cross-border transaction involving an Italian buyer.
Factur-X → UBL 2.1
Extracts the CII XML from the Factur-X PDF and converts to UBL. The result is a standalone UBL file ready for Peppol delivery or ERP import. This is the recommended path for processing incoming French invoices in a pan-European procurement workflow.
CII as Source — 3 Target Formats
CII → FatturaPA
Maps UN/CEFACT CII fields to the Italian FatturaPA schema. VAT categories, party IDs, and amount fields are all remapped. Use when a CII-producing system needs to deliver invoices to Italian buyers via SDI.
CII → UBL 2.1
Converts CII to UBL following EN 16931 equivalence tables. Produces a Peppol-ready UBL file. Use when you receive CII invoices from a trading partner and need to import them into a UBL-native ERP or send them on via Peppol.
CII → Human Readable PDF
Generates a readable PDF from the CII data. Same use case as UBL-to-PDF: for human review, archiving, or emailing to partners who cannot consume XML.
What to Check After Every Conversion
- Invoice totals: net amount, VAT amount, and payable amount must match the source exactly
- Line count: the output must contain the same number of lines as the source
- Party identifiers: VAT numbers, company IDs, and routing codes must not be truncated
- VAT categories: check that standard-rate lines are coded S and reverse-charge lines are coded AE in UBL targets
- Dates: confirm issue date and due date are in YYYY-MM-DD format in XML targets
Start Converting
Open the Invoice Format Converter, upload your source file, and select the target format. For format-specific field details, see the pages below.
- European eInvoicing Overview
- EN 16931 — semantic model and mandatory fields
- Peppol BIS 3.0 — validation and identifiers
- Country formats — Italy, Germany, France, Poland
- implementation-guide — onboarding steps for ERP/accounting teams