# Convert an EDI 850 purchase order to Excel

The 850 is the order your American customer sends you, and it is the one that has to be right before anything ships. Drop it here and read it as a table.

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

## The order comes in, the invoice goes out

European suppliers issue their own invoices, so the inbound American documents that hurt are the order, the ship notice and the remittance rather than the 810. The 850 opens that sequence: line items, quantities, requested dates and ship-to addresses, in a syntax nobody outside the trade reads comfortably. In rows, it can be checked against what you can actually deliver.

## What you get out

- BEG purchase order number, type and date
- N1 loop parties, including ship-to and bill-to with their codes
- PO1 line items with quantity, unit price and product identifiers
- DTM requested and delivery dates, plus PER contacts
- All remaining segments element by element, unaltered

## Questions

### Is a purchase order an invoice?

No, and it is not treated as one. The totals check does not apply, and the export keeps the order fields rather than pretending there is a VAT breakdown.

### Can I compare it with the invoice I sent?

Not automatically yet. Export both to Excel and the comparison is a formula away. Matching documents against each other is on the paid roadmap.

### Are 856 and 820 handled too?

Yes, both, each with its own page.

## Related

- [EDI 856 to Excel](https://tally-stick.com/x12-856-to-excel)
- [EDI 810 to Excel](https://tally-stick.com/x12-810-to-excel)
- [EDI 820 to Excel](https://tally-stick.com/x12-820-to-excel)
- [EDIFACT INVOIC to Excel](https://tally-stick.com/edifact-invoic-to-excel)

## 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.