We had several eHBLs that we picked up ‘Removed in Bond’ from the airline but we couldn’t ‘arrive’ them at our CW warehouse sub-loc because they were already released. What do we do? (Same question applies to marine cargo transferred in bond to a CW for deconsolidation.)

We had several eHBLs that we picked up ‘Removed in Bond’ from the airline but we couldn’t ‘arrive’ them at our CW warehouse sub-loc because they were already released. What do we do? (Same question applies to marine cargo transferred in bond to a CW for deconsolidation.)

There is an anomaly in the CBSA eManifest system so that when the CBSA port of discharge and port of destination are the same, even though the destination sub-loc code is different, the carrier’s CACM triggers the ‘arrival’ and with it the release status. The CW warehouse doesn’t have to worry about an AMPs penalty for not arriving the cargo because the regulations require a WACM ‘arrival’ only on ‘goods that are not released’. In these examples, the goods are released already so no WACM required. They are good to move.
[Editor’s Note: This may change in a future CBSA systems release, but for now, good to go.]

The message on this from the CBSA reads, “
According to the example, the PARS, cargo and e-house bill are all set-up for FPOA release, port 809, so since CBSA systems already ‘arrived’ the cargo and released the shipment, WACM was not required. The CBSA will only issue an AMP penalty if found in contravention of regulations/policy and in the example you provided below, since the cargo was already arrived by the CACM there appears to be no contravention of the WACM regulations.”