Yes, the introduction of WKS also affects the Port Order in the Port of Hamburg. These impacts concern both the EMP (Export Management Platform / PortOrder XML) and the Sea Freight Export module in DAKOSY GE. 

Specifically affected are transit procedure goods and transhipment goods from non-Union countries, such as Switzerland, that are shipped via the Port of Hamburg to third countries

 

Die Einführung von WKS betrifft die Anmeldearten MIT und DUX.

• Declaration case MIT:
  As of July 1, 2026, the use of the MIT declaration type will no longer be possible. 
  In agreement with the Hamburg customs authorities, it has been decided that the MIT will be discontinued, and with it the grounds for exemption from filing an exit summary declaration (ASUMA). The creation/submission of an exit summary declaration (ASUMA) or re-export notification (WAM) is therefore mandatory. 
  For information on the possible uses of the DUX declaration type, please refer to the sections “DUX in GM01 format,” “DUX with MRN,” and “DUX without MRN.”
   
• Declaration DUX in GM01 Format (presentation notification):
  As part of the implementation of the new PortOrder XML (EMP), the updated WKS requirements for the GM01 DUX declaration are no longer supported. Therefore, the GM01 can no longer be used for DUX declarations filed on or after 01.07.2026.
  As of 01.07.2026, the DUX declaration case may only be submitted exclusively via HDS or as a PortOrder XML (EMP).
  If you have previously been submitting DUX declarations exclusively in GM01 format, you will need to switch to HDS or PortOrder XML (EMP). This requires amending your DIHS contract.
  If you currently are only able to submit via GM01, please contact us at vertrieb@dakosy.de.
   

• Declaration DUX with MRN:
  The exit summary declaration (ASUMA) or WAM (re-export notification) is submitted in WKS as a self-declarant. The customs process associated with the ASUMA/WAM therefore takes place externally from the Port Order and needs to be managed within WKS. 
  The MRN generated via WKS for the ASUMA / WAM and the corresponding release date are entered in the Port Order under declaration type DUX. Entering additional security-related data is then no longer necessary, as the WKS MRN is specified in the Port Order.
  With the implementation of WKS, in addition to entering the WKS MRN, information regarding the type of WKS transaction (WKS WAM or WKS ASUMA) is also required.

  IMPORTANT: A declaration as “self-declarant” will only be possible at loading terminals that accept this method of declaration for loading. 
  With the adoption of WKS as the leading system for ASUMA/WAM, the four major container terminals in Hamburg no longer accept “self-declarants” (CTA, CTB, CTT, Eurogate).

  For shipments via the terminals listed above, select “DUX without MRN,” which is explained below.
   

• Declaration DUX without MRN:
  By using “DUX without MRN,” it is possible to declare the ASUMA using the Port Order via the Sea Freight Export module in DAKOSY GE or via EMP. No ASUMA/WAM is created in advance during the self-declarant process in WKS. 
  With “DUX without MRN,” it is not possible to make a re-export declaration (WAM). In agreement with the Hamburg customs authorities, only the ASUMA will be used.
  Seit dem 05.05.2026 werden im Anmeldefall „DUX ohne MRN“, zusätzliche WKS-Daten benötigt:
• EORI of the transporter (The person who transports the goods or is responsible for their transport)
• Transport document (type and reference)
• UN Number (in the case of dangerous goods shipments)
• Transition procedures (ATB/MRN reference from the custodian, ATLAS goods item number, and packages)

If the ASUMA is requested via the Port Order in DAKOSY GE or in EMP using “DUX without MRN,” you do not need an additional WKS participant certificate. 

If you create an ASUMA or WAM in WKS as a self-declarant and enter it into the Port Order, a WKS Participant Certificate is required for creation in WKS. (DUX with MRN)

For more information on the WKS Re-Export System – Creating an ASUMA / WAM – please refer to the following FAQ.

 

DUX without MRN

The declaration case DUX without MRN is used to help the EMP/ZAPP declarant to declare the ASumA. All necessary information for the ASumA declaration will be reported via HDS or Port Order XML/EMP. EMP/ZAPP sends the data to ATLAS WKS and receives the MRN for the ASumA in return. The further WKS customs process until the exit confirmation runs automatically. 

So it is not necessary to initiate an ASumA MRN via WKS before, but the SumA ATB/MRN must be specfied for the „Procedure transference“. 

DUX with MRN

For the declaration case DUX with MRN an ASUMA or WAM MRN with release date and time in the Port Order XML/EMP or HDS is necessary. This ASumA or WAM MRN was generated outside of  EMP/ZAPP via the customs procedure WKS.

The HHLA container terminals CTA, CTB and CTT and the EUROGATE container terminal in Hamburg do not allow DUX with MRN declarations. This also applies for DUX declarations in consolidated containers which are loaded via this terminal.

During the acquisition of the „Procedure transference“ the data of the summary declaration (SumA) is referenced for the creation of the exit summary declaration (ASumA).

Hereby it is important that

• the ATB or MRN was generated at the customs office Hamburg (4851)
• the SumA positions and packages are precisely referenced

Enclosures usually receive an own position with package number 1 if a transit procedure is completed. That also applies like this for the „Procedure transference“. 

• The customs is ordering a measurement
• The declaration data is rejected with an error message from ATLAS
• The positions and packages specified in the „Procedure transference“ are not deposited at the terminal
• The positions and packages specified in the „Procedure transference“ differ from the positions and packages deposited at the terminal
• The terminal does not hold a loading permission for the SumA
• In case of ATLAS error messages from ATLAS a re-registration with updated data should be carried out.
• In case of problems with custody and loading permission it has to be checked why the terminal is not in custody or does not hold a loading permission.
• The status may change to „Released“ by the transfer of custody to the terminal in custody.
• As soon as the terminal is in custody, the custody data will additionally be checked against the data of the „Procedure transference“. If an error occurs during this check the related S-numbers have to be cancelled and re-registered with „Procedure transference“ data, matching with the goods (data) deposited at the terminal.
• The custody inventory must precisely comply with the data of the „Procedure transference“. 

At the request of the HHLA container terminals CTT, CTA and CTB and for the EUROGATE container terminal Hamburg validations for custody are carried out. Before the presentation of goods it will be validated if

• the positions and packages specified in the Procedure transference are deposited at the terminal
• the terminal holds a loading permission for the SumA

If a consolidated container arrives at one of the terminals mentioned above, validations for all included DUX declarations are starting. If the custody or loading permission is/are missing, the status is set back to „not Released“. 

In case of problems with custody and loading permission it has to be checked why the terminal is not the custodian or does not hold a loading permission. 

The status may change to „Released“ by the transfer of custody to the terminal. 

As soon as the terminal is in custody, the custody data will additionally be checked against the data of the „Procedure transference“. If an error occurs during this check the related S-numbers have to be cancelled and re-registered with „Procedure transference“ data, matching with the goods (data) deposited at the terminal.

The custody inventory must precisely comply with the data of the „Procedure transference“.