AGS is gone Documents via DMS since May 2026 The data set has been expanded

Custom software for customs declarations in DMS

Anyone still talking about AGS is talking about a system that no longer exists. Declarations are now made in DMS, and that is not just a new screen but a different data set, different messaging and a different process after submission. Since May 2026, the documents accompanying a declaration must also be submitted directly via DMS rather than by email.

What has changed and what it means

The AanGifteSysteem (AGS, the Dutch declaration system) has been replaced by the Douane Aangifte Management Systeem (DMS, the Customs Declaration Management System), because European customs legislation prescribes different data and different processes. Since 1 July 2024, declarations can no longer be made in AGS; companies that had registered in time were given a short transition period afterwards. DMS is being introduced in phases for import, storage and export declarations.

The difference is not in the buttons. The data set is more extensive and stricter, the messaging is structured differently, and what happens after submission has changed: different statuses, different feedback and a different way for Customs to communicate with you.

In 2026, something has been added that many companies underestimate. Since mid-May, documents accompanying a declaration must be submitted directly via DMS and no longer by email. That sounds like a change of channel, but it affects your process: someone who used to forward a scan now has to be in a system and attach the right document to the right declaration.

If you work under a simplified procedure, the sharpest issue is not the message but your own records: the entry in them is the declaration. What that requires of your system is covered under software for customs procedures and entry in the records.

How we build this

The declaration, with its documents and authorisations, is the unit here. If it is right up front, the handling afterwards is simply a matter of tracking statuses.

1
Establishing where the data comes from

Item data, commodity codes, value, origin and authorisations come from different systems. What is missing is almost always the same handful of fields.

2
Checks before submission

Every check Customs carries out, you can carry out earlier. A rejected declaration costs you a turnaround time; a rejected field on your own screen costs a second.

3
Attaching documents to the declaration

Not as an email attachment but as part of the declaration, with the right type and the right number. Since May 2026, that is the only route.

4
Following up statuses after submission

What comes back from DMS determines whether a shipment goes ahead. That feedback belongs with the shipment, not in a separate screen.

What the software actually does

The declaration and its supporting evidence carry everything. Which components you need depends on your types of declaration and your authorisations.

Data set checks before submission

Missing or illogical fields are flagged before the declaration goes out. The data set in DMS is more extensive than that of AGS, and that is where most rejections come from.

Documents linked to the declaration

Invoices, authorisations, certificates and statements attached to the right declaration, with type and number. Since May 2026, these go via DMS and no longer by email.

Authorisations monitored

Authorisation numbers belong in the declaration, and authorisations expire. Otherwise you only discover an expired authorisation when a shipment is held up.

Statuses and feedback per shipment

What DMS reports back appears with the shipment it relates to. That way your logistics team can see what is going on without having to open a separate customs environment.

Rejections with follow-up

A rejected declaration becomes an action with an owner and a reason, because a list of errors without an owner only grows.

Integration with your own systems

Item, order and shipment data sit in your ERP or TMS. We build the layer in between using integrations, rather than letting a second set of records emerge.

Who we build for

Your role determines which part carries the most weight. Four situations.

Freight forwarders and customs agents

You file declarations for others and carry the risk of their data. Checking before submission is worth the most here, because a rejection affects your turnaround time and not the client's. The paperwork that accompanies the freight is captured with the customs app.

Import and distribution

High volumes of the same items. The gains lie in master data that is correct, because an error in a commodity code is repeated with every shipment.

Manufacturing with special procedures

Inward processing, storage or customs transit come with authorisations that must be reflected in the declaration. That is exactly where manual work goes wrong. If you also import goods subject to CBAM, a second declaration is added on top.

E-commerce with small shipments

Large numbers of low-value shipments and plenty of returns. The challenge is not the complexity of each declaration but the volume, and therefore how far it can be automated. The VAT side runs through VAT compliance software.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

DMS is being rolled out in phases and the specifications are still being added to. Everything to do with message definitions and data fields should be configurable and stored per version.

Node.js / Python / .NET PostgreSQL Declaration register with complete data set Validation before submission Documents linked to the declaration Authorisation management with expiry dates Status handling after submission Exception management with an owner Integration with ERP, TMS or WMS Message definitions configurable per version Retention of submitted messages Reporting for post-clearance audits Audit logging Hosting in the EU

Why Appfront

AGS no longer exists

Anyone still building an AGS integration is building on something that has been switched off. We build on DMS and keep the definitions configurable, because the rollout is not yet complete everywhere.

Corrections cost turnaround time

A rejected declaration holds up a shipment. We move the check to the moment of creation, because that is where it costs nothing.

Documents have gone through DMS since May 2026

What used to be an email is now part of the declaration. We build it as an action within the process rather than as a separate step alongside it.

Your ERP stays in place

We build the layer in between using integrations. A second item register for customs is guaranteed to drift out of sync.

Security and privacy

Customs data is commercially sensitive: suppliers, values, origin and volumes together paint a picture of your purchasing that you do not want to share widely. If you file declarations for third parties, you also process your clients' data, and they should not be able to see each other's shipments. We therefore set access per role and per client, and log every time data is viewed.

On the retention side, something applies that weighs more heavily in customs than elsewhere. Customs can audit after the fact, and the question is then what you declared at the time and on the basis of which documents. We therefore retain the submitted message exactly as it went out, with the associated documents and the authorisations that applied at the time, and not just the current state of the shipment. A system that only knows the latest version cannot explain, in a post-clearance audit, why something was declared differently back then. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.

Frequently asked questions about AGS and DMS

No. Since 1 July 2024, declarations can no longer be made in AGS and must be submitted in DMS. Companies that had registered in time for the informal phase had a short transition period afterwards, with agreements made in advance. In practice, this means an AGS integration no longer needs to be maintained.

The data set is more extensive and stricter than in AGS, the messaging is structured differently, and the processes after submission have changed, including the way Customs gives feedback. That is why a ready-made translation of your old AGS messages rarely works.

Since mid-May 2026, declarants must submit documents for a customs declaration directly through DMS instead of by email. This mainly affects the workflow: someone who used to forward a scan now has to attach the right document, of the right type, to the right declaration.

Authorisation numbers must appear in the declaration, and authorisations have a period of validity. In practice, things go wrong with an expired authorisation or a number that was not updated after a change. Monitoring this is a small component with a big impact.

Usually not. Most companies use a software package or work through their freight forwarder for the submission itself. What we build is the layer before that: getting the data complete and correct, linking documents and attaching feedback to the shipment. That is where things go wrong at volume.

The rollout happens in phases and differs per declaration type: import, storage and export do not follow the same pace. What applies to you depends on your declaration types and on the agreements with Customs. Check this with Customs itself, as the timeline has been adjusted several times.

Almost always, and that is the intention. Item data, commodity codes and values are already there; what is usually missing are a few customs fields per item. Adding those to your own master data is cheaper than retyping them for every shipment.

That depends on the number of declaration types, whether documents and authorisations need to be included, and which software package is being integrated. The validation layer on your existing data is usually quick to put to use and immediately shows how many fields are missing. We provide a well-founded estimate after the discovery phase.

Declarations getting stuck?

Take last month's rejections and look at which field they fail on. Usually it is a handful of fields that keep recurring. We build this as a standalone application and as part of a broader custom software project.

Edit content