Is your CDS post-clearance amendment process still valid after 16 June 2026?
The general catch-all category for post-clearance corrections to a CDS declaration — anything that isn't underpayment, overpayment, importer-detail, or a bulk amendment — used to go to HMRC by email. Since 16 June 2026 it does not. Here is what changed, who is still doing it the old way without knowing, and what breaks if you are.
By Saurabh Goyal, Founder & CEO of Phlo Systems. Published 10 August 2026.
If your team corrects CDS declarations after release by emailing HMRC, there is a good chance that process quietly stopped being valid on 16 June 2026 — and nothing about the email bouncing or erroring would necessarily tell you so.
The 30-second answer:
- What changed: the "other amendment" category — HMRC's general catch-all for post-clearance corrections that do not fall under underpayment, overpayment, importer-detail, or bulk amendments — moved from email submission to a new online notification form on GOV.UK, effective 16 June 2026.
- Who is affected: any importer, exporter, or customs broker with an internal procedure, template, or automated correspondence built around emailing HMRC for this category of correction.
- What breaks if you keep emailing: the amendment is submitted through a channel HMRC no longer treats as the correct route for that category — which is exactly the kind of gap that surfaces at audit, not at submission time.
- What to check: whether your correction workflow (or your customs broker's) has actually moved to the online form, not just whether corrections are still "getting sent."
Why this specific category, and why it is easy to miss
CDS post-clearance amendments were never one single process. HMRC splits them by type — underpayment, overpayment, importer-detail changes, bulk amendments — each with its own route and its own audit trail. The category that changed on 16 June 2026 is the general catch-all: the "other amendment" bucket for corrections that do not cleanly fit one of the named categories.
That is precisely the category most likely to be handled by an ad-hoc internal procedure rather than a documented, reviewed workflow. Underpayment and overpayment claims tend to have clear owners and formal templates because real money is visibly at stake. The catch-all category is the one a compliance team is more likely to have solved once, years ago, with an email template someone wrote and nobody has revisited since — exactly the kind of process that keeps "working" (an email sends, nobody complains) long after it has stopped being the correct channel.
What actually changed
| Before 16 June 2026 | After 16 June 2026 | |
|---|---|---|
| Submission channel for "other amendment" corrections | Email to HMRC | Online notification form on GOV.UK |
| Underpayment, overpayment, importer-detail, bulk amendments | Unaffected — separate existing routes | Unaffected — separate existing routes |
| What happens if you still email | No documented fallback — the email channel is no longer the correct route for this category | N/A — this is the only route now |
| Audit trail | Whatever the sender's own records show | Structured submission through the online form |
The change is narrow in scope — one category out of several — which is part of why it is easy for a team to miss: the other categories keep working exactly as before, so a spot-check against "did our overpayment claims still go through" gives a false all-clear.
Who is most exposed
- Compliance teams with a standing email template for post-clearance corrections. If nobody remembers why that template exists or when it was last checked against HMRC's current process, it predates 16 June 2026 by definition and has not been re-validated since.
- Customs brokers running amendments on behalf of multiple clients. A broker who has not updated their internal procedure is exposed across every client relying on that catch-all category, not just one account.
- Anyone using this category to correct classification or valuation errors that do not fit the underpayment or overpayment routes. These are the corrections most likely to fall into "other amendment," and the ones with the most direct link to audit exposure if the submission channel is wrong.
What to check this week
- Find the actual template or procedure your team uses for post-clearance corrections that are not underpayment, overpayment, importer-detail, or bulk amendments. If it produces an email to HMRC, it needs to change.
- Confirm whether it already changed. A procedure written or updated after 16 June 2026 may already point at the online form — check the date, not just the current behaviour, since an email sent today can still appear to "work" from the sender's side.
- If a broker handles this on your behalf, ask them directly whether their internal process has moved to the online form, and since when. Do not assume a broker's book-wide update happened automatically just because one client's corrections went through.
- Treat this as distinct from the 31 March 2026 TRE migration (see related reading below) — that deadline was about retrieving historical declaration data; this one is about submitting a specific category of correction. A business can be fully compliant on one and still exposed on the other.
Frequently Asked Questions
What exactly changed on 16 June 2026?
HMRC moved the "other amendment" category of CDS post-clearance corrections — the general catch-all for changes that do not fall under underpayment, overpayment, importer-detail, or bulk amendments — from email submission to a new online notification form on GOV.UK.
Does this affect overpayment claims (C285) or underpayment corrections?
No. Those categories have their own separate, unaffected routes. This change is specifically about the catch-all "other amendment" category.
How would I know if my process is still using the old email route?
Check the actual template or procedure your team (or your customs broker) uses for this category of correction, and confirm when it was last reviewed against HMRC's current guidance — not just whether corrections are still being sent, since an outdated email process can continue to appear functional from the sender's side with no error or bounce.
What is the risk of not switching?
The amendment is submitted through a channel HMRC no longer treats as correct for that category, creating a gap that is more likely to surface during an HMRC audit than at the moment of submission — by which point it can be harder to demonstrate the correction was made at all.
How Phlo Systems helps
tradePhlo's Declarations module replaces ad-hoc email-based amendment tracking with a structured workflow that follows HMRC's current submission routes for each amendment category, so a process change like the 16 June 2026 move to an online form does not depend on someone remembering to update an email template. See how tradePhlo handles UK customs declarations.
Related reading:
- HMRC's CDS report contracts expired 31 March 2026 — are you still using TRE?
- What is the UK Customs Declaration Service (CDS), and how do you submit an import declaration in 2026?
Saurabh Goyal is the Founder & CEO of Phlo Systems. He spent 12 years building CTRM and ERP systems for global commodity trading houses before founding Phlo in 2016.
Want to learn more about Phlo Systems?
See how our platform digitises international trade for commodity traders, importers, and exporters.
Get Started