What Is EDI 850 Purchase Order?
Also known as: X12 850, EDI purchase order, ORDERS
Definition
The EDI 850 is the ANSI X12 transaction set used to transmit a purchase order electronically from a buyer to a supplier, carrying header terms, ship-to and bill-to parties, and line item details such as quantity, price, and product identifiers.
EDI 850 Purchase Order Explained
The 850 is the document that starts the order-to-cash cycle in EDI. A buyer's purchasing system generates it, a translator formats and transmits it, and the supplier's system converts it into a sales order. Its EDIFACT counterpart is ORDERS. Because it initiates revenue and drives production scheduling, the 850 is usually the first transaction set a supplier implements and the one with the highest cost of error - a mis-mapped quantity or unit of measure becomes shipped product.
Structurally the transaction opens with a BEG segment carrying the purchase order type code, the buyer's PO number, and the PO date. Header-level segments follow: REF for reference identifiers such as contract or release numbers, PER for contact details, FOB for shipping terms, ITD for payment terms, DTM for requested delivery dates, and an N1 loop identifying parties by role - buying party, ship-to, bill-to - with N3 and N4 supplying address detail. Header-level notes appear in NTE or MSG segments.
Line detail lives in the PO1 loop. Each PO1 segment carries a line number, quantity, unit of measure, unit price, a basis of unit price code, and pairs of product identifier qualifier and value - buyer part number, vendor part number, UPC, or GTIN. Subordinate segments extend the line: PID for item description, SCH or DTM for line-level schedule and delivery dates, REF for line references, and SAC for allowances and charges. The transaction closes with CTT for line count and control totals, then SE.
The 850 rarely travels alone. A 997 functional acknowledgment confirms the interchange was syntactically valid. An 855 purchase order acknowledgment communicates business acceptance, rejection, or change at the line level. An 860 carries buyer-initiated changes to an existing order, and an 865 responds to them. A 856 advance ship notice precedes the shipment, and an 810 invoices it. Automotive and retail programs frequently add an 830 planning schedule or an 862 shipping schedule that behave as releases against a blanket order rather than discrete purchase orders.
Mapping into ERP is where implementations succeed or fail. The buyer's part number must resolve to an internal item, which requires a maintained customer part cross-reference. Unit of measure codes must translate to the ERP's units, since EA, PC, and CA can all mean pieces to different partners. Pricing must be reconciled against contract pricing with a documented tolerance and an exception path. Duplicate PO number handling, change order semantics, and whether a repeated 850 replaces or supplements an existing order all need explicit rules before go-live.
Why It Matters
- The 850 initiates revenue, so mapping errors flow straight into production, shipment, and invoice with real financial consequences.
- Customer part cross-references must be maintained in ERP or inbound orders fail, creating manual queues that defeat the purpose of EDI.
- Unit of measure and price mismatches are the most common causes of chargebacks and disputed invoices on large retail and automotive accounts.
- Change order handling through 860 documents determines whether the supplier ships the current requirement or an obsolete one.
In Practice
A repeat offender is price tolerance. A buyer sends an 850 at a price two cents below the contract price because their system rounds differently. Configure the integration to accept within a defined tolerance and post the difference for review, rather than either failing the order into an exception queue or silently accepting the buyer's price. Suppliers that fail the order lose a day of lead time; suppliers that accept silently erode margin across thousands of lines before anyone notices.
Frequently Asked Questions
What is the difference between an EDI 850 and an EDI 855?
The 850 is the buyer's purchase order requesting goods or services. The 855 is the supplier's purchase order acknowledgment, communicating whether the order is accepted as sent, accepted with changes, or rejected, generally line by line with reason codes. A 997 only confirms syntax was valid, so the 855 is the document that conveys actual business acceptance.
How does an EDI 850 become a sales order in ERP?
A translator parses the X12 envelope and transaction set, then a mapping converts each segment and element to ERP fields. Buyer part numbers resolve through a customer cross-reference table, unit of measure codes translate to internal units, and ship-to identifiers resolve to customer addresses. The mapped record posts through an ERP interface or API, with validation failures routed to a monitored exception queue.
Related Terms
EDI (Electronic Data Interchange)
EDI (Electronic Data Interchange) is the computer-to-computer exchange of business documents such as purchase orders, invoices, and shipping notices between trading partners in a standardized structured format, without human intervention.
Data Mapping
Data mapping is the process of defining how each field in a source system corresponds to a field in a target system, including the transformation rules, value translations, default values, and conditional logic needed to move data correctly between them.
Middleware
Middleware is software that sits between applications and handles the communication, transformation, routing, and reliability concerns of moving data between them, so that the applications themselves do not need to know about each other directly.
Go Deeper
AS9100 Audit Readiness Checklist
A 30-point checklist for AS9100 Rev D certification and surveillance audits, weighted toward the aerospace-specific requirements where auditors write the most findings.
Lot Traceability in Electronics Manufacturing
Lot traceability in electronics manufacturing explained: component-level genealogy, ERP lot control setup, IPC-1782 levels, recall readiness, and AI-driven trace.
Serialization Strategies for Defense Electronics
Electronics serialization compliance for defense: DFARS 252.211-7003 IUID, MIL-STD-130 marking, counterfeit-part traceability and ERP serial genealogy.
Working with EDI 850 Purchase Order in a live environment? Our engineers do this every day - and our AI agents automate most of it.
Try it here, free
X12 850 Purchase Order EDI Skeleton Generator
Builds a single-line ANSI X12 850 purchase order with ISA, GS, ST, BEG, N1 and PO1 segments you can use as a test file or mapping reference.
Keep exploring
Free tools
- X12 850 Purchase Order EDI Skeleton GeneratorBuilds a single-line ANSI X12 850 purchase order with ISA, GS, ST, BEG, N1 and PO1 segments you can use as a test file or mapping reference.
- EDI X12 850 Purchase Order Skeleton GeneratorFill in the partner IDs, PO number and one line item to generate a valid-looking X12 850 test message in 005010 format.
- EDI Transaction Set Reference (850, 855, 856, 810, 997, 940, 945)A searchable lookup of common X12 transaction sets with GS01 functional codes, typical direction and the segments that carry the business data.
ERP fixes and how-tos
- How to Set Up an EDI Trading Partner in Plex SystemsHow to configure a new EDI trading partner in Plex EDI Data Manager, map document types like 850, 830, 862, and 856, and test before going live.
- SyteLine EDI or BOD inbound document fails to create a sales orderWhy an inbound EDI order or ION BOD fails to create a SyteLine sales order, and how to trace the failure through the EDI error log or ION BOD inbox to the root cause.
Runs with your ERP
- Cleo Integration Cloud with SAP: EDI 850, 856 and 810How Cleo Integration Cloud connects trading partners to SAP S/4HANA and ECC for 850 orders, 856 ASNs and 810 invoices using IDocs and S/4HANA APIs.
- TrueCommerce EDI and Infor M3TrueCommerce managed EDI for Infor M3 (also VISUAL and other Infor ERPs): documents, data flows, setup steps, pitfalls, alternatives and where AI helps.
- TrueCommerce EDI and Oracle NetSuite: SuiteApp integration for trading partnersHow TrueCommerce EDI works with NetSuite as a SuiteApp using SuiteTalk: order-to-cash, procure-to-pay and 3PL flows, setup steps, pitfalls and alternatives.
Guides
- SyteLine EDI Transaction Sets: Configuring 850, 810 & 856Configure EDI transaction sets 850, 810, and 856 in Infor SyteLine. Step-by-step guide for purchase orders, invoices, and ASN documents with IDO mapping.
- EDI Transaction Sets Every Manufacturer Should KnowA manufacturer reference to EDI transaction sets: what 850, 855, 856, 810, 862, and 830 documents contain and how each maps into ERP order and shipping data.
- How to Fix SyteLine EDI Transaction RejectionsTroubleshoot SyteLine EDI transaction rejections including 'EDI validation failed' and mapping errors. Covers 850, 856, 810 document fixes and trading partner setup.