Home Circulars 2005 Customs Customs - 2005 This
Forgot password New User/ Regiser ⇒ Register to get Live Demo
Automation of movement of containerized cargo from Gateway Ports to hinterland ports – SMTP - Customs - 046/05Extract Automation of movement of containerized cargo from Gateway Ports to hinterland ports - SMTP - regarding CIRCULAR NO. 46/2005-Cus F.No.450/66/2004-CUS-IV Government of India Ministry of Finance Department of Revenue Central Board of Excise Customs November 24th, 2005 Subject: Automation of movement of containerized cargo from Gateway Ports to hinterland ports - SMTP - regarding- The undersigned is directed to state that during the deliberations of Inter Ministerial Group consisting of representatives of Ministry of Shipping, Ministry of Commerce and Planning Commission under the Chairmanship of Secretary (Revenue), one of the issues that came up was the requirement of filing Sub-Manifest Transhipment Permit (SMTP) application and consequent delay in clearance of goods meant for transshipment to hinterland ports/ ICDs/ CFSs. 2. The Board has now decided to automate the transshipment of containerized cargo from one Port to an Inland Port or ICD/CFS where the Indian Customs EDI System (ICES) is operational. This would involve exchange of messages for Transshipment of Cargo electronically among Customs, Port authorities, ICDs and Shipping Agents.. The implementation of this module is a significant step in the ongoing Business Process Re-engineering initiatives of the department. This will also reduce the congestion and dwell-time of cargo at the ports and will contribute to reduction in transaction costs of imports. 3. In the automated Transshipment Module, the requirement of an application by the carrier will be done away with and the SMTP (Sub manifest Transshipment Permit) portion of the IGM itself will be treated as a request for transshipment. Carriers will not be required to separately file an application for this purpose. They will however be required to indicate the code of the transporter undertaking the transshipment (e.g. CONCOR) in the IGM. For this purpose, a field is being added in the IGM format to capture this information. The ICES system will allow transshipment of those containers against whom the port of destination is indicated as ports other than the port of discharge. 4. The transshipment permit information will be sent to the carrier, the transporter undertaking the transshipment, custodian of the gateway port, and the ICES system at the destination ICD. Transshipment permit can also be printed by the carrier in his office or in the custom house. 5. The transshipment permit transmitted to the recipient port/ ICD/ CFS will automatically be converted into an IGM and the Shipping Lines will not be required to file any fresh IGM in respect of such containers. 6. The transporter performing the transshipment activity will be required to electronically submit a container arrival report to the ICES system at the destination ICD/ CFS in a specified format. The container arrival report will be matched with transshipment message received from the GatewayPort and a 'landing certificate ' message will be generated by the inland port/ICD/CFS which will be transmitted to the Gateway port for closure of IGM Lines. 7. Instructions on debit of Bonds for transshipment are also being modified to enable the carrier to carry out debit and credit in the Bonds. Circular in this regard is being issued separately. 8. Presently the automated transshipment module is implemented between JNPT and ICD Tughlakabad. Detailed transshipment procedure is being worked out by the Directorate of Systems and will be circulated to all automated custom locations for informing the trade before implementation. 9. Receipt of this Circular may be acknowledged.
|