# Convert CII to PDF

Drop the CII XML and read the invoice as a document: parties, line items, VAT per rate and the totals, typeset from the data rather than captured from a screen. A bare CII file has no picture of itself.

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

## The syntax with no picture of its own

CII is the second syntax EN 16931 allows, and the one sitting inside every ZUGFeRD and Factur-X PDF. Those arrive with a visual layer their sender designed. A CII file on its own does not, which is why people so often cannot open it. This page draws the picture from the data.

## What you get out

- Seller and buyer trade parties with their registered identifiers
- Document number, issue date and the document type code
- Line items with quantity, unit, unit price and net amount
- Tax breakdown per rate with the basis amount
- Settlement terms and payment means where present

## Questions

### Which CII version is read?

D16B, the version EN 16931, ZUGFeRD 2.x and Factur-X all build on. ZUGFeRD 1.0 files are read as well.

### A credit note came in as CII. Will it say invoice?

No. Type code 381 is read as a credit note and the PDF is titled accordingly, because a document that reverses money should not be filed as one that asks for it.

### Can I get the same data as a spreadsheet?

Yes, the CII to Excel page writes the same document as rows, and every converter here offers Excel, CSV, JSON and PDF from the one file you dropped.

## Related

- [CII to Excel](https://tally-stick.com/cii-to-excel)
- [XRechnung to PDF](https://tally-stick.com/xrechnung-to-pdf)
- [UBL invoice to PDF](https://tally-stick.com/ubl-invoice-to-pdf)
- [Peppol BIS to PDF](https://tally-stick.com/peppol-bis-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.