IMP newsletter No. 12 -

IMP

IMP - Newsletter

You will find all newsletters on our homepage. Here you also get access to the English version of the newsletter.

The newsletter 12/2019 provides information about changes and new functionalities in the Import Message Platform. The software changes for the IMP release 9.1.0 become active with the maintenance work during the night of 17.12.2019. Since the last newsletter could not be delivered properly to all participants, we decided to include the changes of the release 9.0.0 again.

Information and implementation guides can be found at: http://www.imp-hamburg.de.

The application IMP-Direct can be reached at: http://www.imp-direct.de.

A complete inventory of fixed bugs and smaller enhancements can be found in the releasenotes via IMP-Direct, which can be found in the menu “Help/Release-Notes".

The IMP team wishes you a Merry Christmas and a happy New Year!

Information for freight forwarders

Lifting of the restriction of one import operation instruction message per container
Filter import instructions by manifest-match

Information for terminals

List of loading units with reference to the water police
Emails from monitoring customs processes now with container no. in the subject line

Information for carriers

Correction: status 938 for B- and S-numbers
New version 1.9.4a of the message implementation guide IFTMCS

Scheduling overview

Summary of IMP relevant dates

Information for freight forwarders

Lifting of the restriction of one import operation instruction message per container

We are pleased to inform you that the participants of the IMP working group decided to lift the restriction of only one import operation instruction message per container until further notice. In practice, conflicts often arise during the message creation, e.g. if a second freight forwarder is being charged with the handling of customs formalities. Until now the IMP rejected second import operation instruction messages with an error message.

As of now the restriction does not apply anymore. From now on it is possible to send a second import operation instruction message with the parameters container and B/L number.

If a second import operation instruction message to a container arrives, both participants will be informed that another import operation instruction message exists with the new status 903. Along with the status message we also provide the participant code and the freight forwarders reference (if available), in case of possible demands.

Filter import instructions by manifest-match

From now on you can filter import operation instruction messages which do not match with a manifest so far. You can activate the new checkbox "import operation instructions without manifest-match".

Information for terminals

List of loading units with reference to the water police

A new display was implemented for the terminals. It can be reached via the menu item "Terminal - loading units with reference to the water police". The list contains all loading units with reference to the water police.

Emails from monitoring customs processes now with container no. in the subject line

From now on the emails to the terminal include the container no. at the beginning of the subject line, if available.

Information for carriers

Correction: Status 938 for B- and S-numbers

Due to a software error the status 937 (release B-number), which has been cancelled in 2017, has been assigned again for a while. As described within the newsletter 09/2017 the difference between status 937 (release B-number) and 938 (release S-number) should be cancelled and converted into the common status 938 as " release of ZAPP reference". This change has been rebuilt with the actual release.

New version 1.9.4a of the message implementation guide IFTMCS

In the Newsletter 10/2019 we pointed out that the exemption reason in case of previous document type OESUMA has to be adapted to the new legal requirements (UZK – Community Customs Code). In case of import shipments with loading ports inside the EU we recommend to transmit the required segment as follows from now on:

RFF+AEI:Art 136 UZK and type 104 UZK-DA::OESUMA

Please note, that the exemption reason may not contain more than 30 characters. The corresponding examples in the implementation guide have been adapted to the UZK. The version has only been updated to 1.9.4a, since no structural changes have been made.