# Convert X12 850 to PDF

An 850 tells you what a customer wants, at what price, by when. Drop it here and read the order as a document, before anyone ships against it or invoices it.

Source: https://tally-stick.com/x12-850-to-pdf

## An order is not an invoice

The 850 is a purchase order, and the PDF says so on the masthead: titled as an order, with an order number, not an invoice number. That distinction is the whole point. A purchase order dressed as an invoice is a document somebody can pay by mistake, so the writer reads the transaction set before it chooses its labels.

## What you get out

- Buyer and vendor from the N1 loops, with the ship-to party when present
- Purchase order number and date from BEG
- Ordered lines from PO1 with quantity, unit, unit price and product identifiers
- Requested dates from DTM, and terms from ITD where the order carries them
- The order total where the message states one

## Questions

### Will this look like an invoice?

No. It is titled Purchase order and numbered as one. Nothing in the layout claims money is due, because on an order none is.

### Can I check it against the invoice that follows?

That is the usual reason to open one. Read the 850 here and the matching 810 on its own page, and the line quantities and prices sit in the same places on both.

### Is an 855 acknowledgement handled?

It is recognised and titled as a PO acknowledgement. The same rule applies: the document is named for what it is.

## Related

- [EDI 850 to Excel](https://tally-stick.com/x12-850-to-excel)
- [X12 856 to PDF](https://tally-stick.com/x12-856-to-pdf)
- [X12 810 to PDF](https://tally-stick.com/x12-810-to-pdf)
- [X12 820 to PDF](https://tally-stick.com/x12-820-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.