PGA Exception: Details are required to be fed correctly as mentioned in this “SWIFT Referencer” - Customs - PUBLIC NOTICE NO. 02/2019

OFFICE OF THE COMMISSIONER OF CUSTOMS, NS-III MUMBAI CUSTOMS ZONE-II JAWAHARLAL NEHRU CUSTOM HOUSE, NHAVA SHEVA, TAL:- URAN, DIST : RAIGAD. PIN 400 707. F. No. S/22-Gen-402/2017-18/AM(I)/JNCH. Pt. I Dated 02.01.2019 PUBLIC NOTICE NO. 02/2019 Subject: PGA Exception: Details are required to be fed correctly as mentioned in this SWIFT Referencer , reg. Attention of the Importers, Exporters, General Trade and all other stakeholders is invited to various discussions in regard to routing of import declarations to Participating Government Agencies (PGAs) particularly about either out of scope items or dual use items being referred to PGAs due to incorrect or incomplete details given in the bill of entry / integrated declaration files / submitted by importer / Customs Broker. 2. In this regard, attention of importers / Customs Brokers is invited to SWIFT PGA Filing QUICK REFERENCER VERSION 1.5 as available on ICEGATE link as provided here (https://www.icegate.gov.in/Download/SWIFT_Quick_Referencer V1.5.pdf ). It explains as how to use this Referencer . Important part of this reference as regards to declaration of dual use items is PGA Exception where details are required to be entered correctly as mentioned in this referencer. It has been provided that in the reference that: i. Based on the CTH of the item, importer should check CTH-PGA mapping to identify the PGAs from whom NOC may be required for that commodity. ii. Check if the Product is covered in PGA Exception category as listed in page 35 of said reference. If so, For such PGA, in SW_INFO_TYPE table, Enter Info_type as PEC, Info_qfr as in PGA_CAT, info_code as in PGA_SLNO. E.g PEC DC0012016 0001 3. Annexure IV of the said Referencer contains details about PGA Exception Category in the format as mentioned below. Please refer to complete details on the website (link as provided above) Annexure IV-PGA Exception Category PGA_CAT PGA_SLNO PGA_DESC DC0012016 0001 Aluminium Oxide Alodur DC0012016 0002 (-) Diisopinocampheylchloroborane (60% Solution in Heptane) DC0012016 0003 (R) - Glycidyl Butyrate ----- ---- ---- ----- ----- ---- 4. It is also expected that PGA data requirements are met as also specified in the Referencer: PGA Data Requirement: May refer to individual PGA page ( 5-9) for data requirements: i. The Code in Type(coded) may be entered in Info_Type field. ii. The Code in Qualifier(Coded) may be entered in Info_qfr field. iii. The value may be Code, Text, measurement or both as indicated. iv. The qualifier may be mandatory or optional as indicated. For some goods, though it is optional, same is to be provided as was provided manually. v. The value if needed in text or measurement may be entered in respective field vi. The value needed in codes may be selected from codes indicated therein. vii. The value should not be given in other fields other than indicated. e.g. if value is Code, the value should not be given in text or measurement. 5. It is also expected that importer / Customs Broker should correctly declare above details in the integrated declaration. Single Window: Draft Guidelines for Agency-Wise Data Requirements are available at following link: https://www.icegate.gov.in/Download/Agency_wise_Filing_guidelines_29_March_2016. pdf ) 6. It has been provided that importer / Customs Broker should comply with following requirements to ensure minimum time taken at the end of PGAs and to avail proper facilitation from RMS i. The ICES captures Participating Government Agencies data requirements based on Customs Tariff Heads (CTHs). Therefore, importer / Customs Broker should look-up the Directory on CTH-wise agency clearance requirements published on ICEGATE. ii. For the given CTH, there are none, one or more than one agency listed. Against a CTH, if there is more than one agency indicated, the Bill of Entry should contain data required for all those agencies. iii. If any data has been missed in the first filing, it should be re-submitted along with amendments. 7. Please also refer to SW_FAQ Version 1.1 (available at https://www.icegate.gov.in/Download/SW_Declaration_FAQ_1.1.pdf ) This FAQ addresses the common queries sought by stakeholders regarding various data elements in the new integrated BE Declaration. For sake of convenience, the FAQ is ordered in the sequence of Tables listed in the Message Guidelines for BE Version 2.1, which is published on the ICEGATE website. Two relevant questions and answers related to endues field in the bill of entry are as under: 9. What is the change in Enduse of the item data field ? Ans: Earlier, this data field was a mandatory free text field. It is now converted into a coded field. It would only accept codes to be entered in Enduse. The list of codes are already published in the SW Directories. Only the Code needs to be entered. The text should not be entered along with the code. 12. Why is Enduse field changed from free text to Coded values ? Ans: When free text was provided, most importers were not declaring it in a form which can be used for any qualitative decision making. Most PGAs require codified end-use or purpose of import. End use having gained more importance with integration of PGAs, it is made as coded field, to make it useful for taking qualitative decision on facilitating PGA reference. Only list of values can be populated in the data field. 8. Thus, it can be seen that filling of correct and proper details in the aforesaid field is pre-requisite for proper treatment of the bill of entry and reduce dwell time for obtaining NOC from PGAs. 9. In case of any difficulty, the specific issue may be brought to the notice of Deputy/Assistant Commissioner in charge of DC/AC Group-I, Nhava Sheva-I or Appraising main (Import), NS-III (email address: email address: [email protected] ) . 10. Action to be taken in terms of decisions taken in this Public Notice should be considered as standing order for the purpose of officers and staff. Sd/- (SUBHASH AGRAWAL) Commissioner of Customs (NS-III).