X12 transaction guide · Communications

EDI 998 Set Cancellation

The X12 document used to request deletion of a previously transmitted transaction set, with the reason, such as a diversion or cancelled bill.

Sent by
Sender of the original transaction set
Received by
Receiver of the original transaction set
Standard
ANSI ASC X12

What is an EDI 998?

The EDI 998 Set Cancellation is the ANSI X12 transaction set used to request the deletion of a previously transmitted transaction set, indicating the reason, such as a diversion or a cancelled bill.

It is used mainly in transportation, for example to cancel a bill of lading or waybill that was sent but will not be used. The receiver identifies the original transaction from the references in the 998 and removes it from processing, so the cancelled document does not lead to movements or charges.

How the EDI 998 worksDiagram of the EDI 998 Set Cancellation. Sender of the original transaction set sends it to receiver of the original transaction set. 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: ZD (Transaction Set Deletion - ID, Reason, and Source). 0 optional loops are listed by their first segment.How the EDI 998 worksSet Cancellation: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 998SENDERSender of the originaltransaction setRECEIVERReceiver of theoriginal transaction set997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code ALGS … GETransaction set 998ST … SEHEADINGZDTransaction Set Deletion - ID, Reason, and SourceBlue 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 998. Your trading partner's implementation guide adds its own requirements.
How the EDI 998 worksDiagram of the EDI 998 Set Cancellation. Sender of the original transaction set sends it to receiver of the original transaction set. 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: ZD (Transaction Set Deletion - ID, Reason, and Source). 0 optional loops are listed by their first segment.How the EDI 998 worksSet Cancellation: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 998SENDERSender of theoriginaltransaction setRECEIVERReceiver of theoriginaltransaction set997 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 AL (GS … GE)Transaction set 998 (ST … SE)HEADINGZDTransaction Set Deletion - ID,Reason, and SourceBlue 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 998. Your trading partner'simplementation guide adds its own requirements.

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

  • Cancelling a bill of lading sent in error
  • Deleting a waybill after a diversion
  • Withdrawing a transaction before it is processed

Where it fits in the document flow

This document 998 Set Cancellation
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 998 (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
  • ZD
  • SE

Practical example

The 998 in practice

A shipper sends a railroad a 404 bill of lading for a car, but the customer cancels the order before the car is pulled. The shipper sends the railroad a 998 identifying the bill of lading and the reason. The railroad deletes the waybill, so the car is not moved or billed.

Implementation

Implementation considerations for the 998

  • Reference the original transaction precisely.
  • State the cancellation reason with agreed codes.
  • Confirm the receiver supports set cancellation.
  • Send cancellations before the original is acted on.

Need help with the EDI 998?

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