# X12 Order-to-Cash Transaction Sets Reference

> Source: https://netray.co/tools/x12-order-to-cash-transaction-sets-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A lookup table of the X12 transaction sets that touch quoting, ordering, shipping, invoicing and payment, with who sends what.

## Category

supply-chain

## Audience

- Customer service
- EDI analyst
- Sales operations

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Set

**Key:** set

**Type:** text

#### Transaction set name

**Key:** name

**Type:** text

#### Typical sender to receiver

**Key:** flow

**Type:** text

#### Order management use

**Key:** use

**Type:** text

**Rows:**

#### Request for Quotation

**Set:** 840

**Flow:** Buyer to seller

**Use:** Customer asks for a price and lead time

#### Response to Request for Quotation

**Set:** 843

**Flow:** Seller to buyer

**Use:** Your quote back to the customer

#### Purchase Order

**Set:** 850

**Flow:** Buyer to seller

**Use:** New customer order; becomes your sales order

#### Purchase Order Acknowledgment

**Set:** 855

**Flow:** Seller to buyer

**Use:** Confirms acceptance, dates and any changes

#### Purchase Order Change Request, Buyer Initiated

**Set:** 860

**Flow:** Buyer to seller

**Use:** Customer changes quantity, date or price

#### Purchase Order Change Acknowledgment/Request, Seller Initiated

**Set:** 865

**Flow:** Seller to buyer

**Use:** Your response to a change or your own change

#### Planning Schedule with Release Capability

**Set:** 830

**Flow:** Buyer to seller

**Use:** Forecast and planning releases

#### Shipping Schedule

**Set:** 862

**Flow:** Buyer to seller

**Use:** Firm release schedule against a blanket order

#### Ship Notice/Manifest

**Set:** 856

**Flow:** Seller to buyer

**Use:** Advance ship notice with packing detail

#### Invoice

**Set:** 810

**Flow:** Seller to buyer

**Use:** Electronic invoice for shipped goods

#### Payment Order/Remittance Advice

**Set:** 820

**Flow:** Buyer to seller

**Use:** Payment and remittance detail for cash application

#### Receiving Advice/Acceptance Certificate

**Set:** 861

**Flow:** Buyer to seller

**Use:** Customer confirms what was received

#### Order Status Inquiry

**Set:** 869

**Flow:** Buyer to seller

**Use:** Customer asks where an order stands

#### Order Status Report

**Set:** 870

**Flow:** Seller to buyer

**Use:** Your answer to a status inquiry

#### Inventory Inquiry/Advice

**Set:** 846

**Flow:** Either

**Use:** Stock levels shared with customers or distributors

#### Product Activity Data

**Set:** 852

**Flow:** Reseller to supplier

**Use:** Sales and stock data from distributors

#### Price/Sales Catalog

**Set:** 832

**Flow:** Seller to buyer

**Use:** Price list and catalog updates

#### Return Merchandise Authorization and Notification

**Set:** 180

**Flow:** Either

**Use:** Return authorization data

#### Application Advice

**Set:** 824

**Flow:** Receiver to sender

**Use:** Business-level error or acceptance notice

#### Functional Acknowledgment

**Set:** 997

**Flow:** Receiver to sender

**Use:** Syntax-level receipt confirmation

#### Warehouse Shipping Order

**Set:** 940

**Flow:** Depositor to warehouse

**Use:** Instruct a 3PL to ship

#### Warehouse Shipping Advice

**Set:** 945

**Flow:** Warehouse to depositor

**Use:** 3PL confirms what shipped

#### Motor Carrier Load Tender

**Set:** 204

**Flow:** Shipper to carrier

**Use:** Tender a truckload or LTL shipment

#### Transportation Carrier Shipment Status Message

**Set:** 214

**Flow:** Carrier to shipper

**Use:** Tracking events for customer status answers

**Notes:** Flow shows the usual direction in a buyer and seller relationship. Individual partners may use sets differently, so confirm in the trading partner guide.

## Content

**Intro:** Order management EDI is a handful of numbered documents that mirror the paper flow: quote, order, acknowledgment, change, ship notice, invoice and payment. This table lists the sets customer service teams run into most.

**Sections:**

#### How to use it

**Body:** Search by number or by what you are trying to do, such as 'change' or 'status'. Each row gives the official set name, who normally sends it and how it appears in the order desk workflow. Print or export it to keep next to the order entry screen.

#### The core order loop

**Body:** The loop is 850 in, 855 out, then 860 and 865 for changes, 856 when goods ship, 810 for the invoice and 820 for payment. If your partner uses planning releases, an 830 or 862 replaces repeated 850s against a blanket order. Knowing which set carries a given fact tells you where to look when a customer disputes it.

#### Status inquiries and acknowledgments

**Body:** The 869 and 870 pair is the formal way to ask for and report order status, but many partners never implement it and rely on the 855 and 856. The 997 only proves a file was received. The 824 is the one that reports business-level problems such as an unknown part or an invalid ship-to.

#### Common mistakes

**Body:** Teams often treat a 997 as order acceptance, process an 860 without sending a 865 back, or forget that an 856 normally has to arrive before the goods do. Agree acknowledgment time limits and change cut-off rules with each customer in writing.

**Cta:** If your team re-keys EDI orders because mapping is incomplete, we can look at where AI-assisted extraction and ERP integration would help. The reference stands alone.

**Faq:**

#### What EDI documents are used in order management?

**Answer:** The usual set is 850 purchase order, 855 acknowledgment, 860 and 865 change messages, 856 ship notice, 810 invoice and 820 remittance. Planning customers add 830 and 862, and status-focused partners add 869 and 870.

#### What is the difference between EDI 860 and 865?

**Answer:** An 860 is a change request initiated by the buyer. An 865 is initiated by the seller, either to request a change or to respond to an 860, stating what was accepted or rejected.

#### What is EDI 870 used for?

**Answer:** The 870 Order Status Report is the seller's reply to an 869 Order Status Inquiry. It reports status and dates at order or line level without sending a new acknowledgment.

#### Do all customers use every set?

**Answer:** No. Most customers use between three and six sets. Each partner publishes a guide listing the sets, versions and required segments they actually accept.

## Search terms

edi transaction codes list, x12 850 855 856 810 list, edi 860 vs 865, edi 870 order status report, edi transaction set numbers meaning, edi order to cash documents, edi 940 945 warehouse

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json