X12 transaction code
X12 895 Delivery Return Acknowledgment Or Adjustment
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 895
- Trading partners
- 1
Specification summary
X12 895 Delivery Return Acknowledgment Or Adjustment at the element level
The X12 895 specification defines 15 segments carrying 65 data elements, 40 of which are mandatory.
- Segments
- 15
- Data elements
- 65
- Mandatory elements
- 40
| Segment | Elements | Mandatory |
|---|---|---|
| G87 | 6 | 5 |
| LS | 1 | 1 |
| G89 | 7 | 1 |
| G72 | 7 | 2 |
| LE | 1 | 1 |
| G23 | 11 | 2 |
| G85 | 1 | 1 |
- Initiator Code
- Credit/Debit Flag Code
- Supplier's Delivery/Return Number
- Integrity Check Value
- Adjustment Number
- Loop Identifier Code
- Direct Store Delivery Sequence Number
- Allowance or Charge Code
Trading partners that support X12 895
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 895 Delivery Return Acknowledgment Or Adjustment
895 is used most heavily in grocery & food.
The 895 closes the DSD delivery loop: it acknowledges an 894 Delivery/Return Base Record or communicates the adjustments store personnel identified during check-in. Per the X12 purpose, the transaction contains only the detail data being changed, and an 895 with no changes is considered acceptance of the preceding base record or adjustment. Suppliers require it so route accounting settles against what the store actually received. The retailer's store or headquarters receiving system sends the 895 back to the DSD supplier or distributor after checking in the delivery reported on the 894. Store personnel complete check-in of a DSD delivery and the receiving system confirms the driver's 894 or reports the quantity and item corrections found at the back door.
By industry
- grocery & food 1 channel
FAQ
X12 895 questions
What is X12 895 Delivery Return Acknowledgment Or Adjustment?
X12 895 (Delivery Return Acknowledgment Or Adjustment) is an EDI transaction set defined by ANSI ASC X12 for exchanging delivery return acknowledgment or adjustment between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 895?
1 Stacksync partner accepts X12 895: 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 895 with my ERP?
Stacksync handles the full X12 895 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.
