Building an app for registration on receipt and release
Under a simplified procedure, you make a declaration by entering goods in your own records. That means the forklift driver who books in a pallet performs a legal act: at that moment the customs debt arises. A booking date that someone can change later is no longer a booking date.
Why the warehouse floor is the legal moment here
The authorisation for entry in the declarant's records is granted for special procedures: customs warehousing, temporary admission, end-use and inward or outward processing. Instead of sending a declaration message for each shipment, you enter the goods in your own records. From that moment everything starts running: the customs debt arises, the deadline for the supplementary declaration begins and the goods fall under the procedure.
In the Netherlands the period is one calendar day, and the supplementary declaration must be submitted no later than the tenth day after entry. That makes the day on which something was entered decisive for which batch it ends up in. A pallet that arrives at 23:40 but is booked in the next morning ends up in the wrong period, and you only notice once the message has already been sent.
The requirement for the records is explicit: they must be set up so that data is recorded correctly, on time and in full. Many inventory systems post with a date that a user can choose or correct afterwards. That is convenient for ordinary stock records, but unsuitable for this scheme, because here that field is the declaration date.
How we build this
The entry must be made at the moment of the physical handling, with a timestamp nobody can change. Everything else follows from that.
Scanning on receipt or dispatch is the entry, not a preparation for it. That is the only way the timestamp and reality coincide.
The moment of handling is recorded and cannot be changed afterwards. A correction is added alongside it, with the reason and the person responsible.
Does this type of goods fall under the authorisation, and is the procedure permitted? Once the entry is made, a mistake becomes a correction, with all the consequences that brings.
A customs warehouse does not have coverage everywhere. The app keeps working locally and retains the original timestamp when it syncs.
What the app actually does
The entry at the point of handling carries the whole thing. What you add beyond that depends on which procedures you operate.
Registering by scanning
On receipt or dispatch, the consignment is entered with the timestamp of the handling. No form afterwards, because that is exactly where the date starts to drift.
Checks before the legal moment
Type of goods, procedure and validity of the authorisation are checked before the entry becomes final. After that, it is a correction.
The period visible on the floor
Which calendar day applies and until when it stays open. For a handling late in the evening, that makes the difference for the supplementary declaration.
Stock with procedure and discharge deadline
With customs warehousing and inward processing, every batch carries a procedure and a discharge deadline. Without that information, your stock is not a customs record.
Works without coverage
In a warehouse, the signal drops out. Everything is recorded locally with the original timestamp and synchronised later.
Connecting to your customs records
The authorisations, periods and supplementary declarations remain in your customs administration system. We write to it via integrations.
Who we build for
Where the entry takes place differs per procedure. Four situations.
Customs warehouse
Goods in and goods out are the moments that count here. The stock records must match, at any moment, what customs holds in its own system.
Inward processing
Material arrives under suspension and leaves again after processing. The link between incoming and outgoing batch is a customs question here too, not just a production question.
Import with large numbers of consignments
Many entries per day and short lead times. What matters most here is that the period closes with everything in it and nothing outside it. Filing itself is covered under software for customs declarations.
Freight forwarders and representatives
You register on behalf of several clients, each with their own authorisations. Registering under the wrong authorisation then becomes a liability issue.
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 and message versions change. Everything to do with procedures, periods and checks should be configurable rather than hard-coded in the app.
Why Appfront
The act is the declaration
We build the registration into the scan itself. A form completed afterwards puts the declaration date at the wrong moment.
The timestamp must be fixed
We make the moment immutable. A posting date that a user can choose is unsuitable for this arrangement.
Checking beforehand, correcting afterwards is expensive
We place the check on goods type and authorisation before the registration, because afterwards the legal moment has already passed.
A warehouse has no coverage
We build it to work offline, preserving the original timestamp. Otherwise the registration gets the time of synchronisation.
Security and privacy
This app touches your purchasing, your suppliers and your margins, and, for a representative, the data of several principals at once. We set access per principal and per authorisation, show on the floor no more than is needed for the task, and log every view.
With this subject, record-keeping is not supportive but legal. The registration is the declaration, so a timestamp that shifts afterwards or a line that is quietly updated directly affects what you have declared. We record registrations immutably with time, place and person, even when synchronisation happens later, and turn a correction into a visible correction alongside the original line. How we handle security ourselves is set out in our information security policy; external reports go through our CVD policy.
Frequently asked questions about the DMS app
With a authorisation for registration in the declarant's records, yes: the customs debt arises at the moment of registration in your records. What exactly that registration is and which data it must contain is set out in your own authorisation. Have your customs adviser check this before you set up a process.
Because that field is the declaration date here. In an ordinary stock system an editable posting date is handy; here it determines which period the consignment falls in and when the supplementary declaration must be submitted. We therefore fix the moment and place a correction next to it rather than over it.
In the Netherlands the period is one calendar day. The supplementary declarations for that period are all submitted at once, no later than the tenth day after registration. A consignment registered just after midnight therefore belongs to the next day. Check the exact deadlines in your authorisation.
The AGS app deals with the documents that travel with a customs consignment and with what must be present during loading and unloading. This app deals with the registration itself: the act by which you make the declaration. That is a different act at a different moment.
Yes, and that is necessary: a customs warehouse rarely has coverage everywhere. Everything is recorded locally with the original timestamp and synchronised later. Without that preservation, a registration would get the time of synchronisation, and then the period would no longer be correct.
Yes, and that is the most important function. Goods type, procedure and validity of the authorisation are checked before the registration becomes final. After that moment it is a correction, with everything that entails towards Customs.
Yes, and then separation is the key. Each principal has its own authorisations with its own conditions. We set access and checks per principal, so that an employee does not accidentally register under the wrong authorisation.
That depends on the number of handling points, which procedures you run and whether integrations are needed with your stock and customs systems. Scanning with the upfront check is usually quick to put into use and removes the biggest risk; the stock side costs more. We give a substantiated estimate after the discovery phase.
Want to know if your registration time is correct?
Take a registration from last week and compare the time in the system with the moment the pallet was physically there. If there is a gap, your declaration date falls at the wrong moment. We build this as a standalone app and as part of a broader app development project.