ICES 1.

5
Customs - DGFT Message Integration
(Technical Document) Version 1.9

Directorate of Systems Central Board of Excise & Customs Department of Revenue Ministry of Finance C. R. Building, I.P. Estate New Delhi – 110002

Finance Informatics Division National Informatics Centre Department of Information Technology Ministry of communication & Information Technology A-Block, CGO Complex New Delhi – 110003

National Informatics Centre

ICES 1.5

Customs-DGFT Message Formats

Customs – DGFT Message Formats

Document Modification Summary
S.No . 1 2 3 4 Document Version Version .1.0 Version 1.1 Version 1.2 Version 1.2 Date of Modification 28th April, 2003 30th July, 2003 6th August, 2003 11th August, 2003 License Message Integration in ICES part added . License Release Advice Messages added Release Advice Messages, changes in Page 40 for fields 7, 8 and in page 41 for fields 13,14,15. Release Advice Messages : Customs Notification Date added to License Master. Message structure added to message CHCHL02. Page 43, Message exchange server directories „era‟ replace with „lra‟ Note at Page 6, Page 11 Description of drug composition, multi drug tag, example added in message structure at page 15,16, License control file added Page 19, The field length of field 13(Quantity for value cap item changes from 16 to 11,3 Brief Description of Changes Document Description Document : MS Word File : CustomsDGFTMessageFinal28042003 Document : MS Word File : Customs-DGFT MessageV1.1(31072003) Document : MS Word File : Customs-DGFT MessageV1.2(06082003) Document : MS Word File : Customs-DGFT MessageV1.2(1108-2003) Document : MS Word File : Customs-DGFT MessageV1.2(1208-2003) Document : MS Word File : Customs-DGFT MessageV1.3(0906-2004) Document: MS Word File : Customs-DGFT messagesV1.3(0608-2004)

5

Version1.2

12th august, 2003

6

Version 1.3

15th June, 2004

7

Version 1.3

06th August,2004

NIC-ICES-MSG-DGFT

Version 1.9

Release Date 21/07/2008

i

National Informatics Centre

ICES 1.5

Customs-DGFT Message Formats

S.No .

Document Version

Date of Modification

Brief Description of Changes License message (DGCH 002): Master: File Number removed; Field name – DEPB credit changed to Duty credit/saved; Waiver – Field type changed to N; Items of import: SION detailed removed; Conditions and Co-Licensee Tables added; SB Table- Mater removed, items of export table modified; Amendment procedure write-up added; CHDG003: SION Product Group, SION Sr. No added and field order changed in Details of items of export. New table – Details of License added.

Document Description

8

Version 1.4

31st August 2005

Document: MS Word File : Customs_DGFT_Message_Format_Ver1.4

9

Version 1.5

28th September 2005

License acknowledgement format modified

Document: MS Word File : CustomsDGFT messagesV1.5(28.09-2005 Document: MS Word File : CustomsDGFT messagesV1.5(28.09 -2005 Document: MS Word File : CustomsDGFT messagesV1.6(04.01.-2006)

10

Version 1.5

10th October 2005

New SB Message – CHCH003 from Customs House to Central Server for DEPB and DFRC Licenses introduced. Message CHDG003 modified – In „Details of items of exports‟, two new parameters, namely – Appraised FOB value and IEC of third party added. License Message (DGCH002) – Shipping Bill details modified by including Parameters – Flag for contentious issues resolved manually by DGFT and Customs; quantity; Unit of measurement and Amount realized (as per BRC) CHDG003: Explanations CHDG006: Additional Error Codes – 95,96 and 97

11

Version 1.6

4th

January 2006

12

Version 1.7

28th August 2006

Document: MS Word File : CustomsDGFTMessageFormatsVersion1.7

NIC-ICES-MSG-DGFT

Version 1.9

Release Date 21/07/2008

ii

Control file information removed for both the messages.No .8 NIC-ICES-MSG-DGFT Version 1.8 17th March 2008 Document: MS Word File : CustomsDGFTMessageFormatsVersion1.9 21sy July 2008 Document: MS Word File : CustomsDGFTMessageFormatsVersion1. separate control file is not required. DGCH003: In case of Advance License Scheme (Scheme Code: 03) DGFT to transmit the license message on submission of application by importer with File No and File Date. New mapping table (File No – License No) introduced CHDG005. File naming convention modified. Document Version Date of Modification Brief Description of Changes Technical documentation for ICES 1. CHDG005: IE Code Dir.: Message format.5 Customs-DGFT Message Formats S. Ack. DGCH013: EODC Certificate introduced CHDG004: BE Message format revised Message numbering is revised according to the flow .8 14 Version 1.: Message format. CHDG014: EODC acknowledgement introduced RA messages removed Document Description 13 Version 1. and after processing with License No and Date.National Informatics Centre ICES 1.9 Release Date 21/07/2008 iii . File naming convention modified.5 DGCH001: IE Code Dir. CHDG007: Since validations are SB/BE level.

2 4.1 4. 1 9 10 11 11 16 17 44 46 55 60 62 63 65 66 68 70 79 80 NIC-ICES-MSG-DGFT Version 1.11 4.8 4.National Informatics Centre ICES 1.3 4.13 4.5 Customs-DGFT Message Formats Contents Section 1.12 4.14 Topic Introduction List of Messages File naming conventions Messages IE Code Directory IE Code acknowledgement License information License acknowledgement Shipping Bill Format Shipping Bill acknowledgement Bill of Entry information BE Acknowledgement Non-receipt of message from DGFT Non-receipt of acknowledgement from DGFT DEPB Directory Customs Notification Directory EODC Certificate EODC Acknowledgement Annexure Page No.5 4.9 Release Date 21/07/2008 iv .9 4.0 3.4 4.0 2.6 4.10 4.0 4.0 4.7 4.

.9 Release Date 21/07/2008 Page 1 of 676789 .5 Customs-DGFT Message Formats Customs – DGFT 1. Please note that there will be no ASCII 29 Char (field separator) after the last field. tables are created in the ICEGATE Schema.National Informatics Centre ICES 1. Message Format Details: ICEGATE Header and Footer details for all the messages are provided separately. To summarize. Aa Delhi through ICEGATE. The application. NIC-ICES-MSG-DGFT Version 1. would insert the record in the Control Table and other application will update the appropriate parameters after completing the action. which will be used by both ICES and ICEGATE applications for message integration/generation.5. Similarly. This includes the header and Trailer. . ASCII 10 will be used as record separator. the ICEGATE has to parse the message and after the basic validations. These will apply to all messages. the information will be loaded in the message specific tables and insert a record in the control table. The regional offices of DGFT will collect the data from offices under its jurisdiction and transmit to the Customs Hq. Processing of Messages at ICEGATE and ICES For information exchange with the trading partners. Since the outbound data is generated by ICES itself. For all incoming messages. Using the Control Table ICES application would integrate the message and update the Control Table. The messages are then integrated with ICES 1. with Message name as table name. The system will also maintain a Control table in the ICEGATE Schema. no additional validation is done at ICEGATE. for the incoming message. the Controls tables will reside in the ICEGATE Schema and – There will be one Control Table for each outbound message. ASCII 29 will be used as field separator all over the document. the ICES will provide view access on specific transaction tables to ICEGATE user or create a database table(s) in ICEGATE Schema (of ICES). which initiates the transaction/message.0 INTRODUCTION The message exchange between Customs and DGFT take place at head office level through ICEGATE.

National Informatics Centre

ICES 1.5

Customs-DGFT Message Formats

-

Incoming single table messages will have all the control information in the same message table. Incoming multiple table message will have a separate control table. This control table is common for all inbound multiple table messages.

There will be separate control table for each outbound message and one central control table for all inbound messages with multiple tables. Control information for inbound single tables will be included in the data tables itself. Note: For inbound messages, it is assumed that the first level validations (like checking of mandatory fields, checking of message tags etc will be done by ICEGATE before the data is made available for pick-up by ICES. For all incoming messages, the ICES would generate acknowledgement after validation. The acknowledgement information will be present in the inbound table of ICEGATE Schema. ICEGATE will read this information and will generate the acknowledgement message. This document for each message, defines – a) b) c) d) The message structure for the recipient, Table /view definition for the ICEGATE application for generation of outgoing message, Control table structure and Table structures for each incoming message.

Acknowledgement from ICES application: The ICES application would generate an acknowledgement for all inbound messages. Both positive and Negative Acknowledgements will be generated for all records for transmission to trading partner through ICEGATE. Similarly, all outbound messages will have to be acknowledged by the Trading Partner. To facilitate generation of acknowledgement following is the mechanism: After ICEGATE puts the control parameters and data for any inbound message in the designated table(s), ICES will start processing the same for integration. In the course of processing, the records will be validated against a set of conditions and valid records get integrated. If a record is found invalid due to any reason, ICES will mark the error code for the same. There can be multiple errors against a single record. The errors are codified (Error codes ranging from 01 to 99) and are specific to each individual message. The error code list is included in the Message Specification Document for the inbound messages.

NIC-ICES-MSG-DGFT

Version 1.9

Release Date 21/07/2008

Page 2 of 676789

National Informatics Centre

ICES 1.5

Customs-DGFT Message Formats

The control/data tables in the ICEGATE schema are suitably modified by adding a field – „err_cd‟, for erroring code specification. The valid record will be marked with „00‟. In case of error(s), the appropriate code will be shown against each record. Multiple error codes will be separated by field delimiter „|‟. For single-table inbound messages (where control and data fields are included in the same table) such as COCHI04, the field will be added in the common table itself. For multiple table inbound message (where control table will be independent of the data tables), each data table will have an additional field (Unique_Id).

An additional control field – „Job Sequence No‟, is proposed – which will be purely for the purpose of internal processing of inbound messages by ICES. The details are given in the Technical Notes segment. Two additional fields are required in the control/data tables for the incoming messages: Err_cd: The field is required to specify the Error Code identified against a record during integration. ICES will update the field for all processed records. In case of valid record, the field will be marked with „00‟. In case of any error(s) the appropriate code will be shown against each record. Multiple error codes will be separated by a field delimiter - „|‟. For single-table inbound messages (where control and data fields are included in the same table) such as COCHI04, this field will be added in the common table itself. For multiple table inbound message (where control table is independent of the data tables), each data table will have this additional field as associated with the respective Primary Key. ICEGATE can generate the record-wise acknowledgement messages based on the contents of this field. Though the error codes are associated with rows from the data table, the Control Information for outbound acknowledgement will be present in the control table. Once ICES finishes its processing, and marks the records as „P‟. There will be an additional flag (Ack_Status_Flag) that will be used for processing of Acknowledgements. ICES will update this flag to „W‟. ICEGATE will pick-up the records for generating the acknowledgement messages in the specified format. Once the Acknowlegement is processed, the acknowledgement status flag will be changed to P. In addition, 2 more control fields (Ack_Create_Timestamp and Ack_Sent_Timestamp) will

NIC-ICES-MSG-DGFT

Version 1.9

Release Date 21/07/2008

Page 3 of 676789

National Informatics Centre

ICES 1.5

Customs-DGFT Message Formats

be used for recording when ICES updated error code and when ICEGATE sent the acknowledgement. Job_sequence_id: To handle large volume of messages, multiple processes may be required to be run in parallel for any particular inbound message. ICES requires an additional field in the control table of all inbound messages to facilitate identification/ demarcation of data related to separate processes. The 2-digit N field will be used exclusively by the ICES processes. The ICEGATE application shall not update/modify the field.. Access to ICES User (in ICEGATE Schema): Two different users are created for access to Control tables in the ICEGATE Schema, one for Imports and Exports. For import: Username Password For export: Username Password : : gxs_sb_exp gxs$exp02 : : gxs_be_imp gxs$imp01

Table naming conventions: Out-bound messages from ICES: Tables/Views are created in the ICES Schema with name(s) – M_<message Id>. Alias will be created for these views such that there will be no necessity to prefix the schema name. Example: SB message from Customs to CONCOR (CHCOE01) Table/View name will be – M_CHCOE01 IGM Message from Customs to CONCOR Table /view names will be – M_CHCOI01, MCHCOI02, M_CHCOI03

-

Corresponding Controls will be create in ICEGATE Schema with name –

NIC-ICES-MSG-DGFT

Version 1.9

Release Date 21/07/2008

Page 4 of 676789

the data tables will be created as –<message id>.National Informatics Centre ICES 1. For single-table inbound messages (where control and data fields are included in the same table) table naming convention will be – <message id> Ex: coche02 In the case of multi table inbound messages.5 Customs-DGFT Message Formats Control_table_obt_<message Id> Example: SB message from Customs to CONCOR (CHCOE01) Control table name: control_table_obt_ chcoe01 IGM Message from Customs to CONCOR Control table name: control_table_obt_ chcoi010203 - In-bound message from ICEGATE: Tables are created in the ICEGATE Schema. There will be one control table for all inbound multi table messages with the name of control_table_inb.9 Release Date 21/07/2008 Page 5 of 676789 . NIC-ICES-MSG-DGFT Version 1.

<Date> <Time> Date of transmission of message Time of transmission of message The same Sequence or Control Number that is used in the header has to be repeated in the trailer. Ex: CHCOI01 <Sequence or Control Number> is a unique value that can be used to uniquely identify the document. The value currently being passed in the second record can be used here. i.9 Release Date 21/07/2008 Page 6 of 676789 . Example: HREC^]ZZ^]ABCD^]ZZ^]XYZ^]ICES1_5^]P^]^]COCHE01^]123456^]20071015^]1015 TREC^]123456 All messages will have Header and footer by default.National Informatics Centre ICES 1. Currently it is “ICES1_5” is the test (T) or production (P) indicator is the message name or id.5 Customs-DGFT Message Formats ICEGATE Header and Footer ICEGATE Header: HREC^]ZZ^]<Sender ID>^]ZZ^]<Receiver ID>^]<Version No>^]<T or P>^] ^]<Message ID>^]<Sequence or Control Number>^]<Date>^]<Time> ICEGATE Footer: TREC^]<Sequence or Control Number> Where <Sender ID> <Receiver ID> <Version No> <T or P> <Message ID> is the ICEGATE code of the Customs House is the ICEGATE code of CONCOR/Custodian is the ICEGATE version being used. NIC-ICES-MSG-DGFT Version 1. This will not be included as part of each message separately.e. This will be used for tracking purposes.

National Informatics Centre ICES 1.5 Customs-DGFT Message Formats NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 7 of 676789 .

5 Customs-DGFT Message Formats Message Flow : Customs – DGFT IE Code Directory IE Code Acknowledgement License Information Customs License Acknowledgement Shipping Bill details SB Acknowledgement DGFT Bill of Entry Data BE Acknowledgment DEPB Directory NIC-ICES-MSG-DGFT 676789 Version 1.National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 8 of .

National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 9 of 6767 . 2. Bill of Entry Data BE Acknowledgement Customs DGFT DGFT Customs CHDG007 DGCH008 NIC-ICES-MSG-DGFT Version 1. 6. 9.5 Customs-DGFT Message Formats 2. Message Description IE Code Directory IE Code Acknowledgement License Information License Acknowledgement DEPB Directory Notification Directory EODC Certificate From DGFT Customs DGFT Customs DGFT Customs DGFT To Customs DGFT Customs DGFT Customs DGFT Customs Message DGCH001 CHDG002 DGCH003 CHDG004 DGCH011 CHDG012 DGCH013 Sr. No. 10. Message Description Shipping Bill Data SB Acknowledgement Non-receipt of message from Customs Non-receipt of acknowledgement from DGFT From Customs DGFT DGFT Customs To DGFT Customs Customs DGFT Message CHDG005 DGCH006 DGCH009 DHDG010 12. 3. No. 11. 5. 1. 7.0 List of Messages Sr. 8. 4. 13.

licaud 4.National Informatics Centre ICES 1. License Information License Acknowledgement Shipping Bill Data SB Acknowledgement Bill of Entry Data BE Acknowledgement DGCH003 <Custom Port Id>+<Date>+<Serial No>.EOD + Non-receipt of message from Customs 10. LICACK Code>+<DATE>+SR. 2.DIR <DDMMYYYY>. ERR Acknowledgement 3. Non-recipt of acknowledgement from DGFT 11. CHDG004 <Customs Port No. ”NSB” DGFT + <Custom Port Code> <EGMDATE> + ”SBAUD”.LIC <Port Code> + <Date>. No.0 File naming conventions Sr. 6.notn <Custom Port Code> + <Date> + <Serial No>. 7.5 Customs-DGFT Message Formats 3. EODC Certificate NIC-ICES-MSG-DGFT Version 1. ”SB”ACK DGFT + <Custom <DDMMYYYY> . 9. Message Description IE Code Directory IE Code: Message DGCH001 CHDG002 File naming convention “iec” + Date + Serial No. DEPB Directory 12. Notification Directory 13.ack DGFT+<Custom Port Code> + <DATE>. CHDG005 DGCH006 CHDG007 DGCH008 DGCH009 DHDG010 DGCH011 CHDG012 DGCH013 DGFT+<Port Code>+<EGMDATE>.BE Port Code> + DGFT + <Custom Port Code> + <DDMMYYYY> + ‟BE‟.nck DEPYYYYMMDD1. 5. 1. 8. IEC “iec” + Date + Serial No.9 Release Date 21/07/2008 Page 10 of 6767 .SB (DDMMYYYY: EGM date) DGFT + <Customs Port Code> + <DATE> .

5 Customs-DGFT Message Formats 4 4.9 Release Date 21/07/2008 Page 11 of 6767 . No. IE Master Sr. 1 2 3 4 5 6 7 8 9 10 11 12 13 Field Description IEC Number Party Name Address Line1 Address Line2 City State Pin Code IEC Issue Date Exporter Type PAN Number (BIN Number) PAN Issuing Authority PAN Issue Date IEC Status IEC Modification Date Field Type C C C C C N Date N C C Date N Date Field Length 10 50 35 35 35 6 ddmmyyyy 1 15 20 ddmmyyyy 1 ddmmyyyy B. Name. IEC Branch Sr. No. Corporate Address.1 Message Formats DGCH001 : From : IE Code Directory DGFT To CUSTOMS The message constitutes the Master details containing IE Code. Frequency of transmission : Once in a day. Date of Allotment etc. A. 1 2 3 4 5 6 Field Description IEC Number Branch Code Address Line1 Address Line2 City State Pin Code Field Type C N C C C N Field Length 10 3 35 35 35 6 Code directory: Export Status Code 1 2 3 4 5 6 Description Merchant Exporter Manufacturer Exporter Service Provider Others Merchant/Manufacturer None NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1. the Branch Office addresses are transmitted through a separate message.

5 Customs-DGFT Message Formats IEC Status Code 0 1 2 3 4 7 8 9 Description Normal Black Listed Suspended Cancelled Clear from Black List Revoke Suspension Revoke Cancellation Amendment Format of IE Code IEC number format is as PPYYNNNNNC Where PP YY NNNNN C DGFT Office code Year of Issue Running serial No.National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 12 of 6767 .IEC Message structure: <iec> <ie_master> ……… ……… ……… <END_ie_master> <iec_branch> ------------------------<END_iec_branch> <END_iec> NIC-ICES-MSG-DGFT Version 1. Check Digit File naming convention “iec” + Date + Serial No. IEC Example: Where Date Serial No Date of file creation Serial No of the message generated on <date>. iecYYYYMMDD99.

9 Release Date 21/07/2008 Page 13 of 6767 .PURNAVILLAGE.5 Customs-DGFT Message Formats Sample message formats: <iec> <iec_master> 0201001110|INDIA LEATHER WORKS. |FLAT-503.|KOLKATA(W.B. BLOCKA. |12.)|700089|20010427|1|AEVPM4674BFT002|||0|20010427| 0201001136|MANAGEMENT & COMPUTER CONSULTANTS.|FLAT-503. JESSORE ROAD.PURNAVILLAGE.|KOLKATA(W.B. LOUDAN STREET.PITAMPURA||DELHI|110034| | 0201001136|1|37/A DARGA ROAD CAL||CAL|700017| | NIC-ICES-MSG-DGFT Version 1.BIHWANDHI||MAHARASTRA|400004| 0201001110|2|PARVANAMARG.|CALCUTTA(W.)|700017|27/04/2001|AAFFM8472KFT001| ||0|27/04/2001| | 0201001110|INDIA LEATHER WORKS. BLOCK-A.National Informatics Centre ICES 1.PITAMPURA||DELHI|110034| 0201001136|1|37/A DARGA ROAD CAL||CAL|700017| <end_iec_branch> <end_iec> Master Acknowledgment file: From CUSTOMS to DGFT 0201001136|MANAGEMENT & COMPUTER CONSULTANTS.LOUDANSTREET.B. JESSORE ROAD.|CALCUTTA(W.BIHWANDHI||MAHARASTRA |400004| |0201001110|2|PARVANAMARG.|210.|FLAT-2E.|FLAT-2E.)|700089|27/04/2001|AEVPM4674BFT002| ||0|27/04/2001| | Branch Acknowledgment file: From CUSTOMS to DGFT 0201001110|1|ARIHANT.|210.)|700017|20010427 |1|AAFFM8472KFT001| ||0| 20010427| <end_iec_master> <iec_branch> 0201001110|1|ARIHANT.B.|12.

error records.ERR NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1. ERR Example: Where Date Serial No Date of file creation Serial No of the message generated on <date>. iecYYYYMMDD99. the Customs will generate an acknowledgement. No. it has to retransmit the message. It will be two in parts. 1 2 4 Field Description DGFT_FILE_NAME Field Type C Field Length 60 Master K K M IEC ERR_CD N C 7 100 Example 1: DGFT File Name IEC Error Code List of Error Codes: Message ID CHDG001 CHDG001 CHDG001 CHDG001 CHDG001 CHDG001 Error Code 00 01 02 03 04 05 Error Description IE Code accepted IE Code duplicate File naming convention “iec” + Date + Serial No.2 CHDG002 : From : IE Code acknowledgement Customs to DGFT On receipt of the IE Code directory from DGFT. Message Format : Application at the ICEGATE shall generate the acknowledgement message in the following format from the information available in tables . If the acknowledgement is not received by DGFT in the specified time period.5 Customs-DGFT Message Formats 4.IEMASTER and IEBRANCH Sr.9 Release Date 21/07/2008 Page 14 of 6767 . one .giving the number of IE Codes accepted (valid entries) and the other .

The License massage constitutes of Master details containing IE Code.. name of the Exporter/Importer. 2 In respect of DEPB license.3 DGCH003 : From : License Information DGFT TO CUSTOMS NOTE: 1 Duplicate License Number in a message will not be accepted.5 Customs-DGFT Message Formats 4. Frequency of transmission: Once in a day NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 15 of 6767 . Amendment: All the parameters of the corresponding level shall be given with Status flag “A”. the items of export and import. Refer to the detailed procedure explained in the document.National Informatics Centre ICES 1. the message shall contain details of all items of a SB as 3 4 5 6 forwarded by Customs through message . Re-instated message will be accepted only for suspended licenses. Message with status „F‟ will be accepted only once for a license. Before receiving Amended/Cancelled/Suspended/Re-instated messages. Message with status F already should have been received for the respective license.CHDG003. Value of the license (FOB and CIF values) in INR and Foreign Currency etc.

2 16. The DGFT will also give the mapping table of File No and License No as described in Part H of message format. 12. 7.2 16. 2.C. 19.2 3 10 1 1 (Y/N) 5. the DGFT would transmit the message with File NO and File Date. 11. 14.) Total CIF Value in F. 21. ddmmyyyy NOTE: In case of Advance License Scheme (Scheme Code: 03).C Code Customs Notification Number Customs Notification Date Fixed Norms (F) / Norms not fixed (A) /Others (NULL) Transferability Waiver in %age of CIF Value Field Type C Date C Date C C Date C C N Date N N C N N N C C Date C C N Field Length 1 25 6 2 3 10 2 16. Code Total CIF Value in Rs. 9. License Master Details Sr.2 3 16. 8. 3. 6. 10. File Number Format: Office Code/ Section Code/ Category/ Serial Number/ Application Period/ Export Period. 17. 13.C F. Duty Credit/Saved (in Rs. 22. 16.2 Mandatory/ Optional M M K K M M M M M O M* M* M* M* M* M* M* M* M M O M M Date . No. 5. and approved values of other parameters. Field Description Status Status Date License Number / File No License issue / File Date Port of Registration Scheme Code Import Validity end date Currency Area (GCA/RPA) IEC Branch Serial Number (as in IEC Database) Export Obligation end date FOB Value in Rs. F.National Informatics Centre ICES 1.C. XX/XX/XXX/XXXXX/XXXX/XXXX 12/34/567/99999/AMXX/AMXX NIC-ICES-MSG-DGFT Version 1. After issue of license.2 16.5 Customs-DGFT Message Formats A. 20. on submission of the application by the importer. 23. 4. 18. the same message would be transmitted with License No and issue date.9 Release Date 21/07/2008 Page 16 of 6767 . FOB Value in F. 15. 1.

F.5 Customs-DGFT Message Formats Sr. 40. 37.) Total CIF Value in F. 24. 36. 45.9 Release Date 21/07/2008 Page 17 of 6767 . 41. 30. 44. 29. 38. Duty Credit/Saved (in Rs. 28.C. 32. 43. 46. Field Description Status Status Date License Number / File No 27. 25. 34.C.C Code Customs Notification Number Customs Notification Date Fixed Norms (F) / Norms not fixed (A) /Others (NULL) Transferability Waiver in %age of CIF Value FOR DES Mandatory / Optional M M M (File Number applicable to DES) M M M M M M O M M M M M NULL M M M M O M O FOR EPCG Mandatory / Optional M M M FOR DEPB Mandatory / Optional M M M M M M M M M O M M M M O M O O M M NULL M NULL M M M M M M O NULL M NULL NULL NULL M NULL NULL M M NULL M NULL Date: ddmmyyyy NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1. 35. 39. 42. 33.C F. No. FOB Value in F. Code Total CIF Value in Rs. 26. 31. License issue / File Date Port of Registration Scheme Code Import Validity end date Currency Area (GCA/RPA) IEC Branch Serial Number (as in IEC Database) Export Obligation end date FOB Value in Rs.

7. 8. 05. 03 Export Obligation end date FOB Value in Rs.) 9.5 Customs-DGFT Message Formats Refer to Annexure C for DEPB. No. 17. FOB Value in F. DES and EPCG Schemes Valid for Scheme Codes – 01. 4.DES and EPCG Schemes For DES and EPCG Schemes only For ALL Schemes Null for DEPB Scheme (06) Refer to Annexure A Not for DEPB Scheme For DEPB Scheme only Duty credit: Valid for DEPB Scheme (Cd: 06) Duty saved: Valid for EPCG Scheme (Cd: 11) Valid for license category codes – 03. 3. Status and Status Date: Status Fresh License Amendment Cancellation Suspension Re-instated (Code F) (Code A) (Code C) (Code P) (Code R) Status Date License issue date Amendment Date Cancellation Date Suspension Date Re-instated Date NIC-ICES-MSG-DGFT Version 1. Fixed Norms (F) / Norms not fixed (A) /Others (NULL) Transferability Waiver in %age of CIF Value CURRENCY AREA CODE GCA RPA NAME General Currency Area Rupee Payment Area Note: DGFT shall provide the Customs Notification Number and Date ( Sr Nos – 18 and 19) in the format adopted by Customs. 2. 1. 10. Code Total CIF Value in Rs.National Informatics Centre Sr. Field Description Port of Registration Import Validity end date ICES 1.C.C. Duty Credit/Saved (in Rs. F. 6. 5. 18 Mandatory for DEPB. Customs will provide the Notification directory in the message format CHDG010.9 Release Date 21/07/2008 Page 18 of 6767 . 11.

C. Customs would not match SION Product Group and SION Sl. FOB Value in F. 2.19 SION : : S. No. Code SION Product Group SION Serial Number 02 12 Field Type C Date C N C C C N C N N C C C 03 17 Field Length 1 25 4 8 120 1000 13. No.02. No 10) and (Sr.No Refer to Annexure A Refer to Annexure B are valid for Scheme Codes: DES Scheme : FOB Value in Rs (Sr. 9. 7. No.04.9 Release Date 21/07/2008 Page 19 of 6767 .12) and FOB Value in FC (Sr. 11. No 10) and (Sr. No. Field Description Status Status Date License Number/File No Serial Number as in License ITC (HS) Code Description of Product/Item Technical Specifications Quantity Unit of Measurement Code FOB Value in Rs.05. as mentioned in licence and as declared by exporter in Shipping Bills while allowing exports under DES. 3. 21 (Fixed Norms (F) / Norms not fixed (A) /Others (NULL)). 8. No. 10. No. 21) ie if value is ‘F’ in field no. 6.13) in License Master detail should not tally with the sum total of the same mentioned for each item of export (Sr. 13) and SION Serial Number(Sr. 11) SION product Group (Sr. then SION Product Group and SION Sr.14) shall synchronize with License Master details (Sr. ITC (HS) Code : The directory shall be provided by DGFT in the format as described in Annexure D NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1. Items of Export Mandatory for Scheme Codes: 01 11 Sr. 14.2 3 2 6 05 18 08 09 Mandatory/ Optional M M K K M M O O O M O O M M F.No. 4. 13. 12) and FOB Value in FC (Sr.18. No. No.2 16.C F.13) in License Master detail shall tally with the sum total of the same mentioned for each item of export (Sr. No. 1. 12. 5. Code Unit of Measurement Code SION Product Group. NO will not be null.C.03.5 Customs-DGFT Message Formats B.3 3 16. 01.No. 11) EPCG Scheme : FOB Value in Rs (Sr.

14 and 16) in License Master details shall tally with the sum total of the same mentioned for each item of import (Sr.9 Release Date 21/07/2008 Page 20 of 6767 . 15) and CIF Value in FC (Sr.C Code 01 11 02 12 Field Type C Date C N N C C C N C N N C 03 17 05 18 Field Length 1 25 4 4 8 120 1000 11 3 16. 5.No. No.5 Customs-DGFT Message Formats C. 9.17) in License Master detail should not tally with the sum total of the same mentioned for each item of import (Sr. 17) in License Master details shall tally with the sum total of the same mentioned for each item of import (Sr. No of Item of Export as in License Serial Number as in License ITC (HS) Code Description of product/item Technical Specifications Quantity Unit of Measurement Code CIF Value in Rs.C. 4. CIF Value in F. No 11) and (Sr. 6. No. No 12) In case of EPCG Scheme : CIF Value in Rs (Sr.2 16. 2. 7. 13.C. 3. F. No 11) and (Sr. No.2 3 08 09 Mandatory/ Optional M M K M K M M O O O M O O F. No. 11.National Informatics Centre ICES 1. No.15) and CIF Value in FC (Sr. 1. Items of Import Mandatory for Scheme Codes: Sr. 8. 10. No. Field Description Status Status Date License Number/File No Sr. Code Unit of Measurement Code : : Refer to Annexure A Refer to Annexure B Note: CIF Value in Rs and FC (Sr. 12) NIC-ICES-MSG-DGFT Version 1. 12. No 9 and 10) DES Scheme : CIF Value in Rs (Sr.

05) Sr. 1. 3. address etc shall be given. 2. 8. 11. Conditions Valid for all licenses Sr. Co-licensee details Valid for Advance License Scheme Codes only (01. 7. 4. IE code.5 Customs-DGFT Message Formats D. List of supporting manufacturers Valid for Scheme Codes: Sr. Field Description Status Status Date License No/File No IE Code Branch Sr. 2. 3. Number Conditions F. Name. 9. 5. 6.03. No Field Type C Date C C N Field Width 1 10 10 2 Mandatory/ Optional M M K K M NIC-ICES-MSG-DGFT Version 1. 12. E. if not available. 1. Field Description Status Status Date License Number/File No Serial Number of the Manufacturer IE CODE Branch Serial Number Supporting manufacturer Name Address1 Address2 Address 3 Pin Central Excise Registration Number 01 02 03 05 Field Type C Date C N C N C C C C C C 18 Field Width 1 25 02 10 02 35 35 35 35 06 15 Mandatory/ Optional M M K K O O M M O M O O Supporting manufacturer may have/not have IE Code. No. 4. 5. 5.National Informatics Centre ICES 1. No. 3. No. (Except for Scheme Code : 06) Field Type C Date C N C Field Width 1 25 3 1000 Mandatory/ Optional M M K K M Field Description Status Status Date License No/File No Sr.9 Release Date 21/07/2008 Page 21 of 6767 . 2. 10.02. 1. 4.

8. No. 11. 1.2 2 10 1 11. Field Description License Number Status (F/S/D) Shipping Bill No Shipping Bill Date Port of Export Invoice Number Item Sr. No. Quantity of Export 4. Unit of Measurement 15. 3. 12.5 Customs-DGFT Message Formats G. 7. otherwise NULL Same as above 2.CODE: 03) NIC-ICES-MSG-DGFT Version 1. Shipping Bill details (In case of DEPB Scheme . Flag for Contentious issues (for issue of license) resolved Manually by DGFT and Customs 3. Unit of Measurement : H.) Field Type C C N Date C C N C N C C C N C N Field Length 10 1 07 ddmmyyyy 06 17 4 120 16.2 NOTES: Sr.Cap item. No. Field Description Port of Export Field Type Refer to Annexure C M–DEPB GR.9 Release Date 21/07/2008 Page 22 of 6767 . 4. Amount realized (as per BRC – in Rs.3 3 16. 2. No.National Informatics Centre ICES 1. 9. in the Invoice Description of Item of Export DEPB Credit for the item (in Rs) DEPB Group Code Item Sr. 5. Code/ Item Sr. 1. License No aginst a File No (Applicable for Advance License Shme only Scheme .CODE: 06 only) Shipping Bill details will be transmitted only in the case of DEPB license (Scheme Code: 06). Description of goods exported Sr. NO mismatch allowed. No in the Group Flag for Contentious issues (for issue of license) resolved Manually by DGFT and Customs 13. 6. Quantity of Export 14. in the Group mis-match allowed OTHER-WISE NULL Shall be provided only in the case of value. 10. I – IE Code mis-match allowed C – Commodity description mismatch allowed B – Both IE Code and DEPB Group Code and Item Sr.

Field Description ICES 1. if required.9 Release Date 21/07/2008 Page 23 of 6767 . C . E .List of supporting manufacturers. Similarly.Particulars of Import Goods. F – Conditions.Items of Export. 1. Status Date. 2.Shipping Bill details NOT TO BE GIVEN) Suspended or Cancelled License can be re-instated. Amendment: All the parameters of the corresponding level shall be given with Status flag “A”. if affect the values at master level.5 Field Type C Date C Date Customs-DGFT Message Formats Field Length 25 10 File No File Date License No Date of issue of License NOTES: Amendment to the License No key parameters can be amended.Provisional Exports. Amendment to the key parameters. corresponding information shall also be given. The amendment at the master level. 4. if affecting the values in item of export/import. D . Deletion of items of export or import Only the following parameters of Items of export/import shall be given with - - NIC-ICES-MSG-DGFT Version 1. Ex: Export obligation end date is amended: All the parameters at the master level shall be given with Status Flag “A” and Status date (amendment effective date). No. License Number. the amendment to values in items of export/import. 3.National Informatics Centre Sr. and Date of Issue of License Rest of the information is not required (B . information shall be provided. a delete message (Status – D) shall be forwarded followed by new message (Status – F) License Cancellation/Suspension/Re-instation (License Status – C/P/R): Only the following key parameters shall be given at the License master level – License Status. and G .

Running serial no.5 Customs-DGFT Message Formats License Status Status Date License Number Serial Number as in License “D” - Amendment date The deletion. Gem & Jewellery EPCG NIC-ICES-MSG-DGFT Version 1. License Number Format Format is „PPCNNNNNNN’ Where PP .DGFT Office code C . the same shall be given with status flag – A. if affecting the values in the License Master. otherwise not required Supplementary items of export or import All the parameters of Items of export/import shall be given with License Status Status Date “S” - Amendment date The supplementary items.Category Code NNNNNNN .National Informatics Centre ICES 1. if affecting the values in the License Master.9 Release Date 21/07/2008 Page 24 of 6767 . otherwise not required. the same hall be given with status flag – A. Category Code: LICENSE Category Directory Category Code 1 Category Name Duty exemption Scheme Code 03 05 06 17 18 22 23 24 25 08 11 Scheme name Advance License Advance License for Deemed Exports (Discontinued) DEPB-Post Export Advance License for Annual Requirements Duty Free Replenishment Certificate Duty Free Credit Entitlement Certificate Target Plus Scheme Vishesh Krishi Upaj Yojana DFCE for Status holder Replenishment License EPCG Concessional Duty 05% SION Applicable? Y/N Y/N N Y N N N N N 2 3 Diamond.

5 Customs-DGFT Message Formats N N Import License for negative list of import items Export License Scheme Code Scheme Code 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 41 42 43 44 45 46 47 48 49 49 50 51 52 Description FREE SHIPPING BILL INVOLING REMITTANCE OF FOREIGN EXCHANGE ADVANCE LICENSE WITH ACTUAL USER CONDITION ADVANCE LICENSE FOR INTERMEDIATE SUPPLIES ADVANCE LICENSE ADVANCE RELEASE ORFER ADVANCE LICENSE FOR DEEMED EXPORTS DEPB POST EXPORT DEPB-PRE EXPORTS REPLENISHMENT LICENSE DIAMOND IMPREST LICENSE BULK LICENSE Concessional DUTY EPCG SCHEME ZERO DUTY EPCG SCHEME CCP IMPORT LICENSE FOR RESTRICTED ITEMS OF IMPORTS SPECIAL IMPORT LICENSE EXPORT LICENSE ADVANCE LICENSE FOR ANUAL REQUIREMENT DUTY FREE REPLENISHMENT CERTIFICATE Drawback JOBBING (JBG) EOU/EPZ/SEZ/EHTP/STP Duty Free Credit Entitlement Certificate Target Plus Scheme Vishesh Krishi Upaj Yojana (VKUY) DFCE for Status holder DFIA Focus Market Focus Product High Tech Product EPS DRAWBACK AND ADVANCE LICENSE DRAWBACK AND DFRC DRAWBACK AND ZERO DUTY EPCG DRAWBACK AND CONCESSIONAL DUTY EPCG DRAWBACK AND PRE EXPORT DEPB DRAWBACK AND POST EXPORT DEPB DRAWBACK AND JBG DRAW BACK AND DIAMOND IMPREST LICENSE DRAWBACK AND EOU/EPZ/SEZ EPCG AND ADVANCE LICENSE EPCG AND DFRC EPCG AND JBG NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 25 of 6767 .National Informatics Centre 4 5 Import License –ve List Export License 14 16 ICES 1.

DRAWBACK AND DFRC EPCG. DRAWBACK AND DEPB POST EXPORT EPCG. DRAWBACK AND DIAMOND IMPREST LICENSE EPCG.National Informatics Centre Scheme Code 53 54 55 56 59 71 72 73 74 75 76 79 99 Description ICES 1. DFIA and DBK NFEI (No Foreign Exchange involved) – Exclusive to Customs – NOTTO BE USED by DGFT DGFT Office Code Code 02 03 04 05 06 07 08 09 10 12 13 17 26 30 50 Name Calcutta Bombay Madras New Delhi Cochin Bangalore Ahmedabad Hyderabad Ernakulam Amritsar Jaipur Panjim Vishakhapatnam Ludhiana Kandla Note : DGFT may provide latest directory] LICENSE STATUS CODE F A C P R D S NAME Fresh License Amended Cancelled Suspended Re-instated Item deletion Supplementary item CURRENCY CODES NIC-ICES-MSG-DGFT Version 1. DRAWBACK AND DEEC EPCG.5 Customs-DGFT Message Formats EPCG AND DIAMOND IMPREST LICENSE EPCG AND REPLENISHMENT LICENSE EPCG AND DEPB (POST EXPORTS) EPCG AND DEPB (PRE-EXPORTS) EPCG and DFIA EPCG.9 Release Date 21/07/2008 Page 26 of 6767 . DRAWBACK AND JOBBING EPCG. DRAWBACK AND DEPB (PRE-EXPORT) EPCG.

9 Release Date 21/07/2008 Page 27 of 6767 . <lic> <Control> 0131234567^]01082008^]1^]2^]5^]1^]2^]0^]0^]0^] 0117777777^]01082008^]1^]1^]3^]0^]0^]1^]^]1^] 0113333333^]01082008^]1^]0^]0^]0^]0^]0^]6^]1^] <END_Control> <master> ……… ……… ……… <END_master> <item_export> ------------------------<END_item_export> <item_import> -----------------------<END_item_import> <supmnf> ----------------<END_supmnf> <conditions> ----------------<END_conditions> <co_licency> ----------------<END_co_licency> <sb_item> -----------------------<END_sb_item> NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1.5 Customs-DGFT Message Formats DGFT will adopt the codes used by Customs Message structure: All types of messages can be clubbed together and sent in one single message.

9 Release Date 21/07/2008 Page 28 of 6767 . 3.LIC INDEL62002051301. of records in Table – File No Field Type C Date N N N N N N N N Field Length 25 4 4 4 4 4 4 4 4 File Naming Convention: <Port Code> + <Date>.LIC A delimiter should separate the fields ' ^]' LICENCE CONTROL FILE Sr. DGFT is requested to carry out necessary validation check at their end before transmitting the EDI message to Customs System. of records in Table – Co. No. 2. 7. 5. if were to happen. of records in Table – Conditions No.licaud Important: In order to ensure that there are no rejections in exchange of messages.Items of Import No.Master No. 8. 6. of records in Table . Field Description License/File No Date of issue of License/File No of Record in Table . 1.lecensees No.LIC Example: INDEL42002051301. 10. of records in Table – SB Items No. 9. of records in Table . It is presumed that the contents of document given to the importer/exporter do not differ from the contents transmitted electronically. 4. of records in Table – Supporting Manufacturers No.5 Customs-DGFT Message Formats <file_no> ------<END_file_no> <END_lic> File naming convention: <CUSTOMS PORT CODE>+<Date>+<Serial No>.Items of Export No. the Customs authorities will not be in position to accept such document till the discrepancy on the document or in the electronic message is rectified NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1.

License Number will be used for processing of Bill of Entry and Shipping Bill declarations. The frequency of the message generation has to be agreed upon by DGFT and Customs. if in the acceptable format. File naming convention: DGFT would generate message file Customs site-wise. A Shipping Bill can be considered against more than one license. (??????) ICEGATE application does the validation checks on the file format. alterenately report is forwarded.5 Customs-DGFT Message Formats System implementation  DGFT would generate digitally signed License message once/twice in a day and put in the FTP server at their-end in the specified directory. ICEGATE would pick-up the message file from the FTP Server. before registering the license for utilization against import. The license message constitutes the Shipping Bills.9 Release Date 21/07/2008 Page 29 of 6767 . At the Customs end. the license is accepted and an acknowledgement for transmission to DGFT using the Control Table. the message would be loaded in defined tables in ICEGATE schema and insert record in Control table for processing by ICES If no discrepancy found. DGFT shall account for all items of the SB. An item of a SB will not be considered for more than one License.     License registration at Customs House: No separate registration is required at the Customs Station.National Informatics Centre ICES 1. - - - NIC-ICES-MSG-DGFT Version 1. Refer file-naming convention given above. the Customs process verify the authenticity of the Shipping Bills used for issue of license. DEPB POST EXPORT (Scheme Code . The license is issued for import from a specific Customs Station from where the exports have taken place. which are considered for issue of the license. .6): DGFT issues the license – On the basis of the Shipping Bill information provided by Customs. The file. The valid license is only to be registered.

DEPB license message to be transmitted by DGFT will contain information of Shipping Bills considered.National Informatics Centre ICES 1. In case of discrepancy. The message will be forwarded to the DGFT. 3. 2. 1. No. Paralally. The Shipping Bill data is moved to archival mode. SB information will also be stored in a separate database table for verification of license message. Based on the Shipping Bill data forwarded by Customs. the DGFT would issue an import license. 6. EGM Date Invoice Number Field type N Date C N Date C Field Length 07 06 7 17 NIC-ICES-MSG-DGFT Version 1. The ICES would validate the SB information given along with the license with the Customs information.   The message is forwarded to the DGFT through the ICEGATE. the SB information will be forwarded only after completion of the process. the license is not accepted and a negative acknowledgement is generated. 4.5 Customs-DGFT Message Formats System flow  ICES in the beginning-of-the-day operation would generate Shipping Bill message file for whom the EGM is filed and having items of export under DEPB Scheme. The Shipping Bill data transmitted would also be available for verification of license. The structure of the database will be similar to the message format (CHDG003) with additional parameters: Description of goods exported Sr. Field Description Shipping Bill No Shipping Bill Date Port of Export EGM No.   Validation checks for matching the Shipping Bill information of License with the Customs database: The system implementation procedure will be as follows:  ICES in the end-of-the-day operation generate a message for all those Shipping Bills for which EGM is filed.9 Release Date 21/07/2008 Page 30 of 6767 . Digitally signed message file transmitted to DGFT. In case of provisional assessment of Customs and where market enquiry is called. 5.

as given by DGFT. 10. NO import is permitted against the license other than the port of registration.       NIC-ICES-MSG-DGFT Version 1. As the exports against the Advance License are permitted from any on the Customs Ports. items of export. 11. NO. 8. conditions of license and co-licensy details. On receipt of the license. in the Invoice Description of Item of Exports Scheme Code License No. Provisional exports against the Advance License: The exporter in the SB declaration would provide only the File Number. Monitoring of fulfillment of export obligation by the License holder is the responsibility of the DGFT. The license data would be copied in the Customs tables. ICES 1. the ICES would perform the format validations and data validations. ICES. against which logged Date of logging Advance License Schemes (Scheme Codes: 01/02/03/05) License holder is allowed to export from any of the Customs Ports and import is allowed from a designated Port only. ICES in the beginning-of-the-day operation would generate Shipping Bill message file for transmission to DGFT. 9. The message file generated at the Customs port will also have Date of Registration. Exports are allowed against the Advance License application also. after acceptance of the license message would generate the message file through ICEGATE to the rest of the sites. Items of import.5 Customs-DGFT Message Formats N C C N Date 4 120 02 10 Item Sr.National Informatics Centre 7. the License information has to be transmitted to all ports.9 Release Date 21/07/2008 Page 31 of 6767 . License information transmitted from the Port of registration will be revalidated at each port.  Advance license message to be transmitted by DGFT will have information regarding License Master particulars.

9 Release Date 21/07/2008 Page 32 of 6767 .National Informatics Centre ICES 1.5 Customs-DGFT Message Formats System Implementation System Flow DGFT RO DGFT RO DGFT RO DGFT Central Server (DELHI) DGFT FTP Server ICE GATE Message Exchange Server at Custom House CUSTOMS Indian Customs EDI System Server NIC-ICES-MSG-DGFT Version 1.

„C‟.C. Not Null Any other format of date would be invalid F/N Y/N and not Null Y/N or Null NIC-ICES-MSG-DGFT Version 1..F. „R‟ -Status Codes .National Informatics Centre ICES 1.C Code Customs Notification Number Customs Notification Date Norms fixed (F) / Norms not fixed (N) Transferability Waiver Should be prior to date of receipt. otherwise message will be rejected. „P‟.C. F.) Total CIF Value in F. License should not have been registered with ICES earlier.9 Release Date 21/07/2008 Page 33 of 6767 . Valid Custom Port Directory First two Cs of File No shall match with first two digits of License No. „R‟: The License No should have been registered earlier with ICES.„A‟. DEPB Credit (in Rs. „A‟. No. 1 2 3 Field Description Status Status Date License Number Validation for Scheme „F‟. Validation against the Currency Code Directory Null Should be > Zero Null Null Not Null DGFT shall use the Notification Directory as provided by Customs.C F. „P‟. Check from Scheme Code Directory No check GCA/RPA Validation against IE Code Directory Validation against IE Code Directory Null for Scheme Code 6 Not null & should be greater than Zero Shall be null if Currency Area is „RPA’. Unique and will never be repeated in future. Code Total CIF Value in Rs.5 Customs-DGFT Message Formats License Message – Validation checks Sr. FOB Value in F. 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 22 23 Date of Issue of License Port of Registration File Number Category of License (Scheme Code) Import Validity end date Currency Area IEC Branch Serial Number(as in IEC Database) Export Obligation end date FOB Value in Rs. „C‟. Status code .

SION norms are fixed. FOB Value in FC in License Master details shall tally with the sum total of the same mentioned for each item of export. List of Supporting Manufacturers 1. 9. 05. No.9 Release Date 21/07/2008 Page 34 of 6767 . Conditions Sheet 3. Validated against the directory Valid for scheme codes 01 02. Sr. Field Description Status Status Date License Number Serial Number as in License ITC (HS) Code Description of Product/Item Technical Specifications Quantity Unit of Measurement Code FOB Value in Rs. 3. Same Condition Serial Number should not be repeated for a License. No. F. only once for the item Shall not be prior to the License date Shall not be repeated for a License Validated against the directory 11. Serial Number of the manufacturer should not be repeated for a License.C 12. As above Items of Exports Sr. No of the item in the invoice should not be duplicate An item of a SB will not be considered for more than one License. „A‟.National Informatics Centre ICES 1. Code SION Product Group SION Serial Number Validated against the directory FOB Value in Rs in License Master details shall tally with the sum total of the same mentioned for each item of export. „D‟ Status – F. 03. 14.C. No. Valid if. „S‟. FOB Value in F. 4 5 6 Field Description Port of Export Invoice Number Item Sr. NIC-ICES-MSG-DGFT Version 1. 5. 8. 1. in the Invoice Validation for Scheme code 06 Port of Export in the License and SB shall be same. Validation checks „F‟.5 Customs-DGFT Message Formats Items of export Sr. IE code and branch serial number should be valid IE code as per directory. 6. 13. 2. 4. 7. 10. 2.

21. 10. 6. 15. 19. 4. 12. 8. 11.4 CHDG004 : From : License Acknowledgement Customs to DGFT At Customs end. 18. 17. the control file information . 16. 20. 14. 5.National Informatics Centre ICES 1. 22. Field Description File Name Status Status Date License Number License Date Field Type C C Date C Date C C N C N C N C N C N C N Date C C N C Field Length 50 1 10 10 6 50 4 50 4 50 2 50 2 50 2 50 7 6 17 4 50 Port of Registration License Mater Error Code ITEM SR NO IN PART E ITEM SR NO IN PART E – ERROR CODE ITEM SR NO IN PART C ITEM SR NO IN PART C – ERROR CODE SR NO Of Supporting Manufacturer SR NO Of Supporting Manufacturer – Error Code SR NO Of Conditions SR NO Of conditions – Error Code SR NO Of Co-licensee SR NO Of Co-licensee – Error Code SB Number SB Date Port of Export Invoice Number Item Sr No in Invoice Error Code Error codes : A record can have multiple errors and each code will be separated by delimiter – ‘.5 Customs-DGFT Message Formats 4. 13.LICACK NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 35 of 6767 .’. Sr. 1. File naming convention: <Customs Port Code>+<DATE>+<Serial Number>. 7. 3.No. 9. 2.if not tallied complete message file will be rejected. Refer to Error codes for their explanation. 23.

does not tally with the sum total of the same for items of export FOB Value in FC does not tally with the sum total of the same for items of export CIF Value in Rs. No.5 Customs-DGFT Message Formats ERROR CODES Code 00 01 02 03 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 51 52 53 54 55 56 57 58 71 81 82 92 93 94 95 96 97 DESCRIPTION No error Control file mis-match Data Error Validation Procedure not executed Invalid Status Code Invalid License Number Duplicate License Number Invalid Port of Registration Invalid Scheme Code Invalid Import Validity End Date Invalid Currency Area Invalid IE Code/ IE Code doesn‟t tally with Customs data Invalid Branch Serial Number FOB value in Rs.National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 36 of 6767 ./ Duty Saved is missing/ Additional DEPB credit missing for DEPB License FOB Value in Rs. in the Group does not match with SB Quantity and Unit of measurement does not match with SB NIC-ICES-MSG-DGFT Version 1./ Duty Saved does not tally with the sum total of the same for items of import CIF Value in FC does not tally with the sum total of the same for items of import Invalid FC FOB value in FC Missing / Additional CIF value in FC Missing / Additional Invalid Custom Notification Number Invalid Fixed Norms Items of Export Missing Items of Import Missing Invalid Status Date Invalid License Date Invalid Transferability SB Details Missing ( For DEPB License) SB Item already used License Number missing Duplicate / Invalid Serial Number in License Invalid ITC (HS) Code Invalid Unit of Measurement Code SION Product Group code Missing/Additional SION Serial Number Missing/Additional Item Description for item of export missing Item cannot be deleted as it is the only item in License Quantity Missing / Additional Supporting manufacturer name / address missing Condition Missing Invalid DEPB Amount Item not found in customs database DEPB credit does not tally with sum total of same in SB details Item description does not match DEPB Group Code/Item Sr. Missing / Additional Total CIF value in Rs.

National Informatics Centre ICES 1. Applicable for Air locations Vessel Applicable for Sea locations.2 Port of Export : Refer to Annexure C Note: 1 Flight Number and Flight Date Code and Sailing Date For ICD locations parameters Sailing Date will have no values. The DEPB credit is based on the raw materials used.5 Customs-DGFT Message Formats 4. Mostly such items fall under drug formulations (Example: DEPB Group Code 62 Item Sr. A Shipping Bill Master details Sr. It was informed by DGFT that such license requests would be processed manually.5 CHDG005 : From : Shipping Bill Data Customs to DGFT Customs will generate daily one message for all those Shipping Bills for which EGM is filed and – no provisional assessment of DEPB OR DEPB is finally assessed OR Re-transmission request is received The Shipping Bill message does not include the information of raw material consumed in the manufacture of export item. Vessel Code and 2 NIC-ICES-MSG-DGFT Version 1. 1 2 3 4 5 6 7 8 9 10 Field Description Shipping Bill Number Shipping Bill Date Port of Export IEC Number of Exporter EGM No. 37A. Date of Export (EGM Date) Flight No/Vessel Code Flight Date/Sailing Date Date of LEO Total FOB Value (In Rs. EGM Number. No. 37C and 37D). 37B.9 Release Date 21/07/2008 Page 37 of 6767 .) Field Type N Date C N N Date C Date Date N Field Length 7 06 10 7 15 / 7 15. Nos.

Appraised FOB Value for DEPB purpose IEC of third party Field type N Date C C N C C C N C N N C N N N N C Field Length 07 06 17 4 120 8 02 11. 7. No.C Foreign Currency Code Exchange Rate (In Rs) Unit in Rs Present Market Value (PMV) in Rs. 18. if no change made.9 Release Date 21/07/2008 Page 38 of 6767 . NO. Otherwise NULL value. in the Invoice Description of Item of Exports ITCHS Code Scheme Code Total Quantity Unit of measure code FOB Value In Rs. 2.2 15.4 7.5 Customs-DGFT Message Formats B Details of items of export (As per Shipping Bill – Invoice) Sr.National Informatics Centre ICES 1.2 10.3 03 16. FOB Value in F. 17. 14. 1. 15. Field Description Shipping Bill No Shipping Bill Date Port of Export Invoice Number Item Sr.2 10 credit Foreign Currency code Foreign Currency Code Unit of Measurement Code Appraised FOB Value for DEPB credit purpose IEC of third party : : : : Invoice currency Refer Annexure A Refer to Annexure B The value will be same as FOB value of item.2 03 9. 4. 6. In case of third party export. 8. 10. IEC Of the third party will be given. 13. 11. 16. 5. 9. 3.2 16. 12. : NIC-ICES-MSG-DGFT Version 1.

2. 11. 10. Field Description Shipping Bill No Shipping Bill Date Port of Export Invoice Number Item Sr. 5. 12. No. 12. No. 8. 1. in the Invoice SION Product Group SION Serial Number SION Item of Import Serial Number File No License No Serial No. No. 3. in the Invoice DEPB Group Code Item Sr. 9. D Details of License (Items of import – Part C) Sr. otherwise NULL DGFT shall return the same values in the license message. of Item as on License (Part C) Quantity of import under the license Unit of measure code Field type N Date C C N C C C C N N N C Field Length 07 06 17 4 2 6 3 25 10 03 11. 6. 11. 10. 4. 3.National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 39 of 6767 . 13. 7. 5. Field Description Shipping Bill No Shipping Bill Date Port of Export Invoice Number Item Sr. in the Group File No License No Serial No. 7. of Item as on License (Part E) Quantity of export under the license Unit of measure code Field type N Date C C N C C C N N N C Field Length 07 06 17 4 2 10 25 10 03 11. Number : Valid for Scheme Code – 06 only Null for export under other Schemes Quantity of export under the license & Unit of measurement: In the case of export under DEPB Scheme (Scheme Code – 06) values will be provided for only value cap item. NO.3 03 NIC-ICES-MSG-DGFT Version 1.3 03 DEPB Group Code and Item Sr. 1. NO. 8. 4. 6.5 Customs-DGFT Message Formats C Details of License (Items of export – Part E) An Item can be exported –  Under more than one License (of same scheme)  Under combination Scheme Code (50/51/53/54/55/71 to 76) Quantity of export of the items under each License will be provided in the following format: Sr. 2. 9.

03. 12 And NULL for regular exports NULL for all other Schemes Codes Valid for regular exports under all Scheme Codes except Code – 06 (DEPB Schemes) As per directory provided by DGFT. 03. 05 Valid for provisional exports under Advance licenses schemes/ EPCG Schemes only .05. License Number Category of license : : File naming convention: DGFT+<Port Code>+<EGMDATE>+<Sequence Number>. 05.9 Release Date 21/07/2008 Page 40 of 6767 . No of the item as on License File Number : : : SB Number + SB Date + Port of export NULL for provisional exports under Scheme Codes – 01.01.National Informatics Centre ICES 1. XX/XX/XXX/XXXXX/XXXX/XXXX 12/34/567/99999/AMXX/AMXX Notes: Unique identifier Sr.02.19 Null for export under other Schemes Office Code/ Section Code/ Category/ Serial Number/ Application Period/ Export Period. 02.SB (DDMMYYYY: EGM date) Message Structure <sb> <sb_master> ----------------<END_sb_master> <sb_item> ----------------<END_sb_item> <sb_lic_parte> ---------------<END_sb_lic_parte> <sb_lic_partc> --------- NIC-ICES-MSG-DGFT Version 1.03.18. 02.5 Customs-DGFT Message Formats SION Product Group SION Serial Number File Number Format: : Valid for Scheme Codes – 01. 11.

5 Customs-DGFT Message Formats --------<END_sb_lic_partc> <END_sb> NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 41 of 6767 .

’.9 Release Date 21/07/2008 Page 42 of 6767 . Field Description File Name SITE ID SB NUMBER SB Date INVOICE Number ITEM NO ITEM SR NO IN PART E ITEM SR NO PART C SB LEVEL ERROR CODE ITEM ERROR CODE ITEM SR NO IN PART E – ERROR CODE ITEM SR NO IN PART C – ERROR CODE Field Type C N N Date Date N C C C C C C Field Length 50 07 7 10 Ddmmyyyy 06 06 50 50 50 50 NOTE : Error codes : A record can have multiple errors and each code will be separated by delimiter – ‘. sb_no.5 Customs-DGFT Message Formats 4. 5.No. File naming convention: DGFT+<Customs Port Code>+<DATE>+<Sequence Number>. 8. site id.National Informatics Centre ICES 1. Refer to Error codes for their explanation. 3. In case SB is accepted then only file_name. 4. 11. 10. 9.sb_dt with sb_level_error_code = 0 has to l be sent If child level err is sent then the corresponding key element must be sent Sr.”SB”ACK NIC-ICES-MSG-DGFT Version 1.6 DGCH006: SB Acknowledgement From : DGFT To Customs DGFT has to acknowledge for each Shipping Bill forwarded by Customs. 12. 6. 7. 1. 2.

is missing or invalid invoice Sl. is missing or invalid FOB value in Rs. No.9 Release Date 21/07/2008 Page 43 of 6767 . does not match the sum total of the same for SB items. Invalid Item Sl. is missing Parent record missing Invalid Port of export or does not match file name Invalid IEC No. No.5 Customs-DGFT Message Formats ERROR CODES: Code Description 00 01 02 03 04 05 06 07 08 09 10 11 12 14 16 18 19 21 23 24 28 30 31 33 35 37 40 42 44 46 51 52 55 61 No Error Control File mismatch Data Error Table could not be added due to some error Control File error : Data file indicated is not present Data with this File name already exists Data problem in related record (record being deleted) SB master detail not present SB item detail not present Table could not be added due to duplicate record Data Error in some other related table Invalid SB no. No. Invoice Sl.National Informatics Centre ICES 1. Invoice no. Invalid SB date SB no. is missing or invalid invoice no. Item description is missing or length is not proper Invalid ITCHS Code Invalid Scheme code or Scheme code is missing Total quantity is missing Unit of measurement is missing/Invalid Invalid unit of measurement Exchange rate is missing Invalid Foreign currency Item could not be added Parte could not be added Child record (Item missing) Invalid DEPB Group Code/DEPB Group code is missing/License detail missing NIC-ICES-MSG-DGFT Version 1. Invalid LEO/LEO less than SB date FOB value in Rs.

No. No.5 Customs-DGFT Message Formats Invalid DEPB Group Sl. NIC-ICES-MSG-DGFT Version 1. is missing Invalid License No. Invalid File No./DEPB Group Sl.National Informatics Centre 63 65 74 ICES 1.9 Release Date 21/07/2008 Page 44 of 6767 .

2 F. as given in the license (Part C: Item of Import) INV No Item No 1 1 1 1 1 7 18 20 License no Sl No in Lic qty 1 1 1 1 100 kg 200 kg 200 kg 100 kg 1234567890 1234567890 1234567890 1234567890 The will be represented as123 01/01/2008 E INDEL4 1234567890 1 IEC 600 kg . 14.2 16.9 Release Date 21/07/2008 Page 45 of 6767 . Field Description Port of Import Bill of Entry Number Bill of Entry Date Invoice Number Item Sr. File naming convention: DGFT+<Custom Port Code>+<DDMMYYYY>+<sequence Number>. in invoice License no Sl. 3. 2. who has filed the BE) Quantity Unit of Measurement CIF Value in Rs.C FC Code Duty foregone Field Type C C Date C N C N C N C N N C N Field Length 6 7 ddmmyyyy 17 4 10 4 10 16. 6.C. No. No. 12. No. as given in the license (Part C: Item of Import) IEC (Actual importer. 7. 9.10-12: Example: BE No BE Date 123 123 123 123 01/01/2008 01/01/2008 01/01/2008 01/01/2008 Are as per Sl. 11.National Informatics Centre ICES 1. 1.2 3 16. 4.3 3 16.BE NIC-ICES-MSG-DGFT Version 1.5 Customs-DGFT Message Formats 4. CIF value in F. 8. 10. No. 13. 5.7 CHDG007 : From : Bill of Entry information Customs to DGFT Customs will generate daily one message for all those Bills of Entry for which out of charge is issued A delimiter should separate the fields ' | Sr. Code : Refer to Annexure A Parameters 8.

File naming convention: DGFT+<Port Code>+<DDMMYYYY>. 1. ICEGATE application has to create the control file during creation of message file.9 Release Date 21/07/2008 Page 46 of 6767 . The control file will have one record as per the format given below: Sr. No. IMPORT CONTROL FILE: Out-of-charge. the message is to be generated at the specified time by the ICEGATE application by using the views/table given above. There is no necessity for control table. the control file will be generated with field values as 0. 2. Hence. 3.National Informatics Centre ICES 1. Control file as described below required for sending the message to DGFT. Frequency: Customs would transmit the file once a day.BEAUD NIC-ICES-MSG-DGFT Version 1. if not given on any given day.5 Customs-DGFT Message Formats Control Table: The BE data is to be given to DGFT once a day. Field Description File Name Site ID Number of Records – BE Field Type Character Character Number Field Length 22 6 06 .

3. Refer to Error codes for their explanation. 6.9 Release Date 21/07/2008 Page 47 of 6767 . 1. BE_no.5 Customs-DGFT Message Formats 4. site id.’.No. File naming convention: YYYYMMDDBE. 7. 2. BE_dt with error_code = 0 has to l be sent If child level err is sent then the corresponding key element must be sent Sr. Field Description File Name SITE ID BE NO BE Date INVOICE Number ITEM NO License NO Error Code Field Type C C N Date C N C C Field Length 50 06 7 10 17 4 10 50 NOTE : Error codes : A record can have multiple errors and each code will be separated by delimiter – ‘.ACK NIC-ICES-MSG-DGFT Version 1.8 DGCH008 From : : BE Acknowledgement DGFT To Customs DGFT has to acknowledge for each Bill of Entry forwarded by Customs. 4. 8.National Informatics Centre ICES 1. 5. In case BE is accepted then only file_name.

3.”NSB” NIC-ICES-MSG-DGFT Version 1.5 Customs-DGFT Message Formats 4. 2. Field Description Date (DDMMYYYY) Customs House Code Type of document (SB/BE) Field Type date C C Field Length 06 2 File naming convention: DGFT+<Port Code>+<DATE>. Sr. 1.9 Release Date 21/07/2008 Page 48 of 6767 . No.9 DGCH009 : Non-receipt of message from Customs From : DGFT To Customs DGFT shall generate a message for non-receipt of Shipping Bill/BE information from a given port for the given date in the following format.National Informatics Centre ICES 1.

Sr.nck NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1. 1.10 CHDG010: Non-receipt of acknowledgment from DGFT From : Customs To DGFT Customs will generate a message for non-receipt of acknowledgement for the Shipping Bill information transmitted vide message number CHDG005 to DGFT.9 Release Date 21/07/2008 Page 49 of 6767 .5 Customs-DGFT Message Formats 4. Field Description File Name (Export Control File Name) Field Type C Field Length 22 File naming convention: DGFT+<Port Code>+<EGMDATE>+”SBAUD”. No.

1 Fresh/Final (Message Type: F): New Group Code or Item Code. Valid upto date = Effective date (mentioned in the Amendment message) . No.5 Customs-DGFT Message Formats 4.9 Release Date 21/07/2008 Page 50 of 6767 . the update process would append the entry to the database. the update process would close the existing entry by updating the "Valid up to date" and insert new record. the message shall be transmitted with flag 'F' At the Customs end. Valid up to date: Message Type: Null in all cases A F C Amendment Final/Fresh Closed Amendment (Message Type: A): Rate of credit for an item. if amended through a Notification. if introduced.2 3 2 Field Type C C C C C C N N C C Date Date Final F M K M K M M O O M M X Amendment A M K M K M M O O M M X Close C M K X K X X X X X M X : Field Description Message Type Public Notice Number Group Code Group Name Item Code Brief Description of Item Rate of Benefit (%age) Value capping (in INR) Unit of Measurement DEPB Claim Type Flag Effective Date Valid up to Date Mandatory parameters: For value cap items field . Close (Message Type: C): NIC-ICES-MSG-DGFT Version 1."Value capping in Rs" and "Unit of measurement" are mandatory. 1 2 3 4 5 6 7 8 9 10 11 12 DEPB Directory DGFT To Customs Field Length 1 15 2 40 10 250 12.11 DGCH011 : From Sr.National Informatics Centre ICES 1. the message shall be transmitted with flag "A" At the Customs end.2 12.

the message shall be transmitted with flag 'C'. if de-classified under the DEPB Scheme.9 Release Date 21/07/2008 Page 51 of 6767 .Group Code 62) Benefit is based on value capping File naming convention: DEPYYYYMMDD1. the update process would close the existing entry by updating the "Valid up to date".National Informatics Centre ICES 1.029/2001^]20^]PAINTS^]2^]XXXX^]8^]^]^]2^]08072001^]^] EXAMPLE 3: Closed C^]PN. Valid upto date = Effective date (mentioned in the Amendment message) .039/2001^]20^]^]2^]^]8^]^]^]^]30072001^]^] NIC-ICES-MSG-DGFT Version 1.019/2001^]43^]TEXTILES^]20^]READYMADE GARMENTS^]10^]^]^]2^]20052001^]^] EXAMPLE 2: Amendment A^]PN.1 DEPB Claim type: 2 4 5 Benefit based on % age of FOB Benefit on derived items (Ex: Chemical compositions . At the Customs end.5 Customs-DGFT Message Formats An item.DIR EXAMPLE 1: Fresh F^]PN.

6.notn 4. 1. 6. 2. No. 1. 3.9 Release Date 21/07/2008 Page 52 of 6767 . 8. Field Description License Number License Date Port of registration SB Number SB Date Port of Export Invoice Number Item Number FOB Value Field Length 10 ddmmyyyy 6 7 6 17 4 16. No. 2. 1 2 3 4 Notification Directory Customs to DGFT Field Length 10 Date Date 2 Field Type C Mandatory/ Optional M M O M : Field Description Customs Notification No Notification Effective Date Notification End Date Scheme Code C Whenever the scheme notifications are updated. the message will be forwarded to DGFT File naming convention: <DDMMYYYY>. 9.2 Field Type C Date C N Date C C N N Mandatory/ Optional M M M M M M M M M NIC-ICES-MSG-DGFT Version 1.2 Field Type C Date C C Date N Mandatory/ Optional M M M M M M Shipping Bills associated with EODC: Sr.13 DGCH013 : From EODC Master: Sr. 4. 5. No. 5. 3.5 Customs-DGFT Message Formats 4. 7. 4. EODC Certificate DGFT To Customs : Field Description License Number License Date Port of registration EO fulfilled (Y/N) EODC Date (dd/mm/yyyy) Total FOB Value Field Length 10 ddmmyyyy 6 1 16.12 CHDG012 : From Sr.National Informatics Centre ICES 1.

File naming convention: <CUSTOMS PORT CODE>+<Date>+<Serial No>. the ICES application would validate against the License and SB information. bond will be discharged. ICES would generate an positive acknowledgement OR negative acknowledgement. On acceptance of EODC.EOD NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 53 of 6767 .National Informatics Centre ICES 1...5 Customs-DGFT Message Formats On receipt of the message. receipt of EODC would be marked.

National Informatics Centre ICES 1. 4.5 Customs-DGFT Message Formats 4. 5.9 Release Date 21/07/2008 Page 54 of 6767 . Message Format : Application at the ICEGATE shall generate the acknowledgement message in the following format from the information available in tables – EODC_MASTER and EODC_SB Sr. 8. 9. 6. 7.14 CHDG014 : From : EODC acknowledgement Customs to DGFT On receipt of the EODC message from DGFT. 2. the Customs will generate an acknowledgement. It will contain – EODCs accepted (valid entries) and the rejected ones with error code.ERR NIC-ICES-MSG-DGFT Version 1. 11. 1. No. 3. Field Description File_name_of_DGFT License_Number License_Date Field Type C C Date Field Length 60 10 File name of DGFT License Number License Date Port_of_registration EODC_Date SB_Number SB_Date Port_of_Export Invoice_No Item_No ERR_CD C Date N Date C 1C N C 6 7 6 17 4 50 Port of registration EODC Date Error Code List of Error Codes: Message ID CHDG014 CHDG014 CHDG014 CHDG014 CHDG014 CHDG014 Error Code 00 01 02 03 04 05 Error Description EODC accepted EODC duplicate File naming convention <CUSTOMS PORT CODE>+<Date>+<Serial No>. 10.

National Informatics Centre ICES 1.9 Release Date 21/07/2008 Page 55 of 6767 .A. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Currency Code ATS AUD BEF CAD DKK FRF HKD ITL JPY MYD NLG NOK SGD CHF SEK GBP USD RUR INR DEM THB NZD AED EUR Currency Name AUSTRIAN SCHILLINGS AUSTRALIAN DOLLARS BELGIUM FRANCS CANADIAN DOLLARS DANISH KRONERS FRENCH FRANCS HONG KONG DOLLARS IATALIAN LIRE JAPANESE YEN MALAYSIAN DOLLARS NETHERLANDS GUILDERS NORWEGIAN KRONERS SINGAPORE DOLLARS SWISS FRANCS SWEDISH KRONERS POUND STERLING USA DOLLARS USSR ROUBLE INDIAN RUPEE DEUTSCHE MARKS THAILAND BAHT NEW ZEALAND DOLLAR U.No. DIRHAMS EURO NIC-ICES-MSG-DGFT Version 1.5 Customs-DGFT Message Formats Annexure A Currency Code Directory S.E.

No.National Informatics Centre ICES 1. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Unit Code BOX BTL BUN CBM CCM CMS DOZ DRM FTS GGR GMS GRS GYD KGS KLR KME LBS LTR MTR MTS NOS PAC PCS QTL RLS Unit Name BOX BOTTLES BUNCHES CUBIC METER CUBIC CENTIMETER CENTIMETER DOZEN DRUM FEET GREAT GROSS GRAMS GROSS GROSS YARDS KILOGRAMS KILOLITER KILOMETERS POUNDS LITERS METER METRIC TON NUMBER PACKS PIECES QUINTAL ROLLS NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 56 of 6767 .5 Customs-DGFT Message Formats Annexure B Unit of Measurement Code Directory S.

No. Tughlakabad Patparganj Jaipur Ludhiana ICD Tuticorin Raxaul LCS Petrapole LCS Ballabh Garh. ICD Cochin CH Mangalore CH Trivandrum Air Cargo Vizag.5 Customs-DGFT Message Formats Annexure C Customs Port Code Directory S.National Informatics Centre ICES 1. Mundra Kandla CH Port Code INMAA4 INBOM4 INDEL4 INCCU4 INCCU1 INBLR4 INHYD4 INMAA1 INBOM1 INNSA1 INMRM1 INSBI6 INCOK1 INNML1 INTRV4 INVTZ1 INTKD6 INPPG6 INJAI6 INLDH6 INTUT1 INRXL8 INPTP8 INFBD6 INLDH6 INMUN1 INIXY1 NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 57 of 6767 . ICD Ludhiana. OWPL . Port Name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Chennai Air Sahar Air Delhi Air Kolkata Air Kolkata Sea Bangalore Air Cargo Hyderabad Air Cargo Chennai Sea Mumbai Sea Nhava Sheva Goa CH Ahmedabad.ICD GAPL.

CONCOR. Port Name 28 29 30 31 32 33 34 35 36 Ahmedabad Air Cargo Mulund CFS Bangalore ICD Kakinada Port Hyderabad ICD Pitampur ICD Tuticorin ICD Garhi Harsaru ICD Ludhiana.National Informatics Centre S.5 Customs-DGFT Message Formats Port Code INAMD4 INMUL6 INWFD6 INKAK1 INSNF6 ININD6 INTUT6 INGHR6 INLDH6 NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 58 of 6767 . ICD ICES 1.No.

9 Release Date 21/07/2008 Page 59 of 6767 . unit of measurement NIC-ICES-MSG-DGFT Version 1. description.5 Customs-DGFT Message Formats Annexure D ITC (HS) Code Directory DGFT shall provide ITC (HS) code directory in the following format: 1 2 3 4 2 Digit Code and description 4 digit code and description 6 digit code and description 8 digit code.National Informatics Centre ICES 1.

5 Customs-DGFT Message Formats NOTN ---------032/97 048/2000 203/92 204/92 104/93 079/95 080/95 148/95 149/95 106/95 107/95 030/97 031/97 036/97 077/98 050/2000 051/2000 048/99 160/92 122/93 110/95 111/95 111/95 028/97 029/97 029/97 049/2000 160/92 046/2002 043/2002 044/2002 047/2002 055/2003 054/2003 053/2003 056/2003 031/2004 093/2004 090/2004 091/2004 092/2004 094/2004 097/2004 097/2004 053/2003 032/2005 041/2005 009/2006 040/2006 SLNO ---------.9 Release Date 21/07/2008 Page 60 of 6767 .1 J 1 R 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 1 D 2 G 1 G 1 G 1 G 2 G 1 G 1 G 2 G 1 G 1 G 1 R 1 D 1 G 1 D 1 G 1 H 1 H 1 D T 1 D 1 R 1 D 1 H 1 D 1 G 2 G 1 F 1 T 1 K F 1 I A NOTN_DT NOTN_ENDT ----------------01-sep-01 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 28-feb-02 22-apr-02 28-feb-02 28-feb-02 22-apr-02 01-apr-03 01-apr-03 01-apr-03 01-apr-03 09-jul-04 10-sep-04 10-sep-04 10-sep-04 10-sep-04 10-sep-04 17-sep-04 17-sep-04 10-jan-06 08-apr-05 09-may-05 01-mar-06 01-may-06 NIC-ICES-MSG-DGFT Version 1.National Informatics Centre ICES 1.

5 Customs-DGFT Message Formats 073/2006 073/2006 1 T T 10-jul-06 10-jul-06 NIC-ICES-MSG-DGFT Version 1.9 Release Date 21/07/2008 Page 61 of 6767 .National Informatics Centre ICES 1.

Mail Phone Fax : : : sastry@nic.Block.S.National Informatics Centre ICES 1. SASTRY Deputy Director General National Informatics Centre Department of Information Technology Ministry of Communication & Information Technology A.5 Customs-DGFT Message Formats For feedback. CGO Complex Lodhi Road New Delhi – 110003 E.9 Release Date 21/07/2008 Page 62 of 6767 .in 011-24366350 011-436 2628 011-436 4873 NIC-ICES-MSG-DGFT Version 1. please contact : A.