DEV Community

Cover image for Troubleshooting Common TSS Agent Account Issues
Kristi Hampson
Kristi Hampson

Posted on

Troubleshooting Common TSS Agent Account Issues

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.

Top comments (0)