972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Shipping and logistics

EDI 895 Delivery/Return Acknowledgment or Adjustment

The X12 document used to acknowledge completion of a direct store delivery, or to communicate adjustments to it.

Sent by
Retail store or DSD vendor
Received by
DSD vendor or retail store
Standard
ANSI ASC X12

What is an EDI 895?

The EDI 895 Delivery/Return Acknowledgment or Adjustment is the ANSI X12 transaction set that lets a distributor or direct store delivery (DSD) vendor communicate adjustments to a DSD delivery, or acknowledge the completion of a delivery.

After the store checks the delivery described in the 894, differences such as short quantities or price disagreements are recorded as adjustments. The acknowledged delivery, with any adjustments, becomes the agreed basis for payment, later summarized in the 882. It closes each delivery's check-in.

How the EDI 895 worksDiagram of the EDI 895 Delivery/Return Acknowledgment or Adjustment. Retail store or DSD vendor sends it to dSD vendor or retail store. It usually follows 894. It is usually followed by 882 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G87 (Delivery/Return Adjustment Identification) and summary: G86 (Signature Identification) and G85 (Record Integrity Check). 1 optional loops are listed by their first segment.How the EDI 895 worksDelivery/Return Acknowledgment or Adjustment: who sends it, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS894Delivery/Return BaseRecordEDI 895SENDERRetail store or DSDvendorRECEIVERDSD vendor or retailstore997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY882Direct Store DeliverySummary Information997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code DXGS … GETransaction set 895ST … SEHEADINGG87Delivery/Return AdjustmentIdentificationDETAIL+ 1 optional loop, starting with:G89SUMMARYG86Signature IdentificationG85Record Integrity CheckBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 895. Your trading partner's implementation guide adds its own requirements.
How the EDI 895 worksDiagram of the EDI 895 Delivery/Return Acknowledgment or Adjustment. Retail store or DSD vendor sends it to dSD vendor or retail store. It usually follows 894. It is usually followed by 882 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G87 (Delivery/Return Adjustment Identification) and summary: G86 (Signature Identification) and G85 (Record Integrity Check). 1 optional loops are listed by their first segment.How the EDI 895 worksDelivery/Return Acknowledgment orAdjustment: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS894Delivery/Return Base RecordEDI 895SENDERRetail store orDSD vendorRECEIVERDSD vendor orretail store997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY882Direct Store Delivery SummaryInformation997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code DX (GS … GE)Transaction set 895 (ST … SE)HEADINGG87Delivery/Return AdjustmentIdentificationDETAIL+ 1 optional loop, starting with:G89SUMMARYG86Signature IdentificationG85Record Integrity CheckBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 895. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 895, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 895 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Acknowledging a completed DSD delivery
  • Recording quantity or price adjustments
  • Agreeing the basis for payment

Where it fits in the document flow

Usually follows 894 Delivery/Return Base Record
This document 895 Delivery/Return Acknowledgment or Adjustment
Usually followed by 882 Direct Store Delivery Summary Information997 Functional Acknowledgment

Structure

Mandatory segments in the 895 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • G87
  • G89
  • G86
  • G85
  • SE

Practical example

The 895 in practice

A store receiver finds two cases fewer than shown in the driver's 894. The store's system sends an 895 adjusting the quantity and acknowledging the rest of the delivery. The vendor's system updates the delivery, and the corrected total is included in the weekly 882 summary.

Implementation

Implementation considerations for the 895

  • Use adjustment reason codes agreed with the vendor.
  • Acknowledge every delivery so none remains open.
  • Reconcile acknowledged deliveries with billing.
  • Resolve price disputes using synchronized price data.

How ECOM helps

Automate the 895 with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related shipping and logistics documents

All 15 shipping and logistics documents

Need help with the EDI 895?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us