TTM8.0.1 Live Documentation

TTM8.1.0 is now live and available to resume testing

This milestone delivers:

  • Enhancements to CDS error codes
  • Goods blocked under control for Imports and Exports
  • Imports submission of Type J & K declarations (further procedure codes)
  • Imports simulated quota scenarios
  • Exports submission of Type J & K declarations
  • Exports handling of reprocessing errors (limited scenarios)
  • Exports excise movements
  • Tariff uplift incorporating the TARIC3 delta files through 24/07/2019

The enhancement to CDS error codes are part of the work we have been doing in response to your feedback to improve the quality of the error messages produced by CDS.

The programme’s immediate focus has been on the most frequently triggered error messages and ‘quick wins’ which HMRC can implement through changes to in-house configuration. Error messages CDS10001 and CDS12056 have been broken out into new, more granular, error messages. In addition, the wording of all declaration validation related error messages has been reviewed and updated where feasible. The latest list of CDS error codes can be found in the CDS 03 Codelists and WCO References document, found in the Google Drive Folder CDS 03 Customs Declaration.

Error handling for the Tariff application has been reviewed and more information is returned when measure conditions are not fulfilled, which are usually document errors, ratio errors, or a mixture of the two. Following error code CDS40045, the CDS system is now pointing to the additional document and listing the failed condition(s) and missing certificate type(s).

The team are also now validating one excise calculation scenario to reject when a calculation leads to a negative value, and we are no longer exposing validation failures between internal CDS components.

Please note that the ‘duplicated’ validation errors which can be generated when TARIC additional codes are used have not yet rationalised.

The phased approach to the review of CDS error messages will pick up deeper, technical changes over time. Your feedback  on these initial enhancements is welcome and will continue to provide updates on this work.

For Exports, please note that the Trade Test environment is continuing to use a stubbed CHIEF service. Against this stub, it will be possible to test arrivals, departures, and consolidations of a DUCR or MUCR in CDS. Please note that, with this stub, if you submit a movement or consolidation message with a message code of “EDL”, “EAC”, or “CST” that triggers an error against the consignment in CDS, two error responses will be returned during this phase of Trade Test.

Supporting Documents




Trade Test Scenarios Document – outlines high-level functional scenarios enabled by the functionality in this release, as well as previous Trade Test deployments.

Please note that Section E-5 (Exports Inventory Linking Dual Running) outlines the functionality that will be enabled once connectivity has been established between CDS Trade Test and the CHIEF HMUT service. As we expect this connection to be established later this month, we have included this section in this version of the Trade Test Scenarios Document to support your test preparation. However, please do not execute any tests in either HMUT or CDS with the intention to test the Exports Inventory Linking solution until we have confirmed that this connectivity has been established and the service is available end-to-end.

TTM8.1.0 Test Data Cover Sheet – Please ensure the correct combination of EORI, authorisations, and payment details are used for tests submitted in Trade Test depending on the test scenario being executed.

TTM8.1.0 Known Error Log (KEL) – 16 known errors from previous releases have now been resolved and an additional 7 known errors have been added. This document will also be uploaded to the Google Drive and is updated fortnightly with any new errors identified through our investigation of your queries. Please refer to the Google Drive for the latest Trade Test KEL.

In addition to the known errors outlined in this document, please note that erroneous validation rules have been introduced on Declaration Types B and E. These are mandating a number of additional data elements which, if provided, trigger further cross-field validation failures. It is therefore advised to suspend testing of Declaration Types B and E until these problems have been resolved. Please note that the provided Type B and E samples remain valid, but these will not currently process successfully due to these issues. In addition, IM_IVL_Sample_TC05 has been updated to Declaration Type F to work around this issue.

XML Sample Messages – new XML samples have been produced for this release and some of the existing samples have also been updated in response to your feedback and queries. Please contact the secretariat if you would like to have these.

The updates to the XML sample messages include:

  • Removal of AcceptanceDateTime tag from Imports frontier declarations. This field should only be populated for supplementary declarations Type Y or Z.
  • Removal of erroneous XML tags (non-required data items) from Exports payloads.
  • Removal of the 505N workaround. CCG authorisation, or exemptions, should now be declared as per the guidance in the UK Trade Tariff: volume 3.
  • Modifications to the notification format. Please note that this has only been applied to the new XML samples for this release. The programme is impacting the work to apply this to the existing payloads.
  • IM_IVL_Sample_TC03 and IM_IVL_Sample_TC04 have been removed from the XML samples as these files were incomplete.

Please note that we continue to investigate the queries that have been raised through the Trade Test support model and there may be some open queries which have not yet been addressed in this iteration of the XML sample messages. Please continue to raise any questions you have through the Trade Test support model.

In addition, please be advised that IM_A_Sample_TC08 and IM_A_Sample_TC09 are declarations and notifications for a blocking & final control scenario. To simulate the seizure, detention, or destruction of goods in Trade Test, the Packaging/Type (DE 6/9) of the first goods item should be entered as 'PK'.  However, for this phase of Trade Test, please note that once Packaging/Type ‘PK’ has been entered, declaration processing will pause and the declaration will not be invalidated. A solution to invalidate the declaration and produce a DMSINV notification in Trade Test is being impacted by the CDS Programme. In the meantime, please refer to IM_A_Sample_TC08 and IM_A_Sample_TC09 for the notifications produced in this scenario, including the cancellation messages.


Back to news

We use cookies on this site to improve your experience. By continuing to browse the site you are agreeing to our use of cookies. You will only see this message once. Find out more