EU to Great Britain: Entry Summary Declarations are now business-as-usual.
For years, imports from the EU into Great Britain benefited from a temporary waiver on Safety & Security filings. That grace period has ended.
Since 31 January 2025, every EU-to-GB import movement must be covered by a Safety and Security declaration also known as an Entry Summary Declaration (ENS).
This is not a “nice-to-have” administrative step. It is a border-safety requirement that sits alongside (not instead of) your customs and SPS processes. If your organisation still treats ENS as a future change, you are already exposed.
What changed and what this means in practice
- To ease implementation, HMRC introduced a reduced dataset for EU imports: 20 mandatory fields, 8 conditional fields, and 9 optional fields.
- That reduction helps—but it does not remove the hard part: getting the right data, from the right party, early enough to submit pre-arrival.
In most supply chains, the friction point is not capability; it is accountability and data ownership. Who is on the hook?
HMRC is clear: carriers/hauliers are legally responsible for ensuring Safety & Security declarations are submitted, even if another party (importer, intermediary, broker) lodges the declaration on their behalf. Translated into leadership terms: if responsibilities are unclear in your contracts and operating model, you will see:
- Last-minute data chases.
- Loading cut-off failures.
- Avoidable delays and compliance escalation.
- Reputational damage with key customers and logistics partners.
Submission isn’t “a portal click”
ENS is lodged into Safety and Security Great Britain (S&S GB). Importantly, S&S GB does not have a user interface, so you either:
- build compatible capability in-house
- buy compatible software,
- use a Community System Provider, or
- appoint an agent/intermediary.
If you submit yourself, you will also need a Government Gateway account and a GB EORI number. A practical leadership checklist (what I’d ask my team this week)
- Confirm scope: Which EU lanes, modes, and service types (parcel, groupage, RoRo, unaccompanied, etc.) do we run into GB?
- Assign accountability: For each lane, who ensures the ENS is filed and what is the back-up plan if the primary party fails?
- Lock the data model: Do we reliably hold (and can we share) the essentials—routing, transport IDs, goods descriptions, consignor/consignee, packaging counts, and the GB port location code? 4. Choose the filing route: Software, CSP, or agent then test end-to-end with real movements, not mock examples.
- Embed cut-offs in operations: ENS is a pre-arrival discipline; treat it like a departure-critical milestone (not a post-shipment admin task).
- Governance and KPIs: Track “ENS right-first time” and exception rates by lane and provider. What gets measured gets fixed.
Bottom line
The EU-to-GB ENS requirement is not a rumour and not a 2026 change. It has been live since 31 January 2025.
Organisations that treat it as “just another customs step” will keep paying an operational tax in the form of disruption and firefighting. Those that treat it as a data, accountability, and partner-management programme will protect service levels and maintain credibility at the border.
If you want one simple starting point: bring your logistics partners, customs support, and internal ops into one room and agree lane by lane, who files, with what data, by what time, using which system.
