29th March 2019
This update includes an overview of the functionality, updates to codelists and the known error log as well as supporting documentation.
TM6.2.0 includes the following functionality:
Two new API endpoints have been added to the Customs Declaration API to support this functionality. These endpoints adhere to the WC02 Declaration Submission schema.
Supporting documents for testing in TTM6.2.0,
Updated TCM and Codelists Documents – updates have been made to these documents as follows.
TTM6.2.0 Scenarios – this provides a high-level summary of the test scenarios enabled by this release. Please note the limitations to the procedure codes available, as outlined above, while the hot fix is delivered into CDS Trade Test.
TTM6.2.0 Test Data Cover Sheet – additional test data has been added to the Trade Test environment to support the immediate payments simulation and Exports. Please ensure the correct combination of EORI, authorisations, and payment details are used for tests submitted where the expected result is clearance.
XML Samples – New XML samples have been produced for TTM6.2.0. Please note that we have added the prefix IM to all imports samples and EX to all exports samples to differentiate them.
The CDS Programme will continue to iterate on the XML sample messages as additional functionality is released into CDS Trade Test.
TTM6.2.0 Known Error Log (KEL) – the KEL has been updated to remove the errors from previous milestones that are resolved in this release, as well as to include new errors identified through our testing of TTM6.1.0. These updates will also be made to the KEL on the online forum.
The following known errors from the TTM6.1.0 KEL are now resolved
KEL ID 002
o Declaration is accepted and duties are correctly calculated if the VAT code is incorrectly entered in DE 6/17, rather than DE 6/16.
KEL ID 049
o DMSREJ is inconsistently returning the SequenceNumeric element for repeating elements where a SequenceNumeric should always be provided. Beginning in TTM6.0.0, where there is only one instance of an element, a SequenceNumeric should not be returned in the rejection notification and the DMSREJ should never include a SequenceNumeric of 0. However, there remain some instances where SequenceNumeric is not provided for a repeating element.
The following are NEW known errors
o Amendment is not successfully applied when a valid amendment message is submitted for the following types of amendment: Amend Licence, Amend Value, Amend CPC, Amend Currency, Amend Consignee/Consignor, Delete Item, Amend Preference.
o Declaration is incorrectly rejected when country of destination is declared at Header level only. To ensure Exports declarations are processed successfully, country of destination should be declared at the item-level.
o Null amendment to override the 1 hour wait timer is incorrectly rejected following a negative inventory match on a Type A declaration only. The second expected UKCIUM message is received once the 1 hour wait timer has elapsed, rather than as a response to the null amendment. Null amendments are correctly processed (and so can be tested) for Type C declarations.
o An internal processing error occurs in the calculation step when a declaration is submitted under a procedure or declaration category where Item Price/Amount (DE 4/14) is not required for the declaration. This applies to declaration category, H2, which does not include DE 4/14. If a declaration is submitted without the element ItemChargeAmount, a DMSACC will be received, but no further notifications.
please keep in mind that CDS Trade Test is a test system and, while every effort has been made to ensure the KEL and other documentation are comprehensive, if you do encounter any issues, please continue to raise these via the SDST keeping in mind that trade test is currently supported from 9am to 5pm Monday to Friday, excluding UK bank holidays.