TTM8.1.2 is Live
8th October 2019
TTM8.1.2 is now live and available for you to resume testing
This deployment was proven end-to-end by submitting the XML sample messages for both Imports and Exports into CDS from v2.0 of the API. All expected notifications were received.
As a reminder, the TTM8.1.2 release enables Exports inventory linking dual running between CDS Trade Test and CHIEF HMUT. This means the Trade Test environment is no longer using a stubbed CHIEF service. Section E-5 (Exports Inventory Linking Dual Running) of the attached CDS Trade Test Scenarios Document outlines the functionality that will be enabled once connectivity has been established between CDS Trade Test and the CHIEF HMUT service.
The following supporting documents have also been released:
Trade Test Scenarios Document – This has been re-attached with no change following the TTM8.1 release, and 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 has been enabled by Exports inventory linking dual running between CDS Trade Test and CHIEF HMUT.
TTM8.1.2 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. As the ability to carry out arrivals and departures in linked to both the EORI and the goods location, there are a range of location codes and authorised operators configured to support your testing Trade Test outlined in this document.
Please be aware that only a subset of location codes are valid for both HMUT and CDS Trade Test. One of the following location codes must be used on tests exercising Exports inventory linking dual running functionality with HMUT. This applies also to CSP transactions, where the operators are authorised to arrive or depart for all locations.
Valid Location Codes for Exports Inventory Linking Dual Running
TTM8.1.2 Known Error Log (KEL) – since the TTM8.1.0 release, 3 known errors have been resolved and an additional 10 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.
KEL ID 138 outlines the CDS good location codes that are currently compatible with CHIEF. Please note that dual running scenarios that do not use a Goods Location code from this list will not be successful.
XML Sample Messages – new XML samples have been produced for this release. Please note that 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.
To test Exports inventory linking dual running scenarios in Trade Test, please note that only a subset of location codes are valid for both HMUT and CDS Trade Test. Please ensure to use the correct dual running location codes when adapting any of the Exports sample XMLs for use in a dual running scenario.
Please also 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.
Finally, 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.
- IM_Amendment_Sample_TC01 – Amendment request for a Type B declaration and associated CDS response
- IM_Cancellation_Sample_TC01 – Cancellation request for a Type Z declaration and associated CDS response
- IM_GPN_Sample_TC01 - Used to support the testing of non-inventory linked arrivals using the Arrival Notification endpoint
- IM_IVL_Sample_TC01 – Inventory linked pre-lodged Type F declaration followed by arrival of the goods, includes all CSP notifications
- IM_IVL_Sample_TC02 – Inventory linked pre-lodged Type F declaration with an inventory mismatch and revalidation, includes all CSP notifications
- IM_IVL_Sample_TC05 – Inventory linked pre-lodged Type D declaration with a physical control, includes all CSP notifications
- IM_IVL_Sample_TC06 – Inventory linked Type pre-lodged Type F declaration with an inventory mismatch followed by a null amendment, includes all CSP notifications
- IM_A_Sample_TC01 – Standard frontier Type A declaration
- IM_A_Sample_TC02 – Type A declaration with End Use Relief
- IM_A_Sample_TC03 – Type A declaration with immediate payments as a method of payment
- IM_A_Sample_TC04 – Type A declaration for goods entered into a Customs Warehouse
- IM_A_Sample_TC05 – Type A declaration with an Excise duty calculation
- IM_A_Sample_TC06 – Type A declaration with an EU country of origin for goods which have a protected designation of origin
- IM_A_Sample_TC07 – Type A declaration with a quota which has been partially allocated
- IM_A_Sample_TC08 – Type A declaration that triggers a documentary control task which is then blocked, using Packaging/Type PK
- IM_A_Sample_TC09 – Type A declaration that triggers a physical control task which is then blocked, using Packaging/Type PK
- IM_B_Sample_TC01 – Simplified occasional frontier Type B declaration
- IM_C_Sample_TC01 – Standalone simplified Type C declaration
- IM_D_Sample_TC01 – Standard pre-lodged Type D declaration
- IM_D_Sample_TC02 – Pre-lodged Type D declaration where the combination of commodity code and country of origin attract CAP safeguarding measures
- IM_D_Sample_TC03 – Pre-lodged Type D declaration for entry to an approved customs warehouse, being re-imported following temporary export under outward processing procedures
- IM_E_Sample_TC01 – Simplified occasional pre-lodged Type E declaration
- IM_F_Sample_TC01 – Standalone pre-lodged Type F declaration
- IM_J_Sample_TC01 – Standalone inventory summary Type J declaration
- IM_K_Sample_TC01 – Pre-lodged inventory summary Type K declaration
- IM_Y_Sample_TC01 – Type Y declaration with value build-up, currency conversion, and preference of 300
- IM_Y_Sample_TC03 – Type Y declaration with an ADD commodity and currency conversion
- IM_Y_Sample_TC04 – Type Y declaration with Onward Supply Relief (OSR)
- IM_Y_Sample_TC05 – Type Y declaration with invalid EORIs that generates a DMSREJ with CDS12005 and CDS12007 errors
- IM_Z_Sample_TC01 – Type Z declaration where the agent has standing authority to use the trader’s DAN
- IM_Z_Sample_TC02 – Type Z declaration with indirect representative and a FEC check
- IM_Z_Sample_TC03 – Type Z declaration with value build-up and a FEC check
- IM_Z_Sample_TC04 – Type Z declaration with Inward Processing (IP) suspension
- IM_Z_Sample_TC05 – Type Z aggregated supplementary declaration
- IM_Z_Sample_TC06 – Type Z declaration with Inward Processing (IP) where duty is calculated using manual override
- IM_Z_Sample_TC07 – Type Z declaration with 3 goods items claiming trade preference and triggering a security deposit
- EX_C_Sample_TC01 – Standalone Exports Simplified Type C declaration
- EX_D_Sample_TC01 - Inventory linked Type D Air declaration with one MUCR and one DUCR, arrived and departed at MUCR level
- EX_D_Sample_TC02 - Two Inventory linked Type D Maritime declarations with one DUCR arrived separately, consolidated into one MUCR, MUCR shut and departed
- EX_D_Sample_TC03 - Inventory linked Type D Maritime declaration with one DUCR, arrived and departed at DUCR level
- EX_D_Sample_TC04 – Inventory linked Type D declaration that is arrived 5 times at the same location
- EX_D_Sample_TC05 – Inventory linked Type D declaration that is arrived and triggers a physical control
- EX_D_Sample_TC06 – Inventory linked Type D declaration that is arrived and departed at two different locations
- EX_D_Sample_TC07 – Inventory linked Type D declaration that is arrived and there is a control on goods exported under excise duty suspension
- EX_E_Sample_TC01 – Exports pre-lodged occasional simplified Type E declaration which is arrived
- EX_F_Sample_TC01 – Exports pre-lodged simplified Type F declaration with a special procedure which is arrived
- EX_K_Sample_TC01 – Exports pre-lodged inventory declaration which is arrived
- EX_K_Sample_TC02 – Exports pre-lodged inventory declaration which is arrived and triggers a control
- NEW EX_K_Sample_TC03 – Dual running Exports pre-lodged inventory declaration on CHIEF which is arrived via CDS
- NEW EX_K_Sample_TC04 – Dual running Exports pre-lodged inventory declaration on CHIEF which is arrived via CDS
- EX_Y_Sample_TC01 – Type Y declaration
- EX_Y_Sample_TC02 – Type Y declaration with DIT licensing
- EX_Y_Sample_TC03 – Type Y declaration with AEO authorisation
- EX_Z_Sample_TC01 – Type Z declaration
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.
Should you have any Trade Test queries or other questions relating to your product development, you can contact the HMRC dedicated Software Developers Support Team mailbox. Queries received through this mailbox are addressed using a triage system to ensure resolution by the Policy, IT and Project Teams.
Back to news