X12 transaction code
EDI 895 Delivery/Return Acknowledgment or Adjustment (X12 895)
EDI 895 is the X12 Delivery/Return Acknowledgment or Adjustment transaction set, used when delivery or return quantities are acknowledged or adjusted. 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.
- Standard
- X12
- Code
- 895
- Partner references
- 1
At a glance
EDI 895 at a glance
What the 895 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 895 Delivery/Return Acknowledgment or Adjustment |
|---|---|
| Business record | Delivery or return response |
| Who sends it to whom | 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. |
| When it is sent | 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. |
| Match on | Original delivery, response and affected item |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 894 Delivery/Return Base Record |
Key segments in an EDI 895
The business segments in the one partner document reference listed below. 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 |
|---|---|---|---|
| G87 | Delivery/Return Adjustment Identification | To transmit identifying numbers, dates, and other basic data relating to the transaction set. | 1 of 1 |
| G89 | Line-Item Detail Adjustment | To transmit line-item detail adjustments. | 1 of 1 |
| G72 | Allowance or Charge | To specify allowances, charges, or services. | 1 of 1 |
| G23 | Terms of Sale | To specify the terms of sale. | 1 of 1 |
| G84 | Delivery/Return Record of Totals | To specify summary details of total items in terms of quantity or amount. | 1 of 1 |
| G86 | Signature | To transmit an electronic identity. | 1 of 1 |
| G85 | Record Integrity Check | To provide a secure method of identifying authenticity of record content. | 1 of 1 |
Stacksync connects EDI documents such as the X12 895 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 895 mapping and validation
X12 895 Delivery/Return Acknowledgment or Adjustment is used when delivery or return quantities are acknowledged or adjusted. Preserve original delivery, response and affected item so the delivery or return response 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 response original delivery, response and affected item |
|
| Update the receiving system | Processing the delivery or return response ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the delivery or return response 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 894 Delivery/Return Base Record
delivery or return base record: delivery or return details establish a reconciliation baseline.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when delivery or return quantities are acknowledged or adjusted. Name the operational owner of the delivery or return response and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original delivery, response and affected 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 response 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 response processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 895 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic delivery or return response 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 response without processing it twice.
Document structure
X12 895 Delivery/Return Acknowledgment or Adjustment at the element level
The X12 895 reference contains 15 segment entries and 65 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 895
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 895 Delivery/Return Acknowledgment or Adjustment appears in this catalog
The largest groups of classified 895 catalog entries are in grocery & food.
By industry
- grocery & food 1 channel
FAQ
EDI 895 questions
What is an EDI 895?
EDI 895 is the X12 Delivery/Return Acknowledgment or Adjustment transaction set. Trading partners use it when delivery or return quantities are acknowledged or adjusted. It carries the data for the delivery or return response, and your system matches it on original delivery, response and affected item.
Who sends an EDI 895 and who receives it?
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. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 895 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 895?
The one partner document reference listed here includes G87 (Delivery/Return Adjustment Identification), G89 (Line-Item Detail Adjustment), G72 (Allowance or Charge), G23 (Terms of Sale), G84 (Delivery/Return Record of Totals), G86 (Signature). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 895 and EDI 894?
The 895 carries the delivery or return response and is used when delivery or return quantities are acknowledged or adjusted. The 894 carries the delivery or return base record and is used when delivery or return details establish a reconciliation baseline.
What should I map for X12 895?
Start with original delivery, response and affected item and the target delivery or return response. 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 895 error handling?
Apply an adjustment to the correct base-record line. Test multiple responses without applying the same quantity correction twice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 895?
The directory on this page links 1 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.
