Draft P R O T O C O L on electronic information exchange between the Eurasian Economic Union and its Member States, of the one part, and the Socialist Republic of Viet Nam, of the other part, within the Electronic Origin Certification and Verification System The Governments of the Member States of the Eurasian Economic Union (hereinafter referred to as “the EAEU Member States”) and the Eurasian Economic Union, of the one part, and the Government of the Socialist Republic of Viet Nam (hereinafter referred to as “Viet Nam”), of the other part (hereinafter referred to as “the Parties”): Recalling Article 4.29 (Development and Implementation of Electronic Origin Certification and Verification System) of the Free Trade Agreement between the Eurasian Economic Union and its Member States, of the one part, and the Socialist Republic of Viet Nam, of the other part, on 29 May 2015; Welcoming the reduction of the costs relating to the documentary proof of origin used for the purposes of application of tariff preferences; Aiming at simplifying the procedures and reducing the time for the application of tariff preferences; and Desiring to strengthen cooperation between the customs authorities and the bodies and organisations authorised to issue certificates of origin of the Parties, HAVE AGREED as follows: Article 1 Definitions For the purposes of this Protocol: “Authorised Body” means a body or an organisation authorised by the EAEU Member State or by Viet Nam to issue a certificate of origin, generate and maintain information resources containing information on issued certificates of origin, and to provide information on certificates of origin, for their verification in response to the requests of the customs authorities; 2 “Integrated information system of the EAEU” means a set of geographically distributed state information resources and information systems of authorised authorities, information resources and information systems of the Eurasian Economic Commission, combined by the national segments of the EAEU Member States and the integration segment of the Eurasian Economic Commission; and “National Single Window of Viet Nam” means the mechanism of Viet Nam which allows the customs declarants to send the information and electronic documents for completion of customs procedures and procedures of state management agencies related to exported and imported goods through an integrated information system. Article 2 Transmission of Information 1. For the purpose of this Article, the exchange of information shall be carried out via the Integrated Information System of the EAEU and the National Single Window of Viet Nam based on the requirements of the Technical Specifications specified in the Annex to this Protocol. 2. The Authorised Body of Viet Nam shall transmit to the relevant central customs authority of the EAEU Member States the information contained in the certificates of origin issued for goods exported from the territory of Viet Nam to the territory of this EAEU Member State. 3. The relevant Authorised Body of the EAEU Member State shall transmit to the central customs authority of Viet Nam the information contained in the certificates of origin issued for goods exported from the territory of this EAEU Member State to the territory of Viet Nam. Article 3 Confidentiality All information provided in accordance with this Protocol shall be treated by the Parties as confidential in accordance with their respective domestic laws and regulations.
It shall not be disclosed by the customs authorities of a Party without the written permission of the Authorised Bodies of the other Party which provided such information except to the extent that it may be required to be disclosed in the context of judicial proceedings. 3 Article 4 Amendments 1. This Protocol may be amended by mutual consent of the Parties. 2. Such amendments shall be formalised by separate protocols and constitute an integral part of this Protocol. Article 5 Consultations 1. Any matters related to the implementation of this Protocol shall be settled through consultations or negotiations between the Parties. 2. If a Party considers that the matter cannot be settled through consultations or negotiations as provided for in paragraph 1 of this Article, that Party shall have the right to seek resolution in the Joint Committee established in accordance with Article 1.4 (Joint Committee) of the Free Trade Agreement between the Eurasian Economic Union and its Member States, of the one part, and the Socialist Republic of Viet Nam, of the other part, on 29 May 2015. Article 6 Entry into Force 1. This Protocol shall enter into force on the date of receipt, through diplomatic channels, of the last written notification certifying that the Parties have completed their respective internal legal procedures necessary for entry into force of this Protocol. 2. The exchange of notifications provided for in paragraph 1 of this Article shall be performed by Viet Nam and the Eurasian Economic Commission as the custodian of this Protocol authorised by the Republic of Armenia, the Republic of Belarus, the Republic of Kazakhstan, the Kyrgyz Republic and the Russian Federation. DONE at , this day of 20___, in two originals in the English language, both texts being equally authentic. 4 For the Government of the Republic of Armenia For the Government of the Socialist Republic of Viet Nam For the Government of the Republic of Belarus For the Government of the Republic of Kazakhstan For the Cabinet of Ministers of the Kyrgyz Republic For the Government of the Russian Federation For the Eurasian Economic Union Annex to the Protocol on electronic information exchange between the Eurasian Economic Union and its Member States, of the one part, and the Socialist Republic of Viet Nam, of the other part, within the Electronic Origin Certification and Verification System T E C H N I C A L S P E C I F I C A T I O N Pages 118 2 I. Purpose of the document These Technical Specifications set technical requirements and conditions for the implementation of the electronic information exchange between the central customs authorities of the Member States of the Eurasian Economic Union (hereinafter referred to as “the Member States”, “the Union”) and of the Socialist Republic of Viet Nam within the Electronic Origin Certification and Verification System (hereinafter referred to as “the Parties”, “the EOCVS”) in accordance with Article 4.29 of the Free Trade Agreement between the Eurasian Economic Union and its Member States, of the one part, and the Socialist Republic of Viet Nam, of the other part, dated May 29, 2015 (hereinafter referred to as “the Agreement”).
These Technical Specifications define participants, procedures and regulations of the electronic information exchange, content and structure of transmitted information and messages, used classifiers and directories, security requirements for information exchange and technical aspects and interaction parameters within the EOCVS for exchanging information on certificates of origin issued by the authorized bodies of one Party and used by the customs authorities of the other Party in order to verify validity and content of the issued certificates of origin. 3 II. Chronology of the document’s revisions Number of revision Date of revision Description of the changes Initiator of the changes 01.00 24.09.2017 First version of the document Eurasian Economic Commission 15.7 13.12.2017 Draft for 3th round of negotiations Eurasian Economic Commission 15.8 21.12.2017 Results of 3th round of negotiations are implemented Joint working group 15.10 28.02.2018 Comments and proposals of Vietnamese Side are implemented Joint working group 15.11 02.03.2018 The results of negotiations on exchange of customs information are included Eurasian Economic Commission 16.00 01.09.2021 The results of negotiations reached during the Subcommittee Meeting on Rules of Origin in December 2019 are included Eurasian Economic Commission 17.00 13.11.2023 The results of negotiations reached during the fifth session of the Joint Committee in November 2023 are included Eurasian Economic Commission III.
Terms and abbreviations The following terms and definitions are used in these Technical Specification: “SOAP” (Simple Object Access Protocol) – message-exchange protocol in the distributed computing environment; “UML” – Unified Modeling Language; “UUID” – Universally Unique Identifier; “XML” (Extensible Markup Language) – recommended by the World Wide Web Consortium (W3C) Extensible Markup Language; “Asynchronous Interaction” – a kind of electronic data exchange, in which the Sender resumes his work immediately after sending the message, without waiting for a response from the receiver; 4 “Business process” – a set of interrelated operations and procedures for implementation of the electronic information exchange; “Verification” – the procedure for confirming the authenticity of the certificate of origin; “External Gateway” – a subsystem of the Integrated information system of the Union that provides interaction with the National Single Window of Viet Nam; “Information Protection” – development and implementation of a set of legal, organizational and technical measures to identify, achieve and maintain the confidentiality, integrity and availability of information and processing facilities in order to eliminate or minimize unacceptable risks for the participants of information exchange; “Initiator” – a participant of electronic information exchange initiating the transaction; “Information system” – a set of information technologies and technical means to ensure the processing of information resources; “Information resource” – an ordered set of documented information (databases, other information arrays) contained in Information Systems; “Communication channel” – the unidirectional network connection for transmitting electronic messages; “Classifier” – a systematic, structured and codified list of names of items of classification; “Commission” – the Eurasian Economic Commission which is a permanent regulatory body of the Eurasian Economic Union in accordance with the Treaty on the Eurasian Economic Union dated May 29, 2014; “Integrated information system of the Union” – a set of geographically distributed state information resources and information systems of authorized authorities, information resources and information systems of the Eurasian Economic Commission, combined by the national segments of the Member States of the Eurasian Economic Union and the integration segment of the Eurasian Economic Commission; “National Single Window of Viet Nam” – the mechanism which allows customs 5 declarant on the Viet Nam side to send information and electronic documents for performing of customs procedures and procedures of state management agencies related to exported and imported goods, as well as which allows the Authorised Bodies of Viet Nam to receive the information necessary for performing of customs procedures, providing the information exchange with the external gateway of the Integrated information system of the Union; “Business Process Operation” – a regular, repetitive action, which is part of the range of functions, tasks of a certain Participant of the Business Process; “Control Error” – a type of exception signals that occurs when the notice received by the Respondent is checked, or the waiting time of the notice that the Respondent accepts the received information for processing expires; “Business process procedure” – a set of interrelated operations performed by participants of the business process and aimed at solving a specific task within a business process; “Respondent” – a participant of electronic information exchange exc
hanging messages with the Initiator within the transaction; “Service” – the process of providing users with information technology resources to ensure the performance of their business functions, which has the ability to perform the required functions in a given period of time; “Certificate of origin” – certificate of origin form EAV issued by an authorized body of the Party in accordance with Section 2 of Chapter 4 of the Agreement; “Message” – a formalised information transmitted from the sender to the receiver using information and telecommunications networks; “Directory” – a systematic, structured and codified list of information, that is homogeneous in its content or substance; “Transaction” – an elementary information interaction between two participants of business process, which is carried out by each participant within its Business Process Operation; “Participant of the business process” – a participant of electronic information exchange within the business process. 6 In order to provide clear presentation of transferred information and message structures, tables are used. These tables contain the following columns: “requisite name / element” – common or official verbal mark of an electronic information requisite or a message element; “requisite description / description” – a text defining the meaning (semantology) of an electronic information requisite or a message element; “data type” – a verbal mark of possible values of an electronic information requisite or a message element; “mult.” – requisite multiplicity – necessity (optionality) and the number of possible requisite or message element repetitions. To indicate the necessity of filling electronic information or message element structure requisites, the following notations are used in “mult.” column: 1 – a requisite (element) is obligatory, no repetitions are allowed; n – a requisite (element) is obligatory, shall be repeated n times, n > 1; 0..1 – a requisite (element) is optional, no repetitions are allowed; 0..* – a requisite (element) is optional, can be repeated without restrictions; 0..m – a requisite (element) is optional, can be repeated no more than m times, m > 1; 1..* – a requisite (element) is obligatory, can be repeated without restrictions; n..* – a requisite (element) is obligatory, shall be repeated at least n times, n > 1; n..m – a requisite (element) is obligatory, must be repeated at least n times and not more than m times, n > 1, m > n. IV. General information 4.1 General principles of the electronic information exchange Electronic information exchange within the EOCVS is intended to ensure the possibility to verify authenticity, issuance and content of the issued certificates of origin. EOCVS is developed to create databases of certificates of origin issued by authorized bodies of exporting countries available for customs authorities of importing 7 countries to verify the issuance and the content of issued certificates of origin. Information from certificates of origin is exchanged between the participants within the EOCVS on a regular basis by means of electronic messages exchange. Participants of electronic information exchange ensure the development and maintenance of structured information resources containing current information on certificates of origin, as well as information systems that support services for electronic information exchange.
Requirements for composition and structure of data used in data exchange are defined based on international standards and generally accepted initiatives in the field of electronic data exchange (including the Data Model of the World Customs Organization). These Technical Specifications do not include requirements for unification of database structures and rules for their organization and functioning. Such requirements are defined at the national level. Electronic information exchange participants shall protect transmitted information (including protection of information authenticity and integrity), as well as protect information from unauthorised access, destruction, change and prevent inappropriate storage. Electronic information exchange participants submitting information shall ensure the completeness and correctness of information on issued certificates of origin provided within the EOCVS to enable the participants receiving information to check the issuance of certificates of origin and the authenticity of information contained. Electronic information exchange participants shall provide 24-hour functioning of information resources and information systems, as well as related services. 4.2. Participants of electronic information exchange The electronic information exchange involves: 1. Central customs authorities of the Member States and Viet Nam receiving information on the issued certificates of origin for their verification: The State Revenue Committee of the Republic of Armenia; The State Customs Committee of the Republic of Belarus; 8 The State Revenue Committee of the Ministry of finance of the Republic of Kazakhstan; The Customs Service under the Ministry of Finance of the Kyrgyz Republic; The Federal Customs Service (the Russian Federation); The Ministry of Finance (General Department of Viet Nam Customs) of the Socialist Republic of Viet Nam. 2. Authorized bodies of the Member States and Viet Nam providing information on certificates of origin: The Chamber of Commerce and Industry of the Republic of Armenia; The Chamber of Commerce and Industry of the Republic of Belarus; The National Chamber of Entrepreneurs of the Republic of Kazakhstan; The Chamber of Commerce and Industry of the Kyrgyz Republic; The Chamber of Commerce and Industry of the Russian Federation; The Ministry of Industry and Trade of the Socialist Republic of Viet Nam. 4.3. The main technical solutions Electronic information exchange within the EOCVS is carried out by its participants using the Integrated Information System of the Union (hereinafter referred to as “the IIS”) and the National Single Window of Viet Nam. The information transmitted by the authorized bodies of Viet Nam, using the National Single Window of Viet Nam facilities through the External Gateway services is received by the IIS and then it is routed to the central customs authorities of the Member States through the relevant national segments of the Member States. The information transmitted by the authorized bodies of the Member States through the relevant national segments of the Member States, is transmitted to the IIS, enters the External Gateway and then it is transmitted through the services of the National Single Window of Viet Nam to the customs authorities of Viet Nam. Electronic information exchange within the EOCVS is carried out by its participants at the logic levels, such as transport, technological and application levels.
Procedures of electronic information exchange at the transport level between the External Gateway and the National Single Window of Viet Nam ensure data delivery 9 via HTTP protocol. Electronic information exchange between the External Gateway and the National Single Window of Viet Nam at the technological level is implemented by means of messages in the SOAP format. Procedures of electronic information exchange at the application level provide exchanging of electronic data (hereinafter referred to as “the applied data”) between the participants of electronic information exchange through messaging. Electronic information exchange at the application level is carried out by asynchronous interaction in which the sender resumes his work immediately after sending the message without waiting for the response from the recipient. The requirements to the structure and format of messages as well as the procedure of messaging at the technological level are established in accordance with Sections VI and VII of these Technical Specifications. 4.4 Requirements for unique identification of information A unique identifier is assigned to each document in electronic form used within the electronic information exchange. The following information is used as a unique identifier of the certificate of origin issued by the authorized body of the Party: Registration number of the certificate of origin; Certificate of origin type; Country of issuance; Date of certification (issuance of the certificate of origin); The unique identifier of an electronic message specified in the header block at the technological level is the UUID electronic message identifier as RFC 4122 Specification (http://www.ietf.org/rfc/rfc4122.txt). Cohesiveness of electronic messages at the technological level is determined by the identifier of cohesive message sent in the header block. 10 V. Description of business processes of electronic information exchange (information exchange regulations) 5.1. Description of electronic information exchange participants' roles within business process implementation The roles of business process participants within the EOCVS are listed in Table 1. Table 1 The list of business process participants' roles Designation Name Description ESS.VN.ACT.001 authorized body-information owner an authorized body of an exporting country which collects, stores and submits current information on certificates of origin to a receiving customs authority ESS.VN.ACT.002 customs authority-information receiver a customs authority of an importing country which receives, processes and stores certificates of origin submitted by authorized owning body Within the EOCVS the authorized bodies develop and maintain their own information resources containing electronic information on certificates of origin. During business process execution customs authorities-information receivers develop and maintain the information resources containing electronic information about certificates of origin provided by authorized bodies-information owners. Business process procedures are provided in Table 2. 11 Table 2 Business process procedures Designation Name ESS.VN.PRC.001 providing information on the issued certificate of origin ESS.VN.PRC.002 receiving information on the certificate of origin Description of the business process structure is shown in Figure 1.
Provision of information on the issued certificate of origin (ESS.VN.JRC.001) Customs authority- information receiver (ESS.VN.ACT.002) Receiving information on the certificate of origin (ESS.VN.PRC.002) Authorized body- information owner (ESS.VN.ACT.001) «Participation» «Participation» «Participation» «Participation» Figure 1. Business process structure 5.2 Business process procedures 5.2.1. The procedure “Providing information on the issued certificate of origin” The procedure “Providing information on the issued certificate of origin” shall be carried out within 4 hours after the authorized body-information owner performs one of the following procedures: issuance of the original certificate of origin; issuance of the duplicate of certificate of origin; 12 issuance of the certificate of origin in substitution of the original certificate of origin; annulment (recall) of the previously issued original certificate of origin, the duplicate of certificate of origin, or the certificate of origin in substitution of the original certificate of origin; inclusion of information related to it in the information resource containing information about certificates of origin. The scheme of the procedure “Providing information on the issued certificate of origin” is provided in Figure 2. : Authorized body-information owner : Customs authority-information receiver Transferring information on the issued certificate of origin (ESS.VN.OPR.001) : certificates of origin [information on the issued certificate of origin is transferred] Receiving and processing of information on the issued certificate of origin (ESS.VN.OPR.002) Receiving and processing of the notice on the results of processing of information on the issued certificate of origin (ESS.VN.OPR.003) : certificates of origin [information on the issued certificate of origin is received] Figure 2. Scheme of the procedure “Providing information on the issued certificate of origin” 13 The operation “Transferring information on the issued certificate of origin” is carried out first, followed by preparing and providing information on the issued (annulled, recalled) certificate of origin to the receiving customs authority by the authorized owning body. When the receiving customs authority receives information on the issued (annulled, recalled) certificate of origin, the procedure “Receiving and processing of information on the issued certificate of origin” shall be carried out, followed by receiving, processing and providing notice on the results of processing to the authorized owning body by the receiving customs authority. When the authorized owning body receives the notice on the results of processing from the receiving customs authority, the procedure “Receiving and processing of the notice on the results of processing of information on the issued certificate” is carried out. Based on the results of this operation, the authorized owning body processes the received notice. The result of the procedure “Providing information on the issued certificate of origin” is the provision of information on the issued (annulled, recalled) certificate of origin by the authorized owning body and its processing by the receiving customs authority. The list of operations carried out under the procedure “Providing information on the issued certificate of origin” is given in Table 3.
Table 3 List of business process operations carried out within the procedure “Providing information on the issued certificate of origin” (ESS.VN.PRC.001) Designation Name Description ESS.VN.OPR.001 transferring information on the issued certificate of origin provided in Table 4 ESS.VN.OPR.002 receiving and processing of information on the issued certificate of origin provided in Table 5 ESS.VN.OPR.003 receiving and processing of the notice on the results of processing of information on the issued certificate of origin provided in Table 6 14 The description of the operation “Transferring information on the issued certificate of origin” (ESS.VN.OPR.001) is given in Table 4. Table 4 Description of the operation “Transferring information on the issued certificate of origin” (ESS.VN.OPR.001) No. Element Description 1 Designation ESS.VN.OPR.001 2 Operation Transferring of information on the issued certificate of origin 3 Executor authorized body-information owner 4 Execution conditions carried out within 4 hours after the certificate of origin is issued (annulled, recalled), and the executor includes information on it into the information resource 5 Restrictions the format and structure of the information provided shall be in accordance with the description provided in Appendix B 6 Operation description the executor prepares information on the issued (annulled, recalled) certificate of origin and provides the receiving customs authority with it 7 Results information on the issued (annulled, recalled) certificate of origin is prepared and transferred to the receiving customs authority The description of the operation “Receiving and processing of information on the issued certificate of origin” (ESS.VN.OPR.002) is given in Table 5. Table 5 Description of the operation “Receiving and processing of information on the issued certificate of origin” (ESS.VN.OPR.002) No. Element Description 1 Designation ESS.VN.OPR.002 2 Operation receiving and processing of information on the issued certificate of origin 15 No. Element Description 3 Executor customs authority-information receiver 4 Execution conditions carried out after the executor receives information on the issued (annulled, recalled) certificate of origin (the operation “Transferring information on the issued certificate of origin” (ESS.VN.OPR.001)) 5 Restrictions the format and structure of provided information shall comply with the description provided in Appendix B 6 Operation description the executor receives and checks information on the issued (annulled, recalled) certificate of origin and provides the authorized owning body with the notice on the results of information processing 7 Results information on the issued (annulled, recalled) certificate of origin is processed, and the authorized owning body is provided with the notice on the results The description of the operation “Receiving and processing of the notice on the results of processing of information on the issued certificate of origin” (ESS.VN.OPR.003) is given in Table 6. Table 6 Description of the operation “Receiving and processing of the notice on the results of processing of information on the issued certificate of origin” (ESS.VN.OPR.003) No.
Element Description 1 Designation ESS.VN.OPR.003 2 Operation receiving and processing of the notice on the results of processing of information on the issued certificate of origin 3 Executor authorized body-information owner 4 Execution conditions carried out after the executor receives the notice on the results of processing of information (the operation “Receiving and processing of information on the issued certificate of origin” (ESS.VN.OPR.002)) 5 Restrictions the format and structure of the information provided shall be in accordance with the description provided in Appendix B 16 No. Element Description 6 Operation description the executor receives and processes the notice on the results of processing of information on the issued (annulled, recalled) certificate of origin 7 Results the notice on the results of processing of information is processed 5.2.2. The procedure “Receiving information on the certificate of origin” If necessary the receiving customs authority can generate a request to confirm the authenticity of a certain certificate of origin. The scheme of the procedure “Receiving information about the certificate of origin” is given in Figure 3. The procedure “Receiving information on the certificate of origin” is carried out by the receiving customs authority upon the request, if the information on the issued certificate of origin is necessary. The authorized body-information owner, having received such a request, generates the response containing the requested data or information about their absence. : Customs authority-information receiver : Authorized body-information owner Request for information about the certificate of origin (ESS.VN.OPR 004) : certificates of origin [information on the issued certificate of origin is requested] Provision of information on the certificate of origin (ESS.VN.OPR.005) Receiving and processing of information on the certificate of origin (ESS.VN.OPR.006) : certificates of origin [information on the issued certificate of origin is provided] : certificates of origin [information on the issued certificate of origin is absent] Figure 3. Scheme of the procedure “Receiving information on the certificate of origin” 17 The operation "Requesting information about the certificate of origin" is carried out first, according to the results of which the customs recipient body forms and sends to the authorized authority-owner of the information request to provide information about the certificate of origin. When the request for providing information on the certificate of origin is received by the authorized owning body, the operation “Providing information on the certificate of origin” is carried out, based on the results of which the authorized owning body generates and sends current information on the certificate of origin or notice on absence of information complying with the parameters of the request to the receiving customs authority. When the receiving customs authority receives current information on the certificate of origin or the notice on absence of information complying with the parameters of request, the operation “Receiving and processing of information on the certificate of origin” is carried out, followed by the processing of received information by the receiving customs authority. The result of the procedure “Receiving information on the certificate of origin” is the receiving and processing of current information on the certain certificate of origin or notice on the absence of information complying with the request parameters by the receiving customs authority.
The list of business process operations carried out within the procedure “Receiving information on the certificate of origin” (ESS.VN.PRC.002) is given in Table 7. 18 Table 7 List of business process operations carried out within the procedure “Receiving information on the certificate of origin” (ESS.VN.PRC.002) Designation Name Description ESS.VN.OPR.004 requesting for information about the certificate of origin provided in Table 8 ESS.VN.OPR.005 providing information about certificate of origin provided in Table 9 ESS.VN.OPR.006 receiving and processing of information on the certificate of origin provided in Table 10 The description of the operation “Requesting for information on the certificate of origin” (ESS.VN.OPR.004) is given in Table 8. Table 8 Description of the operation “Requesting for information on the certificate of origin” (ESS.VN.OPR.004) No. Element Description 1 Designation ESS.VN.OPR.004 2 Operation requesting for information on the certificate of origin 3 Executor customs authority-information receiver 4 Execution conditions performed if necessary to receive information about the certificate of origin by the customs authority- information receiver 5 Restrictions the format and structure of the request shall be in accordance with the description given in Appendix B 6 Operation description the executor generates and sends a request for providing information about the certificate of origin to the authorized body-information owner 7 Results the request for providing information about the certificate of origin is sent to the authorized body- information owner 19 The description of the operation “Providing information on the certificate of origin” (ESS.VN.OPR.005) is given in Table 9. Table 9 Description of the operation “Providing information on the certificate of origin” (ESS.VN.OPR.005) No. Element Description 1 Designation ESS.VN.OPR.005 2 Operation providing information on the certificate of origin 3 Executor authorized body-information owner 4 Execution conditions carried out after the request for providing information on the certificate of origin (the operation “Requesting for information on the certificate of origin” (ESS.VN.OPR.004)) is received 5 Restrictions the format and structure of the request and the provided information shall be in accordance with the description given in Appendix B 6 Operation description the executor checks the received request, generates and sends current information on the certificate of origin or the notice on absence of information complying with the request parameters, indicating the code of the processing result, corresponding to the absence of information, to the receiving customs authority 7 Results information on the certificate of origin or the notice on absence of information complying with the request parameters is provided to the receiving customs authority The description of the operation “Receiving and processing of information on the certificate of origin” (ESS.VN.OPR.006) is given in Table 10. 20 Table 10 Description of the operation “Receiving and processing of information on the certificate of origin” (ESS.VN.OPR.006) No.
Element Description 1 Designation ESS.VN.OPR.006 2 Operation receiving and processing of information on the certificate of origin 3 Executor customs authority-information receiver 4 Execution conditions carried out after information on the certificate of origin or notice on the absence of information complying with the request parameters (the operation “Providing information on the certificate of origin” (ESS.VN.OPR.005)) is provided 5 Restrictions the format and structure of the provided information shall be in accordance with the description given in Appendix B 6 Operation description the executor processes the received information 7 Results the information about the certificate of origin or the notification on absence of information complying with the parameters of the request is received and processed 5.3. Regulation of interaction during the implementation of the business process Information interaction of participants during the implementation of the business process is carried out through transactions. Information interaction defines the order of execution of transactions. Each transaction is the exchange of messages between the participants of electronic information exchange in order to synchronize the statuses of information resources containing information on certificates of origin. For each information interaction, the relationships between operations and the corresponding transactions are defined. Within the operation (the initiating operation) one participant of the electronic information exchange (the initiator) shall provide another participant of electronic information exchange (the respondent) with a message, in response to which the 21 respondent shall send a response message within the operation he performs (the receiving operation). Messages exchanged within the business process shall be formed in accordance with the requirements specified in Section VI of these Technical specifications. Table 11 presents a relationship between the operations, intermediate and resulting states of information objects of business process and transactions for each Business Process Procedure. 22 Table 11 The list of transactions No.
Operation performed by the Initiator Intermediate state of information object of the business process Operation performed by the Respondent Resulting state of information object of the business process Transaction 1 Providing information on the issued certificate of origin (ESS.VN.PRC.001) 1.1 transferring information on the issued certificate of origin (ESS.VN.OPR.001) receiving and processing of the notice on the results of processing of information on the issued certificate of origin (ESS.VN.OPR.003) certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is transferred receiving and processing of information on the issued certificate of origin (ESS.VN.OPR.002) certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is received providing information on the issued certificate of origin (ESS.VN.TRN.001) 2 Receiving information on the certificate of origin (ESS.VN.PRC.002) 2.1 requesting for information on the certificate of origin (ESS.VN.OPR.004) receiving and processing of information on the certificate of origin (ESS.VN.OPR.006) certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is requested providing information on the certificate of origin (ESS.VN.OPR.005) certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is provided certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is absent receiving information on the certificate of origin (ESS.VN.TRN.002) 23 The scheme of the transaction “Providing information on the issued certificate of origin” (ESS.VN.TRN.001) is provided in Figure 4. : Initiator : Respondent Information on the issued certificate of origin (ESS.VN MSG.001) Transferring information on the issued certificate of origin certificates of origin [information on the issued certificate of origin is received] Receiving and processing of information on the issued certificate of origin Control Error Succes Notification of the results of processing of information (ESS.W MSG.002) Figure 4. Scheme of the transaction “Providing information on the issued certificate of origin” (ESS.VN.TRN.001) The scheme of the transaction “Receiving information on the certificate of origin” (ESS.VN.TRN.002) is provided in Figure 5. 24 : Initiator : Respondent Request for information about the certificate of origin (ESS.VN. MSG.004) Request for information about the certificate of origin : certificates of origin [information on the issued certificate of origin is absent] Provision of information on the certificate of origin Control Error Succes Notification on absence of information (ESS.VN. MSG.003) Provision of information on the certificate of origin (ESS.VN. MSG.005) : certificates of origin [information on the issued certificate of origin is provided] Succes Figure 5. Scheme of the transaction “Receiving information on the certificate of origin” (ESS.VN.TRN.002) The parameters of the transactions “Providing information on the issued certificate of origin” (ESS.VN.TRN.001) and “Receiving information on the certificate of origin” (ESS.VN.TRN.002) are listed in Subsection 9.4 of these Technical Specifications. VI. Content and structure of information transmitted 6.1. Content of information transmitted Description of the content of information transmitted is provided in Appendix A. 6.2. Structure of information transmitted Description of structures of information transmitted and rules for their filling out and control is provided in a set of tables in Appendix B.
Description of the structure of transmitted information and messages in W3C language notation of XML-schemes is provided in Appendix C. 25 Examples of transmitted information and messages in the form of XML- documents are provided in Appendix D. Information about web services standards is provided in Appendix F. VII. Structure and format of messages 7.1. General requirements and applicable standards The information transmitted as a part of the described business process, shall be XML-formatted in accordance with the Extensible Markup Language (XML) 1.0 standard (Fifth Edition) that can be found at: http://www.w3.org/TR/REC-xml. When describing the structure and format of messages, the namespaces given in Table 12 are used, as well as the specifications provided in Table 13. Table 12 List of XML-document namespaces Prefix Address soap http://www.w3.org/2003/05/soap-envelope wsa http://www.w3.org/2005/08/addressing xs http://www.w3.org/2001/XMLSchema A message in SOAP format transmitted between electronic information exchange participants is made in accordance with the SOAP 1.2 specification and consists of a header block (soap:Header) and a body block (soap:Body). The header block contains technological information required for routing and processing of a message, as well as for monitoring of electronic information exchange. 26 Table 13 Specifications used to describe structure and format of messages Short name Full name SOAP 1.2 SOAP Version 1.2 Part 1: Messaging Framework (Second Edition). W3C Recommendation 27 April 2007. http://www.w3.org/TR/soap12-part1 WS-Addressing 1.0–Core Web Services Addressing 1.0 – Core. W3C Recommendation 9 May 2006. http://www.w3.org/TR/ws-addr-core XML 1.0 Extensible Markup Language (XML) 1.0 (Fifth Edition). W3C Recommendation 26 November 2008. http://www.w3.org/TR/2008/REC-xml-20081126 The body block includes the application or technological information important for the participants of electronic information exchange and shall conform with the structure of transmitted data specified in Appendix B and W3C language notation of XML-schemes specified in Appendix C. UTF-8 encoding shall be used for generating messages and contents of their blocks. The maximum length of a message transmitted is 100 MB. The list of business process messages transmitted within the information interaction when implementing the business process is given in Table 14.
Table 14 The list of messages transmitted Structure identifier (message identifier) Type of information Purpose Certificate (ESS.VN.MSG.001) information on the issued certificate of origin contains information on the issued (annulled, recalled) certificate of origin provided by the authorized owning body Response (ESS.VN.MSG.002) notice on the results of processing of information notice on the results of processing of information on the issued (annulled, recalled) certificate of origin provided by the receiving customs authority 27 Structure identifier (message identifier) Type of information Purpose Response (ESS.VN.MSG.003) notification on absence of information notification on results of processing of request by the authorized body-information owner, containing information about absence of requested information Request (ESS.VN.MSG.004) request for information about the certificate of origin contains a request of the customs authority- information receiver for information about the certificate of origin Certificate (ESS.VN.MSG.005) information on the certificate of origin provided in response to the request contains information on the issued (annulled, recalled) certificate of origin provided by the authorized owning body in response to the request 7.2. The structure of header blocks The header block contains headers in accordance with WS-Addressing 1.0 – Core specification, as well as specialized headers used to organize interaction. The header block includes the following headers: a) wsa:To – a header containing information on the receiver; b) wsa:From – a header containing logical address of the sender, to which the response message should be sent; c) wsa:MessageID – a header containing message identifier; d) wsa:RelatesTo – a header containing message reference identifier; e) wsa:Action – a header identifying message content; The wsa:To header is obligatory to fill out and shall include the logical address of the receiver. The logical address is used to identify the receiver in messages between the External Gateway and electronic information exchange services provided by the National Single Window of Viet Nam. The wsa:From header is obligatory to fill out and shall include the logical address of the sender. The list of logical addresses of participants of electronic information exchange within the Electronic Origin Certification and Verification System is given in Table 15. 28 Table 15 The list of logical addresses of participants of electronic data exchange Logical address of the exchange participant Participant of electronic information exchange ESS.VN.AM The State Revenue Committee of the Republic of Armenia; The Chamber of Commerce and Industry of the Republic of Armenia ESS.VN.BY The State Customs Committee of the Republic of Belarus; The Chamber of Commerce and Industry of the Republic of Belarus ESS.VN.KZ The State Revenue Committee of the Ministry of finance of the Republic of Kazakhstan; The National Chamber of Entrepreneurs of the Republic of Kazakhstan ESS.VN.KG The Customs Service under the Ministry of Finance of the Kyrgyz Republic; The Chamber of Commerce and Industry of the Kyrgyz Republic ESS.VN.RU The Federal Customs Service (the Russian Federation); The Chamber of Commerce and Industry of the Russian Federation ESS.VN.VN The Ministry of Finance (General Department of Viet Nam Customs) of the Socialist Republic of Viet Nam; The Ministry of Industry and Trade of the Socialist Republic of Viet Nam.
The wsa:MessageID header is obligatory to fill out and is intended for unique identification of separate message instances. Values of message identifiers shall be globally unique and be UUID in accordance with RFC 4122 specification. The wsa:Action header is intended for informing participants of the electronic information exchange on the business process procedure within which a message was sent. The wsa:RelatesTo header is intended for message chains creation. The wsa:RelatesTo header shall contain a value of the wsa:MessageID header of the original message. In this case, the wsa:MessageID header shall be filled with a new value. 29 The wsa:Action header of an applied message transmitted as part of a business process is filled out by the uniform resource identifier (URI), consisting of the following components, divided by slash-symbol “/”: а) fixed prefix “tr://”; b) CERTIFICATE identifier; c) components of information on the message contents. Components of information about the contents of the message are specified in the following order: а) version of the interaction services; b) procedure code defined in Table 2 of these Technical Specifications; c) transaction code defined in Table 11 of these Technical Specifications; d) message code defined in Table 14 of these Technical Specifications; Example of filling out the wsa:Action header: tr://CERTIFICATE/0.1/ESS.VN.PRC.001/ESS.VN.TRN.001/ESS.VN.MSG.001. VIII. Use of directories and classifiers Special directories and classifiers are used for electronic information exchange. Lists of directories and classifiers used within the electronic information exchange are provided in Tables 16–18. 30 Table 16 The list of main directories and classifiers used by all electronic information exchange participants Name Type Description country classifier the classifier contains the list of codes and names of countries (used in accordance with ISO 3166) https://www.iso.org/ob p/ui/#iso:std:iso:3166:- 1:ed-3:v1:en,fr language classifier the classifier contains the list of codes and names of languages in accordance with IETF RFC 5646 and IANA Language Subtag Registry https://tools.ietf.org/ht ml/rfc5646 and https://www.iana.org/as signments/language- subtag- registry/language- subtag-registry classifier of cargoes, packages and packaging materials the classifier contains the list of codes and names of types of cargo, packages and packaging materials https://www.unece.org/ fileadmin/DAM/cefact/ recommendations/rec2 1/rec21rev1_ecetrd195 e.pdf UN EDIFACT Code list 3031 Types of addresses the classifier contains the list of codes and names of address types https://unece.org/filead min/DAM/trade/untdid /d15a/tred/tred3131.ht m UN EDIFACT Code list 3155 Types of communications the classifier contains the list of codes and names of communication types https://unece.org/filead min/DAM/trade/untdid /d13a/tred/tred3155.ht m 31 Table 17 List of directories and classifiers used by the Member States Name Type Description a Unified goods nomenclature of foreign economic activity of the Eurasian Economic Union based on the Harmonized Description and Coding System of the World Customs Organization the classifier contains the list of codes and names of goods https://eec.eaeunion.org /comission/department/ catr/ett/ https://eec.eaeunion.org /comission/department/ catr/psn/ units of measurement classifier the classifier contains the list of codes, names and symbols of units of measurement https://portal.eaeunion.
org/sites/odata/_layouts /15/Portal.EEC.Registr y.Ui/DirectoryForm.as px?ViewId=61f9080c- 730e-4dfb-addb- 2e6b11d5e84b&ListId =0e3ead06-5475-466a- a340- 6f69c01b5687&ItemId =283# classifier of transport and transportation of goods currency qualifier the classifier contains the list of types of vehicles and transportation of goods and the corresponding codes https://portal.eaeunion. org/sites/odata/_layouts /15/Portal.EEC.Registr y.Ui/DirectoryForm.as px?ViewId=61f9080c- 730e-4dfb-addb- 2e6b11d5e84b&ListId =0e3ead06-5475-466a- a340- 6f69c01b5687&ItemId =272# 32 Name Type Description classifier of documents used for customs declaration the classifier contains a list of codes and names types of documents and information used for customs declaration https://portal.eaeunion. org/sites/odata/_layouts /15/Portal.EEC.Process 11/TreeListForm.aspx? ViewId=TreeView&Lis tId=0e3ead06-5475- 466a-a340- 6f69c01b5687&ItemId =277 33 Table 18 List of directories and classifiers used by the Socialist Republic of Viet Nam Name Type Description Harmonized System (HS Code), compatible with ASEAN Harmonized Tariff Nomenclature (AHTN) the classifier contains the list of codes and names of goods To be provided by the Socialist Republic of Viet Nam units of measurement classifier the classifier contains the list of codes and names of units of measurement To be provided by the Socialist Republic of Viet Nam classifier of transport and transportation of goods currency qualifier the classifier contains the list of types of vehicles and transportation of goods and the corresponding codes To be provided by the Socialist Republic of Viet Nam classifier of documents used for customs declaration the classifier contains a list of codes and names types of documents used for customs declaration To be provided by the Socialist Republic of Viet Nam The contents of detailed information from directories and classifiers and their structures are defined in Appendix E. Directories and classifiers shall be updated when new versions are released. Participants of electronic information exchange routinely exchange updated versions of directories and classifiers defined in Appendix E. The participants of electronic information exchange shall solely track changes of versions of the directories and classifiers defined in tables 16–18 using open sources. 34 IX. Technical aspects and interaction parameters 9.1. General information The procedure of information interaction during the implementation of the business processes is defined in Section V of these Technical Specifications. When a transaction is executed, each of the sent messages shall be processed successfully, or all the application-level changes in the systems of the participants of electronic information exchange made due to processing of the transaction messages shall be cancelled. As a part of the transactions, the following types of messages are used: business process messages, acknowledgment signals, exception signals. The list of business process messages is provided in Table 18 of these Technical Specifications. A business process message is an applied message, which contains a set of applied data transmitted between the participants of electronic information exchange in accordance with the rules given in Section 5.3 of these Technical Specifications. The acknowledgment signal is an applied message reporting on successful stage of business process message processing. The exception signal is an applied message reporting on deviation from the business process message routine processing.
Description of acknowledgment and exception signals is provided in Section 9.5 of these Technical Specifications. In order to implement a reliable information interaction it is possible to resend a business process message, if no response or an error process message was received. When resending the message, a new wsa:MessageID identifier shall be generated. To ensure communication between the messages within a transaction, wsa:RelatesTo field is filled out for all the business process messages, except those initiating a transaction. Wsa:RelatesTo field contains a wsa:MessageID identifier obtained by the participant of electronic information exchange at the previous stage of the 35 transaction. In order to ensure control (tracking) of duplicates (resent messages), the applied data structures shall be controlled. In this case, if the Respondent finds that the message is resent by the Initiator, the Respondent shall regenerate and send a response. 9.2. Message exchange procedure During the execution of a transaction (for all transactions defined in Section 5.3 of these Technical Specifications), the following messaging sequence is implemented: the initiator sends a request to the respondent and waits for confirmation of receipt of the request till the time determined in the scope of transaction parameters as a deadline for confirmation of receipt expires; the respondent receives the request and conducts the process and structural control in accordance with the rules specified in Section 9.3 of these Technical Specifications, and sends a “Received” acknowledgment signal to the initiator; after processing of the “Received” acknowledgment signal from the respondent, the Initiator waits for confirmation of acceptance of the information contained in the request for processing till the time determined in the scope of transaction parameters as a deadline for confirmation of processing expires; the respondent controls the data in the request in accordance with the rules specified in Section 9.3 of these Technical Specifications, and confirms the acceptance of information received for processing by sending an “Accepted for processing” acknowledgment signal to the Initiator; after processing the “Accepted for processing” acknowledgment signal from the respondent, the initiator waits for a response with information till the time determined in the scope of transaction parameters as a deadline for receiving a response expires; the respondent processes the received request and sends a response to the initiator; the initiator controls data contained in the response in accordance with the 36 rules specified in Section 9.3 of these Technical Specifications. The order of transaction is given in Figure 6. Initiator Respondent Initiating message Signal Received Signal Accepted for processing Response-message Figure 6. The order of transaction 9.3. Procedure of message processing by receiver Message processing is performed by the receiver (the respondent) in accordance with the following standard stages: a) process control of the message; b) structural control of the body block; c) processing of the body block data. The process control of a message involves checking the message structure for compliance with the established formats and structures of messages without regard to the applied data transmitted, as well as checking the connectivity of messages at the message header level.
If process control of a message results in errors and checked message is not an error process message, the respondent shall send a soap:Sender error message to the initiator in accordance with the WS-Addressing 1.0 – Binding specification under the 37 terms specified in Section 9.6 of these Technical Specifications. The structural control of the body block involves checking its structure for compliance with the established data structures (according to XSD schema). 9.4. Parameters of transactions Transactions shall be carried out in accordance with the given transaction parameters. The parameter “Time to confirm receipt” sets the maximum time period between sending a business process message by the initiator and the time of receipt of the acknowledgment signal “Received”. The initiator of the business process message shall resend the message if the respondent has not confirmed the receipt within an agreed period of time. The number of retries is set using the parameter “Number of retries”. The parameter “Time to confirm acceptance for processing” sets the maximum period of time between sending a business process message by the initiator and the time of receipt of the acknowledgment signal “Accepted for processing”. The initiator of request shall resend the message if the respondent has not confirmed the receipt within the agreed period of time. The number of retries is set using the parameter “Number of retries”. The parameter “Time to respond” sets the maximum period of time between sending a business process message (request) by the initiator and the time of receipt of the respondent’s response with the information on the results of processing of the request (response). The initiator shall resend the request, if no response has been received from the respondent within the agreed period of time. The number of retries is set using the parameter “Number of retries”. Control over the observance of procedural deadlines set by the parameters “Time to confirm receipt”, “Time to confirm acceptance for processing” and “Time to respond” is the initiator’s responsibility. The Respondent bears no responsibility for control of these parameters. 38 The parameter “Number of retries” sets the maximum number of retries of business process messages. The situation when all the retries of sending a business process message have been exhausted and the required messages have not been received by the initiator is emergency. The procedure for actions performed by the parties in emergency situations is specified in Section XI of these Technical Specifications. 9.4.1. Parameters of the transaction “Providing information on the issued certificate of origin” Parameters of the transaction “Providing information on the issued certificate of origin” (ESS.VN.TRN.001) are given in Table 19. Table 19 Description of the transaction “Providing information on the issued certificate of origin” (ESS.VN.TRN.001) No.
Parameter Description 1 Designation ESS.VN.TRN.001 2 Name of transaction providing information on the issued certificate of origin 3 Initiator authorized body-information owner 4 Initiation operation transferring information on the issued certificate of origin (ESS.VN.OPR.001) 5 Respondent customs authority-information receiver 6 Receiving operation receiving and processing of information on the issued certificate of origin (ESS.VN.OPR.002) 7 Result of transaction certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is received 8 Parameters of transaction: time to confirm receipt 5 min time to confirm acceptance for 20 min 39 No. Parameter Description processing time to wait for response 20 min number of retries 3 9 Messages of transaction: initiation message information on the issued certificate of origin (ESS.VN.MSG.001) response message notice of the results of processing of information (ESS.VN.MSG.002) 9.4.2. Parameters of the transaction “Receiving information on the certificate of origin” Parameters of the transaction “Receiving information on the certificate of origin” (ESS.VN.TRN.002) are given in Table 20. Table 20 Description of the transaction “Receiving information on the certificate of origin” (ESS.VN.TRN.002) No. Parameter Description 1 Designation ESS.VN.TRN.002 2 Name of transaction receiving information about the certificate of origin 3 Initiator customs authority-information receiver 4 Initiation operation requesting for information on the certificate of origin (ESS.VN.OPR.004) 5 Respondent authorized body-information owner 6 Receiving operation providing information on the certificates of origin (ESS.VN.OPR.005) 40 No. Parameter Description 7 Result of transaction certificates of origin (ESS.VN. BEN.001): information on the certificate of origin is absent certificates of origin (ESS.VN.BEN.001): information on the issued certificate of origin is provided 8 Parameters of transaction: time to confirm receipt 5 min time to confirm acceptance for processing 5 min time to wait for response 10 min number of retries 3 9 Messages of transaction: initiation message request for information about the certificate of origin (ESS.VN.MSG.004) response message providing information on the certificate of origin (ESS.VN.MSG.005); notice on absence of information (ESS.VN.MSG.003) 9.5. Acknowledgment signals and exception signals The namespaces used for description of the structure and the requisite composition of acknowledgment signals and exception signals are given in Table 21. Table 21 Namespaces Prefix Address xs http://www.w3.org/2001/XMLSchema sgn urn: certificate:signal:v1.0 The base data types used for description of the structure and the requisite composition of acknowledgment signals and exception signals are given in Table 22. 41 Table 22 Base data types Name Description sgn:EDocIdType the document identifier, which is a UUID in accordance with standard ISO/IEC 9834-8:2005. String of symbols with framework [0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0- 9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12} sgn:DateTimeType the Gregorian calendar date and time in the format of ISO 8601 “Data elements and interchange formats — Information interchange — Representation of dates and types” sgn:ErrorCodeType designation of the Control Error. String consists of 1 to 255 symbols sgn:StringType textual arbitrary information. A string is of arbitrary length 9.5.1.
The acknowledgment signal “Received” The respondent will send the acknowledgment signal “Received” at the moment when the step of the structural block content control is made. P.MSG.RCV message code for the acknowledgment signal “Received” will be used when the wsa:Action header, identifying the contents of the business process message, is formed. Other components of the data on message content are specified in accordance with the rules for forming the wsa:Action header for applied messages as described in Section 7.2. The structure and requisite composition of the acknowledgment signal “Received” are given in Table 23. Table 23 The structure and requisite composition of the acknowledgment signal “Received” Element Data type Description Mult . sgn:DeliveryReceipt sgn:DeliveryReceiptType wrapping element of the acknowledgment signal “Received” sgn:SignalId sgn:EDocIdType signal identifier 1 sgn:DateTime sgn:DateTimeType date and time of the acknowledgment signal forming “Received” 1 42 9.5.2. The acknowledgment signal “Accepted for processing” The acknowledgment signal “Accepted for processing” is sent by a respondent before processing of the body block data. P.MSG.PRS message code for the acknowledgment signal “Accepted for processing” will be used when the wsa:Action header, identifying the contents of the business process message, is formed. Other components of the data on message content are specified in accordance with the rules of forming of the wsa:Action header for applied messages as described in Section 7.2 of these Technical Specifications. The structure and requisite composition of the acknowledgment signal “Accepted for processing” are given in Table 24. Table 24 The structure and requisite composition of the acknowledgment signal “Accepted for processing” Element Data type Description Mult . sgn:ProcessingReceip t sgn:Processing ReceiptType wrapping element of the acknowledgment signal “Accepted for processing” sgn:SignalId sgn:EDocIdType signal identifier 1 sgn:DateTime sgn:DateTimeType date and time of the acknowledgment signal forming “Accepted for processing” 1 9.5.3. The exception signal “Error” The situation, when the respondent sends the exception signal “Error” to the initiator, occurs in the following cases: a) the respondent has accepted the business process message, which was not expected to be received within a transaction execution; b) the respondent has found errors during the structural control of the body block or format-logic control of the body block; c) an unrecoverable error, making it impossible to perform applied data processing, occurred on the applied data processing step. 43 The situation, when the respondent has received the business process message, which was not expected to be received within a transaction execution, occurs in the following cases: the message received is a business process message or an acknowledgment signal, and thus it does not apply to transactions executed by the respondent; the respondent is not authorized to process the message received (if they do not participate in information interaction, procedure or transaction). In these cases, the value (code) “Common:UnexpectedMessage” is assigned to the designation of Control Error (field sgn:Code) of the exception signal “Error”. If the respondent finds an error during the structural control of the body block, the value (code) “Common:DataError” is assigned to the designation of Control Error (box sgn:Code) of the exception signal “Error”.
If the respondent finds an error during the format-logical control of the business process message, the value of rule code is assigned to the designation of Control Error (sgn:Code field) of the exception signal “Error”, within checking of which an error occurred according to Table 29. If there is a situation, when an unrecoverable error occurred on the step of body block data processing, making it impossible to perform data processing, the value (code) “Common:FatalError” is assigned to the designation of Control Error (field sgn:Code) of the exception signal “Error”. List of unrecoverable errors is determined by the participant of electronic information exchange independently. P.MSG.ERR message code for the exception signal “Error” will be used when the wsa:Action header, identifying the contents of the business process message, is formed. Other components of the data on message content are specified in accordance with the rules of forming of the header wsa:Action for applied messages. The structure and requisite composition of the exception signal “Error” are given in Table 25. 44 Table 25 The structure and requisite compositon of the exception signal “Error” Element Data type Description Mult . sgn:ValidationError sgn:ValidationError Type wrapping element of the exception signal “Error” sgn:SignalId sgn:EDocIdType identifier of the exception signal “Error” 1 sgn:DateTime sgn:DateTimeType date and time of the exception signal forming “Error” 1 sgn:Error sgn:ErrorType wrapping element 1..* sgn:Code sgn:ErrorCodeTyp e error designation 1 sgn:Description sgn:StringType error text value 1 sgn:Details sgn:StringType error detailed data 0..1 sgn:EDocId sgn:EDocIdType document identifier, in which the error occurs. It is completed if the error is related to a certain document and the document identifier was extracted 0..1 sgn:Reference sgn:StringType a string of symbols that allows to uniquely locate the item that caused the error 0..1 To participate in the information interaction, the participants of electronic information exchange shall implement the services enforcing Business Process Procedures on their side. Description of services in WSDL-format is given in Appendix F. 9.6. Error process message If an error occurs at the step of the process control of a message, an error process message shall be formed. Error process message body block shall contain elements specified in Table 26. 45 Table 26 Composition of the process message body block Element Data type Description Mult . soap:Fault soap:Fault block wrapping element soap:Code soap:faultcode wrapping element 1 soap:Value soap:faultcodeEnu m error class 1 soap:Subcode soap:subcode error code wrapping element 1 soap:Value xs:QName error code 1 soap:Reason soap:faultreason wrapping element of the error text description 1 soap:Text soap:reasontext block of the error text description 1..* @xml:lang – language identifier 1 soap:Detail soap:detail error details 0..1 The soap:Code/soap:Value element shall be completed in accordance with SOAP 1.2 specification. The soap:Code/soap:Subcode/soap:Value element shall contain an error code. The list of standard error codes and rules on the use of codes from WS- Addressing 1.0 – Binding specification are provided in Table 27.
46 Table 27 Typical errors codes Error class Error code Description and application features soap:Sender wsa:InvalidAddressingHea der used in accordance with the rules defined by WS- Addressing 1.0–Binding specification with the following restrictions: Subsubcode values are not used, wsa:DuplicateMessageID error type is not generated and is not sent soap:Sender wsa:MessageAddressingHe aderRequired used according to the rules, defined by WS- Addressing 1.0–Binding specification soap:Sender wsa:DestinationUnreachabl e used according to the rules, defined by WS- Addressing 1.0–Binding specification soap:Sender wsa:ActionNotSupported used according to the rules, defined by WS- Addressing 1.0–Binding specification soap:Sender int:InvalidHeader one or more specific headers are missing soap: Receiver wsa:EndpointUnavailable used according to the rules, defined by WS- Addressing 1.0–Binding specification with the following restrictions: the element wsa:RetryAfter shall not be used while implementation of the electronic information exchange soap: Receiver int:InternalError an unexpected error occurred while processing the message soap:Sender int:DataError received applied data have an incorrect structure The soap:Text element shall contain the error text description. Each soap:Text element shall contain the xml:lang language identifier, formed in accordance with XML 1.0 specification. If there is a set of soap:Text elements in the error process message, each of these elements shall contain the xml:lang language identifier, that differs from the IDs of other soap:Text elements. The error process message shall contain at least one soap:Text element, the 47 contents of which is presented in English, and the xml:lang language identifier shall contain “en” value. The soap:Detail optional element shall include information detailing the error. 9.7. Services technical implementation Electronic information exchange between the External Gateway and information interaction services provided by National Single Window of Viet Nam is performed using SOAP services. The SOAP service shall be implemented on each side, both the External Gateway and Viet Nam side. To implement electronic information exchange within the EOCVS defined in these Technical Specifications, EECVNCERTIFICATION service shall be used. The list of EECVNCERTIFICATION service methods is given in Table 28. Table 28 List of EECVNCERTIFICATION service methods No. Method Description 1 sendCertificateDetails providing information on the issued certificate of origin 2 sendRequestCertificateDetails receiving information about the certificate of origin 3 sendResultCertificateDetails receiving results of processing containing information on the certificate of origin 4 sendSignal receiving of signals on the current processing status 5 sendResult receiving of the processing result 9.7.1. The method “sendCertificateDetails” Purpose: implementation of the operation “Receiving and processing of information on the issued certificate of origin” (ESS.VN.OPR.002) Business process procedure: ESS.VN.PRC.001 SOAP method: sendCertificateDetails 48 Description: providing information on the issued certificate of origin (carried out by calling the sendCertificateDetails method by the respondent (receiver) of the message “Information on the issued certificate of origin” (ESS.VN.MSG.001)).
Input parameters: ESS.VN.MSG.001 (Certificate) Output parameters: no data Description of the operation algorithm: Message processing steps within the execution of the service shall comply with the rules specified in Section 9.3 of these Technical Specifications: 1. Process control of the message; 2. Structural control of the body block; 3. Processing of the data block. For the services, being implemented on Viet Nam side, all the message processing stages shall be executed. For the services implemented on the External Gateway, steps 1 and 2 shall be executed. Processing step 3 is implemented and executed within Information Systems of the receiving customs authorities of the Member States. Structural control of the body block involves the check of the message structure “Information on the issued certificate of origin” (ESS.VN.MSG.001) for compliance with the structure “Information on the certificate of origin” (Certificate) provided in Appendices B and C of these Technical Specifications. If the results of message process control and body block structural control are successful, the acknowledgment signal “Received” shall be generated and sent. The acknowledgement signal “Received” is transmitted by calling the method “Receiving of signals on the current processing status” (sendSignal) on the side of the original message sender. If process control of the message resulted in errors, the receiver shall send an error process message of the soap:Sender class to the sender. A detailed description of the error process message is provided in Section 9.6 of these Technical Specifications. Before processing of the body block data, the acknowledgment signal 49 “Accepted for processing” shall be generated and sent. The acknowledgement signal “Accepted for processing” is transmitted by calling the method “Receiving of signals on the current processing status” (sendSignal) on the side of the original message sender. Requirements for the method of message body block data processing and requirements for the storage of message processing results are defined by information interaction participants. If the body block data is processed successfully, the message “Notice on the results of processing of information” (ESS.VN.MSG.002) containing results of processing of information on the certificate of origin shall be prepared and sent. The message is transmitted using the method “Receiving of processing result” (sendResult) on the side of the original message sender. If an error occurred during the body block data processing, the exception signal “Error” shall be prepared and sent in accordance with the rules from Section 9.5.3 of these Technical Specifications. The list of potential errors within the implementation of the transaction “Providing information on the issued certificate of origin” (ESS.VN.TRN.001) is given in Table 29. Table 29 Error code Error description Description of checking within body block processing 1 Duplication error. Registration number of the certificate is found among previously transmitted certificates. The CancellationDateTime (“Date of certificate annulment”) requisite is not filled within previously provided information on the issued certificate, and the “Certificate registration number” ID requisite value is found within previously transferred certificates The exception signal “Error” is transmitted by calling the method “Receiving of signals on the current processing status” (sendSignal) on the side of the original message sender. 50 9.7.2.
The method “sendRequestCertificateDetails” Purpose: implementation of the operation “Providing information on the certificate of origin” (ESS.VN.OPR.005) Business process procedure: ESS.VN.PRC.002 SOAP method: sendRequestCertificateDetails Description: receiving information on the certificate of origin (carried out by calling the sendRequestCertificateDetails method on the receiver side of the message “Request for information on the certificate of origin” (ESS.VN.MSG.004)). Input parameters: ESS.VN.MSG.004 (Request) Output parameters: no data Description of the operation algorithm: Message processing steps within the execution of the service shall comply with the rules specified in Section 9.3 of these Technical Specifications: 1. Process control of the message; 2. Structural control of the body block; 3. Processing of the data block. For the services, being implemented on Viet Nam side, all the message processing stages shall be executed. For the services implemented on the External Gateway, steps 1 and 2 shall be executed. Processing stage 3 is implemented and executed in information systems of the authorized body-information owner of Member States. Structural control of the body block involves the check of the message structure “Request for information on the certificate of origin” (ESS.VN.MSG.004) for compliance with the structure “Request for information on certificates of origin” (Request) provided in Appendices B and C of these Technical Specifications. If the results of message process control and body block structural control are successful, the acknowledgment signal “Received” shall be generated and sent. The acknowledgement signal “Received” is transmitted by calling the method “Receiving of signals on the current processing status” (sendSignal) on the side of the original message sender. 51 If process control of the message resulted in errors, the receiver shall send an error process message of the soap:Sender class to the sender. A detailed description of the error process message is provided in Section 9.6 of these Technical Specifications. Before processing of the body block data, the acknowledgment signal “Accepted for processing” shall be generated and sent. The acknowledgement signal “Accepted for processing” is transmitted by calling the method “Receiving of signals on the current processing status” (sendSignal) on the side of the original message sender. If the information that satisfies the request was found, the message “Providing information on the certificate of origin” (ESS.VN.MSG.005) containing the information found shall be generated and sent. The message is transmitted using the method “Receiving of processing results containing information on the certificate of origin” (sendResultCertificateDetails) on the side of the original message sender. If the information that satisfies the request was not found, the message “Notice on absence of information” (ESS.VN.MSG.003) shall be generated and sent. The message is transmitted using the method “Receiving of processing result” (sendResult) on the side of the original message sender. If an error occurred during the body block data processing, the exception signal “Error” shall be prepared and sent in accordance with the rules from Section 9.5.3 of these Technical Specifications. 9.7.3.
The method “sendResultCertificateDetails” Purpose: implementation of the operation “Receiving and processing of information on the issued certificate of origin” (ESS.VN.OPR.006); Business process procedure: ESS.VN.PRC.002; SOAP method: sendResultCertificateDetails Description: receiving the results of processing containing information on the certificate of origin (carried out by calling the sendResultCertificateDetails method on the receiver side of the message “Information on the certificate of origin provided in response to the request” (ESS.VN.MSG.005)). 52 Input parameters: ESS.VN.MSG.005 (Certificate) Output parameters: no data Description of the operation algorithm: Message processing steps within the execution of the service shall comply with the rules specified in Section 9.3 of these Technical Specifications: 1. Process control of the message; 2. Structural control of the body block; 3. Processing of the data block. For the services, being implemented on Viet Nam side, all the message processing stages shall be executed. For the services implemented on the External Gateway, steps 1 and 2 shall be executed. Processing step 3 is implemented and executed within Information Systems of the receiving customs authorities of the Member States. Structural control of the body block involves the check of the message structure “Information on the issued certificate of origin provided in response to the request” (ESS.VN.MSG.005) for compliance with the structure “Information on the certificate of origin” (Certificate) provided in Appendices B and C of these Technical Specifications. If process control of the message resulted in errors, the receiver shall send an error process message of the soap:Sender class to the sender. A detailed description of the error process message is provided in Section 9.6 of these Technical Specifications. Requirements for the method of message body block data processing and requirements for the storage of message processing results are defined by information interaction participants. If an error occurred during the body block data processing, the exception signal “Error” shall be prepared and sent in accordance with the rules from Section 9.5.3 of these Technical Specifications. The exception signal “Error” is transmitted by calling the method “Receiving of signals on the current processing status” (sendSignal) on the side of the original 53 message sender. 9.7.4. The method “sendSignal” Purpose: Implementation of receiving and processing of acknowledgment signals and exception signals. Business process procedure: ESS.VN.PRC.001; ESS.VN.PRC.002; SOAP method: sendSignal Description: Receiving of signals on the current processing status Input parameters: P.MSG.ERR P.MSG.PRS P.MSG.RCV Output parameters: no data Description of the operation algorithm: The procedure is defined by the signal type and transaction during which the signal was received (see Section 5.3 of these Technical Specifications). 9.7.5.
The method “sendResult” Purpose: Implementation of the following operations: “Receiving and processing of the notice on the results of processing of information on the issued certificate of origin” (ESS.VN.OPR.003); “Receiving and processing of information on the certificate of origin” (ESS.VN.OPR.006); Business process procedure: ESS.VN.PRC.001; ESS.VN.PRC.002; SOAP method: sendResult Description: Receiving of data processing result Input parameters: ESS.VN.MSG.002; 54 ESS.VN.MSG.003; Output parameters: no data Description of the operation algorithm: The procedure is defined by the message code and transaction, during which the signal was received (see Section 5.3 of these Technical Specifications). X. Information protection The information transmitted within the business process is the information of restricted access (confidential information), the access of third parties to this information is limited, and its uncontrolled distribution is not allowed. The Member States, the Socialist Republic of Viet Nam and the Commission shall protect information in its transferring, receiving and processing within their area of responsibility. When information is transferred within the information space of the Member State, it is protected in accordance with the legislation and technical requirements for ensuring information protection in force on the territory of the Member State concerned. When transmitting information within the information space of Viet Nam, the protection is ensured in accordance with the legislation and the technical requirements for information protection in force on the territory of Viet Nam. The Commission and the General Department of Viet Nam Customs shall protect information transmitted between the IIS and the National Single Window of Viet Nam. When transmitting information using IIS functions of protection of information from unauthorized access, information security and permanence upon unauthorized or accidental impacts is provided by means of IIS. 55 When transmitting and receiving information through communication channels between the External Gateway and the National Single Window of Viet Nam, the information shall be protected by means of virtual private network (VPN) using hardware-software and/or software solutions. The authentication of the interacting parties and the encryption of the transmitted data shall be organized using the IPSec (RFC 2401–2412) and IPlir (Р1323565.1.034-2020) protocols. To implement cooperation with the services two cryptographic data channels shall be used: channel for transferring data from Viet Nam to the Commission built on the Pulse Secure Gateway VPN gateway and controlled by Viet Nam; channel for transferring data from the Commission to Viet Nam built on the VipNet Coordinator HW VPN gateway and controlled by the Commission. Cryptographic keys for VPN channel organization are issued and withdrawn by: from the side of the Union – by the verification center of the Commission; from the side of Viet Nam – by the verification center of the National Single Window of Viet Nam. To ensure the decryption of traffic and its redirection to the service, the objects of Pulse Secure Ipsec VPN Endpoint and VipNet Client Endpoint shall be used. These objects are dedicated workstations with installed VPN gateway software client. To ensure the flotation of data through encrypted channels, asymmetric routing shall be used.
To ensure the transmission of data from the National Single Window of Viet Nam to the IIS and from the IIS to the National Single Window of Viet Nam, source and destination IP-addresses shall be defined at the electronic information exchange implementation stage. The applicable parameters of VPN data channels are given in Table 30. 56 Table 30 No. Parameter IPsec IPlir Mode Tunnelling tunnelling Authentication technique Pre-shared key (PSK) and public IP-address keys and identifiers of nodes in the ViPNet network Authentication encryption algorithm ESP hmac-sha1-96 GOST 28147-89 (key length: 256 bits) Data encryption algorithm 3des-cbc GOST 28147-89 (key length: 256 bits) IKE encryption algorithm Diffie-Hellman Group 2, 3des-cbc — SA lifetime 86 400 seconds (24 hours) — SA traffic volume ---- — The information security solutions defined by these Technical Specifications shall be synchronized with the information security solutions implemented for exchange of customs information between the customs authorities of the Member States and Viet Nam and are determined by these customs authorities. XI. Emergency procedures The emergency situations (the situations when data cannot be processed correctly) can arise during information interaction within the Business Process Procedures. Emergency situations appear due to technical faults, timeout, Control Error structure and in other cases. Receiving any error process messages when performing Business Process Procedures is an emergency situation. In order to resolve emergency situations, the Parties and the Commission shall provide each other with the information on the persons responsible for providing technical support during the electronic information exchange, their contact details and working hours (providing for timezone differences). 57 If an emergency situation is not caused by the availability of specific resources, the recipient of the exception signal “Error” and/or error process message (hereinafter referred to as “the Error notice”) shall review the message, in regard to which the error notification was received, for compliance with the description of formats and structures of electronic documents, information and requirements for the message control specified in these Technical Specifications, particularly in Appendices B and C. If the non-compliance with specified requirements is detected, the recipient shall take all necessary measures to eliminate the error and send the message again. If non- compliances are not detected, the error notice recipient shall send the message containing information on the emergency situation and the inspection results to the IIS technical support. The IIS technical support shall review the description of the emergency situation considering the information on the results of inspection carried out by the error notification recipient, prepare guidelines for its elimination, and carry out and/or coordinate works on the elimination in cooperation with the recipient and the sender of the error notice. If an emergency situation is caused by the unavailability of certain resources, the recipient shall inform the IIS technical support on the emergency situation. If necessary, the IIS technical support shall request additional information from the error notice sender, review the emergency situation, prepare guidelines for its elimination, and carry out and/or coordinate works on the elimination in cooperation with the recipient and the sender of the error notice.
The authorized bodies and central customs authorities of the Member States, Viet Nam and the Commission shall inform each other about maintenance works on their information systems, while these information systems are unable to send and receive messages, not later than 24 hours before these works start. General recommendations for resolving emergency situations are given in Table 31. 58 Table 31 Actions in emergency situations Description of emergency situation Causes of emergency situation Description of actions in emergency situation 1 2 3 the transaction Initiator did not receive a response message after the agreed number of retries technical failures in the transportation system or system software error send a request to the support service of the integrated information system the transaction Initiator received an error message directories and classifiers are not synchronized or XML- schemas of electronic documents (information) are not updated the transaction initiator needs to check the structure of sent messages, synchronize directories and classifiers. If non-compliances were not found, the transaction Initiator sends the message describing the emergency situation to the technical support of the integrated information system an error occurred while processing the response message from the respondent within the Initiator’s information system error in checking and processing of the message content block on the side of the transaction Initiator the transaction Initiator shall check the content block for the correctness of the transmitted information and send a message describing the emergency situation to the technical support of the transaction Respondent XII. Applicable standards The list of international and industrial standards used in the electronic information exchange implementation and these Technical Specifications development is given in Table 32. 59 Table 32 The list of applicable standards Classifier name Reference 1 2 Classifier of transport means categories UN/Recommendation 19 http://www.unece.org/fileadmin/DAM/cefact/re commendations/rec19/rec19_01cf19e.pdf Codes for types of cargo, packages and packaging materials EDIFACT codes (7065) = UN/ECE Recommendation 21 Annex VI https://www.unece.org/fileadmin/DAM/cefact/r ecommendations/rec21/rec21rev1_ecetrd195e.p df Country classifier EDIFACT codes (3207) = ISO 3166-2 https://www.iso.org/obp/ui/#iso:std:iso:3166:- 1:ed-3:v1:en,fr ISO 8601:2004 international standard. Representation of date and time https://www.iso.org/obp/ui/#iso:std:iso:8601:ed- 3:v1:en Harmonized Commodity Description and Coding System http://www.wcoomd.org/en/topics/nomenclature /instrument-and-tools/hs-nomenclature-2017- edition/hs-nomenclature-2017-edition.aspx ISO/IEC 9834-8:2014. Information technology. Procedures for the operation of object identifier registration authorities.
Part 8: Generation of universally unique identifiers (UUIDs) and their use in object identifiers https://www.iso.org/obp/ui/#iso:std:iso- iec:9834:-8:ed-3:v1:en UN/EDIFACT Code Lists 1001, 3035, 3131, 3155, 3207, 3229, 7065, 8053 https://unece.org/fileadmin/DAM/trade/edifact/c ode/1001cl.htm https://unece.org/fileadmin/DAM/trade/untdid/d 97b/uncl/uncl3035.htm https://unece.org/fileadmin/DAM/trade/untdid/d 15a/tred/tred3131.htm https://unece.org/fileadmin/DAM/trade/untdid/d 13a/tred/tred3155.htm https://unece.org/fileadmin/DAM/trade/untdid/d 14a/tred/tred3207.htm https://unece.org/fileadmin/DAM/trade/edifact/c ode/3229cl.htm https://unece.org/fileadmin/DAM/trade/untdid/d 14a/tred/tred7065.htm https://unece.org/fileadmin/DAM/trade/edifact/c ode/8053cl.htm Extensible Markup Language (XML) 1.0 (Fifth Edition). W3C Recommendation https://www.w3.org/TR/2008/REC-xml- 20081126/ 60 Classifier name Reference 1 2 ISO/IEC 40210:2011 Information technology. W3C SOAP — Version 1.2. Part 1, Part 2 and others https://www.iso.org/ru/ics/35.080/x/ ISO/IEC 19505-1-2012 Information technology. Object Management Group Unified Modeling Language (OMG UML). Part 1: Infrastructure ISO/IEC 19505-2-2012 Information technology. Object Management Group Unified Modeling Language (OMG UML). Part 2: Superstructure https://www.omg.org/spec/UML/ https://www.omg.org/spec/UML/2.5.1/PDF RFC 2401–2412 https://www.ietf.org/rfc/ XIII. Implementation order To implement the electronic information exchange, the Parties shall: appoint persons on the part of the Participants of electronic information exchange, as well as on the part of the Commission responsible for ensuring the electronic information exchange, and perform mutual exchange of information about persons mentioned above; synchronize directories and classifiers specified in Appendix E hereto between the Parties; synchronize information from national directories and classifiers used for the formation of electronic messages; modify the software of authorized bodies and central customs authorities of the Member States and Viet Nam in terms of formation and maintenance of information resources containing information on certificates of origin; develop software components that implement the electronic information exchange; provide secure communication channels between the External gateway and the National Single Window of Viet Nam; perform an internal, integrated and inter-state testing; modify the software based on the test results. 61 Appendix A. Scope of information to be exchanged within implementation of electronic information exchange Table A1 Data list from a certificate of origin Name of data Description Mult. 1. Designation of the form of the certificate the «EAV» code of the certificate is specified 1 2. Designation of special marks the code designating the following is specified: ORG - the issued certificate of origin is the original; DBL - the issued certificate of origin is the duplicate of the certificate of origin; CHG - the certificate of origin is issued in substitution of the original certificate of origin 1 3. Data on the certificate data according to the list provided in Table A2 are specified 1 4. Data on the country which issued the certificate the code and the name of the country in which the certificate of origin was issued is specified 1 5. Data on the country for which the certificate is issued the code and the name of the country for which the issued certificate of origin is intended is specified 1 6.
Date of annulment of the certificate if necessary the date of annulment (recall) of the certificate is specified 0..1 7. Date of modification of the certificate if necessary the date of modification of the certificate of origin according to article 4.21 of FTA is specified 0..1 8. Code designation of the certificate category if necessary, the R.TR code is specified designating that the certificate of origin was issued afterwards. 0..1 9. Data on earlier issued certificate the registration number and the date of the certificate (issue) of earlier issued certificate of origin (according to Table A2) are specified if the certificate of origin is duplicate or issued in substitution of the original certificate (data at number 2 are «DBL» or «CHG»). 0..* 10. Data on the country of origin the code and the name of the country of origin of goods (the Member State of the Eurasian Economic Union or the Viet Nam) is specified 1 11. Data on the authorized body the code of the authorized body which issued the certificate of origin including the name of authorized body is specified 1 12. Data of the certificate verification data on the place of the certificate verification are specified 1 13. Information about the applicant data on the place and date of announcement of data and also the information about the applicant are specified 1 14. Data on consignment contain data according to the list provided in Table A3 of this Appendix 1 15. Date and time of recording of data date and time of recording of data of the certificate of origin are specified 1 62 Table A2 Document data list Table A3 Consignment data list Name of data Description Mult. 1. Information about the exporter information about the exporter of goods, including the name of the exporter, and the address including the country code of the exporter are specified 1 2. Information about the importer information about the importer of goods, including the name of the importer and the address including the country code are specified 1 3. Information about the receiver (consignee) of goods information (if it is known) about the consignee of goods, including name of a consignee and the address including the country code is specified 0..1 4. Data on a route of transportation of goods data on a route of transportation of goods are specified 0..1 5. Data on goods data according to the list provided in Table A4 of this Appendix are specified 1..* Table A4 Goods data list Name of data Description Mult. 1. Sequence number sequence number of goods 1 2. Data on packaging of goods data on a code of a type of packaging of goods and their name and also on the number of packagings of each type are specified 1..* 3. A commodity code according to HS the commodity code according to the harmonized system at the level of 6 signs is specified 1 4. Description of goods the detailed description of goods is specified, if applicable ,the name of model and trademark allowing 1 Name of data Description Mult. 1. Certificate identifier the registration number of the certificate of origin is specified 1 2. Unique identification number of the certificate the unique identification number of the certificate is specified 0..1 3. Date of the certificate verification (issue) date of the certificate verification (issue) is specified 1 4. Expiration date of the certificate expiration date of the certificate is specified 1 63 Name of data Description Mult. to identify goods 5. Additional marks the additional marks on goods provided by FTA are specified 0..1 6.
Data on criteria of goods origin the code of designation of origin criterion according to the list is specified: WO – goods are wholly obtained or produced in a Party as provided for in article 4.4 of FTA; PE – goods are produced entirely in the territory of one or both Parties, exclusively from originating materials from one or both Parties; PSR – goods are produced in the territory of a Party using non-originating material and satisfies the requirements as specified in Annex 3 FTA 1 7. Gross weight data on gross weight in kilograms or in other measurement, quantity of goods in units with the indication of unit code from the measurement units list 0..1 8. Invoice data data according to the list provided in Table A5 of this Appendix are specified 1..* Table A5 Invoice data list Name of data Description Mult. 1.Invoice information the document type code, number and document date are specified 1 2. Additional features: if the invoice is issued in the Third Country and provided for delivery to the importing country, a mark of TCI is given and: 2.1 number and date of invoice, as well as the name and the country of the company which issued such invoice; 0..1 2.2 information that the invoice will be issued later, as well as the trade name and the address of a physical person or a legal entity which will issue this invoice in the Third Country; 0..1 2.3 number and date of invoice of the exporter (issued in the Union/Viet Nam). 0..1 64 Appendix B.
Structure of information transmitted Table B1 Imported namespaces № Namespace identifier Prefix 1 2 3 1 urn:wco:datamodel:WCO:DS:1 ds 2 urn:un:unece:uncefact:data:standard:QualifiedDataType:5 qdt 3 http://www.w3.org/2001/XMLSchema xsd 4 urn:un:unece:uncefact:codelist:standard:UNECE:ScheduleTaskRelationshipType:D08A clm69673 5 urn:un:unece:uncefact:codelist:standard:UNECE:PaymentMeansCode:D08A clm64461 6 urn:un:unece:uncefact:codelist:standard:UNECE:ReportingThresholdTriggerType:D08A clm69667 7 urn:un:unece:uncefact:codelist:standard:UNECE:ScheduleTaskType:D08A clm69675 8 urn:un:unece:uncefact:codelist:standard:UNECE:PaymentMethodCode:D08A clm64439 9 urn:un:unece:uncefact:codelist:standard:UNECE:ResourceCostCategory:D08A clm69669 10 urn:un:unece:uncefact:identifierlist:standard:UNECE:PaymentTermsDescriptionIdentifier:D08A ids64277 11 urn:un:unece:uncefact:codelist:standard:UNECE:TransportModeCode:2 clm6Recommendation19 12 urn:un:unece:uncefact:codelist:standard:UNECE:PriceTypeCode:D08A clm65375 13 urn:un:unece:uncefact:codelist:standard:UNECE:ProjectTypeCode:D08A clm69665 14 urn:un:unece:uncefact:codelist:standard:UNECE:SecurityClassificationType:D08A clm69677 15 urn:un:unece:uncefact:codelist:standard:UNECE:ResourcePlanMeasureType:D08A clm69671 16 urn:un:unece:uncefact:codelist:standard:UNECE:PaymentGuaranteeMeansCode:D08A clm64431 65 № Namespace identifier Prefix 1 2 3 17 urn:un:unece:uncefact:codelist:standard:UNECE:TransportMeansTypeCode:2007 clm6Recommendation28 18 urn:un:unece:uncefact:codelist:standard:UNECE:MessageFunctionCodeAcknowledgement:D08A clm61225Acknowledgement 19 urn:un:unece:uncefact:codelist:standard:UNECE:FundingTypeCode:D08A clm69659 20 urn:un:unece:uncefact:codelist:standard:UNECE:EventTimeReferenceCodePaymentTermsEvent: D08A clm62475PaymentTermsEvent 21 urn:un:unece:uncefact:codelist:standard:UNECE:EarnedValueCalculationMethod:D08A clm69657 22 urn:un:unece:uncefact:codelist:standard:UNECE:DocumentStatusCode:D08A clm61373 23 urn:un:unece:uncefact:codelist:standard:UNECE:AdjustmentReasonDescriptionCode:D08A clm64465 24 urn:un:unece:uncefact:codelist:standard:UNECE:DocumentNameCode:D08A clm61001 25 urn:un:unece:uncefact:codelist:standard:UNECE:DeliveryTermsCode:D08A clm64053 26 urn:un:unece:uncefact:codelist:standard:UNECE:CostManagementCode:D08A clm69653 27 urn:un:unece:uncefact:codelist:standard:UNECE:DutyorTaxorFeeCategoryCode:D08A clm65305 28 urn:un:unece:uncefact:codelist:standard:UNECE:DocumentNameCodeBillingDocument:D08A clm61001BillingDocument 29 urn:un:unece:uncefact:codelist:standard:UNECE:CostReportingCode:D08A clm69655 30 urn:un:unece:uncefact:codelist:standard:UNECE:HierarchicalStructureTypeCode:D08A clm69661 31 urn:un:unece:uncefact:codelist:standard:UNECE:ContractTypeCode:D08A clm69651 32 urn:un:unece:uncefact:codelist:standard:UNECE:DutyTaxFeeTypeCode:D08A clm65153 33 urn:un:unece:uncefact:codelist:standard:UNECE:EventTimeReferenceCode:D08A clm62475 66 № Namespace identifier Prefix 1 2 3 34 urn:un:unece:uncefact:codelist:standard:UNECE:MeasurementUnitCommonCodeDuration:4 clm6Recommendation20Durati on 35 urn:un:unece:uncefact:identifierlist:standard:5:ISO316612A:SecondEdition2006VI-3 ids5ISO316612A 36 urn:un:unece:uncefact:codelist:standard:IANA:MIMEMediaType:2008-11-12 clmIANAMIMEMediaType 37 urn:un:unece:uncefact:codelist:standard:IANA:CharacterSetCode:2007-05-14 clmIANACharacterSetCode 38 urn:un:unece:uncefact:codelist:standard:6:0133:40106 clm60133 39 urn:un:unece:uncefact:codelist:standard:5:ISO42173A:2008-11-12 clm5ISO42173A 40 urn:un:unece:uncefact:codelist:standard:6:Recommendation20:5 clm6Re
commendation20 41 urn:un:unece:uncefact:data:standard:UnqualifiedDataType:6 udt Table B2 Requisite composition of an electronic document (data) structure «Information about certificate of origin» (Certificate) Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. RootDocument Certificate data ds:RootDocumentType 1 1 CancellationDateTime Date of the certificate annulment Optional ds:RootDocumentIssueDateTimeType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A1 line 6 Absent at form 0..1 2 EffectiveDateTime Date of certificate information change Optional ds:RootDocumentEffectiveDateTimeT yp Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A1 line7 Absent at form 0..1 67 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 3 ExpirationDateTime Expiration date of the certificate Mandatory ds:RootDocumentExpirationDateTime Type Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A2 line 4 Absent at form 1 4 FunctionCode Function code: Mandatory One of the values is specified: ORG - the issued certificate of origin is the original; DBL - the issued certificate of origin is the duplicate of the certificate of origin; CHG - the certificate of origin is issued in substitution of the original certificate of origin ds:RootDocumentFunctionCodeType Format – an..3. EDIFACT codes (1225) Appendix A Tab A1 line 2 5 1 5 FunctionalReferenceID Certificate unique identifier Optional ds:RootDocumentFunctionalReferenceI DType Format – an..35 Appendix A Tab A2 line 2 4 0..1 6 ID Registration number of the certificate Mandatory ds:RootDocumentIdentificationIDTyp e Format – an..35 Appendix A Tab A2 line 1 4 1 7 IssueDateTime Date of certificate issue Mandatory ds:RootDocumentIssueDateTimeType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A2 line 3 12 1 8 issueLocationID Place of certificate issue Mandatory ds:RootDocumentIssueLocationIdentif icationIDType Format – an..5 UN/LOCODE Appendix A Tab A1 line 4 12 1 9 TypeCode Type of the certificate, coded.. Mandatory Fixed value «EAV» ds:RootDocumentTypeCodeType Format – an..3 Appendix A Tab A1 line 1 4 1 10 AdditionalDocument Additional Information Defined by the types of nesting elements see lines 11-46 see lines 11-46 1 11 IssueDateTime ApplicationDate Mandatory ds:AdditionalDocumentIssueDateTime Type Appendix A Tab A1 line 13 13 1 68 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone 12 issueLocationID Application Place, coded Mandatory ds:AdditionalDocumentIssueLocationI dentificationIDType Format – an..5 UN/LOCODE Appendix A Tab A1 line 13 Absent at form 1 13 IssueLocationName Application Place Mandatory ds:AdditionalDocumentIssueLocation NameTextType Format – an..256 Appendix A Tab A1 line 13 13 1 14 @languageID Language identifier Optional “En” by Default xs:language Format – an..35.
IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 15 Authenticator Information about the authorized body that issued the certificate Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 11 12 1 16 Name Name of the authorized body that issued the certificate Mandatory ds:AuthenticatorNameTextType Format - an..70 Appendix A Tab A1 line 11 12 1 17 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 18 ID Identifier of the authorized body that issued (authenticated) the certificate Mandatory ds:AuthenticatorIdentificationIDType Format – an..17. International codes (e.g. DUNS, EAN) or user codes Appendix A Tab A1 line 11 Absent at form 1 19 RoleCode RoleCode of the authorized body that issued (authenticated) the certificate Mandatory Fixed value AX. ds:AuthenticatorRoleCodeType Format – an..3. UNTDID 3035 = AX, Authenticating party - Absent at form 1 20 Address Address Data of authorized body that issued (authenticated) the certificate Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 11 12 1 21 TypeCode Address type code Optional ds:AddressTypeCodeType - Absent at form 0..1 69 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. Format – an..3. EDIFACT codes (3131) 22 CityName City name, city Optional ds:AddressCityNameTextType Format – an..35 Appendix A Tab A1 line 11 12 0..1 23 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 24 CountryCode Country code according to ISO 3166 Certificate issued country code. Mandatory ds:AddressCountryCodeType Format – a2.EDIFACT codes (3207) = ISO 3166-1 2-alpha code Appendix A Tab A1 line 4 and 11 4 1 25 CountrySubDivision Code Code of the country subdivision Optional ds:AddressCountrySubDivisionCodeT ype Format – an..9. EDIFACT codes (3229) = ISO 3166-2 2-alpha code or User code Appendix A Tab A1 line 11 12 0..1 26 CountrySubDivision Name Name of the country subdivision Optional ds:AddressCountrySubDivisionNameT extType Format – an..35 Appendix A Tab A1 line 11 12 0..1 27 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 28 Line Building number and street name, or P/O Box Building number Optional ds:AddressLineTextType Format – an..70 Appendix A Tab A1 line 11 12 0..1 29 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 30 PostcodeID Post code Optional ds:AddressPostcodeIDType Format – an..9 Appendix A Tab A1 line 11 12 0..1 31 LPCOAuthorizedParty Applicant data Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 13 13 1 32 Name Applicant Name Mandatory ds:LPCOAuthorizedPartyNameTextTy pe Format - an..70 Appendix A Tab A1 line 13 13 1 33 @languageID Language identifier xs:language - - 0..1 70 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. Optional “En” by Default Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt 34 ID Identifier of the applicant Optional ds:LPCOAuthorizedPartyIdentification IDType Format – an..17. International codes (e.g.
DUNS, EAN) or user codes - Absent at form 0..1 35 RoleCode RoleCode of the body that issued (authenticated) the certificate Mandatory Fixed value – DT. ds:LPCOAuthorizedPartyRoleCodeTy pe Format – an..3. UNTDID 3035 = DT, Declarant - Absent at form 1 36 Address Applicant Address Data Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 13 13 1 37 TypeCode Address type code Optional ds:AddressTypeCodeType Format – an..3. EDIFACT codes (3131) - Absent at form 0..1 38 CityName City name, city Optional ds:AddressCityNameTextType Format – an..35 Appendix A Tab A1 line 13 13 0..1 39 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 40 CountryCode Country code according to ISO 3166 Mandatory ds:AddressCountryCodeType Format – a2.EDIFACT codes (3207) = ISO 3166-1 2-alpha code Appendix A Tab A1 line 13 13 1 41 CountrySubDivision Code Code of the country subdivision Optional ds:AddressCountrySubDivisionCodeT ype Format – an..9. EDIFACT codes (3229) = ISO 3166-2 2-alpha code or User code Appendix A Tab A1 line 13 13 0..1 42 CountrySubDivision Name Name of the country subdivision Optional ds:AddressCountrySubDivisionNameT extType Format – an..35 Appendix A Tab A1 line 13 13 0..1 43 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 71 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 44 Line Building number and street name, or P/O Box Building number Optional ds:AddressLineTextType Format – an..70 Appendix A Tab A1 line 13 Appendix A Tab A1 line 13- 0..1 45 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 46 PostcodeID Post code Optional ds:AddressPostcodeIDType Format – an..9 Appendix A Tab A1 line 13 Appendix A Tab A1 line 13- 0..1 47 AdditionalInformation Special Marks Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 8, 15 see lines 48-52 1..* 48 Content Additional Information description in free form. Optional Used for transmitting the transfer of information about the certificate issued retroactively (provided that the value is specified in the Statement Code - R.TR) ds:AdditionalInformationContentText Type Format – an..512 Appendix A Tab A1 line 8, 15 Absent at form 0..1 49 StatementCode Type code for tha additional information: “R.DT” for data registration date-time in authorized body database, “R.TR” if the certificate was isuued retroactively/ Mandatory ds:AdditionalInformationStatementCo deType Format – an..17, User codes Appendix A Tab A1 line 8, 15 Absent at form for ‘R.DT’, Section 5 for ‘R.TR’ 1 50 StatementDescription StatementCode description in free- form. Optional ds:AdditionalInformationStatementDe scriptionTextType Format – n..512 Appendix A Tab A1 line 8, 15 Absent at form 0..1 51 @languageID Language identifier Optional “En” by Default Appendix A Tab A1 line 8, 15 - - 0..1 52 LimitDateTime Certificate data registration date- time in authorized body database. Mandatory for StatementCode «R.DT», prohibited (0) для StatementCode «R.TR», ds:AdditionalInformationLimitDateTi meType Format – an..17.
UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A1 line 15 Absent at form 0..1 53 GoodsShipment Goods shipment Mandatory Defined by the types of nesting elements Appendix A Tab A4 6-11 1 72 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 54 ExportationCountryCode Origin country code according to ISO 3166 Mandatory ds:GoodsShipmentExportationCountry CodeType Format – a2.EDIFACT codes (3207) = ISO 3166-1 2-alpha code Appendix A Tab A1 line 10 13 1 55 AdditionalInformation Additional iformation on invoice issued in the Third Country Optional Defined by the types of nesting elements Appendix A Tab A5 line 2 8 0..* 56 Content Data required: Name and the country of the company which issued the invoice; information that the invoice will be issued later, as well as the trade name and the address of a physical person or a legal entity which will issue this invoice in the third country. Mandatory) ds:AdditionalInformationContentText Type Format – an..512 Appendix A Tab A5 line 2 8 1 57 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 58 StatementCode Type Code for the additional information: Invoice is issued in the third country Mandatory Fixed value = «TCI» ds:AdditionalInformationStatementCo deType Format – an..17, User codes Appendix A Tab A5 line 2 8 1 59 StatementDescription StatementCode description in free- form... Mandatory ds:AdditionalInformationStatementDe scriptionTextType Format – n..512 Appendix A Tab A5 line 2 Absent at form 0..1 60 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 61 Consignee Information about Consignee Optional Defined by the types of nesting elements Appendix A Tab 3 line 3 2 0..1 62 Name Name of Consignee Mandatory ds:ConsigneeNameTextType Format – an..70 Appendix A Tab A3 line 3 2 1 73 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 63 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 64 ID Consignee Identifier Optional ds:ConsigneeIdentificationIDType Format – an..17. International codes (e.g. DUNS, EAN) or user codes - Absent at form 0..1 65 RoleCode Consignee RoleCode Mandatory Fixed value – CN. ds:ConsigneeRoleCodeType Format – an..3. UNTDID 3035 = CN - Absent at form 1 66 Address Consignee address data Mandatory The element has an element content Appendix A Tab A3 line 3 2 1 67 TypeCode Address type code Optional ds:AddressTypeCodeType Format – an..3. EDIFACT codes (3131) - Absent at form 0..1 68 CityName City name, city Optional ds:AddressCityNameTextType Format – an..35 Appendix A Tab A3 line 3 2 0..1 69 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 70 CountryCode Country code according to ISO 3166 Mandatory ds:AddressCountryCodeType Format – a2.EDIFACT codes (3207) = ISO 3166-1 2-alpha code Appendix A Tab A3 line 3 2 1 71 CountrySubDivision Code Code of the country subdivision Optional ds:AddressCountrySubDivisionCodeT ype Format – an..9.
EDIFACT codes (3229) = ISO 3166-2 2-alpha code or User code Appendix A Tab A3 line 3 2 0..1 72 CountrySubDivision Name Name of the country subdivision Optional ds:AddressCountrySubDivisionNameT extType Format – an..35 Appendix A Tab A3 line 3 2 0..1 73 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 74 Line Building number and street name, or P/O Box Building number Optional ds:AddressLineTextType Format – an..70 Appendix A Tab A3 line 3 2 0..1 74 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 75 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 76 PostcodeID Post code Optional ds:AddressPostcodeIDType Format – an..9 Appendix A Tab A3 line 3 2 0..1 77 Contact Data on Consignee contact persons Optional Defined by the types of nesting elements - Absent at form 0..* 78 Name Contact person’s name Optional ds:ContactNameTextType Format – an..70 - Absent at form 0..1 79 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 80 Communication Information about communication channels Optional Defined by the types of nesting elements - Absent at form 0..* 81 ID Communication link identifier – phone number, e-mail address etc. Mandatory ds:CommunicationIdentificationIDTyp e Format – an..50 - Absent at form 1 82 TypeID Communication link type: code from EDIFACT Codelist 3155 Optional ds:CommunicationTypeIDType Format – an..3. EDIFACT codes (3155) - Absent at form 0..1 83 Consignment Route and transport details Optional Defined by the types of nesting elements Appendix A Tab A3 line 4 3 0..* 84 BorderTransportMeans Information about transport means Optional Defined by the types of nesting elements Appendix A Tab A3 line 4 3 0..* 85 Name Border Transport Means Name Optional ds:BorderTransportMeansNameTextT ype Format - an..35 Appendix A Tab A3 line 4 3 0..1 86 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 87 ID Transport means identifier Optional For the road transport – national registration numbers; ds:BorderTransportMeansIdentificatio nIDType Format – an..25 Appendix A Tab A3 line 4 3 0..1 75 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult.
For the railway transport – registration numbers of vans (platforms, tanks etc); For the sea (maritime) transport – name of a vessel; For the air transport – flight number 88 TypeCode Transportation mode code: Mandatory To be filled in: by the authorities of the EAEU in accordance with the classifier of modes of transport and transportation of goods used in the Union; by the authorities of Viet Nam in accordance with the classifier of modes of transport and transportation of goods used in Viet Nam ds:BorderTransportMeansTypeCodeT ype Format – an..2 See Table C3 Appendix A Tab A3 line 4 3 1 89 @listAgencyNa me Responsible organization Mandatory Values: EAEU, Viet Nam clm63055:AgencyIdentificationCodeC ontentType Format – an..18 - - 1 90 LoadingLocation Loading Location Data Optional Defined by the types of nesting elements Appendix A Tab A3 line 4 3 0..* 91 Name Loading Location Name Mandatory ds:LoadingLocationNameTextType an..256 Appendix A Tab A3 line 4 3 1 92 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 93 ID Loading Location Name, coded Mandatory ds:LoadingLocationIdentificationIDTy pe Format – an..5 UN/LOCODE Appendix A Tab A3 line 4 3 1 94 DepartureDateTime DepartureDateTime Optional ds:LoadingLocationDepartureDateTim eType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A3 line 4 3 0..1 76 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 95 UnloadingLocation Unloading Location Data Optional Defined by the types of nesting elements Appendix A Tab A3 line 4 3 0..* 96 ID Unloading Location Name, coded Mandatory ds:UnloadingLocationIdentificationID Type Format – an..5 UN/LOCODE Appendix A Tab A3 line 4 3 1 97 DeliveryDestination Certificate destination country code Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 5 4 1 98 Address Certificate destination country code Mandatory Defined by the types of nesting elements Appendix A Tab A1 line 5 4 1 99 CountryCode Code of country certificate to be submitted, according to ISO 3166 Mandatory ds:AddressCountryCodeType Format – a2. EDIFACT codes (3207) = ISO 3166-1 2-alpha code Appendix A Tab A1 line 5 4 1 100 Exporter Exporter Data Mandatory Defined by the types of nesting elements Appendix A Tab A3 line 1 1 1 101 Name Exporter Name Mandatory ds:ExporterNameTextType an..70 Appendix A Tab A3 line 1 1 1 102 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 103 ID Exporter Identifier Optional ds:ExporterIdentificationIDType Format – an..17. International codes (e.g. DUNS, EAN) or user codes - Absent at form 0..1 104 RoleCode Exporter RoleCode Mandatory Fixed value EX. ds:ExporterRoleCodeType Format – an..3. UNTDID 3035 = EX - Absent at form 1 105 Address Exporter Address Data Mandatory Defined by the types of nesting elements Appendix A Tab A3 line 1 1 1 106 TypeCode Address type code Optional ds:AddressTypeCodeType Format – an..3. EDIFACT codes (3131) - Absent at form 0..1 107 CityName City name, city Optional ds:AddressCityNameTextType Format – an..35 Appendix A Tab A3 line 1 1 0..1 108 @languageID Language identifier Optional “En” by Default xs:language Format – an..35.
IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 109 CountryCode Country code according to ISO 3166 ds:AddressCountryCodeType Appendix A Tab A3 line 1 1 1 77 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. Mandatory Format – a2.EDIFACT codes (3207) = ISO 3166-1 2-alpha code 110 CountrySubDivision Code Code of the country subdivision Optional ds:AddressCountrySubDivisionCodeT ype Format – an..9. EDIFACT codes (3229) = ISO 3166-2 2-alpha code or User code Appendix A Tab A3 line 1 1 0..1 111 CountrySubDivision Name Name of the country subdivision Optional ds:AddressCountrySubDivisionNameT extType Format – an..35 Appendix A Tab A3 line 1 1 0..1 112 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 113 Line Building number and street name, or P/O Box Building number Optional ds:AddressLineTextType Format – an..70 Appendix A Tab A3 line 1 1 0..1 114 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 115 PostcodeID Post code Optional ds:AddressPostcodeIDType Format – an..9 Appendix A Tab A3 line 1 1 0..1 116 GovernmentAgencyGoodsI tem Data on goods Mandatory Defined by the types of nesting elements Appendix A Tab A4 6-11 1..* 117 SequenceNumeric SequenceNumeric Mandatory ds:CommoditySequenceNumericType Format – n..5 Appendix A Tab A4 line 1 6 1 118 Commodity Description of good at line Mandatory Defined by the types of nesting elements Appendix A Tab A4 line 1 8 1 119 Description General description of good at line Mandatory ds:CommodityDescriptionTextType an..512 Appendix A Tab A4 line 4 8 1 120 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 121 CountQuantity Good Quantity at line Optional ds:CommodityCountQuantityType Format - n..16 Appendix A TabA 4 line 7 10 0..1 122 @unitCode Units of measurement Mandatory clm6Recommendation20:Measuremen tUnitCommonCodeContentType Appendix A Tab A4 line 7 10 1 78 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. Format – an..5. International codes for Union, National codes for Viet Nam See Table C2 123 AdditionalInformati on Infoirmation on additional marks, FTA: If the goods satisfy a description of footwear made of leather for use in indoor and outdoor sporting activities (ex 6403 91, 6403 99) stipulated in Annex 1 to this Agreement the mark “Sporting Footwear” shall be indicated. Optional Defined by the types of nesting elements Appendix A Tab A4 line 5 8 0..* 124 Content Additional Information (additional marks) description in free form. Optional ds:AdditionalInformationContentText Type Format – an..512 - Absent at form 0..1 125 StatementCode Additional marks, coded Fixed value: «Sporting Footwear» Mandatory ds:AdditionalInformationStatementCo deType Format – an..17, User codes= Sporting Footwear. Appendix A Tab A4 line 5 8 1 126 StatementDescrip tion Additional marks. Free text .Marked as «Sporting Footwear» Optional ds:AdditionalInformationStatementDe scriptionTextType Format – n..512 Appendix A Tab A4 line 5 8 0.1 127 @languageI D Language identifier Optional “En” by Default xs:language Format – an..35.
IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 128 Classification Commodity code data Mandatory Defined by the types of nesting elements Appendix A Tab A4 line 3 8 1 129 ID Commodity code according to the line. 6-digits HS code according to The Harmonized Commodity Description and Coding System/ Mandatory ds:ClassificationIdentificationIDType Format – an..18 Appendix A Tab A4 line 3 8 1 130 IdentificationTy peCode Commodity code type Fixed value “ZZZ” – Mutually defined Mandatory ds:ClassificationIdentificationTypeCo deType Format – an..3, EDIFACT codes (7143) - Absent at form 1 79 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 131 GoodsMeasure Goods weight data by line Optional Defined by the types of nesting elements Appendix A Tab A4 line 7 10 0..1 132 GrossMassMeas ure Goods gross weight with units of measurment specification Mandatory ds:GoodsMeasureGrossMassMeasureT ype Format - n..16,6 Appendix A Tab A4 line 7 10 1 133 @unitCode Units of measurement Mandatory clm6Recommendation20:Measuremen tUnitCommonCodeContentType Format – an..5. International codes for Union, National codes for Viet Nam See Table C2 Appendix A Tab A4 line 7 10 1 134 NetNetWeightM easuree Goods Net weight with units of measurment specification Optional ds:GoodsMeasureNetNetWeightMeasu reType Format - n..16,6 Appendix A Tab A4 line 7 10 0..1 135 @unitCode Units of measurement Mandatory clm6Recommendation20:Measuremen tUnitCommonCodeContentType Format – an..5. International codes for Union, National codes for Viet Nam See Table C2 Appendix A Tab A4 line 7 10 1 136 Product Name Additional good data bн line Optional Defined by the types of nesting elements Appendix A Tab A4 line 4 8 0..* 137 Name Good Name or other product characteristic Mandatory ds:ProductNameNameTextType Format – an..35 Appendix A Tab A4 line 4 8 1 138 @languageI D Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 139 NameQualifierC ode A qualifier to describe the commodity name or other product characteristic, e.g., chassis No for motor vehicles/ Optional ds:ProductNameNameQualifierCodeT ype Format – an..3. EDIFACT codes (7081) Appendix A Tab A4 line 4 8 0..1 140 Origin Origin criteria Mandatory Defined by the types of nesting elements Appendix A Tab A4 line 6 12 1 141 RuleCode Origin criteria: Mandatory WO – goods are wholly obtained or produced in a Party as provided for in article 4.4 of Free Trade ds:OriginRuleCodeType Format - an..3. User codes Appendix A Tab A4 line 6 9 1 80 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. Agreement (hereinafter referred to as FTA); PE – goods are produced entirely in the territory of one or both Parties, exclusively from originating materials from one or both Parties; PSR – goods are produced in the territory of a Party using non- originating material and satisfies the requirements as specified in Annex 3 to FTA 142 Packaging Packaging data Mandatory Defined by the types of nesting elements Appendix A Tab A4 line 2 7 1..* 143 MarksNumbersID Free form description of the marks and numbers on a transport unit or package.
Optional ds:PackagingMarksNumbersIDType Format - an..512 UN/ECE Recommendation 15 Appendix A Tab A4 line 7 0..1 144 QuantityQuantity Package quantity Mandatory ds:PackagingQuantityQuantityType Format - n..16,6 Appendix A Tab A4 line 7 1 145 TypeCode Package type Mandatory ds:PackagingTypeCodeType Format - an..2. EDIFACT codes (7065) = UN/ECE Recommendation 21 Annex VI Appendix A Tab A4 line 7 1 146 Importer Importer Data Mandatory Defined by the types of nesting elements Appendix A Tab A3 line 2 2 1 147 Name Importer Name Mandatory ds:ImporterNameTextType an..70 Appendix A Tab A3 line 2 2 1 148 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 149 ID Importer Identifier Optional ds:ExporterIdentificationIDType Format – an..17. International codes (e.g. DUNS, EAN) or user codes - Absent at form 0..1 150 RoleCode Importer RoleCode Mandatory Fixed value – IM. ds:ImporterRoleCodeType Format – an..3. UNTDID 3035 = IM - Absent at form 1 81 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 151 Address Importer address data Mandatory Defined by the types of nesting elements Appendix A Tab A3 line 2 2 1 152 TypeCode Address type code Optional ds:AddressTypeCodeType Format – an..3. EDIFACT codes (3131) - Absent at form 0..1 153 CityName City name, city Optional ds:AddressCityNameTextType Format – an..35 Appendix A Tab A3 line 2 2 0..1 154 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 155 CountryCode Country code according to ISO 3166 Mandatory ds:AddressCountryCodeType Format – a2.EDIFACT codes (3207) = ISO 3166-1 2-alpha code Appendix A Tab A3 line 2 2 1 156 CountrySubDivision Code Code of the country subdivision Optional ds:AddressCountrySubDivisionCodeT ype Format – an..9. EDIFACT codes (3229) = ISO 3166-2 2-alpha code or User code Appendix A Tab A3 line 2 2 0..1 157 CountrySubDivision Name Name of the country subdivision Optional ds:AddressCountrySubDivisionNameT extType Format – an..35 Appendix A Tab A3 line 2 2 0..1 158 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 159 Line Building number and street name, or P/O Box Building number Optional ds:AddressLineTextType Format – an..70 Appendix A Tab A3 line 2 2 0..1 160 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt - - 0..1 161 PostcodeID Post code Optional ds:AddressPostcodeIDType Format – an..9 Appendix A Tab A3 line 2 2 0..1 162 Invoice Invoice data Mandatory Defined by the types of nesting elements Appendix A Tab A4 line 8 11 1..* 163 ID Invoice number by line Mandatory ds:InvoiceIdentificationIDType Format –an..35 Appendix A Tab A5 line 1 11 1 82 Requisite name Requisite description / Mandatory or optional Data type * Reason of inclusion Form section Mult. 164 IssueDateTime Invoice issue date by line Mandatory ds:InvoiceIssueDateTimeType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A5 line 1 11 1 165 TypeCode Invoice Type by line, including invoice, issued by Exporter, invoice, isssued in third-country (TCI). Mandatory ds:InvoiceTypeCodeType Format – an..3. EDIFACT codes (1001) or National codes Appendix A Tab A5 line 1 11 1 166 SequenceNumeric Sequence number.
It has to correlate with the GovernmentAgency GoodsItmem element SequenceNumeric . Mandatory ds:InvoiceSequenceNumericType Format – n..5 Appendix A Tab A5 line 1 6 1 167 PreviousDocument Identification of previous certificates Optional Defined by the types of nesting elements Appendix A Tab A1 line 9 5 0..* 168 ID Registration number of the certificate Mandatory ds:PreviousDocumentIdentificationID Type Format – an..35 Appendix A Tab A1 line 9 5 1 169 IssueDateTime Registration date of the certificate Mandatory ds:RootDocumentIssueDateTimeType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone Appendix A Tab A1 line 9 5 1 170 TypeCode Certificate of origin type code Mandatory Fixed value - 861 ds:RootDocumentTypeCodeType Format - an..3. EDIFACT codes (1001) or National codes=861 - Absent at form 1 Table B3 Requisite composition of an electronic document (data) structure «Notification on absence of information» (Response) Requisite name Requisite description Data type * Mult. RootDocument Notification of the results of processing of information ds:RootDocumentType 1 1 IssueDateTime Date and time of notification Optional ds:RootDocumentIssueDateTimeType Format: an..17 0..1 83 Requisite name Requisite description Data type * Mult. Source: UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone 2 AdditionalInformation Description of the result of information processing in a free form Optional Defined by the types of nesting elements 0..* 3 StatementDescription Description text, up to 512 symbols Mandatory (1) ds:AdditionalInformationStatementDescriptionTextType Format – an..512 1 4 @languageID Language identifier Optional “En” by Default xs:language Format – an..35. IETF RFC 5646 http://www.rfc- editor.org/rfc/rfc5646.txt 0..1 5 ContactOffice Contact information Optional Defined by the types of nesting elements 0..1 6 Contact Contact person Optional Defined by the types of nesting elements 0..* 7 Name Contact person’s name Mandatory ds:ContactNameTextType Format: an..70 1 8 @languageID Language identifier Optional “En” by Default xs:language Format: an..35 Source: IETF RFC 5646 http://www.rfc-editor.org/rfc/rfc5646.txt, IANA Language Subtag Registry http://www.iana.org/assignments/language-subtag-registry 0..1 9 Communication Information about communication links Mandatory Defined by the types of nesting elements 1..* 10 ID Communication link identifier Mandatory ds:CommunicationIdentificationIDType Format: an..50 1 11 TypeID Communication link type: code from EDIFACT Codelist 3155 Optional ds:CommunicationTypeIDType Format: an..3 Source: EDIFACT codes (3155) 0..1 12 Communication Information about communication links Optional 0..* 13 ID Communication link identifier Mandatory ds:CommunicationIdentificationIDType Format: an..50 1 14 TypeID Communication link type: code from EDIFACT Codelist 3155 Optional ds:CommunicationTypeIDType Format: an..3 Source: EDIFACT codes (3155) 0..1 15 Error Validation error Optional Defined by the types of nesting elements 0..* 16 ValidationCode Error code Mandatory ds:ErrorValidationCodeType Foramt an..3. WCO codes or user codes 1 84 Requisite name Requisite description Data type * Mult.
17 @name Error message text Optional xs:string 0..1 18 Pointer Error location Optional Defined by the types of nesting elements 0..* 19 SequenceNumeric Sequence number Mandatory ds:PointerSequenceNumericType Format - n..5 1 20 TagID Data element tag identifier Mandatory ds:PointerTagIDType Format - an..4 1 21 Status Status of processing Mandatory Defined by the types of nesting elements 1 22 NameCode Status code: Mandatory 0 – Data processed successfully 1 – No data available ds:StatusNameCodeType Format – n1 1 23 ReleaseDateTime Date and time of status Mandatory ds:StatusReleaseDateTimeType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone 1 24 Declaration Processed certificate transaction identifier Optional Defined by the types of nesting elements 0..1 FunctionalReferenceID Certificate unique identifier Optional ds: DeclarationFunctionalReferenceIDType Format – an..35 0..1 26 ID Certificate registration number Mandatory ds:RootDocumentIdentificationIDType Format: an..35 1 Table B4 Requisite composition of an electronic document (data) structure «Request for information about certificates of origin» (Request) Requisite name Requisite description Data type Mult. RootDocument Information about certificate RootDocumentType 1 1 ID Certificate ID Mandatory ds:RootDocumentIdentificationIDType Format – an..35 0..1 2 IssueDateTime Date of the certificate issue or date of data update Mandatory ds:RootDocumentIssueDateTimeType Format – an..17. UNTDID 2379 = 304 CCYYMMDDHHMMSSZZZ Z=Time zone 1 3 IssueLocationID Country of issuance of the certificate code. Mandatory ds:RootDocumentIssueLocationIdentificationIDType Format – an..5 UN/LOCODE 1 85 Requisite name Requisite description Data type Mult. UN/LOCODE data format: (first two symbols is country code - format ISO 3166-1 alpha-2) 4 TypeCode Type of the certificate, coded. Fixed value «EAV» Mandatory ds:RootDocumentTypeCodeType Format – an..3 0..1 * There are the format rules explanations: 1) n – digit in the interval 0..9 is allowed; 2) a – character in the intervals a-z, A-Z is allowed 3) an – both: digit in the interval 0..9 or character in the interval a-z, A-Z is allowed 4) ak, where k>0 – a sting of characters with length k; an..k, where k>0 – string of characters and digits with length less than k+1. 86 Appendix C.
W3C XML-Schemes Table C1 Requisite of an electronic document (information) structure «Information about certificates of origin» (Certificate) <?xml version="1.0" encoding="UTF-8"?> <!-- edited with XMLSpy v2013 sp1 (http://www.altova.com) by AMD (ru-Board) --> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:wco:datamodel:WCO:Declaration:2" xmlns:ds="urn:wco:datamodel:WCO:DS:1" targetNamespace="urn:wco:datamodel:WCO:Declaration:2"> <xs:import namespace="urn:wco:datamodel:WCO:DS:1" schemaLocation="DS_1p0.xsd"/> <xs:element name="RootDocument" type="RootDocumentType"/> <xs:complexType name="RootDocumentType"> <xs:sequence> <xs:element name="CancellationDateTime" type="ds:RootDocumentCancellationDateTimeType" minOccurs="0"/> <xs:element name="EffectiveDateTime" type="ds:RootDocumentEffectiveDateTimeType" minOccurs="0"/> <xs:element name="ExpirationDateTime" type="ds:RootDocumentExpirationDateTimeType"/> <xs:element name="FunctionCode" type="ds:RootDocumentFunctionCodeType"/> <xs:element name="FunctionalReferenceID" type="ds:RootDocumentFunctionalReferenceIDType" minOccurs="0"/> <xs:element name="ID" type="ds:RootDocumentIdentificationIDType"/> <xs:element name="IssueDateTime" type="ds:RootDocumentIssueDateTimeType"/> <xs:element name="issueLocationID" type="ds:RootDocumentIssueLocationIdentificationIDType"/> <xs:element name="TypeCode" type="ds:RootDocumentTypeCodeType"/> <xs:element name="AdditionalDocument"> <xs:complexType> <xs:sequence> <xs:element name="IssueDateTime" type="ds:AdditionalDocumentIssueDateTimeType"/> <xs:element name="issueLocationID" type="ds:AdditionalDocumentIssueLocationIdentificationIDType"/> <xs:element name="IssueLocationName" type="ds:AdditionalDocumentIssueLocationNameTextType"/> <xs:element name="Authenticator"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:AuthenticatorNameTextType"/> <xs:element name="ID" type="ds:AuthenticatorIdentificationIDType"/> <xs:element name="RoleCode" type="ds:AuthenticatorRoleCodeType"/> <xs:element name="Address"> <xs:complexType> <xs:sequence> <xs:element name="TypeCode" type="ds:AddressTypeCodeType" minOccurs="0"/> <xs:element name="CityName" type="ds:AddressCityNameTextType" minOccurs="0"/> <xs:element name="CountryCode" type="ds:AddressCountryCodeType"/> <xs:element name="CountrySubDivisionCode" type="ds:AddressCountrySubDivisionCodeType" minOccurs="0"/> 87 <xs:element name="CountrySubDivisionName" type="ds:AddressCountrySubDivisionNameTextType" minOccurs="0"/> <xs:element name="Line" type="ds:AddressLineTextType" minOccurs="0"/> <xs:element name="PostcodeID" type="ds:AddressPostcodeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="LPCOAuthorizedParty"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:LPCOAuthorizedPartyNameTextType"/> <xs:element name="ID" type="ds:LPCOAuthorizedPartyIdentificationIDType" minOccurs="0"/> <xs:element name="RoleCode" type="ds:LPCOAuthorizedPartyRoleCodeType"/> <xs:element name="Address"> <xs:complexType> <xs:sequence> <xs:element name="TypeCode" type="ds:AddressTypeCodeType" minOccurs="0"/> <xs:element name="CityName" type="ds:AddressCityNameTextType" minOccurs="0"/> <xs:element name="CountryCode" type="ds:AddressCountryCodeType"/> <xs:element name="CountrySubDivisionCode" type="ds:AddressCountrySubDivisionCodeType" minOccurs="0"/> <xs:element name="CountrySubDivisionName" type="ds:AddressCountrySubDivisionNameTextType" minOccurs="0"/> <xs:element name="Line" type="ds:AddressLineTextType" minOccurs="0"/> <xs
:element name="PostcodeID" type="ds:AddressPostcodeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="AdditionalInformation"> <xs:complexType> <xs:sequence> <xs:element name="StatementCode" type="ds:AdditionalInformationStatementCodeType" minOccurs="0"/> <xs:element name="StatementDescription" type="ds:AdditionalInformationStatementDescriptionTextType" minOccurs="0"/> <xs:element name="LimitDateTime" type="ds:AdditionalInformationLimitDateTimeType"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GoodsShipment"> <xs:complexType> <xs:sequence> 88 <xs:element name="ExportationCountryCode" type="ds:GoodsShipmentExportationCountryCodeType"/> <xs:element name="AdditionalInformation" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="Content" type="ds:AdditionalInformationContentTextType"/> <xs:element name="StatementCode" type="ds:AdditionalInformationStatementCodeType"/> <xs:element name="StatementDescription" type="ds:AdditionalInformationStatementDescriptionTextType"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Consignee" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:ConsigneeNameTextType"/> <xs:element name="ID" type="ds:ConsigneeIdentificationIDType" minOccurs="0"/> <xs:element name="RoleCode" type="ds:ConsigneeRoleCodeType"/> <xs:element name="Address"> <xs:complexType> <xs:sequence> <xs:element name="TypeCode" type="ds:AddressTypeCodeType" minOccurs="0"/> <xs:element name="CityName" type="ds:AddressCityNameTextType" minOccurs="0"/> <xs:element name="CountryCode" type="ds:AddressCountryCodeType"/> <xs:element name="CountrySubDivisionCode" type="ds:AddressCountrySubDivisionCodeType" minOccurs="0"/> <xs:element name="CountrySubDivisionName" type="ds:AddressCountrySubDivisionNameTextType" minOccurs="0"/> <xs:element name="Line" type="ds:AddressLineTextType" minOccurs="0"/> <xs:element name="PostcodeID" type="ds:AddressPostcodeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Contact" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:ContactNameTextType" minOccurs="0"/> <xs:element name="Communication" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:CommunicationIdentificationIDType"/> <xs:element name="TypeID" type="ds:CommunicationTypeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Communication" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:CommunicationIdentificationIDType"/> 89 <xs:element name="TypeID" type="ds:CommunicationTypeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Consignment" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="BorderTransportMeans" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:BorderTransportMeansNameTextType" minOccurs="0"/> <xs:element name="ID" type="ds:BorderTransportMeansIdentificationIDType" minOccurs="0"/> <xs:element name="TypeCode" type="ds:BorderTransportMeansTypeCodeType"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="LoadingLocation" minOccurs="0" maxOccurs="unbounded"> <xs:complexType>
<xs:sequence> <xs:element name="Name" type="ds:LoadingLocationNameTextType"/> <xs:element name="ID" type="ds:LoadingLocationIdentificationIDType"/> <xs:element name="DepartureDateTime" type="ds:LoadingLocationDepartureDateTimeType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="UnloadingLocation" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:UnloadingLocationIdentificationIDType"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="DeliveryDestination"> <xs:complexType> <xs:sequence> <xs:element name="Address"> <xs:complexType> <xs:sequence> <xs:element name="CountryCode" type="ds:AddressCountryCodeType"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> 90 </xs:element> <xs:element name="Exporter"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:ExporterNameTextType"/> <xs:element name="ID" type="ds:ExporterIdentificationIDType" minOccurs="0"/> <xs:element name="RoleCode" type="ds:ExporterRoleCodeType"/> <xs:element name="Address"> <xs:complexType> <xs:sequence> <xs:element name="TypeCode" type="ds:AddressTypeCodeType" minOccurs="0"/> <xs:element name="CityName" type="ds:AddressCityNameTextType" minOccurs="0"/> <xs:element name="CountryCode" type="ds:AddressCountryCodeType"/> <xs:element name="CountrySubDivisionCode" type="ds:AddressCountrySubDivisionCodeType" minOccurs="0"/> <xs:element name="CountrySubDivisionName" type="ds:AddressCountrySubDivisionNameTextType" minOccurs="0"/> <xs:element name="Line" type="ds:AddressLineTextType" minOccurs="0"/> <xs:element name="PostcodeID" type="ds:AddressPostcodeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="GovernmentAgencyGoodsItem" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="SequenceNumeric" type="ds:CommoditySequenceNumericType"/> <xs:element name="Commodity"> <xs:complexType> <xs:sequence> <xs:element name="Description" type="ds:CommodityDescriptionTextType"/> <xs:element name="CountQuantity" type="ds:CommodityCountQuantityType" minOccurs="0"/> <xs:element name="AdditionalInformation" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="StatementCode" type="ds:AdditionalInformationStatementCodeType"/> <xs:element name="StatementDescription" type="ds:AdditionalInformationStatementDescriptionTextType"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Classification"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:ClassificationIdentificationIDType"/> <xs:element name="IdentificationTypeCode" type="ds:ClassificationIdentificationTypeCodeType"/> </xs:sequence> </xs:complexType> 91 </xs:element> <xs:element name="GoodsMeasure" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="GrossMassMeasure" type="ds:GoodsMeasureGrossMassMeasureType"/> <xs:element name="NetNetWeightMeasure" type="ds:GoodsMeasureNetNetWeightMeasureType"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ProductName" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:ProductNameNameTextType"/> <xs:element name="NameQualifierCode" type="ds:ProductNameNameQualifierCodeType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Origin"> <xs:complexType> <xs:sequence> <xs:element name="RuleCode" type="ds:OriginRuleCodeType"/> </xs:s
equence> </xs:complexType> </xs:element> <xs:element name="Packaging" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="MarksNumbersID" type="ds:PackagingMarksNumbersIDType" minOccurs="0"/> <xs:element name="QuantityQuantity" type="ds:PackagingQuantityQuantityType"/> <xs:element name="TypeCode" type="ds:PackagingTypeCodeType"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Importer"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:ImporterNameTextType"/> <xs:element name="ID" type="ds:ExporterIdentificationIDType" minOccurs="0"/> <xs:element name="RoleCode" type="ds:ImporterRoleCodeType"/> <xs:element name="Address"> <xs:complexType> <xs:sequence> <xs:element name="TypeCode" type="ds:AddressTypeCodeType" minOccurs="0"/> 92 <xs:element name="CityName" type="ds:AddressCityNameTextType" minOccurs="0"/> <xs:element name="CountryCode" type="ds:AddressCountryCodeType"/> <xs:element name="CountrySubDivisionCode" type="ds:AddressCountrySubDivisionCodeType" minOccurs="0"/> <xs:element name="CountrySubDivisionName" type="ds:AddressCountrySubDivisionNameTextType" minOccurs="0"/> <xs:element name="Line" type="ds:AddressLineTextType" minOccurs="0"/> <xs:element name="PostcodeID" type="ds:AddressPostcodeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Invoice" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:InvoiceIdentificationIDType"/> <xs:element name="IssueDateTime" type="ds:InvoiceIssueDateTimeType"/> <xs:element name="TypeCode" type="ds:InvoiceTypeCodeType"/> <xs:element name="SequenceNumeric" type="ds:InvoiceSequenceNumericType"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="PreviousDocument" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:PreviousDocumentIdentificationIDType"/> <xs:element name="IssueDateTime" type="ds:PreviousDocumentIssueDateTimeType"/> <xs:element name="TypeCode" type="ds:PreviousDocumentTypeCodeType"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:schema> Table C2 The scheme of electronic document data (information) «Notification on absence of information» (Response) <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:wco:datamodel:WCO:Declaration:3" xmlns:ds="urn:wco:datamodel:WCO:DS:1" targetNamespace="urn:wco:datamodel:WCO:Declaration:3"> <xs:import namespace="urn:wco:datamodel:WCO:DS:1" schemaLocation="DS_1p0.xsd"/> <xs:complexType name="RootDocumentType"> <xs:sequence> 93 <xs:element name="FunctionalReferenceID" type="ds:RootDocumentFunctionalReferenceIDType"/> <xs:element name="IssueDateTime" type="ds:RootDocumentIssueDateTimeType" minOccurs="0"/> <xs:element name="AdditionalInformation" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="StatementDescription" type="ds:AdditionalInformationStatementDescriptionTextType"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ContactOffice" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="Contact" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="Name" type="ds:ContactNameTextType"/> <xs:element name="Communication" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:CommunicationIdentificationIDType"/> <xs:el
ement name="TypeID" type="ds:CommunicationTypeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Communication" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ID" type="ds:CommunicationIdentificationIDType"/> <xs:element name="TypeID" type="ds:CommunicationTypeIDType" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Error" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="ValidationCode" type="ds:ErrorValidationCodeType"/> <xs:element name="Pointer" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="SequenceNumeric" type="ds:PointerSequenceNumericType"/> <xs:element name="DocumentSectionCode" type="ds:PointerDocumentSectionCodeType"/> </xs:sequence> </xs:complexType> 94 </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Status"> Table C3 The scheme of electronic document data (information) «Request for information about certificates of origin» (Request) <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:wco:datamodel:WCO:Declaration:1" xmlns:ds="urn:wco:datamodel:WCO:DS:1" targetNamespace="urn:wco:datamodel:WCO:Declaration:1"> <xs:import namespace="urn:wco:datamodel:WCO:DS:1" schemaLocation="DS_1p0.xsd"/> <xs:element name="RootDocument" type="RootDocumentType"/> <xs:complexType name="RootDocumentType"> <xs:sequence> <xs:element name="ID" type="ds:RootDocumentIdentificationIDType" minOccurs="0"/> <xs:element name="IssueDateTime" type="ds:RootDocumentIssueDateTimeType"/> <xs:element name="issueLocationID" type="ds:RootDocumentIssueLocationIdentificationIDType" minOccurs="0"/> <xs:element name="TypeCode" type="ds:RootDocumentTypeCodeType"/> </xs:sequence> </xs:complexType> </xs:schema> Table C4 The scheme of acknowledgment and exception signals data <?xmlversion=«1.0» encoding=«UTF-8»?> <!-- Structure and requisite composition of acknowledgment and exception signals --> <xs:schemaxmlns:xs=«http://www.w3.org/2001/XMLSchema» xmlns:sgn=«urn:EEC:signal:v1.0» targetNamespace=«urn:EEC:signal:v1.0» elementFormDefault=«qualified» attributeFormDefault=«unqualified»> <xs:simpleType name=«EDocIdType»> <xs:annotation> <xs:documentation>Document ID</xs:documentation> </xs:annotation> <xs:restriction base=«xs:token»> <xs:pattern value=«[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA- F]{12}»/> </xs:restriction> </xs:simpleType> <xs:simpleType name=«DateTimeType»> <xs:annotation> <xs:documentation>Date by the Gregorian calendar and time in the Standard ISO 8601 format</xs:documentation> </xs:annotation> 95 <xs:restriction base=«xs:dateTime»/> </xs:simpleType> <xs:simpleType name=«ErrorCodeType»> <xs:annotation> <xs:documentation> Error code designation </xs:documentation> </xs:annotation> <xs:restriction base=«xs:token»> <xs:minLength value=«1»/> <xs:maxLength value=«255»/> </xs:restriction> </xs:simpleType> <xs:simpleType name=«StringType»> <xs:annotation> <xs:documentation> Arbitrary information in text form </xs:documentation> </xs:annotation> <xs:restriction base=«xs:string»/> </xs:simpleType> <xs:complexType name=«DeliveryReceiptType»> <xs:annotation> <xs:documentation>>"Receipt" confirmation signal Type </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name=«SignalId» type=«sgn:EDocIdType»/> <xs:element name=«DateTime» type=«sgn:DateTimeType»/> </xs:sequence> </xs
:complexType> <xs:element name=«DeliveryReceipt» type=«sgn:DeliveryReceiptType»> <xs:annotation> <xs:documentation>"Receipt" confirmation signal </xs:documentation> </xs:annotation> </xs:element> <xs:complexType name=«ProcessingReceiptType»> <xs:annotation> <xs:documentation>"Processing Receipt" confirmation signal Type </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name=«SignalId» type=«sgn:EDocIdType»/> <xs:element name=«DateTime» type=«sgn:DateTimeType»/> </xs:sequence> </xs:complexType> <xs:element name=«ProcessingReceipt» type=«sgn:ProcessingReceiptType»> <xs:annotation> <xs:documentation>"Processing Receipt" confirmation signal </xs:documentation> </xs:annotation> </xs:element> <xs:complexType name=«ValidationErrorType»> <xs:annotation> <xs:documentation>"Error" Signal-exception Type </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name=«SignalId» type=«sgn:EDocIdType»> <xs:annotation> 96 <xs:documentation> Signal-exception ID </xs:documentation> </xs:annotation> </xs:element> <xs:element name=«DateTime» type=«sgn:DateTimeType»> <xs:annotation> <xs:documentation> Date and Time </xs:documentation> </xs:annotation> </xs:element> <xs:element name=«Error» type=«sgn:ErrorType» maxOccurs=«unbounded»> <xs:annotation> <xs:documentation> Error Details </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name=«ErrorType»> <xs:annotation> <xs:documentation> Error Type </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name=«Code» type=«sgn:ErrorCodeType»> <xs:annotation> <xs:documentation> Control Error Code Designation </xs:documentation> </xs:annotation> </xs:element> <xs:element name=«Description» type=«sgn:StringType»> <xs:annotation> <xs:documentation> Control Error Code Designation </xs:documentation> </xs:annotation> </xs:element> <xs:element name=«Details» type=«sgn:StringType» minOccurs=«0»> <xs:annotation> <xs:documentation> Error Detailed Information </xs:documentation> </xs:annotation> </xs:element> <xs:element name=«EDocId» type=«sgn:EDocIdType» minOccurs=«0»> <xs:annotation> <xs:documentation> Identifier of the document in which the error occurred </xs:documentation> </xs:annotation> </xs:element> <xs:element name=«Reference» type=«sgn:StringType» minOccurs=«0»> <xs:annotation> <xs:documentation> String of characters that makes it possible to locate unambiguously an element in the document that caused an error </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:element name=«ValidationError» type=«sgn:ValidationErrorType»> <xs:annotation> <xs:documentation>"ControlError" Signal-exception </xs:documentation> </xs:annotation> 97 </xs:element> </xs:schema> 98 Appendix D.
Examples of electronic documents Table D1 Example of electronic message “Information on the issued certificate of origin” (ESS.VN.MSG.001) <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:urn="urn:EEC:Interaction:v1.0" xmlns:wsa="http://www.w3.org/2005/08/addressing"> <soap:Header> <wsa:To>ESS.VN.VN</wsa:To> <wsa:From> <wsa:Address>ESS.VN.RU</wsa:Address> </wsa:From> <wsa:Action>tr://CERTIFICATE/0.1/ESS.VN.PRC.001/ESS.VN.TRN.001/ESS.VN.MSG.001</ wsa:Action> <wsa:MessageID>urn:uuid:dba8fff6-bbb3-47c3-afb2-a9a9accce8dd</wsa:MessageID> </soap:Header> <soap:Body> <n1:RootDocument xsi:schemaLocation="urn:wco:datamodel:WCO:Declaration:2 Certificate.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:n1="urn:wco:datamodel:WCO:Declaration:2"> <CancellationDateTime>2017-12-17T00:00:00Z</CancellationDateTime> <EffectiveDateTime>2017-10-15T00:00:00Z</EffectiveDateTime> <ExpirationDateTime>2018-09-17T00:00:00Z</ExpirationDateTime> <FunctionCode>CHG</FunctionCode> <FunctionalReferenceID>PcaFAG0kNUGqHYoSTryWbg%3d%3d</FunctionalReferenceID> <ID>12345</ID> <IssueDateTime>2017-09-17T09:30:00Z</IssueDateTime> <issueLocationID>RU MOW</issueLocationID> <TypeCode>EAV</TypeCode> <AdditionalDocument> <IssueDateTime>2017-09-17T00:00:00Z</IssueDateTime> <issueLocationID>RUMOW</issueLocationID> <IssueLocationName>Russian Federation, Moscow</IssueLocationName> <Authenticator> <Name>The Chamber of Commerce and Industry of the Russian Federation (CCI of Russia)</Name> <ID>1027746000853</ID> <RoleCode>AX</RoleCode> <Address> <TypeCode>2</TypeCode> <CityName>Moscow</CityName> <CountryCode>RU</CountryCode> <Line>Ilyinka 6/1, 1 Moscow, Russian Federation</Line> <PostcodeID>109012</PostcodeID> </Address> </Authenticator> <LPCOAuthorizedParty> <Name>RostovVinTrade</Name> <ID>1234567890987</ID> <RoleCode>DT</RoleCode> 99 <Address> <TypeCode>2</TypeCode> <CityName>Rostov-on-Don</CityName> <CountryCode>RU</CountryCode> <Line>Rostov-on-Don, Lenina st, 18, Russia</Line> <PostcodeID>344012</PostcodeID> </Address> </LPCOAuthorizedParty> </AdditionalDocument> <AdditionalInformation> <StatementCode>R.TR</StatementCode> <StatementDescription>Issued Retroactively</StatementDescription> <LimitDateTime>2017-09-16T00:00:00Z</LimitDateTime> </AdditionalInformation> <GoodsShipment> <ExportationCountryCode>RU</ExportationCountryCode> <AdditionalInformation> <Content>Invoice will be issued later by Asia Grocery Distribution Limited. Address：4/F How Ming Factory Building, 99 How Ming Street, Kwun Tong</Content> <StatementCode>TCI</StatementCode> <StatementDescription>Third Country Invoice</StatementDescription> </AdditionalInformation> <Consignee> <Name>LEE KHOA TRADING</Name> <RoleCode>CN</RoleCode> <Address> <CityName>Hanoi</CityName> <CountryCode>VN</CountryCode> <Line>Add.
44/4 Dang Van Ngu Str., Dong Da Distr.,Hanoi, Viet Nam, 115000 </Line> </Address> </Consignee> <Consignment> <BorderTransportMeans> <TypeCode listAgencyName="EAEU">40</TypeCode> </BorderTransportMeans> <LoadingLocation> <Name>Russiian Federation, Moscow</Name> <ID>RUSVO</ID> </LoadingLocation> <UnloadingLocation> <ID>VNHAN</ID> </UnloadingLocation> </Consignment> <DeliveryDestination> <Address> <CountryCode>VN</CountryCode> </Address> </DeliveryDestination> <Exporter> <Name>RostovVinTrade</Name> <RoleCode>EX</RoleCode> <Address> 100 <TypeCode>2 </TypeCode> <CityName>Rostov-on-Don</CityName> <CountryCode>RU</CountryCode> <Line>Rostov-on-Don, Lenina st, 18, Russia, 344012</Line> </Address> </Exporter> <GovernmentAgencyGoodsItem> <SequenceNumeric>1</SequenceNumeric> <Commodity> <Description>Sparkling wine</Description> <CountQuantity unitCode="796">144</CountQuantity> <Classification> <ID>2204101100</ID> <IdentificationTypeCode>HS code</IdentificationTypeCode> </Classification> <GoodsMeasure> <GrossMassMeasure unitCode="166">80</GrossMassMeasure> <NetNetWeightMeasure unitCode="166">60</NetNetWeightMeasure> </GoodsMeasure> <ProductName> <Name>Rostovskoye Igristoye</Name> <NameQualifierCode>brand name</NameQualifierCode> </ProductName> </Commodity> <Origin> <RuleCode>WO</RuleCode> </Origin> <Packaging> <QuantityQuantity>1</QuantityQuantity> <TypeCode>32</TypeCode> </Packaging> </GovernmentAgencyGoodsItem> <GovernmentAgencyGoodsItem> <SequenceNumeric>2</SequenceNumeric> <Commodity> <Description>Dry white wine</Description> <CountQuantity unitCode="796">144</CountQuantity> <Classification> <ID>2204210700</ID> <IdentificationTypeCode>HS code</IdentificationTypeCode> </Classification> <GoodsMeasure> <GrossMassMeasure unitCode="166">70</GrossMassMeasure> <NetNetWeightMeasure unitCode="166">55</NetNetWeightMeasure> </GoodsMeasure> <ProductName> <Name>TSIMLYANSKY RESERVE</Name> <NameQualifierCode>brand name</NameQualifierCode> </ProductName> </Commodity> <Origin> <RuleCode>WO</RuleCode> 101 </Origin> <Packaging> <QuantityQuantity>1</QuantityQuantity> <TypeCode>32</TypeCode> </Packaging> </GovernmentAgencyGoodsItem> <GovernmentAgencyGoodsItem> <SequenceNumeric>3</SequenceNumeric> <Commodity> <Description>vodka</Description> <CountQuantity unitCode="796">144</CountQuantity> <Classification> <ID>2208601100</ID> <IdentificationTypeCode>HS code</IdentificationTypeCode> </Classification> <GoodsMeasure> <GrossMassMeasure unitCode="166">60</GrossMassMeasure> <NetNetWeightMeasure unitCode="166">50</NetNetWeightMeasure> </GoodsMeasure> <ProductName> <Name>Ataman Platov</Name> <NameQualifierCode>brand name</NameQualifierCode> </ProductName> </Commodity> <Origin> <RuleCode>WO</RuleCode> </Origin> <Packaging> <QuantityQuantity>1</QuantityQuantity> <TypeCode>32</TypeCode> </Packaging> </GovernmentAgencyGoodsItem> <Importer> <Name>LEE KHOA TRADING</Name> <RoleCode>CN</RoleCode> <Address> <TypeCode>2</TypeCode> <CityName>Hanoi</CityName> <CountryCode>VN</CountryCode> <Line>Add.
44/4 Dang Van Ngu Str., Dong Da Distr.,Hanoi, Viet Nam, 115000 </Line> </Address> </Importer> <Invoice> <ID>12345</ID> <IssueDateTime>2017-08-17T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>1</SequenceNumeric> </Invoice> <Invoice> <ID>12333</ID> <IssueDateTime>2017-08-17T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> 102 <SequenceNumeric>1</SequenceNumeric> </Invoice> <Invoice> <ID>12444</ID> <IssueDateTime>2017-08-18T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>2</SequenceNumeric> </Invoice> <Invoice> <ID>12555</ID> <IssueDateTime>2017-08-19T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>3</SequenceNumeric> </Invoice> </GoodsShipment> <PreviousDocument> <ID>12097</ID> <IssueDateTime>2017-09-01T00:00:00Z</IssueDateTime> <TypeCode>861</TypeCode> </PreviousDocument> </n1:RootDocument> </soap:Body> </soap:Envelope> Table D2 Example of electronic message “Notice on the results of processing of information” (ESS.VN.MSG.002) <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:urn="urn:EEC:Interaction:v1.0" xmlns:wsa="http://www.w3.org/2005/08/addressing"> <soap:Header> <wsa:To>ESS.VN.VN</wsa:To> <wsa:From> <wsa:Address>ESS.VN.RU</wsa:Address> </wsa:From> <wsa:Action>tr://CERTIFICATE/0.1/ESS.VN.PRC.001/ESS.VN.TRN.001/ESS.VN.MSG.002</ wsa:Action> <wsa:MessageID>urn:uuid:55cc3611-b3b4-4cfa-aebb-e12c4a48d20e</wsa:MessageID> <wsa:RelatesTo>urn:uuid:dba8fff6-bbb3-47c3-afb2-a9a9accce8dd</wsa:RelatesTo> </soap:Header> <soap:Body> <n1:RootDocument xsi:schemaLocation="urn:wco:datamodel:WCO:Declaration:3 Response.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:n1="urn:wco:datamodel:WCO:Declaration:3"> <AdditionalInformation> <StatementDescription>Success</StatementDescription> </AdditionalInformation> <Status> <NameCode>0</NameCode> <ReleaseDateTime>2017-09-17T12:33:47Z</ReleaseDateTime> </Status> <Declaration> 103 <FunctionalReferenceID>f6819dcd-0df4-40e2-9e9b-40df4b3c0e4</FunctionalReferenceID> <ID>12345</ID> </Declaration> </n1:RootDocument> </soap:Body> </soap:Envelope> Table D3 Example of electronic message “Notice on absence of information” (ESS.VN.MSG.003) <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:urn="urn:EEC:Interaction:v1.0" xmlns:wsa="http://www.w3.org/2005/08/addressing"> <soap:Header> <wsa:To>ESS.VN.VN</wsa:To> <wsa:From> <wsa:Address>ESS.VN.RU</wsa:Address> </wsa:From> <wsa:Action>tr://CERTIFICATE/0.1/ESS.VN.PRC.002/P.EE.02.TRN.002/ESS.VN.MSG.003</ wsa:Action> <wsa:MessageID>urn:uuid:55cc3611-b3b4-4cfa-aebb-e12c4a48d20e</wsa:MessageID> <wsa:RelatesTo>urn:uuid:23ccf7cb-c507-404f-aa78-4f0152a6633a </wsa:RelatesTo> </soap:Header> <soap:Body> <n1:RootDocument xsi:schemaLocation="urn:wco:datamodel:WCO:Declaration:3 Response.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:n1="urn:wco:datamodel:WCO:Declaration:3"> <AdditionalInformation> <StatementDescription>Success</StatementDescription> </AdditionalInformation> <Status> <NameCode>1</NameCode> <ReleaseDateTime>2017-09-17T12:33:47Z</ReleaseDateTime> </Status> <Declaration> <FunctionalReferenceID>f6819dcd-0df4-40e2-9e9b-40df4b3c0e4</FunctionalReferenceID> <ID>12345</ID> </Declaration> </n1:RootDocument> </soap:Body> </soap:Envelope> Table D4 Example of electronic message “Request for information on the certificate of origin” (ESS.VN.MSG.004) <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:urn="urn:EEC:Interaction:v1.0" xmlns:wsa="http://www.w3.org/2005/08/addressing"> <soap:Header> <wsa:To>ESS.VN.RU</wsa:
To> <wsa:From> <wsa:Address>ESS.VN.VN</wsa:Address> 104 </wsa:From> <wsa:Action>tr://CERTIFICATE/0.1/ESS.VN.PRC.002/ESS.VN.TRN.002/ESS.VN.MSG.004</ wsa:Action> <wsa:MessageID>urn:uuid:23ccf7cb-c507-404f-aa78-4f0152a6633a</wsa:MessageID> </soap:Header> <soap:Body> <ns1:RootDocument xsi:schemaLocation="urn:wco:datamodel:WCO:Declaration:1 Request.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="urn:wco:datamodel:WCO:Declaration:1"> <ID>12345</ID> <IssueDateTime>2016-12-17T00:00:00Z</IssueDateTime> <issueLocationID>RUMOW</issueLocationID> <TypeCode>EAV</TypeCode> </ns1:RootDocument> </soap:Body> </soap:Envelope> Table D5 Example of electronic message “Information on the issued certificate of origin provided in response to the request” (ESS.VN.MSG.005) <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:urn="urn:EEC:Interaction:v1.0" xmlns:wsa="http://www.w3.org/2005/08/addressing"> <soap:Header> <wsa:To>ESS.VN.VN</wsa:To> <wsa:From> <wsa:Address>ESS.VN.RU</wsa:Address> </wsa:From> <wsa:Action>tr://CERTIFICATE/0.1/ESS.VN.PRC.002/ESS.VN.TRN.002/ESS.VN.MSG.005</ wsa:Action> <wsa:MessageID>urn:uuid:84cec07f-122f-459e-a5ef-707188452691</wsa:MessageID> <wsa:RelatesTo>urn:uuid:23ccf7cb-c507-404f-aa78-4f0152a6633a</wsa:RelatesTo> </soap:Header> <soap:Body> <n1:RootDocument xsi:schemaLocation="urn:wco:datamodel:WCO:Declaration:2 Certificate.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:n1="urn:wco:datamodel:WCO:Declaration:2"> <CancellationDateTime>2017-12-17T00:00:00Z</CancellationDateTime> <EffectiveDateTime>2017-10-15T00:00:00Z</EffectiveDateTime> <ExpirationDateTime>2018-09-17T00:00:00Z</ExpirationDateTime> <FunctionCode>CHG</FunctionCode> <FunctionalReferenceID>PcaFAG0kNUGqHYoSTryWbg%3d%3d</FunctionalReferenceID> <ID>12345</ID> <IssueDateTime>2017-09-17T09:30:00Z</IssueDateTime> <issueLocationID>RUMOW</issueLocationID> <TypeCode>EAV</TypeCode> <AdditionalDocument> <IssueDateTime>2017-09-17T00:00:00Z</IssueDateTime> <issueLocationID>RUMOW</issueLocationID> <IssueLocationName>Russian Federation, Moscow</IssueLocationName> <Authenticator> 105 <Name>The Chamber of Commerce and Industry of the Russian Federation (CCI of Russia)</Name> <ID>1027746000853</ID> <RoleCode>AX</RoleCode> <Address> <TypeCode>2</TypeCode> <CityName>Moscow</CityName> <CountryCode>RU</CountryCode> <Line>Ilyinka 6/1, 1 Moscow, Russian Federation</Line> <PostcodeID>109012</PostcodeID> </Address> </Authenticator> <LPCOAuthorizedParty> <Name>RostovVinTrade</Name> <ID>1234567890987</ID> <RoleCode>DT</RoleCode> <Address> <TypeCode>2</TypeCode> <CityName>Rostov-on-Don</CityName> <CountryCode>RU</CountryCode> <Line>Rostov-on-Don, Lenina st, 18, Russia</Line> <PostcodeID>344012</PostcodeID> </Address> </LPCOAuthorizedParty> </AdditionalDocument> <AdditionalInformation> <StatementCode>R.TR</StatementCode> <StatementDescription>Issued Retroactively</StatementDescription> <LimitDateTime>2017-09-16T00:00:00Z</LimitDateTime> </AdditionalInformation> <GoodsShipment> <ExportationCountryCode>RU</ExportationCountryCode> <AdditionalInformation> <Content>Invoice will be issued later by Asia Grocery Distribution Limited. Address：4/F How Ming Factory Building, 99 How Ming Street, Kwun Tong</Content> <StatementCode>TCI</StatementCode> <StatementDescription>Third Country Invoice</StatementDescription> </AdditionalInformation> <Consignee> <Name>LEE KHOA TRADING</Name> <RoleCode>CN</RoleCode> <Address> <CityName>Hanoi</CityName> <CountryCode>VN</CountryCode> <Line>Add.
44/4 Dang Van Ngu Str., Dong Da Distr.,Hanoi, Viet Nam, 115000 </Line> </Address> </Consignee> <Consignment> <BorderTransportMeans> <TypeCode listAgencyName="EAEU">40</TypeCode> </BorderTransportMeans> <LoadingLocation> 106 <Name>Russiian Federation, Moscow</Name> <ID>RUSVO</ID> </LoadingLocation> <UnloadingLocation> <ID>VNHAN</ID> </UnloadingLocation> </Consignment> <DeliveryDestination> <Address> <CountryCode>VN</CountryCode> </Address> </DeliveryDestination> <Exporter> <Name>RostovVinTrade</Name> <RoleCode>EX</RoleCode> <Address> <TypeCode>2</TypeCode> <CityName>Rostov-on-Don</CityName> <CountryCode>RU</CountryCode> <Line>Rostov-on-Don, Lenina st, 18, Russia, 344012</Line> </Address> </Exporter> <GovernmentAgencyGoodsItem> <SequenceNumeric>1</SequenceNumeric> <Commodity> <Description>Sparkling wine</Description> <CountQuantity unitCode="796">144</CountQuantity> <Classification> <ID>2204101100</ID> <IdentificationTypeCode>HS code</IdentificationTypeCode> </Classification> <GoodsMeasure> <GrossMassMeasure unitCode="166">80</GrossMassMeasure> <NetNetWeightMeasure unitCode="166">60</NetNetWeightMeasure> </GoodsMeasure> <ProductName> <Name>Rostovskoye Igristoye</Name> <NameQualifierCode>brand name</NameQualifierCode> </ProductName> </Commodity> <Origin> <RuleCode>WO</RuleCode> </Origin> <Packaging> <QuantityQuantity>1</QuantityQuantity> <TypeCode>32</TypeCode> </Packaging> </GovernmentAgencyGoodsItem> <GovernmentAgencyGoodsItem> <SequenceNumeric>2</SequenceNumeric> <Commodity> <Description>Dry white wine</Description> 107 <CountQuantity unitCode="796">144</CountQuantity> <Classification> <ID>2204210700</ID> <IdentificationTypeCode>HS code</IdentificationTypeCode> </Classification> <GoodsMeasure> <GrossMassMeasure unitCode="166">70</GrossMassMeasure> <NetNetWeightMeasure unitCode="166">55</NetNetWeightMeasure> </GoodsMeasure> <ProductName> <Name>TSIMLYANSKY RESERVE</Name> <NameQualifierCode>brand name</NameQualifierCode> </ProductName> </Commodity> <Origin> <RuleCode>WO</RuleCode> </Origin> <Packaging> <QuantityQuantity>1</QuantityQuantity> <TypeCode>32</TypeCode> </Packaging> </GovernmentAgencyGoodsItem> <GovernmentAgencyGoodsItem> <SequenceNumeric>3</SequenceNumeric> <Commodity> <Description>vodka</Description> <CountQuantity unitCode="796">144</CountQuantity> <Classification> <ID>2208601100</ID> <IdentificationTypeCode>HS code</IdentificationTypeCode> </Classification> <GoodsMeasure> <GrossMassMeasure unitCode="166">60</GrossMassMeasure> <NetNetWeightMeasure unitCode="166">50</NetNetWeightMeasure> </GoodsMeasure> <ProductName> <Name>Ataman Platov</Name> <NameQualifierCode>brand name</NameQualifierCode> </ProductName> </Commodity> <Origin> <RuleCode>WO</RuleCode> </Origin> <Packaging> <QuantityQuantity>1</QuantityQuantity> <TypeCode>32</TypeCode> </Packaging> </GovernmentAgencyGoodsItem> <Importer> <Name>LEE KHOA TRADING</Name> <RoleCode>CN</RoleCode> <Address> 108 <TypeCode>2</TypeCode> <CityName>Hanoi</CityName> <CountryCode>VN</CountryCode> <Line>Add.
44/4 Dang Van Ngu Str., Dong Da Distr.,Hanoi, Viet Nam, 115000 </Line> </Address> </Importer> <Invoice> <ID>12345</ID> <IssueDateTime>2017-08-17T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>1</SequenceNumeric> </Invoice> <Invoice> <ID>12333</ID> <IssueDateTime>2017-08-17T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>1</SequenceNumeric> </Invoice> <Invoice> <ID>12444</ID> <IssueDateTime>2017-08-18T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>2</SequenceNumeric> </Invoice> <Invoice> <ID>12555</ID> <IssueDateTime>2017-08-19T00:00:00Z</IssueDateTime> <TypeCode>02017</TypeCode> <SequenceNumeric>3</SequenceNumeric> </Invoice> </GoodsShipment> <PreviousDocument> <ID>12097</ID> <IssueDateTime>2017-09-01T00:00:00Z</IssueDateTime> <TypeCode>861</TypeCode> </PreviousDocument> </n1:RootDocument> </soap:Body> </soap:Envelope> 109 Appendix E. Directories and classifiers Table E1 Units of measurement Classifier (used in the Union) Code Name 166 Kilogram 797 Hundred pieces 246 1000 kilowatt-hour 130 1000 liters 114 1000 cubic meters 798 Thousand pieces 163 Grams 306 Gram fissile isotopes 162 Metric carats (1carat=2*10 (-4) kg 845 Kilogram of dry (90% ) substance 841 Kilogram of hydrogen peroxide 852 Kilogram of potassium oxide 859 Kilogram of potassium hydroxide 861 Kilogram of nitrogen 863 Kilogram of sodium hydroxide 865 Kilogram of phosphorus pentoxide 867 Kilogram of uranium 305 Curie 112 Litre 831 Liter of pure (100%) alcohol 006 Meter 055 Square meter 113 Cubic meter 715 Pair 185 Capacity in tons 796 Piece Units of measurement Classifier (used in the Viet Nam) Code Name DUNK 10 units DPCE 10 pieces DMTR 10 meters HPCE 100 pieces HFT 100 FT HGRM 100 GRAMME HMTR 100 meters HUNV 100 units KSET 1000 sets KPCE 1000 pieces KUNC 1000 units KROL 1000 rolls 110 Code Name KPR 1000 pairs KPKG 1000 packs KUNK 1000 boxes KMTK 1000 square meters KPIP 1000 pipes KUNQ 1000 units KPRO 1000 products KUNV 1000 unit KMTQ 1000m2 ONZ Ounce OII Ounce (including package) OIC Ounce (including container) OMC Ounce (by metal content) ODW Ounce (by dry weight) OZI Measurement Ounce BAN Piece BANG Piece BBL Barrel BICH Piece SET Set PCE Piece UNH Unit CT Cara UNY Unit CEN Centimeter UNA Bottle CHI CHI CM2 cm2 CM3 cm3 UNC unit CONT CONTAINER UNU Piece CUC Unit CUM Group of unit UNN Roll ROL Roll DM dm DM2 dm2 PR pair GLL Galon GRM Gramme GII Gramme (including package) GIC Gramme (including container) GMC Gramme (by metal content) GDW Gramme (by dry weight) PKG Package LC lactose contained HLTR Hectoliter YRD Yard 111 Code Name YDQ Cubic yard YDK Square yard INC Inch UNK Pack/box KL Kiloliter KMTR Kilometer (1000 meters) KHW Kilowatt hour KGM Kilogram KII Kilogram (including package) KIC Kilogram (including container) KMC Kilogram (by metal content) KDW Kilogram (by dry weight) KIT KIT KVA KVA LIEU Dose LTR Litter QT British litter LOT Lot UNL can MTR meter MTQ cubic meter MTK square meter MGRM Milligrams MLT Milliliters MMTR Millimeter MM2 mm2 MM3 mm3 TH Thousands PIP Pipe PTI Pints LBR Pounds LII Pounds (including package) LIC Pounds (including container) LMC Pounds (by metal content) LDW Pounds (by dry weight) FOT Feet FTQ Cubic feet FTK Square feet UNQ Pieces UNB Quyển/Tập RAM RAM SOI String STER Ster DZN Dozens HKGM Quintal (100kg) TAM Piece TNE Ton MII Tons (including package) MIC Tons (including container) 112 Code Name MMC Tons (by metal content) MDW Tons (by dry weight) LTN Long tons STN Short tons UNT Piece TO Sheet GRO Gross GT Gross tonnage TRO Troy ounce DPT Tonnage BAG Bag UND Unit UNV Un
it UNIT UNIT LBS LBS VI Grid INC2 Inch2 SYS System PRO Product PAIL Barred Table E2 Classifier of transport and transportation of goods (used in the Union) Code Name 10 Sea transport* 20 Railway transport* 30 Road transport* 40 Air transport* 50 Mailing 71 Pipeline transport 72 Power line 80 Inland waterway transport * 90 Vehicles transported as goods under their own power 99 Others * Including any vehicle which is transported by said transport type. Classifier of transport and transportation of goods (used in the Viet Nam) Code Name 1 Air route 2 Sea route (container) 3 Sea route (un-container) 4 Land route (truck) 5 Rail way 6 River route 9 Others 113 Table E3 Classifier of documents types used for customs declaration (used in the Union) Code Name 2. Transport (shipping) documents 02011 Bill of lading 02012 Waybill for the carriage of goods by water transport 02013 Railway invoice 02024 TIR carnet 02025 ATA carnet 02022 Baggage check 02014 Other documents required by the rules of railway transportation 02015 Waybill under the Convention on the Contract for the International Carriage of Goods 1956 02016 Another waybill for the carriage of goods by road transport 02017 Air waybill 02018 Transport documents used in the movement of goods through pipelines or power transmission lines 02019 Postal waybill 02020 General waybill for express delivery 02021 Individual waybill for express delivery 02026 Packing List 02099 Other transport (shipping) documents 3. Documents confirming the consummation of foreign trade transaction or other documents confirming the right of possession, use and (or) disposal of goods 03011 Agreement (contract), concluded when consummating the foreign trade transaction 03012 Documents ammending or supplementing the document, the details of which are listed under code 03011 03013 Document confirming consummation of unilateral foreign trade transaction 03014 Documents confirming the right of possession, use and (or) disposal of goods in the absence of any transaction 03021 Documents confirming the transfer of intellectual property rights (author, license agreement, certificate of registration of intellectual property, contract for use of the trademark and similar documents) 03022 Documents confirming the introduction into circulation of goods designated by the trademark within the customs territory of the Customs Union, with the consent of the owner (dealership, distributorship agreement, written consent and similar documents) 03999 Other documents confirming the right of possession, use and (or) disposal of goods 4.
Commercial documents 04021 Invoice to the Contract 04022 Other settlement or commercial documents (including cash or sales receipt for the purchase of goods in retail stores) 04023 Bank documents (if the invoice is paid, depending on the conditions of foreign trade contract), as well as other payment documents reflecting the value of the goods 04025 Pro forma invoice to the Contract 04031 Invoice for the carriage (transportation), loading, unloading and reloading goods 04032 Bank or other payment documents for payment of transportation costs, reflecting the cost of transportation (transportation), loading, unloading and reloading goods 04033 Contract on transportation, loading, unloading or reloading goods 114 Code Name 04041 Invoices for provision of broking services 04042 Bank or other payment documents for provision of broking services 04043 Broking service agreement 04051 Documents on the value of goods and services provided to customers free of charge or at reduced prices for use in connection with the production and sale 04061 Invoice containing information on payments for the use of intellectual property 04062 Bank payment documents, accounting and other documents containing information on payments for the use of intellectual property 04071 Documents (including accounting) and information containing data on part of the income (revenue), which directly or indirectly is owed to the seller as a result of the subsequent sale, disposition or other means of use of goods 04081 Invoice that contains information about the cost of packaging materials and (or) work on the packaging 04082 Bank or other payment documents on the cost of packaging materials and (or) work on the packaging 04083 Contract on the cost of cargo containers, packaging, packaging materials and works on packaging 04091 Accounting records of producer of goods being valued, which contain information on the costs of production or acquisition of materials, of production costs, as well as other operations related to the production of imported goods, commercial invoices of producer of goods being valued, prepared in accordance with generally accepted accounting principles 04101 Invoice on the cost of design, development, engineering, artwork, drawings and sketches 04102 Bank or other payment documents on the cost of design, development, engineering, artwork, drawings and sketches 04111 Invoice for provision of insurance services 04112 Bank or other payment documents on the cost of insurance services 04113 Insurance policy 04115 Insurance contract 04121 Quotes of the world's stock exchanges 04999 Other documents and information that the customs applicant can provide in support of the declared customs value 6. Documents confirming and (or) containing information about the country of origin 06011 The certificate of origin (form CT-1) 06013 The certificate of origin (form A) 06014 Non-preferential certificate of origin (general form) 06015 Advance ruling on the country of origin 06016 Declaration of origin 06017 The certificate of origin (form CT-2) 06018 The certificate of origin (form EAV) 06999 Other documents confirming the origin of goods 115 Classifier of documents types used for customs declaration (used in Viet Nam) Code Name INV Invoice BOL B/L (Bill of Lading) AWB AWB (Air Waybill) INS Details of insurance CON Contract ALL All application dossier ETC Other 116 Appendix F.
The description of web-services Table F1 Description of Web-services in WSDL-format <?xml version="1.0" encoding="utf-8"?> <wsdl:definitions xmlns:tns="http://tempuri.org/" xmlns:ls_1="urn:wco:datamodel:WCO:Declaration:1" xmlns:ls_2="urn:wco:datamodel:WCO:Declaration:2" xmlns:ls_3="urn:wco:datamodel:WCO:Declaration:3" xmlns:sgn="urn:EEC:signal:v1.0" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" name="EECVNCertificateService" targetNamespace="http://tempuri.org/"> <wsdl:types> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://tempuri.org/" xmlns:ls_1="urn:wco:datamodel:WCO:Declaration:1" xmlns:ls_2="urn:wco:datamodel:WCO:Declaration:2" xmlns:ls_3="urn:wco:datamodel:WCO:Declaration:3" xmlns:sgn="urn:EEC:signal:v1.0" elementFormDefault="qualified"> <xsd:import namespace="urn:wco:datamodel:WCO:Declaration:1" schemaLocation="Request.xsd"/> <xsd:import namespace="urn:wco:datamodel:WCO:Declaration:2" schemaLocation="Certificate.xsd"/> <xsd:import namespace="urn:wco:datamodel:WCO:Declaration:3" schemaLocation="Response.xsd"/> <xsd:import namespace="urn:EEC:signal:v1.0" schemaLocation="EECSoapSignal.xsd"/> <xsd:element name="sendCertificateDetails"> <xsd:complexType> <xsd:sequence> <xsd:element name="RootDocument" type="ls_2:RootDocumentType"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="sendRequestCertificateDetails"> <xsd:complexType> <xsd:sequence> <xsd:element name="RootDocument" type="ls_1:RootDocumentType"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="sendResultCertificateDetails"> <xsd:complexType> <xsd:sequence> <xsd:element name="RootDocument" type="ls_2:RootDocumentType"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="sendSignal"> <xsd:complexType> <xsd:sequence> 117 <xsd:element name="Signal" type="sgn:Signal"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="sendResult"> <xsd:complexType> <xsd:sequence> <xsd:element name="ls_3RootDocument" type="ls_3:RootDocumentType"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> </wsdl:types> <wsdl:message name="sendCertificateDetails"> <wsdl:part name="parameters" element="tns:sendCertificateDetails"/> </wsdl:message> <wsdl:message name="sendRequestCertificateDetails"> <wsdl:part name="parameters" element="tns:sendRequestCertificateDetails"/> </wsdl:message> <wsdl:message name="sendResultCertificateDetails"> <wsdl:part name="parameters" element="tns:sendResultCertificateDetails"/> </wsdl:message> <wsdl:message name="sendSignal"> <wsdl:part name="parameters" element="tns:sendSignal"/> </wsdl:message> <wsdl:message name="sendResult"> <wsdl:part name="parameters" element="tns:sendResult"/> </wsdl:message> <wsdl:portType name="EECVNCertificateService_PortType"> <wsdl:operation name="sendCertificateDetails"> <wsdl:documentation>”Providing information on the issued certificate of origin” service</wsdl:documentation> <wsdl:input name="sendCertificateDetails" message="tns:sendCertificateDetails" wsam:Action="http://tempuri.org/EECVNCertificateService/sendCertificateDetails"/> </wsdl:operation> <wsdl:operation name="sendRequestCertificateDetails"> <wsdl:documentation>”Receiving information about the certificate of origin” service</wsdl:documentation> <wsdl:input name="sendRequestCertificateDetails" message="tns:sendRequestCertificateDetails" wsam:Action="http://tempuri.org/EECVNCertificateService/sendRequestCertificateDetails"/> </wsdl:operation> <wsd
l:operation name="sendResultCertificateDetails"> <wsdl:documentation>”Receiving results of processing containing information on the certificate of origin” service</wsdl:documentation> <wsdl:input name="sendResultCertificateDetails" message="tns:sendResultCertificateDetails" wsam:Action="http://tempuri.org/EECVNCertificateService/sendResultCertificateDetails"/> </wsdl:operation> <wsdl:operation name="sendSignal"> <wsdl:documentation>”Receiving of signals on the current processing status” service</wsdl:documentation> 118 <wsdl:input name="sendSignal" message="tns:sendSignal" wsam:Action="http://tempuri.org/EECVNCertificateService/sendSignal"/> </wsdl:operation> <wsdl:operation name="sendResult"> <wsdl:documentation>”Receiving of the processing result” service</wsdl:documentation> <wsdl:input name="sendResult" message="tns:sendResult" wsam:Action="http://tempuri.org/EECVNCertificateService/sendResult"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="EECVNCertificateService_Binding" type="tns:EECVNCertificateService_PortType"> <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="sendCertificateDetails"> <soap12:operation soapActionRequired="false" style="document"/> <wsdl:input name="sendCertificateDetails"> <soap12:body use="literal"/> </wsdl:input> </wsdl:operation> <wsdl:operation name="sendRequestCertificateDetails"> <soap12:operation soapActionRequired="false" style="document"/> <wsdl:input name="sendRequestCertificateDetails"> <soap12:body use="literal"/> </wsdl:input> </wsdl:operation> <wsdl:operation name="sendResultCertificateDetails"> <soap12:operation soapActionRequired="false" style="document"/> <wsdl:input name="sendResultCertificateDetails"> <soap12:body use="literal"/> </wsdl:input> </wsdl:operation> <wsdl:operation name="sendSignal"> <soap12:operation soapActionRequired="false" style="document"/> <wsdl:input name="sendSignal"> <soap12:body use="literal"/> </wsdl:input> </wsdl:operation> <wsdl:operation name="sendResult"> <soap12:operation soapActionRequired="false" style="document"/> <wsdl:input name="sendResult"> <soap12:body use="literal"/> </wsdl:input> </wsdl:operation> </wsdl:binding> <wsdl:service name="EECVNCertificateService"> <wsdl:port name="EECVNCertificateService" binding="tns:EECVNCertificateService_Binding"> <soap12:address location="http://tempuri.org/EECVNCertificateService"/> </wsdl:port> </wsdl:service> </wsdl:definitions>