Incomplete documentation

In some cases, the information submitted may not be sufficient to complete processing. At the endpoint "/house-consignment/validation-status/{requestIds}", you will receive a list of reason codes under "incompleteDocumentationReasonList". It is also possible to query the endpoints "/house-consignment/transport-document/status" or "/master-consignment/transport-document/status" to get this information.

Specified field cannot have a value when specified customs procedure ("importProcedure" is X) is provided

Response

{
  "status": "FAILURE",
  "requestId": "${requestIdForSubmission}",
  "notificationDate": "${dateTimeResultWasReady}"
  "validationErrorList": [
    {
      "description": "Field cannot be filled out when consignmentHouseLevel.importProcedure is ${importProcedureType}",
      "pointer": {
        "messageElementPath": "consignmentHouseLevel.previousDocuments[${indexInList}].${fieldName}"
      }
    }
  ]
}

Cause

If the customs procedure ("importProcedure") is specified, this field cannot be filled out, i.e., the field specified in "messageElementPath". This error occurs when the specified customs procedure is different from "IMMEDIATE_RELEASE_IMPORT" while specifying values in the fields that indicate the reference to the customs declaration. ("consignmentHouseLevel.previousDocuments.sequenceNumber", and/or "consignmentHouseLevel.previousDocuments.declarantNumber" and/or "consignmentHouseLevel.previousDocuments.declarationDate")

Correction

Either change the importProcedure or remove the value in this field. Resubmit. Use the new "requestId" received in return for the new submission and verify that asynchronous validation for this returns the field "status" with the value "SUCCESS" when new processing is complete.

Field cannot have a value for transit ("N820") if the procedure the consignment was subject to until border crossing into Norway ("outgoing procedure") is specified as export ("EXP")

Response

{
  "status": "FAILURE",
  "requestId": "${requestIdForSubmission}",
  "notificationDate": "${dateTimeResultWasReady}"
  "validationErrorList": [
    {
      "description": "Field cannot have value N820 out when consignmentHouseLevel.outgoingProcedure is EXP",
      "pointer": {
        "messageElementPath": "consignmentHouseLevel.previousDocuments[${indexInList}].typeOfReference"
      }
    }
  ]
}

Cause

If the procedure the consignment was subject to until border crossing into Norway ("outgoingProcedure") is specified as export (with value "EXP"), the value "N820" cannot be specified in this field. This applies to references to previous customs procedures that the goods have been subject to. If the previous customs procedure is specified as export, a reference to transit cannot be provided.
See choice of customs procedure mo-vei-EN.html#utfyllingForsend

Correction

Either change the value in the field or outgoingProcedure. Resubmit. Use the new "requestId" received in return for the new submission and verify that asynchronous validation for this returns the field "status" with the value "SUCCESS" when new processing is complete.

When the referenced document ("typeReference") is a customs declaration ("CUDE"), the specified field is mandatory

Response

{
  "status": "FAILURE",
  "requestId": "${requestIdForSubmission}",
  "notificationDate": "${dateTimeResultWasReady}"
  "validationErrorList": [
    {
      "description": "Required field when typeReference is CUDE",
      "pointer": {
        "messageElementPath": "consignmentHouseLevel.previousDocuments[${indexInList}].${fieldRequired}"
      }
    }
  ]
}

Cause

If the referenced document is a customs declaration ("typeReference" with value "CUDE"), a value must also be provided in the specified field (the field is specified in the error message).

Correction

Either change the typeReference or provide a value for the field. Resubmit. Use the new "requestId" received in return for the new submission and verify that asynchronous validation for this returns the field "status" with the value "SUCCESS" when new processing is complete.

If one or more document references ("previousDocument") are specified, a customs procedure (field "importProcedure") must be provided

Response

{
  "status": "FAILURE",
  "requestId": "${requestIdForSubmission}",
  "notificationDate": "${dateTimeResultWasReady}"
  "validationErrorList": [
    {
      "description": "importProcedure is required when any consignmentHouseLevel.previousDocuments[] is provided",
      "pointer": {
        "messageElementPath": "consignmentHouseLevel.importProcedure"
      }
    }
  ]
}

Cause

One or more references to documents (objects in the "previousDocuments" list) have been submitted, but a customs procedure (value in the "importProcedure" field) has not been provided.

Correction

Either provide a value for the importProcedure field or remove all objects in the previousDocuments list. Resubmit. Use the new "requestId" received in return for the new submission and verify that asynchronous validation for this returns the field "status" with the value "SUCCESS" when new processing is complete.

Only one document reference to a customs declaration (an object in the "previousDocuments" list) of type customs declaration (with "typeOfReference" = "CUDE") can be provided

Response

{
  "status": "FAILURE",
  "requestId": "${requestIdForSubmission}",
  "notificationDate": "${dateTimeResultWasReady}"
  "validationErrorList": [
    {
      "description": "PreviousDocuments can only contain one document of type CUDE",
      "pointer": {
        "messageElementPath": "consignmentHouseLevel.previousDocuments"
      }
    }
  ]
}

Cause

More than one customs declaration (object in the "previousDocuments" list) with the value "CUDE" in the field "typeOfReference" has been submitted.
Only one customs declaration per consignment is allowed.

Correction

Ensure that only one object with the typeOfReference value "CUDE" is in the previousDocuments list.
Resubmit. Use the new "requestId" received in return for the new submission and verify that asynchronous validation for this returns the field "status" with the value "SUCCESS" when new processing is complete.

If the document reference is something other than a customs declaration ("typeOfReference" <> "CUDE"), the reference must be provided in the "referenceNumber" field in the "previousDocuments" object

Response

{
  "status": "FAILURE",
  "requestId": "${requestIdForSubmission}",
  "notificationDate": "${dateTimeResultWasReady}"
  "validationErrorList": [
    {
      "description": "Field should have value unless typeOfReference is CUDE",
      "pointer": {
        "messageElementPath": "consignmentHouseLevel.previousDocuments[${indexInList}].referenceNumber"
      }
    }
  ]
}

Cause

When referencing other types of documents than customs declarations, the "referenceNumber" field in "previousDocuments" should be used to provide this reference (typically MRN or similar).
An object in the "previousDocuments" list has been submitted with a value that is not "CUDE" in the field "typeOfReference", while not providing a value in the "referenceNumber" field.
This field must be provided with a value unless "typeOfReference" has the value "CUDE".

Correction

Change the object to have the value "CUDE" in the typeOfReference field, or provide a valid value in the referenceNumber field. Resubmit. Use the new "requestId" received in return for the new submission and verify that asynchronous validation for this returns the field "status" with the value "SUCCESS" when new processing is complete.