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 854 Shipment Delivery Discrepancy Information

The X12 document a carrier uses to notify the shipper or consignee of differences between the freight tendered and the freight delivered.

Sent by
Carrier
Received by
Shipper or consignee
Standard
ANSI ASC X12

What is an EDI 854?

The EDI 854 Shipment Delivery Discrepancy Information is the ANSI X12 transaction set a carrier uses to notify a shipper or consignee of discrepancies between tendered freight and the freight actually delivered. It reports overages, shortages and damage, so the parties can track and control them.

The 854 is not a receipt acknowledgment; consignees confirm receipt with other documents such as the 861 receiving advice. Its value is early warning: the shipper learns of a short or damaged delivery from the carrier before the customer disputes the invoice.

How the EDI 854 worksDiagram of the EDI 854 Shipment Delivery Discrepancy Information. Carrier sends it to shipper or consignee. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BDD (Beginning Segment for Shipment Delivery Discrepancy Information) and detail: the required LX loop with LX (Transaction Set Line Number). 2 optional loops are listed by their first segment.How the EDI 854 worksShipment Delivery Discrepancy Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 854SENDERCarrierRECEIVERShipper or consignee997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code DDGS … GETransaction set 854ST … SEHEADINGBDDBeginning Segment for Shipment DeliveryDiscrepancy Information+ 1 optional loop, starting with:N1DETAILRequired loop LX · repeats up to 999LXTransaction Set Line Number+ 1 optional loop, starting with:N1Blue 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 854. Your trading partner's implementation guide adds its own requirements.
How the EDI 854 worksDiagram of the EDI 854 Shipment Delivery Discrepancy Information. Carrier sends it to shipper or consignee. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BDD (Beginning Segment for Shipment Delivery Discrepancy Information) and detail: the required LX loop with LX (Transaction Set Line Number). 2 optional loops are listed by their first segment.How the EDI 854 worksShipment Delivery Discrepancy Information:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 854SENDERCarrierRECEIVERShipper orconsignee997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code DD (GS … GE)Transaction set 854 (ST … SE)HEADINGBDDBeginning Segment forShipment DeliveryDiscrepancy Information+ 1 optional loop, starting with:N1DETAILRequired loop LX · repeats up to999LXTransaction Set LineNumber+ 1 optional loop, starting with:N1Blue 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 854. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 854, 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 854 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

  • Reporting shortages or overages found at delivery
  • Reporting freight damaged in transit
  • Supporting later loss and damage claims

Where it fits in the document flow

This document 854 Shipment Delivery Discrepancy Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 854 (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
  • BDD
  • N1
  • LX
  • Q8
  • SE

Practical example

The 854 in practice

A carrier delivers a 24-pallet load to a grocery distribution center, where the receiver finds 23 pallets and one crushed case. The carrier sends the shipper an 854 referencing the bill of lading and pro number, reporting one pallet short and one case damaged. The shipper's customer service team opens an investigation and prepares a credit for the customer before the invoice is short-paid.

Implementation

Implementation considerations for the 854

  • Reference the bill of lading, pro and purchase order numbers so the discrepancy can be traced.
  • Feed discrepancies to customer service and claims teams, not only to the EDI archive.
  • Reconcile carrier-reported discrepancies with the customer's receiving advice.
  • Use the information to support freight claims within carrier claim deadlines.

How ECOM helps

Automate the 854 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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 854?

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

Request a Demo Contact us