Supply Chain & InventoryFree referencePDF, Excel, Word export

EDI Transaction Set Reference: 850, 855, 856, 810, 997, 940, 945 and More

X12 is the dominant EDI standard in North America, and every document type has a three-digit transaction set number. This searchable table lists the ones EDI coordinators meet most often, with the GS01 code and the segments that carry the data.

Download:

Set	Transaction set name	GS01	Typical direction	Key segments	Typical use
810	Invoice	IN	Seller to buyer	BIG, N1, ITD, IT1, TDS, CTT	Bill for goods or services shipped
812	Credit/Debit Adjustment	CD	Either	CDD, N1, REF	Adjust a prior invoice price or quantity
820	Payment Order/Remittance Advice	RA	Buyer to seller or bank	BPR, TRN, RMR, ENT	Payment and remittance detail
824	Application Advice	AG	Receiver to sender	BGN, OTI, TED	Business-level acceptance or error report
830	Planning Schedule with Release Capability	PS	Buyer to seller	BFR, LIN, FST, SDP	Forecast and material release schedule
832	Price/Sales Catalog	SC	Seller to buyer	BCT, LIN, CTP	Send item and price catalog
846	Inventory Inquiry/Advice	IB	Seller or 3PL to buyer	BIA, LIN, QTY	Report on-hand or available inventory
850	Purchase Order	PO	Buyer to seller	BEG, N1, PO1, PID, CTT	Place an order for goods
855	Purchase Order Acknowledgment	PR	Seller to buyer	BAK, PO1, ACK, CTT	Accept, change or reject a PO
856	Ship Notice/Manifest (ASN)	SH	Seller to buyer	BSN, HL, SN1, TD1, MAN	Describe a shipment and its packaging
860	Purchase Order Change Request (Buyer)	PC	Buyer to seller	BCH, POC, N1	Change an existing PO
861	Receiving Advice/Acceptance Certificate	RC	Buyer to seller	BRA, RCD	Confirm what was received
862	Shipping Schedule	SS	Buyer to seller	BSS, LIN, SDP, FST	Short-term just-in-time shipping releases
865	Purchase Order Change Acknowledgment (Seller)	CA	Seller to buyer	BCA, POC, ACK	Respond to a PO change
875	Grocery Products Purchase Order	OG	Buyer to seller	G50, G51, G53	Grocery PO with grocery-specific segments
880	Grocery Products Invoice	GI	Seller to buyer	G01, G02, G22	Grocery invoice
940	Warehouse Shipping Order	OW	Owner to warehouse or 3PL	W05, N1, W01, W76	Instruct a warehouse to pick and ship
943	Warehouse Stock Transfer Shipment Advice	AR	Shipping warehouse to receiving	W06, W01, W03	Advise of a transfer between warehouses
944	Warehouse Stock Transfer Receipt Advice	RE	Receiving warehouse to owner	W17, W07, W14	Confirm receipt of a transfer
945	Warehouse Shipping Advice	SW	Warehouse or 3PL to owner	W06, N1, W12, W03	Confirm what the warehouse shipped
947	Warehouse Inventory Adjustment Advice	AW	Warehouse to owner	W15, W19	Report adjustments such as damage or counts
997	Functional Acknowledgment	FA	Receiver to sender	AK1, AK2, AK5, AK9	Confirm syntactic receipt of a functional group
999	Implementation Acknowledgment	FA	Receiver to sender	AK1, AK2, IK3, IK4, IK5, AK9	Detailed syntax acknowledgment, often for HIPAA
204	Motor Carrier Load Tender	SM	Shipper to carrier	B2, S5, N1, L11	Tender a load to a truckload carrier
210	Motor Carrier Freight Details and Invoice	IM	Carrier to shipper	B3, N1, LX, L1	Freight bill
214	Transportation Carrier Shipment Status Message	QM	Carrier to shipper	B10, L11, AT7	Tracking status events

Segment lists show the principal business segments, not every segment in the standard. Direction is typical, not mandatory. GS01 codes are the functional identifier codes used in the GS segment. Confirm versions (004010, 005010) and mandatory segments in your trading partner's implementation guide.

Map your EDI documents to your ERP

Optional: share your document list and we can outline how each one maps to your ERP tables and APIs.

Optional. The tool and every export work without this. No spam.

How to use the reference

Type a set number or a word such as invoice, ship notice or warehouse into the search box to filter the table. Use the GS01 column when you configure functional groups: the GS segment's first element must match the transaction set, so an 856 goes in a group with GS01 of SH and an 810 in a group with GS01 of IN. Export the table to Excel to paste into an onboarding document or a partner spec.

The core order-to-cash flow

A typical manufacturing or distribution flow starts with the buyer's 850 purchase order. The seller replies with an 855 acknowledgment, ships the goods and sends an 856 advance ship notice, then bills with an 810 invoice. Every document should be answered by a 997 functional acknowledgment at the technical level. Warehouse flows add the 940 shipping order and the 945 shipping advice between the owner and a third-party logistics provider, and inventory visibility uses the 846.

850, 855, 860, 865: order and change cycle
856, 861: shipment and receipt
810, 812, 820: invoice, adjustment and payment
940, 943, 944, 945, 947: warehouse and 3PL exchange

997 versus 999 and other cautions

The 997 confirms that a functional group was received and passed or failed syntax checks. The 999 is a richer implementation acknowledgment used widely in healthcare, with segment and element level error detail. Neither confirms that the business content was accepted: that is the job of the 824 application advice or the 855. Treat version differences carefully, because 004010 and 005010 differ in segments, element lengths and code lists for the same set number.

Frequently Asked Questions

What do 850, 855, 856 and 810 stand for?

850 is the purchase order, 855 is the purchase order acknowledgment, 856 is the advance ship notice (ship notice/manifest), and 810 is the invoice. Together they cover the main order-to-cash exchange between a buyer and a seller.

What are the 940 and 945 used for?

The 940 is the warehouse shipping order sent to a warehouse or 3PL to pick and ship goods. The 945 is the warehouse shipping advice the warehouse returns to confirm what actually shipped, including quantities and tracking details.

Is the 997 an acknowledgment of the order?

No. It only confirms that the EDI file was received and checked for syntax. It does not say the buyer accepted the order. Business acceptance is conveyed by an 855 or an 824 application advice.

Which X12 version should I use?

Use whatever your trading partner's guide specifies. 004010 remains very common in retail and manufacturing, while 005010 is mandatory in US healthcare. Version affects segments, lengths and code lists, so do not assume maps are interchangeable.

If you are mapping these documents into SAP, Oracle, Infor, Epicor or Dynamics, we can help build and test the maps against live ERP data.

Talk to an Expert Explore More Free Tools

Related Tools

Supply Chain & Inventory

More Supply Chain & Inventory tools

See all

Back to All Tools