DMS10001
Also known as: mandatory rule error, VERPLICHTINGREGEL FOUT
DMS10001 is the error code VERPLICHTINGREGEL FOUT in table A99 of the Codeboek Douane. A mandatory field or a mandatory combination is missing or does not match, and the location in the message points to the element.
What does DMS10001 say according to the code book?
In the Codeboek Douane, onderdeel DWU Aangiftebehandeling of 17 February 2026, DMS10001 carries the description VERPLICHTINGREGEL FOUT. It is an acceptance-blocking error. The declaration is not accepted for as long as the named element breaks the rule that DMS applies to it. There is no MRN until that element follows the rule. A mandatory rule is not the same as a missing free-text field. It is a rule in the message model: this field must be present, or this field must have this value if another field has a given code. TARIC can draw such a rule, an authorisation can, or the UCC data model itself. The code tells you that that rule is broken, not which source set it. The location in the XML points to the field. If Classification with IdentificationTypeCode TRC stands there, it is about the TARIC code on that item line. If Authorisation stands there, it is about an authorisation. Without that location you guess which field is missing, and you file a declaration that is still wrong on the real field.
Where does the error sit most often?
On item lines. A mandatory document at the goods code, an additional code, a net mass, a preference code or a supporting document that TARIC requires. The location then names GoodsItem with a sequence number. That number is the line in your declaration, counted from one. GoodsItem[6] is line six. Less often, but harder, the error sits at declaration level: an authorisation that is mandatory for this procedure, an EORI of the declarant, or an office of entry. Then the path starts with Declaration/ without GoodsItem. If you correct an item while the error sits on the header, the rejection remains. Look at whether the path contains GoodsItem before you open an item line. A mandatory rule can also be a combination. Field A may only be present if field B has a given value, or field A must be present as soon as field B is filled. Filling one field without the other produces the same code as omitting both. The location usually names the field that DMS misses first.
How do you check the rule before you file again?
Open the item line that the location names. Check the goods code against the DTV and TARIC, including measures and mandatory document codes. If a mandatory document code is listed and the supporting document is missing, that is the mandatory rule. If the code is present but in the wrong format, the same DMS10001 can fall, or a format code such as DMS10010. Then check the authorisations on the header of the declaration. An IMA under article 23 without the authorisation standing on the declarant or the importer is a mandatory rule. An STO without a warehouse authorisation is too. The master data of the client should already carry that authorisation. Do not file again with only an extra space or a capital letter changed. The mandatory rule looks at presence and at the allowed value. Cosmetics in the description do not solve it. If you cannot see which field is mandatory, trace the location back to the screen field, not to the error text in general.
What is the difference with DMS10047 and DMS10048?
DMS10047, AANGIFTE GEGEVEN VERPLICHT, says that a data element on the declaration is mandatory. DMS10048, AANGIFTE GEGEVEN NIET TOEGESTAAN, says that a data element may not stand there. DMS10001 is broader: the mandatory rule can be a combination, a condition from TARIC, or a rule from the data model that does not fit those two short texts. In practice they overlap. A missing goods code can come back as 10001 or as 10047, depending on where in the model the rule hangs. Always read the location. The three codes send you to the same kind of work: lay the field next to the source and carry out the rule attached to it. What you must not do is fill the same field three times because you saw three codes. One correction at the location that sits highest in the path often clears a chain of messages. Item line six with a missing code sometimes also pulls a mass rule and a document rule with it. First the code, then file again, then read the rest.
How do you prevent DMS10001 in a batch?
Check every item line against TARIC before the batch goes to DMS. Missing document codes, missing additional codes and goods codes that expired on 1 January are the classic mandatory rules in a large consignment. A mapping that was right in December can give 10001 in January on hundreds of lines at once. Per client it should be fixed which authorisation stands on which declaration type. If that link is missing, the whole day's flow for that client fails on the same code. That is not chance in the messages, that is master data. Correct the card once, then the open files. E-commerce via DECO has its own, limited data set. A mandatory rule from a full IMA does not simply belong on it. Anyone who files an H7 consignment as IMA, or the other way round, gets mandatory rules that belong to the wrong type. Choose the channel first, then the fields. DMS is the Dutch system for the full declaration. DECO is the Dutch e-commerce channel.
What do you do if the location names a field you do not know?
Translate the XML path to the screen. Classification/IdentificationTypeCode TRC is the TARIC code. TypeCode on AdditionalReference is the document code of the supporting document. ID on SupervisingOffice is the supervising office. The paths are English because the message model is English. The code itself and the description in A99 are Dutch. If you still cannot work it out, the official route is the code book plus the Nationale Helpdesk Douane, not a forum post about AGS. The Helpdesk helps with the meaning of the message. The correction in your master data remains your work. Save the rejection on the file, with code, text and location. If the same 10001 comes back a week later on another client, you compare the locations. If it always sits on the same kind of line, the mapping or the authorisation rule is the cause, not the individual paper of that day.