Routed Transaction Flag Added to AESDirect WebLink

In line with the addition of the Routed Transaction flag to the U.S. Customs AES specification, we are adding a new element to AESDirect WebLink. The Routed Transaction Flag will be sent as element RT, and should be sent Y if the shipment is a routed transaction, or N if the shipment is not a routed transaction.

The routed transaction flag will be required by U.S. Customs starting January 1, 2001. We will be implementing the routed transaction flag in WebLink in mid-December. You can send the RT element before that date. As with any other required element in WebLink, if you do not send the RT element after it is implemented, users will be prompted to select if the shipment is a routed transaction before it will be accepted. In short, you can add the routed transaction flag to your application at any time.

The WebLink API has been updated to reflect these changes.