Key Takeaways
- Treat a CDS availability issue as an operational incident, not just an IT fault, because release, inventory linking, licences, duty payment and customer promises can all be affected.
- Check HMRC’s Customs Declaration Service availability page first, then your software provider, Community System Provider and port or inventory system messages before you escalate.
- Build an evidence pack before raising a case: LRN, MRN, DUCR or MUCR, error code, software conversation ID, inventory status message, screenshots and a timestamped timeline.
- GOV.UK says urgent CDS problem reports receive a response within 2 hours after form submission, while all other reports receive a response within 24 hours.
- After service recovery, reconcile declarations, deferment or cash account movements, licence releases, postponed VAT entries and customer delay records before closing the incident.
Why CDS availability needs a playbook
CDS availability incidents create commercial risk long before they become a formal HMRC outage. A declaration that cannot be accepted, amended, arrived or linked to inventory can hold goods at the port, stop a haulier from collecting, prevent Permission to Progress on an export movement, or leave a customer with no reliable release time. The right response is a short playbook that tells the duty manager what to check, what evidence to collect and who to contact.
HMRC maintains a GOV.UK page for “Customs Declaration Service: service availability and issues”, and the research notes for this article record that the page was last updated on 11 September 2026. That matters because it gives your team a single official place to confirm planned downtime, live incidents and resolved problems before chasing software support or escalating to HMRC. It also helps you separate a CDS platform issue from a problem in your own declaration data.
The playbook below is written for importers, exporters, customs brokers and freight forwarders using CDS directly or through a broker, software provider or Community System Provider. It assumes you already understand the basics of a customs declaration; if not, start with our UK customs clearance step-by-step guide and our EORI number guide before turning this into an internal SOP.
The first five minutes
The first five minutes decide whether the incident stays controlled. Your aim is not to solve CDS immediately; it is to identify whether the problem is local, supplier-specific, border-system related or visible on HMRC’s own service pages. Assign one person to lead the incident log and one person to keep operations moving, even if that means telling commercial teams that the next update will come at a fixed time rather than instantly.
Start with GOV.UK. Check the CDS service availability and issues page for live incidents, planned maintenance, update history and any wording about whether declarations should be held, submitted later or expected to queue. The research notes include a planned CDS downtime from 7pm on Saturday 26 September 2026 to 8:30am on Sunday 27 September 2026, according to GOV.UK, and a separate 29 April 2026 window where HMRC said declarations should not be submitted during maintenance. Those examples show why the exact wording matters.
Then check your own chain. Look at your declaration software status page, CSP messages, port community system alerts, inventory-linking responses and any emails from your broker or agent. If only one user, badge, Government Gateway account or branch cannot submit, treat it as an access or permission issue first. If multiple traders, multiple branches or multiple software tenants see the same error at the same time, start incident handling while support teams investigate.
Classify the incident before escalating
Most CDS problems fall into one of five operating categories. Label the incident early so the team knows which evidence to collect and which service owner to contact. The label can change later, but it gives the first response a structure.
| Incident type | What it looks like | First owner |
|---|---|---|
| CDS platform availability | Submissions, amendments or notifications fail across users or software routes | Duty manager with software support |
| Access and authorisation | User cannot sign in, access CDS, use an EORI or reach a Customs Financial Account | Internal admin or agent relationship owner |
| Data or validation error | Declaration rejected with specific codes, missing fields or invalid procedure combinations | Declarant or broker |
| Linked government system | Licence, Defra, sanitary, phytosanitary or other permission message does not flow | Compliance lead and relevant authority |
| Inventory or border movement | Declaration exists but inventory status, arrival, release or movement message is blocked | CSP, port or carrier contact |
HMRC’s Developer Hub says CDS supports import and export declarations for goods moving into and out of the UK, including submission, notifications, supporting documents, declaration status, export inventory linking, arrival notifications and import movement validation for CSPs. That breadth is useful, but it also means a “CDS issue” can sit at several points in the chain. Do not assume the platform is unavailable simply because a single release message has not arrived.
Linked-system incidents need special care. GOV.UK Notice to Exporters 2026/06 records licence transmission issues between CDS and Department for Business and Trade electronic licensing systems that were identified during the night of 24 February 2026, escalated on 25 February and formally closed on 5 March 2026. In that kind of incident, resubmitting the same declaration repeatedly can create noise without solving the underlying licence flow.
Build the evidence pack
An evidence pack speeds up support and reduces the chance that HMRC, the software provider and the CSP each ask for different details. Create a shared incident note before you submit a form or email, then paste from that record. Keep the language factual: what was attempted, what happened, what message appeared, what goods are affected and whether anything is stuck at the border.
For imports, HMRC’s report-a-problem guidance says users may need a Local Reference Number, Movement Reference Number, error code and description of the problem. For exports, the same guidance says users may need DUCR, MUCR, movement details, inventory status message, software conversation ID, error code and problem description. Capture the exact values from the declaration record, not from a copied email thread.
Your minimum evidence pack should include:
- LRN and MRN for each affected import declaration, where available.
- DUCR, MUCR, movement details and inventory status for affected exports.
- EORI number, declarant badge or branch reference and the software route used.
- Error code, full error text, screenshot and timestamp in UK local time.
- Goods location, port, inventory system, carrier, vessel or flight reference.
- Whether the goods are physically stuck, time-sensitive, licensed or perishable.
- A timeline of attempted submissions, amendments, arrivals, releases and support contacts.
Screenshots are useful only if they show the timestamp, error wording and reference values. Avoid sending customer invoices or commercially sensitive documents unless the support route asks for them. If the issue touches valuation, origin or classification rather than system availability, keep it in the customs compliance route and use our commodity code and tariff classification guide to check whether the declaration content is the real cause.
Decide whether to wait, amend or escalate
The decision tree starts with the official status message. If GOV.UK says a maintenance window is underway and declarations should not be submitted, pause planned submissions unless there is a documented urgent route. If the page says a related reporting service is unavailable but CDS remains available, keep declarations moving and only defer the affected report. The research notes include a 9 July 2026 GOV.UK update stating that the Customs Data Report online service would be unavailable from 5pm on 10 July to 8am on 13 July 2026, while CDS itself would remain fully available and declarations could still be submitted.
If the declaration has a clear validation error, fix the data before escalating. Repeated submission of the same bad data wastes support time and can make your timeline harder to read. Common examples include invalid procedure code combinations, missing document codes, inconsistent valuation data, an EORI mismatch or licence references that do not align with the goods.
If the declaration is valid but the service route is failing, escalate through the correct chain. Software problems go first to the software provider because they can see API calls and conversation IDs. Inventory status and release problems usually need the CSP or port community system. HMRC should receive the issue when the evidence shows a CDS service problem, a cross-user failure, a problem the provider cannot resolve, or goods materially stuck because a CDS function is not behaving as expected.
For urgent cases, use the official HMRC problem reporting route and include the evidence pack in the format requested. GOV.UK says that after submitting the CDS problem form, users receive a confirmation email with a reference number; urgent problems receive a response within 2 hours and all other problems within 24 hours. Record that reference number in the incident log and in any customer update that depends on HMRC’s response.
Keep carriers and customers aligned
Good communication during a CDS incident is short, factual and timestamped. Do not promise release, refund storage charges or confirm a revised delivery slot until you know whether the declaration can move. A useful customer note says what is affected, what has been checked, who has the next action and when the next update will be sent.
For carriers and hauliers, focus on operational instructions. Tell them whether to hold at origin, wait off-port, keep the vehicle on standby, or avoid arriving until inventory status changes. If a container or trailer is already at the border, include the MRN, port reference and the exact point where the release process has stopped, but avoid forwarding full internal incident logs.
Commercial teams need a separate update. They should know whether the risk is a short system delay, a declaration correction, a licence problem or a border-release issue. This prevents account managers from turning an unresolved operational incident into an unrealistic customer promise.
If import VAT, deferment or postponed VAT accounting may be affected, flag finance early. CDS incidents can produce late postings, duplicate-looking entries, missing statements or delayed reconciliation. Our UK import VAT guide explains the finance records that usually need checking after import clearance.
After the service recovers
Do not close the incident when the status page says “resolved”. Close it when the affected consignments, declarations and accounts have reconciled. Build a recovery checklist that the duty manager signs off before the incident record is archived.
Start with declarations and movement status. Confirm each affected MRN has reached the expected status, amendments have been accepted, arrivals or releases have processed, and any rejected pre-lodged declarations have been corrected. The research notes record an April 2026 GOV.UK update warning that declarations pre-lodged before a 28 March update needed to be updated before arrival or they would be rejected, delaying goods release. That is the kind of detail a recovery check should catch.
Then reconcile money and controls. Check Customs Financial Account movements, deferment account usage, cash account balances, postponed VAT accounting records, duty and VAT charges, licences, certificates and inspection holds. If a broker handled the declaration, ask for a written summary of the final status and any entries that need finance follow-up.
Finally, update the SOP. Add the incident date, root cause category, references used, escalation contacts, what worked, what failed and which customers were affected. If the same issue appears again, the next duty manager should have a shorter route from first error to correct escalation.
Frequently Asked Questions
Where should I check first during a CDS outage?
Check HMRC’s Customs Declaration Service service availability and issues page first, because it is the official source for planned downtime and live or resolved service incidents. Then check your declaration software provider, CSP, port community system and broker messages. If those sources disagree, record the difference and keep the incident open until the declaration path is proven.
Should I keep submitting declarations during planned maintenance?
Only if the official maintenance notice says the relevant route remains available. Some downtime affects a reporting service while CDS declarations can still be submitted, while other maintenance windows say declarations should not be submitted. Follow the wording of the current GOV.UK notice rather than relying on a previous incident.
What details does HMRC need for a CDS problem report?
For imports, prepare the LRN, MRN, error code and a clear description of the problem. For exports, prepare the DUCR, MUCR, movement details, inventory status message, software conversation ID, error code and problem description. Include whether goods are stuck at the border and keep screenshots tied to timestamps.
How quickly will HMRC respond?
GOV.UK says that after you submit the CDS problem form, HMRC sends a confirmation email with a reference number. The same guidance says urgent problems receive a response within 2 hours and all other problems within 24 hours. Use that reference number in all follow-up communication.
Is every release delay a CDS service issue?
No. A release delay can come from bad declaration data, a missing licence, a CSP inventory issue, a carrier or port hold, an inspection, a deferment account problem or a wider CDS incident. Classify the issue before escalating so the right owner receives the evidence pack first.
Should importers or brokers own the incident?
The party with operational control of the declaration should own the incident log, but the importer remains accountable for the movement and customer impact. If a broker submits the declaration, agree in advance who checks GOV.UK, who contacts HMRC, who speaks to the carrier and who updates the customer. Write that split into your customs SOP before the next incident.