ICS2 D1_2 Header
Import Control System 2 (ICS 2)
Impacting all shipments to or via EU as of March 1st, 2023.
ICS2 D13_3 1 Process compliance
How we ensure process compliance from our side
We actively participate in the ICS 2 working groups of EU and IATA
We invest in adapted processes and updated IT landscape
We offer customer Q&A sessions in order to jointly prepare for ICS 2
We offer the option for multiple filing as set under ICS2
ICS2 D13_3 2 contribute to implementation
What is required from you, to jointly ensure the ICS2 compliance
Provide the mandatory HS codes and consignee EORI where assigned
Provide electronic data for a timely ICS 2 filing
Provide meaningful and complete data such as the goods description, also on HAWB level. The better the data, the lower risk for authority questions on the shipments
Contact us for the required alignment on the multiple filing option
ICS Additional Questions
Do you have additional questions on ICS 2?
ICS FAQ Heading
ICS 2 - Frequently asked questions
Import Control System 2 will be introduced as of 01st March 2023 for all shipments (general cargo and airmail) destined for or transiting the European Union.
Lufthansa Cargo requests the provision of the mandatory data as of 01st January 2023 in order to ensure a smooth implementation of the required reporting processes.
Immediately after relevant data is available to us (FWB/FHL).
In case of electronic data transmission, the PLACI is triggered automatically by IT and ensures a reply by EU customs before goods are handed over to Lufthansa Cargo.
In the case of paper shipments, the PLACI-data can only be sent after goods acceptance.
As early as dependable data is available and before goods acceptance.
Ideally Cargo XML is used as it is a better vehicle for all data required. Cargo IMP will still be accepted. A guide detailing in which field the data should be sent in will be published shortly.
A risk analysis process is triggered at the moment of receipt of the ENS (Entry Summary Declaration) filing containing the required PLACI data. The PLACI risk assessment is only focused on the detection of an immediate risk to aviation.
Yes, we will be submitting to our provider in CXML, however still accepting CIMP, whilst of course preferring CXML in GHA and customer messaging to us as carrier.
Transmission to us has been and will continue to be pushed, eAWB is already covering most of our shipments. The earlier we have the data, the better.
Currently not planned and we don’t expect it will be necessary.
To be handled by central referral handling team and first point of entry in the EU.
Even if only one HAWB has a referral pending we will hold the entire shipment until cleared.
EORI is not a mandatory field for ICS2, but business rule says that if the consignee has been assigned an EORI number to also submit it in the filing. So in the end it is an ICS2 requirement and will also be a TSD requirement in future.
If the consignee does not have an EORI number (e.g. private person or small entity), the EORI number is not required. If consignee is in a Non-Eu country, then third country unique trader identification number to be provided, if assigned.
Depending on the Origin Station and local authority regulations: Offer to perform the extra screening against a fee or return to customer.
The requirement expects LCAG to provide all HS Codes, meaning every single one contained in the shipment or HAWB.