X12 transaction code
X12 857 Shipment And Billing Notice
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 857
- Trading partners
- 3
Specification summary
X12 857 Shipment And Billing Notice at the element level
The X12 857 specification defines 39 segments carrying 112 data elements, 48 of which are mandatory.
- Segments
- 39
- Data elements
- 112
- Mandatory elements
- 48
| Segment | Elements | Mandatory |
|---|---|---|
| BHT | 6 | 2 |
| HL | 3 | 2 |
| FOB | 4 | 1 |
| DTM | 2 | 1 |
| N9 | 3 | 1 |
| PER | 8 | 1 |
| CUR | 2 | 2 |
| N1 | 4 | 1 |
| TDS | 1 | 1 |
| SAC | 4 | 1 |
- Hierarchical Structure Code
- Transaction Set Purpose Code
- Hierarchical ID Number
- Hierarchical Level Code
- Shipment Method of Payment
- Date/Time Qualifier
- Reference Identification Qualifier
- Contact Function Code
Trading partners that support X12 857
3 partners, 3 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 857 Shipment And Billing Notice
857 is used most heavily in retail and grocery & food.
The 857 consolidates the shipment detail of an 856 and the billing detail of an 810 into one document, giving the recipient data for both receipt planning and payment generation. X12 intends it to replace both documents together, never one of them alone, and notes it is not appropriate in Evaluated Receipts Settlement environments where prices are predetermined. Adoption is narrow and concentrated in grocery and wholesale distribution. Sent by the supplier to the buyer, typically a grocery retailer or wholesaler, covering both the delivery notice and the invoice for a shipment. A supplier ship-confirms an order and issues a single document at shipment that serves as both the ship notice and the invoice.
By industry
- retail 2 channels
- grocery & food 1 channel
By network
- SPS Commerce 1 channel
FAQ
X12 857 questions
What is X12 857 Shipment And Billing Notice?
X12 857 (Shipment And Billing Notice) is an EDI transaction set defined by ANSI ASC X12 for exchanging shipment and billing notice between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 3 Stacksync trading partners support this code across 3 channels.
Which trading partners use X12 857?
3 Stacksync partners accept X12 857: Barnes & Noble, Cabela's, Stater Bros. Markets. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 857 with my ERP?
Stacksync handles the full X12 857 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
