When NCTS rejects a declaration, the movement is held until you resolve it. The fastest path is to work through the usual causes in order rather than guessing. Remember, a rejection is a validation failure, not a fine.
The rejection checklist
Check for missing house consignments first. Then confirm commodity codes are complete and valid. Verify the guarantee reference exists and is active. Confirm the destination office is recognised. Finally, review safety and security data for gaps.
When a fix is not enough
If the same rejection keeps returning, the problem is upstream in your data or process. Fixing the symptom repeatedly can still leave an accepted declaration inaccurate, which is where penalties start. This guide to fixing NCTS declaration rejections explains when a recurring error becomes a compliance risk.
Document as you troubleshoot
Record each rejection cause and resolution. That log is useful operationally and supports a self-correction case if HMRC reviews your record.
FAQ
Does resubmitting fix everything? Only if the root cause is fixed, not just the field.
Can rejections become penalties? If the underlying data stays wrong on accepted declarations, yes.
Root-cause fixes beat repeated resubmissions. See how validation pinpoints the real issue. Watch a demo.
