Office of The Commissioner of Customs (General)
Mumbai Customs, Zone II, Nhava Sheva
F.No.: S/3-Gen-92/ 2019-20/IN/JNCH
DIN No.: 20210978NW00000C6BB
Date: 23.09.2021
PUBLIC NOTICE NO. 87/2021 – JNCH
Subject: Ship-Call based Monitoring of Compliance to Sea Cargo Manifest and Transhipment Reglulations (SCMTR), 2018 – reg
Attention of all Port Terminals, Shipping lines, Shipping Agents, Transhippers, Custodians, Freight forwarders, Customs Brokers, Importers, Exporters, and other stakeholders is invited to Sea Cargo Manifest and Transhipment Regulations (hereinafter referred to as SCMTR) notified through Board Notification No 38/2018-Customs dated 11.05.2018 as amended through Notification No 54/2019-Customs dated 01.08.2019, Notification No. 78/2019-Customs dated 31.10.2019 and Notification No.94/2020-Customs dated 30.09.2020.
2. It is observed that various stakeholders have not adhered to mandated timelines for filing of messages/manifests under SCMTR inspite of phased manner of adoption provided as per the Annexure A to Circular No 43/2020-Customs dated 30 September 2020 read with Regulation 15(1), and numerous extensions given by way of amendment to Regulation 15(2).
3. Stakeholders are hereby informed that Ship-call based monitoring of messages and manifests mandated under SCMTR will be undertaken by Nhava Sheva, in order to speedily resolve errors, and ensure successful error-free filing of mandated messages in all respects (viz. Import, Export & Transhipment).
4. The Joint/Additional Commissioner (SCMTR) shall allocate each vessel calling on Nhava Sheva to an Asst/ Deputy Commissioner for the purpose of error resolutions, and ensuring its SCMTR compliance in the following manner: –
a) the SCMTR Section shall maintain a register which shall be updated daily with particulars of upcoming ship-calls as prescribed in Annexure A.
b) immediately on receipt of intimation regarding a ship-call, the Joint/Additional Commissioner SCMTR section shall allocate an Assistant/Deputy Commissioner for each vessel. The SCMTR Section shall proceed to immediately inform the concerned ASC/ASA regarding name and contact details of the Asst/Deputy Commissioner who will assist with SCMTR compliance for the upcoming ship-call, with copy endorsed to the designated Asst./Dy Commissioner.
5.1 The Assistant/Deputy Commissioner assigned with ensuring SCMTR compliance for the ship-call shall reach out to the ATO/ASC/ASA/ANC/ATP/ACU associated with the ship call well in advance and ascertain whether all manifests mandated under SCMTR are successfully filed with proper acknowledgement.
5.2 The Assistant/Deputy Commissioner shall refer to FAQs, and Guides available https:/ iwww.icegate.gov.in/SeaManifestRe_gulation.html, and resolve user errors in SCMTR filing on the basis of the error codes returned in the acknowledgement. The Reporting Addl/Joint Commissioner shall monitor that all reported errors are resolved timely.
5.3 The Assistant/Deputy Commissioner shall ensure that all user level errors are resolved at the level of the stakeholder, before proceeding to escalate unresolved errors to DG systems for resolution through the SCMTR cell.
5.4 The monitoring log, as prescribed in Annexure B; report on the status SCMTR filing by each vessel shall be maintained by the Assistant/ Deputy Commissioner for each vessel allocated.
5.5 The monitoring log shall be submitted to SCMTR section weekly.
6. Concerned Stakeholders will be informed on their registered email ID regarding the details of the officer assigned for error resolution in relation to a ship-call. In case of any difficulty stakeholders may also reach out to:
SCMTR Cell
Sh Mohit Jangid
Deputy Commissioner
Ph: 7619759248
mohit.jangidAgov.in
Sh Rishikesh Yadav
Supdt
Ph: 9661111250
scmtr-jnch@gov.in
(Istikhar Baig)
Commissioner of Customs, NS-Gen
Copy to:
1. Chief Commisisoner of Customs, Mumbai Zone-II, JNCH
2. Commissioner of Customs, NS–I/NS-II/NS-III/NS-Audit/NS-V, JNCH
3. Port Terminals, CSLA, MANSA, Transhippers (ATP), CFSAI, CFSs (ACU), BCBA, FFAI, and all other stakeholders
4. All officers in Mumbai Zone II via Website
5. DC/EDI- for uploading on JNCH website
Annexure-A
Allocation of specific AC/DC to Ship Call
| Port Code |
IMO Ves-sel/ Train No. / Tr-uck No. |
Expec-ted date of arri-val |
Ship-ping line Code/ Car-rier code |
Conta-iner / Bulk | Term-inal code / Custo-dian code |
Stat-us of ship call (valid/ canc-elled) |
SSOID of the Of-ficer task allo-tted to |
Na-me of the Offi-cer |
Em-ail | Mo-bile No. | Name of JC/ ADC repor-ting to | Mo-bile No. |
| (1) | (2) | (3) 1 (4) | (5) | (6) | (7) | (8) | (9) | (10) | (11) | (12) | (13) | |
–
| 11) | IMO ve3sellTrain N {) . : Truck No, | ||
| (2′ | Expected dale of arrival | ||
| (3) | SSOID ID | ||
| (4) | VC N Gpmeraled (YIN) | VCN | |
| (0) | VCN Number allotted | ||
| (1) | VC N_ Reasons for error | ||
| (2) | VCN rectification status | ||
| (3) | ‘,.CN DG System responses | ||
| 9) | Successlul SAM Submission (Y/N) | SAM | |
| (10) | SAM Rotaion No. | ||
| (11) | Dale of ACK from ICEGATE | ||
| 1121 | SAM rerison for error | ||
| (13) | SAM Resclrfication Status | ||
| (14) | SAM_ DG Systems responses | ||
| 1151 | SEI | ||
| 116) | SE I Rotation No. | ||
| (17) | Date of ACK from ICEGATE | ||
| (15) | SEl_reason for error | ||
| (16) | :71EI_Resclific:ation Status | ||
| (201 | SE I__ DG Systems reqoonses | ||
| (21) | Succksfilul SDNI Submission (YIN) | SDM | |
| (17) | SDM Rotation No. | ||
| (18) | Dale of ACK torn ICEGATE | ||
| 124) | spiv_ r4:-Rson for error | ||
| 125) | SDK_ RE soification Status | ||
| (26) | SDM_DC:’, Systems tespHoses | ||
| (27) | Success( ul SDN Submission (Y/N) | SDN | |
| (22) | ZSDN Rotation No. | ||
| (29) | Date of ACK from ICEGATE | ||
| (30) | SDN_ reason for error | ||
| (31) | SDN Resctification Status | ||
| (32) | SDN DG Systems re..winses | ||
| (33) | Successf ul ELR (ELR Load) Submission (YIN) | ELR (Load ELR (Lan, | |
| (34) | ELR ‘FUR Load) Rotation No. | ||
| (35) | Date oi ACK from ICE GATE | ||
| (36) | ELR (ELR Load) reason for error | ||
| (37) | ELR (ELR Load’ Roschficalion Stews | ||
| (38) | ELR (ELR Load) DG Systems response3 | ||
| (39) | Successful ELR (ELR Larld) Submission (Y/N) | ||
| (40) | ELR (ELR Land) Rotation No. | ||
| (Al) | Date of ACK from ICEGATE | ||
| (42) | ELR (ELI; Lend) Meson for error | ELR (Land) |
|
| (12) | ELR (ELR Land) IR esditication Slake | ||
| (43) | ELR IELR Land) DC Systems responses | ||
Annexure-B2
