X12 transaction code
X12 857 Shipment And Billing Notice
X12 857 Shipment And Billing Notice: explore its business purpose, mapping identifiers, validation tests and 3 partner references across 3 listed channels.
- Standard
- X12
- Code
- 857
- Partner references
- 3
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): shipment contents are known before the agreed notification deadline.
- 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
X12 857 questions
What is X12 857 Shipment And Billing Notice used for?
857 is used when shipment and billing details are transmitted together. It carries information for the combined shipment and billing record. Match it to your business system using shipment, invoice and order references.
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.
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.
How does 857 relate to other EDI messages?
X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 810 Invoice 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 857 and 850?
857 is used when shipment and billing details are transmitted together. 850 is used when a buyer places an order. 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.
