Skip to content

X12 transaction code

X12 850 Purchase Order

X12 850 Purchase Order: explore its business purpose, mapping identifiers, validation tests and 389 partner references across 516 listed channels.

Standard
X12
Code
850
Partner references
389
Book an EDI demo ← All trading partners

Implementation guide

X12 850 mapping and validation

X12 850 Purchase Order is used when a buyer places an order. Preserve buyer purchase order, order line and trading-party identifiers so the purchase order or sales order in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • Define which combination of buyer purchase order, order line and trading-party identifiers identifies one business record, its lines and any later revision.
Update the receiving system Processing the purchase order or sales order

ID assigned by the receiving system and processing result
  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
Check the processing result Processing status for the purchase order or sales order

Original document reference and matching response
  • Reconcile the purchase order or sales order with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a buyer places an order. Name the operational owner of the purchase order or sales order and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map buyer purchase order, order line and trading-party identifiers. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic purchase order or sales order data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful purchase order or sales order processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 850 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic purchase order or sales order data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out purchase order or sales order without processing it twice.

Document structure

X12 850 Purchase Order at the element level

The X12 850 reference contains 71 segment entries and 282 data elements; 84 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
71
Data elements
282
Mandatory elements
84
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BEG 5 4
CUR 5 2
REF 3 1
FOB 7 1
SAC 11 1
DTM 4 1
PID 4 1
TXI 8 1
N9 3 1
MSG 2 1
Key identifiers in 850
  • Transaction Set Purpose Code
  • Purchase Order Type Code
  • Purchase Order Number
  • Date
  • Entity Identifier Code
  • Currency Code
  • Reference Identification Qualifier
  • Shipment Method of Payment

Find your trading partner for X12 850

389 partners, 516 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 850 Purchase Order appears in this catalog

The largest groups of classified 850 catalog entries are in retail, grocery & food and apparel & footwear.

By industry

  • retail 92 channels
  • grocery & food 83 channels
  • apparel & footwear 68 channels
  • building & hardware 62 channels
  • furniture & home 45 channels
  • healthcare & pharma 35 channels

By network

  • SPS Commerce 92 channels
  • Epicor Eclipse 44 channels
  • TrueCommerce 27 channels
  • Rithum 25 channels
  • Logicbroker 9 channels
  • iTradeNetwork 8 channels
Partner entries with the most listed channels

FAQ

X12 850 questions

What is X12 850 Purchase Order used for?

850 is used when a buyer places an order. It carries information for the purchase order or sales order. Match it to your business system using buyer purchase order, order line and trading-party identifiers.

Which partners list X12 850?

The directory on this page links 389 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 850?

Start with buyer purchase order, order line and trading-party identifiers and the target purchase order or sales order. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 850 error handling?

Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 850 relate to other EDI messages?

X12 855 Purchase Order Acknowledgment; X12 856 Ship Notice Manifest; X12 810 Invoice; X12 860 Purchase Order Change Request Buyer Initiated are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 850 and 855?

850 is used when a buyer places an order. 855 is used when a seller responds to an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

What is the difference between 850 and 810?

850 is used when a buyer places an order. 810 is used when a bill is ready for the buyer to process. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform