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.
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.
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.
What happened?
Choose the closest description.
These are diagnostic categories, not official PoUS message names or error codes.
Review the submitted data.
A validation problem may indicate missing information, an incompatible value or inconsistency with the applicable dataset.
-
01
Read the actual validation response and identify the affected information.
-
02
Compare the submitted particulars with the applicable PoUS data requirements.
-
03
Correct the underlying issue using the permitted procedure before resubmitting.
Check the specific validation feedback before making changes.
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.
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.
01
Mandatory information missing
Incomplete submission data
Identify the missing field or data element.
Operator review
Required information may have been omitted or not supplied in the expected structure.
Compare the submitted information with the applicable dataset and the actual validation feedback.
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
Descriptions, quantities, transport references or other particulars may not align with the underlying commercial documentation.
Reconcile the proof particulars with the relevant commercial, transport and customs records.
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
The selected proof may not correspond to the territorial, transport or procedural circumstances.
Review the movement, relevant fiscal territory rules and the conditions for the intended proof type.
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
The authentication process, account configuration or selected access route may not be working as expected.
Verify the applicable EU or national access mechanism, user credentials and account configuration.
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
The user may lack the required application permissions, representation rights or customs authorisation for the intended action.
Distinguish portal permissions from customs authorisations. An EORI number alone does not establish entitlement to every simplified procedure.
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
A network interruption, unavailable response or technical problem may have affected the acknowledgement without proving that transmission failed.
Review available submission history, references and acknowledgements before attempting another transmission.
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
The applicable procedure may require customs endorsement or additional examination before registration.
Check the actual processing outcome, outstanding requests and whether further information is required.
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
The reference may be incorrect, the proof may not be registered, or a customs verification issue may need resolution.
Confirm the MRN, proof particulars, registration outcome and applicable presentation requirements.
Correct reference errors where permitted. Refer unresolved registration or verification issues to the appropriate customs channel.
Investigating a validation problem?
Continue with the dedicated PoUS Validation guide for a more detailed explanation of data checks and processing outcomes.
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.
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.
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.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.Four situations. Four different approaches.
Identify the scenario that corresponds to the available evidence before taking corrective action.
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 ValidationTechnical 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 SubmissionsEndorsement 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 processProof 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 validationFive checks before taking action.
Use this local checklist to organise your review. It does not query PoUS, submit information or verify any customs record.
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.
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.
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
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
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
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.
Make the first request useful.
Report the actual behaviour and any available system response.
Explain whether the request was rejected, received, registered or remains uncertain.
Identify what has already been investigated without exposing credentials.
Ask a specific question about access, recovery, processing or verification.
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?
02 What should I do if PoUS shows a technical error?
03 Can I resubmit a rejected PoUS request?
04 Why can I access the portal but not use a PoUS function?
05 What happens if a request is awaiting customs endorsement?
06 What if the MRN cannot be found or verified?
07 Who should I contact about a PoUS problem?
08 Does Customs Explorer connect directly to PoUS?
EU legislation & official resources
The legal framework governs proof of Union customs status. Technical error handling and access procedures must also be checked against the applicable official system guidance.
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