X12 transaction code
EDI 857 Shipment and Billing Notice (X12 857)
EDI 857 is the X12 Shipment and Billing Notice transaction set, used when shipment and billing details are transmitted together. The supplier sends the 857 to the buyer, typically a grocery retailer or wholesaler, as both the delivery notice and the invoice for a shipment.
- Standard
- X12
- Code
- 857
- Partner references
- 3
At a glance
EDI 857 at a glance
What the 857 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 857 Shipment and Billing Notice |
|---|---|
| Business record | Combined shipment and billing record |
| Who sends it to whom | The supplier sends the 857 to the buyer, typically a grocery retailer or wholesaler, as both the delivery notice and the invoice for a shipment. |
| When it is sent | A supplier ship-confirms an order and issues a single document at shipment that serves as both the ship notice and the invoice. |
| Match on | Shipment, invoice and order references |
| Partner references | 3 trading partners in this directory |
| Related documents | X12 850 Purchase Order, X12 856 Ship Notice/Manifest, X12 810 Invoice |
Key segments in an EDI 857
The business segments that appear in at least half of the 3 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BHT | Beginning of Hierarchical Transaction | To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time. | 3 of 3 |
| HL | Hierarchical Level | To identify dependencies among and the content of hierarchically related groups of data segments. | 3 of 3 |
| G05 | Total Shipment Information | To provide totals relating to the shipment. | 3 of 3 |
| DTM | Date/Time Reference | To specify pertinent dates and times. | 3 of 3 |
| N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 3 of 3 |
| N1 | Name | To identify a party by type of organization, name, and code. | 3 of 3 |
| TDS | Total Monetary Value Summary | To specify the total invoice discounts and amounts. | 3 of 3 |
| IT1 | Baseline Item Data (Invoice) | To specify the basic and most frequently used line item data for the invoice and related transactions. | 3 of 3 |
| TD5 | Carrier Details (Routing Sequence/Transit Time) | To specify the carrier and sequence of routing and provide transit time information. | 2 of 3 |
| MAN | Marks and Numbers | To indicate identifying marks and numbers for shipping containers. | 2 of 3 |
Stacksync connects EDI documents such as the X12 857 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 857 mapping and validation
X12 857 Shipment and Billing Notice is used when shipment and billing details are transmitted together. Preserve shipment, invoice and order references so the combined shipment and billing record 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.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | combined shipment and billing record shipment, invoice and order references |
|
| Update the receiving system | Processing the combined shipment and billing record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the combined shipment and billing record Original document reference and matching response |
|
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.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 856 Ship Notice/Manifest
shipment notice (ASN): an order ships, before the goods arrive.
- X12 810 Invoice
accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when shipment and billing details are transmitted together. Name the operational owner of the combined shipment and billing record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map shipment, invoice and order references. 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.
-
Test failures before launch
Run the failure cases in the mapping table against realistic combined shipment and billing record data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful combined shipment and billing record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 857 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic combined shipment and billing record 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 combined shipment and billing record without processing it twice.
Document structure
X12 857 Shipment and Billing Notice at the element level
The X12 857 reference contains 39 segment entries and 112 data elements; 48 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 857
3 partners, 3 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 857 Shipment and Billing Notice appears in this catalog
The largest groups of classified 857 catalog entries are in retail and grocery & food.
By industry
- retail 2 channels
- grocery & food 1 channel
By network
- SPS Commerce 1 channel
FAQ
EDI 857 questions
What is an EDI 857?
EDI 857 is the X12 Shipment and Billing Notice transaction set. Trading partners use it when shipment and billing details are transmitted together. It carries the data for the combined shipment and billing record, and your system matches it on shipment, invoice and order references.
Who sends an EDI 857 and who receives it?
The supplier sends the 857 to the buyer, typically a grocery retailer or wholesaler, as both the delivery notice and the invoice for a shipment. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 857 sent?
A supplier ship-confirms an order and issues a single document at shipment that serves as both the ship notice and the invoice. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 857?
Across 3 partner document references listed here, the business segments that appear most often include BHT (Beginning of Hierarchical Transaction), HL (Hierarchical Level), G05 (Total Shipment Information), DTM (Date/Time Reference), N9 (Reference Identification), N1 (Name). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 857 and EDI 850?
The 857 carries the combined shipment and billing record and is used when shipment and billing details are transmitted together. The 850 carries the purchase order or sales order and is used when a buyer places an order.
What should I map for X12 857?
Start with shipment, invoice and order references and the target combined shipment and billing record. 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 857 error handling?
Reconcile shipped quantity with invoiced quantity while allowing an agreed partial shipment. Prevent separate shipment and billing processing from creating duplicate downstream records. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 857?
The directory on this page links 3 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
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.
