Diagnose the layer before the symptom
Almost every TRACES NT access issue resolves to one of four causes: an unactioned approval, an EU Login credential problem, a duplicate organisation record, or a missing administrator. Identifying which layer failed saves days of guessing.
Failure one: status stuck on pending
Pending means the approver has not actioned the request yet. For an existing organisation that is your internal administrator. For a new organisation it is the competent authority. Contact the approver directly. Resubmitting creates noise without changing the outcome, which is set out clearly in this TRACES NT login troubleshooting guide.
Failure two: cannot log in
This is usually EU Login rather than TRACES NT. Reset the password through the EU Login portal, then confirm two-factor authentication points at a phone number you still control. Staff who changed devices without updating 2FA are a frequent cause.
Failure three: duplicate organisations
These appear when a colleague creates a new entry instead of joining the existing one. The result is split records and confused approvals. Correction requires competent authority intervention to merge or amend, so raise it as soon as you notice.
Failure four: no administrator left
If your only administrator leaves the business, internal approvals stop. Request administrator rights through the competent authority, then keep a minimum of two administrators permanently.
Escalation path
The TRACES helpdesk is reachable through the Help menu inside the platform. Competent authorities handle organisation level approvals.
Find out how iCustoms catches submission errors before a border control post does. Watch a demo.
Top comments (0)