How to resolve a reject for “invalid status of request/cargo control number” or “ccn in history” (error code 464 and T36)

How to resolve a reject for “invalid status of request/cargo control number” or “ccn in history” (error code 464 and T36)


If you receive an “invalid status of request/cargo control number” or “CCN in history” response for your initial Add submission, please note that this means the cargo control number has been used previously and will require you to assign a new cargo control number and resubmit to CBSA. Please note the official response from CBSA regarding this rejection below.

 

CBSA Message No. : TCC014-008 – Electronic Commerce Unit – Reminder to clients

 

Duplicate Cargo Control Numbers

 

If you receive a reject message on your release transaction for “invalid status of request/cargo control number” or “CCN in history” (error code 464 and T36) there is no need to contact the EDI hotline during the day or after business hours. These reject messages mean the cargo control number (CCN) has been used previously. To correct the rejection, a new cargo control number is required from the carrier.

 

These are straightforward reject messages and no assistance is required from the EDI hotline to resolve this.

 

If you need to know where this cargo control was used, you may contact the carrier. Alternatively, you or the carrier may transmit a status query through the Release Notification System (RNS) which can provide this information.   For more information on the status query function, please consult the RNS Electronic Commerce Clients Requirements Document (ECCRD).  If needed, you may request a copy of the RNS ECCRD by email at ECU.UCE@CBSA-ASFC.GC.CA.