# Convert X12 810 to PDF Drop the X12 810 file and read it as an invoice: who billed whom, the lines, the tax and the total. An 810 is the invoice your US customer sends, and it looks like nothing until something renders it. Source: https://tally-stick.com/x12-810-to-pdf ## A US invoice a European desk can read A European supplier selling into the United States receives X12 where it issues EN 16931, so the same clerk meets two worlds in one week. The 810 is the one X12 transaction set that really is an invoice. That is why it prints with prices and an amount due, while an 850 or an 856 does not. ## What you get out - Buyer and supplier names and addresses from the N1 loops - Invoice number and date from BIG, with the purchase order it refers to - Line items from IT1 with quantity, unit, unit price and product identifiers - Charges and allowances, and tax from the TXI segments - The invoice total from TDS, checked against the sum of the lines ## Questions ### Does it need the ISA and GS envelope? The envelope is read when it is there and the file is refused when the ISA is missing, because without it the separators are a guess. A single transaction set inside a full interchange is the normal case and works. ### Several 810s in one file? Each ST to SE transaction set is read as its own invoice, so an interchange holding a batch gives you each of them rather than the first one only. ### What about an 812 adjustment? It is recognised and titled as a credit or debit adjustment rather than as an invoice, so a document that moves money back is not filed as one that asks for it. ## Related - [EDI 810 to Excel](https://tally-stick.com/x12-810-to-excel) - [X12 850 to PDF](https://tally-stick.com/x12-850-to-pdf) - [X12 820 to PDF](https://tally-stick.com/x12-820-to-pdf) - [EDIFACT INVOIC to PDF](https://tally-stick.com/edifact-invoic-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.