Automation of transshipment permits treats IGM entries as transshipment requests, streamlining electronic port to ICD cargo movement. The SMTP portion of the IGM will be treated as the transshipment request, eliminating separate carrier applications; carriers must record the transporter code in a new IGM field. ICES will exchange transshipment permit data among carrier, transporter, gateway custodian and destination ICD/CFS. Transporters must electronically submit a Container Arrival Report to the destination ICES, which will be matched to generate a Landing Certificate transmitted to the gateway for closure of IGM lines. Transmitted permits will be converted into IGMs at the recipient port without fresh filing by shipping lines; bond debit/credit rules are being revised separately.
Cases where this provision is explicitly mentioned in the judgment/order text; may not be exhaustive. To view the complete list of cases mentioning this section, Click here.
Provisions expressly mentioned in the judgment/order text.
Automation of transshipment permits treats IGM entries as transshipment requests, streamlining electronic port to ICD cargo movement.
The SMTP portion of the IGM will be treated as the transshipment request, eliminating separate carrier applications; carriers must record the transporter code in a new IGM field. ICES will exchange transshipment permit data among carrier, transporter, gateway custodian and destination ICD/CFS. Transporters must electronically submit a Container Arrival Report to the destination ICES, which will be matched to generate a Landing Certificate transmitted to the gateway for closure of IGM lines. Transmitted permits will be converted into IGMs at the recipient port without fresh filing by shipping lines; bond debit/credit rules are being revised separately.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.
TaxTMI 
of 
TaxTMI 
