Custom software for customs procedures and entry records
With an authorisation for entry in the declarant's records, the customs debt arises the moment you enter something in your own system. Not when you send a message, but at entry. That makes your records not a preparation for the declaration but the declaration itself, with all the requirements that come with it.
What the authorisation requires of your system
The authorisation is only granted for special procedures: customs warehousing, temporary admission, end-use, inward processing and outward processing. And only to those who already hold an authorisation for that procedure themselves. So there are always two authorisations stacked on top of each other, and the conditions of both apply at the same time. That is the first place where systems fall short: they know the declaration but not the authorisation.
Entry in the records is the legal moment. From that point the deadline for the supplementary declaration starts running, and it must be submitted no later than the tenth day after entry. In the Netherlands the period is one calendar day, and the supplementary declarations for that period are all sent at once. A consignment entered on the wrong day therefore ends up in the wrong batch, and you only notice once the message has already been sent.
The requirement for the records themselves is explicit: they must be set up so that data is recorded accurately, on time and in full. In practice that means three things that are rarely all in place. The time of entry must be fixed and must not shift afterwards. What has been entered must be complete at that very moment. And the authorisation conditions must be checked before anything goes in, not afterwards.
The entry itself takes place on the warehouse floor, at receipt or dispatch, and that is where the time must be fixed. See the app for entry at receipt and dispatch.
How we build this
Entry in the records is the pivotal point. Everything before it is checking, and everything after it is accountability.
Each authorisation with its number, validity, types of goods and conditions. As long as these sit in a PDF, nothing can be checked against them.
Does this type of goods fall under the authorisation, is the procedure permitted, is the deadline still valid. Once entered, an error is a correction with a notification, not an adjustment.
All entries for a day belong in a single supplementary declaration. The system closes the period and shows what is in it before it is sent.
The clock starts at entry, not when the supplementary declaration is drawn up. That is precisely the difference that goes wrong in calendars.
What the software actually does
The authorisation register with the entry in the records carries everything. What else you need depends on which procedures you operate.
Authorisations with their conditions
Number, validity, permitted goods and the special conditions, as data rather than as an attachment. That is what must be checked before anything is entered.
Checking up front instead of correcting afterwards
The system checks the type of goods, the procedure and the validity before entry. After that moment, an error is a correction with everything that comes with it.
The deadline from entry
The clock runs from the moment of entry. The system monitors that deadline per period, so nobody needs a calendar for it.
Closing the period and submitting the supplementary declaration
All entries for a day brought together in a single supplementary declaration, with a check on what is in it before it is sent.
Warehouse stock with the procedure attached
In a customs warehouse or under processing, every batch has a procedure and a deadline attached. Stock without that information is not a stock record as far as customs is concerned.
Connecting to your own systems
Receipt, stock and dispatch come from your existing systems through integrations. A second entry creates a second version of the truth, and here that truth is the declaration.
Who we build for
The procedure determines where it hurts. Four situations.
Customs warehousing and storage
Many movements and long storage periods. The stock records are the core here, because they must match at any moment what customs has in its own system.
Inward processing and processing operations
Material arrives under suspension and leaves again once processed. The yield rate and the discharge deadline are where things go wrong. For the transport around it, there is transport software.
Import using the simplified procedure
High shipment volumes and short lead times. What matters most here is that the period closes cleanly and the supplementary declaration goes out on time. See also customs declaration software in DMS.
Customs brokers and representatives
You act on behalf of multiple clients, each with their own authorisations. Checking the right conditions per client is not a luxury but the core of your liability. For the air side, there is air freight software.
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
Authorisation conditions, message versions and deadlines change. All of it should be configurable and stored with its history, because you also need to be able to account for an old entry.
If you want to check your own EORI numbers and those of your business partners in advance against the European Commission's EORI database, take a look at our EORI-DMS integration.
Why Appfront
The authorisation belongs in the system
We record conditions as data that can be checked against. In a PDF, a condition does nothing.
Check before the legal moment
We put the check before the entry. After that, an error becomes a correction with a notification rather than a simple amendment.
Your records are the declaration
That is why we build to the standards that apply to evidence: a fixed time, no silent changes, and full recording at the moment itself.
The clock starts earlier than people think
We start the deadline from the entry, not from when the supplementary declaration is drawn up. Otherwise that difference results in a late declaration.
Security and privacy
Customs data touches your purchasing, your margins and your customers. For a representative, there is the added requirement that the data of different clients must remain strictly separated. We set up access per client and per authorisation, and log every view.
On this topic, record-keeping is not a supporting function but a legal one. The entry is the declaration, so a time that shifts afterwards or a line that is quietly updated directly affects what you have declared. That is why we record entries immutably, with time and person, and make a correction a visible correction alongside the original line. In an audit, that is the difference between records and an assertion. How we handle security ourselves is set out in our information security policy; external reports go through our CVD policy.
Frequently asked questions about DMS and authorisations
It is a simplification where you declare goods by entering them in your own records, instead of sending a declaration message per shipment. The customs debt arises at the moment of that entry. A supplementary declaration for the period follows. The exact conditions are set out in your own authorisation.
For the special procedures: customs warehousing, temporary admission, end-use, inward processing and outward processing. And only if you already hold an authorisation for that procedure itself. So there are always two authorisations layered on top of each other, with conditions that apply at the same time.
No later than the tenth day after the entry. In the Netherlands, the period is one calendar day and the supplementary declarations for that period are submitted in one go. An important detail: the clock starts at the entry, not when the supplementary declaration is drawn up. Check the exact deadlines in your authorisation.
That page covers submitting declarations now that the old declaration system has been replaced: messages, statuses and declarations that get stuck. This page covers the layer before that: which authorisations you hold, what they permit, and the records that, under a simplified procedure, effectively are the declaration.
Probably on one point: the moment of entry must be fixed and not be shiftable afterwards. Many stock systems post with a posting date that someone can change, and that is unsuitable for this scheme. The other data you need is set out in your authorisation and in Customs' explanatory notes.
Yes, and for a representative that is the core requirement. Each client has its own authorisations with its own conditions, and these must remain strictly separate. We set up access and validation per client, so that an employee cannot accidentally make an entry under the wrong authorisation.
Then it is a correction rather than an amendment, because the legal moment has already passed. Your system must be able to record that correction alongside the original entry, with the reason and a timestamp. How you handle the correction with Customs depends on the case; agree this with your customs adviser.
That depends on which schemes you operate, the number of authorisations and whether integrations with your stock and shipping systems are needed. The authorisation register with upfront validation is usually quick to put to use and removes the biggest risk; the supplementary declaration per period costs more. We provide a substantiated estimate after the discovery phase.
Want to know whether your entry is fixed?
Look up an entry from last month and check whether the timestamp is still the original or a posting date that someone has set. That difference determines whether you have records or just an assertion. We build this as a standalone application and as part of a broader custom software project.