To start and identify an interchange of zero or more functional groups and interchange-related control segments
Barnes & Noble X12 857 Shipment and Billing Notice
Plan X12 857 Shipment and Billing Notice for Barnes & Noble. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 19
- Loops
- 6
- X12 857
- Partner references ↗
Implementation guide
Barnes & Noble: 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.
This document is listed for Barnes & Noble. Confirm the version, required fields and responses that apply to your account.
| 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 |
|
The document reference includes 19 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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 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 Barnes & Noble 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.
Transaction context
Where 857 Shipment and Billing Notice fits on Barnes & Noble
- Barnes & Noble channels
- 1 of 1
1 of Barnes & Noble's 1 channel list 857
- Trading partners
- 3
partner references list 857
- Channels
- 3
channel entries list 857
Frequently listed alongside 857
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 |
Key identifiers in 857
- 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
Segment reference — 19 segments 6 loops · X12 857 Shipment and Billing Notice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
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
HL Loop Repeat: 1
To identify dependencies among and the content of hierarchically related groups of data segments
G05 Loop Repeat: 1
To provide totals relating to the shipment
To specify the carrier and sequence of routing and provide transit time information
To specify pertinent dates and times
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To transmit identifying information as specified by the Reference Identification Qualifier
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
TDS Loop Repeat: 1
To specify the total invoice discounts and amounts
To provide reference to a specific purchase order
LX Loop Repeat: 1
To reference a line number in a transaction set
To describe marking, packaging, loading, and unloading requirements
To indicate identifying marks and numbers for shipping containers
IT1 Loop Repeat: 1
To specify the basic and most frequently used line item data for the invoice and related transactions
To specify the physical qualities, packaging, weights, and dimensions relating to the item
To specify pricing information
Related references
Other transactions in Barnes & Noble
Other EDI documents listed on this channel.
Barnes & Noble EDI 857 questions
Common questions about 857 Shipment and Billing Notice on the Barnes & Noble channel.
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.
Is 857 required for Barnes & Noble?
857 is listed for Barnes & Noble. Confirm the required version and direction for your business unit and account with the partner.
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 810 Invoice are related documents also listed on Barnes & Noble. 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 Barnes & Noble 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.
