ENSconnect
Brexit border declarations for every trip between the EU and the UK

Upload the trip's documents. Press one button. Customs done.

The problem

Every trip across the Channel needs three declarations

Since Brexit, every trip between the EU and the UK needs three border declarations on top of its customs declarations. ENSconnect does exactly these three, and nothing else.

A stack of documents retyped into three separate portals
ENS

Safety and security declaration

Into the UK it goes to HMRC, into the EU it goes to ICS2. One per consignment.

GMR

Goods Movement Reference

For the UK border. One per trip, bundling all its declarations.

ELO

The French border envelope

The barcode the driver shows at the port. One per trip.

Today an operator reads the loading order, the customs declarations and the CMR, then types the same data into two or three portals. The more goods lines a truck carries, the longer it takes. A typo means a truck stopped at the border.

What ENSconnect does

The Brexit border declarations: ENS, GMR and ELO

The safety and security declaration, the Goods Movement Reference and the French border envelope, built from your documents and filed directly with HMRC, ICS2 and French customs.

What ENSconnect does not do

Import and export declarations

CDS, ABD, DAU, EAD and the other customs declarations stay with your customs broker, as today. ENSconnect reads them and builds the border declarations from them. It replaces the retyping, not your broker.

How it works

Three steps, one screen per trip

1

Upload

Drop everything you have for the trip: loading order, customs declarations, CMR, invoices, even phone photos. ENSconnect reads each document. Nothing to type.

Documents flying into the ENSconnect upload panel
2

Review and press Submit

The trip is built for you: parties, goods, truck and route, turned into the declarations the trip needs. One ENS per customs declaration, one GMR and one ELO per trip; groupage splits itself, one declaration per exporter and importer pair. Green is confirmed by the documents, amber needs a glance. Mistakes are caught before customs sees them.

The ENSconnect page with ENS, GMR and ELO ready and the Submit button
3

Filed with customs

ENS and GMR go to HMRC, ENS into the EU goes to ICS2, the ELO goes to French customs. The MRN, the GMR reference and the driver's barcode come back on the same screen.

ENS and GMR sent to HMRC, ENS to ICS2, ELO to France
Under the hood

An AI pipeline that reads, maps, builds and checks

Every trip goes through the same four stages. Nothing is retyped from the documents, and nothing leaves with a known error.

A CDS import declaration being read, each line picked up by the reader
1 · Read

Every document, any format

Loading order, customs declarations, CMR, invoices, scans and phone photos. Each document type has its own reader, so a new broker layout never breaks the others.

Each field of the declaration linked to the document and box it was read from
2 · Map

Fields to the customs data model

Parties, EORIs, goods lines, weights, plates and route are matched across documents, deduplicated and mapped to the fields HMRC, ICS2 and SI Brexit expect.

The ENS, GMR and ELO of the trip built and ready to submit
3 · Build

Declarations by the book

One ENS per customs declaration, one GMR and one ELO per trip, built to the HMRC Safety and Security guide, the ICS2 specification and the SI Brexit ELO rules.

A UK Trader town corrected by the guard and every field checked against the documents
4 · Guard

Checked before it leaves

Every declaration is verified against your own documents and the customs rules. Missing EORIs, wrong countries, inconsistent weights and references are caught and corrected before anything is sent.

It fills the form. Your operator still signs it.

The platform will not guess. Anything it could not read with confidence is flagged amber against the source document, in plain words. A missing ferry crossing or a carrier EORI that is in nobody's paperwork is asked for, never invented.

The guard is the difference between a truck that crosses and a truck that waits. Checks run before anything is sent: MRN check digits, EORI format and registry name, weights against the declared totals, commodity codes against the goods described. When the border still says no, the rejection comes back as a sentence attached to the field that caused it, with the fix offered where it is already known, as with a misread character in an MRN off a phone photo.

Coverage

What it reads, what it files

What it reads today

UKCDS import and export declarations, entry documents, S&S reports
DEABD Ausfuhrbegleitdokument, loading orders
FRDAU and Delta barcode sheets
ITEXA / DAE export declarations
BE · NLEDMS and Dutch export declarations
HUAES export declarations
EUNCTS / T1 transit, ATA carnets
AnyLoading orders, CMRs, invoices, and phone photos of all of them

What it files, and where

Into UKENS to HMRC, one per consignment
Out of UKENS to ICS2, the EU entry system
BothGMR to GVMS, bundling every declaration on the trip
FRELO for the French border, with the driver's envelope
AfterAmendments and cancellations, up to check-in; then the movement is followed: accepted, paired, checked in, embarked
AlwaysEvery filing, edit and customs answer is kept: who did what, when, and what the border replied
Where it files

Direct to customs, no portal in between

ENSconnect talks to the customs systems themselves. The references come back the moment customs answers.

ENS, GMR and ELO accepted by HMRC and French customs, each with its reference
HMRC
ENSGMR

Safety and Security GB for ENS into the UK, GVMS for the GMR in both directions.

ICS2
ENS

Import Control System 2 for ENS into the EU, through a certified access point.

French customs
ELO

SI Brexit: the envelope that pairs the vehicle with its declarations at the French ports.

Time

Under a minute to issue the three declarations

< 1 minto issue ENS, GMR and ELO for a trip

One button. The MRN, the GMR reference and the ELO barcode come back on the same screen.

0:00

Drags the trip's PDFs onto the page

0:26

Reads the declarations the platform built, beside the documents they came from

0:40

One click. ENS and ELO go to customs

then

The GMR follows by itself the moment the MRN lands, bundling every declaration on the trip

MRN26GB00AB1CD2EF3GH4
GMRGMRA000X0X0X
ELON0000000000

What lands on the trip (example values). Every value on the screen carries its source: the document and the page it was read from.

Who it is for

Built for the people who move the trucks

Whoever is responsible for the border declarations of a trip, ENSconnect takes the retyping off their desk.

A curtain-side lorry with three accepted declarations above the trailer

Freight forwarders

Your dispatchers file from the loading order they already have. No customs software to learn.

Hauliers

GMR and ELO for every trip, with the driver's barcode ready before departure.

Customs brokers

Groupage trips with dozens of declarations composed automatically, one ENS per declaration.

Each company sees only its own trips and documents. Every action and every customs answer is kept in an audit trail. Proven daily on a real fleet between Germany and the UK.
Book a demo

A live demo, on your own documents

Send us the documents of a trip you handled last week. We upload them in front of you and file the declarations to the customs test systems, live, in under ten minutes.

An envelope with three accepted declarations sliding out of it