A. General Information

1. Title

GACC and Mongolia Customs Administration eManifest electronic data exchange

2. Status of the project
3. Implementation period of the project/service:
5. Geographical coverage
Participating countries: China, Mongolia
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
Customs Administrations
Other participating agencies/entities
b. Operational stage
Lead agencies/entities (op)
Customs Administrations
Other participating agencies/entities (op)
7. Main stakeholders/beneficiaries of the project
Traders (big enterprises)
Traders (SMEs)
8. Business process category of the project
Regulatory/official control

B. Lessons Learned

9. Summary description of the project/service
a. Objective(s)

a.    To facilitate Trade
b.    To secure the trade: minimize the illegal trade, 
c.    To better manage risks
d.    To enhance effective Customs controls
e.    To promote paperless trade
f.    To promote Tariffs collection – from China
g.    To promote effective revenue collection 
h.    To promote joint control 

b. Business need for the project (background)

To raise the efficiency of control mechanisms, strengthen risk management and facilitate the clearance and quick release of goods, the two Customs Administrations have negotiated and piloted the information exchange through the relevant cross-border dry ports and customs checkpoints.   
The legal bases for the information exchange are the Protocol to the Tripartiy Memorandum between the Customs General Administration of Mongolia and PRC GACC. 

c. Business process covered*

Customs Declaration for Import/Export
Risk Management in both Customs Administrations
Data verification and reconciling between the two administrations for the declared imports and exports 

d. Overall architecture and functionalities*

C2C electronic data exchange through APIs

-    Before starting data exchange, exchange encryption key between two countries, and each country register registers this key to their system
-    Application generates XML instance of cargo manifest
-    Then, request MQ to send this message to the China Customs system by API
-    MQ encrypts this message and envelops with the MQ environment
-    Then, MQ sends this encrypted message to the China Customs MQ system
-    If failed, Mongolian Customs MQ retry to send it to the China Customs MQ system
-    Else, the China Customs MQ system sends an Acknowledgement to the Mongolian Customs MQ system

e. Relevant document/figure
10. Documents and data exchanged via the project

Joint Cargo Manifest
-    China: Combine from conveyance (transport means report), consignment (Cargo manifest) + 
         declaration from customs broker or exporter
-    Mongolia: Combine from consignment (Cargo manifest) + declaration

11. Data models/databases, proprietary solutions, hybrid approaches

WCO DM 3.0 was used as a reference data model.

-    Mongolian Customs has used an international code list based on WCO CDM 2.0 and added their own code

12. Main challenges faced during the project

Overall, challenges were related to the harmonization of data to be exchanged, code lists to be used, and Data Models to adopt. Because Mongolian Customs code lists were not following the WCO DM 3.0, there were some difficulties in harmonizing the data elements. The problem was settled by harmonizing the code lists when sending the messages.

13. Lessons learned from the project
14. Main benefit(s) of the project
Enhanced regulatory compliance*
Transaction Cost savings*
Transaction Time savings
Simplified process
14A. Elaborations/detailed description on benefits gained
15. Technical/financial/capacity building/other assistance
16. Future plan for expansion of the project
17. Other information or relevant references on the project
18. Relevant document regarding the project

C. Relevant Standards

20. Electronic message standard
20A. Electronic message standard supporting the project
- Other XML format: N/A
- Other XML format: N/A
- Other XML format: N/A
20B. Type of standard for electronic message applied for the project
International standard
Technical recommendations from international body(ies)
21. Technical communication standard
21A. Technical communication standard supporting the project
21B. Type of technical communication standard applied for the project
International standard
Technical recommendations from international body(ies)
22. Security-related standards*
22A. Security-related standard supporting the project
VPN (Virtual Private Network)
22B. Type of security-related standard applied for the project
International standard
Industry-specific standard
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
23B. Other technical implementation information
Message Level
- XML Digital Signature, encryption/decryption, PKI, hash-value, etc.
- Cross verification of digital signature based on X.509 PKI