Customs Explorer
⌕

Customs Explorer

PoUS troubleshooting

EU DIGITAL CUSTOMS / OPERATIONAL GUIDANCE

PoUS
Troubleshooting.

Submission rejected? Validation failed? Unexpected system response?

Understand common problems affecting Proof of Union Status submissions, distinguish technical errors from customs processing outcomes, and identify the appropriate next steps.

Practical guidance · Not an official EU diagnostic service
PoUS / DIAGNOSTIC OVERVIEW ◇
SUBMISSION REVIEW
!
Issue detected Illustrative diagnostic scenario
✓
Operator identification Review completed
!
Submitted data Further verification required
···
Processing outcome Check actual system response
DIAGNOSTIC PRINCIPLE Identify the cause before resubmitting.
✓
Resolve systematically Data · Access · Procedure · System
QUICK ANSWER ?

What should you do when a PoUS submission fails? First determine whether the problem concerns technical transmission, data validation, user permissions or customs processing. Review the actual response and existing records before correcting or resubmitting information. An unsuccessful-looking screen does not, by itself, prove that no submission was received.

01 / INTERACTIVE DIAGNOSTIC

Start with the symptom.
Find the next step.

Select the issue that most closely matches your situation. Customs Explorer will display a practical investigation path, helping you distinguish data problems from access, transmission and customs processing issues.

STEP 01

What happened?

Choose the closest description.

i

These are diagnostic categories, not official PoUS message names or error codes.

STEP 02 / DIAGNOSTIC RESULT GUIDED CHECK
!
DATA & VALIDATION

Review the submitted data.

A validation problem may indicate missing information, an incompatible value or inconsistency with the applicable dataset.

INVESTIGATION PATH 3 CHECKS
  1. 01

    Read the actual validation response and identify the affected information.

  2. 02

    Compare the submitted particulars with the applicable PoUS data requirements.

  3. 03

    Correct the underlying issue using the permitted procedure before resubmitting.

RECOMMENDED NEXT ACTION

Check the specific validation feedback before making changes.

!
Important: identify the actual system outcome before resubmitting.

A missing response, a validation rejection and a customs decision are different situations. Avoid creating duplicate requests until you have checked whether the original submission was received.

02 / ERROR REFERENCE

Common problems.
Clear investigation paths.

Use this operational reference to investigate recurring PoUS difficulties. The examples describe problem categories rather than official system error messages. Always follow the actual response and instructions issued through the relevant customs system.

PRIMARY INVESTIGATION ROUTE
Operator review Access / technical support Customs involvement
01
Mandatory information missing Incomplete submission data
Identify the missing field or data element.
Operator review
POSSIBLE CAUSE

Required information may have been omitted or not supplied in the expected structure.

RECOMMENDED CHECK

Compare the submitted information with the applicable dataset and the actual validation feedback.

NEXT STEP

Complete the information and use the appropriate correction or resubmission procedure.

02
Inconsistent goods particulars Conflicting references or quantities
Compare the proof data with supporting records.
Operator review
POSSIBLE CAUSE

Descriptions, quantities, transport references or other particulars may not align with the underlying commercial documentation.

RECOMMENDED CHECK

Reconcile the proof particulars with the relevant commercial, transport and customs records.

NEXT STEP

Determine whether the record can be corrected or whether a different procedure is required.

03
Incorrect proof type selected T2L, T2LF or CGM context
Verify the movement and applicable proof method.
Operator review
POSSIBLE CAUSE

The selected proof may not correspond to the territorial, transport or procedural circumstances.

RECOMMENDED CHECK

Review the movement, relevant fiscal territory rules and the conditions for the intended proof type.

NEXT STEP

Confirm the correct method before preparing a new submission. Do not assume different proof types are interchangeable.

04
Authentication or login failure Portal access unavailable
Check identity, login route and account configuration.
Access / support
POSSIBLE CAUSE

The authentication process, account configuration or selected access route may not be working as expected.

RECOMMENDED CHECK

Verify the applicable EU or national access mechanism, user credentials and account configuration.

NEXT STEP

Follow the relevant authentication support process rather than changing the customs submission data.

05
Insufficient permissions Role, representation or authorisation
Verify permissions and the applicable authorisation.
Access / support
POSSIBLE CAUSE

The user may lack the required application permissions, representation rights or customs authorisation for the intended action.

RECOMMENDED CHECK

Distinguish portal permissions from customs authorisations. An EORI number alone does not establish entitlement to every simplified procedure.

NEXT STEP

Resolve the relevant permission or authorisation issue with the competent access administrator or customs authority.

06
Timeout or missing acknowledgement Transmission outcome uncertain
Determine whether the original request was received.
Access / support
POSSIBLE CAUSE

A network interruption, unavailable response or technical problem may have affected the acknowledgement without proving that transmission failed.

RECOMMENDED CHECK

Review available submission history, references and acknowledgements before attempting another transmission.

NEXT STEP

Use the relevant support or recovery process if the outcome cannot be established. Avoid automatic duplicate submissions.

07
Customs endorsement not completed Request awaiting customs processing
Review the processing information and customs messages.
Customs involvement
POSSIBLE CAUSE

The applicable procedure may require customs endorsement or additional examination before registration.

RECOMMENDED CHECK

Check the actual processing outcome, outstanding requests and whether further information is required.

NEXT STEP

Follow the customs instructions or contact the competent office where appropriate. Do not treat processing time alone as evidence of rejection.

08
MRN or proof verification issue Reference not found or proof questioned
Verify the reference and actual registration status.
Customs involvement
POSSIBLE CAUSE

The reference may be incorrect, the proof may not be registered, or a customs verification issue may need resolution.

RECOMMENDED CHECK

Confirm the MRN, proof particulars, registration outcome and applicable presentation requirements.

NEXT STEP

Correct reference errors where permitted. Refer unresolved registration or verification issues to the appropriate customs channel.

↗
RELATED OPERATIONAL GUIDE

Investigating a validation problem?

Continue with the dedicated PoUS Validation guide for a more detailed explanation of data checks and processing outcomes.

Explore PoUS Validation
03 / RECOVERY & RESUBMISSION

An error is not
an invitation to resend.

Before correcting or repeating a PoUS submission, establish what happened to the original request. The recovery path depends on whether the information was rejected, received, registered or remains subject to customs processing.

THE RECOVERY DECISION

What happened to the original request?

Follow the actual response and available system records. The diagram below is an investigative framework, not an official PoUS status model.

START HERE Submission problem detected Review available feedback and records
KEY QUESTION Can you establish the actual outcome?
YES — OUTCOME KNOWN
✓

Follow the recorded outcome

Determine whether the request was rejected, remains under processing or resulted in a registered proof.

Use the procedure appropriate to that outcome.
NO — OUTCOME UNCERTAIN
?

Investigate before repeating

Check submission history, acknowledgements and available references. Contact the appropriate support channel if needed.

Do not assume a timeout means non-receipt.
RECOVERY SCENARIOS

Four situations. Four different approaches.

Identify the scenario that corresponds to the available evidence before taking corrective action.

01 / VALIDATION !

Data rejected before acceptance

The response identifies a validation problem preventing the request from proceeding.

APPROACH Identify the affected data, correct the cause and follow the permitted submission route. PoUS Validation
02 / TRANSMISSION ⇄

Technical outcome uncertain

A timeout or interrupted connection occurred without a conclusive response.

APPROACH Investigate whether the original request was received before attempting another transmission. PoUS Submissions
03 / CUSTOMS PROCESSING ◷

Endorsement still outstanding

The request may require customs processing before registration can be completed.

APPROACH Review customs communications and follow the competent office’s instructions where applicable. Submission process
04 / REGISTERED PROOF #

Proof already registered

A registered proof exists, but an error, discrepancy or presentation issue remains.

APPROACH Check the existing proof and applicable correction or customs procedure before creating another record. Proof validation
PRE-RESUBMISSION CONTROL

Five checks before taking action.

Use this local checklist to organise your review. It does not query PoUS, submit information or verify any customs record.

REVIEW PROGRESS 0 / 5
Complete the review before deciding how to proceed.
!
Completion of the checklist is not authorisation to resubmit.

The correct procedure depends on the actual customs and system outcome. Where the situation remains uncertain, use the appropriate official support channel or contact the competent customs authority.

04 / SUPPORT & ESCALATION

The right problem.
The right support channel.

When a PoUS problem cannot be resolved internally, identify who is responsible for the next action. Technical assistance, user access administration and customs authorities perform different roles.

01 ⌁
IDENTITY & PERMISSIONS

Access administration

For authentication failures, user roles, delegation or representation access problems.

Prepare:
  • Relevant user and operator identifiers
  • Access route and attempted function
  • Exact error text and time of occurrence
02 ⇄
TECHNICAL FUNCTIONALITY

System support

For technical interruptions, unavailable functionality, transmission uncertainty or reproducible application errors.

Prepare:
  • Application and access environment
  • Timestamp and observed behaviour
  • Available acknowledgement or technical reference
03 §
CUSTOMS PROCEDURE

Competent customs office

For endorsement, customs examination, procedural discrepancies or questions concerning an actual customs decision.

Prepare:
  • Proof type and movement circumstances
  • Submission or registered proof reference, if available
  • Relevant customs communications and supporting records
PRACTICAL TOOL / LOCAL ONLY

Build a clearer
support request.

Prepare a structured summary before contacting the appropriate support channel. Select the problem category, enter non-sensitive details and copy the resulting report.

✓
Processed in your browser No information is transmitted by this tool. Avoid entering passwords, authentication tokens or unnecessary personal data.
SUPPORT CASE BUILDER LOCAL WORKSHEET
BEFORE CONTACTING SUPPORT

Make the first request useful.

01 Describe the symptom

Report the actual behaviour and any available system response.

02 Establish the outcome

Explain whether the request was rejected, received, registered or remains uncertain.

03 Document prior checks

Identify what has already been investigated without exposing credentials.

04 State the assistance needed

Ask a specific question about access, recovery, processing or verification.

05 / FREQUENTLY ASKED QUESTIONS

PoUS troubleshooting.
Essential answers.

Understand how to investigate failed submissions, technical interruptions, access restrictions and customs processing issues without confusing different system outcomes.

01 Why was my PoUS submission rejected?
A submission may be rejected because the supplied information does not satisfy applicable validation requirements or because another procedural condition has not been met. Examine the actual system response to identify the reason. Do not assume every rejection has the same cause or correction procedure.
02 What should I do if PoUS shows a technical error?
Record the error and the time it occurred, then check the available submission history and acknowledgements. If the outcome is uncertain, use the appropriate technical support route before repeating the transmission. A technical error does not necessarily mean the original request was not received.
03 Can I resubmit a rejected PoUS request?
A further submission may be appropriate after a confirmed rejection, depending on the reason for rejection and the applicable procedure. First identify and correct the underlying issue. Check whether an existing record must be amended or handled through another permitted process rather than automatically creating a new request.
04 Why can I access the portal but not use a PoUS function?
Successful authentication does not necessarily establish permission to perform every operation. The issue may concern application roles, representation arrangements or a required customs authorisation. An EORI number alone does not confer authorised issuer status.
05 What happens if a request is awaiting customs endorsement?
Where customs endorsement is required, electronic submission does not automatically mean that the proof has been registered. Review the actual processing information and any customs communication. If necessary, follow the instructions of the competent customs office.
06 What if the MRN cannot be found or verified?
Verify the reference entered, the proof particulars and the registration outcome. A reference problem may involve incorrect information, an unavailable record or a verification issue. Unresolved matters should be investigated through the appropriate customs or technical support channel.
07 Who should I contact about a PoUS problem?
The appropriate contact depends on the issue. Authentication and role problems may require access administration; technical failures may require the designated system support channel; endorsement, customs decisions and procedural questions may require the competent customs authority. Available support routes can differ by Member State and access interface.
08 Does Customs Explorer connect directly to PoUS?
No. The diagnostic and support preparation tools on this page provide independent informational guidance. They do not connect to the official PoUS system, retrieve live customs records, validate MRNs or submit information to customs authorities.
CUSTOMS EXPLORER / EU DIGITAL CUSTOMS

Diagnose the problem.
Protect the process.

Accurate troubleshooting begins with the actual system response, a clear understanding of the customs procedure and a documented recovery path. Resolve the cause before taking the next action.

Explore official PoUS resources