Customs Explorer
⌕

Customs Explorer

PoUS validation

EU DIGITAL CUSTOMS / POUS SYSTEM

PoUS
Validation.

Understand what gets checked, what the results mean and what happens next.

The Proof of Union Status (PoUS) system supports electronic management of evidence that goods have Union customs status. Learn how submission data checks, customs processing and subsequent proof verification differ — and why passing one stage does not automatically complete the others.

THE KEY DISTINCTION

Valid data is not the same as an endorsed or registered proof. A successful technical check does not, by itself, establish that customs have accepted the proof or that it can be used for a particular movement.

CE
PoUS / VALIDATION Conceptual process overview
REFERENCE MODEL
THREE DISTINCT QUESTIONS

What does each check establish?

01
Data validation FORMAT & CONSISTENCY

Are the submitted particulars complete and consistent with applicable checks?

✓
02
Customs processing PROCEDURAL OUTCOME

Is customs endorsement required, and what processing outcome applies?

§
03
Proof verification REFERENCE & STATUS

Can the relevant proof and its particulars be verified for the intended use?

⌕
01 Data quality Completeness and consistency
02 Customs outcome Endorsement or registration
03 Proof verification Reference and applicable use
01 / VALIDATION WORKFLOW

From submitted data
to usable proof.

PoUS processing involves several distinct checks and outcomes. Understanding where each stage begins and ends helps operators avoid treating a successful transmission or technical validation as confirmation of Union customs status.

PROCESS OVERVIEW Five operational stages
Data / system Customs / procedure Proof use
01
DATA / SYSTEM PREPARATION

Prepare the proof particulars

The operator identifies the appropriate proof type and prepares the required information concerning the goods, movement and relevant parties. Supporting documentation should substantiate the declared Union customs status.

Key question Is the intended proof appropriate for the movement and supported by the underlying records?
02
DATA / SYSTEM SUBMISSION CHECKS

Submit and validate the data

The electronic request is subject to applicable technical and business-rule checks. These may concern required data elements, permitted values, consistency and relevant conditions for the submission.

Key question Has the system accepted the data for further processing, or identified an issue requiring action?
03
CUSTOMS / PROCEDURE PROCESSING

Determine the applicable customs outcome

Where the procedure requires customs endorsement, the competent authority may examine the request before the proof is registered. Different arrangements can apply where the operator holds a relevant authorised issuer authorisation.

Key question Is customs endorsement required, and has the applicable procedural requirement been met?
04
CUSTOMS / PROCEDURE REGISTRATION

Establish proof registration

Once the applicable conditions are satisfied, the proof can be registered in the relevant electronic process and identified by its reference. A submission acknowledgement should not be confused with confirmation of registration.

Key question Does the available system information confirm registration of the relevant proof?
05
PROOF USE PRESENTATION / VERIFICATION

Present and verify the proof

The relevant proof reference and particulars are used in accordance with the applicable presentation requirements. Customs may verify the proof and its relationship to the goods concerned.

Key question Can the proof be verified and used for the intended goods and movement?
i

This is a simplified operational model, not an official PoUS screen sequence. Actual processing and system messages depend on the proof type, applicable procedure and operator authorisations.

IMPORTANT DISTINCTION

Three outcomes that must not be confused.

These concepts answer different questions. Treating them as interchangeable can lead to incorrect operational decisions.

A

Data accepted

The electronic information has passed the relevant submission checks.

Does not by itself confirm an endorsed or registered proof.
B

Proof registered

Registration has occurred following the applicable procedural requirements.

Does not eliminate the need to meet presentation and use requirements.
C

Proof verified

The relevant reference and proof particulars are checked in the context of their intended use.

Must relate to the goods and circumstances concerned.
OPERATIONAL EXAMPLE

A T2L request passes the initial data checks.

An operator submits a T2L request and receives feedback indicating that the submitted information passed the applicable validation checks.

This does not necessarily mean that the proof has completed customs processing or has been registered. The operator must establish the actual outcome before relying on the proof.

WHAT TO VERIFY NEXT
01

Was the request received for processing?

02

Was customs endorsement required?

03

Has the proof been registered?

04

Are the reference and particulars available for the intended use?

02 / DATA VALIDATION REQUIREMENTS

Better data.
Fewer avoidable errors.

Reliable PoUS submissions begin with accurate, consistent and properly supported information. Review the main data categories before submission and distinguish technical validity from the underlying customs requirements.

i
What does PoUS data validation actually cover?

Electronic checks may assess required data elements, formats, permitted values and relationships between particulars. These checks do not replace the need to substantiate Union customs status or comply with the applicable proof procedure.

PRE-SUBMISSION REVIEW

Six essential information groups

Use these categories as a practical preparation framework, not as a substitute for the official PoUS data requirements.

01 IDENTIFICATION

Operator and party information

Check the relevant operator identifiers, party particulars and the capacity in which the submission is made.

REVIEW POINTS
  • Relevant EORI and party information
  • Correct operator or representative
  • Applicable access and authorisation conditions
Identity, system permissions and customs authorisations are distinct matters.
02 PROOF SELECTION

Correct proof type

Confirm that the selected means of proving Union customs status corresponds to the applicable movement and legal circumstances.

REVIEW POINTS
  • T2L or T2LF applicability
  • Territorial and fiscal circumstances
  • Conditions for any other applicable proof method
T2L, T2LF and the Customs Goods Manifest must not be treated as interchangeable.
03 GOODS DATA

Goods description and particulars

Ensure that the goods can be identified consistently from the submitted information and supporting commercial records.

REVIEW POINTS
  • Accurate goods descriptions
  • Quantities and relevant measurement details
  • Consistency with underlying documentation
A technically valid description must still accurately identify the goods concerned.
04 MOVEMENT CONTEXT

Transport and movement information

Review the movement circumstances and any transport-related particulars required for the selected proof.

REVIEW POINTS
  • Relevant transport information
  • Movement and territorial context
  • Consistency across transport records
Required transport particulars can differ according to the proof and procedure.
05 DOCUMENTARY EVIDENCE

Supporting records and references

Verify that the information is supported by the relevant records and that any required references are accurate.

REVIEW POINTS
  • Relevant commercial or transport records
  • Accuracy of required document references
  • Evidence supporting Union customs status
Documentary support is not equivalent to automatic customs acceptance.
06 CROSS-DATA CONSISTENCY

Consistency across the submission

Review relationships between the different information groups and investigate any apparent contradictions.

REVIEW POINTS
  • Matching goods and document particulars
  • Consistent parties and movement details
  • Compliance with applicable data rules
Passing individual field checks does not guarantee overall procedural correctness.
UNDERSTANDING VALIDATION

Not every check answers the same question.

A useful internal review separates three different aspects of data quality and compliance.

A

Structural validity

Is the information provided in the required format and structure, with the applicable mandatory elements?

B

Logical consistency

Are values and relationships between data elements compatible with the relevant business rules?

C

Customs substantiation

Do the actual facts and supporting evidence justify the use of the selected proof under the applicable customs rules?

These are analytical categories used by Customs Explorer. They are not official PoUS response statuses or a complete specification of system checks.

OPERATIONAL EXAMPLE / T2L VS T2LF

A complete dataset can still use the wrong proof.

Consider a movement involving a territory where the distinction between T2L and T2LF is relevant. An operator may prepare complete, internally consistent goods information but select an inappropriate proof type.

This illustrates why reviewing data completeness alone is insufficient. The territorial and procedural context must also be established before submission.

ILLUSTRATIVE COMPARISON
Data completeness Required particulars reviewed
✓ Checked
Internal consistency Goods and references reconciled
✓ Checked
Proof applicability Territorial rules not yet confirmed
! Review
Key lesson

Correct data does not compensate for an incorrect legal or procedural choice.

03 / ERRORS & PROCESSING OUTCOMES

Read the result.
Choose the right action.

Not every unsuccessful PoUS operation is a validation failure. A rejected dataset, an uncertain transmission and a request awaiting customs processing require different responses.

Never interpret an unknown outcome as a confirmed rejection.

If a transmission was interrupted or an acknowledgement is missing, first investigate whether the original request was received or registered. Repeating an uncertain submission without checking may create unnecessary duplicate records or procedural complications.

INTERACTIVE REFERENCE

Identify the type of problem

Select an operational scenario to see its likely significance and recommended checks.

DATA VALIDATION GUIDANCE
SELECTED SCENARIO

Missing or invalid data

A required data element may be absent, incorrectly formatted or incompatible with an applicable validation rule.

WHAT TO CHECK
  • Identify the field or rule mentioned in the actual response.
  • Compare the submitted information with supporting records.
  • Confirm the applicable data requirements for the proof type.
RECOMMENDED NEXT STEP

Correct the underlying data issue and follow the permitted correction or resubmission procedure.

A rejected dataset should be distinguished from a request that was successfully received and remains under processing.

REFERENCE ONLY

These are illustrative operational categories, not official PoUS error codes, system messages or live customs status information.

INTERPRETING SYSTEM FEEDBACK

Four outcomes. Four different meanings.

Determine what the actual system communication establishes before deciding whether to correct, wait, investigate or escalate.

01
Data rejected

Applicable checks have identified a problem preventing the request from progressing in its submitted form.

CORRECT
02
Transmission uncertain

The available information does not establish whether the original request was received or processed.

INVESTIGATE
03
Request under processing

The request may have passed initial checks but has not yet reached the relevant procedural outcome.

MONITOR
04
Proof registered

Registration has been established, but the proof must still be used and presented according to the applicable requirements.

VERIFY USE

These descriptions are explanatory categories. Always rely on the actual official PoUS messages and applicable procedural instructions.

VALIDATION BOUNDARY

What automated checks cannot establish alone.

01 Actual customs status

Data consistency alone does not prove that goods legally have Union customs status.

02 Customs endorsement

Passing a technical check does not replace endorsement where it is required.

03 Proof applicability

A technically accepted request does not automatically establish that the proof is appropriate for the intended movement.

NEED TO INVESTIGATE A FAILED OPERATION?

Move from validation to troubleshooting.

Follow the dedicated recovery guide for transmission uncertainty, processing problems and appropriate escalation routes.

Open PoUS Troubleshooting
04 / INTERACTIVE READINESS CHECKER

Check before
you submit.

Review the essential preparation questions before submitting an electronic proof of Union customs status. Identify missing information and create a practical pre-submission review summary.

PoUS Readiness Checker Independent preparation worksheet
LOCAL / NO API
STEP 01

Select the intended proof

Choose the proof type being considered. This selection does not establish that it is legally appropriate.

T2L selected. Confirm that T2L is the appropriate proof for the actual goods and movement.
STEP 02

Complete the preparation review

Mark an item only when the relevant information has actually been reviewed.

01

Proof and procedure

Confirm the applicable legal and procedural context.

02

Operator and goods

Check identity and the particulars identifying the goods.

03

Movement and evidence

Reconcile the submission with the supporting records.

04

Final consistency review

Identify contradictions and confirm readiness for official checks.

AFTER COMPLETING THE REVIEW

A completed checklist is not an approved proof.

Even when every preparation item has been reviewed, the official submission remains subject to applicable system and procedural requirements. Where required, customs endorsement and subsequent registration must still be established.

05 / FAQ & OFFICIAL REFERENCES

PoUS validation.
Questions answered.

Practical answers to common questions about PoUS data validation, customs processing, registration and the use of electronic proof of Union customs status.

01 What is PoUS validation?

PoUS validation refers to the checks applied to information submitted through the Proof of Union Status system. Depending on the applicable electronic process, checks may concern required particulars, data formats, permitted values and consistency between information elements.

Technical validation must be distinguished from customs endorsement, proof registration and subsequent verification of the proof.

02 Does successful PoUS validation mean that a T2L is approved?

No. Passing applicable data checks does not, by itself, establish that the proof has been endorsed or registered.

The operator must establish the actual procedural outcome. The processing route may differ depending on whether customs endorsement is required or relevant authorised issuer arrangements apply.

03 What information should be checked before submitting a PoUS request?

Review the selected proof type, relevant operator and party information, goods particulars, movement circumstances, supporting records and consistency across the submission.

The precise mandatory elements and business rules must be determined from the applicable official PoUS requirements. The preparation categories in this guide are not a complete technical specification.

04 What is the difference between T2L and T2LF validation?

T2L and T2LF are distinct means of demonstrating Union customs status in different legal and territorial circumstances.

The correct selection depends on the applicable movement and territorial rules. Data completeness does not compensate for choosing an inappropriate proof type.

See the dedicated guides: T2L in PoUS and T2LF in PoUS.

05 Can an authorised issuer bypass PoUS validation?

Authorised issuer arrangements may affect the requirement for customs endorsement, subject to the relevant authorisation and applicable conditions.

They do not create a general exemption from accurate data, applicable electronic requirements or the legal conditions governing proof of Union customs status. An EORI number alone does not establish authorised issuer status.

06 What should I do if a PoUS request fails validation?

Identify the actual response and determine whether it concerns missing data, an invalid value, an inconsistency or another applicable rule.

Correct the underlying issue using the permitted procedure. If the transmission outcome is uncertain, investigate the original request before attempting another submission.

For recovery scenarios, consult PoUS Troubleshooting.

07 Does a registered PoUS proof always guarantee acceptance at presentation?

No. Registration does not remove the applicable requirements for presentation and use of the proof.

The proof must relate to the goods concerned and remain subject to applicable customs verification. Any relevant validity period or procedural condition must also be respected.

08 Can Customs Explorer validate a PoUS submission automatically?

No. The Customs Explorer readiness checker is an independent educational preparation tool. It does not connect to the official PoUS system or validate submissions against its technical and business rules.

It helps operators review information before submission but cannot confirm customs status, authorisation, endorsement, registration or acceptance of a proof.

CUSTOMS EXPLORER / POUS

Prepare with confidence.
Verify with the official system.

Use the readiness checker to organise your pre-submission review, then follow the applicable official PoUS procedure for validation, processing and proof registration.