You’ve got a GB EORI number. You discovered that you’ll also need an EU EORI number if you sell or hold goods in Europe. Now you’ll need to apply for a third XI EORI number if you sell to or from Northern Ireland.
Thanks go to our friends at GFS who tipped us off on the post Brexit requirement XI EORI for Goods moving between Great Britain and Northern Ireland. As well as keeping Tamebay readers up to date with all the key changes and breaking news on everything shipping related in Q4, we are also holding a webinar in January to review what’s happened and offer advice to cover anything, like applying for an XI EORI, that you might have missed. Register for our Peak, Brexit and COVID – What on earth happened? webinar now to get a reminder nearer the time.
If you’ve been ignoring Brexit because you only sell within the UK then this will also impact you as the first time a customer based in Northern Ireland purchases from you your carrier will need your XI EORI number. While the ‘Whole of the UK’ has left the EU with the transition agreement expiring on the 31st of December 2020, a new Northern Ireland Protocol comes into force the next day on the 1st of January 2021 meaning that Northern Ireland will be treated somewhat differently from the rest of the UK.
As an example, if you are sending a shipment from Great Britain to Belfast in Northern Ireland you will quote your XI EORI number. And for shipments from Great Britain to Dublin in Southern Ireland you will quote your GB EORI number. N.B. you do not need to quote both EORI numbers for Northern Ireland – only the XI EORI number.
If you do not quote the correct EORI number when shipping to Northern Ireland then the likelihood is that the goods will not be shipped by the carrier.
Sign up on Gov.uk here to to make sure your business gets an XI EORI number that you’ll need to move goods to Northern Ireland from the 1st of January 2021.
The post XI EORI requirement for Northern Ireland trade post Brexit appeared first on Tamebay.
from Ecommerce – Tamebay https://ift.tt/2UW4Zow via IFTTT
No comments:
Post a Comment