A. General Information
1. Title
Mercosur Blockchain for AEO data exchange
2. Status of the project/service
3. Implementation period of the project/service:
5. Geographical coverage
Brazil, Argentina,Paraguay,Uruguay
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
Serpro (for Brazilian Internal Revenue Service)
Other participating agencies/entities
--
b. Operational stage
Lead agencies/entities (op)
Serpro (for Brazilian Internal Revenue Service)
Other participating agencies/entities (op)
--
7. Main stakeholders/beneficiaries of the project/services
Traders (big enterprises)
Traders (SMEs)
Customs brokers
Customs
8. Business process category of the project/service
Regulatory/official control
B. Lessons Learned
9. Summary description of the project/service
a. Objective(s)
bConnect platform begins to be used by Brazil, Argentina, Paraguay and Uruguay to ensure more agility and security in the exchange of information on foreign trade. bConnect is a tool that allows the network sharing of registration information of companies certified by the Federal Revenue Service as an Authorized Economic Operator (OAS) and that enjoy benefits such as facilitation of customs procedures, both in Brazil and abroad.
bConnect was created to supply an international need of automated exchange of customs data of the OAS between the countries, that, before, was made, in its majority, by means of spreadsheets elaborated or extracted from the system that each country had and sent by electronic mail
The bConnect network begins by allowing the sharing of information from Authorized Economic Operators (AEO) and there are already plans to increase the network to meet the sharing of information from Customs Declarations.
the bConnect solution was developed using the Hyperledger Fabric 1.4 framework, an open source application maintained by The Linux Foundation.
b. Business need for the project/service (background)
--
c. Business process covered*
Data flows through an encrypted tunneling channel, between countries and according to the respective agreement.
d. Overall architecture and functionalities*
https://www.douane.gouv.fr/sites/default/files/2021-02/26/Preparing-for-brexit-French-customs-guidelines.pdf
e. Relevant document/figure
--
10. Documents and data exchanged via the project/service
AEO data exchange
Customs declarations
11. Data models/databases, proprietary solutions, hybrid approaches
--
12. Main challenges faced during the project/service
Blockchains interoperability
13. Lessons learned from the project/service
--
14. Main benefit(s) of the project/service
Enhanced regulatory compliance*
Transaction Cost savings*
Transaction Time savings
Simplified process
14A. Elaborations/detailed description on benefits gained:
Blockchain platform is very suitable for sharing logistic events and documents among all parties in supply chains
Facilitation of customs procedures
Data protection and consistency
15. Technical/financial/capacity building/other assistance
--
16. Future plan for expansion of the project and service
Expand to different countries, more regions
17. Other information or relevant references on the project and service
//https_latam.portalerp.com/?url=https%3A%2F%2Flatam.portalerp.com%2Flas-aduanas-del-mercosur-estan-conectadas-por-blockchain
https://www.ibm.com/topics/hyperledger
18. Relevant document regarding the project/service
--
C. Relevant Standards
19. Name(s) of any international, national legal instrument underpinning the project/service
Bilateral agreement between Uruguay and Brazil
Bilateral agreement between Uruguay and Argentina
20. Electronic message standard
20A. Electronic message standard supporting the project/service:
bConnect solution was developed using the Hyperledger Fabric framework,an open source application maintained by Linux Foundation:
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
--
