From 4e455505d42270cc1ebfaded82ca2b1d348e3fcc Mon Sep 17 00:00:00 2001 From: wol22 Date: Tue, 7 Jan 2025 16:02:19 +0000 Subject: [PATCH] Amend commit with updated content Signed-off-by: wol22 --- .../trade_and_customs/attribution.txt | 2 +- .../miscellaneous_unknown/trade_and_customs/qna.yaml | 10 +++++++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/knowledge/miscellaneous_unknown/trade_and_customs/attribution.txt b/knowledge/miscellaneous_unknown/trade_and_customs/attribution.txt index b7fdfb192..ada455d2c 100644 --- a/knowledge/miscellaneous_unknown/trade_and_customs/attribution.txt +++ b/knowledge/miscellaneous_unknown/trade_and_customs/attribution.txt @@ -1,5 +1,5 @@ Title of work: Customs Declarations end-to-end service guide Link to work: https://developer.service.hmrc.gov.uk/guides/customs-declarations-end-to-end-service-guide Revision: Revised 17/12/2024 -License of the work: Public +License of the work: Open Government License v3.0 Creator names: HMRC diff --git a/knowledge/miscellaneous_unknown/trade_and_customs/qna.yaml b/knowledge/miscellaneous_unknown/trade_and_customs/qna.yaml index 6e33011e4..9a347e69b 100644 --- a/knowledge/miscellaneous_unknown/trade_and_customs/qna.yaml +++ b/knowledge/miscellaneous_unknown/trade_and_customs/qna.yaml @@ -1,7 +1,15 @@ created_by: wol22 version: 3 domain: Tax and customs -document_outline: "For imports and exports, the submitter of the declaration interacts with CDS to manage events such as:\n•\tthe declaration submission. CDS expects to receive declaration data within the WCO format, defined by the schema and the HMRC Customs Tariff. The schema keeps most elements as optional to allow for capturing a complete declaration, or just partial (e.g. to support simplified import declarations).\n•\tthe request for amendment message is based on the definition of the declaration. The main difference is the change to the functional code of the message. The message structure also uses pointers so CDS can understand which data element needs to be altered within the declaration. For example, a change to the gross mass would require a pointer to the relevant element (one for each ‘layer’ of the message), but the message must also contain the new value. The pointers are defined by the WCO data element tags (found in [4, 5]). Some amendments will require approval by customs.\n•\tthe request for invalidation. Submitted to allow for a trader-initiated cancellation. Some invalidations will require approval by customs.\n•\treceiving the trader notifications. As the declaration goes through its lifecycle, certain notifications may be triggered back to the trader. At a bare minimum, a notification of acceptance and clearance can be expected, though others may be sent due to control, liabilities due, etc. A full table is listed below in section Types and Definitions.\n•\tthe goods arrival message is submitted to instruct CDS that goods are available for inspection following the submission of a pre-lodged declaration.\n" +document_outline: >- + For imports and exports, the submitter of the declaration interacts with CDS + to manage events such as the declaration submission. CDS expects to receive + declaration data within the WCO format, defined by the schema and the HMRC + Customs Tariff. The schema keeps most elements as optional to allow for + capturing a complete declaration, or just partial (e.g. to support simplified + import declarations). The goods arrival message is submitted to instruct CDS + that goods are available for inspection following the submission of a + pre-lodged declaration. seed_examples: - context: >- # Technical Validation Carried out on all Declarations