A. General Information

1. Title

SASEC Customs-to-Customs data exchange

2. Status of the project/service
MOU to exchange pre-arrival cargo data signed in July 2021. (To be operationalized)
3. Implementation period of the project/service:
To be implemented
4. Website
5. Geographical coverage
Bilateral: India and Maldives
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
Customs of SASEC member countries
Other participating agencies/entities
b. Operational stage
Lead agencies/entities (op)
The operation has not started yet.
Other participating agencies/entities (op)
7. Main stakeholders/beneficiaries of the project/services
Traders (big enterprises)
Traders (SMEs)
8. Business process category of the project/service
Regulatory/official control

B. Lessons Learned

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

Promote C2C SASEC regional data exchange 

b. Business need for the project/service (background)

The 3rd SASEC Customs Sub-group meeting held in Goa on 12 March 2015 endorsed the Terms of Reference for conduct of a Feasibility Study on the Electronic Exchange of Data among Customs Administrations in the SASEC region and to recommend a viable model to exchange data electronically. The exchange of data between Customs administrations has been a feature of global cooperation in the enforcement field for many years. 

c. Business process covered*

Focus is on the electronic data exchange between Customs administrations. 

d. Overall architecture and functionalities*


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


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


12. Main challenges faced during the project/service
13. Lessons learned from the project/service
14. Main benefit(s) of the project/service
14A. Elaborations/detailed description on benefits gained:
15. Technical/financial/capacity building/other assistance
16. Future plan for expansion of the project and service
17. Other information or relevant references on the project and service
18. Relevant document regarding the project/service

C. Relevant Standards

20. Electronic message standard
20A. Electronic message standard supporting the project/service:
20B. Type of standard for electronic message applied for the project/service
21. Technical communication standard
21A. Technical communication standard supporting the project/service
21B. Type of technical communication standard applied for the project/service
22. Security-related standards*
22A. Security-related standard supporting the project/service
22B. Type of security-related standard applied for the project/service
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
23B. Other technical implementation information