Every EORI number checked Recorded against your relations Correct in every declaration

Custom EORI DMS integration

Anyone doing business with Customs needs an EORI number, and a customs declaration quickly ends up containing the EORI numbers of several parties: declarant, represented party, consignor or consignee. A wrong or expired number holds up a declaration. Appfront builds the integration that manages EORI numbers in your own systems: checking them against the European Commission's EORI database, recording them against the right relation and passing them on correctly to the declarations you submit in DMS.

What is an EORI-DMS integration?

An EORI-DMS integration makes sure the EORI number of every party in your systems is correct before it ends up in a customs declaration. EORI stands for Economic Operators Registration and Identification. According to Dutch Customs, it is a mandatory European identification number for businesses dealing with Customs, needed for import and export outside the EU, for submitting declarations and for applying for a licence. The European Union keeps all EORI numbers centrally in a single database. A company established in the Netherlands or outside the EU applies for the number free of charge at the Nationale Helpdesk Douane (Dutch Customs helpdesk); a company in another member state does so in that member state. Branches use the number of the head office.

A company established in the Netherlands that submits its own declarations may also compose its own EORI number: NL followed by the RSIN, padded with leading zeros to nine digits. The number is then registered at the first declaration or licence application. This is not possible for sole traders: since 2022 they receive a customs number, and the old number based on the BSN (citizen service number) is no longer valid. Anyone who gets a new VAT number, for example when changing from sole trader to private limited company, also applies for a new EORI number. You can check whether a number is valid in the European Commission's EORI database, by number only and not by name. Name and address are only visible there if the company has given permission for publication.

We build this custom because EORI numbers live in many places at once: in your customer records, in orders and shipments, at freight forwarders and in the declaration itself. In a declaration they are mandatory for, among others, the declarant, the represented party and the consignor or exporter, unless it concerns a private individual. The integration checks numbers via the European Commission's validation service, which returns a status per number, records the result with the date against the customer record, and prepares the correct number for each role for the declaration in DMS, the Customs Declarations Management System that replaced AGS in 2024. A number that is not valid goes onto a list with the reason, instead of into the declaration.

Checked

Status from the EU database.

Per customer

Number recorded with date.

In the declaration

Correct number per role.

How we build your EORI-DMS integration

We start with your declaration process: which parties appear in your declarations, where their EORI numbers are currently stored, who prepares the declaration and in which system. We then read in your customer records and check all existing numbers against the EORI database, so it becomes clear which are missing, invalid or belong to an old legal form. We build the checking and recording at customer level first, and let you review the outcome. Passing numbers on to declarations and rechecking them when details change follow once that works well. After that, we maintain the integration whenever Customs or the European Commission changes anything in messages or services.

1
Mapping the process

Parties, roles, systems.

2
Check your records

All numbers checked against the EU.

3
Document

Status per customer.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when things change.

What an EORI-DMS integration actually does

The components below feature in almost every EORI integration. Which ones you need depends on the number of customers and on how you submit declarations.

Validation

Via the Commission's service.

Bodybuilding

Country code and RSIN verified.

Contacts

Number and date per party.

Rolls

Declarant, consignor, consignee.

Alerts

New VAT number detected.

Log

Every check can be traced.

Who we build an EORI-DMS integration for

The integration is intended for organisations that regularly submit or prepare declarations and work with many different parties in doing so. The more customers and the more declarations, the more it delivers.

Importers

Suppliers outside the EU.

Exporters

Customers per country.

Customs agents

Clients' numbers.

Software builders

Checks within your software.

Technology and integrations

This page is about the EORI number itself: requesting, checking, recording and passing it on. For customs procedures, authorisations and registration in your records, see our page on software for customs procedures and registration. If you are AEO or want to become AEO, take a look at the AEO control measures file; for the file per shipment there is the forwarding file, and for electronic freight information the eFTI integration. You can read about our approach at building software.

EORI validation service SOAP web service DMS National Customs Helpdesk RSIN and VAT number ERP and customer management Roles in the declaration Format check Roles and permissions Audit log

Why Appfront for your EORI-DMS integration?

An EORI number retyped in a customer record, a number belonging to a sole proprietorship that has since become a limited company, or a declaration sent back because the consignee's number does not exist: all of these cost time and cause delays at the border. That is what we build around: numbers checked in advance, a fixed place for each customer and an audit log where you can see when each number was checked.

Accurate

Checked before the declaration.

Up to date

Rechecked when details change.

Traceable

Date and status recorded.

Security and privacy in an EORI-DMS integration

The integration processes data about your business relations: EORI numbers, company names and addresses. For sole traders this is personal data, so the GDPR applies. The integration sends only the number to the validation service, stores the result against the right relation, and logs every check with its time and outcome. It only takes over the name and address from the database if the company has consented to publication.

The integration runs in a European data centre, with encrypted connections and storage. Login credentials and certificates for the declaration systems are kept secure and are not visible to staff. We agree with you in advance who may change numbers and who may approve a discrepancy, so every change can be traced back to a person.

Frequently asked questions about an EORI-DMS integration

Questions that importers, exporters and customs brokers ask before they get started.

The Economic Operators Registration and Identification number, a mandatory European identification number for businesses that deal with Customs. You need it for imports and exports outside the EU, when submitting declarations and when applying for a customs authorisation.

If your company is established in the Netherlands or outside the EU, you apply for it free of charge via the Dutch National Customs Helpdesk (Nationale Helpdesk Douane). If your company is established in another member state, you apply there. A company established in the Netherlands that submits its own declarations may also compile the number itself based on its RSIN (the Dutch legal entities and partnerships identification number).

You put NL in front of your RSIN and pad it with leading zeros to nine digits, so RSIN 1234567 becomes NL001234567. This is only allowed if you submit your own declarations in the Netherlands, and not if you are a sole trader. The number is registered with your first declaration or authorisation application.

In the European Commission's EORI database. You search there by number, not by name. You only see the company's name and address if it has given consent for publication. For checks from software, the Commission also offers a web service that returns a status per number.

According to Customs, among other things when you receive a new VAT number, for example because your sole proprietorship becomes a private limited company (bv). Sole traders with an old number based on their BSN (citizen service number) only use the new number from the letter from Customs.

Software for customs procedures handles authorisations, conditions and registration in your records. An EORI-DMS integration is one part of that: making sure the EORI numbers of all parties are correct and end up in the right place in the declaration. That integration can be built into an existing system.

For organisations with many relations outside the EU, for customs brokers who submit declarations for many clients, and for software suppliers who prepare declarations. If you work with a handful of regular parties, occasionally checking the EORI database is enough.

Checking EORI numbers before the declaration?

Tell us where your relations' EORI numbers are currently stored and how your declarations come about. We will show you how an integration makes that reliable.

Edit content