CDS Amendment

Overview

The Amend Declaration feature lets you update or remove eligible data on a declaration you've already submitted to CDS, without needing to cancel and start again.

Amendments still have to pass the same validation rules as a new declaration, so not everything on a submitted entry can be changed, and timing matters.

This article covers the amendment journey, which declaration statuses actually allow an amendment, which fields are off-limits, when you'll see a rejection notification, and what a "nil amendment" is for.

The CDS Amendment Journey

Once a declaration is submitted and accepted by CDS, it isn't locked immediately — there's a window where corrections can still be made directly through your software.

Here's how that window opens and closes:

1. Declaration submitted and accepted — CDS validates and accepts the entry (DMSACC).
2. Indicative tax calculation issued — CDS calculates the duty/VAT due, but marks it as "indicative," meaning it can still change. This is your amendment window..
3. Amendment submitted (if needed) — any correction goes through CDS again for re-validation, the same as a fresh declaration..
4. Arrival and clearance — once the declaration has arrived and CDS issues the cleared message (DMSCLE), the final tax calculation is issued..
5. Window closed — once the final tax calculation is received, the declaration can no longer be amended through your software.
   
   

After that point, a correction has to go through a formal HMRC process instead (a voluntary clearance amendment for an underpayment, or a repayment claim for an overpayment) rather than a straightforward system amendment.

Which Statuses Allow an Amendment

In short: if the final tax calculation hasn't been issued yet, you can still amend.

• Received.
• Accepted.
• Route 1
• Cleared (Export)

Fields That Cannot Be Amended

Regardless of status, certain fields are locked from amendment entirely. CDS will block the amendment if you try to change any of the following:

• Declaration Type (DE 1/1 and DE 1/2).

• Functional Reference ID (DE 2/5).

• MUCR and DUCR values.

• Procedure Code at item level.

Beyond these, one level mandatory fields if removed in amendment from one level then it should be given on another level .  — if a mandatory field is taken off the header, it needs to reappear at item level (and for every item, if there's more than one).

When Does an Amendment Rejected Notification Appear?

An amendment goes through the same validation logic as a brand-new declaration. If the amended version fails that validation — for example, a required field ends up missing, an invalid combination is introduced, or a locked field is touched — CDS will reject the amendment and send back a rejection notification, in the same way it would reject an initial submission with an error.

In short: a rejected amendment notification means the changes you submitted didn't pass CDS's rules — not that the original declaration itself has a problem.

Nil Amendment — What It Is and Why It's Used

A nil amendment is exactly what it sounds like: an amendment submitted with no actual changes.

It's used specifically after an amendment attempt comes back with an error. Rather than leaving the declaration stuck, submitting a nil amendment effectively pauses the declaration in its current state while the real issue is investigated and fixed — it doesn't change any data, it simply holds things in place.

Once the underlying problem is resolved, the correct amendment can then be submitted properly.

Need Help?

If you need assistance with amending a declaration, understanding an amendment rejection, or using a nil amendment in iCustoms, please contact the iCustoms Support Team for assistance Contact Support Team