iCareZ CDS Error Handling and Resolution

The iCareZ guide to CDS error handling and resolution is a comprehensive reference designed to help declarants, brokers, and system integrators navigate HMRC CDS error codes with confidence. It provides clear explanations of each error, identifies likely causes, and offers practical guidance for efficient resolution. By using this guide, clients and potential clients can better understand common CDS submission issues, reduce errors, and improve first-time acceptance rates.

For an overview of how iCareZ supports CDS submissions, you can return to the Customs Declaration Services (CDS).

Description:
Obligation error: Mandatory Data Element has not been provided.

Explanation:
Required details are missing – Either a DE is missing, or required information in a DE is missing/incomplete.

Check the declaration to ensure that all the required data elements have been completed in full. For example, if declaring a party name and address, then name, street and number, country and postcode must be completed.

Reason:
One or more mandatory data elements are missing or incomplete in the declaration. All required components of each data element, such as party name, street and number, country, and postcode, must be fully provided to pass CDS validation.

Resolution:

  • Review the declaration to ensure all mandatory data elements are completed in full.
  • Verify that no required field is blank or partially completed.
  • Ensure all components of party information (name, street and number, country, postcode) are provided where applicable.
  • Reprocess the declaration after correcting all missing or incomplete details.

Description:
Obligation error: Data Element is not allowed.

Explanation:
Invalid entry on the declaration.

Go through the declaration from the beginning to find where you have entered details that are not permitted. Some details are not permitted at item level, only at header level – this is specified by an X or Y at the start of the value sent.

Reason:
This error occurs when a data element is declared at a level where it is not permitted. Certain data elements are only allowed at the declaration header level or the goods item level, depending on CDS rules. If a value is entered at an incorrect level, CDS identifies it as invalid and rejects the declaration.

Resolution:

  • Review the declaration to identify any data elements entered at incorrect levels.
  • Check the CDS specification to confirm whether each affected data element is permitted at header level or goods item level.
  • Remove or relocate data elements that are not allowed for the declaration type.
  • Ensure that only permitted data elements are present at each level of the declaration.
  • Reprocess the declaration after correcting all incorrectly placed data elements.

Description:
Obligation Error: Number of Occurrences exceeds what is allowed for the Data Element.Obligation Error: Number of Occurrences exceeds what is allowed for the Data Element.

Explanation:
Too many instances of a data element.

You have exceeded the limit for one of the fields on the declaration. For example, only 1 preference code can be declared against an item.

Reason:
This error occurs when a data element has been declared more times than permitted under CDS rules. Each data element has a defined maximum number of allowable occurrences. For example, declaring more than one preference code against a single goods item will trigger this error.

Resolution:

  • Review the rejection details to identify the data element exceeding the allowed occurrences.
  • Confirm the maximum number of occurrences for the data element using the CDS specification.
  • Count instances within the declaration and identify any excess entries.
  • Remove or consolidate entries to ensure the total does not exceed the permitted limit.
  • Use alternative permitted data elements or supporting documentation if the same information must appear multiple times.
  • Reprocess the declaration after correcting all occurrence issues.

Description:
Commodity Code Error: Mandatory data element not provided and/or format error and/or number of occurrences exceeds what is allowed for the data element.

Explanation:
Commodity Code Error:

A commodity code error is likely to be caused by missing or incorrect additional codes to the commodity code – these are the national additional codes or TARIC additional codes.
It may also be triggered where an insufficient number of digits have been provided.

Reason:
This error occurs when a declared commodity code is incomplete, incorrectly formatted, or missing mandatory additional codes. Common causes include missing or incorrect national additional codes or TARIC additional codes, or providing a commodity code with insufficient digits as required by tariff rules.

Resolution:

  • Review the rejection details to identify affected goods item lines.
  • Verify that the declared commodity code complies with UK Trade Tariff and TARIC requirements, including the correct number of digits.
  • Ensure all mandatory national and/or TARIC additional codes applicable to the commodity code are present and correctly declared.
  • Add missing additional codes and correct any formatting errors.
  • Confirm that the number of additional codes does not exceed the maximum permitted for the goods item.
  • Reprocess the declaration after correcting all commodity code format and occurrence issues.

Description:
Format Error: data element has invalid format.

Explanation:
Invalid Format.

One of the data elements does not comply with the minimum/maximum number of characters or uses characters not permitted. For example, the country code field with the address must only use alphabetic characters.

Reason:
This error occurs when a data element does not meet the required character format, length, or type. For example, alphabetic fields such as country codes must only contain letters, and numeric fields must not include letters, symbols, or extra spaces.

Resolution:

  • Review the rejection message to identify the affected data element(s) and the corresponding item or declaration section.
  • Check the CDS specification to confirm required format, character type (alphabetic, numeric, or alphanumeric), and minimum/maximum length.
  • Examine the entered value for invalid characters, incorrect length, extra spaces, or prohibited punctuation.
  • Correct the value to comply with the required format.
  • Ensure numeric fields contain only numeric values, and alphabetic fields contain only letters.
  • Reprocess the declaration after correcting all format issues.

Description:
Domain Error: data element contains invalid value.

Explanation:
Invalid Value:

A code used in the declaration is either not a recognised code or is not a code permitted on the particular declaration.
For example:
A document code which is only permitted on export declarations has been declared on an import declaration.
A valid code has been entered on the declaration, but has been entered at the wrong level (header or item) to which it is permitted.

Reason:

This error occurs when a code declared in the submission is either not recognised by CDS or is not permitted for the specific declaration type or data element.
Common scenarios include:
Using a code valid for export on an import declaration (or vice versa).
Entering a valid code at an incorrect level, such as item level instead of header level.

Resolution:

  • Review the CDS rejection message to identify the affected data element and invalid code.
  • Refer to the official CDS code list or domain for the data element (e.g., document codes, country codes, additional codes).
  • Confirm that the code is permitted for the declaration type (import or export) and allowed at the correct level (header or goods item).
  • Replace unrecognised or invalid codes with valid codes from the relevant domain.
  • Move any correctly valued codes declared at the wrong level to the appropriate level.
  • Reprocess the declaration after correcting all domain and level issues.

Description:
Data Error: Value must be positive.

Explanation:
You appear to have entered a negative value.

A negative amount has been declared for writing off a licence. The quantity being written off for a licence must be equal to or greater than zero.

Reason:
This error occurs when a negative value is declared where only zero or positive values are permitted.
A common scenario is entering a negative quantity or amount for a licence write-off. Under CDS rules, the quantity being written off must be equal to or greater than zero.

Resolution:

  • Identify the data element referenced in the CDS rejection (e.g., amount, quantity, or licence write-off field).
  • Check the entered value for negative indicators such as minus signs (-) or parentheses.
  • Replace the negative value with a valid positive value or zero according to CDS requirements.
  • If the negative value was intended for reversal, confirm the correct data element or adjustment method to use.
  • Ensure numeric formatting is correct (valid decimals, no embedded commas or non-numeric characters).
  • Reprocess the declaration after correcting all negative or invalid values.

Description:
Calculated item Customs value is negative. Check declaration valuation data.

Explanation:
Valuation Error:

The deductions you declared may exceed the value of the items. See CDS Tariff completion notes for data element 4/9. Apportioning a deduction across multiple items must not reduce the value of any single item to zero or a negative amount.

Reason:
This error occurs when declared deductions reduce the customs value of one or more items below zero.
Under CDS valuation rules, deductions apportioned across multiple items must not reduce any individual item’s value to zero or a negative amount. This is governed by CDS Tariff Completion Notes for Data Element 4/9 (Deductions).

Resolution:

  • Review all deductions declared under Data Element 4/9 for the affected goods items.
  • Compare total deductions against each item’s declared customs value.
  • Identify any deductions that result in zero or negative item values.
  • Adjust, remove, or re-apportion deductions to ensure each item retains a positive customs value.
  • Recalculate customs value for each item after correcting deductions.
  • Ensure deductions are apportioned proportionately in accordance with CDS Tariff Completion Notes.
  • Reprocess the declaration after correcting all deductions and item values.

Description:
Relation Error: The value declared in Total Number of Items (D.E. 1/9) does not correspond with the number of goods items on the declaration.

Explanation:
You have more or fewer items than the number you declared.

Amend data element 1/9 to match the number of declared goods items on the declaration.

Reason:
This error occurs when the total number of goods items declared does not match the actual number of goods items included in the declaration.
Data Element 1/9 (Total Number of Items) must accurately reflect the count of goods item lines present. Any discrepancy, whether more or fewer items than declared, will result in rejection.

Resolution:

  • Count the actual number of goods item lines included in the declaration.
  • Compare this count with the value declared in Data Element 1/9 (Total Number of Items).
  • Update Data Element 1/9 to exactly match the number of goods items declared.
  • Check for and remove any unintended blank, duplicate, or partially created item lines.
  • Ensure all goods items are correctly numbered and sequential.
  • Reprocess the declaration after correcting the item count.

Description:
Relation Error: The combination of Trade Movement Type, Declaration Type followed by requested procedure and /or previous procedure code is invalid.

Explanation:
Relation Error:

The combination of procedure code and additional procedure code is either invalid or is not permitted on this type of declaration.
Or the additional procedure code combination is not permitted.

Reason:
This error occurs when the combination of procedure code and additional procedure code declared is invalid or not permitted for the specific declaration type.
It may also arise when multiple additional procedure codes are used together in a combination that CDS rules do not allow.

Resolution:

  • Identify the procedure code declared for each affected goods item.
  • Review the associated additional procedure code(s) for that procedure code.
  • Confirm that each additional procedure code is allowed with the selected procedure code.
  • Verify that the overall combination is valid for the declaration category (e.g., H1, I1, B1).
  • Remove any additional procedure codes that are not permitted or replace them with valid alternatives.
  • Refer to CDS Tariff and procedure code combination tables to confirm allowed usage.
  • Reprocess the declaration after correcting the procedure code combination.

Description:
Relation Error: The Requested Procedure (D.E. 1/10) for each Goods Item must derive the same Declaration Category (e.g. H1) or acceptance date is not valid. No further validation has been carried out.

Explanation:
Relation Error:

All items on the declaration must derive from the same procedure category. For example if one item has requested procedure 40, then another item must not have a requested procedure of 71 because this would require a different declaration type.

Reason:
This error occurs when goods items within the same declaration are assigned to different procedure categories.
All items in a single declaration must belong to the same declaration type (e.g., H1, I1, B1).

Resolution:

  • Review the requested procedure code (D.E. 1/10) for each goods item.
  • Identify any item with a procedure code that belongs to a different declaration category than the others.
  • Determine the correct declaration type for the consignment.
  • Amend procedure codes so that all items align to a single, permitted declaration category.
  • Remove or replace any conflicting procedure codes causing a mismatch.
  • Reprocess the declaration after ensuring all goods items derive from the same procedure category.

Description:
Relation Error: Net Mass must be lower than Gross Mass

Explanation:
Relation Error:

Net mass declared is greater than the gross mass declared.

Reason:
This error occurs when the net mass declared for a goods item exceeds the gross mass.
Gross mass must always include the net mass plus any packaging; net mass cannot be greater than gross mass.

Resolution:

  • Review net mass and gross mass declared for each affected goods item.
  • Identify any items where net mass exceeds gross mass.
  • Correct net and/or gross mass values so that gross mass ≥ net mass including packaging.
  • Ensure units of measurement are consistent across the declaration.
  • Reprocess the declaration after verifying all mass values are correct and logically consistent.

Description:
Relation Error: The submitter of the Additional Message differs from the original declaration.

Explanation:
Additional message cannot be accepted.

A person linked to a different EORI number or different identification details cannot send a request to HMRC about the declaration, such as requesting a cancellation. Only the original declarant can send requests.

Reason:
This error occurs when a follow-up request (e.g., cancellation or amendment) is submitted by a different EORI or legal entity than the original declarant. Only the original declarant is permitted to send requests related to an existing declaration.

Resolution:

  • Identify the EORI used to submit the additional message or request.
  • Compare it with the original declarant’s EORI on the declaration.
  • Ensure that any follow-up request is submitted by the same legal entity and EORI that originally lodged the declaration.
  • If necessary, coordinate with the original declarant to submit the request on your behalf.
  • Reprocess the declaration once the correct EORI and sender details are confirmed.

Description:
Element is not allowed to be amended on this declaration type.

Explanation:
Element is not allowed to be amended on this declaration type.

Check your amendment request. For example, you cannot change a declaration from prelodged (D) to arrived (A) through amendment, only through goods arrival.

Reason:
This error occurs when an amendment attempts to change data elements or declaration states that are not amendable under CDS rules. For example, a declaration cannot be changed from pre-lodged (D) to arrived (A) via an amendment; this must be done using the goods arrival process.

Resolution:

  • Identify all data elements included in the amendment request.
  • Verify which data elements and declaration states are amendable under CDS rules.
  • Remove any amendment attempts for non-amendable fields or states.
  • Use the correct CDS process (e.g., goods arrival) for status changes not allowed via amendment.
  • Retain only valid and permitted changes in the amendment request.
  • Reprocess the amendment once all invalid changes have been removed and compliance is ensured.

Description:
Uniqueness Error: Reuse of LRN (D.E. 2/5) is not allowed within 48 hours.

Explanation:
Local reference number duplication.

You used the same local reference number (LRN) within 48 hours. Change the LRN or add a version number at the end using letters and numbers only.

Reason:
This error occurs when the same Local Reference Number (LRN) is reused within a 48-hour period. CDS requires each declaration to have a unique LRN during this timeframe. Reuse of an existing LRN causes the declaration to be rejected.

Resolution:

  • Identify the previously submitted declaration that used the same LRN.
  • Generate a new unique LRN or append a version identifier using permitted characters (letters and numbers only).
  • Update the declaration with the revised LRN.
  • Confirm the new LRN has not been used in any CDS submission within the last 48 hours.
  • Reprocess the declaration once the LRN is corrected and uniqueness is ensured.

Description:
Authorisation Error: Party ID unknown or invalid.

Explanation:
Identification not recognised.

An EORI or VAT number included on the declaration is not recognised or the number used is not permitted in this DE.

Reason:
This error occurs when an EORI or VAT number declared is either unrecognised by CDS or not permitted for the specific data element. Causes may include an invalid number, incorrect format, or use in an inappropriate context.

Resolution:

  • Identify the data element (DE) flagged in the rejection message.
  • Verify the EORI or VAT number against official records (HMRC, VIES, or CDS reference data).
  • Ensure the number is valid, active, and correctly formatted (no spaces or invalid characters).
  • Confirm that the number is allowed for the specific data element and declaration role.
  • Replace the number with a valid and authorised one if necessary.
  • Reprocess the declaration once the number is corrected and compliance is confirmed.

Description:
License Error: License has expired; or License ID cannot be recognised; or License ID does not belong to the party on the declaration; or License declared has insufficient balance remaining; or License does not apply to the goods or country declared.

Explanation:
Licence has expired, not recognised, or does not match.

You declared a licence number that is failing validation for one of these reasons:

Expiry date is in the past.
Licence ID not recognised.
Licence DUCR not matching declaration DUCR.
Licence ID does not match EORI declared.
Licence declared has insufficient balance remaining.
Licence does not match country of origin specified.
Licence does not permit quantity declared.

Reason:
This error occurs when a declared licence fails CDS validation due to one or more of the following: expired licence, unrecognised licence ID, licence DUCR mismatch, EORI mismatch, insufficient balance, licence not applicable to the declared goods or country, or quantity not permitted. Any of these issues will result in declaration rejection.

Resolution:

  • Identify the licence-related data element (DE) flagged in the rejection message.
  • Verify the licence is valid, recognised, and not expired.
  • Confirm the licence DUCR matches the declaration DUCR, if applicable.
  • Ensure the declared EORI corresponds to the licence EORI.
  • Check that the licence has sufficient balance for the declared quantity.
  • Confirm the licence applies to the declared goods and country of origin.
  • Amend or replace the licence in the declaration with correct and valid details.
  • Reprocess the declaration after all licence validation issues have been corrected.

Description:
Authorisation Error: Authorisation has expired or Authorisation reference number provided is not recognised.

Explanation:
Authorisation number not accepted.

You declared an authorisation that has expired; or the reference number does not belong to the party on the declaration; or the reference number provided is not recognised.

Reason:
This error occurs when a declared authorisation fails CDS validation due to one or more of the following: expired authorisation, reference number not belonging to the declared party, or unrecognised reference number. Any of these issues will result in declaration rejection.

Resolution:

  • Identify the authorisation-related data element (DE) flagged in the rejection message.
  • Verify the authorisation reference number is valid and correctly entered.
  • Check that the authorisation has not expired and is still active.
  • Ensure the authorisation is linked to the EORI declared on the submission.
  • Replace any expired, incorrect, or unrecognised authorisation with a valid one.
  • Reprocess the declaration after all authorisation validation issues have been corrected.

Description:
Authorisation Error: provided VAT number is not a valid destination for VAT transfer.

Explanation:
Authorisation Error:

VAT number is not a valid destination for VAT transfer.

Reason:
This error occurs when the VAT number declared as the destination for VAT transfer is invalid, not authorised, or not permitted under CDS rules for the specific data element.

Resolution:

  • Identify the data element (DE) where the VAT number has been declared.
  • Verify that the VAT number is valid, active, and correctly formatted.
  • Confirm the VAT number is authorised and eligible as a destination for VAT transfer under CDS rules.
  • Ensure the VAT number belongs to the correct party and is permitted for the declaration type.
  • Replace any invalid or unauthorised VAT number with a valid one.
  • Reprocess the declaration after all VAT transfer validation issues have been corrected.

Description:
Sequence Error: A Goods Arrival Notification must follow a pre-lodged declaration.

Explanation:
Goods arrival notification required.

A goods arrival notification must follow a pre-lodged declaration.

Reason:
A Goods Arrival Notification must be submitted following a valid pre-lodged declaration. The notification may be missing, incorrectly linked, or submitted out of sequence.

Resolution

  • Confirm the original declaration was submitted as a pre-lodged declaration.
  • Ensure the Goods Arrival Notification is correctly linked to the relevant pre-lodged declaration reference.
  • Verify the submission sequence so the arrival notification follows the pre-lodged declaration.
  • Check compliance with CDS timing and sequencing rules.
  • Reprocess the declaration after all sequence issues have been corrected.

Description:
Sequence Error: AdditionalMessage.declarationReference does not refer to an existing declaration or the existing declaration is not in a permissible state to process the request.

Explanation:
Declaration status does not allow request.

The request to arrive, amend or cancel declaration is invalid because the declaration cannot be found or is in a state that will not allow the requested action.

Reason:
The requested action (arrival, amendment, or cancellation) cannot be processed because the referenced declaration either does not exist or is in a status that does not permit the requested operation.

Resolution

  • Verify that the declaration reference provided in the request exists in CDS.
  • Check the current status of the declaration to confirm whether it allows the requested action.
  • Ensure that the arrival, amendment, or cancellation is permitted for the declaration’s current status.
  • Correct the declaration reference if incorrect, or wait until the declaration reaches a permissible state.
  • Reprocess the request once the declaration is in an appropriate status.

Description:
Date Error: The acceptance date must not be in the future and must not be more than 180 days in the past.

Explanation:
Supplementary declaration is too late or predates acceptance.

The date when goods were accepted for the simplified declaration or EIDR must not be
more than 365 days in the past (or 200 days for a type Q declaration) and also cannot be
in the future (cannot be before the goods are accepted).

Reason:
The acceptance date for the simplified declaration or EIDR is invalid because it is either in the future or exceeds the permitted historical limit. The date must not be more than 365 days in the past (or 200 days for a Type Q declaration) and must not be a future date.

Resolution

  • Review the acceptance date entered on the declaration.
  • Confirm the acceptance date is not set in the future.
  • Ensure the date does not exceed the allowed historical limit (365 days, or 200 days for Type Q declarations).
  • Correct the acceptance date if it falls outside the permitted range.
  • Reprocess the declaration once the acceptance date is valid.

Description:
Relation Error: The Good Item Number (D.E. 1/6) is larger than the total number of goods items on the declaration.

Explanation:
Number of items error.

The goods item number declared is larger than the total number of goods items on the declaration.

Reason:
The declared Goods Item Number (D.E. 1/6) exceeds the total number of goods items specified on the declaration, resulting in an invalid item reference.

Resolution

  • Verify the total number of goods items declared.
  • Review the Goods Item Number assigned to each item.
  • Correct any item numbers that exceed the declared total.
  • Ensure the goods item numbering sequence is consistent and sequential.
  • Reprocess the declaration after correcting the item numbers.

Description:
Uniqueness Error: The value declared should be unique.

Explanation:
Uniqueness Error:

You have declared a value and repeated it, when that is not allowed.

Check the entries for these data elements:
1/11 – additional procedure code can only be used once on each item.
1/6 – item number cannot be repeated on the declaration.
2/3 – ARC number declared with document code C651 can only be used on one declaration.
4/9 – addition or deduction code can only be used once at header level or once with each item.
2/3 – licence ID cannot be repeated on the same item.

Reason:
A data element value has been declared more than once where uniqueness is required. Certain elements must contain unique values and cannot be repeated within the same declaration or goods item. This includes, but is not limited to, Additional Procedure Codes (DE 1/11), Goods Item Numbers (DE 1/6), ARC numbers with Document Code C651 (DE 2/3), Addition/Deduction Codes (DE 4/9), and Licence IDs on the same goods item.

Resolution

  • Review the declaration to identify duplicate data element values.
  • Confirm which elements require uniqueness according to CDS rules.
  • Remove or correct any repeated values to ensure each data element is declared only once where required.
  • Ensure all values subject to uniqueness rules are unique at the header or goods item level.
  • Reprocess the declaration after correcting all duplicates.

Description:
Uniqueness Error: The same data element cannot be amended more than once in the same request.

Explanation:
Field has been amended more than once.

On amendments the same data element can only be amended once per amendment submission.

Reason:
The same data element has been amended more than once within a single amendment request. Under CDS rules, each data element may only be amended once per amendment submission.

Resolution

  • Review the amendment request to identify data elements amended multiple times.
  • Remove any duplicate amendments for the same data element.
  • Retain only one valid amendment per affected data element.
  • Re-validate the amendment submission to ensure compliance with CDS rules.
  • Reprocess the amendment request after correcting all duplicates.

Description:
Sequence Error: Goods Arrival Notification must be submitted within 30 days.

Explanation:
Arrival notification is too late.

Goods arrival notification has been submitted 30 or more days after the date the declaration was originally submitted and received.

Reason:
The Goods Arrival Notification was submitted 30 days or more after the original declaration submission date. CDS rules require arrival notifications to be submitted within 30 days of the declaration being received.

Resolution

  • Verify the original declaration submission and acceptance date.
  • Review the submission date of the Goods Arrival Notification.
  • Ensure the arrival notification is submitted within the 30-day timeframe.
  • If the notification exceeds the allowed period, follow the appropriate CDS corrective process.
  • Reprocess the Goods Arrival Notification once all timing issues are corrected.

Description:
Relation Error: Submission channel of amendment must be the same as the original declaration.

Explanation:
Amendment request is invalid.

The amendment must be submitted using the same submission channel as the original declaration.

Reason:
The amendment request is invalid because it was not submitted through the same channel as the original declaration. CDS requires that amendments be submitted via the same channel to maintain consistency.

Resolution:

  • Identify the submission channel used for the original declaration.
  • Confirm that all affected data elements comply with CDS amendment rules.
  • Reprocess the amendment using the same submission channel as the original declaration.
  • Validate the amendment to ensure channel consistency and data compliance.
  • Reprocess the amendment.

Description:
Sequence Error: A new request cannot be submitted until a response is received to your previous request.

Explanation:
Request not accepted.

There is an outstanding cancellation or amendment request. A new request cannot be submitted until a response is received to your previous request.

Reason:
A new request cannot be submitted because there is an outstanding amendment or cancellation request that has not yet received a response.

Resolution:

  • Check for any pending amendment or cancellation requests.
  • Wait for CDS to respond to the previous request.
  • Ensure all data elements in the new request are correct.
  • Reprocess the new request once the previous request has been completed and permitted.

Description:
Relation Error: elements must be identical within the Goods Item.

Explanation:
Relation Error:

Different quota order numbers cannot be declared on the same item. Note that declaration will be rejected if there is more than one quota order number in data element 8/1 for an item.

Reason:
Different quota order numbers cannot be declared within the same goods item (DE 8/1). CDS will reject the declaration if more than one quota order number is present for an item.

Resolution:

  • Review DE 8/1 entries for each goods item.
  • Ensure only one quota order number is declared per item.
  • Remove any duplicate or conflicting quota order numbers.
  • Validate the consistency of all goods item entries.
  • Reprocess the declaration once corrections are applied.

Description:
External Validation MUCR result: validation errors encountered.

Explanation:
MUCR reference is invalid.

Reason:
The MUCR reference provided is invalid or incorrectly formatted, causing CDS validation to fail.

Resolution:

  • Verify the MUCR reference against CDS or the relevant authority.
  • Correct any invalid or incorrectly formatted MUCR in the declaration.
  • Validate and reprocess the declaration once the MUCR is correct.

Description:
Process Error: Goods Arrival Notification was not received within 30 days of the pre-lodged declaration.

Explanation:
Goods arrival notification has not been submitted within 30 days from the date the declaration was originally received. The declaration must now be resubmitted to CDS as either arrived (where permitted) or pre-lodged and then arrived.

Reason:
Goods Arrival Notification was not submitted within 30 days of the pre-lodged declaration, causing the declaration to be out of sequence.

Resolution:

  • Verify the original submission date of the pre-lodged declaration.
  • Confirm that the Goods Arrival Notification was not submitted within the required 30-day timeframe.
  • Validate all relevant data elements for compliance.
  • Reprocess the declaration following the correct process (either as arrived or pre-lodged then arrived, as permitted).

Description:
A valid Requested Procedure (D.E. 1/10) has not been provided or acceptance date is not valid. No further validation has been carried out.

Explanation:
Procedure code is missing or invalid.

Declaration must include at least one item and every item must include a valid procedure code.

Reason:
Procedure code is missing or invalid. Each goods item must include a valid Requested Procedure (D.E. 1/10), and the acceptance date must be correct.

Resolution:

  • Check all goods items for the Requested Procedure (D.E. 1/10).
  • Enter valid procedure codes for each item.
  • Verify that the acceptance date is within permitted limits.
  • Validate all data elements for completeness and compliance.
  • Reprocess the declaration once all corrections are applied.

Description:
A valid Declaration Type (D.E. 1/2) has not been provided or acceptance date is not valid. No further validation has been carried out.

Explanation:
No valid declaration type.

Enter the declaration type – standard, simplified (regular use), simplified (occasional use), supplementary or clearance, and prelodged or arrived. See data element 1/2 for the correct codes.

Reason:
No valid Declaration Type (D.E. 1/2) provided. Each declaration must specify a correct type—standard, simplified (regular or occasional use), supplementary, clearance, pre-lodged, or arrived—and the acceptance date must be valid.

Resolution:

  • Verify the Declaration Type entered in D.E. 1/2.
  • Select the correct type according to the declaration’s purpose.
  • Check that the acceptance date is within permitted limits.
  • Validate all data elements for compliance.
  • Reprocess the declaration once all corrections are applied.

Description:
Relation Error: the combination of elements is not allowed.

Explanation:
The combination of 2 values you entered is not allowed or requires another value entered.
For example:
A document code has an incompatible document status.
or
You have declared a code/codes which require that another code is then entered but is missing, such as an additional procedure code required for another additional procedure code to be used.
or
You cannot enter the customs procedure using ABDIN for Authorisation by Declaration (ABD).

Reason:
The combination of data elements declared is invalid. Certain codes require other associated codes, or some values are incompatible with each other (e.g., a document code with an incompatible document status, or use of ABDIN for Authorisation by Declaration without required elements).

Resolution:

  • Identify the conflicting data elements in the declaration.
  • Review CDS rules to confirm permitted combinations.
  • Correct invalid values or add any missing required data elements.
  • Validate that all data element combinations comply with CDS rules.
  • Reprocess the declaration once all corrections are applied.

Description:
Relation Error: The invoice currency must be the same for every goods item on the declaration.

Explanation:
Invoice currency for all items must be the same.

See data element 4/14 for the requirement.

Reason:
Invoice currency must be consistent across all goods items. Different currencies declared within the same declaration are not permitted (DE 4/14).

Resolution:

  • Review DE 4/14 for all goods items to identify the declared invoice currency.
  • Ensure all items use the same currency.
  • Correct any discrepancies in currency entries.
  • Validate that the declaration complies with CDS currency rules.
  • Reprocess the declaration once all items have a consistent currency.

Description:
Relation Error: When the packaging quantity is zero, then there must be another goods item with the same marks and numbers having a quantity greater than zero.

Explanation:
Number of packages error.

Packaging quantity cannot be zero for all packages for combined packaging.

Reason:
Packaging quantity cannot be zero for all goods items sharing the same marks and numbers. At least one item must have a positive quantity for combined packaging.

Resolution:

  • Identify goods items with zero packaging quantity.
  • Ensure at least one item with the same marks and numbers has a quantity greater than zero.
  • Correct packaging quantity entries where required.
  • Validate consistency of combined packaging across affected items.
  • Reprocess the declaration once all packaging quantities are compliant.

Description:
External Validation DUCR result: validation errors encountered.

Explanation:
DUCR reference is a duplication or is invalid.

Reason:
DUCR reference is a duplication or is invalid.

Resolution:

  • Check the DUCR used in the declaration.
  • Verify that it is unique and valid in CDS.
  • Correct or replace duplicate/invalid DUCR.
  • Validate all related data elements.
  • Reprocess the declaration.

Description:
This element or value is not allowed in combination with the declared element(s) or value(s).

Explanation:
Either:
1) The way the declaration has been completed requires specific DEs to also be completed with certain values. For example, required DE has not been completed or not completed correctly, or;
2) The way the declaration has been completed is not permitted. For example, the combination of DEs or their content is not allowed.

Reason:
The declared element(s) or value(s) are not permitted in combination with the specified element(s) or value(s).

Resolution:

  • Identify the DEs causing the invalid combination.
  • Review CDS rules for required DE combinations.
  • Complete any missing DEs or correct incorrect values.
  • Validate that all combinations comply with CDS rules.
  • Reprocess the declaration.

Description:
These elements or values are not allowed in combination with the declared element(s) or value(s).

Explanation:
Either a DE is not permitted to be completed on a declaration, has been completed incorrectly, or the combination of declared elements required has not been satisfied.
For example:
DE 8/1 Quota has been completed on a declaration where NIDOM and NIQUO are present in DE 2/2, or;
DE 3/40 has been completed at header on a H8 declaration, but either APCs ‘A04’ or ‘1VW’ and/or AI Statement ‘PVA01’ are missing.

Reason:
A data element is not permitted, completed incorrectly, or required combinations are missing (e.g., DE 8/1 Quota with NIDOM/NIQUO in DE 2/2).

Resolution:

  • Identify all DEs causing invalid combinations and review them against CDS rules.
  • Correct any DEs that are not permitted, completed incorrectly, or missing required values.
  • Add any mandatory elements or codes needed to satisfy CDS combination requirements.
  • Validate the declaration to ensure all element combinations are compliant.
  • Reprocess the declaration once all issues are resolved.

Description:
This combination of elements mandates the declaration of a Document Identifier.

Explanation:
A document code identifier is required for a specific doc code entered in DE 2/3.

Reason:
A document code identifier is required for a specific document code in DE 2/3.

Resolution:

  • Identify the document code in DE 2/3 that mandates a document identifier.
  • Enter the required document identifier for that code.
  • Validate all related data elements to ensure CDS compliance.
  • Reprocess the declaration once the document identifier is correctly included.

Description:
Declaration invalidation is already being processed at the Office of Exit. Please wait for further update.

Explanation:
Declaration invalidation is already being processed at the Office of Exit. Please wait for further update.

Reason:
Declaration invalidation is already being processed at the Office of Exit.

Resolution:

  • Confirm that the invalidation request has been submitted.
  • Wait for CDS to complete processing at the Office of Exit.
  • Avoid submitting duplicate invalidation requests.
  • Monitor status updates and take further action once invalidation is complete.
  • Reprocess any follow-up actions after confirmation of completion.

Description:
Relation Error: The value supplied in Data Element 1 mandates the completion of Data Element 2.

Explanation:
A required field is missing a value or is invalid.

For example, you have entered a value that requires another field to be completed, or makes another field or code entered invalid.

Reason:
A value entered in one data element requires another data element to be completed, and the dependent field is missing or incomplete.

Resolution:

  • Identify all dependent data elements triggered by the value in DE 1.
  • Complete the required DE(s) with valid values according to CDS specifications.
  • Verify that all related fields are accurate and complete.
  • Validate the declaration to ensure mandatory dependencies are satisfied.
  • Reprocess the declaration once all required data elements are correctly entered.

Description:
Relation Error: Data Element must be supplied at either header or item level and cannot be declared at both levels.

Explanation:
A field has been completed at header and item level.

Check the data element completion guide for exports from the CDS Tariff. This tells you the exact requirements for each field. In particular see the data element completion guide for data elements 3/9, 5/8, 5/14, 7/10 and 8/5.

Reason:
A data element has been completed at both header and item level; only one level is permitted (e.g., DEs 3/9, 5/8, 5/14, 7/10, 8/5).

Resolution:

  • Identify any data elements declared at both header and item level.
  • Determine the correct level for each affected DE according to the CDS Tariff completion guide.
  • Remove or adjust entries at the incorrect level.
  • Validate the declaration to ensure all DEs are correctly placed.
  • Reprocess the declaration once compliance is confirmed.

Description:
Relation Error: Either Data Element 1 or Data Element 2 must be supplied, but not both.

Explanation:
Relation Error:

This could be an unacceptable combination of values at header and item level, for example gross weight has been declared at both header and item level.

Or EORI as well as name and address has been declared for consignee, consignor or buyer.

Reason:
An unacceptable combination of values at header and item level (e.g., gross weight declared at both levels, or both EORI and name/address for consignee/consignor/buyer).

Resolution:

  • Identify the conflicting DEs.
  • Determine the correct DE to declare according to CDS rules.
  • Remove the incorrectly supplied DE.
  • Validate the declaration for correct DE usage.
  • Reprocess the declaration once corrected.

Description:
Relation Error: Data Element must be supplied at header or item level.

Explanation:
Relation Error:

A value is missing or has been entered at the wrong level.

Check these data elements:

2/1, (31 or 3/2), and 8/5 must be declared at least once at either header or item level.
7/10 must be declared at least once at header or item level if 7/2 is coded 1.
3/15 or 3/16 must be declared at header level.

Reason:
A data element is missing or declared at the incorrect level; only header or item level is permitted (e.g., DEs 2/1, 3/1, 3/2, 8/5, 7/10, 3/15, 3/16).

Resolution:

  • Identify DEs with missing or incorrectly positioned values.
  • Check CDS Tariff guidance for the correct header/item level.
  • Correct the DE placement.
  • Validate all DEs for compliance.
  • Reprocess the declaration.

Description:
Relation Error: Because Data Element 1 is not supplied, Data Element 2 is mandatory.

Explanation:
Data elements are missing and one or the other is required.

Check the data element completion guide for the CDS Tariff, and declare one or the other but not both. For example, exporter, consignor and carrier, complete either an EORI or name and address. See Tariff for specific requirements.

Reason:
A mandatory data element has not been declared where an either/or rule applies; one qualifying element must be completed (e.g., EORI or name and address for exporter, consignor, or carrier), but not both.

Resolution:

  • Identify the related data elements subject to the either/or requirement.
  • Refer to the CDS data element completion rules to determine which element must be declared.
  • Complete the required data element and ensure the alternative is not populated.
  • Validate the declaration for compliance.
  • Reprocess the declaration.

Description:
Relation Error: Data Element 2 must not be supplied with this value in Data Element 1.

Explanation:
Relation Error:

If one of the fields is completed the other should not have a value and should therefore be removed. For example, a document code and document status have been entered but the status is not required for this code. This can also indicate that a data element has been declared but is not permitted on this type of declaration.

Reason:
A dependent data element has been declared where it is not permitted for the value used in another data element, or the data element is not allowed for the declaration type (e.g. a document status provided for a document code that does not require or allow it).

Resolution:

  • Identify the conflicting data elements (DE 1 and DE 2).
  • Confirm, using CDS Tariff rules, whether DE 2 is permitted for the value declared in DE 1 and for the declaration type.
  • Remove or correct the value in DE 2 where it is not allowed.
  • Validate that the remaining data complies with CDS rules.
  • Reprocess the declaration.

Description:
Relation Error: A valid value must be supplied in Data Element 2 as Data Element 1 is present.

Explanation:
Relation Error: affecting one or more additional completion requirements.

For example, the completion of one DE with a certain value/code requires another value/code to be entered in the same DE or a different DE (such as not entering 00100 in DE 2/2 when ABDIN is entered in DE 2/2 etc),
or;
the DE itself has not been fully completed/populated as required (such as an address not fully completed when a name is provided in DE 7/14 etc).
or;
the DE has been completed incorrectly, for example DE 4/4 measurement units KTC or CTG cannot have zero values.

Reason:
A mandatory dependent data element has not been correctly completed where its completion is required by the presence or value of another data element.

Resolution:

  • Identify the triggering data element (DE 1) and its dependent data element (DE 2).
  • Confirm, using CDS Tariff rules, the required value or completion conditions for DE 2.
  • Enter a valid and complete value in DE 2 and ensure any related fields are also correctly populated.
  • Validate the declaration for CDS compliance.
  • Reprocess the declaration.

Description:
Relation Error: As no Deferment Account Number is provided in D.E. 2/6, an immediate Method of Payment must be offered in D.E. 4/8.

Explanation:
Relation Error: As no Deferment Account Number is provided in D.E. 2/6, an immediate Method of Payment must be offered in D.E. 4/8.

Reason:
When no deferment account number is declared, an immediate payment method must be provided in DE 4/8.

Resolution:

  • Confirm whether a valid Deferment Account Number is present in DE 2/6.
  • Where no deferment account is declared, specify a valid immediate Method of Payment in DE 4/8.
  • Ensure the payment method complies with CDS payment rules and is correctly formatted.
  • Validate payment-related data elements for consistency.
  • Reprocess the declaration.

Description:
Relation Error: Data Element 2 must not be supplied with Data Element 1.

Explanation:
Relation Error: Two values you declared are incompatible.
For example:
A data element is declared at both header and item levels but only one level is permissible;
You have entered a MUCR in DE 2/1 for a GVMS location code in DE 5/23.

Reason:
Two data elements have been declared together where CDS rules require mutual exclusivity. This commonly occurs when a data element is declared at an invalid level (header and item) or where incompatible values are used together (for example, a MUCR in DE 2/1 conflicting with a GVMS location code in DE 5/23).

Resolution:

  • Identify the conflicting Data Elements (DE 1 and DE 2) within the declaration.
  • Determine which data element is permitted based on CDS level and compatibility rules.
  • Remove or correct the data element that is not allowed in combination.
  • Verify the remaining data element is correctly declared and compliant.
  • Reprocess the declaration.

Description:
Relation Error: Combination of Addition / Deduction codes (DE 4/9) is not allowed.

Explanation:
Relation Error:

You have used a mix of addition or deduction codes for an item that is not permitted. Certain addition/deduction codes cannot be declared together.

Additions and deductions should only be declared at header level where they apply to all good items on the customs declaration.
Each addition or deduction code can only be declared once at header level. The same addition or deduction code cannot then be declared at item level as well.
If a specific addition or deduction is being declared at item level, that addition or deduction may only be declared once per item.

Reason:
Addition/deduction codes cannot be mixed for an item; each code can only be declared once at header level or per item if applicable.

Resolution:

  • Review all Data Element 4/9 entries at both header and goods item level.
  • Identify any mixed or conflicting addition and deduction codes.
  • Ensure each addition or deduction code is declared only once at the appropriate level (header or item).
  • Validate the declaration against CDS rules for addition and deduction code usage.
  • Reprocess the declaration once corrections are complete.

Description:
Relation Error: Importer (D.E. 3/16) & Exporter (D.E. 3/2) must not be the same party.

Explanation:
Relation Error: Importer (D.E. 3/16) & Exporter (D.E. 3/2) must not be the same party.

Reason:
The same party has been declared as both importer and exporter, each role must be assigned to a distinct entity.

Resolution:

  • Verify the EORI numbers declared in DE 3/16 and DE 3/2.
  • Correct either DE 3/16 or DE 3/2 to reflect the correct party.
  • Validate the declaration for compliance.
  • Reprocess the declaration once corrected.

Description:
Relation Error: The currency declared in DE 4/11 must be the same as the currency declared in DE 4/14.

Explanation:
Relation Error:

The currency declared for the total amount invoiced does not match the currency declared at item price amount (data element 4/14).

Reason:
The currency declared for the total invoiced amount does not match the currency declared for individual item prices.

Resolution:

  • Review DE 4/11 and DE 4/14 for all goods items.
  • Ensure DE 4/11 and DE 4/14 use the same currency code and correct any inconsistencies currency entries.
  • Validate the declaration for currency consistency.
  • Reprocess the declaration once corrected.

Description:
Relation Error: For Country of Preferential Origin DE 5/16 where mandated, only provide one country or country group, not both.

Explanation:
Relation Error:

You have provided both a country and country group for mandatory data element Preferential Origin.

Where the proof of origin document refers to a group of countries, enter the group of countries by using the relevant Union codes in accordance with the codes listed in Appendix 13: Country Codes.

Where data element 5/16 is completed using a preference group code, data element 5/15 must be completed with the specific country of origin for the goods.

Reason:
Both a country and a country group have been provided for the mandatory Preferential Origin data element; only one is permitted.

Resolution:

  • Identify DE 5/16 and DE 5/15 entries.
  • Remove the conflicting value so only a country or country group is declared.
  • Ensure the declared code type aligns with CDS rules.
  • Validate against CDS Tariff Appendix 13.
  • Reprocess the declaration.

Description:
Relation Error: Either Consignee Name (DE 3/9) or Consignee Identification Number (DE 3/10) must be supplied, but not both.

Explanation:
Consignee Details:

You have provided both consignee name and consignee EORI. Only declare either the EORI or the full name and address of consignee not both. EORI should be declared when known.

Reason:
Both Consignee Name and Consignee Identification Number have been provided; only one is permitted.

Resolution:

  • Check DE 3/9 and DE 3/10 entries.
  • Remove the incorrectly supplied value so only one method of identification is declared.
  • Validate consistency across the declaration.
  • Reprocess the declaration.

Description:
Relation Error: Either Carrier Name (DE 3/31) or Carrier Identification Number (DE 3/32) must be supplied, but not both.

Explanation:
Carrier Details:

You have provided both Carrier name and Carrier EORI. Only declare either the EORI or the full name and address of carrier not both. EORI should be declared when known.

Reason:
Both Carrier Name and Carrier Identification Number have been provided; only one is permitted.

Resolution:

  • Verify DE 3/31 and DE 3/32.
  • Remove the incorrectly supplied value so only one identification method is declared.
  • Validate declaration for consistency.
  • Ensure correct carrier details are associated with the shipment.
  • Reprocess the declaration.

Description:
Relation Error: VAT Declaring Party Identification (DE 3/40), where mandated, must be supplied at either header or item.

Explanation:
Additional fiscal party.

You have declared your additional fiscal party VAT number at both header and item level. It should only be declared at either item or header level. Or you have declared procedure code 1042 and not declared an additional fiscal references ID.

Reason:
DE 3/40 has been declared at both header and item levels; only one level is permitted.

Resolution:

  • Check DE 3/40 entries at header and item levels.
  • Retain the declaration at the correct level only.
  • Add any required additional fiscal reference ID if mandated by procedure code.
  • Validate the declaration against CDS rules.
  • Reprocess the declaration.

Description:
Relation Error: Either Agent Name (DE 3/19) or Agent Identification Number (DE 3/20) must be supplied.

Explanation:
Representative details missing.

To correct this error, complete the EORI in data element 3/19, or the name and address in 3/20, even if they are your own details as the declarant and you are the direct representative.

Reason:
Both DE 3/19 and DE 3/20 are incomplete; only one must be supplied.

Resolution:

  • Check DE 3/19 and DE 3/20 entries.
  • Declare either the agent EORI (DE 3/19) or full name/address (DE 3/20).
  • Validate the agent information.
  • Reprocess the declaration.

Description:
Relation Error: Consignee Party Name (DE3/9) must be supplied at either header or item level.

Explanation:
Consignee party details.

Consignee party name and address must be declared at either header or item level on a C21e unless the procedure code is 0019.

Reason:
Consignee name and address must be declared at header or item level on a C21e unless procedure code 0019 is used.

Resolution:

  • Identify where DE 3/9 is missing.
  • Declare the consignee name and address at the correct level.
  • Verify the procedure code applicability.
  • Validate completeness of the declaration.
  • Reprocess the declaration.

Description:
Relation Error: Carrier Name (DE 3/31) or Carrier Identification Number (DE 3/32) must be supplied for the 17X Additional Procedure Code at either header or item level.

Explanation:
Carrier EORI.

When declaring additional procedure Code 17X on a C21e clearance request, the carrier name and address or the carrier EORI must be declared at header level.

Reason:
For Additional Procedure Code 17X on a C21e clearance request, either the carrier name and address or carrier EORI must be declared at header level.

Resolution:

  • Verify the declaration includes Additional Procedure Code 17X.
  • Declare either carrier name/address or carrier EORI at header level.
  • Remove conflicting entries at item level.
  • Validate all related data elements.
  • Reprocess the declaration.

Description:
Relation Error: Consignee (D.E. 3/10) & Exporter (D.E. 3/1) must not be the same Party.

Explanation:
Relation Error:

Consignee (receiver of goods) and exporter cannot have the same EORI number.

Reason:
Consignee and Exporter cannot have the same EORI number.

Resolution:

  • Verify the EORI numbers for consignee and exporter.
  • Correct either DE 3/10 or DE 3/1 to ensure distinct parties.
  • Validate all related data elements.
  • Reprocess the declaration.

Description:
Relation Error: Seller (DE 3/25) & Exporter (DE 3/1) must not be the same Party.

Explanation:
Relation Error:

You have declared the same party for seller (data element 3/25) and exporter (data element 3/1).

The seller details are only required where the seller is a different party to the exporter.

Where the seller is a different party to the exporter and holds a recognised EORI number, enter the seller’s EORI number in data element 3/25.

Reason:
The same party has been provided for Seller and Exporter. Seller details are only required if different from the Exporter. If different, enter seller EORI in DE 3/25.

Resolution:

  • Verify DE 3/25 and DE 3/1 entries.
  • Correct DE 3/25 if the seller is a different party.
  • Ensure EORI numbers are correctly declared.
  • Reprocess the declaration.

Description:
Relation Error: Additional Procedure Combination (DE 1/11) can only be used when Country of Dispatch/Export (DE 5/14) Exportation Country is a Third Country.

Explanation:
Relation Error:

You have used an additional procedure combination (data element 1/11) incorrectly. Additional procedure codes 1IL and 1LV can only be used for goods dispatched/exported from a third country.

Reason:
Incorrect use of additional procedure codes (DE 1/11) such as 1IL and 1LV can only be used for goods dispatched/exported from a third country.

Resolution:

  • Verify DE 1/11 and DE 5/14 values.
  • Ensure additional procedure codes 1IL or 1LV are only applied for third-country exports.
  • Correct any invalid combinations.
  • Reprocess the declaration.

Description:
Relation Error: Provided Authorisation Type (D.E. 3/39) requires specific document in Additional Documents.

Explanation:
Authorisation Error:

When declaring any of the authorisation types CGU, EUS, IPO or TEA in data element 3/39, it is necessary to declare document code C505 (Customs Comprehensive Guarantee) in DE 2/3. It may be necessary to declare C505 together with a waiver status code such as XW.

Reason:
Authorisation types CGU, EUS, IPO, or TEA (DE 3/39) mandate the declaration of document code C505 (Customs Comprehensive Guarantee) in DE 2/3 and may require a waiver status code such as XW.

Resolution:

  • Verify DE 3/39 for the authorisation type.
  • Include the required document code C505 in DE 2/3.
  • Add any necessary waiver status codes.
  • Reprocess the declaration.

Description:
Relation Error: Combination Additional Procedure Code (D.E. 1/11) and Country of Destination in DE 5/8 is not allowed.

Explanation:
Relation Error:

When declaring Additional Procedure Code F75, the destination country must be a Special Fiscal Territory or other territory with which the EU has formed a Customs Union.

Reason:
When declaring Additional Procedure Code F75, the destination country must be a Special Fiscal Territory or another territory with which the EU has a Customs Union.

Resolution:

  • Check DE 1/11 and DE 5/8 values.
  • Ensure F75 is used only with approved destination countries.
  • Correct any invalid destination entries.
  • Reprocess the declaration.

Description:
Relation Error: Combination of Means of Transport (DE 7/4) and Delivery Terms in DE 4/1 is not allowed.

Explanation:
Relation Error:

You have declared a means of transport code (data element 7/4) that is not compatible with the delivery terms (data element 4/1).

Reason:
The means of transport declared (DE 7/4) is not compatible with the delivery terms specified (DE 4/1).

Resolution:

  • Review DE 7/4 and DE 4/1 entries.
  • Correct either the means of transport or delivery terms to a valid combination.
  • Validate the declaration for compatibility.
  • Reprocess the declaration.

Description:
Relation Error: Combination of elements that make up the Goods Location code (5/23) is invalid.

Explanation:
Goods location code not recognised.

Check the codes listed in Appendix 16 and in the supplements to Tariff, where new goods location codes may be listed.

Reason:
The goods location code declared (DE 5/23) is not recognised or invalid.

Resolution:

  • Verify the DE 5/23 entry.
  • Replace with a valid goods location code from the appendix 16 and Tariff supplements.
  • Correct any invalid combinations.
  • Validate the declaration.
  • Reprocess the declaration.

Description:
Relation Error: Combination of Delivery terms (DE 4/1) and Addition/Deduction code (DE 4/9) is not allowed.

Explanation:
Relation Error:

You have declared Delivery Terms (data element 4/1) that are not compatible with the Addition/Deduction code (data element 4/9).

The combination of Delivery Terms and Addition/Deduction Code must be compatible.

Reason:
Delivery Terms (DE 4/1) are incompatible with Addition/Deduction code (DE 4/9); combination must be valid.

Resolution:

  • Review DE 4/1 and DE 4/9 and correct any incompatible combinations.
  • Ensure addition/deduction codes are declared at the correct level (header or item).
  • Validate and reprocess the declaration.

Description:
Relation Error: Declared Tax Type (DE4/3) is not allowed in combination with the Additional Procedure.

Explanation:
Relation Error:

You have declared an additional procedure code that is not permitted to be combined with the declared tax type (data element 4/3). For example, additional procedure codes 32D, 31D, 1IL and 1LV cannot be used with an excise tax type.

Reason:
Additional procedure code cannot be combined with the declared Tax Type (DE 4/3); certain combinations (e.g., 32D, 31D, 1IL, 1LV with excise tax) are not permitted.

Resolution:

  • Review DE 4/3 and the Additional Procedure code; remove any incompatible combinations.
  • Validate and reprocess the declaration.

Description:
Relation Error: Deferred Payment Method in DE 4/8 is Required with the duty deferment account number provided in DE 2/6.

Explanation:
Relation Error:

You have not declared the deferred payment method which is required for the duty deferment account number declared.

Reason:
Deferred Payment Method (DE 4/8) is required when a duty deferment account number is provided in DE 2/6.

Resolution:

  • Verify DE 2/6 for the duty deferment account and enter the corresponding deferred payment method in DE 4/8.
  • Validate and reprocess the declaration.

Description:
Relation Error: Valid delivery destination is required in D.E.5/8 for a CO declaration.

Explanation:
Relation Error:

When declaring Declaration Type code CO in data element 1/1, the destination country must be a Special Fiscal Territory or other territory with which the EU has formed a Customs Union.

Reason:
A valid delivery destination (DE 5/8) is required for a CO declaration; it must be a Special Fiscal Territory or an EU Customs Union territory.

Resolution:

  • Verify DE 1/1 and DE 5/8 and correct the destination to an approved country or territory.
  • Validate and reprocess the declaration.

Description:
Relation Error: Valid Import Procedure code (1/10) is required.

Explanation:
Relation Error:

For declaration type code IM, the procedure code must be a permitted import procedure code. Check Appendix 1 of the Import Tariff and the Inventory Import Tariff.

Reason:
A valid Import Procedure code (DE 1/10) is required for the declaration; the code must be permitted under the Import Tariff and Inventory Import Tariff.

Resolution:

  • Verify DE 1/10 and correct to a valid import procedure code.
  • Validate and reprocess the declaration.

Description:
Relation Error: Addition/Deduction code (DE 4/9) not allowed with the declared Additional Procedure Code (DE1/11).

Explanation:
Relation Error:

When using additional procedure code E01 (simplified procedure value) or E02 (standard import value), data element 4/9 additions and deductions, must not be declared.
See Appendix 1 for more information.

Reason:
Addition/Deduction codes (DE 4/9) cannot be used with Additional Procedure Codes E01 or E02 (DE 1/11).

Resolution:

  • Review DE 1/11 for E01/E02 and remove any DE 4/9 entries.
  • Validate and reprocess the declaration.

Description:
Relation Error: Appropriate Additional Information Code must be provided in DE2/2 with Additional Procedure Code 1CL.

Explanation:
Relation Error:

An appropriate Additional Information (AI) code is required with the additional procedure code 1CL.

Reason:
An appropriate Additional Information (DE 2/2) code is required when Additional Procedure Code 1CL (DE 1/11) is declared.

Resolution:

  • Check DE 1/11 for code 1CL and enter the corresponding AI code in DE 2/2.
  • Validate and reprocess the declaration.

Description:
Relation Error: Conditions not met for the requested simplification. Please see CDS Trade Tariff Vol.3 Appendix 4.

Explanation:
Relation Error:

When using Additional Information code 00600, data element 2/3 must not include any licence document codes, even if claiming a waiver/exemption.

Reason:
When using AI code 00600, DE 2/3 must not include licence document codes, even if claiming waiver/exemption.

Resolution:

  • Verify DE 2/2 for AI code 00600 and remove any licence codes from DE 2/3.
  • Validate and reprocess the declaration.

Description:
Obligation Error: DUCR is mandatory on an Export Declaration.

Explanation:
Obligation Error:

Declaration Unique Consignment Reference (DUCR) is mandatory at header level on an export declaration.

Reason:
Declaration Unique Consignment Reference (DUCR) is missing; it is mandatory at header level for an export declaration.

Resolution:

  • Ensure DUCR is declared at header level.
  • Validate and reprocess the declaration.

Description:
Obligation Error: When providing fixed rate of exchange rate in DE 4/15, a currency code of GBP must be supplied.

Explanation:
Total invoiced amount should be in GBP.

You declared a fixed rate of exchange meaning a contractually agreed rate of exchange was used. The invoice value (data element 4/14) on an import declaration or the total amount invoiced (data element 4/11) on an export declaration, needs to be declared in GBP, converted using the agreed rate.

Reason:
When using a fixed exchange rate (DE 4/15), the invoiced amount must be declared in GBP (DE 4/11 for export or DE 4/14 for import).

Resolution:

  • Check DE 4/15 for fixed rate.
  • Verify invoice amounts are in GBP.
  • Validate and reprocess the declaration.

Description:
Relation Error: A Quota Order number (DE8/1) cannot be provided in combination with this Preference Code (DE 4/17).

Explanation:
Relation Error:

The Preference Code declared (data element 4/17) is incompatible with claiming Quota (data element 8/1).

Reason:
The Preference Code declared (DE 4/17) is incompatible with a Quota Order number (DE 8/1).

Resolution:

  • Review DE 4/17 and DE 8/1 for incompatibility.
  • Remove or correct DE 8/1 if required.
  • Validate and reprocess the declaration.

Description:
Relation Error: The provided tax amount (DE 4/6 or DE 4/7) must always be declared with currency code GBP.

Explanation:
Relation Error:

You have declared the tax amount (data element 4/6 or 4/7) in the incorrect currency. Tax amounts should always be declared with the sterling GBP currency code.

Reason:
The tax amount (DE 4/6 or DE 4/7) has been declared in a currency other than GBP.

Resolution:

  • Check DE 4/6 and DE 4/7 for currency.
  • Correct the currency to GBP.
  • Validate and reprocess the declaration.

Description:
Relation Error: Airfreight related additions/deduction code must be provided in DE 4/9 when an airport place of loading is provided in DE 5/21.

Explanation:
Addition/Deduction code missing.

You have not provided the mandatory airfreight related addition/deduction code (data element 4/9) for the declared airport place of loading (data element 5/21).

Reason:
An airfreight-related Addition/Deduction code (DE 4/9) is missing for the declared airport place of loading (DE 5/21).

Resolution:

  • Verify DE 5/21 for airport loading.
  • Declare the corresponding DE 4/9 airfreight code.
  • Validate and reprocess the declaration.

Description:
Relation Error: Authorisation holder CGU requires a guarantee type of 0 or 1 to be provided in D.E.8/2.

Explanation:
Authorisation CGU requires a guarantee.

Holder of authorisation type CGU has been declared and so guarantee type in data element 8/2 must be 0 (Guarantee Waiver) or 1 (Comprehensive Guarantee).

Reason:
Authorisation holder of type CGU requires a guarantee type of 0 (Guarantee Waiver) or 1 (Comprehensive Guarantee) in DE 8/2.

Resolution:

  • xCheck DE 3/39 for authorisation type CGU.
  • Enter guarantee type 0 or 1 in DE 8/2.
  • Validate and reprocess the declaration.

Description:
Relation Error: Value declared must be less than 100 as DE 4/9 Additions/Deductions code is a percentage.

Explanation:
Relation Error:

The value you declared may not be less than 100%. The Additions/Deductions code is a percentage and so the value provided in data element 4/9 must be less than 100.

Reason:
The value declared in DE 4/9 (Additions/Deductions code) must be less than 100%, as it represents a percentage.

Resolution:

  • Verify the value in DE 4/9.
  • Correct any entries equal to or above 100%.
  • Validate and reprocess the declaration.

Description:
Relation Error: Declared Procedure Code (DE 1/10 and / or 1/11)  mandates the use of Additional Document (DE 2/3) 185C.

Explanation:
Relation Error:

You have not have declared document code 185C (Claim to Visiting Forces Relief for goods removed from a customs warehouse), required for the additional procedure code entered.

Reason:
The declared procedure code (DE 1/10 or 1/11) requires the additional document code 185C to be provided in DE 2/3.

Resolution:

  • Check the procedure code in DE 1/10 or DE 1/11.
  • Add the required document code 185C in DE 2/3.
  • Validate and reprocess the declaration.

Description:
Relation Error: Importer (DE 3/16) & Buyer (DE 3/27) must not be the same party.

Explanation:
Relation Error:

You have declared the same EORI for the Importer and Buyer on an import declaration.

Reason:
The same party has been declared for both Importer (DE 3/16) and Buyer (DE 3/27); each must be a distinct party.

Resolution:

  • Verify DE 3/16 and DE 3/27.
  • Correct the EORI or party details so Importer and Buyer are distinct.
  • Validate and reprocess the declaration.

Description:
Relation Error: Consignor (DE3/1) information must be supplied for the 17X Additional Procedure Code at either header or item level and cannot be declared at both levels.

Explanation:
Relation Error:

You have declared consignor details for the additional procedure code 17X at both header and item level. It should only be declared at either item or header level.

Reason:
Consignor details (DE 3/1) for Additional Procedure Code 17X have been declared at both header and item level; only one level is permitted.

Resolution:

  • Review DE 3/1 entries at header and item levels.
  • Remove the duplicate entry from the incorrect level.
  • Validate and reprocess the declaration.

Description:
Relation Error: Declared Additional Document (D.E. 2/3) is not allowed with this Procedure Code (D.E. 1/10 or D.E. 1/11).

Explanation:
Additional document not allowed or is missing.

Additional document code, for example licence, exemption or authorisation number, is not allowed or must not be declared with other data in the declaration.

Examples include C512 and C514 (SDP and EIDR authorisations) not permitted with certain procedure codes; licence document code restrictions with certain additional procedure codes, Special Procedure authorisations required with certain procedure combinations.

Reason:
The declared Additional Document (DE 2/3) is not permitted with the specified Procedure Code (DE 1/10 or DE 1/11); certain document codes (e.g., C512, C514) are restricted for some procedure codes.

Resolution:

  • Verify DE 1/10 or DE 1/11 procedure codes.
  • Remove any incompatible DE 2/3 additional document codes.
  • Validate and reprocess the declaration.

Description:
Relation Error: The appropriate authorisation has not been declared for this Declaration Type (D.E. 1/2).

Explanation:
Authorisation Error:

You may not have declared an authorisation required for this declaration type. If you have declared the correct authorisation, check the authorisation number declared on the ‘Additional documentation’ page.

For SDP declarations, you need document code C512.
For EIDR declarations, you need document code C514.
For submitting an arrived export declaration, data element 3/39 must include one of the authorisation type codes CSE or EXRR.

You may have declared an authorisation that has expired; or the reference number does not belong to the party on the declaration; or the reference number provided is not recognised.

Reason:
The required authorisation for the Declaration Type (DE 1/2) has not been declared, is expired, or the reference number is invalid or does not belong to the party on the declaration (e.g., SDP requires C512, EIDR requires C514, arrived export requires CSE/EXRR in DE 3/39).

Resolution:

  • Verify DE 1/2 declaration type.
  • Declare the correct authorisation document code in DE 2/3.
  • Check DE 3/39 for arrived export declarations.
  • Correct any expired or invalid authorisations.
  • Validate and reprocess the declaration.

Description:
Relation Error: This combination of Additional Information codes (D.E. 2/2) is not allowed.

Explanation:
There is an error with the Additional Information codes against a goods item.

Either, the AI codes declared together for one goods item are not compatible with each other, or an AI code entered for the goods item mandates another AI is present.

Reason:
The combination of Additional Information codes (DE 2/2) declared for a goods item is invalid; either the codes are incompatible or a declared code requires another AI code that is missing.

Resolution:

  • Review DE 2/2 AI codes for each goods item.
  • Remove incompatible AI code combinations and add any required dependent AI codes.
  • Validate and reprocess the declaration.

Description:
Data Error: Value must be greater than 0.

Explanation:
A value declared must be greater than 0.

Invoice value declared in data element 4/14 must be greater than 0.

Reason:
The invoice value declared in DE 4/14 must be greater than 0.

Resolution:

  • Verify DE 4/14 invoice value and correct any zero or negative entries.
  • Validate and reprocess the declaration.

Description:
DAN Error: Account number is not recognised; or Account is suspended or revoked; or Parties declared on the declaration do not have authority to use account number provided.

Explanation:
DAN Error:

The deferment account number or Guarantee reference Number you have provided:
– is not recognised or
– the account may be suspended/revoked or
– Parties declared on the declaration do not have authority to use account number provided.

Check the CDS financial dashboard/contact HMRC deferment department.

Reason:
The deferment account or guarantee reference number is either not recognised, suspended/revoked, or the parties declared do not have authority to use it.

Resolution:

  • Verify the account or guarantee reference number and confirm it is active.
  • Ensure the declared parties are authorised to use the account.
  • Correct any invalid entries, validate, and reprocess the declaration.

Description:
DUCR format not valid.

Explanation:
Declaration Unique Consignment Reference (DUCR) format is not valid.

Reason:
Declaration Unique Consignment Reference (DUCR) format is not valid.

Resolution:

  • Check the DUCR format entered.
  • Correct any formatting errors.
  • Validate and reprocess the declaration.

Description:
MUCR format not valid.

Explanation:
MUCR format is not valid.

If the MUCR was given to you, check it is in a valid format. If you created it yourself, check the guidance on the correct format (opens in new tab).

Reason:
MUCR format is invalid. Check guidance if self-created, or verify given MUCR.

Resolution:

  • Verify the MUCR format.
  • Correct any invalid characters or structure.
  • Validate and reprocess the declaration.

Description:
DUCR and MUCR formats not valid.

Explanation:
MUCR or DUCR format is not valid.

If the MUCR was given to you, check it is in a valid format. If you created it yourself, check the guidance on the correct format (opens in new tab).

If you have declared a previous declaration reference such as for an import, check the DUCR on the previous declaration.

Reason:
MUCR or DUCR format is not valid. For previous declaration references, ensure DUCR matches the previous declaration.

Resolution:

  • Review MUCR and DUCR formats.
  • Correct any invalid structures.
  • Verify previous declaration references if applicable.
  • Validate and reprocess the declaration.

Description:
Relation Error: Country of Export (DE 5/14) must be supplied at either header or item level.

Explanation:
Relation Error:

Country of export is mandatory at header or item level when declaring additional procedure code 1CD, 1CG, 2CG or 2CD.
On a C21I with procedure code 0002, 0003, 0004, 0005, 0006 or 0007.

Reason:
Country of export (DE 5/14) is mandatory at header or item level when declaring certain additional procedure codes (1CD, 1CG, 2CG, 2CD) or C21I with procedure codes 0002–0007.

Resolution:

  • Check DE 5/14 for country of export.
  • Provide it at either header or item level.
  • Validate and reprocess the declaration.

Description:
Relation Error: Provided Additional Procedure Code (DE 1/11) necessitates indirect representation (DE 3/21) for the following declaration types: C F Y J K Z.

Explanation:
Relation Error:

The additional procedure code declared requires this declaration to have indirect representation (data element 3/21).

The representative status declared in data element 3/21 would show Indirect, code ‘3’. The representative status declared in data element 3/21 indicates the relationship between the representative and the importer, not the sub-agent and any other party.

Reason:
Declared Additional Procedure Code (DE 1/11) requires indirect representation (DE 3/21) for declaration types C, F, Y, J, K, Z.

Resolution:

  • Check DE 1/11 for additional procedure code.
  • Verify DE 3/21 indicates indirect representation (‘3’) if required.
  • Correct representative status as needed.
  • Validate and reprocess the declaration.

Description:
Uniqueness Error: Only a single MUCR can be declared in DE 2/1 at Header level on an imports declaration.

Explanation:
Uniqueness Error:

You have declared more than one MUCR at header level on your import declaration.

Reason:
Only a single MUCR can be declared in DE 2/1 at header level on an import declaration.

Resolution:

  • Review DE 2/1 at header level.
  • Remove any duplicate MUCR entries.
  • Validate and reprocess the declaration.

Description:
Relation Error: Provided Additional Procedure Code (D.E. 1/11) cannot be used on a Type J/K (EIDR) declaration.

Explanation:
Additional procedure code is not allowed.

These additional procedure codes cannot be used with an EIDR C21 declaration.

1CD – Controlled drugs using Simplified Procedures.
1CG – Controlled Goods using Simplified Procedures.

Reason:
Additional Procedure Code (DE 1/11) cannot be used on a Type J/K (EIDR) declaration.

Resolution:

  • Check DE 1/11 for additional procedure codes.
  • Remove or correct codes incompatible with EIDR declarations.
  • Validate and reprocess the declaration.

Description:
Relation Error: Additional Information Code OVR01 must be provided in DE 2/2 when entering a manual tax amount in DE 4/6 or DE 4/7.

Explanation:
Relation Error:

You have not provided the Additional Information (AI) Code OVR01 required for the declared manual tax amount in DE 4/6 or DE 4/7.

Reason:
Additional Information Code OVR01 must be declared in DE 2/2 when a manual tax amount is entered in DE 4/6 or DE 4/7.

Resolution:

  • Identify DE 4/6 or DE 4/7 with manual tax amounts.
  • Enter AI code OVR01 in DE 2/2 for the same item.
  • Validate and reprocess the declaration.

Description:
Relation Error: Incompatible goods movements declared. AI codes ‘NIDOM’ and ‘NIIMP’ must not be entered together on the same declaration.

Explanation:
Relation Error:

You have declared a combination of Additional Information Codes ‘NIDOM’ and ‘NIIMP’ that are not permitted to be declared together on the same declaration.

Reason:
You have declared a combination of Additional Information Codes ‘NIDOM’ and ‘NIIMP’ that are not permitted together.

Resolution:

  • Review AI codes in DE 2/2.
  • Remove either ‘NIDOM’ or ‘NIIMP’.
  • Validate and reprocess the declaration.

Description:
Incompatible goods movements declared. AI codes ‘NIREM’ and ‘NIAID’ must not be entered together on the same goods item on a declaration.

Explanation:
DE 2/2 AI Statement Error:

The combination of NI Additional Information Codes are not permitted to be declared together on the same goods item.

Reason:
The combination of NI Additional Information Codes ‘NIREM’ and ‘NIAID’ is not allowed on the same goods item.

Resolution:

  • Check DE 2/2 for AI codes.
  • Ensure only one of ‘NIREM’ or ‘NIAID’ is declared per goods item.
  • Correct the declaration to remove any incompatible AI code combinations.
  • Confirm all AI codes comply with Northern Ireland protocol rules.
  • Validate and reprocess the declaration.

Description:
Relation Error: EU Quota order number beginning ’09’ must not be entered in DE 8/1 for any imports into the UK.

Explanation:
Relation Error:

You have entered the incorrect EU Quota order number beginning with ’09’ which is not permitted for imports into the UK.

Reason:
For Requested Procedure code 42 (DE 1/10), AI code NIIMP must also be declared.

Resolution:

  • Review DE 8/1 for quota order numbers.
  • Remove or correct any number starting with ’09’.
  • Verify the declaration reflects permitted quota numbers.
  • Validate and reprocess the declaration.

Description:
Relation Error: When declaring the Requested Procedure code 42 in DE 1/10, the Additional Information code NIIMP must be declared in DE 2/3.

Explanation:
Relation Error:

For the Requested Procedure code 42 in data element 1/10 the Additional Information code, NIIMP, must be declared in data element 2/2.

Reason:
For Requested Procedure code 42 (DE 1/10), AI code NIIMP must also be declared.

Resolution:

  • Check DE 1/10 for Requested Procedure Code 42.
  • Ensure DE 2/2 contains AI code ‘NIIMP’ for the corresponding goods item.
  • Add any missing AI codes required for the procedure.
  • Validate and reprocess the declaration.

Description:
The Requested Procedure code 42 (DE 1/10) and Additional Information code OSR42 (DE 2/2) must be entered together on the same goods item.

Explanation:
Relation Error:

You have not entered either the Requested Procedure code 42 (DE 1/10) or Additional Information code OSR42 (DE 2/2) on the same goods item.

Reason:
Requested Procedure code 42 (DE 1/10) and AI code OSR42 (DE 2/2) must be declared together on the same goods item.

Resolution:

  • Identify goods items with Requested Procedure Code 42.
  • Enter AI code ‘OSR42’ in DE 2/2 for the same goods item.
  • Verify that the procedure code and AI code combination is complete and accurate.
  • Validate and reprocess the declaration.

Description:
Relation Error: UVC01 declared on an original declaration. UVC01 can only be declared on an amendment request for a declaration.

Explanation:
Additional Information (AI) code is not allowed.

AI code UVC01 may only be used on an amendment.

Reason:
AI code ‘UVC01’ may only be used on an amendment request, not on the original declaration.

Resolution:

  • Check AI code UVC01 usage.
  • Remove from original declaration.
  • Include only in amendment requests.
  • Validate and reprocess the declaration.

Description:
Relation Error: Additional Document C506 requires deferred payment method.

Explanation:
Relation Error:

You have not provided a deferred payment method for the declared Additional Document C506.

Reason:
Additional Document C506 requires a deferred payment method to be declared.

Resolution:

  • Check DE 2/3 for Additional Document C506.
  • Ensure DE 4/8 contains a deferred payment method.
  • Validate and reprocess the declaration.

Description:
Relation Error: Additional Procedure code 000 can not be declared with any other Additional Procedure Code.

Explanation:
Relation Error:

Additional procedure code 000 can not be declared with any other additional procedure code.

Reason:
Additional Procedure Code ‘000’ cannot be declared alongside any other Additional Procedure Code.

Resolution:

  • Review DE 1/11 for additional procedure codes.
  • Ensure code 000 is declared alone.
  • Remove any conflicting codes.
  • Validate and reprocess the declaration.

Description:
Authorisation Error: Authorisation reference number does not belong to the party on the declaration.

Explanation:
An authorisation number is invalid.

An authorisation number, such as for a Special Procedure, SDP, EIDR, CCG, Customs Warehousing, national authorisation, is either not valid or is not authorised for use by the party given on the declaration.

Reason:
An authorisation number, such as for a Special Procedure, SDP, EIDR, CCG, Customs Warehousing, or national authorisation, is either invalid or not authorised for use by the declared party.

Resolution:

  • Check the authorisation number in DE 3/39.
  • Ensure it belongs to the declared party.
  • Correct the authorisation reference if necessary.
  • Validate and reprocess the declaration.

Description:
Relation Error: When a licence is declared, ID must be unique from all other additional documents (DE 2/3) in the same goods item.

Explanation:
Duplication Error:

For example:
Licence ID cannot be declared more than once on the same item in DE 2/3.

Reason:
Licence ID cannot be declared more than once on the same goods item in DE 2/3.

Resolution:

  • Review DE 2/3 for duplicate licence IDs.
  • Ensure each licence ID is unique per goods item.
  • Remove duplicates.
  • Confirm that all licence IDs are valid and correctly applied.
  • Validate and reprocess the declaration.

Description:
Additional Procedure Code (DE 1/11) 1H7 can only be used when submitting an SRDS declaration and is required to be declared on all goods items.

Explanation:
An additional procedure code is missing for an H7/SRDS declaration:

Additional Procedure Code ‘1H7’ must be present for the H7/SRDS declaration category.

Reason:
Additional Procedure Code ‘1H7’ must be present for the H7/SRDS declaration category and declared on all goods items.

Resolution:

  • Confirm the declaration type is H7/SRDS.
  • Ensure DE 1/11 includes code 1H7 for all goods items.
  • Add missing codes if required.
  • Validate and reprocess the declaration.

Description:
Relation Error: EORIs with this country code are not supported.

Explanation:
Relation Error:

The country code at the start of an EORI must be GB when declaring any of the parties Importer (DE 3/16), Exporter (DE 3/2), Declarant (DE 3/18), Representative (DE 3/20).

Reason:
The country code at the start of an EORI must be GB when declaring any of the parties: Importer (DE 3/16), Exporter (DE 3/2), Declarant (DE 3/18), Representative (DE 3/20).

Resolution:

  • Check all EORIs in the declaration.
  • Ensure the country code is GB.
  • Correct any non-GB EORI numbers.
  • Validate and reprocess the declaration.

Description:
Incompatible goods movements declared. When AI code ‘NIIMP’, ‘NIDOM’ or ‘NIEXP’ is entered at item level in D.E. 2/2, Document Code – 999L cannot be entered in D.E.2/3.

Explanation:
The Document Code 999L cannot be used for goods being imported or exported from Northern Ireland. Please use the UK/NI online tariff to identify the document codes, other than 999L, required by the measure conditions on your commodity code.

Reason:
The Document Code 999L cannot be used for goods being imported or exported from Northern Ireland when AI codes ‘NIIMP’, ‘NIDOM’, or ‘NIEXP’ are declared in DE 2/2.

Resolution:

  • Check DE 2/2 for NI AI codes.
  • Remove or replace Document Code ‘999L’ in DE 2/3 if present.
  • Verify that the declaration uses permitted document codes for NI.
  • Validate and reprocess the declaration.

Description:
Uniqueness Error: Only one instance of 999L may be declared in D.E. 2/3 per goods item.

Explanation:
Uniqueness Error:

The document code 999L can only be declared once per goods item. It does not have to be declared for each measure for which a waiver applies on that goods item. For example, if a goods item has two measures for which 999L is available to declare a waiver, declaring it once for that goods item will suffice to satisfy both measures. Declaring it twice will result in this rejection.

Reason:
Document code 999L can only be declared once per goods item, even if multiple measures are applicable.

Resolution:

  • Review DE 2/3 for duplicate 999L codes.
  • Ensure only one 999L per goods item.
  • Remove duplicate document codes.
  • Validate and reprocess the declaration.

Description:
Obligation Error: Mandatory Data Element has not been provided or the ID for previous document CLE must match the AcceptanceDate in the format yyyymmdd.

Explanation:
The declaration Acceptance Date is missing or not in the correct format against Previous Document Code ‘CLE’.

Reason:
The declaration Acceptance Date is missing or incorrectly formatted for Previous Document Code ‘CLE’.

Resolution:

  • Verify the Previous Document Code ‘CLE’.
  • Ensure Acceptance Date is provided in yyyymmdd format.
  • Correct the date if necessary.
  • Validate and reprocess the declaration.

Description:
Invalid EORI – This Party must have a permanent business establishment in Northern Ireland or the European Union.

Explanation:
A relevant party on the declaration does not have the status of ‘established in the Union’, for the purposes of an NI declaration.

Reason:
A relevant party does not have the status of ‘established in the Union’ for a Northern Ireland declaration.

Resolution:

  • Check the EORI number for the declared party.
  • Ensure the EORI belongs to a business established in NI or the EU.
  • Correct any invalid or missing EORI details.
  • Validate and reprocess the declaration.

Description:
Missing Element – A non-GB EORI requires entry of NI Movement AI Codes in DE 2/2.

Explanation:
A relevant party on an NI declaration has been entered with an XI EORI number, however no NI AI statements (NIIMP, NIDOM, NIEXP) are present.

Reason:
A party with an XI EORI has been declared, but no NI AI statements (NIIMP, NIDOM, NIEXP) are present.

Resolution:

  • Identify any non-GB (XI) EORIs declared in the submission.
  • Add the required NI AI codes (NIIMP, NIDOM, or NIEXP) in DE 2/2.
  • Confirm all items comply with Northern Ireland protocol requirements.
  • Validate and reprocess the declaration.

Description:
Authorisation Error: Invalid VAT number. Please note, if you are attempting to claim Onward Supply Relief (OSR), you must be identified as trading under the terms of the Northern Ireland Protocol (now Windsor Framework) for VAT.

Explanation:
Authorisation Error: Invalid VAT number. Please note, if you are attempting to claim Onward Supply Relief (OSR), you must be identified as trading under the terms of the Northern Ireland Protocol (now Windsor Framework) for VAT.

Reason:
Invalid VAT number for claiming OSR under the Northern Ireland Protocol. You must be identified as trading under the NI Protocol.

Resolution:

  • Identify DE 1/DE 2 combination causing the error.
  • Complete DE 3 correctly as required.
  • Verify the validity and correct the provided VAT number if required.
  • Confirm that the trader is eligible under the NI Protocol.
  • Validate and reprocess the declaration.

Description:
Relation Error: The values supplied in Data Element 1 and Data Element 2 require a valid value to be provided in Data Element 3.

Explanation:
Due to the way the declaration has been completed, a further DE must be completed or completed in a certain way – For example, on an NI export dec if DE 7/4 is either 1, 3, 4, 8 or 9 then DE 7/15 must be completed.

Reason:
A further DE must be completed correctly due to the combination of DE 1 and DE 2 values. For example, on an NI export declaration, if DE 7/4 is 1, 3, 4, 8, or 9, then DE 7/15 must be completed.

Resolution:

  • Identify the DE 1/DE 2 combination causing the error.
  • Complete the required DE 7/15 or other dependent DEs correctly.
  • Confirm all dependent data elements are accurate and consistent.
  • Validate and reprocess the declaration.

Description:
Relation Error: The values supplied in Data Element 1 and Data Element 2 require a valid value to be provided in Data Element 3 and/or Data Element 4.

Explanation:
Due to the way the declaration has been completed, a further DE must be completed or completed in a certain way – For example, on an NI export supp dec if DE 7/2 is ‘1’ for containerised, a containder ID must be provided in DE 7/10 at header or item.

Reason:
A further Data Element must be completed correctly due to the DE 1 and DE 2 combination.
Example: on an NI export supplementary declaration, if DE 7/2 = ‘1’ for containerised goods, a container ID must be provided in DE 7/10 at header or item level.

Resolution:

  • Identify the DE 1/DE 2 combination causing the issue.
  • Enter the required DE 7/10 container ID at the correct level (header or item).
  • Enter DE 3 and/or DE 4 as required.
  • Validate and reprocess the declaration.

Description:
Credibility check: incredible value found.

Explanation:
Value fails credibility check as too high or too low.

Reason:
Declared value fails credibility checks as it is too high or too low.

Resolution:

  • Review the declared value in the relevant data element.
  • Compare it against expected value ranges or historical data.
  • Correct any values that fall outside the acceptable range.
  • Verify all associated calculations or amounts are consistent.
  • Validate and reprocess the declaration.

Description:
Credibility check: incredible quota value found.

Explanation:
Value fails credibility check as too high or too low.

Reason:
Declared quota value fails credibility checks as it is too high or too low.

Resolution:

  • Review DE 8/1 or the relevant quota-related data elements.
  • Verify values against allowed quota limits for the commodity.
  • Correct any entries exceeding or below permissible limits.
  • Confirm that all quota calculations are accurate and consistent.
  • Validate and reprocess the declaration.

Description:
Additional errors found.

Explanation:
Declaration has multiple errors:
Contact the help desk.

Reason:
The declaration contains multiple errors. Assistance from the help desk may be required.

Resolution:

  • Review all reported errors in the submission.
  • Correct each error according to the guidance provided.
  • Verify the consistency and accuracy of all data elements.
  • Validate and reprocess the declaration.
  • If unresolved, contact the help desk.

Description:
Related movement not (yet) found.

Explanation:
Related movement not found.

Reason:
Related movement not found.

Resolution:

  • Verify the related movement reference you entered.
  • Confirm the movement has been submitted and accepted by CDS.
  • Ensure there are no typos in the movement ID.
  • Re-enter the correct reference if required.
  • Validate and reprocess the declaration.

Description:
Related movement does not match declaration.

Explanation:
Related movement does not match declaration.

Reason:
Related movement does not match declaration.

Resolution:

  • Review the related movement reference against the current declaration.
  • Confirm that both records belong to the same shipment.
  • Correct any mismatched data (UCR, MRN, movement ID).
  • Validate and reprocess the declaration.

Description:
Related movement not found.

Explanation:
Related movement not found.

Reason:
Related movement not found.

Resolution:

  • Confirm the referenced movement exists in CDS.
  • Check for timing issues, movement may not yet be logged.
  • Ensure the correct movement type is used.
  • Correct the reference if needed.
  • Validate and reprocess the declaration.

Description:
Duplicate value.

Explanation:
Duplication Error:

For example, the same Additional TARIC or National additional code has been declared twice for one item.

Reason:
The same Additional TARIC or National additional code has been declared more than once for a single item.

Resolution:

  • Review DE 6/16 and related code sections.
  • Identify and remove duplicate additional codes.
  • Validate and reprocess the declaration.

Description:
Data element value does not apply.

Explanation:
Value given for a data element does not apply.

This could be a formatting error or a code incorrectly completed.

Reason:
Value provided for a data element does not apply. This may be due to an incorrect code or formatting error.

Resolution:

  • Identify the affected data element.
  • Check the value against applicable code lists and format rules.
  • Correct invalid or non-applicable values.
  • Validate and reprocess the declaration.

Description:
Missing data element value.

Explanation:
Missing data element value.

A value that is required by the commodity code has not been completed. For example, supplementary unit. You need to check the ‘Measures’ column for the commodity code on the Trade Tariff.

Reason:
A required value is missing for the commodity code, such as a supplementary unit and check the ‘Measures’ column for the commodity code on the Trade Tariff.

Resolution:

  • Open the commodity code on the Trade Tariff and identify required measures or supplementary units.
  • Enter missing values in the appropriate data elements.
  • Validate and reprocess the declaration.

Description:
At least one of the commodity codes you have declared requires additional information that cannot be provided on this dataset. Please use the standard full export declaration dataset (B1) instead.

Explanation:
At least one of the commodity codes you have declared requires additional information that cannot be provided on this dataset. Please use the standard full export declaration dataset (B1) instead.

Reason:
At least one of the commodity codes declared requires additional information that cannot be provided on the current dataset.

Resolution:

  • Identify which commodity code requires additional data.
  • Switch from the current dataset to a B1 full dataset.
  • Provide all additional required details in the appropriate data elements.
  • Validate and reprocess the declaration.

Description:
Data element contains invalid value.

Explanation:
A DE contains invalid information related to a Tariff measure/condition – For example, the Preference code in DE 4/17 is incorrect.

Where this is in relation to a measurement unit error on DE 6/2 and/or DE 4/4:
This can be due to the values supplied being invalid, or an incorrect combination has been entered. For example, supplying both LPA and ASV in DE 4/4 against an excise tax type that does not permit this combination.
It can also indicate that two instances of the same measurement amount do not align. For example, the DE 6/2 Supplementary unit amount in litres differs to the amount entered against a measurement unit LTR in DE 4/4.

Reason:
A data element contains invalid information, such as incorrect preference codes, invalid measurement units, or mismatched quantities.

Resolution:

  • Identify the data elements highlighted by CDS, for example DE 4/17, DE 6/2, DE 4/4.
  • Correct invalid values according to tariff codes, units, and measurement rules.
  • Validate and reprocess the declaration.

Description:
Disallowed Document.

Explanation:
Document declared is not allowed for the given commodity code.

You need to check the ‘Conditions’ box for the commodity code on the Trade Tariff. If you do not hold any licence, you must decide if you can declare a waiver (usually a Y-code). Instructions for how to use the code are given in the ‘Conditions’ box for the commodity code and Appendix 5A.

Reason:
Document declared is not allowed for the given commodity code. Check the ‘Conditions’ box for the commodity code on the Trade Tariff.

Resolution:

  • Open the commodity code in the Tariff.
  • Check the ‘Conditions’ section for allowed documents.
  • Remove any document not permitted.
  • If no licence is held, apply an appropriate waiver (e.g., Y-code).
  • Validate and reprocess the declaration.

Description:
Missing document.

Explanation:
A document is missing.

The licence or exemption required for these goods is missing. You need to check the ‘Conditions’ box for the commodity code on the Trade Tariff. If you do not hold any licence, you must decide if you can declare a waiver (usually a Y-code). Instructions for how to use the code are given in the ‘Conditions’ box for the commodity code and Appendix 5A.

Reason:
A required licence or exemption is missing for this commodity code. Check the ‘Conditions’ box on the Trade Tariff.

Resolution:

  • Identify required document codes for the commodity.
  • Add the missing licence, exemption, or valid waiver (Y-code).
  • Ensure document ID matches the requirement.
  • Validate and reprocess the declaration.

Description:
Prohibition.

Explanation:
Value not allowed.

Reason:
Value declared is not allowed.

Resolution:

  • Identify the prohibited value or code.
  • Check tariff restrictions for the commodity.
  • Replace with a permitted value.
  • Validate and reprocess the declaration.

Description:
Quota exhausted.

Explanation:
Quota used up.

Reason:
Quota claimed is exhausted.

Resolution:

  • Confirm that the quota attempted to be claimed is exhausted.
  • Remove the quota claim.
  • Use the correct duty rate or alternative relief if applicable.
  • Validate and reprocess the declaration.

Description:
Quota suspended.

Explanation:
Quota suspended.

Reason:
Quota suspended.

Resolution:

  • Check the status of the quota for your commodity.
  • Remove the quota claim from your declaration.
  • Apply normal duty rates or alternative reliefs if applicable.
  • Validate and reprocess the declaration.

Description:
Incomplete measure or commodity code.

Explanation:
Incomplete measure or commodity code.

Reason:
Incomplete measure or commodity code.

Resolution:

  • Review the commodity code in the tariff.
  • Identify missing measures, including units, additional codes, or conditions.
  • Add all required information in the relevant data elements.
  • Validate and reprocess the declaration.

Description:
Tariff condition not fulfilled.

Explanation:
Tariff condition not fulfilled.

Value is not allowed to be used for the given commodity code. You need to check the ‘Measures’ box for the commodity code on the Trade Tariff. If you do not hold any licence, you must decide if you can declare a waiver (usually a Y-code). Instructions for how to use the code are given in the ‘Conditions’ box for the commodity code and Appendix 5A.

Reason:
Value is not allowed for the given commodity code. Check the ‘Measures’ or ‘Conditions’ box for guidance.

Resolution:

  • Check the commodity code’s tariff conditions.
  • Identify the value that violates the condition.
  • Replace or correct the value in the relevant data element.
  • Validate and reprocess the declaration.

Description:
Additional Excise code is missing.

Explanation:
National additional code for excise is missing.

Reason:
National additional code for excise is missing.

Resolution:

  • Check the commodity code for excise-related requirements.
  • Add the missing national excise additional code in the relevant data element.
  • Validate and reprocess the declaration.

Description:
Quota Closed.

Explanation:
Quota Error:

The Quota claimed is no longer available.

Reason:
The quota claimed is no longer available.

Resolution:

  • Check quota availability for the commodity.
  • Remove the quota claim from the declaration.
  • Apply normal duty rates.
  • Validate and reprocess the declaration.

Description:
When AI code ‘NIIMP’ is entered at item level in D.E. 2/2, it must be declared on all goods items in the declaration.

Explanation:
Additional information code NIIMP must appear on all items.

Additional information code NIIMP when used on one item must be entered on all items.

Reason:
AI code NIIMP used on one item must be entered on all items.

Resolution:

  • Check all goods items for presence of NIIMP.
  • Add NIIMP to any missing items.
  • Validate and reprocess the declaration.

Description:
When AI code ‘NIDOM’ is entered at item level in D.E. 2/2, it must be declared on all goods items in the declaration.

Explanation:
Additional information code NIDOM must appear on all items.

Additional information code NIDOM when used on one item must be entered on all items.

Reason:
AI code NIDOM used on one item must be entered on all items.

Resolution:

  • Review all goods items for NIDOM.
  • Add missing NIDOM codes where required.
  • Validate and reprocess the declaration.

Description:
When AI code ‘NIEXP’ is entered at item level in D.E. 2/2, it must be declared on all goods items in the declaration.

Explanation:
Additional information code NIEXP must appear on all items.

Additional information code NIEXP when used on one item must be entered on all items.

Reason:
AI code NIEXP used on one item must be entered on all items.

Resolution:

  • Identify goods items missing NIEXP.
  • Add NIEXP to all relevant goods items.
  • Validate and reprocess the declaration.

Description:
When de-risking AI code ‘NIREM’ is entered at item level in D.E. 2/2, either ‘NIIMP’ or ‘NIDOM’ AI codes must also be entered at item level on the same goods item.

Explanation:
You declared NIREM additional information code on its own.

NIREM additional information (AI) code may not be declared in isolation; NIDOM or NIIMP must also be declared on the same item.

Reason:
NIREM may not be declared on its own; NIIMP or NIDOM must also be declared on the same item.

Resolution:

  • Check item-level AI codes for NIREM.
  • Add NIIMP or NIDOM where NIREM is declared.
  • Validate and reprocess the declaration.

Description:
When subsidy AI code ‘NIAID’ is entered at item level in DE 2/2, either ‘NIIMP’ or ‘NIDOM’ AI codes must also be entered at item level on the same goods item.

Explanation:
Relation Error:

You have not entered either ‘NIIMP’ or ‘NIDOM’ AI codes when you declared subsidy AI code ‘NIAID’. Either of these codes are required to be entered at item level on the same good item.

Reason:
You must enter NIIMP or NIDOM when declaring subsidy AI code NIAID.

Resolution:

  • Locate goods items with NIAID.
  • Add NIIMP or NIDOM at item level.
  • Validate and reprocess the declaration.

Description:
Other Errors:

Explanation:
Other Errors.

Reason:
Other Errors.

Resolution:

  • Validate and reprocess the declaration.

Description:
Response from ALVS is not release.

Explanation:
Response from ALVS is not release.

Reason:
Response from ALVS is not released.

Resolution:

  • Check ALVS status and confirm if response is pending.
  • Ensure all required documents are submitted and complete.
  • Wait for ALVS release or correct missing documents.
  • Validate and reprocess the declaration.

Description:
Invalid UCR format, DUCR or MUCR.

Explanation:
Invalid UCR format, DUCR or MUCR.

Reason:
Invalid UCR format, DUCR or MUCR.

Resolution:

  • Verify UCR formatting rules according to CDS guidelines.
  • Enter DUCR or MUCR in the correct format.
  • Correct any typos or invalid characters.
  • Validate and reprocess the declaration.

Description:
UCR is not at the top of its consolidation.

Explanation:
UCR is not at the top of its consolidation.

Reason:
UCR is not at the top of its consolidation.

Resolution:

  • Confirm parent MUCR and associated DUCR.
  • Ensure correct consolidation order is followed.
  • Amend the consolidation structure if necessary.
  • Validate and reprocess the declaration.

Description:
UCR Type does not match UCR Format.

Explanation:
DUCR or MUCR is not the right format.

Reason:
UCR Type does not match UCR format.

Resolution:

  • Check that the UCR type corresponds to the required format.
  • Update DUCR or MUCR format accordingly.
  • Validate and reprocess the declaration.

Description:
Declaration is cancelled/terminated/invalidated/handled externally/rejected (upon arrival).

Explanation:
Declaration is cancelled or terminated upon arrival.

Declaration is cancelled/terminated/invalidated/handled externally/rejected (upon arrival).

Reason:
Declaration is cancelled, terminated, or invalidated.

Resolution:

  • Confirm the declaration status in CDS.
  • Stop sending updates to a cancelled, terminated, or invalidated declaration.
  • Create a new declaration if required.
  • Validate and reprocess the declaration.

Description:
Goods Arrival Date/Time is invalid or not included.

Explanation:
This is an ILE error code and is returned for Inventory linking.

Reason:
Goods Arrival Date/Time invalid or missing.

Resolution:

  • Check the goods arrival timestamp in the declaration.
  • Ensure the date and time match the inventory system format.
  • Correct any missing or invalid date/time entries.
  • Validate and reprocess the declaration.

Description:
Role/Location-Based Authorisation failed (PDS).

Explanation:
Authorisation failed.

Reason:
Role or location-based authorisation failed (PDS).

Resolution:

  • Verify user permissions for the assigned role.
  • Check location-based authorisations.
  • Correct any missing roles or access setup.
  • Validate and reprocess the declaration.

Description:
Goods Location is invalid.

Explanation:
Goods location code invalid.

The codes declared in the goods location code field must be selected from the code lists shown in Appendix 16.

Reason:
Goods Location code is invalid.

Resolution:

  • Refer to Appendix 16 for valid goods location codes.
  • Replace the invalid goods location code with a valid one.
  • Validate and reprocess the declaration.

Description:
Request has been received after a successful RET.

Explanation:
Request has been received after a successful RET.

Reason:
Request received after a successful RET.

Resolution:

  • Confirm that a RET has already been acknowledged.
  • Ensure no new requests are sent that are not allowed after RET.
  • Submit only permitted message types following a RET.
  • Validate and reprocess the declaration.

Description:
Licence Error: Electronic licence does not exist.

Explanation:
Licence Error:

Electronic licence does not exist.

Reason:
Electronic licence does not exist.

Resolution:

  • Check the licence number in the declaration.
  • Confirm the licence is electronic.
  • Replace with the correct electronic licence reference if needed.
  • Validate and reprocess the declaration.

Description:
Licence Error: Electronic licence quoted although Document Status Code indicated paper licence.

Explanation:
Licence Error:

Electronic licence quoted but document status code indicates paper licence. Check the document status code.

Reason:
Electronic licence quoted but status shows paper.

Resolution:

  • Check the document status code for the licence.
  • Ensure the licence type (electronic or paper) matches the declaration.
  • Correct any mismatch between licence type and status.
  • Validate and reprocess the declaration.

Description:
Licence Error: Licence is not valid.

Explanation:
Licence reference quoted is not valid.

This could be because:

  • Licence does not match the commodity code.
  • Licence authority declared is incorrect.
  • Licence is out of date.
  • Licence allows insufficient quantity.
  • Licence reference number declared is incorrect.
  • Licence does not belong to the importer/ exporter declared.
  • Licence is not valid for the country of origin/ dispatch/ destination.
  • Licence does not match the DUCR declared in DE 2/1.

If still stuck, contact the licencing authority.

Reason:
Licence is not valid. Possible causes include wrong commodity, wrong authority, expired licence, insufficient quantity, incorrect reference, wrong importer/exporter, invalid for country, mismatch with DUCR.

Resolution:

  • Review licence details thoroughly.
  • Verify commodity compatibility.
  • Check licence quantity and validity period.
  • Correct any mismatches with DUCR, authority, or party details.
  • Contact the issuing authority if unresolved.
  • Validate and reprocess the declaration.

Description:
Licence Error: An Import licence cannot be used on an Export declaration.

Explanation:
Licence Error:

Import licence cannot be used on an export declaration.

Reason:
Import licence declared on export declaration.

Resolution:

  • Remove the import licence from the export declaration.
  • Add the correct export licence if required.
  • Validate and reprocess the declaration.

Description:
Licence Error: Importer/Exporter is not the owner of the licence.

Explanation:
Licence Error:

Importer/Exporter is not the owner of the licence and/or licence is not valid.

Reason:
Importer/Exporter not owner of licence.

Resolution:

  • Verify the licence ownership against the party declared.
  • Correct the importer/exporter EORI if incorrect.
  • Use the correct licence belonging to the declared party.
  • Validate and reprocess the declaration.

Description:
Licence is not valid for declared Country of Destination.

Explanation:
Licence Error:

Licence is not valid for declared country of destination.

Reason:
Licence not valid for declared Country of Destination.

Resolution:

  • Check the licence’s valid destination countries.
  • Compare the declared Country of Destination with the licence.
  • Correct either the declared destination or the licence reference.
  • Validate and reprocess the declaration.

Description:
Licence Error: Licence is not valid for the declared goods item.

Explanation:

Licence is not valid for this item.

This could be because:

  • Licence does not match the commodity code.
  • Licensing authority declared is incorrect.
  • Licence is out of date.
  • Licence allows insufficient quantity.
  • Licence reference number declared is incorrect.
  • Licence does not belong to the importer/ exporter declared.
  • Licence is not valid for the country of origin/ dispatch/ destination.
  • Licence does not match the DUCR declared in DE 2/1.

If still stuck, contact the issuing authority.

Reason:
Licence not valid for declared goods item. Possible mismatches include commodity code, authority, date, quantity, country, DUCR, importer/exporter.

Resolution:

  • Review all licence conditions.
  • Ensure declared commodity, country, quantity, and DUCR match the licence.
  • Enter the correct licence reference.
  • Contact the issuing authority if conditions are unclear.
  • Validate and reprocess the declaration.

Description:
Licence has insufficient quantity remaining to meet claim.

Explanation:
Licence Error:

Licence does not cover the quantity declared.

Reason:
Insufficient quantity on licence.

Resolution:

  • Check the remaining quantity available on the licence.
  • Reduce declared quantity to match licence or use another licence.
  • Validate and reprocess the declaration.

Description:
Licence Error: Licence line number does not exist on the licence.

Explanation:
Licence Error:

Line number given on licence is not valid.

Reason:
Licence line number does not exist on the licence.

Resolution:

  • Verify the valid line numbers on the licence document.
  • Ensure the declared line number exists and matches the licence.
  • Correct any invalid line numbers.
  • Validate and reprocess the declaration.

Description:
Licence Error: An Export licence cannot be used on an Import declaration.

Explanation:
Licence Error:

Export licence cannot be used on an import declaration.

Reason:
An Export licence cannot be used on an Import declaration.

Resolution:

  • Review the licence type being used.
  • Confirm whether the declaration is Import or Export.
  • Replace the export licence with a valid import licence.
  • Validate and reprocess the declaration.

Description:
Uniqueness Error: Document Codes with identical IDs are not permitted on a single goods item.

Explanation:
Document reference is a duplication.

You cannot use the same reference on a single goods item.

Reason:
Document Codes with identical IDs are not permitted on a single goods item.

Resolution:

  • Review all document codes in DE 2/3.
  • Remove duplicate document IDs.
  • Ensure each document ID appears only once per goods item.
  • Validate and reprocess the declaration.

Description:
Licence Error: All instances of a licence for a declaration must use a consistent Document Status Code.

Explanation:
Licence Error:

All instances of a licence for a declaration must use a consistent Document Status Code.

Reason:
All instances of a licence must use a consistent Document Status Code.

Resolution:

  • Review all document status codes in DE 2/3.
  • Ensure the same licence uses the same status code consistently.
  • Correct any inconsistencies.
  • Validate and reprocess the declaration.

Description:
Licence Error: Document Status Code “EL” or “EP” is not allowed on a Single Use licence.

Explanation:
Licence Error:

Document status code “EL” or “EP” is not allowed on a single use licence.
The licence can only be used once so cannot be part used.

Reason:
Document Status Code “EL” or “EP” not allowed on a Single Use licence.

Resolution:

  • Identify the status code applied to the single-use licence.
  • Remove or replace EL/EP with the valid status code.
  • Validate and reprocess the declaration.

Description:
Licence is already surrendered.

Explanation:
Licence is already surrendered.

Reason:
Licence is already surrendered.

Resolution:

  • Check the licence status.
  • Ensure a valid, active licence is used.
  • Replace with a non-surrendered licence if required.
  • Validate and reprocess the declaration.

Description:
Licence is already exhausted.

Explanation:
Licence is already exhausted.

Reason:
Licence is already exhausted.

Resolution:

  • Review remaining quantities on the licence.
  • Use a licence with an available balance.
  • Update licence details in DE 2/3.
  • Validate and reprocess the declaration.

Description:
Transaction not permitted; Licence is inactive and is no longer available for use.

Explanation:
Licence is no longer available for use.

Licence declared has been made inactive, check correct licence is declared or contact issuing authority.

Reason:
Transaction not permitted; Licence is inactive and no longer available.

Resolution:

  • Confirm the licence’s activation status.
  • Replace with an active licence.
  • Verify with the issuing authority if needed.
  • Validate and reprocess the declaration.

Description:
Licence not valid for declared Country of Origin.

Explanation:
Licence Error:

You have declared an invalid Licence for the declared Country of Origin.

Reason:
Licence not valid for declared Country of Origin.

Resolution:

  • Check the licence’s country validity rules.
  • Ensure it covers the declared country of origin.
  • Replace with a licence valid for the country.
  • Validate and reprocess the declaration.

Description:
Licence not valid for declared Country of Dispatch.

Explanation:
Licence Error:

Licence not valid for declared country of dispatch.

Reason:
Licence not valid for declared Country of Dispatch.

Resolution:

  • Review the country of dispatch.
  • Ensure the licence permits that country.
  • Replace if not valid.
  • Validate and reprocess the declaration.

Description:
Licence Error: Document Status Code “EA” can only be declared on Type Y declaration.

Explanation:
Licence Error:

Document Status Code “EA” can only be used on a supplementary declaration.

Reason:
Document Status Code “EA” can only be declared on Type Y declaration.

Resolution:

  • Check the declaration type.
  • Only use EA for supplementary (Type Y) declarations.
  • Replace the status code if used incorrectly.
  • Validate and reprocess the declaration.

Description:
Licence Error: Licence cannot be declared on declaration category/declaration type combination.

Explanation:
Licence cannot be used.

A licence document code (for example X002, 9106) cannot be declared on this type of declaration, even if using a waiver/exemption document status code. If the goods are entitled to a waiver/exemption and there is a waiver document code which can be used in place of the licence document code (for example Y903, Y927), then this can be used instead. If there is no waiver document code that can be used then it may be necessary to use a standard declaration.

Reason:
Licence cannot be declared on this declaration type.

Resolution:

  • Check whether the declaration type accepts this licence document code.
  • Replace with a Y-code if the tariff allows.
  • If no waiver exists, use a standard declaration instead.
  • Validate and reprocess the declaration.

Description:
Obligation Error: ID must be provided for declared Document Code.

Explanation:
Document identifier required.

Instructions for how to use the code are given in the ‘Conditions’ box for the commodity code and Appendix 5A.

Reason:
Obligation Error: ID must be provided for declared Document Code.

Resolution:

  • Check DE 2/3 for missing document IDs.
  • Add the required identifier (e.g., licence number).
  • Validate and reprocess the declaration.

Description:
Quantity must be provided for Document Category.

Explanation:
Quantity must be provided.

In some cases, when you declare a document status code to indicate a waiver for a licence, you are still required to enter a ‘0’ as the quantity attributed to the licence. This will also require a measurement unit such as GBP. 

Reason:
Quantity must be provided for Document Category.

Resolution:

  • Identify the document requiring a quantity.
  • Enter the required quantity (even 0 if applicable).
  • Add the correct measurement unit.
  • Validate and reprocess the declaration.

Description:
Obligation Error: Document Status Code must be provided for declared Document Code.

Explanation:
Document status code needed.

Check appendix 5A for more information.

Reason:
Document Status Code is missing.

Resolution:

  • Review DE 2/3 for missing status codes.
  • Add the correct status code using Appendix 5A.
  • Validate and reprocess the declaration.

Description:
Licence Error: DUCR must be provided for an Import declaration with a Licence.

Explanation:
Licence Error:

You have not provided a DUCR – this is required at header level for an import declaration with a licence.

Reason:
DUCR must be provided for an Import declaration with a Licence.

Resolution:

  • Add the DUCR at header level.
  • Ensure it follows the correct format.
  • Validate and reprocess the declaration.

Description:
Reservation could not be made.

Explanation:
Reservation could not be made.

Reason:
Reservation could not be made.

Resolution:

  • Review the quota/licence reservation request.
  • Ensure all required details are correct.
  • Retry the reservation.
  • Validate and reprocess the declaration.

Description:
Reason for waiver must be declared for Document Category.

Explanation:
Reason not given for use of a ‘Y’ code.

The Y series document code used requires a document reason. Check the ‘Conditions’ box in the Online Tariff or appendix 5A for the information required.

Reason:
Reason for waiver must be declared for Document Category.

Resolution:

  • Check Y-code requirements in the tariff conditions.
  • Enter the required document reason text.
  • Validate and reprocess the declaration.

Let’s Secure Your Shipments Before Arrival

From one-off filings to continuous trade flows, iCareZ ensures your Entry Summary Declarations are prepared accurately, submitted on time, and aligned with security expectations to streamline your ENS compliance with confidence.

Industry expertise that simplifies complex operations. Let’s work together.