1 / 32

Customs Decl aration Service (CDS)

This event will discuss the technical changes, access security, receiving reports, CDS tariff publication, declaration categories, UCC changes, FEC checks, and exports changes introduced by Customs Declaration Service (CDS). It will also introduce the role of International Trade Development Liaison Officers (ITDLOs) and provide an overview of the phased delivery and migration of CDS functionality.

sheae
Download Presentation

Customs Decl aration Service (CDS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. | Official | Customs Declaration Service / Version 1.0 Customs Declaration Service (CDS) ACITA Southern Region Event 26th July 2018

  2. What changes with CDS?

  3. What changes with CDS? • Technical - From EDIFACT to XML

  4. What changes with CDS? - Technical • No E-mail option • Communication via internet APIs –sending a message directly to an IP address • Responses can be pushed or pulled • Access via CSP doesn’t change • No HCI • Some CSPs will present a screen (built on API) • Some will tell you to use an HMRC Digital service (like NES) Access Security • via OAuth2 tokens (see later) • CSP can still use the Badge

  5. What changes with CDS? - Technical Receiving reports – Digital Dashboard • MSS, Duty Deferment Statements, VAT Certs Receiving reports – E2s etc • No paper • No “reports”, only “notification messages” • Any “reports” will be created by your software, as needed No HCI • Some CSPs will present a screen (built on HMRC APIs) • Some CSPs will tell you to use an HMRC Digital service (like NES)

  6. CDS Tariff publication • Declaration completion guidelines and rules published in the Tariff • Import Tariff – March 18. Contains all Imports CPC codes except those for inventory linking. • Printed version August. Searchable PDF version available now. • Exports Tariff and Inventory Linking – limited draft since early July 18. Remaining CPCs. • Tariff includes CHIEF/CDS code mappings.

  7. Changes introduced by CDS Tariff

  8. Changes introduced by CDS Tariff

  9. Reading the CDS Tariff - Import Declaration Completion Guide

  10. Declaration Categories

  11. What changes with CDS? - Business • “Data Elements” not “SAD Box numbers” • The data elements are in 8 groups;

  12. What changes with CDS? • Customs Procedure Codes now in two parts • D/E 1/10 - 4 digit Procedure Code, plus • D/E 1/11 - (multiple) 3 character Additional Codes

  13. What changes with CDS? • Customs Procedure Codes now in two parts • D/E 1/10 - 4 digit Procedure Code, plus • D/E 1/11 - (multiple) 3 character Additional Codes

  14. What changes with CDS? • More UCC changes • Methods of Payment code harmonisation • Validation of authorisations, guarantees, BTIs etc • More “Parties” (buyer, seller etc) • Incoterms, Nature of Transaction codes, Valuation codes • EIDR is simpler – can move goods under warehouse CPC – so SFDs needed less often

  15. What changes with CDS? • FEC checks • Can now do TARIC checks (Q1/Q2 ratio, check Quantity matches Comm code restrictions) • Other FEC checks are now “non blocking” • Declaration clears after a 10-minute “dwell time” • Change in approach to post-clearance compliance • Can do more in future – eg behavioural analysis

  16. Exports changes for CDS • Some key functional areas of CDS exports will differ from today • Frustrated exports • Arrival post departure and multiple departures • Amendments and Cancellation • ROE code mapping • Topic Types and Customs Position Reason Types (SOE/ICS codes) • DUCR part numbers • Assumed departure

  17. International Trade Development Liaison Officer - ITDLOs • National ITDLO Manager – East Croydon • Currently Three ITDLOs – Bristol, Glasgow and Leeds Agreement to increase from three to thirteen in the next three years. One in each Regional Centre Location. • Main role: • To promote new developments within customs and international trade to businesses and colleagues • “New developments” include changes to existing customs law such as the UCC and trade preparation for CDS and EU Exit • The ITDLO’s • Are currently working on a Special Procedures presentation - available soon • Heavily involved with CDS delivery including writing and delivering  presentations • We have been promoting and explaining about AEO since it started in 2008 .   • And of course once the UK has an agreement (or not) with the EU, the ITDLOs will be explaining this  to Importers and Exporters .

  18. CDS - Migration

  19. Customs Declaration Service | CDS Phased Delivery & Migration Overview • Commencing in August 2018 there will be a phased migration of traders from CHIEF to CDS, aligned to the planned delivery of CDS functionality.Migration tranches • Customers will be migrated in ‘tranches’ which will be aligned to functional releases. Tranches are groups of traders. • Functional releases • Release 1 – 12th August 18 • Scope: Supplementary declaration functionality (Out of Customs Warehouse / Into Free Circulation - Type Z and Y). • Specific criteria applies eg deferred payment only, on single DAN; only UK warehouses; no quotas, suspensions or reliefs.

  20. “ Customs Declaration Service | CDS Phased Delivery & Migration Overview • Functional releases • Release 2 – November 18 • Scope: Remaining import functionality including support for Quota and multiple deferment accounts on a declaration. • No immediate payments or securities; limited Digital services • Release 3 – TBC • Scope: All exports, all other methods of payment, Digital self-service. • Ability to send Exports Inventory Linking requests to CDS will be in place before the first CDS exports declarations.

  21. “ Customs Declaration Service | CDS Phased Delivery & Migration Overview • Phase 2 functionality • Once core functionality is available in CDS and all customers have migrated, further releases in 2019 will offer service improvements • This will include additional Digital services and APIs, better control of Authorisations (e.g. who can claim IPR on your behalf) post-clearance automation

  22. Customs Declaration Service | CDS Release 1 & 2 Data Migration • Release 1 • For 12 August we will migrate data from CHIEF to CDS for those traders we expect to go live in Release 1. • EORI data, authorisations, deferment accounts & OGD licences. • The same data will be on both CHIEF and CDS throughout Release 1 and we will synchronise across the two systems. • We are not migrating any customs declaration data to CDS – there is no need as declarations can be completed on CHIEF. • Release 2 • Migrate data to CDS for every CHIEF trader and synchronise automatically during dual running.

  23. CDS - Digital Registration Process

  24. Customs Declaration Service | Digital registration to use CDS • Before you can use CDS live service you will need to register for CDS. • If you use a Freight Forwarder to submit your CDS declarations then it is only the Freight Forwarder who needs to go through the software authorisation process. • This authorisation process consists of a number of steps on Government Gateway. • Additional screens will be required if applying for EORI and CDS registration at the same time.

  25. Customs Declaration Service | Software Authorisation Steps • Access to CDS APIs requires specific authorisation from the end-user (i.e. the declarant’s organisation) • We use the open standard OAuth 2.0 as a technical solution to let you grant authority to a software application to interact with HMRC on your behalf • Your organisation authenticates with us using your Government Gateway account, and grants authority for the desired CDS functionality • Your software supplier will send you a link to GOV.UK to start the authorisation process, and a unique “client-ID” to identify your software • We issue you with your own OAuth access token (this is a message, not a physical token) • The access token is stored in your software application, and is automatically passed to us as part of subsequent API requests, e.g. to submit a declaration to CDS • This access token only gives access to your own data

  26. Customs Declaration Service | Software Authorisation Steps – Points to Note • You must have an EORI and a Government Gateway account before you can “sign up” for CDS access. • You may need to locate the person in your organisation who manages your existing Government Gateway account • They will need to “sign in” to Government Gateway and verify their identity before they can grant authority to access CDS • As part of this process they must choose a “client secret” for CDS. • They will also have the opportunity to confirm organisation details and link your EORI to your other HMRC accounts, e.g. through a UTR • Your CDS access token expires after 18 months, and you must grant access again (repeat the Government Gateway process) or you will lose access to CDS

  27. CDS Contingency

  28. CDS Contingency • HMRC has created a contingency programme under which additional resilience will be built into the delivery of, and the transition to, CDS. • The contingency programme is responsible for ensuring the existing CHIEF and other legacy declaration systems are scaled so that they are capable of managing the volume of declarations expected after the UK leaves the EU, to ensure that they remain a viable contingency solution beyond March 2019 if required. • .

  29. CDS Contingency • The major elements of our contingency plans are: • A carefully managed transition process between August 2018 and January 2019, where HMRC can flex the pace of transition to reflect service performance. • Dual running of CHIEF with CDS for some months, to ensure that HMRC can slow migration from CHIEF if CDS does not perform as expected. • We have developed a performance testing service, and are using it to identify to what capacity the CHIEF service can be scaled, with a target of 255m declarations. • .

  30. Border Systems Programme • Border Systems Programme (BSP) will contribute towards the UK government’s overarching strategic objectives to: • keep legitimate international trade flowing through the UK border • ensure UK-EU trade post Brexit is as seamless as possible • maintain effective border security to protect society from the threats of terrorism, organised crime and other harms through more effectively targeted border controls • collect revenues due on goods at the right time • Border Systems Programme is the HMRC delivery Programme to ensure readiness for leaving the EU on Day 1. • There are a number of projects within the programme including Ro-Ro, UK Safety and Security, Excise, Transit, Passengers, Parcels, Trade Stats, Northern Ireland and Binding tariff. The landscapes on the projects are flexible to support IT programmes (CDS) and EU Council decisions. • BSP project teams and other Government Departments have visited some maritime and RORO ports with Border Delivery Group over the last few months and held an external stakeholder event on 12 July in London.

  31. Questions ?

More Related