DEV Community: Kristi Hampson

NCTS or CDS Held Your Load: A Troubleshooting Order

Kristi Hampson — Mon, 21 Sep 2026 07:27:39 +0000

When a trailer is held, the fastest recovery comes from checking the right system first.

First check: which declaration is missing

Direct clearance issues sit in CDS. Transit issues sit in NCTS. The NCTS vs CDS distinction tells you where to look before you open either dashboard.

Second check: GMR pairing

At RoRo pre-lodgement, the Goods Movement Reference needs both declarations valid at creation. A missing NCTS entry is the usual cause even when CDS is clean.

Third check: data mismatch

Compare classification, valuation and origin between the two records. A commodity code amended in one system may still be wrong in the other.

Fourth check: discharge status

An NCTS movement not yet discharged will not release the goods at destination even if CDS is settled.

Fifth check: guarantee coverage

Check the guarantee reference is live and sufficient for the movement.

Ready to remove the hunt from the process? Watch a demo.

Troubleshooting NCTS5 Declaration Rejections

Kristi Hampson — Fri, 18 Sep 2026 07:20:58 +0000

What causes most NCTS rejections?

Most rejections come from four sources: missing house consignments, incomplete commodity codes, guarantee mismatches, and partial safety and security data. Reading the functional error message correctly narrows the fix in seconds.

Reading functional errors

Every rejection returns a rule identifier and field pointer. The rule identifier maps to the NCTS5 rule library. The field pointer identifies the exact node that failed.

Fix 1: Structural errors

If the pointer identifies a goods item without a parent house consignment, add the missing layer. Count invoices and match them to house consignments. This how to build an NCTS declaration breakdown shows the correct nesting order.

Fix 2: Commodity code errors

Codes below six digits or missing entirely fail validation. Replace descriptions with the correct HS code from your reference library.

Fix 3: Guarantee errors

EORI mismatches, exhausted balances, or routes outside the guarantee binding conditions all trigger refusal. Verify the guarantee record before resubmitting.

Fix 4: Safety and security errors

If safety and security data is partially populated, either complete every required field or remove the entire dataset from the declaration.

Want automated error resolution built into filing? Watch a demo.

Troubleshooting Stuck EU Transit Movements in NCTS

Kristi Hampson — Thu, 17 Sep 2026 07:27:10 +0000

A stuck movement almost always fails in one of three places. Diagnose in that order and you save hours.

1. Declaration rejects

Check guarantee reference format, EORI validity and commodity code consistency. The authorised consignee procedure explains where the office of departure rules bite hardest for consignor-authorised traders.

2. Missing office of transit notifications

If a border-crossing notification is not received within the expected window, the movement is not discharged and the guarantee stays committed. Confirm the office of transit code is actually a designated CTC post and that the driver presented at the correct location.

3. No discharge at destination

The office of destination must send arrival notification, unloading remarks and discharge. Missing any of the three means the movement is not closed.

A quick triage checklist

MRN state in your system versus NCTS state.
Age of the movement against your discharge SLA.
Guarantee headroom versus open MRNs.
Last message received per MRN. ### When to raise an incident

Seal break, route change, delay beyond the acceptable window. All belong at the Office of Incident, not the Office of Destination.

Cut stuck movements to near zero. Watch a demo.

Troubleshooting UK Transit: Why Your GMR Keeps Failing

Kristi Hampson — Wed, 16 Sep 2026 07:51:27 +0000

First, isolate the failure

A GMR failure is not one problem. It is the visible symptom of an upstream gap. Read the port response carefully — the error usually points at the missing reference.

Common causes and fixes

Export MRN not lodged in CDS before GMR assembly.
Transit MRN not issued because Phase 5 rejected the payload — often a missing house consignment or a five-digit commodity code where six are required.
Import declaration not pre-lodged on the EU side.
EORI mismatch between the guarantee holder and the declared party. Each of these has a documented fix in this transit customs failure points explained breakdown.

The pattern behind repeated failures

Repeated GMR failures are almost always a workflow problem, not a data problem. Committing the GMR before all four gates have closed produces stub records that fail with different error messages depending on which gate is missing.

FAQ

Why does the same trailer sometimes fail and sometimes pass?
Timing. If a transit MRN is issued after the GMR is committed, the GMR is not automatically updated.

Does re-submitting fix a stub GMR?
Only if the underlying gap is closed first. Otherwise it fails again with the same class of error.

Cut GMR failures at source. Watch a demo to see how iCustoms sequences gates.

Troubleshooting NCTS Phase 5 Rejections: An IE056 Field-Pointer Playbook

Kristi Hampson — Tue, 15 Sep 2026 07:51:50 +0000

IE056 in one sentence

IE056 is the office of departure returning a set of functional error codes with field pointers. The pointer tells you exactly which node in your IE015 was rejected.

The six that eat your time

Missing house consignment level — parent path is null when a goods item is attached.
Invalid or missing HS code — fewer than six digits or an unrecognised subheading.
Guarantee not valid — GRN, access code, EORI or balance failure.
Unrecognised office of destination — decommissioned or mistyped reference.
Incomplete S&S dataset — claimed but missing mandatory fields.
Party identity mismatch — EORI does not match declared party. For the full technical context, see the iCustoms NCTS 5 error handling breakdown.

Debug method

Parse the IE056 pointer. Load the offending node. Diff against the schema. Repair, resubmit. Do not re-issue IE015 with unrelated changes bundled in.

Remove the guesswork

Watch a demo to see IE056 pointers surfaced in plain English.

Troubleshooting TSS AI: Why Your Declarations Are Still Failing

Kristi Hampson — Mon, 14 Sep 2026 07:39:07 +0000

Rejections are a diagnostic

Post-AI rejections almost always come from the same handful of causes. Diagnose them with the four-technique lens.

Extraction is failing

Check the source documents. Photographs of paperwork, mixed scans, and non-standard layouts kill extraction accuracy. Send suppliers a template. Push for digital-native invoices.

Validation is thin

If your platform validates format but not TSS-specific consistency and caps, you will see server-side rejections. Ask your vendor for the full rule catalogue and add missing checks.

Classification is being auto-accepted

Model suggestions with high confidence are still suggestions. If nobody is confirming first-time products, expect challenges. Use BTI or ATaR where legal certainty is needed, as covered in the BTI vs ATaR classification guide.

Reuse is carrying forward stale data

Products drift. A material change or a component swap can move the commodity code. Version product records and force review on material changes.

People are being bypassed

If low-confidence fields are auto-submitted because the review queue is under-staffed, you have a workflow problem, not an AI problem.

Data quality upstream is unresolved

"Assorted parts" will fail every time. Fix the description at source, then reprocess.

Peak surges are unmanaged

Deadline weeks expose fragile queues. Pre-warm reviewers and run rehearsals.

Run a diagnostic on your own flow. Watch a demo.

Troubleshooting Common TSS Agent Account Issues

Kristi Hampson — Fri, 11 Sep 2026 06:54:44 +0000

MFA at every login

Agent accounts require authenticator apps and codes at every login. Shift-based teams need shared service processes or per-user credentials with named recovery, not a shared phone in a drawer.

Missing case visibility

Agents see only cases they raised and declarations they submitted. If a colleague raised the case, you cannot see it under the same client without re-raising. Team assignment must be planned deliberately.

Deauthorisation blind spots

If a client withdraws authorisation, access to open cases disappears. This TSS agent account guide covers the automatic transfer of open cases back to the trader account and the operational handover this implies.

UKIMS mismatch on submission

The importer EORI on every declaration must match that trader's UKIMS authorisation. Mismatch rejections often trace back to a shared configuration inherited from the agent, not the trader.

The 99-item ceiling

If a submission fails on line count, split at the load level, not at the declaration level, and re-run through the same reference chain. Ad-hoc splitting inside the declaration creates reconciliation problems downstream.

Assisted Completion Service unavailable

The Assisted Completion Service is not available to customs agents or to traders using intermediaries. Escalation goes through TSS support directly, not through the assisted route.

Handle these issues before they hit month-end. Watch a demo.

Troubleshooting a TSS API Rollout: The Five Recurring Failures

Kristi Hampson — Thu, 10 Sep 2026 09:10:16 +0000

Common failures come from the same places

TSS API projects fail for a small number of reasons. Recognise them early and you save weeks of rework. The TSS declaration workflow options breaks these down alongside the decision framework.

Failure one: unauthoritative product data

If product records are spread across several systems, the mapping will contradict itself. Consolidate first.

Failure two: no rejection design

Success flows through untested. Rejections queue up silently until a deadline is missed. Design the rejection path with the same rigour as the submission path.

Failure three: parallel run cut short

Teams end parallel running as soon as the API works for the easy cases. The full month cycle needs to run cleanly before the portal is decommissioned.

Failure four: peak load surprise

Volume in the test environment does not match volume around the tenth of the month. Load-test at peak, not at baseline.

Failure five: no owner for exceptions

Automated does not mean owner-less. Someone has to own the queue of unresolved rejections, or they will not resolve.

Fix pattern

Fix the data, fix the queue, fix the exception owner, and only then look at the code.

Avoid these failures with a proven TSS integration setup. Watch a demo.

Debugging Failed TSS Declarations: A Field Guide

Kristi Hampson — Wed, 09 Sep 2026 07:44:33 +0000

Rejected declarations rarely fail for exotic reasons. Five categories cover most of them.

1. Commodity code issues

Wrong digit count, expired codes or codes that do not exist in the current tariff. Fix in the product master, not per declaration.

2. Document code mismatches

The document code claimed does not reconcile with the current Tariff Requirements. This is one of the most valuable validations to catch pre-submission, as covered in this TSS validation guide.

3. Mass and package count disagreement

Gross mass, net mass and package count on the declaration do not match the invoice or packing list. Usually a data extraction fault, not a customs one.

4. Missing or invalid licences

Certificate and licence references that do not match, or scheme authorisation numbers invalid for the movement date.

5. Party data drift

Party details out of sync with authorisations. Fixed once at the party master, not at the submission.

See how iCustoms surfaces and routes these failures. Watch a demo.

Debugging a GMR: A Field Checklist

Kristi Hampson — Tue, 08 Sep 2026 07:22:28 +0000

The symptom

Driver at the port. GMR rejected. Loud phone call.

Step 1: Read the reference formats

Was any XI-prefixed MRN entered as a customs declaration on GVMS? That is the most common cause. XI prefix means Entry in Declarant's Records, plus the trader's EORI.

Step 2: Check trailer and vehicle registration match

Any trailer swap in the last hours? Update the GMR before boarding. Nothing can be changed after the boarding barcode is scanned.

Step 3: Reconcile manifest against consignments on the GMR

For groupage, one missing MRN blocks the whole trailer. Count them.

Step 4: Verify non-TSS consignments have safety and security data

If an MRN was added without the S&S data, GVMS accepts the reference but rejects the movement.

Step 5: Check whether upstream declarations actually exist

A GMR cannot be built without underlying MRNs. If TSS has not issued them, the reference build silently produces nothing.

A longer walkthrough of these failure modes is in this GMR troubleshooting field guide.

Step 6: Confirm inspection status after embarkation

Status changes after the ferry leaves. Missing this is how inspection requirements are missed on arrival.

Cut debugging time by connecting TSS declarations directly to GMR building. Watch a demo.

Troubleshooting Northern Ireland ENS Rejections and Delays

Kristi Hampson — Mon, 07 Sep 2026 08:14:09 +0000

The five most common ENS failures

Non-submission.
Late submission.
Description rejection.
EORI error.
Data mismatch between ENS and customs declaration. Each has a specific cause and a specific fix, walked through in the Northern Ireland safety and security filings explainer.

Non-submission

Cause: each party assumes the other is filing.
Fix: written lane agreement stating carrier, trader, and forwarder roles.

Late submission

Cause: treated as customs work rather than a transport-side task.
Fix: bind ENS to the transport booking, not the customs deadline.

Description rejection

Cause: generic or prohibited wording.
Fix: approved plain-language descriptions from a shared library.

EORI error

Cause: GB EORI used instead of XI.
Fix: check identifier at booking, not submission.

Data mismatch

Cause: corrections applied only to the customs declaration, not the ENS.
Fix: correct at the source and cascade to every filing.

See how automated validation catches these before they hit ICS2 — Watch a demo.

Debugging TSS Rejections: Common Failure Modes and Fixes

Kristi Hampson — Fri, 04 Sep 2026 07:01:26 +0000

Read the Rejection First

Every TSS rejection points at a data problem. Treat it as a failing test, not a bureaucratic setback. The message will name a field. Start there.

Common Failure Modes

Description too vague. Fix: rewrite against the five-question standard and store the compliant version in the product master.

Commodity code invalid or wrong digit count. Fix: reverify against the current tariff and set the digit count by goods category.

Weight mismatch. Fix: confirm gross mass > net mass and both match the packing list.

Value mismatch. Fix: sum item values and reconcile to the invoice total; check currency.

Party mismatch. Fix: standardise identifiers and store one canonical spelling per party.

Preference claim without evidence. Fix: remove the claim or attach the evidence.

The TSS goods description standard covers the description fix in the most detail.

Root Cause, Not Line Fix

Fixing the line clears the shipment. Fixing the source stops the pattern. Push every rejection back to the record it came from.

Turn rejections into structural fixes, not one-off patches. Watch a demo.