X12 transaction code
X12 894 Delivery Return Base Record
X12 894 Delivery Return Base Record: explore its business purpose, mapping identifiers, validation tests and 8 partner references across 8 listed channels.
- Standard
- X12
- Code
- 894
- Partner references
- 8
Implementation guide
X12 894 mapping and validation
X12 894 Delivery Return Base Record is used when delivery or return details establish a reconciliation baseline. Preserve delivery reference, store and item so the delivery or return base 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 | delivery or return base record delivery reference, store and item |
|
| Update the receiving system | Processing the delivery or return base record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the delivery or return base 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 895 Delivery Return Acknowledgment Or Adjustment
delivery or return response: delivery or return quantities are acknowledged or adjusted.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when delivery or return details establish a reconciliation baseline. Name the operational owner of the delivery or return base record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map delivery reference, store and item. 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 delivery or return base 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 delivery or return base record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 894 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic delivery or return base 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 delivery or return base record without processing it twice.
Document structure
X12 894 Delivery Return Base Record at the element level
The X12 894 reference contains 17 segment entries and 72 data elements; 45 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 17
- Data elements
- 72
- Mandatory elements
- 45
| Segment | Elements | Mandatory |
|---|---|---|
| G82 | 7 | 5 |
| N9 | 2 | 1 |
| LS | 1 | 1 |
| G83 | 11 | 3 |
| G72 | 8 | 2 |
| LE | 1 | 1 |
| G23 | 3 | 2 |
| G85 | 1 | 1 |
- Credit/Debit Flag Code
- Supplier's Delivery/Return Number
- D-U-N-S Number
- Supplier's Location Number
- Physical Delivery or Return Date
- Reference Identification Qualifier
- Loop Identifier Code
- Direct Store Delivery Sequence Number
Find your trading partner for X12 894
8 partners, 8 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 894 Delivery Return Base Record appears in this catalog
The largest groups of classified 894 catalog entries are in grocery & food.
By industry
- grocery & food 8 channels
By network
- SPS Commerce 1 channel
FAQ
X12 894 questions
What is X12 894 Delivery Return Base Record used for?
894 is used when delivery or return details establish a reconciliation baseline. It carries information for the delivery or return base record. Match it to your business system using delivery reference, store and item.
Which partners list X12 894?
The directory on this page links 8 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 894?
Start with delivery reference, store and item and the target delivery or return base 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 894 error handling?
Separate returned units from delivered units when calculating the net quantity. Retain the original delivery record when a receiving party later disputes a quantity. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 894 relate to other EDI messages?
X12 895 Delivery Return Acknowledgment Or Adjustment is a related document 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 894 and 895?
894 is used when delivery or return details establish a reconciliation baseline. 895 is used when delivery or return quantities are acknowledged or adjusted. 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.
