Customs Explorer
⌕

Customs Explorer

ICS2 incidents

EU CUSTOMS SYSTEMS / ICS2

ICS2 Incidents & Error Management

Understand why an Entry Summary Declaration is rejected, why an ENS remains incomplete, and how to respond to customs safety and security referrals.

A practical guide to ICS2 error notifications, filing validation, missing supplementary data, risk assessment messages and incident resolution for carriers, freight forwarders and other economic operators.

ENS REJECTION INCOMPLETE FILINGS CUSTOMS REFERRALS
CE
ICS2 / INCIDENT MONITOR ILLUSTRATIVE SYSTEM VIEW
MESSAGE FLOW
FILING STATUS Action required
!
IE3N99 / VALIDATION ENS filing rejected Correct the reported data errors
ERROR
02
IE3N02 / COMPLETENESS ENS not complete Review outstanding supplementary filings
PENDING
Q
IE3Q02 / RISK REFERRAL Additional information requested Respond to the customs request
REVIEW
ENS DATA ICS2 VALIDATION RESPONSE

Example messages only — not a live ICS2 connection.

VALIDATION & RESPONSE
SAFETY & SECURITY / EU
01 / INCIDENT CLASSIFICATION

Not every ICS2 incident is a filing error.

The first step in resolving an ICS2 incident is to identify which process has been affected. A rejected message, an incomplete Entry Summary Declaration, a customs risk referral and a technical communication failure require different investigations and actions.

01 / VALIDATION !

Filing rejection

The submitted message fails applicable technical, business or lifecycle validation checks.

Typical messages IE3N99 / IE3N01
OPERATIONAL RESPONSE Identify the error, correct and resubmit.
02 / COMPLETENESS ↔

Missing ENS data

A filing may be registered while required supplementary information remains outstanding in a multiple-filing arrangement.

Typical messages IE3N02 / IE3N11
OPERATIONAL RESPONSE Coordinate and complete the missing filing.
03 / RISK ASSESSMENT ◇

Customs referrals

Customs authorities request additional information, high-risk cargo screening or instruct that cargo must not be loaded.

Typical messages IE3Q01 / IE3Q02 / IE3Q03
OPERATIONAL RESPONSE Follow the specific customs instruction.
04 / COMMUNICATION ⌁

Technical incidents

Access, certificate, connectivity or message delivery problems may interrupt communication with ICS2 or its trader interfaces.

Typical evidence Gateway logs / transmission status
OPERATIONAL RESPONSE Verify delivery and registration status.
02 / OPERATIONAL DIAGNOSIS

Read the message. Identify the affected process.

The notification identifier provides an initial indication of the issue. The actual message content, filing context and applicable technical specifications determine the corrective action.

Message / event What it indicates Initial operational response
IE3N99 Error notification A message has failed an applicable validation check. Examine the reported errors, correct the message and resubmit as appropriate.
IE3N01 Lifecycle validation error A lifecycle validation rule has failed, for example in a duplicate-filing scenario. Review existing filings, identifiers and the applicable lifecycle rules.
IE3N02 ENS not complete Expected supplementary particulars have not all been received or linked. Identify the outstanding filing and coordinate with the responsible operator.
IE3N11 ENS pending notification An expected supplementary filing remains outstanding. Check the required partial filing and its linking information.
IE3Q02 Additional information request Customs requires further information for risk assessment. Provide the requested information through the prescribed response process.
IE3Q03 High-risk cargo and mail screening Customs requires the specified screening action in the applicable air-cargo scenario. Arrange the required screening and submit the prescribed response.
IE3Q01 Do Not Load request Customs has issued a do-not-load instruction. Do not load the affected cargo contrary to the instruction. Follow the applicable security procedure.
No confirmed response Transmission / access issue The operator cannot yet establish whether the message was received, processed or registered. Check interface acknowledgements, logs and filing status before attempting a new submission.

The table is a diagnostic overview, not a complete ICS2 message catalogue. Availability and routing of individual notifications depend on the business scenario, operator role and configured communication path.

03 / SYSTEM STATE VS LEGAL STATUS

A successful transmission is not the end of the process.

ICS2 communications are asynchronous. A technical acknowledgement or successful message delivery does not, by itself, establish that the ENS filing has been registered or that customs risk analysis has been completed.

In multiple filing, the registration of an individual partial filing also does not necessarily establish completeness of the combined ENS.

STAGE 01
Message transmitted Technical delivery must be verified
STAGE 02
Filing registered Registration response / MRN
STAGE 03
ENS complete Required datasets received and linked
STAGE 04
Risk assessment processed Referrals and outcomes handled as applicable
Conceptual checkpoints, not a universal chronological sequence for every ICS2 filing model.
04 / FIRST RESPONSE

What should an operator check first?

01 Identify the message

Record the notification code, its content, relevant identifiers and the time received.

02 Verify the filing status

Determine whether the message was rejected, registered, incomplete or subject to a referral.

03 Identify the responsible party

Establish which declarant, carrier, house filer or technical service provider must act.

04 Preserve the evidence

Retain the message, timestamps, references and corrective actions for operational follow-up.

OFFICIAL TECHNICAL GUIDANCE Always interpret an incident in its filing context.

For the complete message definitions, notification routing and applicable procedures, consult the current European Commission ICS2 documentation.

European Commission ICS2 FAQ
02 / ERROR DIAGNOSIS & RESOLUTION

When an ICS2 filing fails validation.

An ICS2 submission can fail before registration because its message structure, data content or business context does not satisfy the applicable validation rules. Other incidents arise earlier, during transmission, when the operator cannot confirm whether the message reached the system.

The correct response begins with identifying the failure stage, preserving the original evidence and checking the actual system notification—not simply submitting the same dataset again.

SCENARIO A 01

ICS2 has rejected the message.

A negative validation response has been received. The operator can identify the reported problem and determine the appropriate corrective submission.

EXAMPLE NOTIFICATION IE3N99 — Error notification
Investigate the reported validation errors.
SCENARIO B 02

No definitive processing response is available.

A timeout, interrupted connection or missing acknowledgement leaves the operator uncertain about the filing’s actual processing or registration status.

EXAMPLE EVIDENCE Timeout / gateway log / missing response
Establish the status before resubmission.
VALIDATION / ROOT CAUSE ANALYSIS

Four areas to investigate.

The examples below are diagnostic categories, not an exhaustive list of ICS2 validation rules. Individual requirements depend on the message type, dataset, transport mode and filing scenario.

01
MESSAGE STRUCTURE

Syntax and technical format

A required element may be absent, a field may have an invalid format, or the message may not conform to the applicable technical schema.

Illustrative example A date or identifier does not match the required format.

Check: Schema version, element structure, formats, mandatory fields and the validation report.

02
BUSINESS DATA

Missing or inconsistent particulars

A field can be technically well-formed but fail an applicable business rule because required information is absent or inconsistent with another data element.

Illustrative example A conditionally mandatory party or reference is missing.

Check: Applicable dataset, conditional requirements, party information and cross-field consistency.

03
FILING LIFECYCLE

Duplicate or incompatible operations

A submission may conflict with an existing filing or an operation may be incompatible with the current lifecycle state of the declaration.

Illustrative example A second filing conflicts with an already recorded consignment.

Check: Previous submissions, registration responses, references and permitted lifecycle operations.

04
FILING CONTEXT

Incorrect dataset or operator details

The selected filing model, declarant details, EORI references or other contextual information may not match the intended business scenario.

Illustrative example A supplementary filing uses an incorrect linking reference.

Check: Filing type, operator roles, transport document references and applicable linking rules.

ILLUSTRATIVE INCIDENT

A filing is rejected after submission.

TRAINING EXAMPLE
MESSAGE DIAGNOSTIC EXAMPLE ONLY
Notification IE3N99
Processing result Rejected
Possible cause Invalid data format
Required investigation Inspect reported errors
VALIDATION FAILURE

This is an explanatory illustration, not an actual ICS2 message payload or official error-code mapping.

01

Retrieve the complete negative response and associated message references.

02

Identify the rejected data elements and the corresponding validation rules.

03

Correct the source information and revalidate the complete dataset.

04

Submit through the applicable procedure and confirm the new processing outcome.

TRANSMISSION / UNCERTAIN STATUS

Never assume that a timeout means rejection.

A failed connection can occur before delivery, during processing or after the system has processed a message but before the operator receives its response.

Repeating the original submission without checking its status can create duplicate or conflicting operations. The appropriate recovery procedure depends on the trader interface, message type and technical setup.

Operational principle

Verify the outcome using available acknowledgements, message identifiers, interface logs and status enquiry mechanisms supported by the relevant ICS2 communication solution.

STATUS RECONCILIATION Where did the message stop?
1
Local system Was the message generated and handed to the interface?
2
Communication channel Is there evidence of successful delivery?
3
ICS2 processing Was the message validated, rejected or registered?
4
Response delivery Was the resulting notification received and processed locally?
INCIDENT RECOVERY / CHECKLIST

Before closing a validation incident.

01

The original message and negative response are retained.

02

The actual root cause has been identified.

03

The corrected data matches the source documentation.

04

The appropriate correction or resubmission procedure was used.

05

The resulting ICS2 processing status has been confirmed.

06

Outstanding ENS completeness or risk-analysis issues are tracked separately.

OFFICIAL REFERENCES

Technical validation and filing rules

Consult the current Commission ICS2 documentation and applicable Union Customs Code implementing provisions for authoritative message and procedural requirements.

03 / INCOMPLETE ENS & MULTIPLE FILING

The filing is registered. Why is the ENS still incomplete?

In an ICS2 multiple-filing arrangement, different economic operators may submit separate parts of the Entry Summary Declaration. Registration of one partial filing does not automatically establish that all required ENS particulars have been received and correctly linked.

An incomplete ENS incident must be investigated at the level of the entire filing arrangement: participating declarants, outstanding datasets, transport-document references and the applicable linking information.

ILLUSTRATIVE MULTIPLE-FILING SCENARIO One transport movement. Several ENS contributions.
EXAMPLE / NOT LIVE DATA
MASTER LEVEL M

Carrier filing

Relevant master-level transport information has been submitted and registered.

FILING REGISTERED
HOUSE LEVEL / A H1

House filing A

The first supplementary dataset has been submitted and registered.

FILING REGISTERED
HOUSE LEVEL / B H2

House filing B

Required supplementary information has not yet been received or successfully associated.

FILING OUTSTANDING
!
OVERALL ENS COMPLETENESS Required information is still missing.

The registered contributions do not, by themselves, establish a complete ENS for the relevant scenario.

Simplified illustration. Actual filing structures and completeness requirements depend on the applicable ICS2 dataset, transport mode and filing arrangement.

SYSTEM NOTIFICATIONS

Two messages that require immediate investigation.

In relevant multiple-filing scenarios, ICS2 can notify operators that the expected ENS information has not been completed. The message content and the recipient’s role determine the next action.

IE3N02 COMPLETENESS

ENS Not Complete

Indicates that the relevant ENS has not been completed because expected supplementary particulars remain outstanding.

What to investigate
  • Which required partial filing is missing?
  • Which operator is expected to provide it?
  • Were the relevant linking details agreed?
  • Has the missing filing actually been registered?
IE3N11 PENDING FILING

ENS Pending Notification

In the applicable scenario, a supplementary declarant is notified that expected ENS particulars have not yet been provided.

What to investigate
  • Is the recipient responsible for a partial filing?
  • Was the correct filing type selected?
  • Are the references consistent with the master filing?
  • Does a transmission or validation incident exist?

Do not confuse a pending notification with a rejected filing. A missing supplementary filing may never have been submitted, may have failed validation, or may require investigation of its linking information. The cause must be established before deciding how to correct the situation.

ROOT CAUSE / LINKING INFORMATION

The data may exist. But does ICS2 associate it correctly?

Where multiple filing applies, the system needs the prescribed identifiers to associate related partial submissions. Incorrect or inconsistent information can prevent the intended linkage.

Operators should verify the specific Unique Linking Key requirements for the relevant filing types. The required combination is not necessarily identical in every ICS2 business scenario.

LINKING DATA / DIAGNOSTIC VIEW ILLUSTRATIVE
01
Master transport document reference

Confirm that the relevant master reference is recorded consistently in the applicable filings.

CHECK
02
Carrier identification

Verify the required carrier EORI or other prescribed identifying information.

CHECK
03
Supplementary declarant identification

Check the relevant EORI and the identity of the operator expected to provide additional particulars.

CHECK
04
Filing type and transport-document hierarchy

Confirm the selected dataset and whether all required underlying house levels are represented.

CHECK
OPERATOR COORDINATION

Who needs to resolve the missing information?

The response depends on which operator holds the outstanding particulars and which filing obligation applies. Coordination is essential, but each participant must act within its legal and technical role.

01 / CARRIER

Confirm the master-level context

Check the relevant master filing, transport references, expected supplementary data and notifications received by the carrier.

02 / FREIGHT FORWARDER

Verify house-level obligations

Establish whether the forwarder must provide a supplementary filing or supply information to another operator under the applicable rules.

03 / CONSOLIDATOR

Check underlying house documents

Review the transport-document hierarchy, identify any additional house levels and coordinate the required particulars.

04 / IT SERVICE PROVIDER

Verify technical processing

Where involved, investigate message delivery, validation responses, interface logs and technical mapping without assuming the provider is the legal declarant.

INCIDENT RESOLUTION / PRACTICAL WORKFLOW

Resolve the missing filing. Then verify the outcome.

Sending an outstanding dataset is only one part of the recovery process. The operator should also establish that the submission has been processed and that the relevant completeness problem has been resolved.

Deadlines remain applicable.

Notifications and operational linking processes do not automatically extend the statutory ENS filing deadlines. A late or incomplete submission may have legal and operational consequences.

01

Identify the missing contribution. Determine the expected dataset and responsible operator.

02

Check existing submissions. Verify registration, errors and references before resubmitting.

03

Correct the underlying problem. Supply missing information or address the applicable linking issue.

04

Confirm the new system status. Check the resulting messages and completeness information.

05

Close the incident with evidence. Retain references, notifications and corrective-action records.

FURTHER READING / VERIFIED TOPICS

Understand the underlying filing requirements.

04 / CUSTOMS RISK ASSESSMENT

When customs requests further action.

An ICS2 referral is not simply a technical filing error. It is a customs intervention within the safety and security risk-assessment process. Depending on the circumstances, the operator may need to provide additional information, arrange screening or comply with a Do Not Load instruction.

The notification must be assessed according to its actual content, the affected consignment, the transport mode and the applicable operational procedure.

REFERRAL 01 IE3Q02

Request for Information

RFI / ADDITIONAL INFORMATION

Customs requires further particulars to assess the safety and security risk associated with the relevant goods or consignment.

Operational priority

Identify the requested information, obtain it from the appropriate source and submit the prescribed response through the applicable channel.

INFORMATION RESPONSE
REFERRAL 02 IE3Q03

Request for Screening

RFS / ADDITIONAL SCREENING

Customs requests the specified high-risk cargo and mail screening action in an applicable air-cargo or air-mail scenario.

Operational priority

Coordinate with the relevant aviation-security and cargo-handling parties, perform the instructed action and report the outcome as required.

SCREENING RESPONSE
REFERRAL 03 IE3Q01

Do Not Load

DNL / SECURITY INSTRUCTION

Customs issues an instruction prohibiting loading of the affected goods in the applicable pre-loading security scenario.

Operational priority

Prevent the affected goods from being loaded, immediately involve the responsible operational and security parties and follow the competent authority’s instructions.

DO NOT LOAD
A referral is not a generic ENS rejection.

Correcting or resubmitting declaration data does not automatically discharge a customs referral. The requested information, screening action or security instruction must be handled through the applicable ICS2 and operational procedures.

REFERRAL MANAGEMENT

One notification. Several operational responsibilities.

A customs referral can involve the declarant, carrier, freight forwarder, warehouse operator, ground handler or other parties, depending on the transport chain and the action requested.

The notification recipient must identify the affected consignment and coordinate the response with the parties capable of providing the required information or carrying out the instructed action.

CORE PRINCIPLE The party receiving a message is not necessarily the only party required to act operationally.
ICS2 / REFERRAL HANDLING ILLUSTRATIVE VIEW
OPERATIONAL CONTROL Referral response workflow
01
Receive and identify

Record the message, affected goods, references and requested action.

02
Assess the instruction

Distinguish RFI, RFS and DNL. Check the exact wording and scope.

03
Coordinate the action

Involve the responsible filing, transport and security parties.

04
Respond and monitor

Submit the prescribed response where required and monitor subsequent messages.

05
Confirm and document

Verify the relevant outcome before closing the operational incident.

CUSTOMS INSTRUCTIONS TAKE PRIORITY
DECISION MATRIX

Different referrals. Different responses.

This comparison provides a practical starting point. Always follow the actual notification and the applicable customs procedure.

Referral Required focus Typical coordination Important distinction
RFI IE3Q02 Provide the additional information requested by customs. Declarant, carrier and parties holding the relevant commercial or transport data. An information request is not, by itself, a Do Not Load instruction.
RFS IE3Q03 Arrange the specified additional screening in the applicable scenario. Carrier, cargo handler, security personnel and relevant declarant. A data correction does not replace a required physical screening action.
DNL IE3Q01 Prevent loading of the affected goods contrary to the instruction. Carrier, loading personnel, security function and competent customs authorities. The affected cargo must not be loaded unless the competent authority permits it.
PRACTICAL SCENARIO / AIR CARGO

An air-cargo consignment receives an RFI.

A carrier receives a request for additional information concerning goods covered by an ENS filing. The relevant commercial details are held by a freight forwarder.

The carrier and forwarder must coordinate promptly to obtain accurate information and ensure the prescribed response is submitted by the appropriate operator.

The incident is not resolved merely because the forwarder sends information to the carrier: the applicable response must be processed and any subsequent customs instructions must be respected.

Illustrative example. The actual recipient, response mechanism and responsibilities depend on the filing arrangement.
01 / CUSTOMS Additional information requested Referral notification received
02 / OPERATOR Information collected and verified Relevant parties coordinate
03 / ICS2 Prescribed response submitted System processing monitored
04 / FOLLOW-UP Further messages reviewed No automatic assumption of clearance
CRITICAL SECURITY INSTRUCTION

Do Not Load means Do Not Load.

A DNL instruction must be communicated without delay to the parties controlling the loading operation. The affected goods must not be loaded contrary to the instruction.

The operator must follow the competent authority’s directions and applicable security procedures. A filing amendment, technical resubmission or internal operational decision does not independently cancel a DNL instruction.

REGULATORY CONTEXT & RELATED GUIDES

ICS2 risk assessment in context.

The ICS2 process operates within the EU customs safety and security framework. Referral handling must be read together with the applicable ENS and transport rules.

05 / OPERATIONAL KNOWLEDGE BASE

ICS2 incidents. Frequently asked questions.

Practical answers to common problems involving rejected Entry Summary Declarations, incomplete filings, missing notifications, customs referrals and technical failures.

01 What happens if an ICS2 ENS filing is rejected?

A rejected filing has not been successfully accepted through the relevant validation process. The operator should examine the error notification, identify the affected data elements, correct the underlying problem and submit the appropriate message.

A technical acknowledgement alone should not be confused with successful ENS registration.

02 What does ICS2 error notification IE3N99 mean?

IE3N99 is an ICS2 error notification. The actual problem must be identified from the message content and the relevant technical specifications.

The notification identifier alone does not establish which field or business rule caused the failure.

03 Can an ENS be registered but still incomplete?

Yes. In a multiple-filing arrangement, one or more partial submissions may be registered while other required information remains outstanding.

The operator should check the expected supplementary filings, their registration status and the identifiers used to link the related submissions.

04 What is the difference between IE3N02 and IE3N11?

IE3N02 is an ENS Not Complete notification. IE3N11 is an ENS Pending notification, used to inform an identified operator that an expected filing has not yet been provided.

The appropriate response depends on the recipient, the filing arrangement and the outstanding data.

05 What should an operator do after an ICS2 transmission timeout?

First establish whether the original message reached ICS2 and whether it was processed. Review the available technical acknowledgements, message references, interface logs and supported status enquiries.

A timeout does not necessarily mean rejection. Blind resubmission can create duplicate or conflicting operations.

06 What is an ICS2 Request for Information (RFI)?

An RFI is a customs request for additional information needed for safety and security risk assessment. The relevant referral request is identified as IE3Q02.

The operator must provide the requested information using the applicable response procedure and monitor any subsequent customs messages.

07 What is an ICS2 Request for Screening (RFS)?

An RFS, identified by IE3Q03, requests additional high-risk cargo and mail screening in the applicable air-cargo or air-mail security scenario.

The responsible parties must arrange the instructed screening and communicate its outcome according to the applicable procedure.

08 What does Do Not Load mean in ICS2?

Do Not Load (DNL), identified by IE3Q01, is a security instruction prohibiting the loading of the affected goods in the applicable scenario.

The instruction must be communicated to the relevant operational parties and respected until the competent authority permits the appropriate next action.

09 Does successful ENS registration mean customs risk assessment is complete?

No. Registration and safety and security risk assessment are distinct stages. A registered filing can still be subject to further analysis, referrals or other applicable customs measures.

Operators should distinguish the registration response from subsequent risk-assessment notifications and instructions.

10 Who should be contacted when an ICS2 technical incident cannot be resolved?

Economic operators should contact the appropriate National Service Desk of the customs administration concerned. Where a technical service provider is involved, it may also need to investigate the interface and transmission evidence.

An escalation should include relevant message identifiers, timestamps, error notifications, system logs and a clear description of the operational impact, without unnecessarily disclosing sensitive commercial data.

11 Can an ICS2 system outage automatically suspend ENS filing obligations?

No automatic suspension should be assumed. Where an officially activated business continuity arrangement applies, operators must follow the relevant instructions, scope and conditions.

An individual connection problem does not independently authorise the use of contingency procedures.

12 Can an incorrect ICS2 filing be amended after registration?

The Union Customs Code provides for amendment of ENS particulars under the applicable conditions. Whether a specific change is permitted depends on the declaration’s status, the relevant legal restrictions and the technical procedure.

An amendment must not be treated as a substitute for complying with an outstanding customs security instruction.