UUM&DS
Troubleshooting.
Login successful, but access denied? Start by identifying where the process breaks down.
Access to EU customs applications may depend on authentication, organisational context, user authorisations and application-specific requirements. A problem at one stage can prevent access even when the previous stages work correctly.
Proving who you are does not automatically establish which customs services or functions you are permitted to use.
Identify the failed check before changing credentials or permissions.
Where does access fail?
Start with the symptom you can observe.
Different access problems require different investigations. Select the situation that best matches what happens when you try to use the customs application.
These categories are diagnostic starting points, not official UUM&DS error classifications. A single symptom may have several causes.
I cannot complete sign-in.
The user cannot successfully complete the authentication process required by the service.
Initial checks
Am I using the correct sign-in route?
Confirm that you opened the intended customs application through its official entry point. Depending on the service and Member State, authentication may involve EU Login or a national identity system.
Can I complete the required authentication method?
Check whether the authentication method requested by the identity provider is available and working. Follow that provider’s official recovery instructions if a device, credential or verification method is unavailable.
Does the problem occur before I reach the customs service?
Note whether the failure occurs on the identity provider’s page, during redirection or after returning to the customs application. This distinction helps identify the appropriate support channel.
I can sign in, but my organisation is not available.
Authentication succeeds, but the expected economic operator or business context is not recognised or selectable where the service requires one.
Initial checks
Is the correct economic operator involved?
Confirm the organisation and identifiers relevant to the service, including EORI where applicable. An EORI number alone does not establish every application access right.
Is my identity linked to the relevant business context?
The application may require an organisational association, registration or recognised authorisation. Verify the relevant arrangement through the designated access-management procedure.
Am I acting for another organisation?
If you are accessing the service for a client, check whether the necessary digital delegation or equivalent access arrangement is supported and effective.
My identity is recognised, but access is denied.
The sign-in process works, yet the application refuses access to a service, area or operation.
Initial checks
Do I have the required service permissions?
Check whether the necessary authorisation or role has been assigned and recognised by the relevant application. The precise role structure depends on the service.
Am I using the intended organisational context?
Where an application supports more than one business context, verify that the selected organisation is the one authorised for the activity.
Has an administrator or authority confirmed the access?
Some access arrangements depend on approval, registration or administrative action. Check the applicable procedure rather than assuming that successful authentication completes it.
I can access the service, but a function is unavailable.
The user reaches the customs application, but an expected function cannot be used.
Initial checks
Is the function available for my role?
Some applications distinguish between viewing information, preparing submissions and performing administrative actions. Confirm the permissions required for the specific function.
Are additional service conditions required?
The function may depend on service-specific eligibility, registrations, authorisations or procedural conditions beyond basic user access.
Could the application itself be unavailable?
Check official service notices, maintenance information and support guidance. A technical interruption should not be confused with a missing delegation or user role.
An “access denied” message, for example, may reflect missing permissions, an incorrect organisational context or a service-specific condition. Use the checks above to narrow the investigation before escalating the issue.
Sign-in failed?
Identify the point of failure.
An authentication problem can occur before credentials are accepted, during identity verification or when the user returns to the customs application. The location of the failure is often more useful than the error message alone.
Three checkpoints to distinguish.
Conceptual flow. The actual sequence depends on the identity provider and customs service.
Account sign-in
The user reaches the expected sign-in service and attempts to authenticate.
Can you access the account?Required verification
The user completes any additional authentication method required for the service.
Can you complete verification?Return to customs service
The authentication result is processed as the user returns to the intended application.
Does the service open correctly?EU Login is used in relevant EU service access arrangements, but national identity and access-management systems may also be involved. Do not assume every customs application uses an identical authentication route.
Match the symptom to the next check.
These examples help narrow the investigation. They do not establish the definitive cause of an error.
| Observed symptom | What to investigate | Appropriate next action |
|---|---|---|
| Sign-in page does not load | Official entry point, browser connectivity and published service availability notices. | Retry through the official service link and check provider status information. |
| Credentials are rejected | Correct identity provider, account identifier and authentication requirements. | Follow the provider’s official account recovery process where applicable. |
| Verification cannot be completed | Required authentication method, registered device and recovery options. | Use the supported recovery or authentication-method management procedure. |
| Sign-in succeeds, but redirection fails | Application entry point, session handling and service-side integration. | Record the failure stage and consult the target application’s support guidance. |
| Login works, but access is denied | Organisational context, permissions and application eligibility. | Continue with authorisation diagnostics rather than repeatedly resetting credentials. |
Investigate without making the problem worse.
Use a controlled sequence to distinguish a local browser issue from an identity or application problem.
Start from the official application link
Avoid outdated bookmarks or links from unverified messages. Confirm that the intended customs service and identity provider are being used.
Record the exact failure stage
Note whether the error appears before sign-in, during verification or after the return to the customs application.
Check official service notices
Review available maintenance announcements or incident notices before assuming that the account configuration is incorrect.
Try a controlled browser check
If permitted by organisational security policy, test a supported browser or a fresh browser session. Avoid deleting authentication settings or stored credentials without understanding the impact.
Escalate to the correct support channel
Identity-provider problems and customs-application errors may require different support teams. Use the official instructions for the component where the failure occurs.
Useful evidence. No sensitive credentials.
A concise technical description helps the responsible support service investigate the problem.
- Exact customs application involved
- Date and approximate time of the failure
- Stage at which the process stops
- Error text or reference code, if displayed
- Browser and operating system
- Relevant organisation details, only through an authorised support channel
- Passwords or recovery codes
- One-time verification codes
- Authentication tokens or session cookies
- Private keys or digital signature secrets
- Unredacted sensitive personal or commercial data
Screenshots can contain personal data, session information or confidential customs records. Review and redact them before sharing, and use only the authorised support channel.
Use the correct identity support route.
EU Login has its own authentication and account-management procedures. For national authentication systems, consult the relevant Member State authority or identity provider.
Login works. Access does not.
Check the business context behind the user.
A successfully authenticated identity may still lack the organisational association, role or delegation required to use a customs service. The next step is to identify which relationship or permission is missing.
Four elements to verify.
A conceptual diagnostic model, not a universal technical architecture for every customs service.
Who signed in?
For which operator?
Which actions are permitted?
Is access accepted?
Not every application exposes these elements separately to the user. The purpose of this model is to locate the area requiring investigation.
What does the access problem suggest?
Use the observed behaviour to select the next verification. These are possible causes, not definitive diagnoses.
| Observed problem | Possible explanation | What to verify |
|---|---|---|
| Organisation not available | The user may not be associated with the expected business context in the relevant service. | Organisation registration, identity association and applicable access procedure. |
| Correct organisation, missing function | The recognised role or permission may not cover the intended activity. | Service-specific roles, assigned rights and function requirements. |
| One client works, another does not | The relevant delegation or access relationship may differ between the two clients. | Each client’s independent access arrangement and applicable permissions. |
| Access previously worked | A role, delegation, registration or service condition may have changed. | Recent administrative changes, withdrawal of access and service notices. |
| Administrator can access, employee cannot | User-level permissions or organisational assignments may be different. | Individual access rights and supported role-assignment procedures. |
| Delegation exists, but access is refused | The delegation may not cover the service or operation, or may not be effective in the target application. | Scope, recognition, validity and additional service conditions. |
Three situations that require different fixes.
Similar access errors can originate from different organisational relationships.
Employee of the economic operator
The employee can authenticate, but cannot use the required customs function.
InvestigateWhether the user’s organisational association and service permissions have been correctly established.
External customs service provider
The provider accesses its own environment but cannot operate for a particular client.
InvestigateWhether a supported delegation or equivalent access arrangement exists for that client and service.
Existing user with changed responsibilities
Access was previously available, but the user’s role or responsibilities have changed.
InvestigateWhether permissions remain appropriate and whether an authorised administrator must update the assignment.
An EORI number is not a user permission.
EORI identifies economic operators and other persons where required under EU customs rules. Having a valid EORI number does not automatically grant an individual access to a customs application, assign a user role or establish a digital delegation.
Escalate to the party responsible for the missing element.
Different access problems may require action from different administrators or authorities.
Organisation administrator
Where supported, verify the user’s internal association and available role assignments.
Principal economic operator
Confirm whether the intended external relationship and access arrangement have been authorised.
National customs authority
Consult the competent authority where national registration, access approval or delegation procedures are involved.
Application support service
Report cases where the expected access relationship appears correct but is not recognised by the service.
Still unable to access the service?
Escalate with evidence, not assumptions.
When initial identity, organisation and permission checks do not resolve the issue, a structured investigation can help distinguish a local problem from an access-management or customs-application failure.
Look for differences that narrow the cause.
Intermittent access
The same user sometimes accesses the service successfully and sometimes receives an error.
Redirection loop
Authentication appears to complete, but the browser repeatedly returns to sign-in or fails to open the application.
Different users, different results
Two users within the same organisation experience different access outcomes.
Application error after login
The user reaches the target customs service, but an operation fails or an unexpected application error appears.
Four steps from observation to resolution.
Follow the sequence without repeatedly changing credentials, roles or delegation settings.
Document the exact failure
Record the affected application, attempted action, approximate time, displayed error and point at which the process stops.
Change one test condition at a time
Where permitted, compare an approved browser session, official entry point or another authorised user. Do not share accounts or use another person’s credentials.
Identify the responsible component
Determine whether the evidence points primarily to authentication, organisational access, permissions or the target application.
Contact the appropriate support service
Submit a concise description through the official support channel, including only information necessary for the investigation.
Who should receive the issue?
Support responsibilities vary by service and Member State. Use this routing guide to identify the likely starting point.
| Problem area | Likely starting point | Evidence to provide |
|---|---|---|
| EU Login account or verification | Official EU Login support or recovery guidance | Failure stage, time and non-sensitive error details |
| National authentication | Relevant national identity provider or designated authority | Authentication route and observed failure |
| Organisation or user permissions | Authorised administrator or competent customs authority | Business context, intended service and missing access |
| Delegated access | Principal organisation and applicable delegation support channel | Relevant relationship, service and approved scope |
| Customs application malfunction | Official support channel for the target application | Operation, time, error reference and reproducible steps |
Prepare a clear incident report.
Fill in the relevant details and copy the report into your organisation’s approved support process. This worksheet does not send or store the information on a server.
Never enter passwords, verification codes, access tokens, private keys or confidential declarations into this worksheet. Review the copied text before sharing it through an authorised support channel.
Use the service’s published support guidance.
The European Commission provides information about UUM&DS and online customs services. National access arrangements may require consultation with the competent Member State authority.
Still have questions?
Find the right answer and next step.
These frequently asked questions address common EU customs authentication, authorisation and delegation issues. Actual access procedures may vary by application and Member State.
Understand the problem before changing access settings.
A successful sign-in does not always mean that the user has permission to operate within the selected customs application.
Authentication confirms an identity. Authorisation determines which services and functions that identity may access in the relevant context.
Why can I log in to EU Login but not access a customs application?
EU Login authentication does not automatically grant access to every customs application. The service may also require an organisational association, a recognised role, delegation or additional registration. Check the specific application’s access requirements.
What should I check when UUM&DS access is denied?
First identify whether authentication completed successfully. Then verify the relevant organisation, recognised permissions, delegation arrangements where applicable, and the target application’s own requirements. Record the exact error and failure stage before contacting support.
Does a valid EORI number automatically allow customs system access?
No. EORI is an economic operator identification system. A valid EORI number does not automatically assign individual user permissions or provide access to every electronic customs service.
Why can one employee access a service while another cannot?
Individual users may have different organisational associations, permissions or roles. Compare the approved access arrangements for each user without sharing accounts or authentication credentials.
Why can a customs representative access one client’s information but not another’s?
Client-specific access arrangements may differ. Check whether the relevant delegation or equivalent authorisation is recognised for the affected client and service. Access associated with one client should not be assumed to cover another.
What can cause a login redirection loop?
Possible causes include session handling problems, an outdated application entry point or an issue in the authentication handoff. Use the official service link, review service notices and record where the redirection fails. The precise cause requires investigation.
Should I reset my password when access is denied?
Not automatically. If authentication succeeds but the application refuses access, the issue may concern permissions or organisational context rather than credentials. Use password recovery only when the symptoms indicate an account authentication problem.
Who should I contact for UUM&DS access problems?
The correct support channel depends on the failure and application. EU Login account problems may require identity-provider support. Organisational access and delegation may involve an administrator or competent national authority. Application errors should be reported through the relevant service’s official support route.
Choose the next investigation.
A practical summary of the diagnostic process covered in this guide.
Identity provider, verification method and application redirection.
Organisational association, registration and delegation.
User roles, recognised rights and service authorisations.
Collect relevant evidence and contact the correct official support channel.
Start with authoritative information.
The resources below provide official entry points for EU customs digital services and authentication.
Official information on the UUM&DS framework and its role in access to relevant EU customs electronic services.
ACCESS MANAGEMENTOfficial authentication entry point for European Commission services using EU Login.
AUTHENTICATIONEuropean Commission information about online services and electronic customs resources.
CUSTOMS APPLICATIONSFor service-specific errors, consult the target application’s documentation. National identity, registration and delegation procedures may require support from the competent Member State authority.
Find the failed access condition before attempting to fix it.
Identify the failure stage, verify the relevant identity and permissions, examine service-specific conditions and escalate with useful evidence when the problem remains unresolved.
Customs Explorer provides educational guidance and does not operate EU customs authentication or authorisation services. Diagnostic examples are illustrative; official procedures and support channels take precedence.