Transit Dispatch Declaration Rejections by Customs

We are pleased to inform you that all reported issues have been resolved. Customers who reported issues have already been contacted to schedule the release deployment.

If any customer is still experiencing issues, we advise them to submit a support ticket. Our team will promptly get in touch to schedule the necessary release.

We appreciate your patience and cooperation during this process.

We have implemented amendments to address the issue and are currently in the testing phase. Once testing is successfully completed, we will get in touch with the affected customers to schedule a new release.

Regarding the "Previous Document Type" rejection issue, we recommend using the NMRN code as a workaround instead of N830. This workaround is being further investigated internally to ensure a more permanent resolution.

Additionally, for the "Place of Loading" rejection, please ensure that the field "Place of Loading UN" is submitted using the UN Location Code (e.g., NLRTM). If this field is not currently available via the personalization option, it will automatically become visible once the release is completed.

We appreciate your patience and will continue to provide updates as new information becomes available.

We are aware that some of our customers are experiencing issues with Transit Dispatch declarations being unexpectedly rejected by customs. At this time, customs has not provided detailed clarification regarding the reasons for these rejections.

Please rest assured that our team is actively analyzing the rejection messages and collaborating with relevant stakeholders to resolve this issue as quickly as possible. We appreciate your patience and will provide updates as new information becomes available.