Skip to content
EDI Norfolk Southern Norfolk Southern 998
X12 EDI

Norfolk Southern X12 998 Set Cancellation

X12 998 (Set Cancellation) is the EDI transaction exchanged between Norfolk Southern (Norfolk Southern) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
5
Loops
0
X12 998
All partners ↗
Book a demo ← All Norfolk Southern transactions

Transaction context

Where 998 Set Cancellation fits on Norfolk Southern

Norfolk Southern channels
1 of 1

1 of Norfolk Southern's 1 channel carries 998

Trading partners
4

partners across the Stacksync network trade 998

Channels
4

channels network-wide carry 998

Most common alongside 998

The 998 requests deletion of a previously transmitted transaction set and states the reason, such as a diverted shipment or cancelled bill. In practice it is a rail document: shippers use it to void a bill of lading (404) already submitted to the railroad while it is still suspended in the carrier's system. It is a three-segment message (ST, ZD, SE) whose ZD segment identifies the original document by equipment initial and number, bill of lading number, and sender, with a CA qualifier marking the cancellation. Sent by the rail shipper (the railroad's customer) to the rail carrier holding the previously submitted 404 bill of lading.

When it fires: A rail shipment is cancelled or diverted after the bill of lading has been transmitted to the railroad but before the car is waybilled and moves.

Common 998 rejection causes
  • Equipment initial, equipment number, or bill of lading number that do not match the original 404, so the carrier cannot identify which suspended bill to void.
  • X12 version mismatch: carriers such as CN require the 998 to be sent in the same version as the 404 it cancels.
  • Missing the CA cancellation qualifier in the ZD segment, so the request does not register as a cancellation.
  • Cancellation attempted after the bill of lading has left suspended status because the shipment was already waybilled, so no matching suspended bill exists to void.

Specification summary

X12 998 Set Cancellation at the element level

The X12 998 specification defines 5 segments carrying 34 data elements, 30 of which are mandatory.

Segments
5
Data elements
34
Mandatory elements
30
Segments with mandatory elements
Segment Elements Mandatory
ZD 8 4
Key identifiers in 998
  • Transaction Set Identifier Code
  • Equipment Initial
  • Equipment Number
  • Correction Indicator Code
Full segment guideline — 5 segments 0 loops · X12 998 Set Cancellation
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

ZD Transaction Set Deletion - ID, Reason, and Source 8 elements

This segment is used to specify the transaction set to be canceled

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Trading partners

2+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

Norfolk Southern Norfolk Southern EDI 998 FAQ

Common questions about 998 Set Cancellation on the Norfolk Southern channel.

What is X12 998 Set Cancellation?
X12 998 (Set Cancellation) is the EDI transaction set used to exchange set cancellation data. Norfolk Southern's Norfolk Southern channel requires it from trading partners.
Does Norfolk Southern Norfolk Southern require 998 for trading partners?
Yes, Norfolk Southern (Norfolk Southern) supports X12 998 Set Cancellation. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Norfolk Southern 998 with Stacksync?
Most companies go live with Norfolk Southern 998 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 998 on Norfolk Southern?
On Norfolk Southern, X12 998 is typically exchanged alongside 404 Rail Carrier Shipment Information, 824 Application Advice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.

Ready to automate your Norfolk Southern EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a Norfolk Southern EDI demo Tour the platform on your own