AESDirect EDI Update - Routed Transaction Flag

Effective January 1, 2001 AES is implementing an additional data element to indicate if an export shipment is a routed transaction. The element is known as the 'Routed Transaction Flag'. You can send the 'Routed Transaction Flag' before January 1, 2001. This will allow you to make the transition at any time that you wish before January 1, 2001.

Additional information is available in the AESDirect Developers Center

Customs Proprietary Format

The 'Routed Transaction Flag' is position 41 of the SC2 record. While this element is required by AES, it will be treated as optional by AESDirect. If the 'Routed Transaction Flag' is not sent in the SC2 record AESDirect will assume that the shipment is not a routed transaction and will send the shipment to AES with the 'Routed Transaction Flag' set to N (No). Not sending the 'Routed Transaction Flag' is the same as explicitly sending the flag set to N.

For more information see: Notes on the Customs Proprietary Format Accepted by AESDirect

X12-601

The 'Routed Transaction Flag' has been added as element 4 of the M12 record. While this element is required by AES, it will be treated as optional by AESDirect. If the 'Routed Transaction Flag' is not sent in the M12 record AESDirect will assume that the shipment is not a routed transaction and will send the shipment to AES with the 'Routed Transaction Flag' set to N (No). Not sending the 'Routed Transaction Flag' is the same as explicitly sending the flag set to N.

For more information see: AESDirect X12-601 Mapping