DMS19000
Also known as: manually rejected, HANDMATIG AFGEWEZEN
DMS19000 is the error code HANDMATIG AFGEWEZEN DOOR DE DOUANE in table A99. A Customs officer has rejected the declaration, and the Codeboek Douane refers you to the Nationale Helpdesk Douane for more information.
What does DMS19000 say according to the code book?
The Codeboek Douane of 17 February 2026 sets at DMS19000 the text HANDMATIG AFGEWEZEN DOOR DE DOUANE. The legal note in the same table is: your declaration has been rejected manually by Customs. Contact the Nationale Helpdesk Douane for more information. That is the whole official line. There is no field name next to it. This is not a validation error of the message model. The XML was processable enough on the substance to reach an officer. That officer has rejected the declaration. The cause does not stand in the code. The code only says that it was not an automatic mandatory rule. You cannot solve 19000 by guessing at a goods code or an authorisation. For as long as this rejection is open, the declaration has not been accepted. Behaviour is comparable with other acceptance refusals: no MRN, no release, no automatic next step. The difference is the route to the cause. That runs via Customs, not via repairing one XML field. DMS is the Dutch system.
What is the difference with an ordinary validation error?
DMS10001, 10047 or 120AA you can trace yourself to a field. 19000 you cannot. There is no location that says: item six, field mass. The officer has a substantive or procedural objection that the system does not catch in a field rule. The three-part reading of code, description and location therefore stops at the code and the official sentence. Examples that in practice lead to a manual rejection, without the code naming them: a procedure that is not open for these goods, a consignment that should have run in another system, or a declaration that Customs does not want to accept until there has been contact. Those are reasons to call, not to send the same message again. Filing again without contact is pointless if the rejection is manual. DMS can put the message with the same handling again. The Helpdesk asks for the MRN-less reference trail of your filing, the time and the text of 19000. Have those three ready before you call. A second filing while you wait does not create an MRN.
What do you do first?
Stop changing and sending again. Collect the filing reference, the time, the client, the goods code and the procedure. Call or email the Nationale Helpdesk Douane, as the code book prescribes. The official route is that desk, not a vendor forum and not a second guess at the XML. Say that it concerns DMS19000, manually rejected, and ask for the reason. Without that reason every correction in your file is guesswork. With the reason you know whether you must change the procedure, send a document on, or withdraw the declaration. Write the reason into the file in the words of the Helpdesk. Inform the client that the consignment is standing still without an MRN, and that the cause lies in a manual decision, not in a missing digit. For fresh cargo that is the moment to shift the inspection diary, not to hope that a second message is faster. A CHED slot does not move because you resent an IMA.
Can 19000 sit together with other codes?
DMS19999, EXTRA FOUTEN ONTDEKT, means that there are more messages than shown. 19000 can be one of them, or the only visible one. Treat 19000 as the heaviest: first the Helpdesk, then field corrections from other codes in the same response. A mandatory rule you can see is still worth correcting, but it does not replace the call about the manual rejection. If after contact you get a substantive reason that does fall on a field, correct that field and file again. The new response can be an ordinary validation code, or an acceptance with an MRN. 19000 itself does not disappear by ignoring it. Keep 19000 on the file, even after a later MRN on a new filing. In a discussion about lead time this is the proof that the first refusal did not sit in your XML. A client who sees only the later MRN will ask why the consignment lost a day. The saved 19000, with time and Helpdesk reference, is the answer.
How do you prevent 19000?
You do not prevent it with a cleaner mapping. A manual rejection sits outside the automatic rules. What you do prevent is the second 19000 on the same flow: if the Helpdesk says that this procedure or this goods flow may not run via this message, you record that on the client. The next declaration of that type then never leaves the intake. Do not file test messages on live DMS to see what happens. A manual rejection is a handling step at Customs. Repeated testing on the same consignment costs time on both sides and does not solve the first 19000. Live DMS is the Dutch production system. DMS is the Dutch system. A manual rejection in DMS says nothing about a consignment that you should have put in NCTS or in DECO. If the Helpdesk sends you to another channel, that is the correction. Not an extra field on the same IMA.
What do you tell the client?
That Customs has rejected the declaration manually, that there is no MRN, and that the Nationale Helpdesk Douane must give the reason. Do not promise a time at which the consignment will be released. 19000 has no automatic SLA in the code book. A planner who is told this afternoon on the basis of a validation habit will plan a truck that cannot leave. Do not share a made-up cause. Do not say that it is the goods code or the authorisation, unless the Helpdesk has said so. A wrong explanation to the client produces a wrong correction, and a second 19000. Once the reason is in, you record the next step: a new filing with a changed procedure, sending a document on, or withdrawal. That step is operational, not a guess at another error code. Tell the client which of those three it is, and that a new MRN only exists after a new acceptance.