A. General Information

1. Title

Smart Border

2. Status of the project/service
3. Implementation period of the project/service:
5. Geographical coverage
Bilateral: France and the UK
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
French Customs
Other participating agencies/entities
b. Operational stage
Lead agencies/entities (op)
French Customs
Other participating agencies/entities (op)
7. Main stakeholders/beneficiaries of the project/services
Traders (big enterprises)
Traders (SMEs)
Customs brokers
8. Business process category of the project/service
Regulatory/official control

B. Lessons Learned

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

French Customs developed an IT solution known as the “smart border” to keep trade flowing between the UK and France, despite of the reestablishment of customs clearance at the border.It works as an interface between the maritime companies’ systems and the existing customs clearance systems (Delta G, Delta T and ICS) and the existing sanitary IT system (TRACES).

For each crossing point affected by Brexit, the ferry companies, the ports and the Channel Tunnel have worked together to adapt infrastructure and get local operators involved in preparing for the start of the smart border. Smart border is based on the following principles;

Advanced completion of customs declarations prior to arrival at the border point

Identification of trucks by linking their number plates to customs declarations prior to Channel crossing

Automation of data flows

The goal of smart border is as following:

Enable all stakeholders to meet their legal obligations while respecting the regulatory framework

Maintain fluidity by avoiding prolonged stops on site that could lead to infrastructures congestion

Facilitate the exchange of information between stakeholders: hauliers, maritime companies, infrastructure, customs.

The core point is that the economic operator, customs declarant, the shipper, the hauler must be synchronized before the shipment of goods. 

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

To develop a system to facilitate border crossing between UK and France after Brexit.

c. Business process covered*

Import flow from UK to France:

Anticipation of customs and sanitary formalities prior to the pairing, UK side

- Clearance and transit procedures

- Safety/security procedures

The pairing, UK side

The crossing

The disembarkation

Processing of lorries/unaccompanied trailers directed into the “Orange” parking

Export flow from France to UK

Anticipation of customs formalities prior to the pairing, EU side

The pairing, French side

Processing lorries/unaccompanied trailers whose status indicates an incomplete customs procedure or that a customs inspection must be conducted

The boarding for the UK

Access to IT systems

If transit with France is used as country of departure or destination, Delta T convention is to be prepared with the French customs, to access to this application.

to submit the ENS for goods entering the EU customs territory in France, the French ICS must be used

for goods that will be cleared at the entry into France, all the necessary actions must be taken to access to Delta G

All operators crossing the Channel border between UK and FR must use SI Brexit.

For more detail refer to the link:

d. Overall architecture and functionalities*

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

Data for customs border crossing

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
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 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