acita.org€¦ · web viewpurpose. to support readiness for customs declaration service (cds),...

Customs Declaration Service (CDS)

CDS Trade Test ScenariosHigh-level scenario descriptions to support testing of new functionality introduced in CDS Trade Test

Date of issue: 04.03.2020

Team: Customs Transformation

Version: 9.0.2

| Security Marking | Customs Declaration Service | 1


Change Log

Document name: CDS Trade Test Scenarios

Abstract:Outline the new functionality that will be available in Trade Test, and to provide high level example scenarios that demonstrate the happy and unhappy paths that can be tested in this trade test.

Status: IssuedStability: Baselined

Team: Customs Transformation

Version reference Update Author(s) Date

1.0 TTM5 Scope baselined for issue SP 13/12/18

1.1 Reformatting and introduction SC 03/01/19

1.2 Reformatting and comments SC 07/01/19

1.3 Reformatting SC 08/01/19

1.4 Revision EB 10/01/19

1.5 Revisions SP 11/01/19

1.6 Glossary EB 11/01/19

1.7 Revision SP 22/01/19

1.8 TTM6.1 Scope Adjustments GS 21/02/19


1.10 Revision MS 25/02/19


2.0 TTM6.1 baselined for issue EB 25/02/19

2.1 TTM6.2 Scope Adjustments GS 28/02/19

2.2 Amendments added EB 08/03/19

2.3 Revision GS 08/03/19




3.0 TTM6.2 baselined for issue SP 28/03/19





Version reference Update Author(s) Date

6.2 Revision Multiple 04/07/19

7.0 TTM8.0 baselined for issue HS 08/07/19

7.1 Imports updates SP 15/08/19

7.2 Exports updates BM 28/08/19

7.3 Revisions EB 29/08/19

7.4 Revisions EB 30/08/19

7.5 Revisions following review EB 02/09/19

7.6 Final revision EB 03/09/19

8.0 Baselined for Issue EB 04/09/19

8.1 Correction EB 04/09/19

8.2 Controls update & correction HS 02/12/19

8.4 IVL Timer Revised YA 15/01/20

8.5 Imports Updates IA 20/01/20

8.6 Exports Updates DC 20/01/20

8.7 Product Owner Review CC 21/01/20

8.8 Revisions following review YA 22/01/20

9.0 Baselined for issue YA 30/01/20

9.1 Stimulation updates SHR 04/03/20



Contents

A. Introduction.....................................................................................................71. Purpose.......................................................................................................................................7

2. Trade Test Summary..................................................................................................................7

B. Procedure Codes and Additional Procedure Codes....................................81. Imports Procedure Codes...........................................................................................................8

2. Exports Procedure Codes...........................................................................................................8

C. High-level Declaration Processing Functionality in Trade Test (Imports and Exports)......................................................................................................................9

1. Amendment of Declarations........................................................................................................9

1.1 Happy Path Scenarios.......................................................................................................................... 101.2 Unhappy Path Scenarios................................................................................................................111.3 Out of Scope......................................................................................................................................... 11

2. Control Tasks............................................................................................................................12

2.1 Happy Path Scenarios.......................................................................................................................... 142.2 Unhappy Path Scenarios...................................................................................................................... 17

3. Document Status Code Validation............................................................................................18


D. High-level Imports Scenarios in Trade Test................................................231. Imports Frontier and Pre-Lodged Declaration Types................................................................23


2. Imports Aggregation..................................................................................................................27


3. Imports Authorisation Validation...............................................................................................28

3.1 CCG Authorisation................................................................................................................................ 283.2 Authorisations Matrix............................................................................................................................ 293.3 Happy Path Scenarios.......................................................................................................................... 303.4 Unhappy Path Scenarios...................................................................................................................... 32

4. Relief and Suspensions for Imports..........................................................................................34


5. Imports Excise Duty..................................................................................................................40


6. Imports Inventory Linking..........................................................................................................42

6.1 Summary.............................................................................................................................................. 426.2 Workarounds and Known Defects.........................................................................................................43


Customs Declaration Service (CDS)6.3 Happy Path Scenarios.......................................................................................................................... 436.4 Unhappy Path Scenarios...................................................................................................................... 44

7. Imports Simulated Immediate Payment Service.......................................................................45

7.1 Summary.............................................................................................................................................. 457.2 EORIs for Immediate Payments Scenarios...........................................................................................467.3 Happy Path Scenarios.......................................................................................................................... 477.4 Unhappy Path Scenarios...................................................................................................................... 487.5 Out of Scope......................................................................................................................................... 49

8. Trade Preference with Security.................................................................................................49


9. Additional Security Deposit Functionality..................................................................................51

9.1 Happy Path Scenarios.......................................................................................................................... 5110. EU Country of Origin.............................................................................................................51

10.1 Happy Path Scenarios........................................................................................................................ 5211. Simulated Quota Service.......................................................................................................52

11.1 Happy Path Scenarios........................................................................................................................ 53

E. High-level Exports Scenarios in Trade Test...............................................551. Exports Supplementary Declarations with Authorisation Validation.........................................55


2. Exports Licensing......................................................................................................................59


3. Exports Inventory Linking..........................................................................................................61


4. Additional Frontier Declaration Types for Exports....................................................................74

4.1 Happy Path Scenarios.......................................................................................................................... 755. Exports Inventory Linking Dual Running...................................................................................84


F. Summary of Existing Scope (TTM5.1 and earlier)......................................911. Accept and validate...................................................................................................................91

1.1 Notifications.......................................................................................................................................... 911.2 Rejection of duplicate submissions.......................................................................................................91

2. Duty calculation.........................................................................................................................92

2.1 Anti-dumping duty (ADD) (imports only)...............................................................................................922.2 Common Agricultural Policy (CAP) goods (imports only)......................................................................93

3. Value build up...........................................................................................................................93

4. Country codes...........................................................................................................................94

5. Currency conversion.................................................................................................................94

6. Dwell time..................................................................................................................................94


Customs Declaration Service (CDS)7. Cancellations.............................................................................................................................95

8. Front end credibility (FEC) checks............................................................................................95

9. Binding tariff information (BTI) reference number.....................................................................95

10. Locally held licenses..............................................................................................................96

11. DAN Validation......................................................................................................................96

G. Functionality Out of Scope for Trade Test..................................................971. Post-Clearance Cancellations...................................................................................................97

2. Country codes: continental shelf, prohibited, special fiscal territories.......................................97

3. Paper licenses...........................................................................................................................97

4. CAP scenarios for exports........................................................................................................97

5. Registration and subscription....................................................................................................97

6. Special procedures...................................................................................................................97

7. Payment processing..................................................................................................................98

H. Glossary of terms..........................................................................................99



A. Introduction

1. Purpose

To support readiness for Customs Declaration Service (CDS), the CDS Programme is incrementally delivering functionality across a number of Trade Test milestones to provide software developers and Community System Providers (CSPs) with a CDS environment against which their software can be tested.

The purpose of this document is to outline the functionality that will be available in Trade Test, and to provide high level example scenarios that demonstrate the happy and unhappy paths that can be tested in this phase of trade test. Happy path scenarios are those where the declaration should be accepted and cleared by the CDS system with all expected notifications received. Unhappy path scenarios are those where the declaration should be rejected by the CDS system during validation and a DMSREJ notification is received.

2. Trade Test Summary

The CDS Programme is implementing a more iterative Trade Test release process where smaller batches of functionality are dropped into Trade Test when they are ready.

Functional areas across Imports and Exports have been prioritised for Trade Test based on the high-level delivery and migration strategy of the CDS Programme, which is delivering Imports Supplementary declarations, followed by Imports Frontier declarations and Exports.

In terms of Imports supplementary declarations (Type Y and Z), CDS Trade Test supports a range of Relief and Suspensions scenarios (see Section C1) and procedure codes (see Section B). This includes the submission of an aggregated supplementary declaration for multiple removals where the Header and Item level data on the declaration are the same.

CDS Trade Test further supports both inventory linked and non-inventory linked Imports frontier and pre-lodged declaration types A, B, C, D, E, and F, including the ability to arrive or cancel a pre-lodged declaration. It also supports Type J and K Customs Clearance Request declarations.

Complex functional Imports scenarios that are not dependent on declaration type are also in scope, such as those involving currency conversion, value build-up, cancellations, the use of locally held Department for International Trade (DIT) and Rural Payments Agency (RPA) licenses that do not require any controls, and authorisation validation.

Finally, Exports procedure codes for supplementary declarations, frontier movements, authorisation validation, and DIT licensing are also in scope.

Sections C, D, and E of this document highlights the high-level functional test scenarios that are enabled by CDS Trade Test, excluding those from the TTM5.1 release or earlier.

It should be noted that HMRC support will not be able to assist with tests that diverge from the defined scope of each trade test milestone.



Additionally, trade test environment is able to support testing of ‘legitimate’ business volume scenarios and other automated declaration testing.

Business volume scenarios refer to genuine day-in-the-life-of tests which align to current trader patterns on CHIEF or CDS. For example, the arrival of a vessel at a port or a typical day’s submission of supplementary declarations. Full performance and throughput analysis should not be conducted in Trade Test (e.g. to break point). Trade Test is not a performance testing facility and has not been configured to the same standard as a Production environment. Any measured or perceived levels of system performance in Trade Test should not be expected to match the final Production system.

Delays during declaration processing may be experienced, particularly during peak periods, as a result of contention within the environment. Users of CDS Trade Test are strongly advised against conducting performance testing in Trade Test as this may impact the stability of the environment for all users.

Real customer data should not be used in any test environment. .

Test data, including pre-authorised Economic Operator Registration and Identification (EORI) numbers, will be provided for each trade test milestone. Only these EORI numbers should be used for declarations in CDS Trade Test. Please refer to the Test Data Library, issued as part of the release notes for each milestone, for more information.

B. Procedure Codes and Additional Procedure Codes The following section outlines the procedure codes (PCs) and additional procedure codes (APCs) that will be available during this phase of trade test, and the declaration types for which they apply.

1. Imports Procedure Codes

All PCs and APCs specified in the UK Trade Tariff: volume 3 are in scope for submission on imports declarations in this phase of trade test. Please refer to the following appendices for guidance on how to submit these PCs and APCs:

- Requested and Previous Procedure Codes

- Additional Procedure Codes

Please refer to the Inventory Tariff (issued via SDST on 24/06/19) for the full list of PCs and APCs that can be submitted on Type J and K declarations.

2. Exports Procedure Codes

For this phase of trade test all PCs and APCs are in scope for submission on all export declaration types (A, B, C, D, E, F, J and K).


https://www.gov.uk/guidance/additional-procedure-codes-for-data-element-111-of-cds

https://www.gov.uk/guidance/requested-and-previous-procedure-codes-for-de-110-of-cds

Customs Declaration Service (CDS)Please refer to the UK Trade Tariff, CDS Volume 3 Exports (issued via SDST on 21/02/19) and the Inventory Tariff (issued via SDST on 24/06/19) for further information. These documents can also be found in the Google Drive folder CDS 06 Tariff Manual.

C.High-level Declaration Processing Functionality in Trade Test (Imports and Exports)

This section outlines key functionality available in CDS Trade Test which applies to both Imports and Exports declaration submissions.

1. Amendment of Declarations

Trade Test supports the amendment of any declaration Type A, B, C, D, E, F, J, K, Y or Z that has been accepted on the system but that has not yet cleared.

In order to be accepted, the amendment request will need to be submitted by the same party that submitted the original declaration.

Fields that can be amended include, but are not limited to:

Commodity code

Tax line (e.g. Duty Tax Fee – Type Code)

Payment Amount

Preference code

License

Weight

Value

Currency

Procedure code or special procedure code

Consignee / consignor

Amendments to multiple fields can be submitted through a single amendment request.

Please note that, where an invalid amendment request is submitted to CDS (e.g. amend commodity code without required additional document), a DMSREJ will be received for the invalid amendment and the declaration will not clear until a null amendment or valid amendment has been submitted for that declaration.


Customs Declaration Service (CDS)1.1 Happy Path Scenarios

1.1.1 Amendment of a Frontier Declaration

Step Who Declarant submits a frontier declaration (example: Type A declaration). Declarant

The declaration is validated. CDS

The declaration is accepted on the system but is not cleared. Dwell time begins.

CDS

Declarant is notified through the appropriate notifications. CDS

Declarant submits an amendment request during the 10 minute dwell time to amend one or more of the trader-given fields other than the LRN, Dec Type and Additional Dec Type.

Declarant

The declaration is re-validated and re-risked. The submitter-declaration relationship is valid (as submitters can only amend declarations that they submitted).

CDS

The amendment is accepted. CDS


1.1.2 Amendment of a Type Y or Z Supplementary Declaration

Step Who Declarant submits a Type Y or Z declaration. Declarant


The declaration is accepted on the system but is not cleared. Dwell time begins.

CDS


Declarant submits an amendment request during the 10 minute dwell time to amend one or more of the trader-given fields other than the LRN, Dec Type and Additional Dec Type.

Declarant

The declaration is re-validated and re-risked. The submitter-declaration relationship is valid (as submitters as submitters can only amend declarations that they submitted).

CDS

The amendment is accepted. CDS



Customs Declaration Service (CDS)1.2 Unhappy Path Scenarios

1.2.1 Invalid Submitter of the Amendment

Step Who Submitter 1 submits a Type Y or Z declaration, which is accepted by CDS.

Declarant

CDS sends the appropriate notifications to submitter 1 notifying them of the acceptance.

CDS

Submitter 2, who is not the original declarant, submits a request to amend one or more of the amendable fields on the declaration during the dwell time (after the declaration has been accepted, but before it has cleared on the system).

Declarant

The amendment request is rejected as submitters can only amend declarations that they submitted, and the EORI of submitter 2 does not match the EORI of submitter 1.

CDS

CDS sends the appropriate notifications to submitter 2 notifying them of the rejection of the amendment.

CDS

1.2.2 Amendment of a Restricted Field

Step Who Declarant submits a Type Y or Z declaration. Declarant

The declaration is validated and risked, generating no controls. CDS

The declaration is accepted on the system but is not cleared. CDS


Declarant submits an amendment request to amend one or more of the restricted fields on an amendment: LRN, Dec Type or Additional Dec Type.

Declarant

The amendment is rejected due to the field(s) being restricted. CDS


1.3 Out of Scope

The following scenarios are currently not in scope for Trade Test.

Please do not submit declarations using the functionality in this section, as they will not be able to be processed correctly.



Functionality DescriptionAmendment of a Pre-Lodged Declaration

Amendments of a pre-lodged declaration (e.g. Type F) cannot be processed for this trade test.

Post-Clearance Amendments Amendments can only be made during the dwell time. Declarations cannot be amended once they have cleared.

2. Control Tasks

This phase of trade test provides functionality to test declaration controls and risk responses. Note that in trade test, this functionality is automated and does not require a HMRC operative to respond for the control results.

To test control task functionality in trade test, you will be able to trigger different types of control tasks by adding a specific ‘trigger word’ into the commodity description. Please note, blocking documentary and physical control tasks cannot be initiated on supplementary declarations (these are not valid business scenarios). You must submit a frontier declaration in order to trigger a blocking documentary or physical control task.

Please submit the following as part of the Goods Description (DE 6/8) for the first goods item on your test declaration to test each type of control task:

Imports or Exports

Control Generated Goods description on at least one item

Notifications Received

Imports Non-blocking documentary control task

ttimportdocnonblocking DMSDOC

Blocking documentary control task

ttimportdocblocking DMSDOC

Physical control task ttimportphysical DMSCTL for Type A, B and C declarations.

For pre-lodged declarations, the DMSCTL notification will only be received after the declaration is arrived (if the physical control task is still triggered).

Exports Non-blocking documentary control task

ttexportdocnonblocking DMSDOC


Customs Declaration Service (CDS)Imports or Exports

Control Generated Goods description on at least one item

Notifications Received

Blocking documentary control task

ttexportdocblocking DMSDOC

Physical control task ttexportphysical DMSCTL for Type A, B and C declarations.

For pre-lodged declarations, the DMSCTL notification will only be received after the declaration is arrived (if the physical control task is still triggered).

All controls will be automatically cleared by the CDS Trade Test system, simulating a successful documentary or physical check.

To trigger a blocking and final control response, simulating the seizure, detention, or destruction of goods, the Packaging/Type (DE 6/9) of the first goods item should be entered as 'PK' for both Imports and Exports.

Please note that Blocking Documentary controls and Physical controls are not possible when submitting a Supplementary Declaration. Control tasks will always be non-blocking if they are raised against a Supplementary Declaration. Frontier declarations must be used to trigger blocking controls on a declaration.

For this phase of Trade Test, please note that, where Packaging/Type ‘PK’ has been entered to signal a blocking and final control, 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 has been developed by the CDS Programme. The manual action is to be carried out by a HMRC operator during a prescribed window. Any questions regarding this should be directed to SDST.

Please refer to the ‘unhappy’ path section below for a high-level summary of this process.

To test controls in Exports multiple arrivals and departures scenarios, the original declaration should include the appropriate ‘trigger word’ in DE 6/8 as per the guidance above and then the declaration should be arrived.

To trigger a control on a subsequent arrival, the EAL message must contain a specific location code, which will initiate a second control response. Please submit the following on a subsequent (not the first) EAL message to test each type of control task:



Re-Arrival Control Generated

UNLOCODE Location EORI

Physical control GBAUBKGLONSVW Barking [London] - Sivyer Wharf

GB025115111987

Documentary control GBAUBIFBARBIF Barrow in Furness GB025115111987Non-blocking documentary control

GBAUIPSIPSOTE Ipswich GB025115111987

Physical control GBAUCDFCDFCDF Cardiff Docks GB025115133100Documentary control GBAUPMEPTMPME Portsmouth GB025115133100Non-blocking documentary control

GBAUCOWCOWCOW Cowes - Medina Wharf

GB025115133100

Physical control GBAUFISFISFIS Fishguard GB025115155321Documentary control GBAUFLEFLEFLE Fleetwood GB025115155321Non-blocking documentary control

GBAUFOYFOYFOY Fowey Harbour GB025115155321

Physical control GBAUDVRDOVDVR Dover GB025115166433Documentary control GBAUGOOGOOGOO Goole GB025115166433Non-blocking documentary control

GBAUGRGGRGGRG Grangemouth Docks GB025115166433

Physical control GBAUHYMHEYHYM Heysham GB025115188654Documentary control GBAUHLYHLDHLY Holyhead GB025115188654Non-blocking documentary control

GBAUHULHULHUL Hull GB025115188654

Please refer to the Exports Inventory Linking documentation, XML samples, and scenarios in this section for further detail regarding these processes.

2.1 Happy Path Scenarios

2.1.1 Physical Control Task

Step Who Declarant submits a declaration which triggers a physical control task, as well as a successful review of this control task.

Declarant

The control task is raised. CDS

A positive control response is produced and the declarant notified (DMSCTL).

CDS

The declaration is successfully validated. CDS

Declaration is accepted and cleared. CDS



Customs Declaration Service (CDS)2.1.2 Blocking Documentary Control Task

Step Who Declarant submits a declaration which triggers a blocking documentary control task, as well as a successful review of this control task.

Declarant



CDS




2.1.3 Non Documentary Control Task

Step Who Declarant submits a declaration which triggers a non-blocking documentary control task, as well as a successful review of this control task.

Declarant



CDS




2.1.4 Exports Type D declaration, control, DUCR declared

Declaration: Type D declaration (B1 data set, 1040 or 2300), control, DUCR declared.

Movements/Consolidations: DUCR arrived at location (a), receives P2P, DUCR frustrated inland, arrived at location (b) and departed from location (b)

Step Who Declarant submits a type D declaration with the following:

A DUCR created by the declarant and declared at header level in 2/1

Declarant

Declaration validation takes place on the data entered. CDS

Where validation is successful, send a DMSRCV to the trader with the MRN for the pre-lodged declaration.

CDS

Loader submits EAL message to CDS for the declared DUCR including: Goods Location of arrival (a) Master Opt Value

Loader



Step Who Transport Details

Sends a technical acknowledgement to the loader on receipt of each of their EAL messages

CDS

CDS processes arrival of declaration (DUCR) including re-validation of the declaration

CDS

Where validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration. Declaration is then processed by CDS including risk assessment.

CDS

CDS sends to the loader an ERS message for the EAL containing the status of the declaration (ROE/SOE)

CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSLoader sends incomplete departure message (EDL without transport details entered) to indicate the desire not to exit from the current location.

Loader

CDS processes EDL message and sends technical acknowledgement to the loader on receipt of their EDL message.

CDS

Processes EDL message and sends UKCTRL to the loader as acknowledgement

CDS

Loader submits EAL message to CDS for the declared DUCR including: Goods Location of arrival (b) Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of declaration (DUCR) CDSCDS sends to the loader an ERS message for the EAL containing the status of the declaration (ROE/SOE)

CDS

If clearance (P2P) is given, send a DMSCLE-like notification to the declarant

CDS

If P2P given by ERS message then loader sends an EDL message for DUCR to CDS to notify departure from location (b)

Loader

Sends technical acknowledgement to the loader on receipt of their EDL message

CDS


CDS

On finalisation of the declaration CDS sends DMSEOG message to the declarant for each DUCR in the consolidation.

CDS



2.2.1 Physical Control Task

For this phase of Trade Test, please note that, where Packaging/Type ‘PK’ has been entered to signal a blocking and final control, 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 has been developed by the CDS Programme. The manual action is to be carried out by a HMRC operator during a prescribed window. Any questions regarding this should be directed to SDST.

Step Who A Self-Representing Type A Frontier Declaration is submitted which triggers a physical control task:

Goods Description of ttimportphysical Packaging/Type of PK for the first goods item which results in a

blocking and final control task being produced. Country of Origin of US Commodity code of 85109000.

Declarant


A negative control response is produced. CDS

The declaration is rejected. CDS

The declarant receives the following trader notifications:DMSCTL, DMSINV.

CDS

2.2.2 Blocking Documentary Control Task

For this phase of Trade Test, please note that, where Packaging/Type ‘PK’ has been entered to signal a blocking For scenarios where no payment is received and final control, 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 has been developed by the CDS Programme. The manual action is to be carried out by a HMRC operator during a prescribed window. Any questions regarding this should be directed to SDST.

Step Who A Self-Representing Type A Frontier Declaration is submitted which triggers a documentary control task:

Goods Description of ttimportdocblocking Packaging/Type of PK for the first goods item which results in a

blocking and final control task being produced Country of Origin of US Commodity code of 85109000

Declarant


A negative control response is produced. CDS| Security Marking | Customs Declaration Service | 17


Step Who


The declarant receives the following trader notifications:DMSDOC, DMSINV.

CDS

3. Document Status Code Validation

Additional scenarios for document status codes will be available in this phase of trade test.


3.1.1 CCG Authorisation waiver

Step Who Type A declaration is received into DMS which was submitted by a self representing trader for multiple items (2), where CDS will waive CCG Authorisation validation on goods item 1 and performs CCG Authorisation validation on goods item 2.Goods item 1 contains:

Additional document code C505 Reference number: GBCGUguaranteenotrequired-CCC Document status code CC

Goods item 2 contains: Additional document code C505 Reference number, comprised of: 2 digit country code (GB), 3

digit authorisation code (CGU), authorisation reference number No document status code

Declarant

Both items are accepted and the declaration cleared. CDS

The following Trader Notifications are generated and sent to the Trader: DMSACC, DMSTAX, DMSCLE.

CDS

3.1.2 Document status code XW (Waiver Claimed)

Step Who A self-representing Type A Declaration is submitted by a Trader.

The Declaration includes a Licence Document Code of 9100 (Firearms)

The Additional Document Data Element 2/3 contains a Status Code of 'XW' (Waiver claimed), and no licence reference

Declarant



Step Who number/document identifier.

A reason for waiver in D.E 2/3 A commodity code and country of origin which requires the

document code 9100 (example: 9301200000, with country of origin Canada)

CDS will not decrement the Licence as there is no reference supplied. CDS

The Declaration is accepted and cleared. CDS


CDS

3.1.3 Document status code XU (Unknown, specific document cannot be identified)

Step Who A self-representing Type Y Declaration is submitted by a Trader.

The Declaration includes a Licence Document Code of N934 (Customs value DV1)

The Additional Document Data Element 2/3 contains a Status Code of 'XU' (Unknown, specific document can’t be identified )

A commodity code and country of origin which requires the document code N934 (example: 6203423500, with country of origin US)

Declarant

The declaration is accepted and cleared as XU is an acceptable Status Code pertinent to the Additional Document Code N934.

CDS


CDS

3.1.4 Document status code XF (Document not required – goods not going into free circulation)

Step Who

A self-representing Type A Declaration for Inward Processing (Category H4, example procedure code 5100 000) is submitted by a Trader.

The Declaration includes a Document Code of A017 (Certificate of Authenticity)

The Additional Document Data Element 2/3 contains a Status Code of 'XF' (Document not required – goods not going into free circulation)

A commodity code and country of origin which requires the document code N934 (example: 0202209011, with country of origin Canada)

Proof of valid special procedures authorisation for Inward

Declarant



Step Who

Processing (IP)

The declaration is accepted and cleared. CDS


CDS

3.1.5 Document status code AE (Document attached – exhausted by (or only applies to) this entry)

This test is designed to prove that CDS is able to trigger different behaviours against Licences depending on the Document Status Code (D.E. 2/3) indicated against the document code (D.E. 2/3).

Step Who A self-representing Type A Declaration is submitted by the trader, with the following:

Procedure code 4071 000 Document code (License): C673 (Control on illegal, unreported

and unregulated fishing) Document status code: AE Commodity code 0302190000 (Salmonidae, excluding edible fish

offal of subheadings 0302 91 to 0302 99) Country of origin: Jamaica

Declarant

The license is not decremented. The Declaration is accepted and cleared. CDSThe following Trader Notifications are generated and sent to the Trader:DMSACC, DMSTAX and DMSCLE.

CDS

3.1.6 Document status code EP (Electronic details on CDS, part use (applies to this and other entries))

Step Who A Type A Import Declaration (H1) is submitted, with the following:

Procedure code 4000 000 Document (Licence) L001 (Rural Payments Agency (RPA)

Common Agricultural Policy (CAP) import licences) Document Status Code of EP Commodity Code 1006103000 (Rice in the husk, round grain) Preference code 120

Declarant

The licenced quantity in ILMS is decremented accordingly for that licence.

CDS

The declaration is accepted and cleared by DMS CDS



Step Who The following Trader Notifications are generated and sent to the Trader:DMSACC, DMSTAX and DMSCLE.

CDS

3.1.7 Document status code JA (already attributed on simplified declaration)

Step Who A self-representing Type Y Import Declaration into free circulation is submitted by the Trader, with the following:

Procedure code 4000 000 Document code (Licence) C690 (FLEGT import licence for

timber) Document status code 'JA' (already attributed on simplified

declaration) Commodity Code 440711200 (Wood, Pine, Planed) Country of origin Indonesia.

Declarant

The licence is not decremented. CDS


The following Trader Notifications are generated and sent to the Trader: DMSACC, DMSTAX and DMSCLE.

CDS

3.2 Unhappy Path Scenarios

3.2.1 Document code XA (Electronic or paper document to be advised)

Step Who A self-representing Type A Declaration is submitted by a Trader.

The declaration includes a Licence Document Code of N002 (Certificate of conformity with the European Union marketing standards for fresh fruit and vegetables).

The Additional Document Data Element 2/3 contains a Status Code of 'XA' (Electronic or paper document to be advised)

A commodity code and country of origin which requires the document code N002 (example: 0803901000, with country of origin Indonesia)

Declarant

The Declaration is therefore rejected by CDS because of the Document Status Code of 'XA', which cannot be used against a document code for a licence.

CDS

A DMSREJ Trader Notification is produced and sent to the Trader. CDS



D.High-level Imports Scenarios in Trade TestThis section highlights the high-level functional test scenarios that are enabled in this phase of trade test. The scenarios in this document are not meant as a replacement for the message sequence diagrams issue by the CDS Programme.

Please note that DMSTAX and DMSCLE will continue to be received as separate notifications for all declaration types and payment methods.

Trade test users are advised to refer to the latest End to End Sequence Diagrams document for further detail on all declaration submission journeys. This document is available on Google Drive in the folder CDS 10 End to End Sequence Diagrams.

1. Imports Frontier, Pre-Lodged and Supplementary Declaration Types

Trade Test will support the submission of the following declaration types:

Type A: Standard Frontier Declaration

Type B: Simplified Occasional Frontier Declaration

Type C: Simplified Frontier Declaration

Type D: Standard Pre-lodged Declaration

Type E: Simplified Occasional Pre-Lodged Declaration

• Type F: Simplified Pre-Lodged Declaration

• Type J: Customs Clearance Request (Goods Arrived)

• Type K: Customs Clearance Request (Goods have not yet arrived)

• Type Y: Supplementary Declaration

• Type Z: EIDR Supplementary Declaration

This section outlines high-level happy and unhappy path scenarios for declaration types A, B, D, E, J and K. Since TTM6.2, the scope of Trade Test has included the arrival of a non-inventory linked pre-lodged declaration and the cancellation of both inventory linked and non-inventory linked pre-lodged declarations (Types D, E, F).

For cancellations, the submitter will be able to send a cancellation request (pre-clearance) during the 10 minute dwell timer.

For the purposes of CDS trade test only, the declaration will be automatically invalidated. The submitter will receive notice that the declaration has been cancelled following a successful cancellation request.



1.1.1 Submission of a Type D Declaration

This section articulates the full declaration journey associated with a pre-lodged declaration type, including arrival using a Goods Presentation Notification (GPN). Since TTM6.2.0, it has been possible to cancel or arrive all pre-lodged declaration types in Trade Test.

Step Who Declarant submits a Type D pre-lodged declaration. Declarant

The declaration is successfully validated and received. CDS


The declaration is arrived by submitting a Goods Presentation Notification (GPN).

Declarant

The declaration is re-validated and re-risked. CDS



1.1.2 Submission of a Type A declaration

Step Who Declarant submits a Type A declaration. DeclarantThe declaration is successfully validated. CDSThe declaration is accepted and cleared. CDSDeclarant is notified through the appropriate notifications. CDS

1.1.3 Submission of a Type E Declaration

This section articulates the full declaration journey associated with a pre-lodged declaration type, including arrival using a GPN. Since TTM6.2.0, it has been possible to cancel or arrive all pre-lodged declaration types in Trade Test.

Step Who Declarant submits a Type E pre-lodged declaration. DeclarantThe declaration is successfully validated and received. CDSDeclarant is notified through the appropriate notifications. CDSThe declaration is arrived by submitting a Goods Presentation Notification (GPN).

Declarant

The declaration is re-validated and re-risked. CDSThe declaration is accepted and cleared. CDSDeclarant is notified through the appropriate notifications. CDS


Customs Declaration Service (CDS)1.1.4 Submission of a Type B Declaration

Step Who Declarant submits a Type B declaration. DeclarantThe declaration is successfully validated. CDSThe declaration is accepted and cleared. CDSDeclarant is notified through the appropriate notifications. CDS

1.1.5 Submission of a Type J Declaration with C21EIDR dataset

Step Who Declarant submits a Type J declaration with C21EIDR dataset with proof of full EIDR authorisation.

Declarant

The declaration is successfully validated. CDSThe declaration is accepted and cleared. CDSDeclarant is notified through the appropriate notifications. CDS

1.1.6 Submission of a Type J Declaration with C21i dataset (Customs Clearance Request)

Step Who Declarant submits a Type J declaration with C21i dataset with a MUCR at header level.

Declarant

An inventory linking request is triggered from the MUCR submitted. CDSThere is a successful inventory linking match. An inventory release message is sent for matching and release of the goods.

CDS

The declaration is successfully validated. CDSThe declaration is accepted and cleared. CDSThe goods are released from the port. Declarant is notified through the appropriate notifications. CDS

1.1.7 Submission of a Type K Declaration

This section articulates the full declaration journey associated with a pre-lodged declaration type, including arrival using a Goods Presentation Notification (GPN). Since TTM6.2.0, it has been possible to cancel or arrive all pre-lodged declaration types in Trade Test



Step Who Declarant submits a Type K pre-lodged declaration with a C21EIDR or C21i dataset.

Declarant

The declaration is successfully validated and received. CDSDeclarant is notified through the appropriate notifications. CDSThe declaration is arrived by submitting a Goods Presentation Notification (GPN).

Declarant

Please refer to the Type J scenarios for the remaining steps in this journey.


A frontier declaration may be rejected for a number of reasons, driven by the validation rules configured in the CDS Trade Test system according to the UK Trade Tariff: volume 3. The scenarios in this section are not a definitive list and should be considered as examples only.

1.2.1 Procedure Code (D.E 1/10) Not Entered for Declaration Type A

Step Who Declarant submits a Type A Declaration without a procedure code. DeclarantThe declaration fails validation due to the incomplete data item for the declaration type.

CDS

The declaration is rejected. CDSDeclarant is notified through the appropriate notifications. CDS

1.2.2 Procedure Code (D.E 1/10) Not Entered for Declaration Type B

Step Who Declarant submits a Type B Declaration without a procedure code. DeclarantThe declaration fails validation due to the incomplete data item for the declaration type.

CDS

The declaration is rejected. CDSDeclarant is notified through the appropriate notifications. CDS

1.2.3 Goods Items Not Declared on a Type D Declaration when Arrived

This section articulates the full declaration journey associated with a pre-lodged declaration type, including arrival using a GPN.

Step Who Declarant submits a Type D Declaration without any goods items. DeclarantThe declaration is validated and risked. CDSThe declaration is arrived by submitting a Goods Presentation Notification (GPN).

Declarant



Step Who The declaration is re-validated and re-risked. CDSThe declaration fails validation. CDSDeclarant is notified through the appropriate notifications. CDS

1.2.4 Goods Items Not Declared on a Type E Declaration when Arrived

This section articulates the full declaration journey associated with a pre-lodged declaration type, including arrival using a GPN.

Step Who Declarant submits a Type E Declaration without any Goods Items. DeclarantThe declaration is validated and risked. CDSThe declaration is arrived by submitting a Goods Presentation Notification (GPN).

Declarant

The declaration is re-validated and re-risked. CDSThe declaration fails validation. CDSDeclarant is notified through the appropriate notifications. CDS

2. Imports Aggregation

Aggregation enables the submission of a single aggregated supplementary declaration (Type Y or Z) for multiple removals of goods in place of multiple separate supplementary declarations for each goods removal. Only declaration which contain the exact same Header and Item level data can be aggregated.


2.1.1 Aggregation - Type Y

Step Who Declarant submits a Type Y aggregated declaration for multiple removals of goods that does not exceed 10MB. This declaration is completed according to the Data Element Aggregation Rules for CDS.

Declarant

Declaration processed like a normal (non-aggregated) supplementary declaration.

CDS

Declaration is accepted. CDSDeclarant is notified through the appropriate notifications. CDS

2.1.2 Aggregation - Type Z

Step Who Declarant submits a Type Z aggregated declaration for multiple removals of goods that does not exceed 10MB. This declaration is

Declarant


https://www.gov.uk/guidance/data-element-aggregation-rules-for-cds


Step Who completed according to the Data Element Aggregation Rules for CDS. Declaration processed like a normal (non-aggregated) supplementary declaration.

CDS

Declaration is accepted. CDSDeclarant is notified through the appropriate notifications. CDS


2.2.1 Multiple Goods Locations

Step Who Declarant submits a Type Y aggregated declaration for multiple removals of goods. However, two goods locations are submitted in DE 5/23.

Declarant

Declaration processed like a normal (non-aggregated) supplementary declaration through validation and risk.

CDS

Declaration will fail schema validation as DE 2/3 can only be declared once at header level. Note that where aggregated declarations have multiple goods locations, “GBBYAGG + reference number” should be submitted instead of multiple goods locations, as indicated in the Data Element Aggregation Rules for CDS.

CDS

Declarant is notified that the declaration has failed schema validation. CDS

3. Imports Authorisation Validation

3.1 CCG Authorisation

As per the UK Trade Tariff for CDS: volume 3, when MOP E or R (DE 4/8) is used to pay a customs duty, a CCG authorisation must be declared by entering the document code C505 in DE 2/3. If this document code is entered, the Holder of the Authorisation Number (DE 3/39) should be completed with authorisation type code CGU followed by the EORI of the authorised party. Additionally, Guarantee Type (DE 8/2) should be completed with 1 and Guarantee Reference (DE 8/3) should be completed with the UCC comprehensive guarantee reference number under Declaration/ObligationGuarantee/ID.

Please note that, beginning in TTM8.1.0, a waiver to the Comprehensive Customs Guarantee (CCG) authorisation must be declared in line with the guidance in the UK Trade Tariff: volume 3. Specifically, the temporary document code 505N should no longer be used to indicate a CCG exemption. Instead, please use the following status codes in conjunction with document code C505 and GBCGUguaranteenotrequired-CCC, declared in DE 2/3.

For Community Customs Code authorisations, enter status code CC

For OGDs and Public Bodies, enter status code XW| Security Marking | Customs Declaration Service | 27




Customs Declaration Service (CDS) For goods below the statistical threshold, enter status code XB

Where an exemption is being claimed, please note that DE 3/39 should still be completed with the authorisation type code CGU followed by the EORI of the authorised party. In addition, Guarantee Type (DE 8/2) should be completed with a 0 and Guarantee Reference (DE 8/3) should be completed with GuaranteeNotRequired.

Please note that the values in DE 8/3 should be entered as an “Other Reference Number” (Declaration/ObligationGuarantee/ID) and not as a “Guarantee Reference Number” (Declaration/ObligationGuarantee/ReferenceID). Declarations will fail validation if incorrect information is entered in Declaration/ObligationGuarantee/ReferenceID.

3.2 Authorisations Matrix

In addition to the validation of the CCG authorisation, the following additional authorisations will be validated as necessary when a declaration is submitted:

Special Procedures – Inward Processing (IP)

Customs Warehousing (including Excise Warehousing)

Entry in Declarant’s Records (EIDR)

Simplified Procedures (SDP)

Authorised Economic Operator (AEO)

The matrix below shows the authorisations that can be used in combination.

The happy and unhappy path scenarios in this section focus on a single authorisation type, but testing can also be carried out on various combinations of authorisations based on the matrix below (e.g. 3 authorisation types with all valid, 2 valid and 1 invalid, 3 invalid, etc.).

AEO EIDR SDP Special Procedures CW CCG

AEO - 🗸 🗸 🗸 🗸 🗸EIDR 🗸 - x 🗸 x 🗸SDP 🗸 x - 🗸 🗸 🗸Special Procedures 🗸 🗸 🗸 - x 🗸

CW 🗸 x 🗸 x - 🗸CCG 🗸 🗸 🗸 🗸 🗸 -


Customs Declaration Service (CDS)Authorisation validation can be tested in combination with other high-level scenarios in this document, for example:

Inward Processing: Special Procedures Authorisation

Aggregation – Type Y: SDP Authorisation

Aggregation – Type Z: EIDR Authorisation


3.3.1 Valid Special Procedures Authorisation

Special Procedures authorisation applies to Inward Processing, Outward Processing, End Use, and Temporary Admissions. Out of these regimes, only validation of the Inward Processing authorisation is in scope for this phase of trade test.

Step Who Declarant submits a declaration claiming Suspension of Duties under Inward Processing using

An appropriate procedure code/additional procedure code (example: 51 71 000 on a Type Z declaration)

Proof of full authorisation for Special Procedures, including document code C601 and an authorisation number

Proof of CCG authorisation (including document code C505) or exemption (document status code CC)

Declarant

Declaration is validated and risked. The Special Procedures authorisation is validated against the importer and is found to be valid. The CCG authorisation is validated against the importer, declarant, or representative and is either found to be valid, or the party is found to be exempt (document status code CC).

CDS

Duty is calculated with suspension of duties applied to the appropriate tax type(s) for the regime and procedure codes/additional procedure codes used.

CDS

Declarant is notified through the appropriate notifications, including a DMSTAX notification confirming the amount of duty.

CDS

3.3.2 Valid Customs Warehouse Authorisation

Step Who Declarant submits a declaration claiming Suspension of Duties under Customs or Excise Warehousing using both

An appropriate procedure code/additional procedure code (example: 07 00 000 on a Type Y declaration)

Proof of full authorisation for Customs Warehousing, including the appropriate document code for the warehouse type and an authorisation number (for warehouse types U, Y, Z). (example:

Declarant



Step Who document code C517 for Warehouse Type U)

Declaration is validated and risked. The authorisation is validated against the importer (for Warehouse Type U) or the Declarant/Representative (for all other warehouse types) and is found to be valid.

CDS


CDS


CDS

3.3.3 Valid EIDR Authorisation

Step Who Declarant submits a Type Z declaration with document code C514 and a valid authorisation number.

Declarant

Declaration is validated and risked. The authorisation number is validated against the declarant/importer/representative and is found to be valid.

CDS

The declaration is accepted. CDSDeclarant is notified through the appropriate notifications. CDS

3.3.4 Valid SDP Authorisation

Step Who Declarant submits a Type C/F/Y declaration with document code C512 and a valid authorisation number.

Declarant


CDS

The declaration is accepted. CDSDeclarant is notified through the appropriate notifications. CDS

3.3.5 Valid AEO Authorisation

Step Who Declarant submits a declaration with AEO authorisation, including an appropriate document code and authorisation number.

Declarant


CDS

The declaration is accepted. CDS



Step Who Declarant is notified through the appropriate notifications. CDS


3.4.1 Invalid Special Procedures Authorisation (valid CCG)



Proof of full authorisation for Inward Processing, including document code C601 and an authorisation number

Proof of CCG authorisation (including document code C505) or exemption (document status code CC)

Declarant

Declaration is validated and risked. The Special Procedures authorisation is validated against the

importer and is found to be invalid. The CCG authorisation is found to be valid.

CDS

Declaration is rejected due to invalid authorisation. CDSDeclarant is notified through the appropriate notifications. CDS

3.4.2 Invalid CCG (valid Special Procedures Authorisation)




Proof of CCG authorisation (including document code C505, without document status code CC)

Declarant

Declaration is validated and risked. The Special Procedures authorisation is validated against the

importer and is found to be valid. The CCG authorisation is found to be invalid as the declarant has

submitted a CCG authorisation that does not match the CCG authorisation number against their EORI in PDS, and has not declared document status code CC to indicate exemption.

CDS

Declaration is rejected due to invalid authorisation. CDSDeclarant is notified through the appropriate notifications. CDS


Customs Declaration Service (CDS)3.4.3 Invalid Customs Warehouse Authorisation

Step Who Declarant submits a declaration claiming Suspension of Duties under Customs Warehousing using

An appropriate procedure code/additional procedure code (example: 07 71 000 on a Type C declaration)

Proof of full authorisation for Customs Warehousing, including the appropriate document code for the warehouse type and an authorisation number (for warehouse types U, Y, Z) (example: document code C517 for Warehouse Type U)

Declarant

Declaration is validated and risked. The authorisation is validated against the importer (for Warehouse Type U) or the Declarant/Representative (for all other warehouse types) and is found to be invalid.

CDS

The declaration is rejected due to invalid authorisation. CDSDeclarant is notified through the appropriate notifications. CDS

3.4.4 Invalid EIDR Authorisation

Step Who Declarant submits a Type Z declaration with document code C514 and an authorisation number.

Declarant

Declaration is validated and risked. The authorisation number is validated against the declarant/importer/representative and is found to be invalid.

CDS


3.4.5 Invalid SDP Authorisation

Step Who Declarant submits a Type C/F/Y declaration with document code C512 and an authorisation number.

Declarant


CDS



Customs Declaration Service (CDS)3.4.6 Invalid AEO Authorisation

Step Who Declarant submits a declaration with AEO authorisation, including an appropriate document code and an authorisation number.

Declarant


CDS


4. Relief and Suspensions for Imports

The following Relief and Suspension regimes will be facilitated when used with an appropriate procedure code/additional procedure code that is in scope:

Relief of Duties

o Onward Supply Relief (OSR)

o Outward Processing (OP)

o Returned Goods Relief (RGR)

o Community Systems of Duty Relief (CSDR)

o Onward Dispatch (OSD)

o Other additional procedure codes resulting in Outright or Partial Reliefs

Suspension of Duties

o Inward Processing (IP)

o Excise Warehousing (EW)

o Customs Warehousing (CW)

o Temporary Admission (TA)

Functionality is also available to enable duties to be manually entered on the declaration in specific scenarios using the Additional Information code OVR01. For additional guidance on this functionality, please refer to the document CDS Tax Lines in the Google Drive folder CDS 11 Guidance Documents.

Authorisation by declaration and security payments are in scope for this phase of trade test.

Relief and Suspension are not available for the Type C or F scenarios in CDS trade test. During this phase of trade test, a tax notification will not be received for Type C declarations or for arrived inventory linked Type F declarations.



4.1.1 Inward Processing

Step Who Declarant submits a declaration claiming Suspension of Duties using all of the following:



Proof of CCG authorisation (including document code C505) or exemption

Declarant

Declaration is validated and risked. The Special Procedures authorisation is validated against the importer and is found to be valid. The CCG authorisation is validated against the importer, declarant, or representative and is either found to be valid, or the party is found to be exempt.

CDS


CDS


CDS

4.1.2 Excise Warehousing

Step Who Declarant submits a declaration claiming Suspension of Duties under Excise Warehousing using both


Proof of full authorisation for Customs Warehousing, including the appropriate document code for the warehouse type and an authorisation number (for warehouse types U, Y, Z). (example: document code C676 for Warehouse Type Y)

Declarant

Declaration is validated and risked. The authorisation is validated against the declarant and is found to be valid.

CDS


CDS


CDS


Customs Declaration Service (CDS)4.1.3 Onward Supply Relief

Step Who Declarant submits a declaration claiming Onward Supply Relief (OSR) using both


Proof of full authorisation for OSR (one valid UK VAT number with role code of FR1 or FR3)

A valid VAT number for an EU member state in Additional Fiscal Reference (D.E. 3/40) with a prefix of FR2 at item level

Declarant

Declaration is validated and risked. The document code submitted is found to be valid for the requested regime, but the VAT number is not validated against the declarant.

CDS

Duty is calculated with relief applied to the appropriate tax type(s) for the regime and procedure codes/additional procedure codes used.

CDS


CDS

4.1.4 Manual Override for Returned Goods Relief (RGR)

Step Who Declarant submits a declaration claiming Relief of Duties using a procedure code/additional procedure code combination which requires duty to be manually entered

Example for Returned Goods Relief: 61 23 F01 on a Type Y declaration)

Declarant

Declarant enters manual override code OVR01 in the Additional Information field (DE 2/2), and manually enters the amount of duty to be charged as tax lines in the declaration.

Declarant

Declaration is validated and risked. CDS

Duty is calculated with relief applied to the appropriate tax type(s) as per the tax lines entered.

CDS


CDS


Customs Declaration Service (CDS)4.1.5 End Use Relief (Relief by Commodity Code)

Step Who Declarant submits a declaration claiming Relief of Duties under End Use Relief using the following:

Commodity code with an end use measure Preference code 115 or 140 Proof of full authorisation for end use relief (document code

N990) An appropriate procedure code/APC for end use relief (excluding

the APC 2MO)

Declarant

Declaration is validated and risked. The authorisation is validated against the importer and is found to be valid.

CDS

Duties are calculated and relief of duty is applied to the appropriate tax types as per the end use measure against the commodity code.

CDS

Declarant is notified through the appropriate notifications, including a DMSTAX which reflects the appropriate amount of duties.

CDS

4.1.6 End Use Relief (Relief by APC)

Step Who Declarant submits a declaration claiming Relief of Duties under End Use Relief using the following:

A procedure code beginning with 44, and an APC which provides end use relief (example: 44 21 2MO)

Proof of full authorisation for end use relief (document code N990)

Declarant


CDS

Duties are calculated and relief of duty is applied to the appropriate tax types as per the procedure code and additional procedure code submitted.

CDS


CDS

4.1.7 Customs Warehousing

Step Who Declarant submits a declaration claiming Suspension of Duties under Customs Warehousing using both

An appropriate procedure code/additional procedure code (example: 71 00 000 on a Type A declaration)

Proof of full authorisation for Customs Warehousing, including the appropriate document code for the warehouse type and an

Declarant



Step Who authorisation number (for warehouse types U, Y, Z). (example: document code C676 for Warehouse Type Y)

Declaration is validated and risked. The authorisation is validated against the declarant and is found to be valid.

CDS


CDS


CDS

4.1.8 Temporary Admissions (TA)

Step Who Declarant submits a declaration claiming Suspension of Duties under Temporary Admissions using:

An appropriate procedure code/additional procedure code (example: 53 00 D02 on a Type A declaration)

Proof of full authorisation for Temporary Admissions, including document code C516 and an authorisation number


Declarant


CDS


CDS


CDS

4.1.9 Community System of Duty Relief (CSDR)

Step Who Declarant submits a declaration claiming Relief of Duties under CSDR using an appropriate procedure code/additional procedure code (example: 40 00 C30 on a Type A declaration).

Declarant

Declaration is validated and risked. CDS

Duty is calculated with relief of duties applied to the appropriate tax type(s) for the regime and procedure codes/additional procedure codes used.

CDS


CDS


Customs Declaration Service (CDS)4.1.10 Outward Processing (OP)

Step Who Declarant submits a declaration claiming Relief of Duties under Outward Processing using:


Proof of full authorisation for Outward Processing, including document code C019 and an authorisation number


Declarant


CDS


CDS


CDS

4.1.11 Onward Dispatch (OSD)

Step Who Declarant submits a declaration claiming Relief of Duties under Onward Dispatch using:


Declarant


CDS


CDS


CDS

4.1.12 Authorisation by Declaration with Security Deposit

Step Who Declarant submits a declaration claiming Relief or Suspension of Duties under a special procedure using:

An appropriate procedure code/additional procedure code (example: 44 00 000 for End Use on a Type A declaration)

Additional Information code 00100 in D.E. 2/2 Document Code N990 or C990 in D.E. 2/3 followed by “XW” as

the identifier.

Declarant



Step Who Declaration is validated and risked. CDS

Duty is calculated with relief of duties applied to the appropriate tax type(s) for the regime and procedure codes/additional procedure codes used. A security deposit is taken for the value of the relief.

CDS

Declarant is notified through the appropriate notifications, including a DMSTAX notification confirming the security taken.

CDS


4.2.1 Invalid Declaration Type

Step Who Declarant submits a Type Z declaration claiming Suspension of Duties using all of the below:

An appropriate procedure code and additional procedure code (example: 51 71 000 for Inward Processing)

Proof of authorisation for Special Procedures (including document code C601 for IP)

A declaration type that is not allowed for the procedure code specified (example: Type Y is not allowed for 51 71 000).

Declarant

Declaration is validated. CDS

The declaration is rejected as the declaration type is invalid for the procedure code and additional procedure code combination specified.

CDS


5. Imports Excise Duty

Functionality has been introduced to trade test to enable to submission of declarations with commodity codes which attract excise duty. Please refer to the table below for the national additional codes in scope.

National additional codesIn scope X412, X413, X415, X419, X421, X422, X423, X425, X429, X431, X433,

X435, X438, X441, X443, X446, X447, X451, X461, X462, X463, X473, X481, X485, X511, X520, X521, X522, X540, X541, X542, X551, X556, X561, X570, X571, X572, X589, X591, X592, X595, X611, X615, X619, X623 and X627. Tax Type 661 is also supported.

Out of scope Additional Codes X407, X440, X442, X444 and X445. Scenarios where the combination of 473 and 447 tax types are required (Beer Imported (Annual production more than 60,000hl)).



5.1.1 Excise Duty

Step Who Declarant submits a Type A declaration with a commodity code for goods with excise duty applicable, all additional codes required, and supplementary units and tax base values as required.

Declarant


Duty is calculated, including Excise Duty. CDS


Declarant is notified through the appropriate notifications, including a DMSTAX notification specifying the VAT, Duty, & Excise Duty payable.

CDS

5.1.2 Excise Duty and Suspension of Duties

Step Who Declarant submits a Type A declaration with:

a. Goods that have a commodity code with excise duty applicable, all additional codes required, and supplementary units and tax base values as required.

b. Procedure code and additional procedure code which provides suspension of excise duty in D.E. 1/10 and 1/11 (for example, 51 00 000 for inward processing)

Declarant


Duties are calculated and suspension of duty is applied to the relevant tax types, including excise duty.

CDS



CDS

5.1.3 Excise Duty and Relief of Duties


a. Goods that have a commodity code with excise duty applicable, all additional codes required, and supplementary units and tax base values as required.

b. Procedure code and additional procedure code which provides suspension of excise duty in D.E. 1/10 and 1/11 (for example, 42 00 000 for onward supply relief)

Declarant




Step Who Duties are calculated and relief of duty is applied to the relevant tax types, including excise duty.

CDS



CDS


5.2.1 Excise Duty without Required National Additional Code

Step Who Declarant submits a Type A declaration with goods that have excise duty applicable to them, and does not submit all national additional codes required.

Declarant

The declaration does not pass validation. CDS

Declaration is rejected. CDS

Declarant is notified through the appropriate notifications, including a DMSREJ notification.

CDS

6. Imports Inventory Linking

6.1 Summary

The inventory linking of frontier declarations (IM-A / IM-B / IM-C) or pre-lodged declaration (IM-D / IM-E / IM-F), as well as the arrival of inventory linked pre-lodged declarations, is in scope for CDS Trade Test.

For inventory-linked entries to the UK, CDS will send a message to the CSP inventory system so it can link the declaration to the consignment and update the inventory system with the declaration status and route of entry. For declarations that are not matched on input, CDS will look to re-validate the link.

The CSP inventory system will respond to CDS with an inventory return code (IRC) based on matching the inventory fields from the declaration with those defined for the consignment to which it is linked.

The CSP inventory system consignment is linked with CDS by inventory consignment references (ICRs), which will be cross-referenced against the declaration and used to identify the consignment and declaration in subsequent messages between CDS and the CSP inventory system.

The ICR is declared as the master unique consignment reference (MUCR).


Customs Declaration Service (CDS)CSP inventory systems will be updated with significant changes during declaration processing with the import clearance status (ICS) of the declaration as it progresses towards customs clearance or its final state.

For further detail regarding the CDS inventory linking (imports) functionality, CSPs should refer to the inventory linking imports service design document previously issued by HMRC.

6.2 Workarounds and Known Defects

Please refer to the latest version of the Trade Test Known Error Log for a full list of defects and workarounds that apply to this phase of trade test.


6.3.1 Submit Declaration with MUCR at Header Level

Step Who Declarant submits a frontier inventory linked declaration via a CSP. DeclarantCDS send a validate movement message (UKCIUM) to the CSP. CDSThe CSP validates that the UCR reference (DE 2/1) on the declaration exists in the inventory system, and that the number of packages on the declaration matches that in the inventory system. The match request is successful.

CSP

The CSP notifies CDS that the match request is successful (“000” response).

CSP

The declaration is accepted and the appropriate notifications are issued. CDS

6.3.2 Negative Inventory Match Response followed by Amendment and Clearance

Trade Test supports the submission of an amendment or null amendment following an initial negative inventory match to trigger re-processing without waiting for the 24 hour timer to elapse in CDS Trade Test. This 24 hour timer has been configured to facilitate testing in Trade Test only. In the Live CDS system, this timer will be 29 days.

Step Who Declarant submits a frontier inventory linked declaration via a CSP. DeclarantCDS send a validate movement message (UKCIUM) to the CSP. CDSThe CSP validates that the UCR reference (DE 2/1) on the declaration exists in the inventory system, and that the number of packages on the declaration matches that in the inventory system. The match request is unsuccessful as the consignment has not been registered on the system.

CSP

The CSP notifies CDS that the match request is unsuccessful in the ValidateMovementResponse message (“001” response).

CSP

CSP is notified of the mismatch (DMSRCV). CDS



Step Who An amendment message is sent within 24 hours to correct the MUCR on the declaration.

CSP

CDS send a validate movement message (UKCIUM) to the CSP without waiting for the 24 hour timer to elapse.

CDS

The CSP validates that the UCR reference (DE 2/1) on the declaration exists in the inventory system, and that the number of packages on the declaration matches that in the inventory system. The match request is successful (“000” response).

CSP

The declaration is accepted and the appropriate notifications are issued. CDS


6.4.1 Negative Inventory Match Response followed by DMSREJ (no amendment)

Please note that the CDS Trade Test system will dwell for 24 hour following an inventory mismatch in scenarios without an amendment. This 24 hour timer has been configured to facilitate testing in Trade Test only. In the Live CDS system, this timer will be 29 days.


CSP


CSP

CSP is notified of the mismatch (DMSRCV). CDSThe mismatch is not corrected within 24 hours. CSPCDS send a validate movement message (UKCIUM) to the CSP (after 24 hours).

CDS

The CSP validates that the UCR reference (DE 2/1) on the declaration exists in the inventory system, and that the number of packages on the declaration matches that in the inventory system. The match request is unsuccessful.

CSP


Inventory System

The declaration is rejected and the appropriate notifications are issued. CDS


Customs Declaration Service (CDS)6.4.2 Negative Inventory Match Response followed by DMSREJ with amendment

Trade Test supports the submission of an amendment or null amendment following an initial negative inventory match to trigger re-processing without waiting for the 24 hour timer to elapse in CDS Trade Test. This 24 hour timer has been configured to facilitate testing in Trade Test only. In the Live CDS system, this timer will be 29 days.


CSP


CSP

CSP is notified of the mismatch (DMSRCV). CDSA null amendment message is sent within 24 hours. CSPCDS send a validate movement message (UKCIUM) to the CSP without waiting for the 24 hour timer to elapse.

CDS

The CSP validates that the UCR reference (DE 2/1) on the declaration exists in the inventory system, and that the number of packages on the declaration matches that in the inventory system. The match request is unsuccessful.

CSP


Inventory System

The declaration is rejected and the appropriate notifications are issued. CDS

7. Imports Simulated Immediate Payment Service

7.1 Summary

CDS Trade Test supports the use an immediate method of payment for liabilities owed on a frontier declaration and the receipt of all associated notifications.

The immediate payments facility for CDS Trade Test will include the ability to:

Use an immediate payment MOP on the declaration Receive a notification of the liabilities owed including provision of a unique payment

reference Receive a notification that the payment has been fully received Receive a notification that payment is owed in the case of partial or no payment

However, the CDS Trade Test system will not support the initiation of an immediate payment (e.g. via UI) as the trade test system cannot process payments including cash, cheque, card, and bank transfer payments.


Customs Declaration Service (CDS)Instead, the solution requires that mock payments are automatically sent internally within the CDS Trade Test system when one of the immediate payments MOP codes is used on a declaration submission with responses pre-configured dependent on the simulated scenario (full, partial, over or no payment).

Pre-determined EORIs, in combination with the use of an appropriate immediate payments MOP, will drive 4 different Immediate Payments scenarios in this phase of trade test:

Payment equals subscription Payment is greater than subscription Payment is less than subscription No pay-up

An immediate method of payment can be used for declaration types A, B, D, E, J, and K.

The immediate methods of payment in scope for CDS Trade Test are:

MOP code A (Immediate payment in cash) MOP code B (Immediate payment by corporate credit card) MOP code C (Immediate payment by cheque)

MOP code E (Deferred payment – Deferment Account) MOP code H (Immediate payment by electronic credit transfer) MOP code M (Security Deposit – immediate payment (cash deposit))

For the purposes of Trade Test, any of the above MOP codes can be used to trigger these scenarios. The MOP code used will not be validated against the mock payment message triggered internally within CDS Trade Test.

Where a deferment account number has not been declared in DE 2/6, please note that a MOP must be indicated on the declaration in DE 4/8. If neither a deferment account number nor a MOP has been entered on the declaration, the declaration will be rejected and a DMSREJ will be received. This applies to all declaration categories, except H2 which does not mandate a MOP code.

7.2 EORIs for Immediate Payments Scenarios

The table below outlines the EORIs that should be used on declarations in CDS Trade Test intended to trigger particular Immediate Payment scenarios.Where one of the below EORIs is used in conjunction with an Immediate Payments MOP (A, B, C, H) a simulated payment of the value indicated – or no payment if using GB725115006 – will be sent internally within the CDS Trade Test system and trigger the associated notifications.

To trigger a positive payment scenario, ensure the liabilities owed (duty and VAT) for the declaration are less than or equal to the payment amount indicated for the EORI used.

To trigger a negative payment scenario, ensure the liabilities owed (duty and VAT) for the declaration are greater than the payment amount indicated for the EORI used.

EORI Payment AmountGB725115003 £988.00



EORI Payment AmountGB725115004 £1100.00GB725115005 £500.00GB725115006 No messageGB725115007 £100000.00


7.3.1 Payment equals subscription

Step Who Declarant Submits a type A, B, D, E, J or K declaration using the following:

• An immediate payment MOP code• A pre-assigned EORI, based on the amount of customs duty

expected to be owed for the declaration (see section 7.2)

Declarant

Declaration is validated and checked against an emulated immediate payments system. Declarant is notified through the appropriate notifications, including a DMSTAX notification, of the amount of duty owed.

CDS

Immediate Payment simulator sends internal mock payment amounting to the full amount of duty owed.

CDS

Declarant is notified through a DMSACC notification that the declaration is accepted once the mock payment has been made.

CDS

7.3.2 Payment is greater than subscription

Step Who Declarant Submits a frontier type declaration using the following:

An immediate payment MOP code A pre-assigned EORI (see section 7.2)

Declarant


CDS

Immediate Payment simulator sends an internal mock payment for an amount of duty greater than that which was demanded of the declarant.

CDS

Declarant is notified through a DMSACC notification that the declaration is accepted once the mock payment has been made.

CDS


For scenarios where no payment is received or the payment is less than the liabilities owed, the CDS system will send daily reminder notifications indicating that there is an outstanding


Customs Declaration Service (CDS)liability for the declaration. The first reminder notification will be received 24 hours after the initial payment notification (DMSTAX or DMSCPI), with subsequent notifications received every 24 hours from this point. Please refer to the Service Design Document and E2E Sequence Diagrams for further information.

For the purposes of CDS Trade Test, 2 reminder notifications will be sent after which time the declaration will cease to be processed. Once the reminder notifications have expired, the declaration may be cancelled by the end user as it will not be processed. In the Live CDS system, up to 31 reminder notifications will be received daily until either payment is received or the reminders expire.

7.4.1 Payment is less than subscription


An immediate payment MOP code A pre-assigned EORI, based on the amount of customs duty

expected to be owed for the declaration (see section 7.2)

Declarant


CDS

Immediate Payment simulator sends an internal mock payment for an amount of duty less than that which was demanded of the declarant.

CDS

Declarant is notified through reminder notifications that are sent daily that there has been an under payment until the reminders expire (after 2 reminders for the purposes of Trade Test only).

CDS

Declaration is cancelled through the submission of a cancellation request as no payment has been made.

Declarant


Customs Declaration Service (CDS)7.4.2 No pay-up


• An immediate payment MOP code• The pre-assigned EORI that will not trigger any payment:

GB725115006

Declarant


CDS

Immediate Payment simulator does not send any internal mock payment.

CDS

Declarant is notified through reminder notifications that are sent daily that there has been an under payment until the reminders expire (after 2 reminders for the purposes of Trade Test only).

CDS

Declaration is cancelled through the submission of a cancellation request as no payment has been made.

Declarant

7.4.3 No MOP entered in DE 4/8

Step Who Declarant Submits a frontier type declaration (declaration category H1, H3, H4) without a deferment account number in DE 2/6 and without a MOP in DE 4/8.

Declarant

Declaration is validated and risked. The MOP is validated against declaration category and DE 2/6. MOP is found to be missing.

CDS

The declaration is rejected due to missing MOP. CDSDeclarant is notified through the appropriate notifications. CDS

7.5 Out of Scope

This solution is limited to declaration submission and will not allow a trader or software developer to initiate an immediate payment via UI as CDS Trade Test cannot process cash, cheque, card, or bank transfer payments. Instead, the Trade Test solution will automatically send mock payments internally within the CDS Trade Test system when one of the immediate payments MOP codes is used on a declaration submission.

8. Trade Preference with Security

CDS trade test will calculate duties considering claims for preference based on commodity and country. All valid preference codes starting with 2, 3, or 4 are now in scope for Trade Test along with a preference code of 100, indicating no preference.


Customs Declaration Service (CDS)Trade test also provides functionality to test trade preference scenarios where a security deposit will be taken. A security deposit can be triggered by submitting certain document status codes against the document code for the proof of origin document.


8.1.1 Trade Preference with Security Deposit


a. A valid preference code starting with 2, 3, or 4 in D.E. 4/17 (excluding codes for quota).

b. An appropriate document code in D.E. 2/3.c. The applicable document reference code in D.E. 2/3.d. A document status code indicating that the required document

has not been submitted (e.g. JP)

Declarant


Duty is calculated at the preference rate and a security deposit is taken. CDS

The declaration is cleared. CDS


CDS


8.2.1 Trade Preference with Invalid Document Status Code


a. A valid preference code starting with 2, 3, or 4 in D.E. 4/17 (excluding codes for quota).

b. An appropriate preference document code in D.E. 2/3.c. The applicable document reference code in D.E. 2/3.d. An invalid document status code for the trade preference

document code submitted (e.g. XW)

Declarant



Declarant is notified through the appropriate notifications, including a DMSREJ.

CDS

8.2.2 Trade Preference where Document Code is not provided

Step Who Declarant submits a Type A declaration with: Declarant



Step Who a. A valid preference code starting with 2, 3, or 4 in D.E. 4/17

(excluding codes for quota).b. The applicable document reference code in D.E. 2/3.c. No preference document code or document status code in D.E.

2/3.



Declarant is notified through the appropriate notifications, including a DMSREJ. CDS

9. Additional Security Deposit Functionality

In addition to the existing security deposit scenarios available in Trade Test (see sections on Relief & Suspension and Trade Preference), additional scenarios which trigger security deposits are available in this phase of trade test.


9.1.1 CAP Safeguarding Charges

Step Who Declarant submits a Type D standard declaration (H1) with:

Procedure code: 4000 000 Commodity code: 0207129000 (Meat and edible meat offal) Country of Origin: Argentina Item price/value: €600 Net Mass: 1000kg

The customs value for duty entered is lower than the reference price at the time of declaration and the CAP Goods will require a licence.

Declarant

CDS calculates duty Third Country ad valorem duty at rate of: €32.50/100kg, and charges a security deposit.

CDS

The following Trader Notifications are generated and sent to the Trader: DMSACC DMSTAX DMSCLE

CDS

10. EU Country of Origin

Declarations where EU is declared as the Country of Origin can be submitted in this phase of trade test.



10.1.1 Declaration with EU Country of Origin with Dispatch Country US

Step Who A Type A standard declarations (H1) is submitted by an AEO authorized trader, with the following:

Document code (certificate) C644: Certificate of inspection for organic products

Procedure code 4000 000 Commodity Code 2204211110 Country of Origin is EU Country of Dispatch is US

Declarant

The Declaration is accepted and cleared CDS

The Duty is calculated successfully. CDS

The following Trader Notifications are generated and sent to the Trader:DMSACC, DMSTAX and DMSCLE

CDS

11. Simulated Quota Service

Quota functionality is now available in Trade Test. However, as the Trade Test environment does not support live quota data and is not integrated with the EU, a simulated quota service has been developed for Trade Test. In this simulated service, predefined quota order numbers must be included on the declaration to trigger the associated quota allocation scenario and security deposit, if applicable.

An 11-minute delay will be applied at the point of interaction between a declaration and the Simulated Quota Service. This is to ensure that a quota is not allocated before the 10-minute dwell timer, that is applied to all supplementary and frontier declarations, has elapsed. Please see section F.6. for more information on the Dwell Timer.

Please submit the following values on your declaration to test different quota allocations. To trigger a security deposit, quota order number 090041 should be declared.

Quota Order Number

Commodity code

Scenario Preference code

Country

090021 7202300000 Full Allocation

120 CH

090041 0802119000 Zero, Critical 120 CH



11.1.1 Quota allocation

Step Who A Type A Standard Declaration is received which includes the following:

Quota ID 090021 Preference code 120 Commodity Code 72023000 and TARIC code 00 Net mass of 6000kg Country of Origin is CH

Declarant

The quota request is fully allocated. CDS


The following Trader Notifications are generated and sent to the Trader:DMSACC, DMSTAX and DMSCLE.

CDS

12. Electronic Licences

Electronic licence capabilities are now available in Trade Test. A declaration with goods that have Prohibition & Restriction (P&R) measures against them can now be submitted on a declaration and CDS in Trade Test will request that the measure is satisfied with the applicable document code and a valid licence. CDS will then decrement the licence accordingly.


14.1.1 A valid licence is declared


a. Goods item that has a P&R measure against it.b. An appropriate document code in D.E. 2/3.c. A valid Licence ID against the document code used to satisfy the

P&R measure.d. A valid Document Status Code and Quantity.

Declarant


A reservation is made against the licence. CDS

Dwell time elapses and no outstanding controls remain. CDS

Reservation is finalised, remaining balance and licence status is updated.

CDS



14.2.1 An invalid licence is declared


a. Goods item that has a P&R measure against it.b. An appropriate document code in D.E. 2/3.c. An invalid Licence ID against the document code used to satisfy

the P&R measure.d. A valid Document Status Code and Quantity.

Declarant


A reservation is made against the licence. CDS

Dwell time elapses and no outstanding controls remain. CDS

Reservation is finalised, remaining balance and licence status is updated.

CDS



E. High-level Exports Scenarios in Trade TestTrade Test support both supplementary and frontier declaration submissions for Exports. Please refer to the latest version of the Exports Technical Completion Matrix and declaration completion guidance when submitting Exports declarations into CDS Trade Test.

1. Exports Supplementary Declarations with Authorisation Validation

This section outlines suggested happy and unhappy path Exports supplementary declaration scenarios involving the validation of the relationship between declaration type and authorisations.

The following notes are referenced throughout this section.

Note 1AEO statuses and their corresponding Document Code:

Authorisation Type Description Authorisation Type Code Document CodeCustoms Simplifications AEOC C501Safety & Security AEOS C502Full AEOF C503

Note 2Format of D.E. 2/3 is provided in the Paper Tariff. (Document Code (an4) | Document Identifier (an35) | Document Status Code (a2) | Reason (an35) | Issuing Authority (an70) | Date of validity (an8) | Measurement (an4) | Quantity (an16,6)).


1.1.1 Type Y Declaration with SDP Authorisation

This section outlines a high-level Type Y Exports submission scenario. Please refer to the XML samples (E30sc1.1) for lower-level sample declaration data.

Step Who Declarant submits a type Y declaration with the following:

A DUCR of any relating Type C simplified declaration(s) declared for the same goods at Header level; and

Optional MRN for the Type C in DE 2/1; and Authorisation for SDP:

o The declarant has supplied authorisation type SDP in 2/3 as part of Document code C512; and

o The authorisation is held by either the Exporter (DE 3/2), Declarant (DE 3/18) or Representative (DE 3/20)

Declarant

Declaration validation takes place on the data entered; additional CDS| Security Marking | Customs Declaration Service | 54


Step Who validation:

The reference ID and DUCR are found to be valid; and The maximum number of reference IDs which can be input is up to

99 at item level, and 9,999 at header levelValidation for authorisation takes place CDSWhere validation is successful, send a DMSACC to the trader with the MRN for the declaration

CDS

If the declaration is finalised, a clearance notification DMSCLE is sent to the declarant.

CDS

1.1.2 Type Y Declaration with AEO Authorisation



A reference ID (MRN and/or DUCR) of any relating Type C simplified declaration(s) declared for the same goods; and

A DUCR for the Type C in DE 2/1; and Authorisation for AEO:

o The appropriate document code (see note 1 for doc codes) as a prefix to the AEO authorisation number in D.E. 2/3 (see note 2 for D.E. 2/3 format)

o The authorisation number in D.E. 2/3 is validated against the Exporter (D.E. 3/2) or Declarant (D.E. 3/18) or Representative (D.E. 3/20) if they are acting as an indirect representative ("3" in D.E. 3/21 - Representative Status Code)

o Holder of the Authorisation (D.E. 3/39) must have the appropriate Authorisation Type Code (see note 2 for codes)

o a valid EORI number Authorisation for SDP:



Declarant

Declaration validation takes place on the data entered; additional validation:


99 at item level, and 9,999 at header level

CDS

Validation for authorisation takes place CDS



Step Who Where validation is successful, send a DMSACC to the trader with the MRN for the declaration

CDS


CDS

1.2.3 Type Z Declaration with EIDR Authorisation


Step Who Declarant submits a type Z declaration with the following:

A reference ID (MRN and/or DUCR) of any relating C-21 declared for the same goods; and

EIDR authorisation is indicated in DE 1/2:o The declarant has supplied authorisation type EIR in DE 2/3

as part of Document code C514; and/oro The requested procedure code (DE 1/10) is valid against the

declaration type; and/oro The EIDR authorisation is valid for an export declaration

against either the Exporter (DE 3/2), declarant (DE 3/18) or Representative (DE 3/20); and/or

o Holder of the Authorisation Identification Number (DE 3/39) does have the Authorisation Type Code "EIR"; and/or

o A valid EORI number is held in DE 3/39 (EIR/EORI)

Declarant




CDS

Validation for authorisation takes place CDS

Where validation is successful, send a DMSACC to the trader with the MRN for the declaration

CDS


1.2.1 Type Y Declaration without SDP Authorisation



Declarant



Step Who Optional MRN for the Type C in DE 2/1; and Authorisation for SDP NOT provided:

o The declarant has not supplied authorisation type SDP in 2/3 as part of Document code C512; and/or

o No authorisation is held by either the Exporter (DE 3/2), Declarant (DE 3/18) or Representative (DE 3/20)




CDS

Validation for authorisation takes place, and fails CDS

Where validation is unsuccessful, send a DMSREJ to the trader with the MRN for the declaration

CDS

1.2.2 Type Y Declaration without AEO Authorisation


A reference ID (MRN and/or DUCR) of any relating Type C simplified declaration(s) declared for the same goods; and

A DUCR for the Type C in DE 2/1; and Authorisation for AEO not entered or incorrectly entered:

o The appropriate document code (see note 1 for doc codes) as a prefix to the AEO authorisation number in D.E. 2/3 (see note 2 for D.E. 2/3 format)

o The authorisation number in D.E. 2/3 is validated against the Exporter (D.E. 3/2) or Declarant (D.E. 3/18) or Representative (D.E. 3/20) if they are acting as an indirect representative ("3" in D.E. 3/21 - Representative Status Code)

o Holder of the Authorisation (D.E. 3/39) must have the appropriate Authorisation Type Code (see note 2 for codes)

o a valid EORI number Authorisation for SDP not entered or incorrectly entered:



Declarant


The reference ID and DUCR are found to be valid; and

CDS



Step Who The maximum number of reference IDs which can be input is up to


Validation for authorisation takes place, and fails CDS

Where validation is unsuccessful, send a DMSREJ to the trader with the MRN for the declaration

CDS

1.2.3 Type Z Declaration without EIDR Authorisation

Step Who Declarant submits a type Z declaration with the following:

A reference ID (MRN and/or DUCR) of any relating C-21 declared for the same goods; and

EIDR authorisation is not indicated or incorrectly indicated in DE 1/2:o The declarant has not supplied authorisation type EIR in DE

2/3 as part of Document code C514; and/oro The requested procedure code (DE 1/10) is not valid against

the declaration type; and/oro The EIDR authorisation is not valid for an export declaration

against either the Exporter (DE 3/2), declarant (DE 3/18) or Representative (DE 3/20); and/or

o Holder of the Authorisation Identification Number (DE 3/39) does not have the Authorisation Type Code "EIR"; and/or

o A valid EORI number is not held in DE 3/39 (EIR/EORI)

Declarant




CDS

Validation for authorisation takes place and fails CDS

Where validation is not successful, send a DMSREJ to the trader with the MRN for the declaration

CDS

2. Exports Licensing

This phase of Trade Test also supports the declaration of DIT and RPA Exports licenses on a supplementary declaration. This section outlines high-level happy and unhappy path license scenarios and lower-level detail can be found in the XML samples.

Please note that, in CDS trade test, only specific licensing scenarios will be available for testing, based on the test data that has been loaded into the trade test system for validation.

Please refer to the latest version of the Test Data Library for further information.



2.1.1 Licensable commodity declared with appropriate DIT license






A commodity code (DE 6/14) that is subject to a DIT license and the appropriate license type and license number (DE 2/3) for the authorised party

Declarant

Declaration validation takes place on the data entered; the license is found to be valid for the commodity declared and authorised party

CDS

Where validation is successful, send a DMSACC to the trader with the MRN for the declaration

CDS


CDS


2.2.1 Licensable commodity declared without appropriate DIT license






A commodity code (DE 6/14) that is subject to a DIT license, but no license type or license number is declared (DE 2/3)

Declarant

Declaration validation takes place on the data entered and fails as a license is mandatory for the commodity code declared

CDS

Where validation is not successful, send a DMSREJ to the trader with the CDS



Step Who MRN for the declaration

3. Exports Inventory Linking

This phase of Trade Test supports a broader range of exports frontier movements. This includes the following capabilities:

Submission of Type A, B, C D, E, F J and K declarations.

Singular arrival and departure of a declaration.

Consolidations.

Multiple arrivals and departures of a declaration, including from multiple locations.

Movements and consolidations sent to CDS for MUCRs and DUCRs (declarations) present in CHIEF HMUT (CDS-CHIEF Inventory Linking Exports Dual Running)

Please note that, due to a technical constraint testing is confined to the use of a limited set of CDS location codes allocated to pre-defined EORIs. Please see the Test Data Library for further details.


3.1.1 CDS Type D Declaration with DUCR Arrived and Departed

Declaration: Type D declaration (B1 data set, 1040 or 2300), no control, DUCR only declared.

Movements/Consolidations: Arrived and departed.



Declarant



CDS

Loader submits an EAL message to CDS for the declared DUCR including: Goods Location of arrival Master Opt Value Transport Details

Loader

Sends technical acknowledgement to the loader on receipt of their EAL message

CDS


CDS



Step Who Where validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration. Declaration is then processed by CDS including risk assessment.

CDS

CDS sends to the loader an ERS message containing the status of the declaration (ROE/SOE)

CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSIf P2P given by ERS message then loader sends EDL message to CDS to notify departure of the consignment.

Loader


CDS


CDS

On finalisation of the declaration CDS sends DMSEOG message to the declarant

CDS

3.1.2 CDS Type D Declaration with DUCR and MUCR Consolidated on Submission, Arrived, Shut and Departed

Declaration: Type D declaration (B1 data set, 1040 or 2300), no control, DUCR and MUCR declared.

Movements/Consolidations: Consolidated on declaration submission, arrived, shut and departed at MUCR level.


A DUCR and MUCR created by the declarant and declared at header level in 2/1

Declarant

Declaration validation takes place on the data entered and consolidation created.

CDS


CDS

Loader submits an EAL message to CDS for the declared MUCR including: Goods Location of arrival Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of all declarations in consolidation (DUCR) including re-validation of the declarations.

CDS

Where validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration. Declaration is then processed by CDS

CDS



Step Who including risk assessment. CDS sends to the loader an EMR message containing the status of the consolidation (ROE/SOE)

CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSThe consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator

Sends technical acknowledgement to the consolidator on receipt of their CST message

CDS

CDS closes the MUCR and sends an EMR to the consolidator with the status of the MUCR (SOE/ROE)

CDS

If P2P given by EMR message then loader sends EDL message for MUCR to CDS to notify departure of the consolidation.

Loader


CDS

CDS processes EDL message and sends UKCTRL to the loader as acknowledgement

CDS

On finalisation of the declarations CDS sends DMSEOG message to the declarant for each DUCR in the consolidation.

CDS

3.1.3 CDS Type D Declaration with DUCR Consolidated on Submission, Arrived, Shut and Departed


Movements/Consolidations: Consolidated before arrival, arrived, shut and departed at MUCR level.



Declarant

Declaration validation takes place on the declaration submitted CDS


CDS

Consolidator submits an EAC message to CDS for the declared DUCR including a MUCR reference.

Consolidator

Sends technical acknowledgement to the consolidator on receipt of their EAC message

CDS

CDS processes the consolidation request (EAC) consolidating the declared DUCR into the given MUCR reference and sending a EMR for the MUCR

CDS



Step Who to the consolidator with the status of the consolidation (SOE/ROE)Loader submits an EAL message to CDS for the MUCR including:

Goods Location of arrival Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of all declarations in the MUCR including re-validation of the declarations.

CDS

Where validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration.

CDS

CDS sends to the loader an EMR message containing the status of the consolidation (ROE/SOE)

CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSThe consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator


CDS


CDS


Loader


CDS


CDS


CDS

3.1.4 CDS Type D Declaration with DUCR, EAA Submitted, Arrived and Departed


Movements/Consolidations: Anticipated arrival sent for DUCR, arrived and departed at DUCR level.



Declarant



Step Who Declaration validation takes place on the declaration submitted CDS


CDS

Loader submits an anticipated arrival (EAA) message to CDS for the MUCR including:


Loader

Sends technical acknowledgement to the loader on receipt of their EAA message

CDS

Sends an ERS to the loader with the status of the DUCR (provisional SOE/ROE)

CDS

Loader submits an EAL message to CDS for the MUCR including: Goods Location of arrival Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of all declarations in the DUCR including re-validation of the declaration

CDS


CDS


CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSIf P2P given by ERS message then loader sends EDL message for DUCR to CDS to notify departure of the declaration

Loader


CDS


CDS

On finalisation of the declarations CDS sends DMSEOG message to the declarant for the declaration.

CDS

3.1.5 CDS Type D Declaration with DUCR, Consolidated before arrival, EAA sent for MUCR, Arrived, Shut and Departed



Customs Declaration Service (CDS)Movements/Consolidations: Consolidated before arrival, anticipated arrival sent for MUCR, arrived, shut and departed at MUCR.



Declarant

Declaration validation takes place on the declaration submitted CDS


CDS


Consolidator

Sends technical acknowledgement to the consolidator on receipt of their EAC message

CDS

CDS processes the consolidation request (EAC) consolidating the declared DUCR into the given MUCR reference and sending a EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE)

CDS

Loader submits an anticipated arrival (EAA) message to CDS for the MUCR including:


Loader

Sends technical acknowledgement to the loader on receipt of their EAA message

CDS

Sends an EMR to the loader with the status of the MUCR (provisional SOE/ROE)

CDS

Loader submits an EAL message to CDS for the MUCR including: Goods Location of arrival Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of all declarations in the MUCR including re-validation of the declarations.

CDS


CDS

CDS sends to the loader an EMR message containing the status of the consolidation (ROE/SOE)

CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDS



Step Who When all DUCRs have been associated, the consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator


CDS


CDS


Loader


CDS


CDS


CDS

3.1.6 CDS Type D Declaration with DUCR, Arrival before declaration submitted, declaration submitted and DUCR departed


Movements/Consolidations: Arrival before declaration submitted, declaration submitted and DUCR departed.

Step Who Loader submits an EAL message to CDS for DUCR including:


Loader


CDS

CDS sends to the loader an EAL response message containing the CRC code “101” to indicate declaration unknown

CDS

Declarant submits a type D declaration with the following: A DUCR matching that on the EAL and declared at header level in

2/1

Declarant

Declaration validation takes place on the data entered. CDSWhere validation is successful, send a DMSRCV to the trader with the MRN for the pre-lodged declaration.

CDS

CDS links declaration to DUCR and processes arrival of declaration (DUCR) including re-validation of the declaration

CDS



Step Who Where validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration. Declaration is then processed by CDS including risk assessment.

CDS


CDS


Loader


CDS


CDS

On finalisation of the declaration CDS sends DMSEOG message to the declarant

CDS

3.1.7 CDS Type D declaration, no control, DUCR only declared. Declaration covers multiple shipping containers.

Declaration: Type D declaration (B1 data set, 1040 or 2300), no control, DUCR only declared. Declaration covers multiple shipping containers.

Movements/Consolidations: 5 sequential arrivals of the same DUCR at the same location (a). Departure at DUCR level from one goods location (a).



Declarant



CDS

Loader submits 5 EAL messages to CDS for the declared DUCR including: Goods Location of arrival (a) Master Opt Value Transport Details

Loader


CDS


CDS


CDS



Step Who including risk assessment. CDS sends to the loader an ERS message for each of the EALs containing the status of the declaration (ROE/SOE)

CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSIf P2P given by ERS message then loader sends an EDL message to CDS to notify departure of the multiple consignments.

Loader


CDS


CDS

3.1.8 CDS Type D declaration, no control, DUCR declared. Declaration covers 2 shipping containers.

Declaration: Type D declaration (B1 data set, 1040 or 2300), no control, DUCR declared. Declaration covers 2 shipping containers.

Movements/Consolidations: DUCR arrived, consolidated to a MUCR and MUCR shut. MUCR arrived at first location (a) and departed. MUCR arrived at second location (b) and departed.


DUCR created by the declarant and declared at header level in 2/1Declarant


CDS

Loader submits an EAL message to CDS for the declared DUCR including: Goods Location of arrival (a) Master Opt Value Transport Details

Loader


CDS

CDS processes the declaration (DUCR) including re-validation CDSWhere validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration.

CDS


CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSConsolidator submits an EAC message to CDS for the declared DUCR including a MUCR reference.

Consolidator



Step Who Sends technical acknowledgement to the consolidator on receipt of their EAC message.

CDS

CDS processes the consolidation request (EAC) consolidating the declared DUCR into the given MUCR reference and sending a EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE).

CDS

The consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator


CDS

Sends technical acknowledgement to the loader on receipt of their CST message

CDS


CDS

If P2P given by EMR message then loader sends EDL message for MUCR to CDS to notify departure of the consolidation from location a.

Loader


CDS


CDS


CDS

Loader submits a second EAL message to CDS for the declared MUCR including:

Goods Location of arrival (b) (based on the 8th, 9th and 10th characters)

Master Opt Value Transport Details

Loader


CDS

CDS processes re-arrival of all declarations in consolidation (DUCRs) CDSCDS sends a re-arrival confirmation (DMSRCV-like) to the declarant with the MRN for the arrived declaration.

CDS

CDS sends an EMR for the MUCR to the loader with the status of the consolidation (SOE/ROE).

CDS

If clearance (P2P) is given, send a DMSCLE-like notification to the originator of the declaration submission.

CDS

If P2P given by EMR message then loader sends EDL message for MUCR to CDS to notify departure of the consolidation from location b.

Loader


CDS


Customs Declaration Service (CDS)3.1.9 CDS Type D declaration (B1 data set, 1040 or 2300), no control, DUCR only declared


Movements/Consolidations: DUCR arrived at location (a) consolidated to a MUCR and MUCR closed, MUCR arrived at location (b). Departed from location (b).


DUCR created by the declarant and declared at header level in 2/1Declarant


CDS

Loader submits an EAL message to CDS for the DUCR including: Goods Location of arrival (a) Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of the declaration including validation. CDSWhere validation is successful, send a DMSACC to the declarant with the MRN for the arrived declaration. Declaration is then processed by CDS including risk assessment.

CDS

CDS sends to the loader an ERS message containing the status of the declaration (ROE/SOE).

CDS

If clearance (P2P) is given send a DMSCLE to the declarant. CDSConsolidator submits an EAC message to CDS for the declared DUCR including a MUCR reference.

Consolidator

Sends technical acknowledgement to the consolidator on receipt of their EAC message.

CDS

CDS processes the consolidation request (EAC) consolidating the declared DUCR into the given MUCR reference and sending an EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE).

CDS

When all DUCRs have been associated, the consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator


CDS

CDS closes the MUCR and sends an EMR to the consolidator with the status of the MUCR (SOE/ROE).

CDS

Loader submits a second EAL message to CDS for the MUCR including: Goods Location of arrival (b)

Loader



Step Who Master Opt Value Transport Details


CDS

CDS processes re-arrival of all declarations in consolidation (DUCR) CDSCDS sends a re-arrival confirmation (DMSRCV-like) notification to the declarant

CDS

CDS sends an EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE).

CDS

If clearance (P2P) is given, send a DMSCLE-like notification to the declarant

CDS

If P2P given by EMR message then loader sends another EDL message for MUCR to CDS to notify departure of the consolidation.

Loader


CDS


CDS


3.2.1 CDS Type D Declaration with DUCR Cancelled, Loader attempts to arrive DUCR


Movements/Consolidations: Pre-lodged declaration cancelled by declarant, loader attempts to arrive DUCR.



Declarant


CDS

Submits cancellation message for declaration. DeclarantProcesses cancellation and if successful send DMSINV to the declarant. CDSLoader submits an EAL message to CDS for the declared DUCR including:


Loader



Step Who Sends technical acknowledgement to the loader on receipt of their EAL message

CDS

CDS sends error message with code indicating arrival is for a previously cancelled declaration.

CDS

3.2.2 CDS Type D Declaration with DUCR Cancelled, Loader attempts to arrive DUCR

Declaration: 3 x Declarations -

2 x Type D declaration (B1 data set, 1040 or 2300), DUCR and MUCR declared

1 x Type D declaration (B1 data set, 1040 or 2300), DUCR and MUCR declared, controlled goods (goods description populated to trigger test dummy controls)

Movements/Consolidations: Consolidated on declaration submission, arrived, controlled, MUCR shut and departure attempted at MUCR level for the consolidation still under controls.

Step Who Declarant submits 3 type D declarations:

All declarations - a DUCR created by the declarant and declared at header level in 2/1 – unique DUCR on each declaration.

A common MUCR across all declarations. 1 x declaration with a goods location populated to trigger test

dummy controls

Declarant

Declaration validation takes place on all declarations and single consolidation created

CDS

Where validation is successful, send a DMSRCV to the trader with the MRN for each pre-lodged declaration.

CDS

Loader submits an EAL message to CDS for the declared MUCR including: Goods Location of arrival Master Opt Value Transport Details

Loader


CDS

CDS processes arrival of all underlying declarations (DUCRs) including re-validation of the declaration

CDS

Where validation is successful, send a DMSACC to the declarant with an MRN for each of the arrived declarations.

CDS

CDS sends to the loader an EMR message containing the status of the consolidation (ROE/SOE) – Consolidation is under controls documentary or physical due to one DUCR being controlled.

CDS

CDS sends a DMSCTL or DMSDOC to the declarant for the controlled DUCR.

CDS



Step Who CDS sends a DMSCLE to the declarants for the DUCRs with P2P CDSThe consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator


CDS

CDS closes the MUCR and sends an EMR to the consolidator with the status of the MUCR (SOE/ROE) – provisional control result.

CDS

Loader then sends EDL message to CDS to notify departure of the consignment (MUCR)

Loader


CDS

CDS sends an error message to the loader indicating that the EDL is for a MUCR without P2P

CDS

4. Additional Frontier Declaration Types for Exports

Please note that Trade Test now provides the functionality to submit both simplified declaration types C, F, B and E and customs clearance requests (Type J and K).

Trade Test also supports the ability to submit a declaration with an ARC number declared for excise duty suspended goods.

Please note that there will be no functionality in CDS Trade Test for the departure of an export declaration to trigger the closing of an entry in EMCS.

4.0.1 Indirect Exports

This release of CDS includes the introduction of Indirect Exports, however these will not be included in Trade Test. Whilst you can submit a declaration and send an EDL, however it is not currently possible to exit the goods via another member state for the purposes of Trade Test.


4.1.1 CDS Type F Declaration, no control, DUCR only declared

Declaration: Type F Declaration (C1 Data Set, 10-Series), no control, DUCR only declared

Movements/Consolidations: Goods Arrived and Departed.



1040 declared in 1/10

Declarant




CDS

Loader submits an EAL message to CDS for the declared DUCR including: Goods Location of arrival Master Opt Value

Transport Details

Loader


CDS


CDS


CDS


CDS


Loader


CDS


CDS




Step Who Declarant submits a type F declaration with the following:



Declarant


CDS


Transport Details

Loader



Step Who Sends technical acknowledgement to the loader on receipt of their EAL message

CDS


CDS


CDS


CDS


Loader


CDS


CDS







Declarant


CDS


Transport Details

Loader


CDS


CDS


CDS



Step Who including risk assessment. CDS sends to the loader an ERS message containing the status of the declaration (ROE/SOE)

CDS


Loader


CDS


CDS

4.1.4 CDS Type C Declaration, no control, DUCR only declared

Declaration: Type C Declaration (C1 Data Set, 31-Series), no control, DUCR only declared




3151 declared in 1/10 1CS declared in 1/11 and an authorisation for CSE declared.

Declarant


CDS


Transport Details

Loader


CDS


CDS


CDS


CDS

If clearance (P2P) is given send a DMSCLE to the declarant CDSIf P2P given by ERS message then loader sends EDL message to CDS to Loader



Step Who notify departure of the consignment.Sends technical acknowledgement to the loader on receipt of their EDL message

CDS


CDS

4.1.5 CDS Type E Declaration, no control, DUCR only declared

Declaration: Type E Declaration (C1 Data Set, 10-Series), no control, DUCR only declared





Declarant


CDS


Loader


CDS


CDS


CDS


CDS


Loader


CDS


CDS


Customs Declaration Service (CDS)4.1.6 CDS Type E Declaration, no control, DUCR only declared

Declaration: Type E Declaration (C1 Data Set, 10-Series), no control, DUCR only declared





Declarant


CDS


Loader


CDS


CDS


CDS


CDS


Loader


CDS


CDS

4.1.7 CDS Type A Declaration, no control, DUCR only declared

Declaration: Type A Declaration (B4 Data Set, 10-Series), no control, DUCR only declared


Step Who Declarant submits a type A declaration with the following:

A DUCR created by the declarant and declared at header level in Declarant



Step Who 2/1

1040 declared in 1/10 1CS and F75 declared in 1/11 and CSE authorisation declared.


CDS


Loader


CDS


CDS


CDS


CDS


Loader


CDS


CDS

4.1.8 CDS Type D Declaration for excise duty suspended goods, document control, DUCR only declared

Declaration: Pre-lodged declaration is submitted into CDS, (B1 Data Set) with ARC number declared. Control on goods exported under excise duty suspension (goods description populated to test dummy controls). DUCR declared.

Movements/Consolidations: Pre-lodged declaration into CDS, goods arrived at location (a), document control, departed.

Step Who Consignor declares goods in EMCS using an EAD ConsignorDeclarant submits a type D declaration into CDS with the following: Declarant



Step Who A DUCR created by the declarant and declared at header level in

2/1. ARC number generated from EMCS declared in 2/3

CDS validates ARC number to ensure its unique identity CDSWhere validation is successful and ARC number is validated unique, send a DMSRCV to the trader with the MRN for the pre-lodged declaration

CDS

Loader submits EAL message to CDS for the declared DUCR including: Goods Location of arrival (A) Master Opt Value Transport Details

Loader

CDS sends technical acknowledgment to the loader on receipt of their EAL message

CDS

CDS processes arrival of declaration (DUCR) including re-validation of the declaration CDS

CDS

Where validation is successful, CDS sends a DMSACC to the declarant with the MRN for the arrived declaration. Declaration is then processed by CDS including risk assessment.

CDS

CDS sends a DMSDOC to the declarant for the document controlled DUCR.

CDS


CDS

CDS concludes control and sends a DMSCLE to the declarant for the DUCR

CDS

With P2P loader then sends EDL message to CDS to notify departure of the consignment

Loader


CDS


CDS

4.1.9 CDS Type K (pre-lodged C21) declaration, no control, DUCR only declared

Declaration: Pre-lodged Declaration (C21E/ C21EIDR data set) no control, DUCR only declared

Movements/Consolidations: Pre-lodged declaration into CDS, goods arrived at location (a), no control, goods departed

Step Who Declarant submits a declaration with the following:

Additional declaration type ‘K’ indicated in 1/2Declarant



Step Who A DUCR created by the declarant and declared at header level in

2/1



CDS

Loader submits an EAL message to CDS for the declared DUCR including: Goods Location of arrival (A) Master Opt Value Transport Details

Loader


CDS


CDS


CDS


CDS

CDS sends a DMSCLE to the declarants for the DUCRs with P2P CDSWith P2P loader then sends EDL message to CDS to notify departure of the consignment

Loader


CDS


CDS

4.1.10 CDS Type K (pre-lodged C21) declaration, document control, DUCR only declared

Declaration: Pre-lodged Declaration (C21E/ C21EIDR data set), control, DUCR only declared

Movements/Consolidations: Pre-lodged declaration into CDS, goods arrived at location (a), document control, and departed

Step Who Declarant submits a declaration with the following:

Additional declaration type ‘K’ indicated in 1/2 A DUCR created by the declarant and declared at header level in

2/1

Declarant


Where validation is successful, send a DMSRCV to the trader with the CDS



Step Who MRN for the pre-lodged declaration.Loader submits an EAL message to CDS for the declared DUCR including:

Goods Location of arrival (A) Master Opt Value Transport Details

Loader


CDS


CDS


CDS

CDS sends a DMSDOC to the declarant for the document controlled DUCR.

CDS


CDS

CDS concludes control and sends a DMSCLE to the declarant for the DUCR

CDS

With P2P loader then sends EDL message to CDS to notify departure of the consignment

Loader


CDS


CDS

4.1.11 CDS Type K (pre-lodged C21) declaration, no control, DUCR and MUCR declared

Declaration: Pre-lodged Declaration (C21E/ C21EIDR data set), Direct representation, no control, DUCR and MUCR declared

Movements/Consolidations: Goods arrived, goods departed

No. Step Who

1

Direct Representative submits a type K customs clearance request with the following:

- A DUCR and MUCR created by the declarant and declared at header level in 2/1

- Direct Representative (indicated by ‘2’ in DE 3/21)

Representative

2 Customs clearance request validation takes place on the data entered.

CDS



No. Step Who

3Where validation is successful, send a DMSRCV to the trader with the MRN for the pre-lodged type K customs clearance request.

CDS

4

Loader submits EAL message to CDS for the declared DUCR including:

Goods Location of arrival (a) Master Opt Value Transport Details

Loader

5 Sends a technical acknowledgement to the loader on receipt of the EAL message

CDS

6 CDS processes arrival of the customs clearance request DUCR including re-validation of the customs clearance request

CDS

7

Where validation is successful, send a DMSACC to the declarant with the MRN for the arrived customs clearance request. Customs clearance request is then processed by CDS including risk assessment.

CDS

8 CDS sends to the loader an ERS message for the EAL containing the status of the declaration (ROE/SOE)

CDS

9 If clearance (P2P) is given send a DMSCLE to the declarant CDS

10 The Loader closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Loader

11 If P2P given by EMR message then loader sends an EDL message to CDS to notify departure of the consignment.

Loader

12 CDS processes EDL message and sends technical acknowledgement to the loader on receipt of their EDL message.

CDS

13On finalisation of the customs clearance request CDS sends DMSEOG message to the declarant for the DUCR in the consolidation.

CDS

4.1.12 CDS Type F declaration, no control, DUCR and MUCR declaredDeclaration: Type F declaration (C1, 10 series dataset), no control, DUCR and MUCR declared.

Movements/Consolidations: Pre-lodged declaration into CDS, goods arrived at location (a), goods departed

No. Step Who 1 Direct Representative submits a type F declaration with the

following: - A DUCR and MUCR created by the declarant and

Representative



No. Step Who declared at header level in 2/1

- Authorisation for SDE:o The declarant has supplied authorisation type

SDE in 2/3 as part of Document code C512; and

- The authorisation is held the Representative (DE 3/20)- Direct Representative (indicated by ‘2’ in DE 3/21)

2 Declaration validation takes place on the data entered. CDS

3 Where validation is successful, send a DMSRCV to the trader with the MRN for the pre-lodged declaration.

CDS

4

Loader submits an EAL message to CDS for the declared DUCR/MUCR including:


Loader

5 CDS sends technical acknowledgment to the loader on receipt of their EAL message

CDS

6 CDS processes arrival of declaration (DUCR/MUCR) including re-validation of the declaration

CDS

7


CDS

8 Declaration converts to a type C CDS

9 CDS sends to the loader an EMR message containing the status of the MUCR (ROE/SOE).

CDS

10 CDS sends a DMSCLE to the declarants for the DUCRs with P2P

CDS


Loader

11 With P2P loader then sends EDL message to CDS to notify departure of the consignment

Loader

12 Sends technical acknowledgement to the loader on receipt of their EDL message

CDS

13 Processes EDL message and sends UKCTRL to the loader as acknowledgement

CDS

14 On finalisation of the declaration CDS sends DMSEOG message to the declarant CDS


Customs Declaration Service (CDS)4.1.13 CDS Type A Declaration, no control, DUCR and MUCR declared

Declaration: Type A declaration (B1 dataset, 10 series), Direct Representation, no control

Movements/Consolidations: (Submitted an arrival inland), goods departed

No. Step Who

1

Direct Representative submits a type A declaration with the following:

- A DUCR and MUCR created by the declarant and declared at header level in 2/1

- Direct Representative (indicated by ‘2’ in DE 3/21)

Representative

2 Declaration validation takes place on the data entered. CDS

3 Where validation is successful, send a DMSACC to the trader with the MRN for the CSE-lodged declaration. CDS

4Goods re-arrived at port/airport, whereby the Loader sends an EAL.

Port: GBAUSOUSTNSOU – Southampton DocksLoader

5 Where validation is successful, send a DMSRCV to the trader with the MRN for the CSE-lodged declaration. CDS


Loader

7 CDS sends to the loader an EMR message for the EAL containing the status of the MUCR (ROE/SOE) CDS

8 Loader sends an EDL message for DUCR/MUCR to CDS to notify departure of the consignment Loader

9 Sends technical acknowledgement to the loader on receipt of their EDL message CDS

10 Processes EDL message and sends positive UKCTRL to the loader as acknowledgement CDS

11 On finalisation of the declaration CDS sends DMSEOG message to the declarant CDS

5. Exports Inventory Linking Dual Running

Please note that this trade test introduces the capability to arrive, depart and consolidate declarations submitted into CHIEF HMUT via submission of EAL, EAA, EDL, EAC and CST messages to CDS Trade Test.

This includes the full scope of the CDS inventory linking dual solution. Please refer to the Exports Inventory Linking Service Design Document and other documentation, found in the Google Drive folder CDS 01 Inventory Linking Exports.



5.1.1 CHIEF C21 with DUCR reference declared on CHIEF, arrived consolidated and departed via CDS

Declaration: CHIEF declaration with DUCR reference (C21 declaration) declared on CHIEF

Movements/Consolidations: 2 x DUCR arrived at location (a), consolidated on MUCR, no control, P2P given and departed.

Step Who Declarant submits a 2 x C21 declarations into CHIEF with the following:

DUCR created by the declarant and declared at header levelDeclarant

Declaration validation takes place in CHIEF on the declaration submitted. CHIEFWhere validation is successful, CHIEF sends a notification to the trader with the MRN for the pre-lodged declaration.

CHIEF

Loader submits EAL message to CDS for the declared DUCRs including: Goods Location of Arrival (A) Master Opt Value Transport Details

Loader

CDS sends a technical acknowledgement to the loader on receipt of each of their EAL messages at goods location (a)

CDS

CHIEF processes arrival of the declaration including validation and risk assessment

CHIEF


CDS

Steps repeated for each EAL for the DUCR to be submitted. This will be repeated 2 times, 10 minutes apart reflecting the 2 x DUCRs submitted.

Loader

When clearance (P2P) is given, CHIEF sends a CUSRES(X6) to the declarant with the MRN for the arrived declaration

CHIEF


Consolidator

CDS sends technical acknowledgement to the consolidator on receipt of their EAC message.

CDS

CHIEF processes the consolidation request (EAC) consolidating the declared DUCR into the given MUCR reference.

CHIEF

CDS sends an EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE)

CDS

Steps repeated by the consolidator to submit a subsequent EAC message to CDS for the second DUCR.

Consolidator

When the DUCRs have been associated, the consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator



Step Who CDS sends technical acknowledgement to the consolidator on receipt of their CST message

CDS

CHIEF closes the MUCR CHIEFCDS sends an EMR to the consolidator with the status of the MUCR (SOE/ROE).

CDS

Loader submits another EAL message to CDS for the MUCR including: Goods Location of arrival Master Opt Value Transport Details

Loader


CDS

CHIEF processes re-arrival of all declarations in consolidation (DUCRs) CHIEF

CHIEF sends a re-arrival confirmation CUSRES notification to the declarant

CHIEF

CDS sends an EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE).

CDS

If clearance (P2P) is given, send a CUSRES(X6) notification to each declarant for the DUCR.

CHIEF

If P2P given by EMR message then loader sends an EDL message for MUCR to CDS to notify departure of the consolidation.

Loader

CDS sends technical acknowledgement to the loader on receipt of their EDL message (Clearance response) UKCTRL

CDS

CHIEF processes EDL message and sends S8 report to the declarant as acknowledgement

CHIEF


5.2.1 - 2 x CHIEF declarations made with DUCR and MUCR declared. Consolidation processed via CDS and attempted departure of intermediate (child) MUCR.

Declaration: Pre-Lodged declaration submitted with DUCR and MUCR reference into CHIEF, Pre-lodged declaration submitted with DUCR and MUCR into CDS.

Movements/Consolidations: arrival for MUCR, no control, consolidation of MUCR into MUCR and departure attempted on intermediate MUCR

Step Who Declarant submits 2 x Pre-Lodged declarations each with the following:

Declaration into CHIEF with DUCR and MUCR created by the declarant and declared at header level

Declaration into CDS with DUCR and MUCR created by the

Declarant



Step Who declarant and declared at header level

Declaration validation takes place in CHIEF and CDS on the declarations submitted.

CHIEFCDS

Where validation is successful, CHIEF sends a notification to the trader with the MRN for the pre-lodged declaration.

CHIEF


CDS

Consolidator closes the MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator

CDS sends technical acknowledgement to the consolidator on receipt of their CST message

CDS

CHIEF and CDS closes the MUCR CHIEFCDS

CDS sends an EMR to the consolidator with the status of the MUCR (SOE/ROE).

CDS

Consolidator submits the EAC message to CDS for a MUCR declared on a declration to a new MUCR

Consolidator

CDS sends technical acknowledgement to the consolidator on receipt of their EAC message.

CDS

CHIEF and CDS processes the consolidation request (EAC) for a MUCR declared on a declration to a new MUCR

CHIEF CDS

CDS sends an EMR for the MUCR to the consolidator with the status of the consolidation (SOE/ROE)

CDS

Consolidator closes the top parent MUCR by sending a CST message to CDS containing the MUCR to be closed.

Consolidator

CDS sends technical acknowledgement to the consolidator on receipt of their CST message

CDS

CHIEF and CDS closes the top parent MUCR CHIEFCDS

CDS sends an EMR to the consolidator with the status of the top parent MUCR (SOE/ROE).

CDS

Loader submits an EAL message into CDS for the declared MUCR’s including:


Loader

CDS sends a technical acknowledgement to the loader on receipt of each of their EAL messages at goods location (a)

CDS

CHIEF and CDS processes arrival of the declarations (MUCR’s) including CHIEF



Step Who validation CDSDeclaration is then processed including risk assessment. Where validation is successful, CHIEF sends a CUSRES to the declarant with the MRN for the arrived declaration, CDS sends a DMSACC

CHIEF CDS

CDS sends to the loader an EMR message containing the status of the declaration (ROE/SOE)

CDS

When clearance (P2P) is given, CHIEF sends a CUSRES(X6) to the declarant

CHIEF

Loader sends EDL message to CDS to notify departure of the consignment at intermediate MUCR level

Loader

CDS sends technical acknowledgement to the loader on receipt of their EDL message

CDS

CDS sends an error message to the loader indicating that the EDL is for an intermediate MUCR

CDS



F. Summary of Existing Scope (TTM5.1 and earlier)

1. Accept and validate

Data fields on the declaration will be validated and, if appropriate, accepted by CDS. To submit the declaration, developers should use one of the EORI numbers provided for use in the trade test environment or one of the pre-authorised EORI numbers from the latest Test Data Library. These numbers are created specifically for trade test.

1.1 Notifications

The declarant will receive notifications throughout the lifecycle of the declaration. If a notification has not been received following the submission of a declaration, please raise an incident via the support model.

Following the submission and validation of a declaration, a notification to confirm acceptance or rejection of the declaration will be received. At the point of validation, the declarant will be given an MRN unique to their consignment, which is used as their HMRC reference for the consignment. Where a declaration is rejected, the DMSREJ notification will point to the specific validation errors that caused the rejection.

Between TTM4 and TTM6.0.0, the DMSTAX and DMSCLE notifications were consolidated. This consolidated notification detailed the duties liable on the goods and that the goods have been cleared for release. Beginning in TTM6.2.0, DMSTAX and DMSCLE will be received as separate notifications for all declaration types and payment methods. For declarations using duty deferment, these will be received in quick succession. This change is required to support CDS immediate payments, which is planned for a future Trade Test release

Developers should refer to the latest version of the CDS End to End Sequence Diagrams for further detail around the notifications received during each declaration journey.

If the declarant does not accurately complete the declaration – for example misses a mandatory field, completes a field in the wrong format, enters an invalid EORI number, country code, or commodity code – or attempts to submit a different declaration type, they will receive an error message.

Validation rules are being iteratively deployed into the trade test environment, in accordance with the UK Trade Tariff: volume 3. Where validation rules have not yet been configured, declarations may not fail validation and could be accepted by CDS. In this case, declarants will receive an acceptance notification where a rejection notification was anticipated.

1.2 Rejection of duplicate submissions

To avoid multiple processing of a declaration, CDS trade test will reject duplicate declaration submissions based on the local reference number (LRN) and Submitter.

The LRN for every declaration that has passed validation will be stored for 2 calendar days. When a declaration is submitted, the LRN field of the submitted declaration will be checked


Customs Declaration Service (CDS)against the LRN from every successful submission of a declaration from the same Submitter within the last 2 calendar days (Submitter is Agent EORI, if available, or Declarant EORI, if Agent EORI is not available). If the LRN matches an LRN from the same Submitter within the last 2 calendar days, the declaration will be rejected and a rejection notification will be received.

If a declaration is rejected because it has failed a validation check, but this is not due to a duplicate LRN, a subsequent declaration with the same LRN can be submitted and will be processed by CDS.

There is no mandatory format for the LRN field (DE 2/5).

2. Duty calculation

CDS trade test will produce a calculation of the duties owed, calculating against the quantity of the commodity that is declared and taking into account any adjustments.

For the Type C scenarios currently available in trade test, duty is not expected to be owed. A tax notification will not be received for these scenarios.

Declarations may be submitted using any commodity code that does not require functionality that is not yet available in CDS trade test – such as paper licensing, securities, or quota – and that is applicable under the procedures in scope. This includes commodity codes for some textile goods, such as 6109100010, 6212109000, 640299980, and 6110209900. This also includes the 3,784 commodity codes ranging from 0103100000 – 0804500090 where 0% VAT is applied using the additional code VATZ in data element 6/17.

Where a commodity requires a certificate(s), these must be declared. For example, 6110209900 (women’s / girls jumpers) requires validation of certificates C679 and Y922. If the appropriate certificate(s) are not declared for a particular commodity, an error message will be received.

The rest of this section highlights some of the specific complex calculations possible in this phase of CDS trade test.

2.1 Anti-dumping duty (ADD) (imports only)

The submission of a supplementary declaration for goods that attract definitive ADD is in scope for CDS trade test. ADD is chargeable in addition to, and independent of, any other duty to which the goods are liable.

CDS trade test will calculate the definitive ADD liable considering the commodity code and country code. An ADD calculation will only be triggered in CDS if the appropriate measure unit type, country of origin, additional codes, and certificates are included on the declaration.

Commodity code Description Measure

unit typeCountry of origin

Additional codes Certificates

1516209821 Biodiesel TNE#1 TR 4115, 4999C514, N935, 2001903010 Sweetcorn DTN#E TH A890, VATZ



Commodity code Description Measure

unit typeCountry of origin

Additional codes Certificates

C506, C517,C064, 9120, C672

2820100010 Manganese DTN#E ZA A828

4421999910 Wooden ironing board DTN#E CN A999

6907210000 Ceramic tiles DTN#E CN B158

7019120039 Fiberglass rovings DTN#E CN A999

7312106591 Standard wire / ropes / cables DTN#E CN A999

7323930010 Steel ironing board DTN#E CN A999

8305100011 Fitting for loose leaf binders DTN#E CN 8900

8712003010 Bicycles with ballbearings DTN#E LK B772

2.2 Common Agricultural Policy (CAP) goods (imports only)

CDS trade test will calculate the duty liable considering the variable charge based on the commodity code. A list of commodity codes that are CAP goods which do not attract a security deposit are included below. It should be noted that CAP scenarios that would trigger a security deposit remain out of scope for this phase of trade test.

Commodity Code Description07031011 00 Onions

07042000 00 Brussel Sprouts

22030001 00 Beer

22042189 10 Port

24022090 00 Cigarettes

27101211 00 Petroleum Oils

3. Value build up

Full value build up functionality is available in CDS trade test. This ensures the correct handling of the statistical and customs values calculated by CDS, as well as their application in the calculation of the revenue due.

All codes for DE 4/9 additions and deductions, as articulated in Appendix 10 of the UK Trade Tariff: volume 3, are in scope. This includes the ability to apply additions or reductions where only applicable to either VAT or customs duty.

Though the guidance in the UK Trade Tariff indicates that the codes for D.E. 4/9 Additions and Deductions can be declared up to 99 times at both the header and the item level, during TTM5 the following guidance should be followed:


Customs Declaration Service (CDS) Item Level: only one instance of each code will be allowed

Header Level: only one instance of each code will be allowed

Where two instances of a code could be applied, it is requested that the submitter aggregates the value additions or deductions. For example if there is a royalty fee needed across two different agreements of £500 and £600, rather than declaring two instances of code AI, £1100 would be declared against one instance of code AI.

This applies to all codes found in Appendix 10 of the UK Trade Tariff for CDS: volume 3.

4. Country codes

CDS trade test will support declarations made against all country codes with the exception of continental shelf codes (ZB, ZD, ZE, ZF, ZG, ZH, ZN, ZU) and special fiscal territories.

Please note that the XML path for DE 5/15 (Country of Origin) and DE 5/16 (Country of Preferential Origin) is the same. To distinguish between these two data elements, code 1 (Country of Origin) or 2 (Country of Preferential Origin) must be declared in Declaration/GoodsShipment/GovernmentAgencyGoodsItem/Origin/TypeCode.

Please refer to the latest version of the Technical Completion Matrix for further detail.

5. Currency conversion

The declarant will be able to submit declarations in multiple currencies, including GBP, EUR, HKD, JPY, and USD. Exchange rates in CDS trade test are based on a static rate and updated monthly with the values published by HMRC.

6. Dwell time

The 10 minute ‘dwell’ time has been activated for supplementary and frontier declaration types. The dwell time does not apply to pre-lodged declarations.

This 10 minute dwell period will begin after validation of the declaration (DMSACC notification) and prior to duty calculation (if applicable) and clearance.

During the 10 minute dwell time, the submitter may cancel the declaration. This will include the possibility of cancelling the declaration after a non-blocking front end credibility (FEC) challenge.

CDS trade test will assume confirmation after 10 minutes of no response – including where a FEC challenge message is triggered – and, after this time, the declaration will continue to process as normal.

Please be advised the CDS programme is aware that the 10 minute dwell time as configured does not align with the expectations of some external users of CDS. The programme is considering how this may be adapted for a future release.



7. Cancellations

The submitter will be able to send a cancellation request (pre-clearance) in this phase of trade test. For the purposes of CDS trade test only, the declaration will be automatically invalidated. The submitter will receive notice that the declaration has been cancelled following a successful cancellation request.

Where the request to invalidate a declaration is not initiated by HMRC, an indicator will be sent in the notification indicating the invalidation was not triggered by HMRC. This indicator will be different if the invalidation is triggered by HMRC. The indicator can then be used to determine whether the inventory booking reference for that specific consignment should or should not be cancelled.

8. Front end credibility (FEC) checks

FEC challenges help to increase the validity and credibility of declared date for fiscal and statistical purposes, and filter against obvious input errors.

There are 6 specific checks which in scope for this phase of CDS trade test:

1. Exclude certain set(s) of values from being used against declarations for a specific trader for a specific FEC check.

2. Value does not appear credible for commodity weight.

3. Supplementary unit does not appear credible for commodity value.

4. Supplementary unit does not appear credible for commodity weight.

5. Bulking item hides true value.

6. Suspect checks (directed at individual fields or an inter-field relationship that does not involve just quantity and value).

Should the declaration trigger an FEC rule, the DMSACC notification will include a non-blocking challenge message indicating the FEC rules that have been triggered. This will appear as a ‘Smart Error Message’ and include a textual description of the FEC challenge that has been triggered.

The ability to amend the declaration following the receipt of a FEC challenge is not available in this phase of trade test. However, the 10 minute dwell time – during which the declaration may be cancelled – is in scope.

If the declaration has not been cancelled within the 10 minute dwell period, CDS will continue to process the declaration without acknowledgement of the FEC challenge.

9. Binding tariff information (BTI) reference number

The ability to enter a BTI reference number on the declaration is in scope. The BTI is a written classification decision, given on request, which is legally binding on all customs administrations within the European Community and on the BTI holder for 3 years.


Customs Declaration Service (CDS)An error message should be returned if the BTI is entered in the incorrect format.

10. Locally held licenses

The validation of locally held licenses from the Department of International Trade (DIT) and Rural Payments Agency (RPA) that do not require any controls to be performed is in scope for CDS trade test. This includes the ability to declare a license with a document status that indicates that the license has been waived (e.g. XW).

In CDS trade test, only specific licensing scenarios will be available for testing, based on the test data that has been loaded into the trade test system for validation.

Please refer to the latest version of the Test Data Library for further information.

No documents will be uploaded by the declarant for validation by HMRC in trade test. However, electronic license details will be validated against the declaration.

Validation of paper licenses is not in scope for this phase of CDS trade test.

11. DAN Validation

The validation of the deferment account number (DAN) against the EORI is also in scope for CDS trade test. Declarations will fail validation where a DAN is not entered in DE 2/6 in scenarios where it is mandatory, in according with the UK Trade Tariff: volume 3. Additionally, where a DAN is entered and does not meet the format requirements of 7 numeric characters, the declaration will fail validation and be rejected.

The DAN will also be validated against the EORI to confirm that the EORI stated on the declaration has the authority to use the declared deferment account.

CDS will cater for Specific Authority for Duty Deferment Transactions. CDS will allow for an Importer’s DAN to be used where the Importer is not self-representing.

CDS trade test will also validate whether the DAN entered on the declaration is suspended or revoked at the point of declaration validation. If the DAN is suspended or revoked, the declaration will be rejected.

Finally, CDS trade test will also validate whether the deferment account declared has sufficient available balance to undertake the transaction at the point of tax calculation. Where a deferment account does not have sufficient available balance for a Type Y or Type Z supplementary declaration, the declaration will be cleared.

Please refer to the latest version of the Test Data Library for a list of DANs and EORIs to be used in the trade test environment.



G.Functionality Out of Scope for Trade TestThis section provides examples of additional scenarios that utilise functionality that is out of scope for this trade test. Please do not submit declarations using the functionality in this section, as they will not be processed correctly.

1. Post-Clearance Cancellations

Post-clearance cancellations are currently out of scope for this trade test. This means that declarations can only be cancelled during the dwell time before the declaration is cleared.

2. Country codes: continental shelf, prohibited, special fiscal territories

The declarant will be able to declare against all country codes, with the exception of continental shelf codes (ZB, ZD, ZE, ZF, ZG, ZH, ZN, ZU), prohibited countries, and special fiscal territories.

It should be noted that, to better align with the scope of the current CDS Release, imports from special fiscal territories has been removed from the scope of CDS trade test.

3. Paper licenses

Only the electronic locally held licenses DIT and RPA will be validated in trade test.

Scenarios requiring the validation of a paper license, which would require a manual document check, are currently out of scope for CDS trade test.

It should be noted that only a specific range of licensing scenarios will be available for testing in this phase of CDS trade test. These will align with the EORIs provided. Please refer to the latest version of the Test Data Library for further information.

4. CAP scenarios for exports

CAP scenarios for exports remain out of scope for CDS trade test.

5. Registration and subscription

Registration and subscription is out of scope for this phase of trade test. Users will be provided with pre-authorised EORI numbers specifically for the trade test environment through a shared EORI ‘library.’

6. Special procedures

The declaration category data sets for Free Circulation (H1, B1), Customs Warehousing (H2), Temporary Admission (H3), Inward Processing (H4), and Import Simplified Declaration (I1) are available for this phase of CDS trade test.

The imports declaration category data set for Special Fiscal Territories (H5) is out of scope for this phase of trade test.



7. Payment processing

Payments will not be taken in trade test. The following methods of payment are in scope for inclusion on the declaration in this phase of trade test:

MOP code A (Immediate payment in cash) MOP code B (Immediate payment by corporate credit card) MOP code C (Immediate payment by cheque)

MOP code E (Deferred payment – Deferment Account) MOP code H (Immediate payment by electronic credit transfer) MOP code M (Security Deposit – immediate payment (cash deposit))

All other payment types remain out of scope.



H.Glossary of termsADD Anti-dumping Duty

AEO Authorised Economic Operator

APC Additional Procedure Codes

API Application Programme Interface

BTI Binding Tariff Information

CAP Common Agricultural Policy

CCG Comprehensive Customs Guarantee

CDS Customs Declaration Service

CECAS Customs and Excise Core Accounting System

CHIEF Customs Handling of Import and Export Freight

CIF Cost Insurance and Freight

CPC Customs Procedure Code

CSDR Community Systems of Duty Relief

CSP Community System Provider

CUS Customer

CW Customs Warehouse

DAN Deferment Account Number

DE Data Element

DIT Department for International Trade

DMS Declaration Management Service

EIDR Entry in Declarant’s Record

ENS Entry Summary Declaration

EORI Economic Operator Registration and Identification

ETMP Enterprise Tax Management Platform

EU European Union

EUR Euro

EW Excise Warehousing

FAQ Frequently Asked Questions

FEC Front End Credibility



GBP Great British Pound (£)

HKD Honk Kong Dollar

HMRC Her Majesty’s Revenue & Customs

ICR Inventory Consignment References

ID Identification

IP Inward Processing

IVL Inventory Linking

JPY Japanese Yen

KEL Known Error Log

KG Kilograms

LRN Local Reference Number

MiTS Movements in Temporary Storage

MOP Method of Payment

MRN Movement Reference Number

MUCR Master Unique Consignment Reference

OP Outward Processing

OSD Onward Supply Dispatch

OSR Onward Supply Relief

PC Procedure Code

PoUS Proof of Union Status

RGR Returned Goods Relief

RPA Rural Payments Agency

SDP Simplified Procedures

SDST Software Development Support Team

SSL Secure Sockets Layer

TA Temporary Admission

TARIC Integrated Tariff of the European Community (TARif Intégré Communautaire)

TTM Trade Test Milestone

TRM Technical Readiness Meeting

UCC Union Customs Code

UCR Unique Consignment Reference



UK United Kingdom

UN United Nations

URL Uniform Resource Locator

USA United States of America

USD United States Dollar

VAT Value-added Tax

WCO World Customs Organisation

XML eXtensible Mark-up Language
