# Convert a CII invoice to Excel

Drop a Cross Industry Invoice XML. The CII tree is mapped onto the same columns as UBL, so you do not have to learn two vocabularies for one invoice.

Source: https://tally-stick.com/cii-to-excel

## The other half of EN 16931

EN 16931 allows two syntaxes and CII is the second one, the UN/CEFACT Cross Industry Invoice at D16B. It is what sits inside every ZUGFeRD and Factur-X PDF, and what German and French senders often produce even when the file arrives on its own. Its element names look nothing like UBL's. That is the problem this page removes.

## What you get out

- ExchangedDocument header, including type code and issue date
- Seller and buyer trade parties with their tax registrations
- IncludedSupplyChainTradeLineItem detail, line by line
- ApplicableTradeTax per rate and category
- The monetary summation, down to due payable amount

## Questions

### Which CII version does it read?

D16B, which is the version EN 16931, ZUGFeRD 2.x and Factur-X all use. Older D-directories usually still map, since the element names in the invoice branch changed little.

### My file came out of a ZUGFeRD PDF. Same thing?

Yes, that attachment is CII. You can also drop the whole PDF and skip the extraction step.

### Why do CII and UBL exports look identical?

Because that is the point. Both syntaxes are mapped to one set of column names, so a supplier switching syntax does not break your spreadsheet.

## Related

- [Factur-X to Excel](https://tally-stick.com/factur-x-to-excel)
- [ZUGFeRD to Excel](https://tally-stick.com/zugferd-to-excel)
- [UBL to Excel](https://tally-stick.com/ubl-invoice-to-excel)
- [EDIFACT INVOIC to Excel](https://tally-stick.com/edifact-invoic-to-excel)
- [EN 16931 validator](https://tally-stick.com/en16931-validator)
- [CII to PDF](https://tally-stick.com/cii-to-pdf)

## How it works

The invoice is read on your own device. No file is uploaded, no account is required, and the fair usage limit is the only cap. Exports are PDF, Excel, CSV and JSON.