CDS Error Codes

CDS10001

Explanation:

Obligation error: Mandatory Data Element has not been provided

Reason:

This error occurs when the declaration does not include all mandatory data elements. The system checks each required DE, and if any part is missing or incomplete, the declaration is rejected. For example, when declaring a party name and address, all parts such as name, street and number, country, and postcode must be fully completed.

Step-by-step Solution:

1. Check the declaration to confirm all mandatory data elements are completed in full.
2. Review each field where required information is expected.
3. Ensure no mandatory fields are left blank or partially filled.
4. If declaring a party name and address, make sure all components — name, street and number, country, and postcode — are provided.
5. Submit the declaration again after all required details are entered correctly.
   
   

CDS10002

Explanation:

Obligation error: Data Element is not allowed

Reason:

This error occurs when a data element has been entered in a place where it is not allowed. Certain values may only be placed at the header level and not at item level, or vice versa. The system identifies this as an invalid entry and rejects the declaration.

Step-by-step Solution:

1. Start reviewing the declaration from the beginning.
2. Identify any data elements added in locations where they are not permitted.
3. Check whether the value should be at header level or item level.
4. Remove or relocate the incorrect data element to its correct position.
5. Validate the declaration again and resubmit once corrected.
   
   

CDS10003

Explanation:

Obligation error: Number of Occurrences exceeds what is allowed for the Data Element

Reason:

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.

Step-by-step Solution:

1. Identify which data element(s) exceed allowed occurrences from the rejection details.
2. Review the declaration specification for the maximum allowed occurrences for that DE.
3. On the declaration, count instances of the DE and mark extras.
4. Remove or consolidate duplicate/extra instances so the count equals or is below the permitted maximum.
5. If duplicates are needed, move repeated information into a permitted alternate DE or attach supporting documents as required.
6. Validate the declaration to confirm occurrence counts are within limits.
7. Resubmit the declaration.

CDS10004

Explanation:

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

Reason:

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.

Step-by-step Solution:

1. Check which item line(s) triggered the error (note item numbers).
2. Verify the commodity code length and format against TARIC/commodity rules (correct number of digits).
3. Confirm any required national/TARIC additional codes are present and correctly entered.
4. Add any missing additional codes or correct their formats.
5. Ensure only the permitted number of additional codes are present for the item.
6. Run validation for commodity code and additional codes on each affected item.
7. Correct any remaining format or occurrence issues and resubmit.

CDS10010

Explanation:

Format error: data element has invalid format

Reason:

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.

Step-by-step Solution:

1. Note which DE(s) and items/sections are referenced by the error.
2. Check the expected format (character set, length, numeric/alphanumeric rules) for those DEs in the spec.
3. Inspect the entered values for invalid characters, wrong length, or misplaced punctuation.
4. Correct the value to match required format (trim/expand to correct length, remove forbidden characters).
5. Where necessary, convert numeric fields to numeric format (no extra spaces or letters).
6. Re-validate the declaration to confirm format compliance.
7. Resubmit after successful validation.

CDS10020

Explanation:

Domain error: data element contains invalid value

Reason:

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/item) to which it is permitted.

Step-by-step Solution:

1. Identify the DE and the invalid code/value from the rejection details.
2. Check the permitted code list or domain for that DE (e.g., document codes, country codes).
3. Confirm whether the code is valid for this declaration type and the correct level (header/item).
4. Replace the invalid code with a recognised, permitted code from the domain list.
5. If the correct code exists but was entered at the wrong level, move it to the correct level.
6. Re-run validation to ensure the domain error is resolved.
7. Resubmit the declaration.

CDS10021

Explanation:

Data Error: Value must be positive

Reason:

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.

Step-by-step Solution:

1. Locate the field(s) reported (amount, quantity, or licence write-off).
2. Check the entered value(s) for negative signs or parentheses indicating negatives.
3. Replace negative values with the correct positive value (zero or greater as required).
4. If the negative was required for business logic, confirm whether a different DE should be used instead.
5. Validate numeric formats (no embedded commas, correct decimal places).
6. Re-validate the declaration and resubmit.

CDS10045

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Review all valuation adjustments in DE 4/9.
2. Check if deductions exceed the item’s actual value.
3. Remove or reduce deductions causing the value to fall below zero.
4. Recalculate the customs value per item.
5. Ensure apportioning does not bring any item value to zero or negative.
6. Re-validate the valuation.
7. Resubmit the declaration.

CDS11003

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Count the actual number of goods items entered.
2. Compare with DE 1/9 (Total Number of Items).
3. Adjust DE 1/9 to match the actual number.
4. Ensure no extra blank or duplicate items exist.
5. Validate the declaration again.
6. Resubmit.

CDS11004

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check the requested procedure code for each item.
2. Verify the additional procedure codes are allowed with that procedure.
3. Confirm the combination is valid for the declaration type (e.g., H1, I1).
4. Remove or replace invalid procedure/additional procedure codes.
5. Validate permitted combinations using the CDS tariff tables.
6. Correct the entry and resubmit.

CDS11005

Explanation:

Relation Error: The Requested Procedure (D.E. 1/10) for each Goods Item must derive the same Declaration Category

Reason:
 
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.

Step-by-step Solution:

1. Review the requested procedure code for all items.
2. Identify any item with a procedure code belonging to a different declaration category.
3. Align all items to a single permitted category (e.g., Category H1).
4. Remove or amend conflicting procedure codes.
5. Validate the entire declaration after corrections.
6. Resubmit.

CDS11006

Explanation:

Relation Error: Net Mass must be lower than Gross Mass

Reason:
 
Net mass declared is greater than the gross mass declared.

Step-by-step Solution:

1. Review the net mass and gross mass for each goods item.
2. Correct any item where net mass > gross mass.
3. Ensure the gross mass includes packaging weight.
4. Recalculate masses if necessary.
5. Validate again.
6. Resubmit.

CDS11007

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Confirm the EORI of the person sending the additional message.
2. Compare with the EORI of the original declarant.
3. If they differ, stop submission of the message.
4. Ensure the original declarant (same EORI) resends the request.
5. Validate and complete the action once the correct sender is used.

CDS11012

Explanation:

Element is not allowed to be amended on this declaration type

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

Step-by-step Solution:

1. Review which data element you attempted to amend.
2. Check CDS rules to confirm whether the DE is amendable.
3. If not allowed, remove the attempted amendment.
4. Use the correct process (e.g., goods arrival instead of amendment).
5. Validate the remaining permitted changes.
6. Resubmit the amendment request.

CDS12003

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Identify the declaration using the duplicate LRN.
2. Generate a new LRN or append a version number using letters/numbers.
3. Update the declaration with the corrected LRN.
4. Validate that no duplicates exist within the 48-hour period.
5. Resubmit the declaration.

CDS12005

Explanation:

Authorisation Error: Party ID unknown or invalid

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

Step-by-step Solution:

1. Identify the DE containing the unrecognised EORI/VAT number.
2. Verify the number with the issuing authority or CDS reference.
3. Correct the number if invalid or use a valid permitted number.
4. Validate the declaration for compliance.
5. Resubmit the declaration.

CDS12006

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Identify the licence DE causing the error.
2. Check licence validity (expiry date, DUCR, EORI match).
3. Ensure the licence applies to the goods, country, and quantity declared.
4. Correct or replace the licence details accordingly.
5. Validate the declaration and resubmit.

CDS12007

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Identify the authorisation DE with the invalid reference.
2. Verify the reference number and expiry status.
3. Replace expired or unrecognised references with valid ones.
4. Validate the declaration.
5. Resubmit the declaration.

CDS12013

Explanation:

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

Reason:
 
VAT number is not a valid destination for VAT transfer.

Step-by-step Solution:

1. Identify the DE containing the VAT number.
2. Confirm valid VAT numbers eligible for transfer.
3. Replace invalid VAT number with a valid destination VAT.
4. Validate the declaration for VAT transfer compliance.
5. Resubmit the declaration.

CDS12014

Explanation:

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

Reason:
 
Goods arrival notification required. A goods arrival notification must follow a pre-lodged declaration.

Step-by-step Solution:

1. Check if the declaration is pre-lodged.
2. Ensure the Goods Arrival Notification is linked to the pre-lodged declaration.
3. Correct any sequence errors in submission.
4. Validate that the arrival notification follows CDS rules.
5. Resubmit the notification.

CDS12015

Explanation:

Sequence Error: Additional Message.declaration Reference does not refer to an existing declaration or the existing declaration is not in a permissible state to process the request

Reason:
 
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.

Step-by-step Solution:

1. Verify the declaration reference exists in CDS.
2. Check the current status of the declaration.
3. Confirm that the requested action is allowed for this status.
4. Correct the reference or wait until the declaration is in a permissible state.
5. Resubmit the request.

CDS12016

 

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check the acceptance date entered on the declaration.
2. Ensure it is not in the future.
3. Ensure it does not exceed the allowed past period (365/200 days depending on declaration type).
4. Correct the date if invalid.
5. Validate and resubmit the declaration.

CDS12022

Explanation:

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

Reason:
 
Number of items error. The goods item number declared is larger than the total number of goods items on the declaration.

Step-by-step Solution:

1. Verify the total number of goods items declared.
2. Check the Good Item Number entries.
3. Correct any item numbers exceeding the total count.
4. Validate the numbering sequence.
5. Resubmit the declaration.

CDS12024

Explanation:

Uniqueness Error: The value declared should be unique

Reason:
 
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, 2/3 - ARC number with document code C651 can only be used once, 4/9 - addition/deduction code can only be used once per header/item, 2/3 - licence ID cannot be repeated on the same item.

Step-by-step Solution:

1. Identify DEs with duplicate values.
2. Remove or correct repeated values according to CDS rules.
3. Ensure each DE value is unique where required.
4. Validate the declaration for uniqueness compliance.
5. Resubmit the declaration.

CDS12026

Explanation:

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

Reason:
 
Field has been amended more than once. On amendments, the same data element can only be amended once per amendment submission.

Step-by-step Solution:

1. Review the amendment submission for repeated DE changes.
2. Remove duplicate amendments to the same DE.
3. Keep only one valid amendment per DE.
4. Validate the amendment.
5. Resubmit the amendment request.

CDS12031

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check the original submission date of the declaration.
2. Verify the timing of the Goods Arrival Notification.
3. Ensure notification is submitted within 30 days.
4. Correct the submission date or follow the resubmission process.
5. Resubmit the notification.

CDS12034

Explanation:

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

Reason:
 
Amendment request is invalid. The amendment must be submitted using the same submission channel as the original declaration.

Step-by-step Solution:

1. Identify the original submission channel used.
2. Resubmit the amendment via the same channel.
3. Validate submission channel consistency.
4. Ensure all DEs comply with amendment rules.
5. Resubmit the amendment.

CDS12036

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check for any pending amendment or cancellation requests.
2. Wait for a response from CDS on the previous request.
3. Avoid submitting a new request until the previous one is completed.
4. Validate that all DEs are correct for the new request.
5. Submit the new request once permitted.

CDS12042

Explanation:

Relation error: elements must be identical within the Goods Item

Reason:
 
Relation error. Different quota order numbers cannot be declared on the same item. The declaration will be rejected if more than one quota order number is present in DE 8/1 for an item.

Step-by-step Solution:

1. Identify DE 8/1 entries for each goods item.
2. Ensure only one quota order number is declared per item.
3. Remove any duplicate or conflicting quota order numbers.
4. Validate the consistency of goods item entries.
5. Resubmit the declaration.

CDS12044

Explanation:

External Validation MUCR result: validation errors encountered

Reason:
 
MUCR reference is invalid.

Step-by-step Solution:

1. Identify the MUCR reference used in the declaration.
2. Verify the reference against CDS or the relevant authority.
3. Correct any invalid or incorrectly formatted MUCR.
4. Validate the declaration with the corrected MUCR.
5. Resubmit the declaration.

CDS12046

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Verify the original submission date of the pre-lodged declaration.
2. Confirm that the goods arrival notification was not submitted on time.
3. Resubmit the declaration using the correct process (arrived/pre-lodged then arrived).
4. Validate all DEs for compliance.
5. Complete the resubmission to CDS.

CDS12050
 

Explanation:

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.

Reason:
 
Procedure code is missing or invalid. Declaration must include at least one item and every item must include a valid procedure code.

Step-by-step Solution:

1. Check all goods items for the Requested Procedure DE (1/10).
2. Enter valid procedure codes for each item.
3. Verify the acceptance date is correct.
4. Validate the declaration for completeness.
5. Resubmit the declaration.

CDS12052

Explanation:

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.

Reason:
 
No valid declaration type. Enter the declaration type - standard, simplified (regular use), simplified (occasional use), supplementary or clearance, and prelodged or arrived. See DE 1/2 for the correct codes.

Step-by-step Solution:

1. Verify the declaration type entered in DE 1/2.
2. Select the correct type according to the declaration purpose.
3. Check acceptance date validity.
4. Validate the declaration for compliance.
5. Resubmit the declaration.

CDS12056

Explanation:

Relation error: the combination of elements is not allowed.

Reason:
 
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 that requires another code which is missing, or you cannot enter the customs procedure using ABDIN for Authorisation by Declaration (ABD).

Step-by-step Solution:

1. Identify the conflicting DEs.
2. Check CDS rules for allowed DE combinations.
3. Correct the values or add missing required DEs.
4. Validate all combinations in the declaration.
5. Resubmit the declaration.

CDS12057

Explanation:

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

Reason:
 
Invoice currency for all items must be the same. See DE 4/14 for the requirement.

Step-by-step Solution:

1. Check invoice currency in DE 4/14 for all goods items.
2. Ensure all items have the same currency.
3. Correct any discrepancies.
4. Validate that the declaration complies with currency rules.
5. Resubmit the declaration.

CDS12058

Explanation:

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.

Reason:
 
Number of packages error. Packaging quantity cannot be zero for all packages for combined packaging.

Step-by-step Solution:

1. Identify goods items with zero packaging quantity.
2. Ensure at least one item with the same marks/numbers has quantity > 0.
3. Correct the packaging quantity entries.
4. Validate consistency of combined packaging.
5. Resubmit the declaration.

CDS12062

Explanation:

External Validation DUCR result: validation errors encountered.

Reason:
 
DUCR reference is a duplication or is invalid.

Step-by-step Solution:

1. Check the DUCR used in the declaration.
2. Verify that it is unique and valid in CDS.
3. Correct or replace duplicate/invalid DUCR.
4. Validate all related data elements.
5. Resubmit the declaration.

CDS12066

Explanation:

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

Reason:
 
Either: 1) the declaration requires specific DEs to also be completed with certain values (missing/incorrect), or 2) the combination of DEs/content is not permitted.

Step-by-step Solution:

1. Identify the DEs causing the invalid combination.
2. Review CDS rules for required combinations.
3. Correct missing DEs or adjust values.
4. Validate that all combinations are permitted.
5. Resubmit the declaration.

CDS12067

Explanation:

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

Reason:
 
Either a DE is not permitted, has been completed incorrectly, or required combination of elements is missing. Example: DE 8/1 Quota with NIDOM/NIQUO in DE 2/2, or DE 3/40 header on H8 declaration missing APCs 'A04'/'1VW' or AI Statement 'PVA01'.

Step-by-step Solution:

1. Identify DEs with invalid combinations.
2. Verify CDS rules for each element combination.
3. Correct DEs or add required elements.
4. Validate declaration for permitted combinations.
5. Resubmit the declaration.

CDS12068

Explanation:

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

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

Step-by-step Solution:

1. Identify the doc code in DE 2/3 requiring a document identifier.
2. Enter the required document identifier.
3. Validate all related data elements.
4. Confirm compliance with CDS rules.
5. Resubmit the declaration.

CDS12069

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. Please wait for further update.

Step-by-step Solution:

1. Confirm the invalidation request has been submitted.
2. Wait for processing completion at the Office of Exit.
3. Do not submit a duplicate invalidation request.
4. Track status updates from CDS.
5. Take further action once invalidation is complete.

CDS12070

Explanation:

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

Reason:
 
A required field is missing a value or is invalid. For example, a value entered requires another field to be completed, or makes another field/code invalid.

Step-by-step Solution:

1. Identify the dependent DEs.
2. Complete the required DE(s) triggered by DE 1.
3. Validate both DEs for correct values.
4. Check for additional dependent fields.
5. Resubmit the declaration.

CDS12071

Explanation:

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

Reason:
 
A field has been completed at header and item level. Check the CDS Tariff data element completion guide for each field, e.g., DEs 3/9, 5/8, 5/14, 7/10, 8/5.

Step-by-step Solution:

1. Identify DEs entered at both header and item level.
2. Determine the correct level for each DE.
3. Remove the duplicate entry at the incorrect level.
4. Validate remaining entries.
5. Resubmit the declaration.

CDS12072

Explanation:

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

Reason:
 
This could be an unacceptable combination of values at header and item level. Example: gross weight declared at both levels, or both EORI and name/address declared for consignee/consignor/buyer.

Step-by-step Solution:

1. Identify the conflicting DEs.
2. Determine which DE should be supplied according to CDS rules.
3. Remove the incorrectly supplied DE.
4. Validate the declaration for correct DE usage.
5. Resubmit the declaration.

CDS12073

Explanation:

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

Reason:
 
A value is missing or has been entered at the wrong level. Check DEs 2/1, 3/1/3/2, 8/5, 7/10, 3/15, 3/16 for correct header/item level completion.

Step-by-step Solution:

1. Identify DEs with missing or incorrectly positioned values.
2. Check CDS Tariff guidance for correct level.
3. Correct the DE placement (header/item).
4. Validate all DEs.
5. Resubmit the declaration.

CDS12074

Explanation:

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

Reason:
 
Data elements are missing and one or the other is required. Check CDS Tariff data element completion guide and declare one or the other but not both. Example: exporter, consignor, carrier – complete either EORI or name/address.

Step-by-step Solution:

1. Identify DE 1 and DE 2.
2. Determine which DE must be supplied according to CDS rules.
3. Complete the required DE and leave the other blank.
4. Validate the declaration for completeness.
5. Resubmit the declaration.

CDS12075

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Identify DE 1 and DE 2 causing the conflict.
2. Remove the value from DE 2 if it is not allowed.
3. Verify that DE 1 is correctly populated.
4. Validate against CDS rules for this declaration type.
5. Resubmit the declaration.

CDS12077

Explanation:

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

Reason:
 
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 or different DE, or the DE itself is incomplete or contains invalid data.

Step-by-step Solution:

1. Identify DE 1 and DE 2 dependencies.
2. Supply the correct value in DE 2 as required by DE 1.
3. Ensure all related fields are fully completed.
4. Validate values against CDS rules.
5. Resubmit the declaration.

CDS12078

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:
 
Relation Error. When no deferment account number is declared, an immediate payment method must be provided in DE 4/8.

Step-by-step Solution:

1. Check if DE 2/6 (Deferment Account Number) is blank.
2. Provide an immediate payment method in DE 4/8.
3. Validate that the payment method is correctly declared.
4. Ensure consistency with CDS payment rules.
5. Resubmit the declaration.

CDS12079

Explanation:

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

Reason:
 
Relation error – two values declared are incompatible. For example, a DE is declared at both header and item levels but only one level is permissible, or a MUCR in DE 2/1 conflicts with GVMS location code in DE 5/23.

Step-by-step Solution:

1. Identify DE 1 and DE 2 causing the conflict.
2. Remove the value from DE 2 if it is not permitted.
3. Verify DE 1 value for correctness.
4. Check CDS rules for level restrictions and compatibility.
5. Resubmit the declaration.

CDS12080

Explanation:

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

Reason:
 
You have used a mix of addition or deduction codes for an item that is not permitted. Additions and deductions should only be declared at header level where they apply to all goods items. Each addition or deduction code can only be declared once at header level and once per item if declared at item level.

Step-by-step Solution:

1. Review all DE 4/9 entries at header and item levels.
2. Remove conflicting addition/deduction codes.
3. Ensure each code is declared only once per level.
4. Validate against CDS rules for header/item declarations.
5. Resubmit the declaration.

CDS12081

Explanation:

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

Reason:
 
The same party cannot be declared as both importer and exporter.

Step-by-step Solution:

1. Verify the EORI numbers for importer and exporter.
2. Correct either DE 3/16 or DE 3/2 to reflect the actual party.
3. Validate uniqueness of parties.
4. Resubmit the declaration.

CDS12082

Explanation:

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

Reason:
 
The currency declared for the total amount invoiced does not match the currency declared at item price amount.

Step-by-step Solution:

1. Check DE 4/11 and DE 4/14 currency codes.
2. Ensure both use the same currency.
3. Update incorrect entries.
4. Validate consistency across all items.
5. Resubmit the declaration.
    

CDS12083

Explanation:

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

Reason:
 
You have provided both a country and country group for mandatory data element Preferential Origin. If using a group code, ensure DE 5/15 specifies the specific country of origin.

Step-by-step Solution:

1. Identify DE 5/16 and DE 5/15 entries.
2. Remove the conflicting value (country or group).
3. Ensure only the correct code type is declared.
4. Validate against CDS Tariff Appendix 13.
5. Resubmit the declaration.

CDS12084

Explanation:

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

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

Step-by-step Solution:

1. Check DE 3/9 and DE 3/10 entries.
2. Remove either the EORI or full name/address as required.
3. Ensure only one method of identification is declared.
4. Validate consistency across the declaration.
5. Resubmit the declaration.

CDS12086

Explanation:

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

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

Step-by-step Solution:

1. Verify DE 3/31 and DE 3/32.
2. Remove either the carrier name or EORI to comply with rules.
3. Validate declaration for consistency.
4. Ensure correct details are associated with the shipment.
5. Resubmit the declaration.

CDS12087

Explanation:

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

Reason:
 
Additional fiscal party VAT number has been declared at both header and item level. It should only be declared at either item or header level. Or, procedure code 1042 requires an additional fiscal references ID.

Step-by-step Solution:

1. Check DE 3/40 entries at header and item levels.
2. Retain the declaration at the correct level only.
3. Add any required additional fiscal reference ID if missing.
4. Validate against CDS rules.
5. Resubmit the declaration.

CDS12088

Explanation:

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

Reason:
 
Representative details are missing. Complete the EORI in DE 3/19, or the name and address in DE 3/20, even if using your own details as the declarant.

Step-by-step Solution:

1. Check DE 3/19 and DE 3/20.
2. Declare either agent EORI or full name/address.
3. Validate agent information.
4. Confirm compliance with CDS rules.
5. Resubmit the declaration.

CDS12089

Explanation:

Relation error: Consignee Party Name (DE 3/9) must be supplied at either header or item level.

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

Step-by-step Solution:

1. Identify where DE 3/9 is missing.
2. Declare consignee name and address at the appropriate level.
3. Verify the procedure code and rules.
4. Validate declaration completeness.
5. Resubmit the declaration.

CDS12090

Explanation:

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.

Reason:
 
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.

Step-by-step Solution:

1. Check Additional Procedure Code 17X declaration.
2. Provide carrier name and address or carrier EORI at header level.
3. Remove any conflicting data at item level.
4. Validate against CDS procedure rules.
5. Resubmit the declaration.

CDS12091

Explanation:

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

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

Step-by-step Solution:

1. Verify EORI numbers for consignee and exporter.
2. Correct either DE 3/10 or DE 3/1.
3. Ensure parties are distinct.
4. Validate declaration compliance.
5. Resubmit the declaration.

CDS12092

Explanation:

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

Reason:
 
You have declared the same party for seller and exporter. Seller details are only required if different from exporter. If different, enter the seller’s EORI in DE 3/25.

Step-by-step Solution:

1. Check DE 3/25 and DE 3/1.
2. Correct seller details if it is a different party.
3. Ensure EORI numbers are correctly declared.
4. Validate declaration compliance.
5. Resubmit the declaration.

CDS12095

Explanation:

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.

Reason:
 
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.

Step-by-step Solution:

1. Check DE 1/11 and DE 5/14 values.
2. Ensure additional procedure codes 1IL or 1LV are used only for third-country exports.
3. Correct any invalid combinations.
4. Validate declaration against CDS rules.
5. Resubmit the declaration.

CDS12096

Explanation:

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

Reason:
 
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. May also require a waiver status code such as XW.

Step-by-step Solution:

1. Verify DE 3/39 for authorisation type.
2. Include required document code C505 in DE 2/3.
3. Add any necessary waiver status codes.
4. Validate all entries against CDS rules.
5. Resubmit the declaration.

CDS12097

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check DE 1/11 and DE 5/8 values.
2. Ensure F75 is only used with approved destination countries.
3. Correct invalid destination entries.
4. Validate the declaration.
5. Resubmit the declaration.

CDS12098

Explanation:

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

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

Step-by-step Solution:

1. Check DE 7/4 and DE 4/1.
2. Correct the means of transport or delivery terms to a valid combination.
3. Validate compatibility against CDS rules.
4. Resubmit the declaration.

CDS12099

Explanation:

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

Reason:
 
Goods location code not recognised. Check codes listed in Appendix 16 and in the Tariff supplements for new goods location codes.

Step-by-step Solution:

1. Verify DE 5/23 value.
2. Use valid goods location codes from the CDS Tariff appendix.
3. Correct any invalid code combinations.
4. Validate declaration.
5. Resubmit.

CDS12100

Explanation:

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

Reason:
 
Delivery Terms (DE 4/1) are not compatible with the Addition/Deduction code (DE 4/9). Combination must be compatible.

Step-by-step Solution:

1. Review DE 4/1 and DE 4/9.
2. Correct incompatible combinations.
3. Validate against CDS rules.
4. Ensure additions/deductions are at the correct level.
5. Resubmit the declaration.

CDS12101

Explanation:

Relation error: Declared Tax Type (DE 4/3) is not allowed in combination with the Additional Procedure.

Reason:
 
Additional procedure code is not permitted to be combined with the declared tax type (DE 4/3). E.g., codes 32D, 31D, 1IL, 1LV cannot be used with excise tax type.

Step-by-step Solution:

1. Verify DE 4/3 and Additional Procedure code.
2. Remove incompatible tax/procedure combinations.
3. Validate declaration.
4. Correct any conflicting entries.
5. Resubmit.

CDS12102

Explanation:

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

Reason:
 
You have not declared the deferred payment method required for the duty deferment account number.

Step-by-step Solution:

1. Check DE 2/6 for duty deferment account.
2. Declare the deferred payment method in DE 4/8.
3. Validate all related entries.
4. Ensure compliance with CDS rules.
5. Resubmit the declaration.

CDS12103

Explanation:

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

Reason:
 
When declaring Declaration Type CO (DE 1/1), the destination country must be a Special Fiscal Territory or EU Customs Union territory.

Step-by-step Solution:

1. Verify DE 1/1 and DE 5/8.
2. Correct destination to an approved country or territory.
3. Validate declaration.
4. Resubmit the declaration.

CDS12104

Explanation:

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

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

Step-by-step Solution:

1. Check DE 1/10 for procedure code.
2. Correct to a valid import procedure code.
3. Validate declaration entries.
4. Ensure compliance with CDS rules.
5. Resubmit the declaration.

CDS12105

Explanation:

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

Reason:
 
With additional procedure code E01 (simplified) or E02 (standard import), DE 4/9 additions/deductions must not be declared.

Step-by-step Solution:

1. Check DE 1/11 for E01/E02.
2. Remove DE 4/9 additions/deductions if declared.
3. Validate declaration.
4. Resubmit.

CDS12106

Explanation:

Relation error: Appropriate Additional Information Code must be provided in DE 2/2 with Additional Procedure Code 1CL.

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

Step-by-step Solution:

1. Verify DE 1/11 for 1CL.
2. Add corresponding AI code in DE 2/2.
3. Validate declaration entries.
4. Resubmit.

CDS12107

Explanation:

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

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

Step-by-step Solution:

1. Check AI code DE 2/2 for 00600.
2. Remove any licence document codes in DE 2/3.
3. Validate declaration.
4. Resubmit.

CDS12108

Explanation:

Obligation Error: DUCR is mandatory on an Export Declaration.

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

Step-by-step Solution:

1. Check for DUCR in header.
2. Add missing DUCR if not declared.
3. Validate declaration.
4. Resubmit.

CDS12109

Explanation:

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

Reason:
 
Total invoiced amount should be in GBP when using a fixed exchange rate. Invoice value (DE 4/14) on import or total amount invoiced (DE 4/11) on export must be declared in GBP.

Step-by-step Solution:

1. Check DE 4/15 for fixed rate.
2. Ensure invoice amounts are in GBP.
3. Correct currency codes where needed.
4. Validate declaration.
5. Resubmit.

CDS12110

Explanation:

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

Reason:
 
Preference Code declared (DE 4/17) is incompatible with claiming Quota (DE 8/1).

Step-by-step Solution:

1. Check DE 4/17 and DE 8/1.
2. Remove DE 8/1 if incompatible with preference code.
3. Validate entries.
4. Resubmit.

CDS12111

Explanation:

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

Reason:
 
You have declared the tax amount in the incorrect currency. Tax amounts must be declared in GBP.

Step-by-step Solution:

1. Verify DE 4/6 and DE 4/7 currency codes.
2. Correct currency to GBP.
3. Validate all entries.
4. Resubmit.

CDS12112

Explanation:

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.

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

Step-by-step Solution:

1. Check DE 5/21 for airport loading.
2. Add corresponding DE 4/9 airfreight addition/deduction code.
3. Validate declaration.
4. Resubmit.

CDS12113

Explanation:

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

Reason:
 
Holder of authorisation type CGU has been declared. Guarantee type in DE 8/2 must be 0 (Guarantee Waiver) or 1 (Comprehensive Guarantee).

Step-by-step Solution:

1. Verify authorisation type CGU in DE 3/39.
2. Set DE 8/2 guarantee type to 0 or 1.
3. Validate declaration.
4. Resubmit.

CDS12114

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check DE 4/9 value.
2. Ensure the percentage value is less than 100%.
3. Correct any invalid entries.
4. Validate declaration.
5. Resubmit.

CDS12115

Explanation:

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

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

Step-by-step Solution:

1. Verify DE 1/10 or DE 1/11 for the procedure code.
2. Add document code 185C in DE 2/3.
3. Validate declaration entries.
4. Resubmit.

CDS12117

Explanation:

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

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

Step-by-step Solution:

1. Check DE 3/16 and DE 3/27.
2. Ensure Importer and Buyer have different EORI numbers.
3. Correct the duplicate entry.
4. Validate declaration.
5. Resubmit.

CDS12118

Explanation:

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

Reason:
 
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.

Step-by-step Solution:

1. Check DE 3/1 entries at header and item levels.
2. Remove duplicate consignor entry from either header or item level.
3. Validate declaration.
4. Resubmit.

CDS12119

Explanation:

Relation error: Declared Additional Document (DE 2/3) is not allowed with this Procedure Code (DE 1/10 or DE 1/11).

Reason:
 
Additional document code, for example licence, exemption or authorisation number, is not allowed or must not be declared with certain procedure codes. Examples: C512 and C514 not permitted with some procedure codes; licence document restrictions may apply.

Step-by-step Solution:

1. Check DE 1/10 or DE 1/11 procedure code.
2. Remove any incompatible DE 2/3 additional document codes.
3. Validate declaration.
4. Resubmit.
    

CDS12120

Explanation:

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

Reason:
 
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 C514. For arrived export declarations, DE 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.

Step-by-step Solution:

1. Check DE 1/2 declaration type.
2. Verify required authorisation for this type.
3. Ensure correct authorisation document code is declared in DE 2/3.
4. Validate DE 3/39 for arrived export declarations.
5. Correct expired or invalid authorisations.
6. Resubmit declaration.

CDS12121

Explanation:

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

Reason:
 
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, or an AI code entered mandates another AI code to be present.

Step-by-step Solution:

1. Review DE 2/2 AI codes for each goods item.
2. Remove incompatible AI code combinations.
3. Add any missing AI codes required by other AI codes.
4. Validate declaration.
5. Resubmit.

CDS12123

Explanation:

Data Error: Value must be greater than 0.

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

Step-by-step Solution:

1. Check DE 4/14 invoice value.
2. Ensure value is greater than 0.
3. Correct any zero or negative values.
4. Validate declaration.
5. Resubmit.

CDS12125

Explanation:

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.

Reason:
 
The deferment account number or Guarantee reference number provided is either not recognised, suspended/revoked, or parties declared on the declaration do not have authority to use the account number. Check the CDS financial dashboard or contact HMRC deferment department.

Step-by-step Solution:

1. Verify the deferment account or guarantee reference number.
2. Confirm account is active and authorised for the declared parties.
3. Correct any invalid or unauthorised entries.
4. Validate declaration.
5. Resubmit.

CDS12132

Explanation:

DUCR format not valid.

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

Step-by-step Solution:

1. Check the DUCR format entered.
2. Ensure it follows the official CDS DUCR format guidelines.
3. Correct any formatting errors.
4. Validate the declaration.
5. Resubmit.

CDS12133

Explanation:

MUCR format not valid.

Reason:
 
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.

Step-by-step Solution:

1. Verify the MUCR format.
2. Correct any invalid characters or structure.
3. Revalidate the MUCR against CDS rules.
4. Resubmit the declaration.

CDS12134

Explanation:

DUCR and MUCR formats not valid.

Reason:
 
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 guidance. For previous declaration references, ensure the DUCR matches the previous declaration.

Step-by-step Solution:

1. Review MUCR and DUCR formats.
2. Correct any invalid structures.
3. Verify previous declaration references if applicable.
4. Validate declaration.
5. Resubmit.

CDS12135

Explanation:

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

Reason:
 
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 codes 0002–0007, it must also be declared.

Step-by-step Solution:

1. Check DE 5/14 for country of export.
2. Ensure it is provided at either header or item level.
3. Correct missing entries.
4. Validate declaration.
5. Resubmit the declaration.

CDS12136

Explanation:

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.

Reason:
 
The additional procedure code declared requires this declaration to have indirect representation (DE 3/21). The representative status must indicate 'Indirect', code ‘3’.

Step-by-step Solution:

1. Check DE 1/11 for additional procedure code.
2. Verify DE 3/21 indicates indirect representation if required.
3. Correct representative status if needed.
4. Validate declaration.
5. Resubmit.

CDS12137

Explanation:

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

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

Step-by-step Solution:

1. Review DE 2/1 at header level.
2. Ensure only one MUCR is declared.
3. Remove duplicate MUCR entries.
4. Validate declaration.
5. Resubmit.

CDS12138

Explanation:

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

Reason:
 
These additional procedure codes cannot be used with an EIDR C21 declaration. Examples: 1CD – Controlled drugs using Simplified Procedures, 1CG – Controlled Goods using Simplified Procedures.

Step-by-step Solution:

1. Check DE 1/11 for additional procedure codes.
2. Ensure codes are allowed for EIDR declarations.
3. Remove or correct incompatible codes.
4. Validate declaration.
5. Resubmit.

CDS12139

Explanation:

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.

Reason:
 
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.

Step-by-step Solution:

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

CDS12141

Explanation:

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

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

Step-by-step Solution:

1. Review AI codes in DE 2/2.
2. Remove conflicting codes (NIDOM or NIIMP).
3. Validate declaration.
4. Resubmit.

CDS12143

Explanation:

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

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

Step-by-step Solution:

1. Check DE 2/2 for AI codes.
2. Ensure only one of 'NIREM' or 'NIAID' is declared per goods item.
3. Correct the declaration.
4. Validate.
5. Resubmit.

CDS12144

Explanation:

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

Reason:
 
You have entered an EU Quota order number beginning with '09', which is not permitted for imports into the UK.

Step-by-step Solution:

1. Review DE 8/1 for quota order numbers.
2. Remove or correct any number starting with '09'.
3. Validate declaration.
4. Resubmit.

CDS12145

Explanation:

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.

Reason:
 
For Requested Procedure code 42, AI code NIIMP must also be declared.

Step-by-step Solution:

1. Check DE 1/10 for code 42.
2. Ensure DE 2/2 contains NIIMP for the same goods item.
3. Correct the declaration if missing.
4. Validate.
5. Resubmit.

CDS12146

Explanation:

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.

Reason:
 
You have not entered either Requested Procedure code 42 or AI code OSR42 on the same goods item.

Step-by-step Solution:

1. Identify goods items with Requested Procedure code 42.
2. Enter AI code OSR42 in DE 2/2 for the same goods item.
3. Validate declaration.
4. Resubmit.

CDS12147

Explanation:

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

Reason:
 
AI code UVC01 may only be used on an amendment.

Step-by-step Solution:

1. Check AI code UVC01 usage.
2. Remove from original declaration.
3. Include only in amendment requests.
4. Validate declaration.
5. Resubmit.

CDS12148

Explanation:

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

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

Step-by-step Solution:

1. Check Additional Document DE 2/3 for C506.
2. Ensure DE 4/8 contains a deferred payment method.
3. Correct declaration.
4. Validate.
5. Resubmit.

CDS12149

Explanation:

Relation Error: Additional Procedure code 000 cannot be declared with any other Additional Procedure Code.

Reason:
 
Additional procedure code 000 cannot be declared alongside any other additional procedure code.

Step-by-step Solution:

1. Review DE 1/11 for additional procedure codes.
2. Ensure code 000 is not declared with any other codes.
3. Remove any conflicting codes.
4. Validate declaration.
5. Resubmit.

CDS12150

Explanation:

Authorisation Error: Authorisation reference number does not belong to the party 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.

Step-by-step Solution:

1. Check the authorisation number in DE 3/39.
2. Ensure it belongs to the declared party.
3. Correct the authorisation reference if necessary.
4. Validate declaration.
5. Resubmit.

CDS12151

Explanation:

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

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

Step-by-step Solution:

1. Review DE 2/3 for duplicate licence IDs.
2. Ensure each licence ID is unique per goods item.
3. Remove duplicates.
4. Validate declaration.
5. Resubmit.

CDS12152

Explanation:

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.

Reason:
 
Additional Procedure Code '1H7' must be present for the H7/SRDS declaration category.

Step-by-step Solution:

1. Confirm the declaration type is H7/SRDS.
2. Ensure DE 1/11 includes code 1H7 for all goods items.
3. Add missing codes if required.
4. Validate declaration.
5. Resubmit.

CDS12153

Explanation:

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

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).

Step-by-Step Solution:

1. Check all EORIs in the declaration.
2. Ensure the country code is GB.
3. Correct any non-GB EORI numbers.
4. Validate declaration.
5. Resubmit.

CDS12154

Explanation:

Relation Error: Incompatible goods movements declared. When AI code 'NIIMP', 'NIDOM' or 'NIEXP' is entered at item level in DE 2/2, Document Code – 999L cannot be entered in DE 2/3.

Reason:
 
The Document Code 999L cannot be used for goods being imported or exported from Northern Ireland. Use the UK/NI online tariff to identify correct document codes required for your commodity code.

Step-by-Step Solution:

1. Check DE 2/2 for NI AI codes.
2. Remove or replace Document Code 999L in DE 2/3 if present.
3. Validate declaration.
4. Resubmit.

CDS12155

Explanation:

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

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

Step-by-Step Solution:

1. Review DE 2/3 for duplicate 999L codes.
2. Ensure only one 999L per goods item.
3. Remove duplicates.
4. Validate declaration.
5. Resubmit.

CDS12156

Explanation:

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

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

Step-by-Step Solution:

1. Verify the Previous Document Code 'CLE'.
2. Ensure Acceptance Date is provided in yyyymmdd format.
3. Correct the date if necessary.
4. Validate declaration.
5. Resubmit.

CDS12157

Explanation:

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

Reason:
 
A relevant party does not have the status of 'established in the Union' for an NI declaration.

Step-by-Step Solution:

1. Check the EORI for the declared party.
2. Ensure it is valid and belongs to a business established in NI or EU.
3. Correct if necessary.
4. Validate declaration.
5. Resubmit.

CDS12158

Explanation:

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

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

Step-by-Step Solution:

1. Identify non-GB (XI) EORIs in the declaration.
2. Add required NI AI codes in DE 2/2.
3. Validate declaration.
4. Resubmit.

CDS12170

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 NI Protocol. You must be identified as trading under the Northern Ireland Protocol.

Step-by-Step Solution:

1. Verify VAT number validity.
2. Confirm eligibility under the NI Protocol.
3. Correct VAT number if required.
4. Validate declaration.
5. Resubmit.

CDS12171

Explanation:

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

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

Step-by-Step Solution:

1. Identify DE 1/DE 2 combination causing error.
2. Complete DE 3 correctly as required.
3. Validate declaration.
4. Resubmit.

CDS12172

Explanation:

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.

Reason:
 
A further DE must be completed correctly due to 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.

Step-by-Step Solution:

1. Identify DE 1/2 combination causing error.
2. Enter DE 3 and/or DE 4 as required.
3. Validate declaration.
4. Resubmit.

CDS13000

Explanation:

Credibility check: incredible value found.

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

Step-by-Step Solution:

1. Review declared value in relevant DE.
2. Verify it against expected range.
3. Correct value if needed.
4. Validate declaration.
5. Resubmit.

CDS14000

Explanation:

Credibility check: incredible quota value found.

Reason:
 
Quota value fails credibility check as too high or too low.

Step-by-Step Solution:

1. Review DE 8/1 or relevant quota values.
2. Check against allowed quota limits.
3. Correct value if needed.
4. Validate declaration.
5. Resubmit.

CDS19999

Explanation:

Additional errors found.

Reason:
 
Declaration has multiple errors. Contact the help desk for assistance.

Step-by-Step Solution:

1. Review all errors in the submission.
2. Correct each error according to the guidance provided.
3. Validate declaration.
4. Resubmit.
5. If unresolved, contact the help desk.

CDS20001

Explanation:

Related movement not (yet) found.

Reason:
 
Related movement not found.

Step-by-Step Solution:

1. Verify the related movement reference you entered.
2. Check if the related movement has been submitted and accepted by CDS.
3. Ensure there are no typos in the movement ID.
4. Re-enter the correct reference if required.
5. Resubmit the declaration.

CDS20002

Explanation:

Related movement does not match declaration.

Reason:
 
Related movement does not match declaration.

Step-by-Step Solution:

1. Review the related movement reference against the current declaration.
2. Confirm that both records belong to the same shipment.
3. Correct any mismatched data (UCR, MRN, movement ID).
4. Revalidate the declaration.
5. Resubmit.

CDS20003

Explanation:

Related movement not found.

Reason:
 
Related movement not found.

Step-by-Step Solution:

1. Confirm the referenced movement exists in CDS.
2. Check for timing issues—movement may not yet be logged.
3. Ensure the correct movement type is used.
4. Correct the reference if needed.
5. Resubmit.

CDS40007

Explanation:

Duplicate value.

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

Step-by-Step Solution:

1. Review DE 6/16 and related code sections.
2. Identify duplicate additional codes.
3. Remove repeated entries.
4. Validate the declaration.
5. Resubmit.

CDS40010

Explanation:

Data element value does not apply.

Reason:
 
Value given for a data element does not apply. This could be a formatting error or a code incorrectly completed.

Step-by-Step Solution:

1. Identify the DE flagged in the error.
2. Check code lists and format rules in the tariff.
3. Replace incorrect or non-applicable values.
4. Validate remaining fields.
5. Resubmit.

CDS40011

Explanation:

Missing data element value.

Reason:
 
A value required by the commodity code is missing. For example, supplementary unit. Check the 'Measures' column for the commodity code on the Trade Tariff.

Step-by-Step Solution:

1. Open the commodity code on the Trade Tariff.
2. Identify required measures or supplementary units.
3. Enter the missing value in the appropriate DE.
4. Validate the declaration.
5. Resubmit.

CDS40012

Explanation:

Dataset not sufficient for commodity code.

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

Step-by-Step Solution:

1. Identify which commodity code requires more data.
2. Switch from your current dataset to a B1 dataset.
3. Provide all additional required details.
4. Validate the full declaration.
5. Resubmit.

CDS40013

Explanation:

Data element contains invalid value.

Reason:
 
A DE contains invalid information related to a Tariff measure/condition. Examples include:

• Incorrect preference code in DE 4/17
• Invalid measurement unit combinations
• Mismatched litre amounts between DE 6/2 and DE 4/4

Step-by-Step Solution:

1. Identify the DE highlighted by CDS.
2. Check correct tariff codes, units, and combinations in the Trade Tariff.
3. Correct any invalid or conflicting values.
4. Validate all measurement units.
5. Resubmit.

CDS40044

Explanation:

Disallowed Document.

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

Step-by-Step Solution:

1. Open the commodity code in the Tariff.
2. Check the “Conditions” section for allowed documents.
3. Remove any document not permitted.
4. If no licence is held, apply an appropriate waiver (e.g., Y-code).
5. Validate and resubmit.

CDS40045

Explanation:

Missing document.

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

Step-by-Step Solution:

1. Identify required document codes for the commodity.
2. Add the missing licence/exemption or valid waiver (Y-code).
3. Ensure document ID matches requirement.
4. Validate declaration.
5. Resubmit.

CDS40047

Explanation:

Prohibition.

Reason:
 
Value not allowed.

Step-by-Step Solution:

1. Identify the prohibited value or code.
2. Check tariff restrictions for this commodity.
3. Replace with a permitted value.
4. Validate the declaration.
5. Resubmit.

CDS40049

Explanation:

Quota Exhausted.

Reason:
 
Quota used up.

Step-by-Step Solution:

1. Confirm that the quota you attempted to claim is exhausted.
2. Remove the quota claim.
3. Use the correct duty rate or alternative relief (if applicable).
4. Validate the declaration.
5. Resubmit.

CDS40053

Explanation:

Quota Suspended.

Reason:
 
Quota suspended.

Step-by-Step Solution:

1. Check the status of the quota for your commodity.
2. Remove the quota claim from your declaration.
3. Apply normal duty rates or alternative reliefs.
4. Validate the declaration.
5. Resubmit.

CDS40059

Explanation:

Incomplete measure or commodity code.

Reason:
 
Incomplete measure or commodity code.

Step-by-Step Solution:

1. Review the commodity code in the tariff.
2. Identify missing measures (units, additional codes, conditions).
3. Add required information.
4. Validate the declaration.
5. Resubmit.

CDS40066

Explanation:

Tariff condition not fulfilled.

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

Step-by-Step Solution:

1. Check the commodity code’s tariff conditions.
2. Identify the value that violates the condition.
3. Replace or correct the value.
4. Validate declaration.
5. Resubmit.

CDS40068

Explanation:

Additional Excise Code Missing.

Reason:
 
National additional code for excise is missing.

Step-by-Step Solution:

1. Check commodity code for excise-related requirements.
2. Add the missing national excise additional code.
3. Validate declaration.
4. Resubmit.

CDS40069

Explanation:

Quota Closed.

Reason:
 
The quota claimed is no longer available.

Step-by-Step Solution:

1. Check quota availability for the commodity.
2. Remove the quota claim.
3. Apply normal duty rates.
4. Validate and resubmit.

CDS40073

Explanation:

NIREM cannot be used alone.

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

Step-by-Step Solution:

1. Check item-level AI codes.
2. Add NIIMP or NIDOM where NIREM is declared.
3. Validate declaration.
4. Resubmit.

CDS40074

Explanation:

NIAID requires NIIMP or NIDOM.

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

Step-by-Step Solution:

1. Locate items with NIAID.
2. Add NIIMP or NIDOM at item level.
3. Validate and resubmit.

CDS40075

Explanation:

NIIMP must appear on all items.

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

Step-by-Step Solution:

1. Check if NIIMP is present at item level.
2. Add NIIMP to all goods items.
3. Validate declaration.
4. Resubmit.

CDS40076

Explanation:

NIDOM must appear on all items.

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

Step-by-Step Solution:

1. Review all goods items for NIDOM.
2. Add missing NIDOM codes.
3. Validate and resubmit.

CDS40077

Explanation:

NIEXP must appear on all items.

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

Step-by-Step Solution:

1. Identify items missing NIEXP.
2. Add NIEXP to all goods items.
3. Validate declaration.
4. Resubmit.

CDS40078

Explanation:

Relation Error: NIREM cannot be used alone.

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

Step-by-Step Solution:

1. Review goods items for NIREM.
2. Add NIIMP or NIDOM to the same items.
3. Validate declaration.
4. Resubmit.

CDS40079

Explanation:

Relation Error: NIAID requires NIIMP or NIDOM.

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

Step-by-Step Solution:

1. Locate goods items with NIAID.
2. Add NIIMP or NIDOM to these items.
3. Validate declaration.
4. Resubmit.

CDS50000

Explanation:

Response from ALVS is not release.

Reason:
 
Response from ALVS is not released.

Step-by-Step Solution:

1. Check ALVS status.
2. Ensure document requirements are fulfilled.
3. Wait or correct missing documents.
4. Resubmit when ALVS returns “release.”

CDS50001

Explanation:

Invalid UCR Format, DUCR or MUCR.

Reason:
 
Invalid UCR format, DUCR or MUCR.

Step-by-Step Solution:

1. Verify UCR formatting rules.
2. Enter DUCR/MUCR in the correct format.
3. Correct any typos.
4. Validate and resubmit.

CDS50003

Explanation:

UCR is not at the top of its consolidation.

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

Step-by-Step Solution:

1. Confirm parent MUCR and associated DUCR.
2. Ensure correct consolidation order.
3. Amend the consolidation structure.
4. Resubmit.

CDS50008

Explanation:

UCR Type does not match UCR Format.

Reason:
 
DUCR or MUCR is not the right format.

Step-by-Step Solution:

1. Check if the UCR type matches required format.
2. Update DUCR/MUCR format accordingly.
3. Validate.
4. Resubmit.

CDS50015

Explanation:

Declaration is cancelled/terminated/invalidated.

Reason:
 
Declaration is cancelled, terminated, invalidated, handled externally, or rejected upon arrival.

Step-by-Step Solution:

1. Confirm the declaration status in CDS.
2. Stop sending updates to a cancelled declaration.
3. Create a new declaration if needed.
4. Resubmit through the correct process.

CDS50018

Explanation:

Goods Arrival Date/Time invalid or missing.

Reason:
 
This is an ILE error code related to inventory linking.

Step-by-Step Solution:

1. Check goods arrival timestamp.
2. Ensure it matches inventory system format.
3. Correct missing/invalid date or time.
4. Resubmit.

CDS50027

Explanation:

Role/Location-Based Authorisation failed (PDS).

Reason:
 
Authorisation failed.

Step-by-Step Solution:

1. Check user permissions for the role.
2. Verify location authorisation.
3. Correct any missing roles in setup.
4. Resubmit.

CDS50028

Explanation:

Goods Location is invalid.

Reason:
 
Goods location code invalid. Must match codes in Appendix 16.

Step-by-Step Solution:

1. Open Appendix 16.
2. Locate valid goods location code.
3. Replace the incorrect code.
4. Validate.
5. Resubmit.

CDS50031

Explanation:

Request received after a successful RET.

Reason:
 
Request received after a successful RET.

Step-by-Step Solution:

1. Check that a RET has already been acknowledged.
2. Ensure no new requests are sent improperly.
3. Submit only allowed message types after RET.

CDS70711

Explanation:

Electronic licence does not exist.

Reason:
 
Licence error — Electronic licence does not exist.

Step-by-Step Solution:

1. Check the licence number.
2. Confirm licence is electronic.
3. Replace with correct licence reference.
4. Resubmit.

CDS70719

Explanation:

Electronic licence quoted but status shows paper.

Reason:
 
Electronic licence quoted but document status code indicates paper licence.

Step-by-Step Solution:

1. Check the document status code.
2. Ensure the licence type (paper/electronic) matches.
3. Correct any mismatch.
4. Resubmit.

CDS70724

Explanation:

Licence is not valid.

Reason:
 
Licence reference quoted 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

Step-by-Step Solution:

1. Review licence details thoroughly.
2. Check commodity compatibility.
3. Verify quantity and validity period.
4. Correct any mismatch.
5. If unresolved, contact issuing authority.
6. Resubmit.

CDS70739

Explanation:

Import licence declared on export declaration.

Reason:
 
Import licence cannot be used on an export declaration.

Step-by-Step Solution:

1. Remove import licence from export declaration.
2. Add correct export licence (if required).
3. Validate and resubmit.

CDS70740

Explanation:

Importer/Exporter not owner of licence.

Reason:
 
Importer/Exporter does not own the licence and/or licence is not valid for the party.

Step-by-Step Solution:

1. Verify licence ownership.
2. Correct the importer/exporter EORI if wrong.
3. Use the correct licence belonging to the party.
4. Resubmit.

CDS70758

Explanation:

Licence not valid for declared Country of Destination.

Reason:
 
Licence is not valid for the declared destination.

Step-by-Step Solution:

1. Check the licence’s valid destinations.
2. Compare with the declared country.
3. Correct destination or licence.
4. Resubmit.

CDS70760

Explanation:

Licence not valid for declared goods item.

Reason:
 
Licence may not match commodity code, authority, date, quantity, country, DUCR, importer/exporter, etc.

Step-by-Step Solution:

1. Check all licence conditions.
2. Ensure commodity, country, and quantity match.
3. Enter the correct licence reference.
4. If unclear, contact issuing authority.
5. Resubmit.

CDS70761

Explanation:

Insufficient quantity on licence.

Reason:
 
Licence does not cover the quantity declared.

Step-by-Step Solution:

1. Check remaining quantity on licence.
2. Reduce declared quantity or use another licence.
3. Validate.
4. Resubmit.

CDS70791

Explanation:

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

Reason:
 
Licence error — Line number given on licence is not valid.

Step-by-Step Solution:

1. Check the licence document for valid line numbers.
2. Ensure the line number declared matches an existing line.
3. Correct the incorrect line number.
4. Validate the licence data.
5. Resubmit the declaration.

CDS71115

Explanation:

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

Reason:
 
Licence error — Export licence cannot be used on an import declaration.

Step-by-Step Solution:

1. Review the licence type being used.
2. Confirm whether the declaration is import or export.
3. Replace the export licence with a valid import licence.
4. Validate declaration.
5. Resubmit.

CDS71200

Explanation:

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

Reason:
 
Document reference is a duplication. You cannot use the same reference on a single goods item.

Step-by-Step Solution:

1. Review all document codes in DE 2/3.
2. Remove duplicate document IDs.
3. Ensure each document ID appears only once per item.
4. Validate declaration.
5. Resubmit.

CDS71201

Explanation:

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

Reason:
 
Licence error — All instances of a licence for a declaration must use a consistent Document Status Code.

Step-by-Step Solution:

1. Review all document status codes (DE 2/3).
2. Ensure the same licence uses the same status code everywhere.
3. Correct any inconsistencies.
4. Validate declaration.
5. Resubmit.

CDS71203

Explanation:

Licence Error: Document Status Code "EL" or "EP" not allowed on a Single Use licence.

Reason:
 
Licence error — Document status code 'EL' or 'EP' is not allowed on a single-use licence.

Step-by-Step Solution:

1. Identify the status code applied to the single-use licence.
2. Remove or replace EL/EP with the valid status code.
3. Validate declaration.
4. Resubmit.

CDS71204

Explanation:

Licence is already surrendered.

Reason:
 
Licence is already surrendered.

Step-by-Step Solution:

1. Check the licence status.
2. Ensure a valid, active licence is used.
3. Replace with a non-surrendered licence if required.
4. Validate declaration.
5. Resubmit.

CDS71206

Explanation:

Licence is already exhausted.

Reason:
 
Licence is already exhausted.

Step-by-Step Solution:

1. Review remaining quantities on the licence.
2. Use a licence with an available balance.
3. Update licence details in DE 2/3.
4. Validate declaration.
5. Resubmit.

CDS71216

Explanation:

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

Reason:
 
Licence is no longer available for use.

Step-by-Step Solution:

1. Confirm the licence's activation status.
2. Replace with an active licence.
3. Verify with the issuing authority if needed.
4. Validate declaration.
5. Resubmit.

CDS71236

Explanation:

Licence not valid for declared Country of Origin.

Reason:
 
Licence error — You have declared an invalid licence for the declared Country of Origin.

Step-by-Step Solution:

1. Check the licence's country validity rules.
2. Ensure it covers the declared country of origin.
3. Replace with a licence valid for the country.
4. Validate declaration.
5. Resubmit.

CDS71252

Explanation:

Licence not valid for declared Country of Dispatch.

Reason:
 
Licence error — Licence not valid for declared country of dispatch.

Step-by-Step Solution:

1. Review the country of dispatch.
2. Ensure the licence permits that country.
3. Replace if not valid.
4. Validate declaration.
5. Resubmit.

CDS71262

Explanation:

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

Reason:
 
Licence error — Document Status Code 'EA' can only be used on a supplementary declaration.

Step-by-Step Solution:

1. Check the declaration type.
2. Only use EA for supplementary (Type Y) declarations.
3. Replace the status code if used incorrectly.
4. Validate declaration.
5. Resubmit.

CDS73329

Explanation:

Licence cannot be declared on this declaration type.

Reason:
 
A licence document code cannot be declared on this declaration type. A waiver/exemption Y-code may be used instead if allowed.

Step-by-Step Solution:

1. Check whether the declaration type accepts this licence document code.
2. Replace with a Y-code if the tariff allows.
3. If no waiver exists, use a standard declaration instead.
4. Validate declaration.
5. Resubmit.

CDS77000

Explanation:

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

Reason:
 
Document identifier required.

Step-by-Step Solution:

1. Check DE 2/3 for missing document IDs.
2. Add the required identifier (e.g., licence number).
3. Validate declaration.
4. Resubmit.

CDS77001

Explanation:

Quantity must be provided for Document Category.

Reason:
 
Quantity must be provided, sometimes even as '0', with a measurement unit like GBP.

Step-by-Step Solution:

1. Identify the document requiring a quantity.
2. Enter the required quantity (even 0 if applicable).
3. Add the correct measurement unit.
4. Validate declaration.
5. Resubmit.

CDS77002

Explanation:

Obligation Error: Document Status Code must be provided.

Reason:
 
Document status code needed.

Step-by-Step Solution:

1. Review DE 2/3 for missing status codes.
2. Add the correct status code using Appendix 5A.
3. Validate declaration.
4. Resubmit.

CDS77003

Explanation:

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

Reason:
 
Licence error — DUCR is required.

Step-by-Step Solution:

1. Add the DUCR at header level.
2. Ensure it follows the correct format.
3. Validate declaration.
4. Resubmit.

CDS77004

Explanation:

Reservation could not be made.

Reason:
 
Reservation could not be made.

Step-by-Step Solution:

1. Review the quota/licence reservation request.
2. Ensure all required details are correct.
3. Retry reservation.
4. Validate declaration.
5. Resubmit.

CDS77005

Explanation:

Reason for waiver must be declared for Document Category.

Reason:
 
Reason not given for use of a 'Y' code.

Step-by-Step Solution:

1. Check Y-code requirements in the tariff conditions.
2. Enter the required document reason text.
3. Validate declaration.
4. Resubmit.