USM305: Export Entry Trade User Guide - gov.uk · USM305: Export Entry Trade User Guide _____ _____...
108
USM305: Export Entry Trade User Guide _______________________________________________________________________________________ _______________________________________________________________________________________ Filename: USM305 Page 1 of 108 Version: 4.0 USM305: Export Entry Trade User Guide Abstract This document provides a guide to the operation of the CHIEF Export declaration transactions available to the Trade. Origin/Author: John Walker Approved By: Glen Robe Date Approved: 11/01/2016 Status: Approved Prepared by: HMRC (CDIO (C&IT) – CHIEF) Dukes Court Duke Street Woking GU21 5XR 03000 577107
Transcript of USM305: Export Entry Trade User Guide - gov.uk · USM305: Export Entry Trade User Guide _____ _____...
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 1 of 108
Version: 4.0
USM305: Export Entry Trade User Guide
Abstract
This document provides a guide to the operation of the CHIEF Export declaration transactions available to the Trade.
Origin/Author: John Walker
Approved By: Glen Robe
Date Approved: 11/01/2016
Status: Approved
Prepared by: HMRC (CDIO (C&IT) – CHIEF) Dukes Court Duke Street Woking GU21 5XR 03000 577107
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 2 of 108
Version: 4.0
Contents
1. Introduction .............................................................................................................................................. 8
1.1 Purpose and Scope .......................................................................................................................... 8
1.2 Contents ........................................................................................................................................... 8
1.3 Scope of Exports Facilities ................................................................................................................ 8
2. Business Overview................................................................................................................................... 9
2.1 Purpose ............................................................................................................................................ 9
2.1.1 Access to Entries and Movements ............................................................................................. 9
2.2 Export Declarations ......................................................................................................................... 10
3. Data Field Details ................................................................................................................................... 11
3.1 Field Details .................................................................................................................................... 11
3.1.1 Header Data ............................................................................................................................ 11
3.1.2 Item Data ................................................................................................................................. 17
3.1.3 Tax Line Data .......................................................................................................................... 20
3.2 Cross-Field Validation Checks ........................................................................................................ 20
4. IEFD – Insert Export Full Declaration ..................................................................................................... 23
4.1 Business Description ...................................................................................................................... 23
4.2 Starting the Transaction .................................................................................................................. 23
4.3 Document Data ............................................................................................................................... 23
4.4 Document Structure ........................................................................................................................ 27
4.5 Field Completion Rules ................................................................................................................... 27
4.5.1 Header Data ............................................................................................................................ 27
4.5.2 Item Data ................................................................................................................................. 28
4.5.3 Tax Line Data (47) ................................................................................................................... 29
4.6 Field Details .................................................................................................................................... 29
4.7 Cross-Field Validation Checks ........................................................................................................ 29
5. IELP – Insert Export LCP Pre-Shipment Advice ..................................................................................... 30
5.1 Business Description ...................................................................................................................... 30
5.2 Starting the Transaction .................................................................................................................. 30
5.3 Document Data ............................................................................................................................... 30
5.4 Document Structure ........................................................................................................................ 34
5.5 Field Completion Rules ................................................................................................................... 34
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 3 of 108
Version: 4.0
5.5.1 Header Data ............................................................................................................................ 34
5.5.2 Item Data ................................................................................................................................. 35
5.6 Field Details .................................................................................................................................... 36
5.7 Cross-Field Validation Checks ........................................................................................................ 36
6. IESP – Insert Export SDP Pre-Shipment Advice .................................................................................... 37
6.1 Business Description ...................................................................................................................... 37
6.2 Starting the Transaction .................................................................................................................. 37
6.3 Document Data ............................................................................................................................... 37
6.4 Document Structure ........................................................................................................................ 41
6.5 Field Completion Rules ................................................................................................................... 41
6.5.1 Header Data ............................................................................................................................ 41
6.5.2 Item Data ................................................................................................................................. 42
6.6 Field Details .................................................................................................................................... 43
6.7 Cross-Field Validation Checks ........................................................................................................ 43
7. IECR – Insert Export Clearance Request (C21) ..................................................................................... 44
7.1 Business Description ...................................................................................................................... 44
7.2 Starting the Transaction .................................................................................................................. 44
7.3 Document Data ............................................................................................................................... 44
7.4 Document Structure ........................................................................................................................ 47
7.5 Field Completion Rules ................................................................................................................... 47
7.5.1 Header Data ............................................................................................................................ 47
7.5.2 Item Data ................................................................................................................................. 48
7.5.3 Tax Line Data (47) ................................................................................................................... 48
7.6 Field Details .................................................................................................................................... 49
7.7 Cross-Field Validation Checks ........................................................................................................ 49
8. IESD – Insert Export Supplementary Declaration ................................................................................... 50
8.1 Business Description ...................................................................................................................... 50
8.2 Starting the Transaction .................................................................................................................. 50
8.3 Document Data ............................................................................................................................... 50
8.4 Document Structure ........................................................................................................................ 53
8.5 Field Completion Rules ................................................................................................................... 53
8.5.1 Header Data ............................................................................................................................ 53
8.5.2 Item Data ................................................................................................................................. 54
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 4 of 108
Version: 4.0
8.5.3 Tax Line Data (47) ................................................................................................................... 55
8.6 Field Details .................................................................................................................................... 55
8.7 Cross-Field Validation Checks ........................................................................................................ 55
9. IEXS – Insert Exit Summary Declaration ................................................................................................ 56
9.1 Business Description ...................................................................................................................... 56
9.2 Starting the Transaction .................................................................................................................. 56
9.3 Document Data ............................................................................................................................... 56
9.4 Document Structure ........................................................................................................................ 59
9.5 Field Completion Rules ................................................................................................................... 59
9.5.1 Header Data ............................................................................................................................ 59
9.5.2 Item Data ................................................................................................................................. 60
9.6 Field Details .................................................................................................................................... 60
9.6.1 Header Data ............................................................................................................................ 60
9.6.2 Item Data ................................................................................................................................. 61
9.7 Cross-Field Validation Checks ........................................................................................................ 62
10. AEXD – Amend Export Entry .............................................................................................................. 63
10.1 Business Description ...................................................................................................................... 63
10.1.1 Detailed Considerations ........................................................................................................... 64
10.2 Starting the Transaction .................................................................................................................. 64
10.3 Document Data ............................................................................................................................... 64
10.4 Document Structure ........................................................................................................................ 65
10.5 Field Completion Rules ................................................................................................................... 65
10.6 Field Details .................................................................................................................................... 66
10.7 Cross-Field Validation Checks ........................................................................................................ 66
11. AEAL – Notify Export Arrival ............................................................................................................... 67
11.1 Business Description ...................................................................................................................... 67
11.1.1 Arrival of an Individual Declaration (Declaration UCR) ............................................................. 67
11.1.2 Arrival of a Consolidation (Master UCR) .................................................................................. 68
11.2 Starting the Transaction .................................................................................................................. 68
11.3 Document Data ............................................................................................................................... 68
11.3.1 Initial Parameter Screen ........................................................................................................... 69
11.3.2 Input and Acceptance Screens for Arrival of a Single Declaration ............................................ 69
11.3.3 Input and Acceptance Screens for Arrival of a Consolidation ................................................... 71
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 5 of 108
Version: 4.0
11.4 Document Structure ........................................................................................................................ 71
11.5 Field Completion Rules ................................................................................................................... 72
11.6 Field Details .................................................................................................................................... 72
11.7 Cross-Field Validation Checks ........................................................................................................ 74
12. ACST – Change Consolidation Status ................................................................................................ 75
12.1 Business Description ...................................................................................................................... 75
12.2 Starting the Transaction .................................................................................................................. 75
12.3 Document Data ............................................................................................................................... 75
12.4 Document Structure ........................................................................................................................ 76
12.5 Field Completion Rules ................................................................................................................... 76
12.6 Field Details .................................................................................................................................... 76
12.7 Cross-Field Validation Checks ........................................................................................................ 76
13. AEAC – Maintain Export Consolidation ............................................................................................... 77
13.1 Business Description ...................................................................................................................... 77
13.1.1 Shutting a Consolidation .......................................................................................................... 77
13.1.2 Associating Consignments with a Consolidation ...................................................................... 77
13.1.3 Disassociation of a Consignment from its Owning Consolidation ............................................. 78
13.2 Starting the Transaction .................................................................................................................. 78
13.3 Document Data ............................................................................................................................... 78
13.4 Document Structure ........................................................................................................................ 80
13.5 Field Completion Rules ................................................................................................................... 80
13.6 Field Details .................................................................................................................................... 81
13.7 Cross-Field Validation Checks ........................................................................................................ 81
14. AEDL – Notify Export Departure ......................................................................................................... 82
14.1 Business Description ...................................................................................................................... 82
14.2 Starting the Transaction .................................................................................................................. 83
14.3 Document Data ............................................................................................................................... 83
14.3.1 Initial Parameter Screen ........................................................................................................... 83
14.3.2 Input and Acceptance Screens for Departure of a Single Declaration ...................................... 84
14.3.3 Input and Acceptance Screens for Departure of a Consolidation ............................................. 85
14.4 Document Data ............................................................................................................................... 85
14.5 Field Completion Rules ................................................................................................................... 86
14.6 Field Details .................................................................................................................................... 86
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 6 of 108
Version: 4.0
14.7 Cross-Field Validation Checks ........................................................................................................ 87
15. DEVD – Display Entry Version Details ................................................................................................ 89
15.1 Business Description ...................................................................................................................... 89
15.2 Starting the Transaction .................................................................................................................. 90
15.3 Document Data ............................................................................................................................... 90
15.3.1 Initial Parameter Screen – All Entries ....................................................................................... 91
15.3.2 Summary Screens ................................................................................................................... 91
15.3.3 Generated Data Screens ......................................................................................................... 92
15.3.4 Account Details Screens – (Exporters/Submitting Traders only) .............................................. 93
15.3.5 Data As Input Screens ............................................................................................................. 94
15.3.6 Reason for Action Screens – (Exporters/Submitting Traders only) ........................................... 95
15.4 Document Structure ........................................................................................................................ 95
15.5 Field Completion Rules ................................................................................................................... 95
15.6 Field Details .................................................................................................................................... 95
15.6.1 Parameter Fields...................................................................................................................... 96
15.6.2 Displayed Data Fields .............................................................................................................. 97
15.7 Cross-Field Validation Checks ........................................................................................................ 98
16. RACD – Request Accompanying Document ....................................................................................... 99
16.1 Business Description ...................................................................................................................... 99
16.2 Starting the Transaction .................................................................................................................. 99
16.3 Document Data ............................................................................................................................... 99
16.4 Document Structure ...................................................................................................................... 100
16.5 Field Completion Rules ................................................................................................................. 100
16.6 Field Details .................................................................................................................................. 101
16.7 Cross-Field Validation Checks ...................................................................................................... 101
17. RCP3 – Request SAD COPY 3 ........................................................................................................ 102
17.1 Business Description .................................................................................................................... 102
17.2 Starting the Transaction ................................................................................................................ 102
17.3 Document Data ............................................................................................................................. 102
17.4 Document Structure ...................................................................................................................... 103
17.5 Field Completion Rules ................................................................................................................. 104
17.6 Field Details .................................................................................................................................. 104
17.7 Cross-Field Validation Checks ...................................................................................................... 104
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 7 of 108
Version: 4.0
18. Glossary and References ................................................................................................................. 105
18.1 Glossary ....................................................................................................................................... 105
18.2 References ................................................................................................................................... 105
Document Control ....................................................................................................................................... 107
Statement of Confidentiality ........................................................................................................................ 108
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 8 of 108
Version: 4.0
1. Introduction
1.1 Purpose and Scope
This document is one of the Trade Entry User Guides. It provides a guide to the operation of the Export Entry declaration transactions – insert, amend and display. These transactions establish or maintain a DTI Export Entry or provide facilities for the notification of movements (e.g., arrivals, departures). The entry handling transactions that are common with Imports are described in the Common Entry Trade User Guide, Reference [4]. The Common User Facilities User Guide, Reference [5] provides a description of the common transactions (e.g. retrieval from store) supporting these transactions. Reference [4] defines the reports that are triggered by these transactions.
This and other guides should be read in conjunction with References [1], [2] and [3] that together give a general explanation of CHIEF terms and concepts. Together, the guides form a source of reference for the CHIEF system.
This guide describes the data validation which takes place on the input you provide but you will also need to refer to the Tariff (see Reference [9]) published by HM Customs and Excise for the correct codes to be used for the completion of declaration documents.
Other tasks that you may also need to perform, such as the retrieval of Reference Data, are covered in other User Guides. You can find an index to these in Reference [1]. You should note that this Guide covers only the transactions that are available via the CHIEF HCI. Where a transaction is available in EDI, this fact will be indicated in its Business Description., with full details being found in Reference [6].
1.2 Contents
Two main subject areas are described in this user guide. The first gives a brief business overview of Customs Export Entry requirements and the various methods of declaration. This is followed by a detailed description of each Export Entry declaration transaction (Section 4 onwards), explaining its function, how it should be used, and the information that you will need to provide to the system. The declared data is detailed in Section 3 rather than being replicated for each input transaction.
N.B. Screen layouts shown in this document (in common with screen layouts shown in other User Guides) are indicative only as page breaks may vary to accommodate display content.
1.3 Scope of Exports Facilities
The Entry User Guides describe a number of standard CHIEF features or facilities that are not currently fully supported by Exports. For example, it is not anticipated that a levy on Exports will be imposed in the near future but the declarations include all Methods of Payment and a Deferment Approval Number (DAN) for deferred payment. There is also an Entry Accounting Advice (X9) for Exports (see Reference [4]). The tax line is used for CAP refund claims but the other features are included to provide a degree of future proofing and to align with Imports.
END OF SECTION 1
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 9 of 108
Version: 4.0
2. Business Overview
2.1 Purpose
The Export Entry transactions of CHIEF support the declaration of Export entries under a number of schemes, for example, Full SAD, Simplified Local Clearance Procedure (LCP). All declarations are based upon the Single Administrative Document (SAD) supplemented if required by data from the C88 (CAP) for CAP goods. The transactions described here also support the progress of an Export entry from declaration through to departure from the UK.
With the introduction of the ECS Release, the current (‘fiscal’) export declarations become ‘Combined Declarations’, because they include both the existing fiscal data and new Safety and Security data. Exit Summary Declarations are introduced which contain only Safety and Security data. There is no requirement to support ‘fiscal only’ declarations.
Entries can also be listed and cancelled, though accepted Entries for goods which are on hand may only be cancelled by Customs. (The term ‘accepted’ covers an Entry which has been input to the system without errors either as a Pre-lodged Entry if the goods are not on hand, or as a Legally Accepted Entry if the goods are on hand.) The Export Entry transactions incorporate:
validation with the option to ‘store’ invalid data for later correction and submission;
interrogation of Entries and their movements;
advice of goods arrival. This is either an arrival when a declaration was previously recorded on CHIEF as provisionally accepted (pre-lodged) thereby establishing a legally accepted entry or an arrival at a subsequent location (an interim location or the Office from which the goods depart from the UK). CHIEF distinguishes between the initial arrival which establishes the Office of Export, further arrivals at the Office of Export (Related or Additional arrivals) and arrivals elsewhere at the Office of Exit (see Reference [4] Section 3.4);
advice of goods departure;
for Customs only, the opportunity to release the goods for Export by granting permission to progress or to set query or detention status etc., to amend the route and to simulate the interaction with another system when that system is not available.
This user guide specifically addresses the transactions that the Trade may use in order to create, amend or cancel Entries (or request to cancel if the entry is legally accepted and the goods are on-hand). There are some further transactions which can affect the status of an Entry which are not triggered directly by a user (e.g. processes which run in the background and perhaps overnight). These transactions are not described here.
All Export Entry data collected is transferred daily to related systems from which, for example, the monthly UK Trade Statistics are derived.
2.1.1 Access to Entries and Movements
Submitting Traders may only amend Entries that are ‘owned’ by them, in accordance with the access security data privacy features of the system, and may only view the declaration details of their own DTI Entries. Handling Agents, normally via a CSP, may notify anticipated or actual arrival or departure and perform consolidations on Export declarations but may not make changes to declaration details. Such actions result in the creation of movements reflecting the anticipated or actual existence of goods at the nominated location.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 10 of 108
Version: 4.0
2.2 Export Declarations
Exports supports two main procedures - Full and Simplified.
The Full procedures are single declarations based upon either the Single Administrative Document (SAD) or Customs Clearance Request (CCR or C21). The procedures supported include:
Full pre-entry of standard consignments (i.e. neither Low Value (LV) nor non-Statistical (NS));
Full pre-entry of LV consignments;
Full pre-entry of NS consignments;
Customs Clearance Request (C21).
The Simplified procedures are two part declarations comprising a Pre-shipment advice (PSA) followed at a later stage by a Supplementary Declaration (SD) containing full details of the declaration with accompanying tax details where applicable. Such declarations are available to the Submitting Trader via electronic means only. Customs do not accept Simplified procedure declarations on paper for Customs keying.
The SD discharges the financial liabilities of all PSAs which it addresses. The Simplified Procedures supported by New Exports are:
Simplified Declaration Procedure (SDP) of standard consignments;
Simplified Local Clearance Procedure (LCP) of standard consignments.
SDP operates at the UK frontier, Inland Clearance Depots (ICD) and Designated Export Places (DEP), whilst LCP operates inland at the trader’s premises and Customs approved warehouses. A Trader must be authorised to operate the SDP or LCP simplified procedures. A Trader may also use normal procedures either at the UK frontier or inland (e.g. at the Trader’s premises).
There is also a special use of the Supplementary Declaration to declare CAP Export Simplified Victualling and which is not associated with Simplified Procedures. In this case, a single Supplementary Declaration is declared containing all goods exported in a calendar month. The tax point on such declarations carries the date of the last day in the month.
For shipments that have no fiscal aspect, the Exit Summary declaration can be used to lodge safety and security related information.
Declaration transactions are available to both Customs and the Trade. Traders are provided with facilities to input declarations:
via a Customs and/or Government gateway (using EDI via e-mail, Web Forms etc.);
via a CSP at the HCI;
via a CSP by EDI.
END OF SECTION 2
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 11 of 108
Version: 4.0
3. Data Field Details
CHIEF supports five export related Entry types based on the SAD with corresponding insert transactions (IEFD, IELP, IESP, IESD, IEXS). Since they are all based on the SAD they share common field definitions and cross-field validation rules. To avoid replication within this guide and to highlight the differences, the definitions are given in this section rather than being repeated in the sections for the respective transactions.
The C21 also uses the same data and box numbers as the SAD so the field definitions and cross-field validation rules also apply to the C21 insert transaction (IECR).
3.1 Field Details
The following sub-sections give details of the data content and business use for the input fields used by IEFD, IELP, IESP, IESD, IECR and IEXS. Note that not all fields described below apply to all of these transactions. In the case of Exit Summary Declarations the validation applying to Consignee and Consignor differ from that defined for other Export declarations and the description for these fields are described in Section 9 (9.7.1 and 9.7.2).
3.1.1 Header Data
Decln(1) The first 2 characters must be completed with:
‘CO’ – for the export of goods in free circulation to a special territory of the Community; ‘EU’ – for the export of goods to an EFTA or Common Transit country; ‘EX’ – for the export of goods not in free circulation to another EC member state and all
goods to non-EC and non-EFTA / Common Transit countries.
The third character identifies the entry type (Full Dec, SFD, Supp Dec) and whether the declaration is being pre-lodged or is for an arrived consignment, as follows:
“A” – full declaration (IFD), arrived; “C” – non-transit simplified declaration (PSA), arrived; “D” – full declaration (IFD), pre-lodged; “F” – non-transit simplified declaration (PSA), pre-lodged; “J” – C21, arrived; “K” – C21, pre-lodged; “Y” – SDP supplementary declaration; “Z” – LCP supplementary declaration.
An arrived value may only be declared if the goods are on hand and the CPC of the first non-deleted Item so allows; otherwise a pre-lodged value must be declared. When the entry’s goods have already been notified as arrived by an Inventory system or a Movement Agent, CHIEF ignores the value entered into this field. The field cannot be changed on amendment (AEXD).
Items(5) The number of Items that are included on the declaration. This is compared with the number input as a form of batch control.
Pkgs(6) The number of packages that comprise the consignment.
D/Ref(7) The Declarant’s Reference is a commercial reference supplied by the declarant (or consignor) for his own purposes. CHIEF does not support this field as a key to the Entry.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 12 of 108
Version: 4.0
Cnsgnor(2) The following fields are used to identify the consignor. If there is more than one consignor, the consignor is declared for each item except for some circumstances when details of the individual consignors do not have to be supplied. In this case “GB888888811005” is declared as the Consignor’s Id.
Id The Consignor’s TID. When “GBPR”, “GBUNREG” or not a GB trader id, name and address must be supplied. “GB888888811005” is declared for bulk consignors when details do not have to be supplied. Note that if the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
Name Consignor’s name.
Language The code for the language in which the Consignor’s name and address is written.
Street Consignor’s address – street.
City Consignor’s address – city.
Pstcde Consignor’s address – postcode.
Ctry Consignor’s address – country.
Cnsgnee(8) The following fields are used to identify the consignee. If there is more than one consignee, the consignee is declared for each item. Name and address details must be supplied because the foreign trader will not have a GB TURN, and unlike GB Traders, no name and address details are available on CHIEF.
Id The Consignee’s TID. This is optional. Note that if specified, and the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
Name Consignee’s name.
Language The code for the language in which the Consignee’s name and address is written.
Street Consignee’s address – street.
City Consignee’s address – city.
Pstcde Consignee’s address – postcode.
Ctry Consignee’s address – country.
Declrnt(14) The following fields are used to identify the declarant. If the Trader Identifier (TID) of the declarant is not supplied then the declarant defaults to the Consignor in which case only the ‘Rep’ field is supplied.
Id Except for representation “1” (see ‘Rep’ field), the Trader Identifier (TID) of the declarant must be supplied. TIDs start with a country code. GB identifiers are the current TURN including PR and UNREG. When “GBPR”, “GBUNREG” or not a GB trader id, name and address must be supplied. Note that if the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 13 of 108
Version: 4.0
Rep Declares the way in which the declarant is representing the Consignor:
“1” – Declarant;
“2” – Direct representative;
“3” – Indirect representative.
If there is only one consignor and the consignor is the declarant the value is “1”. “Consignor” should be written in Box 14 and Box 44 on any paper SAD.
Otherwise a declarant is declared with a value dependent on the type of representation authority given by the consignor or all the consignors for bulk.
Name Declarant’s name.
Language The code for the language in which the Declarant’s name and address is written.
Street Declarant’s address – street.
City Declarant’s address – city.
Pstcde Declarant’s address – postcode.
Ctry Declarant’s address – country
Disp ctry(15a) The country code of the country (or pseudo country) from which the consignment was dispatched. The country of dispatch must either be declared at the header or item level but not both.
Goods avail For goods declared inland (i.e. at an approved warehouse or trader’s premises), these fields identify when the goods will be available for examination. The fields are only used by LCP authorised traders. Both dates must lie in the future with the ‘to’ date set ahead of the ‘from’ date.
from Date and time at which the goods are intended to be available for examination at the approved inland premises (also known as the intended date into control). The Entry is automatically arrived at this date-time.
to Date and time at which the goods are expected to be removed from the approved inland premises. If the Entry is on Route 3 or 6, Permission to progress will be automatically granted at this date-time.
Dest ctry(17a) The code for the country of ultimate destination. The country of destination must either be declared at the header or item level but not both.
Inlnd Trpt Id(18)
The inland transport identity.
Trpt (21) Id The intended Identity of Transport if known when the declaration is prepared.
Nat The intended Nationality of active means of Transport if known when the declaration is prepared.
Inv Curr(22) The currency that will be used for invoicing the consignee for the goods covered by the Entry.
This is collected for statistical purposes and is not necessarily the same as the Declaration Currency, in which monetary values on the Entry are input.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 14 of 108
Version: 4.0
Trpt Mode(25) The Mode of Transport for the active means of Transport by which the goods will be exported if known when the declaration is prepared.
Inlnd Trpt Mode(26)
The Mode of Transport for the Inland means of Transport when export formalities are carried out away from the point of exit of the goods from the UK.
Goods Dep Date
Date the goods departed from the place of loading (“Pl loading”) or the last day of the period for an aggregated declaration (e.g. a victuallers CAP refund claim).
Exit Offce(29) The intended Office of Exit from the EU.
Locn goods(30)
The location where the goods first come under Customs control. For supplementary declarations it is the ‘place of loading’. Except for a SASP supplementary declaration for goods exported from another Member State, the field identifies a UK Freight Location and optionally the Shed Operator. UK locations are formatted:
“GB”<freight location><shed operator>.
A Shed Operator (characters 6-8) is supplied when the Location of Goods needs to be more fully specified (e.g. by a Transit Shed code).
Where the goods are situated at the authorised Trader premises or within a warehouse, a numeric code can be given to identify the precise location. Such codes are agreed with the local Customs office and are not known to CHIEF. Otherwise the code must be valid for the specified Freight Location (characters 3-5).
ADDITIONAL INFORMATION(44)
Declaration Currency
Identifies the currency in which the declaration is made. In particular it is the currency in which Item Statistical Value (46), Base Amount (47b) and Declared Tax Amount (47d) are declared. Other declared amounts have an associated currency code.
Only the currencies as defined in Tariff Volume 3 can be specified. The declaration currency defaults to GBP.
Regd Consignor
The TURN of the Registered Consignor responsible for the VAT where this differs from the Consignor as declared in box 2.
Premise The name and address of the premises. When premises have to be declared all fields must be supplied. The following fields are used to identify the premises:
Name Name of the approved premises.
Street Approved premises address – street.
City Approved premises address – city.
Pstcde Approved premises address – postcode.
Ctry Approved premises address – country.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 15 of 108
Version: 4.0
Sup Off The following fields are used to identify the Supervising Office for the premises:
Name Supervising Office name.
Street Supervising Office address – street.
City Supervising Office address – city.
Pstcde Supervising Office address – postcode.
Ctry Supervising Office address – country.
AI Statement Text as required for the AI Statement code.
Code The code identifying the type of AI Statement.
Language The code for the language in which the text is written.
Decln The Unique Consignment Reference (UCR) and part number allocated to the goods by the Trader. The Decln UCR/Part must uniquely identify the Export (pre-shipment) Entry on CHIEF. Note, that a PSA and a related Supplementary Declaration may be given the same UCR/ Part. If not supplied, CHIEF generates a Declaration UCR based upon the CHIEF Entry reference (see Reference [4]).
UCR 9DCR-
The UCR (see Reference [4]).
Part A part number of up to three digits is required when more than one declaration is made to cover the goods identified by the same UCR. The field may also contain a one-character alphabetic check character following the Part number (if supplied). The check character covers the UCR and any Part number.
Mastr UCR 9MCR-
If the goods are known to be in a consolidation with the goods covered by other declarations, the Master UCR for the consolidation can be declared. On amendment no change is allowed and any value submitted in this field will be ignored. After initial declaration the associate facility must be used to modify the consolidation in which the consignment resides.
Doc Details of a document that applies to the whole entry.
Code The code identifying the type of document.
St The status of the document which must be specified when required for the type of document. See Reference [4] for details of the values entered into this field.
Document Reference
The reference identifying the document.
Part This is optionally specified to identify a part of the document, for example, the line of a multi-line Licence (defaulting to 1).
Quantity This is optionally specified for a document to identify a quantity, for example, the quantity to be attributed to the licence. The units in which the quantity is given is defined for the document.
Lang The code for the language in which the document reference is written.
Reason For some status values a reason must be given.
DAN(48) (2 fields)
The Deferment Approval Number (DAN) and associated prefix (A, B, C or D) identifying the deferment account from which revenue is to be debited. The validation that applies to DANs is more fully described in Reference [4].
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 16 of 108
Version: 4.0
Premise Id(49) The identity of the warehouse which is required for Items for which the associated Customs Procedure Code relates to warehousing.
Repr The trader’s representative. On CHIEF only the Submitting trader can amend the declaration. The details are optional for a possible future enhancement when EXSs might be lodged for other MS and then this could indicate a trader who acts as an agent at the Office of Exit
Id Trader identifier for the representative. Note that if the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
Name Name of the representative.
Language The code for the language in which the Representative’s name and address is written.
Street Address of the representative – street.
City Address of the representative – city.
PstCde Address of the representative – postcode.
Ctry Address of the representative – country.
Seal Details of a seal.
Id The seal identifier.
Lang The code for the language in which the seal identifier is written.
Trpt Chrge MOP
The Method of Payment for transport charges.
Ctry on route A country through which the goods have moved or are intended to move between the country of dispatch and the country of destination.
Pl loading The code for the intended Place of Loading (i.e. place of departure of the vessel or flight or other transport).
Notify Prty Details of the party to be notified on Export. Note that notification on Export is not supported by CHIEF.
Id Trader identifier for party to be notified. Note that if the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
Name Name of the party to be notified.
Street Address of party to be notified – street.
City Address of party to be notified – city.
Pstcde Address of party to be notified – postcode.
Ctry Address of party to be notified – country.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 17 of 108
Version: 4.0
3.1.2 Item Data
Cnsgnor(2) The following fields are used to identify the consignor for the item. When consignors are declared for each item the consignor is not declared at the header level. The same consignor must not be supplied at the item level for every item.
Id The Consignor’s TID. When “GBPR”, “GBUNREG” or not a GB trader id, name and address must be supplied. Note that if the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
Name Consignor’s name.
Language The code for the language in which the Consignor’s name and address is written.
Street Consignor’s address – street.
City Consignor’s address – city.
Pstcde Consignor’s address – postcode.
Ctry Consignor’s address – country.
Cnsgnee(8) The following fields are used to identify the consignee for the item. When consignees are declared for each item the consignee is not declared at the header level. Name and address details must be supplied because the foreign trader will not have a GB TURN, and unlike GB Traders, no name and address details are available on CHIEF. The same consignee must not be supplied at the item level for every item.
Id The Consignee’s TID. This is optional. Note that if specified, and the country code of the TID indicates an EU Member State, then the Trader must be known to CHIEF (see Reference [4], section 5.4.1.).
Name Consignee’s name.
Language The code for the language in which the Consignee’s name and address is written.
Street Consignee’s address – street.
City Consignee’s address – city.
Pstcde Consignee’s address – postcode.
Ctry Consignee’s address – country.
Disp ctry(15a) The country code of the country (or pseudo country) from which the consignment was dispatched. The country of dispatch must either be declared at the header or item level but not both. The same country of dispatch must not be supplied at the item level for every item.
Dest ctry(17a) The code for the country of ultimate destination. The country of destination must either be declared at the header or item level but not both. The same country of destination must not be supplied at the item level for every item.
Goods Description(31)
Description of the goods.
Language The code for the language in which the goods description is written.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 18 of 108
Version: 4.0
Package(31) Details of the packages containing the goods. The same packages may be declared for more than one item so the Total Packages for the declaration is not expected to be the total of the packages declared for the items.
Marks Marks to enable the packages of the given kind to be identified.
Number The number of packages or pieces of the kind identified in the next field. The number must not be supplied for bulk goods.
Kind The code identifying the kind of package.
Lang The code for the language in which the package marks are written.
Contnr Id(31) The container number.
Comm code (33)
The Commodity Code for the goods being declared as an Item and any associated EC Supplementary Measure codes.
(field 1) the Base (8 digit) Commodity Code. On amendment, an Item is deleted by replacing the commodity code with ‘DEL’ (other fields of the Item should be left unchanged).
(field 2) the first EC Supplementary Measure code. For a CAP refund claim it contains the ERN prefixed with “9”.
(field 3) the second EC Supplementary Measure code. This field may only be completed if first EC Supplementary Measure code is provided and must be a different code to the first one.
Orig ctry(34a) The code of the Country of Origin identifying the country from which the commodity originates.
Gross mass (35)
The gross mass in kilograms (to 3 decimal places) of the commodity or goods being declared. The field must be completed on ex-warehouse declarations. The Item net mass must not exceed Item gross mass.
UNDG code UN Dangerous Goods code.
CPC(37) The Customs Procedure Code (CPC) which applies to the goods being declared as an Item. The value of the CPC determines the requirement for other Item data. The CPCs quoted on all Items must be in the same CPC series.
Net mass(38) The net mass in kilograms of the associated goods. The quantity can be expressed up to three decimal places. When supplied it must be greater than zero. This information may be used for revenue calculation.
Prev Doc/ Decln (40)
Identifies the previous document relating to the declaration.
(field 1) This field identifies the class or kind of previous document being declared.
(field 2) The previous document type. Both class and type must be recognised as a valid combination (table PRDD).
(field 3) The reference to identify the previous document.
Lang The code for the language in which the reference is written (optional).
Supp units(41) The quantity of the associated goods in terms of the second unit identified in the Tariff. The quantity can be expressed up to three decimal places. When supplied it must be greater than zero. This information may be used for revenue calculation.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 19 of 108
Version: 4.0
ADDITIONAL INFORMATION (44)
Third Quantity Third Quantity is a quantity whose units are related to the commodity where this information is required for revenue calculation. The quantity can be expressed up to three decimal places. When supplied it must be greater than zero.
The third quantity is optional on a Non-Stat declaration. Otherwise it is required when specified in the Tariff for the Commodity.
AI Statement Text as required for the AI Statement code.
Code The code identifying the type of AI Statement.
Language The code for the language in which the text is written.
Sup Off The following fields are used to identify the Supervising Office.
Name Supervising Office name.
Street Supervising Office address – street.
City Supervising Office address – city.
Pstcde Supervising Office address – postcode.
Ctry Supervising Office address – country.
(Document) Details of a document. Code The code identifying the type of document.
St The status of the document which must be specified when required for the type of document. See Reference [4] for details of the values entered into this field.
Document Reference
The reference identifying the document.
Part This is optionally specified to identify a part of the document, for example, the line of a multi-line Licence (defaulting to 1).
Quantity This is optionally specified for a document to identify a quantity, for example, the quantity to be attributed to the licence. The units in which the quantity is given is defined for the document.
Lang The code for the language in which the document reference is written.
Reason For some status values a reason must be given.
Stat value(46) The Statistical Value of the Commodity in the declaration currency.
Trpt Chrge MOP
The Method of Payment for transport charges.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 20 of 108
Version: 4.0
3.1.3 Tax Line Data
CALCULATION OF TAXES(47)
Type(a) The Tax Type identifying the category of revenue being declared.
Base Amount(b)
The Tax Base amount that may be used for revenue calculation. An amount cannot be declared as well as a Tax Base quantity.
Base Quantity The Tax Base amount that may be used for revenue calculation. A quantity cannot be declared as well as a Tax Base amount. A Composite Quantity may only be declared for a tax Rate (47c) of ‘C’.
Rate(c) The Tax Rate identifying the rate at which the revenue has been calculated.
Ovr The Tax Override code identifying an exception to the normal calculation of the associated revenue.
Amount(d) The amount of revenue declared for the tax line.
MOP(e) The Method of Payment by which the revenue is to be paid or refunded. Valid MOP codes are listed in Reference [4].
3.2 Cross-Field Validation Checks
Where fields are defined as a group in Section 3.1 the checks between the fields in the group are included in the field descriptions.
1. Decln(1), Cnsgnor(2) Id, Declrnt(14) Id, Goods avail from/to, Locn goods(30)
When the Location of Goods indicates an inland location (i.e. an approved ‘warehouse’ or ‘Trader’s premises’), the Consignor or Declarant must be authorised for Simplified procedures (SDP or LCP) and the Goods availability dates must be supplied. In addition, the entry must be declared pre-lodged. The Goods availability dates must not be supplied on a Full declaration entered at the frontier.
2. Cnsgnor(2)
A Consignor must be declared for each item unless a Consignor is declared at the header level in which case a Consignee must not be declared for an item. The same consignor must not be specified at the item level for every item
3. Cnsgnee(8)
A Consignee can be declared for each item as required unless a Consignee is declared at the header level. The same consignee must not be specified at the item level for every item
4. Disp ctry(15a)
A Dispatch country must be declared for each item unless a Dispatch country is declared at the header level in which case a Dispatch country must not be declared for an item. The same country must not be specified at the item level for every item.
5. Dest ctry(17a)
A Destination country must be declared for each item unless a Destination country is declared at the header level in which case a Destination country must not be declared for an item. The same country must not be specified at the item level for every item.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 21 of 108
Version: 4.0
6. Trpt nat(21), TrptMode(25)
Nationality of Transport is not supplied for Modes of Transport 2, 5 and 7.
7. Regd Consignor(44 RCONR), Cnsgnor(2)
If a Registered Consignor is declared then Consignor must be declared at header level (i.e. not for each item).
8. DAN(48), MOP(e)
If a method of payment representing deferment is specified on any of the tax lines then the Deferment Account Number and prefix must be specified, and vice versa.
9. CPC(37), Stat value(46)
The Statistical value is optional or mandatory depending on the CPC.
10. Item Document Code, St and Licence Type(44)
For a Licence document the combination of Code, Status and the Licence type declared must be valid on CHIEF. For other categories of document the combination of Code and Status must be valid.
11. Trpt Chrge MOP
When required by Tariff (e.g. Customs Procedure, Commodity), or elsewhere, details must be declared either at the header or item level (not both). When declared at the item level the same details must not be declared for all items.
12. Package(31), Header AI statement(44)
For Exit Summary Declarations (EXS), except for Specific Circumstance “A” (header AI code “SPCIA”), package details are required.
13. Package Marks(31), Package Kind(31)
Package Marks must be supplied when the Package Kind identifies that the goods are in packages, otherwise marks are optional.
14. Package Number(31), Package Kind(31)
Package Number must not be supplied when the Package Kind identifies that the goods are bulk, otherwise Package Number must be supplied.
15. Declrnt(14)
Must be declared if a Consignor is not declared at the header level.
16. Ctry on route, Disp ctry(15a), Dest ctry(17a)
Country on route will be rejected if it contains either the country of dispatch of the country of destination. The country of dispatch and the country of destination can be defined at either the header or item level.
17. Disp ctry(15a), Header AI statement(44)
For Exit Summary Declaration entries, the dispatch country is required except for Specific Circumstance “A” (header AI code “SPCIA”). Note, the dispatch country cannot be declared at the item level on an EXS entry.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 22 of 108
Version: 4.0
18. Goods Description(31), Comm code(33)
For Exit Summary Declarations (EXS) either “Goods Description” or “Comm code” must be declared. Both may be declared. Only the first 4 digits of the commodity code need to be declared in the “Comm code”.
19. CPC(37), Inld Trpt Id(18)
Inland transport identity is optional unless:
prohibited by the CPC or CAP refund is claimed, when it is mandatory regardless of any CPC prohibition.
20. CPC(37), Gross Mass(35) , Header AI statement(44)
Gross Mass is mandatory except for Specific Circumstances “E” (header AI code “SPCIE”). For Specific Circumstance “E”, Gross Mass is optional or mandatory depending on the CPC.
21. Decln UCR(44), Header AI Statement (44), Item Document Code(44)
Except for Specific Circumstance “A” (header AI code “SPCIA”), a transport document must be declared for an item unless a DECLN-UCR is declared at the header level.
22. Inv Curr(22), Stat value(46)
Invoice Currency must be declared when the Entry’s items have a Statistical Value at or above a configurable threshold.
This rule does not apply to low value Bulk Entries (as indicated by the CPC on the Entry’s first item).
23. Cnsgnee (8)
Either Consignee Name and Address details or the Consignee Trader id is required for a particular Consignee declared at the header or item level.
24. Cnsgnor(2)
For EXS Declarations, either Consignor Name and Address details or the Consignor Trader id is required for a particular Consignor declared at the header or item level.
25. Cnsgnee(8), Header AI statement(44)
For EXS Declarations, where the Consignee Details (at Entry Header or on any Item) are not supplied, CHIEF requires an AI statement 30600 to be declared. Conversely, CHIEF rejects an Exit Summary declaration where AI Statement 30600 is declared but no Consignee details are omitted (i.e. the AI Statement is superfluous).
END OF SECTION 3
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 23 of 108
Version: 4.0
4. IEFD – Insert Export Full Declaration
4.1 Business Description
This transaction supports the creation of a declaration on CHIEF representing a SAD Export declaration input under the Normal Procedure (also known as Full Pre-entry). The transaction allows for the initial creation of an entry on CHIEF or to allow the user to continue inserting data for such an Entry which was previously stored from within IEFD and which has now been retrieved from store via LSTR for this purpose.
The transaction is available to the Trade and to Customs and can be used via EDI (Trade only) or HCI interfaces. The facility to store is available only in the HCI context.
The CHIEF transaction provides a facility for the supply of a Declaration UCR and optional Part by which the entry may be referenced in later transactions. It is recommended that a Declaration UCR and optional Part is supplied (see Reference [4]). For locations which are inventory controlled, the UCR provides the means by which those systems may notify advice of a consignment arrival at the location, consignment amendment or shipment from the frontier.
The Full Export declaration can operate either at the UK frontier or inland (e.g. at the Trader’s premises). When used in an inland context by a Trader authorised under simplified procedures, this transaction allows the Trader to supply dates defining when the goods will be available to Customs for examination at the inland premises.
Front End Credibility (FEC) checks are applied to the data at this point (see Reference [4]). If a FEC failure is detected, CHIEF automatically offers you the opportunity to address these by amending the data upon which the FEC challenge is based or by confirming the data is correct as input.
Depending on the circumstances, various reports are generated as a result of this transaction (see Reference [4]).
4.2 Starting the Transaction
You may enter this transaction by typing the command code “IEFD” on the command line. There are no parameters for this transaction.
You may also enter this transaction as a downward selection from the LSTR transaction (see Reference [5]) of an Entry that was previously stored by IEFD.
4.3 Document Data
This section shows how the data for this transaction appears as a Document on your screen.
After you have input all the data from the SAD declaration and completed a visual check for accuracy you should validate or commit the data. It first undergoes validation and any errors found will be identified for correction. If errors are found you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or attempt to commit the data again.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 24 of 108
Version: 4.0
a. IEFD – Header Part 1 Data Input screen ]TRADER-ROLE O INSERT EXPORT FULL DECLARATION CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS *
Decln(1) [ ] Items(5) [ ] Pkgs(6) [ ] D/Ref(7) [ ]
Cnsgnor(2) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Cnsgnee(8) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Declrnt(14) Id [ ] Rep [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Disp ctry(15a) [ ] Goods avail from [ / / ][ : ] to [ / / ][ : ]
Dest ctry(17a) [ ] Inlnd Trpt Id(18) [ ] Lang [ ]
Trpt (21): Id [ ] Nat [ ] Inv Curr(22) [ ]
Trpt Mode(25) [ ] Inlnd Trpt Mode(26) [ ]
Exit Offce(29) [ ] Locn goods(30) [ ]
C10058 Beginning of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
b. IEFD – Header Part 2 Data Input screen ]TRADER-ROLE O INSERT EXPORT FULL DECLARATION CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
ADDITIONAL INFORMATION(44) Declaration Currency [ ]-DCURR
Regd Consignor [ ]-RCONR
Premise Name [ ]-PREMS
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Sup Off Name [ ]-SPOFF
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
AI Statement Code
[a ]–[a ]
Language [a ]
Decln UCR 9DCR-[ ] Part [ ]
Mastr UCR 9MCR-[ ]
Code St Document Reference Part Quantity Lang
[b ]-[b ] [b ] [b ] [b ] [b ]
Reason [b ]
DAN(48) [ ] [ ] Premise Id(49) [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 25 of 108
Version: 4.0
c. IEFD – Header Part 3 Data Input screen ]TRADER-ROLE O INSERT EXPORT FULL DECLARATION CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
Repr(50) Id [ ]
Name [ ] Language [e ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Seal Id/Lang [c ] / [ ] [ ] / [ ]
Trpt Chrge MOP [ ]
Ctry on route [d ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Pl loading [ ]
Notify Prty Id [ ]
Name [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
d. IEFD – Item Data Part 1 Input screen ]TRADER-ROLE O INSERT EXPORT FULL DECLARATION CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No(32) ***
Cnsgnor(2) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Cnsgnee(8) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Disp ctry(15a) [e ] Dest ctry(17a) [e ]
Goods Description(31) Language [e ]
[e ]
Package(31) Marks Number Kind Lang
[f ] [f ] [f ] [c ]
Contnr Id(31) [g ] [ ] [ ]
Comm code(33) [e ] [e ] [e ]
Orig ctry(34a) [e ] Gross mass(35) [e ] UNDG code [ ]
CPC(37) [e ] Net mass(38) [e ]
Prev Doc/Decln(40) [i]-[i ]-[i ] Lang [i ]
VALIDATE,COMMIT,STORE,RETURN [ ]
Should you wish to insert a new Item or Delete/Remove an Item already keyed then your cursor should be placed on one of the Comm Code (box 33) fields or the CPC (box 37) field. Note that Items can only be inserted or deleted during an insert transaction. On amend (AEXD) Items can be appended and deletion is by replacing the Commodity Code with ‘DEL’.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 26 of 108
Version: 4.0
e. IEFD – Item Part 2 Data Input screen ]TRADER-ROLE O INSERT EXPORT FULL DECLARATION CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No(32) ***
Supp units(41) [e ]
ADDITIONAL INFORMATION (44) Third Quantity [ ]-THRDQ
AI Statement Code
[j ]-[j ]
Language [j ]
Sup Off Name [e ]-SPOFF
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Code St Document Reference Part Quantity Lang
[k ]-[k ] [k ] [k ] [k ] [k ]
Reason [k ]
Stat value(46) [e ] Trpt Chrge MOP [ ]
CALCULATION OF TAXES(47)
Type(a) Base Amount(b) Base Quantity Rate(c)Ovr Amount(d) MOP(e)
[l ][l . ][l . ] [l ] [l ] [l ] [l]
[ ][ . ][ . ] [ ] [ ] [ ] [ ]
[ ][ . ][ . ] [ ] [ ] [ ] [ ]
C10059 End of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
f. IEFD – Entry Acceptance screen ]TRADER-ROLE O INSERT EXPORT FULL DECLARATION CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
ACCEPTANCE DETAILS Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
REVENUE SUMMARY: MOP Type Amount
[]* []*** *************
[]* []*** *************
Dfrd tot ************* Immed tot ************* Rev tot *************
Refund tot *************
Route []**
MRN ******************
C10004 Data successfully committed
IEFD,ABORT,PRINT [ ]
There are minor differences in the Entry Acceptance screens for Legally Accepted Entries and for Pre-lodged Entries. The refund total excludes CAP refunds as the amount of refund is only determined when RPA receive the claim from CHIEF (generally after the goods have departed from the UK). The layout of the display screens following the Entry Acceptance screen mirror the layout of the input screens but with the data protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 27 of 108
Version: 4.0
4.4 Document Structure
The repeating segments for the data input screens are shown in the table below.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a Header AI Statement 0 40 1 2 b Header Document 0 40 1 3 c Seal 0 99 1 4 d Country on route 0 99 1 5 e Item 1 99 1
5.1 f Package 1 99 1 5.2 g Container 0 99 1 5.4 i Previous document 1 9 1 5.5 j Item AI Statement 0 99 1 5.6 k Item Document 0 99 1 5.7 l Tax line 0 10 2
4.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply. The fields are detailed in sub-sections for Header, Item and Tax Line.
4.5.1 Header Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Decln(1) M 1 Items(5) M Pkgs(6) M D/Ref(7) O Cnsgnor(2) (id/name/address) O 1, 2, 7 Cnsgnee(8) (id/name/address) O 3, 23 Declrnt(14) (id/name/address) O 1, 15 Declrnt(14) Rep M Disp ctry(15a) O 4, 16 Goods avail from/to O 1 Dest ctry(17a) O 5, 16 Inlnd Trpt Id(18) O 19 Trpt (21): Id O Nat O 6 Inv Curr(22) O 22
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 28 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Trpt Mode(25) O 6 Inlnd Trpt Mode(26) O Exit Offce(29) O Locn goods(30) O 1 ADDITIONAL INFORMATION(44) Declaration Currency O Regd Consignor O 7 Premise (name/address) O Sup Off (name/address) O AI Statement, Code, Language O 21 Decln UCR 9DCR-, Part O 21 Mastr UCR 9MCR- O (Document) Code, St, Document Reference, Part, Quantity, Reason
O
DAN(48) O 8 Premise Id(49) O Repr(50) (id/name/address) O Seal Id/Lang O Trpt Chrge MOP O 11 Ctry on route O 16 Pl loading O Notify Prty (id/name/address) O
4.5.2 Item Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Cnsgnor(2) (id/name/address) O 2 Cnsgnee(8) (id/name/address) O 3, 23 Disp ctry(15a) O 4, 16 Dest ctry(17a) O 5, 16 Goods Description(31)/Language M Package(31) Marks/Number/Kind/Lang
M Package Marks 13 Package Number 14
Contnr Id(31) O Comm code(33) O Orig ctry(34a) O Gross mass(35) O 20 UNDG code O
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 29 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
CPC(37) M 9, 19, 20 Net mass(38) O Prev Doc/Decln (40) M Supp units(41) O ADDITIONAL INFORMATION (44) Third Quantity O AI Statement, Code, Language O Sup Off (name/address) O (Document) Code, St, Document Reference, Part, Quantity, Reason
O 10, 21
Stat value(46) O 9 Trpt Chrge MOP O 11
4.5.3 Tax Line Data (47)
Field Name (SAD Box) Optionality Cross-field Validation Checks
Type(a) M Base Amount(b) O Base Quantity O Rate(c) O Ovr O Amount(d) O MOP(e) O 8
4.6 Field Details
The field details are given in Section 3.1.
4.7 Cross-Field Validation Checks
The cross-field validation checks are defined in Section 3.2.
END OF SECTION 4
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 30 of 108
Version: 4.0
5. IELP – Insert Export LCP Pre-Shipment Advice
5.1 Business Description
This transaction supports the creation of a declaration on CHIEF representing a Pre-shipment advice (PSA) input under Local Clearance Procedure (LCP). The transaction allows for the initial creation of an entry on CHIEF, or to allow the user to continue inserting data for such an Entry which was previously stored from that transaction and which has now been retrieved from store, via LSTR, for this purpose.
This transaction is only available to the Trade, and can be used via EDI or HCI interfaces. The facility to store is available only in the HCI context.
This transaction provides a facility for the supply of a Declaration UCR and optional Part number by which the Entry may be referenced in later transactions (e.g. (anticipated) arrival, amendment, departure). In addition, where the goods are to be placed within a consolidation, and this is known at time of declaration, a Master UCR may be provided.
Consignments entered under LCP procedures must be declared prelodged for an inland location. The transaction accepts dates defining when the goods will be available to Customs for examination at the inland premises.
Front End Credibility (FEC) checks are applied to the data provided on a PSA submitted via HCI as described in Reference [4]. If a FEC failure is detected, CHIEF automatically offers the user the opportunity to address these by amending the data upon which the FEC challenge is based, or by confirming them as correct.
Depending on the circumstances, various reports are generated as a result of this transaction. The reports are described in Reference [4].
5.2 Starting the Transaction
You may enter this transaction by typing the command code “IELP” on the command line. There are no parameters for this transaction.
You may also enter this transaction as a downward selection from the “List Stored” transaction (LSTR, described in Reference [5]). This is achieved by selecting an Entry previously stored by IELP.
5.3 Document Data
This section shows how the data for this transaction appears as a Document on the screen. All screens associated with the LCP PSA transaction are shown in this section.
After you have input all the data from the PSA declaration and completed a visual check for accuracy you should validate or commit the data. It first undergoes validation and any errors found will be identified for correction. If errors are found, you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or attempt to commit the data again.
Once the Entry is free of errors and has been committed it becomes an accepted Entry, either Pre-lodged if the Goods have not arrived, or Legally Accepted if the goods are on hand. Confirmation of the acceptance is provided by the Entry Acceptance screen (see f).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 31 of 108
Version: 4.0
a. IELP – Header Part 1 Data Input screen ]TRADER-ROLE O INSERT LCP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS *
Decln(1) [ ] Items(5) [ ] D/Ref(7) [ ]
Cnsgnor(2) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Cnsgnee(8) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Declrnt(14) Id [ ] Rep [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Disp ctry(15a) [ ] Goods avail from [ / / ][ : ] to [ / / ][ : ]
Dest ctry(17a) [ ] Trpt (21): Nat [ ]
Trpt Mode(25) [ ]
Exit Offce(29) [ ] Locn goods(30) [ ]
C10058 Beginning of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
b. IELP – Header Part 2 Data Input screen ]TRADER-ROLE O INSERT LCP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
ADDITIONAL INFORMATION(44) Declaration Currency [ ]-DCURR
Regd Consignor [ ]-RCONR
Premise Name [ ]-PREMS
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Sup Off Name [ ]-SPOFF
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
AI Statement Code
[a ]–[a ]
Language [a ]
Decln UCR 9DCR-[ ] Part [ ]
Mastr UCR 9MCR-[ ]
Code St Document Reference Part Quantity Lang
[b ]-[b ] [b ] [b ] [b ] [b ]
Reason [b ]
Premise Id(49) [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 32 of 108
Version: 4.0
c. IELP – Header Part 3 Data Input screen ]TRADER-ROLE O INSERT LCP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
Repr(50) Id [ ]
Name [ ] Language [e ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Seal Id/Lang [c ] / [ ] [ ] / [ ]
Trpt Chrge MOP [ ]
Ctry on route [d ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Pl loading [ ]
Notify Prty Id [ ]
Name [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
d. IELP – Item Part 1 Data Input screen ]TRADER-ROLE O INSERT LCP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No(32) ***
Cnsgnor(2) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Cnsgnee(8) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Disp ctry(15a) [e ] Dest ctry(17a) [e ]
Goods Description(31) Language [e ]
[e ]
Package(31) Marks Number Kind Lang
[f ] [f ] [f ] [c ]
Contnr Id(31) [g ] [ ] [ ]
Comm code(33) [e ] [e ] [e ]
Gross mass(35) [e ] UNDG code [ ]
CPC(37) [e ] Net mass(38) [e ]
Prev Doc/Decln(40) [i]-[i ]-[i ] Lang [i ]
VALIDATE,COMMIT,STORE,RETURN [ ]
Should you wish to insert a new Item or Delete/Remove an Item already keyed then your cursor should be placed on one of the Comm Code (box 33) fields or the CPC (box 37) field. Note that Items can only be inserted or deleted during an insert transaction. On amend (AEXD) Items can be appended and deletion is by replacing the Commodity Code with ‘DEL’.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 33 of 108
Version: 4.0
e. IELP – Item Part 2 Data Input screen ]TRADER-ROLE O INSERT LCP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No (32) ***
Supp units(41) [e ]
ADDITIONAL INFORMATION (44) Third Quantity [ . ]-THRDQ
AI Statement Code
[j ]-[j ]
Language [j ]
Sup Off Name [e ]-SPOFF
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Code St Document Reference Part Quantity Lang
[k ]-[k ] [k ] [k ] [k ] [k ]
Reason [k ]
Stat value(46) [e ] Trpt Chrge MOP [ ]
C10059 End of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
f. IELP – Entry Acceptance screen ]TRADER-ROLE O INSERT LCP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
ACCEPTANCE DETAILS Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
Route []**
MRN ******************
C10004 Data successfully committed
IELP,ABORT,PRINT [ ]
There are minor differences in the Entry Acceptance screens for Legally Accepted Entries and for Pre-lodged Entries. The layout of the display screens following the Entry Acceptance screen mirror the layout of the input screens but with the data protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 34 of 108
Version: 4.0
5.4 Document Structure
The repeating segments for the data input screens are shown in the table below.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a Header AI Statement 0 40 1 2 b Header Document 0 40 1 3 c Seal 0 99 1 4 d Country on route 0 99 1 5 e Item 1 99 0
5.1 f Package 1 99 1 5.2 g Container 0 99 1 5.4 i Previous document 1 9 1 5.5 j Item AI Statement 0 99 1 5.6 k Item Document 0 99 1
5.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply. The fields are detailed in sub-sections for Header and Tax Line.
5.5.1 Header Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Decln(1) M 1 Items(5) M D/Ref(7) O Cnsgnor(2) (id/name/address) O 1, 2, 7 Cnsgnee(8) (id/name/address) O 3, 23 Declrnt(14) (id/name/address) O 1,15 Declrnt(14) Rep M Disp ctry(15a) O 4, 16 Goods avail from/to O 1 Dest ctry(17a) O 5, 16 Trpt (21): Nat O 6 Trpt Mode(25) O 6 Exit Offce(29) O Locn goods(30) M 1 ADDITIONAL INFORMATION(44)
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 35 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Declaration Currency O Regd Consignor O 7 Premise (name/address) O Sup Off (name/address) O AI Statement, Code, Language O 21 Decln UCR 9DCR-, Part O 21 Mastr UCR 9MCR- O (Document) Code, St, Document Reference, Part, Quantity, Reason
O
Premise Id(49) O Repr(50) (id/name/address) O Seal Id/Lang O Trpt Chrge MOP O 11 Ctry on route O 16 Pl loading O Notify Prty (id/name/address) O
5.5.2 Item Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Cnsgnor(2) (id/name/address) O 2, 24 Cnsgnee(8) (id/name/address) O 3, 23 Disp ctry(15a) O 4, 16 Dest ctry(17a) O 5, 16 Goods Description(31)/Language M Package(31) Marks/Number/Kind/Lang
M Package Marks 13 Package Number 14
Contnr Id(31) O Comm code(33) O Gross mass(35) O 20 UNDG code O CPC(37) M 9, 20 Net mass(38) O Prev Doc/ Decln (40) M Supp units(41) O ADDITIONAL INFORMATION (44) Third Quantity O AI Statement, Code, Language O
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 36 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Sup Off (name/address) O (Document) Code, St, Document Reference, Part, Quantity, Reason
O 10, 21
Stat value(46) O 9 Trpt Chrge MOP O 11
5.6 Field Details
The field details are given in Section 3.1.
5.7 Cross-Field Validation Checks
The cross-field validation checks are defined in Section 3.2.
END OF SECTION 5
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 37 of 108
Version: 4.0
6. IESP – Insert Export SDP Pre-Shipment Advice
6.1 Business Description
This transaction supports the creation of a declaration on CHIEF representing a Pre-shipment advice (PSA) input under the Simplified Declaration procedure (SDP). The transaction allows for the initial creation of an entry on CHIEF, or to allow the user to continue inserting data for such an Entry which was previously stored from that transaction and which has now been retrieved from store, via LSTR, for this purpose.
This transaction is only available to the Trade, and can be used via EDI or HCI interfaces. The facility to store is available only in the HCI context.
This transaction provides a facility for the supply of a Declaration UCR and optional Part number by which the Entry may be referenced in later transactions (e.g. (anticipated) arrival, amendment, departure). In addition, where the goods are to be placed within a consolidation, and this is known at time of declaration, a Master UCR may be provided.
Front End Credibility (FEC) checks are applied to the data provided on a PSA submitted via HCI as described in Reference [4]. If a FEC failure is detected, CHIEF automatically offers the user the opportunity to address these by amending the data upon which the FEC challenge is based, or by confirming them as correct.
Depending on the circumstances, various reports are generated as a result of this transaction. The reports are described in Reference [4].
6.2 Starting the Transaction
You may enter this transaction by typing the command code “IESP” on the command line. There are no parameters for this transaction.
You may also enter this transaction as a downward selection from the “List Stored” transaction (LSTR, described in Reference [5]). This is achieved by selecting an Entry previously stored by IESP.
6.3 Document Data
This section shows how the data for this transaction appears as a Document on the screen. All screens associated with the SDP PSA transaction are shown in this section.
After you have input all the data from the PSA declaration and completed a visual check for accuracy you should validate or commit the data. It first undergoes validation and any errors found will be identified for correction. If errors are found, you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or attempt to commit the data again.
Once the Entry is free of errors and has been committed it becomes an accepted Entry, either Pre-lodged if the Goods have not arrived, or Legally Accepted if the goods are on hand. Confirmation of the acceptance is provided by the Entry Acceptance screen (see f).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 38 of 108
Version: 4.0
a. IESP – Header Part 1 Data Input screen ]TRADER-ROLE O INSERT SDP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS *
Decln(1) [ ] Items(5) [ ] D/Ref(7) [ ]
Cnsgnor(2) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Cnsgnee(8) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Declrnt(14) Id [ ] Rep [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Disp ctry(15a) [ ]
Dest ctry(17a) [ ] Trpt (21): Nat [ ]
Trpt Mode(25) [ ]
Exit Offce(29) [ ] Locn goods(30) [ ]
C10058 Beginning of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
b. IESP – Header Part 2 Data Input screen ]TRADER-ROLE O INSERT SDP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
ADDITIONAL INFORMATION(44) Declaration Currency [ ]-DCURR
Regd Consignor [ ]-RCONR
Premise Name [ ]-PREMS
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Sup Off Name [ ]-SPOFF
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
AI Statement Code
[a ]–[a ]
Language [a ]
Decln UCR 9DCR-[ ] Part [ ]
Mastr UCR 9MCR-[ ]
Code St Document Reference Part Quantity Lang
[b ]-[b ] [b ] [b ] [b ] [b ]
Reason [b ]
VALIDATE,COMMIT,STORE,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 39 of 108
Version: 4.0
c. IESP – Header Part 3 Data Input screen ]TRADER-ROLE O INSERT SDP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
Repr(50) Id [ ]
Name [ ] Language [e ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Seal Id/Lang [c ] / [ ] [ ] / [ ]
Trpt Chrge MOP [ ]
Ctry on route [d ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Pl loading [ ]
Notify Prty Id [ ]
Name [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
d. IESP – Item Part 1 Data Input screen ]TRADER-ROLE O INSERT SDP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No(32) ***
Cnsgnor(2) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Cnsgnee(8) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Disp ctry(15a) [e ] Dest ctry(17a) [e ]
Goods Description(31) Language [e ]
[e ]
Package(31) Marks Number Kind Lang
[f ] [f ] [f ] [c ]
Contnr Id(31) [g ] [ ] [ ]
Comm code(33) [e ] [e ] [e ]
Gross mass(35) [e ] UNDG code [ ]
CPC(37) [e ] Net mass(38) [e ]
Prev Doc/Decln(40) [i]-[i ]-[i ] Lang [i ]
VALIDATE,COMMIT,STORE,RETURN [ ]
Should you wish to insert a new Item or Delete/Remove an Item already keyed then your cursor should be placed on one of the Comm Code (box 33) fields or the CPC (box 37) field. Note that Items can only be inserted or deleted during an insert transaction. On amend (AEXD) Items can be appended and deletion is by replacing the Commodity Code with ‘DEL’.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 40 of 108
Version: 4.0
e. IESP – Item Part 2 Data Input screen ]TRADER-ROLE O INSERT SDP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No (32) ***
Supp units(41) [e ]
ADDITIONAL INFORMATION (44) Third Quantity [ ]-THRDQ
AI Statement Code
[j ]-[j ]
Language [j ]
Sup Off Name [e ]-SPOFF
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Code St Document Reference Part Quantity Lang
[k ]-[k ] [k ] [k ] [k ] [k ]
Reason [k ]
Stat value(46) [e ] Trpt Chrge MOP [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
f. IESP – Entry Acceptance screen ]TRADER-ROLE O INSERT SDP PRE-SHIPMENT ADVICE CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
ACCEPTANCE DETAILS Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
Route []**
MRN ******************
C10004 Data successfully committed
IESP,ABORT,PRINT [ ]
There are minor differences in the Entry Acceptance screens for Legally Accepted Entries and for Pre-lodged Entries. The layout of the display screens following the Entry Acceptance screen mirror the layout of the input screens but with the data protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 41 of 108
Version: 4.0
6.4 Document Structure
The repeating segments for the data input screens are shown in the table below.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a Header AI Statement 0 40 1 2 b Header Document 0 40 1 3 c Seal 0 99 1 4 d Country on route 0 99 1 5 e Item 1 99 0
5.1 f Package 1 99 1 5.2 g Container 0 99 1 5.4 i Previous document 1 9 1 5.5 j Item AI Statement 0 99 1 5.6 k Item Document 0 99 1
6.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply. The fields are detailed in sub-sections for Header and Tax Line.
6.5.1 Header Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Decln(1) M Items(5) M D/Ref(7) O Cnsgnor(2) (id/name/address) O 2, 7 Cnsgnee(8) (id/name/address) O 3, 23 Declrnt(14) (id/name/address) O 15 Declrnt(14) Rep M Disp ctry(15a) O 4, 16 Dest ctry(17a) O 5, 16 Trpt (21): Nat O 6 Trpt Mode(25) O 6 Exit Offce(29) O Locn goods(30) O ADDITIONAL INFORMATION(44) Declaration Currency O
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 42 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Regd Consignor O 7 Premise (name/address) O Sup Off (name/address) O AI Statement, Code, Language O 21 Decln UCR 9DCR-, Part O 21 Mastr UCR 9MCR- O (Document) Code, St, Document Reference, Part, Quantity, Reason
O
Premise Id(49) O Repr(50) (id/name/address) O Seal Id/Lang O Chrge MOP O 11 Ctry on route O 16 Pl loading O Notify Prty (id/name/address) O
6.5.2 Item Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Cnsgnor(2) (id/name/address) O 2, 24 Cnsgnee(8) (id/name/address) O 3, 23 Disp ctry(15a) O 4, 16 Dest ctry(17a) O 5, 16 Goods Description(31)/Language M Package(31) Marks/Number/Kind/Lang
M Package Marks 13 Package Number 14
Contnr Id(31) O Comm code(33) O Gross mass O 20 UNDG code O CPC(37) M 9, 20 Net mass(38) O Prev Doc/ Decln (40) M Supp units(41) O ADDITIONAL INFORMATION (44) Third Quantity O AI Statement, Code, Language O
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 43 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Sup Off (name/address) O (Document) Code, St, Document Reference, Part, Quantity, Reason
O 10, 21
Stat value(46) O 9 Trpt Chrge MOP O 11
6.6 Field Details
The field details are given in Section 3.1.
6.7 Cross-Field Validation Checks
The cross-field validation checks are defined in Section 3.2.
END OF SECTION 6
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 44 of 108
Version: 4.0
7. IECR – Insert Export Clearance Request (C21)
7.1 Business Description
This transaction supports the creation of a declaration on CHIEF representing a clearance request from a declaration supplied on a C21. The C21 declaration is used to trigger the release of goods from an inventory. The transaction allows for the initial creation of an entry on CHIEF, or to continue inserting data for such an Entry that was previously stored from within IECR, and has now been retrieved from store, via LSTR, for this purpose.
The transaction is available to the Trade and to Customs, and can be used via EDI (Trade only) or HCI interfaces. The facility to store is available only in the HCI context.
For a Trader, the Entry Number and Date are not allowed as input, but are supplied by the system when the Entry is accepted. For Customs, this information needs to be input.
Depending on the circumstances, various reports (see Reference [4]) are generated as a result of this transaction.
7.2 Starting the Transaction
You may enter this transaction by typing the command code ‘IECR’ on the command line. No parameters to the command code are necessary.
You may also enter this transaction as a downward selection from the LSTR transaction (see Reference [5]) of an Entry that was previously stored by IECR.
7.3 Document Data
This section shows how the data for this transaction appears as a Document on the screen.
After you have input all the data from the C21 declaration and completed a visual check for accuracy you should validate or commit the data. It first undergoes validation and any errors found are reported for correction. If errors are found you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or commit the data again.
Once the Entry is free of errors and has been committed it becomes an accepted Entry, either Pre-lodged if the Goods have not arrived, or Legally Accepted if the goods are on hand. Confirmation of the acceptance is provided by the Entry Acceptance screen (see e).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 45 of 108
Version: 4.0
a. IECR – Header Part 1 Data Input screen ]TRADER-ROLE O INSERT EXPORT CLEARANCE REQUEST CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS *
Decln(1) [ ] Pkgs(6) [ ] D/Ref(7) [ ]
Cnsgnor(2) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Cnsgnee(8) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Declrnt(14) Id [ ] Rep [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Locn goods(30) [ ]
C10058 Beginning of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
b. IECR – Header Part 2 Data Input screen ]TRADER-ROLE O INSERT EXPORT CLEARANCE REQUEST CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
ADDITIONAL INFORMATION(44) Declaration Currency [ ]-DCURR
Premise Name [ ]-PREMS
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Sup Off Name [ ]-SPOFF
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
AI Statement Code
[a ]–[a ]
Language [a ]
Decln UCR 9DCR-[ ] Part [ ]
Mastr UCR 9MCR-[ ]
Code St Document Reference Part Quantity Lang
[b ]-[b ] [b ] [b ] [b ] [b ]
Reason [b ]
DAN(48) [ ] [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
c. IECR – Header Part 3 Data Input screen ]TRADER-ROLE O INSERT EXPORT CLEARANCE REQUEST CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
Seal Id/Lang [c ] / [ ] [ ] / [ ]
Trpt Chrge MOP [ ]
Ctry on route [d ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Pl loading [ ]
Notify Prty Id [ ]
Name [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 46 of 108
Version: 4.0
d. IECR – Item Data Input screen ]TRADER-ROLE O INSERT EXPORT CLEARANCE REQUEST CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
Goods Description(31) Language [e ]
[e ]
Package(31) Marks Number Kind Lang
[f ] [f ] [f ] [c ]
Contnr Id(31) [g ] [ ] [ ]
Gross mass(35) [e ] UNDG code [ ]
CPC(37) [e ]
Prev Doc/Decln(40) [i]-[i ]-[i ] Lang [i ]
ADDITIONAL INFORMATION (44)
AI Statement Code
[j ]-[j ]
Language [j ]
Code St Document Reference Part Quantity Lang
[k ]-[k ] [k ] [k ] [k ] [k ]
Reason [k ]
Trpt Chrge MOP [ ]
CALCULATION OF TAXES(47)
Type(a) Base Amount(b) Base Quantity Amount(d) MOP(e)
[k ] [k ][k ] [k ] [k]
VALIDATE,COMMIT,STORE,RETURN [ ]
e. IECR – Entry Acceptance screen
]TRADER-ROLE O INSERT EXPORT CLEARANCE REQUEST CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
ACCEPTANCE DETAILS Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
REVENUE SUMMARY: MOP Type Amount
[]* []*** *************
[]* []*** *************
Dfrd tot ************* Immed tot ************* Rev tot *************
Route []**
MRN ******************
C10004 Data successfully committed
IECR,ABORT,PRINT [ ]
There are minor differences in the Entry Acceptance screens for Legally Accepted Entries and for Pre-lodged Entries. The layout of the display screens following the Entry Acceptance screen mirror the layout of the input screens but with the data protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 47 of 108
Version: 4.0
7.4 Document Structure
The repeating segments for the data input screens are shown in the table below.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a Header AI Statement 0 40 1 2 b Header Document 0 40 1 3 c Seal 0 99 1 4 d Country on route 0 99 1 5 e Item 1 1 0
5.1 f Package 1 99 1 5.2 g Container 0 99 1 5.3 i Previous document 1 9 1 5.4 j Item AI Statement 0 99 1 5.5 k Item Document 0 99 1 5.6 l Tax line 0 10 2
7.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply. The fields are detailed in sub-sections for Header and Tax Line.
7.5.1 Header Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Decln(1) M Items(5) M Pkgs(6) O D/Ref(7) O Cnsgnor(2) (id/name/address) M Cnsgnee(8) (id/name/address) O 23 Declrnt(14) (id/name/address) O 15 Declrnt(14) Rep M Locn goods(30) M ADDITIONAL INFORMATION(44) Declaration Currency O Premise (name/address) O Sup Off (name/address) O AI Statement, Code, Language O 21
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 48 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Decln UCR 9DCR-, Part O 21 Mastr UCR 9MCR- O (Document) Code, St, Document Reference, Part, Quantity, Reason
O
DAN(48) O 8 Seal Id/Lang O Trpt Chrge MOP O 11 Ctry on route O Pl loading O Notify Prty (id/name/address) O
7.5.2 Item Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Goods Description(31)/Language M Package(31) Marks/Number/Kind/Lang
M Package Marks 13 Package Number 14
Contnr Id(31) O Gross mass(35) O 20 UNDG code O CPC(37) M 20 Prev Doc/ Decln (40) M ADDITIONAL INFORMATION (44) AI Statement, Code, Language O (Document) Code, St, Document Reference, Part, Quantity, Reason
O 10, 21
Trpt Chrge MOP O 11 7.5.3 Tax Line Data (47)
Field Name (SAD Box) Optionality Cross-field Validation Checks
Type(a) M Base Amount(b) O Base Quantity O Amount(d) O MOP(e) O 8
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 49 of 108
Version: 4.0
7.6 Field Details
The field details are given in Section 3.1.
7.7 Cross-Field Validation Checks
The cross-field validation checks are defined in Section 3.2.
END OF SECTION 7
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 50 of 108
Version: 4.0
8. IESD – Insert Export Supplementary Declaration
8.1 Business Description
This transaction supports the creation of an entry on CHIEF representing a Supplementary Declaration. The transaction allows for the initial creation of an entry on CHIEF or to allow the user to continue inserting data for such an Entry which was previously stored from within IESD and which has now been retrieved from store via LSTR for this purpose.
The transaction is available to the Trade and can be used via EDI or HCI interfaces. The facility to store is available only in the HCI context.
The CHIEF transaction provides the facility to supply a Declaration UCR along with an optional Part number by which the Entry may be referenced in other transactions. The Declaration UCR provides the means by which the related PSA(s) are associated.
8.2 Starting the Transaction
You may enter this transaction by typing the command code “IESD” on the command line. There are no parameters for this transaction.
You may also enter this transaction as a downward selection from the LSTR transaction (see Reference [5]) of an Entry that was previously stored by IESD.
8.3 Document Data
This section shows how the data for this transaction appears as a Document on your screen.
After you have input all the Supplementary Declaration data and completed a visual check for accuracy you should validate or commit the data. It first undergoes validation and any errors found will be identified for correction. If errors are found you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or attempt to commit the data again.
a. IESD – Header Part 1 Data Input screen ]TRADER-ROLE O INSERT EXPORT SUPPLEMENTARY DECLARA CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS *
Tax Point Date [ / / ] Time [ : ]
Decln(1) [ ] Items(5) [ ] Pkgs(6) [ ] D/Ref(7) [ ]
Cnsgnor(2) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Cnsgnee(8) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Declrnt(14) Id [ ] Rep [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Disp ctry(15a) [ ]
Dest ctry(17a) [ ] Trpt (21): Nat [ ] Inv Curr(22) [ ]
Trpt Mode(25) [ ] Inlnd Trpt Mode(26) [ ] Goods Dep Date [ / / ]
Exit Offce(29) [ ] Locn goods(30) [ ]
C10058 Beginning of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 51 of 108
Version: 4.0
b. IESD – Header Part 2 Data Input screen ]TRADER-ROLE O INSERT EXPORT SUPPLEMENTARY DECLARA CHIEF/CIES 01/10/09 12:15
SADHDR4:1H
EPU []*** EPS *
ADDITIONAL INFORMATION(44) Declaration Currency [ ]-DCURR
Regd Consignor [ ]-RCONR
Premise Name [ ]-PREMS
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
Sup Off Name [ ]-SPOFF
Street [ ]
City [ ] PstCde [ ]Ctry [ ]
AI Statement Code
[a ]–[a ]
Language [a ]
Decln UCR 9DCR-[ ] Part [ ]
Code St Document Reference Part Quantity Lang
[b ]-[b ] [b ] [b ] [b ] [b ]
Reason [b ]
DAN(48) [ ] [ ] Premise Id(49) [ ]
Seal Id/Lang [c ] / [ ] [ ] / [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
c. IESD – Item Data Part 1 Input screen ]TRADER-ROLE O INSERT EXPORT SUPPLEMENTARY DECLARA CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No(32) ***
Cnsgnor(2) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Cnsgnee(8) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Disp ctry(15a) [e ] Dest ctry(17a) [e ]
Package(31) Marks Number Kind Lang
[f ] [f ] [f ] [c ]
Contnr Id(31) [g ] [ ] [ ]
Comm code(33) [e ] [e ] [e ]
Orig ctry(34a) [e ] Gross mass(35) [e ]
CPC(37) [e ] Net mass(38) [e ]
Prev Doc/Decln(40) [i]-[i ]-[i ] Lang [i ]
VALIDATE,COMMIT,STORE,RETURN [ ]
Should you wish to insert a new Item or Delete/Remove an Item already keyed then your cursor should be placed on one of the Comm Code (box 33) fields or the CPC (box 37) field. Note that Items can only be inserted or deleted during an insert transaction. On amend (AEXD) Items can be appended and deletion is by replacing the Commodity Code with ‘DEL’.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 52 of 108
Version: 4.0
d. IESD – Item Part 2 Data Input screen ]TRADER-ROLE O INSERT EXPORT SUPPLEMENTARY DECLARA CHIEF/CIES 01/10/09 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No (32) ***
Supp units(41) [e ]
ADDITIONAL INFORMATION (44) Third Quantity [ ]-THRDQ
AI Statement Code
[j ]-[j ]
Language [j ]
Sup Off Name [e ]-SPOFF
Street [e ]
City [e ] PstCde [e ]Ctry [e ]
Code St Document Reference Part Quantity Lang
[k ]-[k ] [k ] [k ] [k ] [k ]
Reason [k ]
Stat value(46) [e ]
CALCULATION OF TAXES(47)
Type(a) Base Amount(b) Base Quantity Rate(c)Ovr Amount(d) MOP(e)
[l ][l . ][l . ] [l ] [l ] [l ] [l]
[ ][ . ][ . ] [ ] [ ] [ ] [ ]
[ ][ . ][ . ] [ ] [ ] [ ] [ ]
C10059 End of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
e. IESD – Entry Acceptance screen ]TRADER-ROLE O INSERT EXPORT SUPPLEMENTARY DECLARA CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
ACCEPTANCE DETAILS Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
REVENUE SUMMARY: MOP Type Amount
[]* []*** *************
[]* []*** *************
Dfrd tot ************* Immed tot ************* Rev tot *************
Refund tot *************
Route []**
MRN ******************
Tax Point Date **/**/**** Time **:**
C10004 Data successfully committed
IESD,ABORT,PRINT [ ]
There are minor differences in the Entry Acceptance screens for Legally Accepted Entries and for Pre-lodged Entries. The refund total excludes CAP refunds as the amount of refund is only determined when RPA receive the claim from CHIEF (generally after the goods have departed from the UK). The layout of the display screens following the Entry Acceptance screen mirror the layout of the input screens but with the data protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 53 of 108
Version: 4.0
8.4 Document Structure
The repeating segments for the data input screens are shown in the table below.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a Header AI Statement 0 40 1 2 b Header Document 0 40 1 3 c Seal 0 99 1 4 e Item 1 99 1
4.1 f Package 1 99 1 4.2 g Container 0 99 1 4.3 i Previous document 1 9 1 4.4 j Item AI Statement 0 99 1 4.5 k Item Document 0 99 1 4.6 l Tax line 0 10 2
8.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply. The fields are detailed in sub-sections for Header, Item and Tax Line.
8.5.1 Header Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Decln(1) M Items(5) M Pkgs(6) M D/Ref(7) O Cnsgnor(2) (id/name/address) O 2 Cnsgnee(8) (id/name/address) O 3,23 Declrnt(14) (id/name/address) O 15 Declrnt(14) Rep M Disp ctry(15a) O 4 Dest ctry(17a) O 5 Trpt (21): Nat M 6 Inv Curr O 22 Trpt Mode(25) M 6 Inlnd Trpt Mode(26) O Goods Dep Date M
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 54 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
Exit Offce(29) O Locn goods(30) M ADDITIONAL INFORMATION(44) Declaration Currency O Regd Consignor O 7 Premise (name/address) O Sup Off (name/address) O AI Statement, Code, Language O Decln UCR 9DCR-, Part O (Document) Code, St, Document Reference, Part, Quantity, Reason
O
DAN(48) O 8 Premise Id(49) O Seal Id/Lang O
8.5.2 Item Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Cnsgnor(2) (id/name/address) O 2 Cnsgnee(8) (id/name/address) O 3, 23 Disp ctry(15a) O 4 Dest ctry(17a) O 5 Package(31) Marks/Number/Kind/Lang
M Package Marks 13 Package Number 14
Contnr Id(31) O Comm code(33) O Orig ctry(34a) O Gross mass(35) O 20 CPC(37) M 9, 20 Net mass(38) O Prev Doc/ Decln (40) M Supp units(41) O ADDITIONAL INFORMATION (44) Third Quantity O AI Statement, Code, Language O Sup Off (name/address) O
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 55 of 108
Version: 4.0
Field Name (SAD Box) Optionality Cross-field Validation Checks
(Document) Code, St, Document Reference, Part, Quantity, Reason
O 10
Stat value(46) O 9
8.5.3 Tax Line Data (47)
Field Name (SAD Box) Optionality Cross-field Validation Checks
Type(a) M Base Amount(b) O Base Quantity O Rate(c) O Ovr O Amount(d) O MOP(e) O 8
8.6 Field Details
The field details are given in Section 3.1.
8.7 Cross-Field Validation Checks
The cross-field validation checks are defined in Section 3.2.
END OF SECTION 8
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 56 of 108
Version: 4.0
9. IEXS – Insert Exit Summary Declaration
9.1 Business Description
This transaction supports the creation of a SAD Export declaration for provision of safety and security information in the exceptional case where no fiscal declaration is required. The goods being declared may have originated from any member state but are regarded as being directly exported from the UK. The EXS is needed so that the goods can be profiled for Safety and Security purposes before exiting from the EU. The validation applied to Consignee and Consignor details differ from those applied to other Export declarations to accommodate EU rules defined within KEL27 and these are summarised in 9.5, 9.6 and 9.7.
9.2 Starting the Transaction
You may enter this transaction by typing the command code “IEXS” on the command line. There are no parameters for this transaction.
You may also enter this transaction as a downward selection from the LSTR transaction (see Reference [8]) of an Entry that was previously stored by IEXS.
9.3 Document Data
This section shows how the data for this transaction appears as a Document on your screen.
After you have input all the data from the SAD declaration and completed a visual check for accuracy you should validate or commit the data. It first undergoes validation and any errors found will be identified for correction. If errors are found you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or attempt to commit the data again.
a. IEXS – Header Part 1 Data Input screen ]ROLE O INSERT EXIT SUMMARY DECLARATION CHIEF/CIES 01/10/07 12:15
SADKEY:1P
EPU []*** EPS *
Items(5) [ ] Pkgs(6) [ ]
Cnsgnor(2) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Cnsgnee(8) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Declrnt(14) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Disp ctry(15a) [ ] Dest ctry(17a) [ ] Locn goods(30) [ ]
C10058 Beginning of Document
VALIDATE,COMMIT,STORE,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 57 of 108
Version: 4.0
b. IEXS – Header Part 2 Data Input screen ]CUSTOMS-USER O INSERT EXIT SUMMARY DECLARATION CHIEF/CIES 01/10/07 12:15
SADHDR4:1H
EPU []*** EPS *
ADDITIONAL INFORMATION(44)
AI Statement Code
[a ]–[a ]
Language [a ]
Decln UCR 9DCR-[ ] Part [ ]
Mastr UCR 9MCR-[ ]
Repr(50) Id [ ]
Name [ ] Language [ ]
Street [ ]
City [ ] PstCde [ ] Ctry [ ]
Seal Id/Lang [c ] / [ ] [ ] / [ ]
Trpt Chrge MOP [ ]
Ctry on route [d ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
VALIDATE,COMMIT,STORE,RETURN [ ]
c. IEXS – Item Part 1 Data Input screen ]ROLE O INSERT EXIT SUMMARY DECLARATION CHIEF/CIES 01/10/07 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No(32) ***
Cnsgnor(2) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ] Ctry [e ]
Cnsgnee(8) Id [e ]
Name [e ] Language [e ]
Street [e ]
City [e ] PstCde [e ] Ctry [e ]
Goods Description(31) Language [e ]
[e ]
Package(31) Marks Number Kind Lang
[f ] [f ] [f ] [c ]
Contnr Id(31) [g ] [ ] [ ]
Comm code(33) [e ]
Gross mass(35) [e ] CPC(37) [e ] UNDG code [ ]
Trpt Chrge MOP [e]
VALIDATE,COMMIT,STORE,RETURN [ ]
Should you wish to insert a new Item or Delete/Remove an Item already keyed then your cursor should be placed on one of the Comm Code (box 33) fields or the CPC (box 37) field. Note that Items can only be inserted or deleted during an insert transaction. On amend (AEXD) Items can be appended and deletion is by replacing the Commodity Code with ‘DEL’.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 58 of 108
Version: 4.0
d. IEXS – Item Part 2 Data Input screen ]ROLE O INSERT EXIT SUMMARY DECLARATION CHIEF/CIES 01/10/07 12:15
SADITKEY:1P
EPU []*** EPS *
ITEM No (32) ***
ADDITIONAL INFORMATION (44)
Code St Document Reference Part Quantity Lang
[k ]-[k ] [k ] [k ] [k ] [k ]
Reason [k ]
VALIDATE,COMMIT,STORE,RETURN [ ]
e. IEXS – Entry Acceptance screen
]ROLE O INSERT EXIT SUMMARY DECLARATION CHIEF/CIES 01/10/07 09 12:15
SADKEY:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
ACCEPTANCE DETAILS Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
Route []**
MRN ******************
C10004 Data successfully committed
IEXS,ABORT,PRINT [ ]
There are minor differences in the Entry Acceptance screens for Legally Accepted Entries and for Pre-lodged Entries. The layout of the display screens following the Entry Acceptance screen mirror the layout of the input screens but with the data protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 59 of 108
Version: 4.0
9.4 Document Structure
The repeating segments for the data input screens are shown in the table below.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a AI Statement 0 40 1 3 c Seal 0 99 1 4 d Country on route 0 99 1 5 e Item 1 999 1
5.1 f Package 1 99 1 5.2 g Container 0 99 1 5.6 k Document 0 99 1
9.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply. The fields are detailed in sub-sections for Header and Item.
9.5.1 Header Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Entry Ref: Number/Date/Time M Items(5) M Pkgs(6) O Cnsgnor(2) (id/name/address) O 2, 15, 24 Cnsgnee(8) (id/name/address) O 3, 23, 25 Declrnt(14) (id/name/address) O 15 Disp ctry(15a) O 16, 17 Dest ctry(17a) M 16 Locn goods(30) M ADDITIONAL INFORMATION(44) AI Statement, Code, Language O 12, 17, 21, 25 Decln UCR 9DCR-, Part O 21 Mastr UCR 9MCR- O Repr(50) (id/name/address) O Seal Id/Lang O Trpt Chrge MOP O 11 Ctry on route O 16
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 60 of 108
Version: 4.0
9.5.2 Item Data
Field Name (SAD Box) Optionality Cross-field Validation Checks
Cnsgnor(2) (id/name/address) O 2, 24 Cnsgnee(8) (id/name/address) O 3, 23, 25 Goods Description(31), Language O 18 Package(31) Marks/Number/Kind/Lang
M 12 Package Marks 13
Package Number 14 Contnr Id(31) O Comm code(33) O 18 Gross mass(35) O 20 CPC(37) M 18, 20 UNDG code O Trpt Chrge MOP O 11 ADDITIONAL INFORMATION (44) (Document) Code, St, Document Reference, Part, Quantity, Reason
O 10, 21
9.6 Field Details
The field details are given in Section 3.1.
In the case of Consignor and Consignee details entered at header or item level, the validation differs for Exit Summary declarations and a separate description is provided for these fields below.
9.6.1 Header Data
Cnsgnor(2) The following fields are used to identify the consignor. If there is more than one consignor, the consignor is declared for each item except for some circumstances when details of the individual consignors do not have to be supplied. In this case “GB888888811005” is declared as the Consignor’s Id. On EXS declarations either Trader ‘Id’ or the Name and Address details are required. Trader ‘Id’ is supplied when it identifies an EU EORI or 3rd country MRA Trader that is known to CHIEF and is active. Otherwise, Trader ‘Id’ is omitted and a Name and Address is required. This means there is no requirement to provide “GBPR” or “GBUNREG” when Private or Unregistered Traders are involved as the Name and Address is sufficient.
Id The Consignor’s TID. “GB888888811005” is declared for bulk consignors when details do not have to be supplied. The TID must identify a known and active EORI Trader when the country code of the TID identifies an EU Member State or, when the country code identifies a 3rd country, a known and active MRA Trader, (see Reference [4], section 5.4.1).
Name Consignor’s name.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 61 of 108
Version: 4.0
Language The code for the language in which the Consignor’s name and address is written.
Street Consignor’s address – street.
City Consignor’s address – city.
Pstcde Consignor’s address – postcode.
Ctry Consignor’s address – country.
Cnsgnee(8) The following fields are used to identify the consignee. If there is more than one consignee, the consignee is declared for each item. On EXS declarations either Trader ‘Id’ or the Name and Address details are required. Trader ‘Id’ is supplied when it identifies an EU EORI or 3rd country MRA Trader that is known to CHIEF and is active. Otherwise, Trader ‘Id’ is omitted and a Name and Address is required. This means there is no requirement to provide “GBPR” or “GBUNREG” when Private or Unregistered Traders are involved as the Name and Address is sufficient.
Id The Consignee’s TID. This is optional. The TID must identify a known and active EORI Trader when the country code of the TID identifies an EU Member State or, when the country code identifies a 3rd country, a known and active MRA Trader, (see Reference [4], section 5.4.1.).
Name Consignee’s name.
Language The code for the language in which the Consignee’s name and address is written.
Street Consignee’s address – street.
City Consignee’s address – city.
Pstcde Consignee’s address – postcode.
Ctry Consignee’s address – country.
9.6.2 Item Data
Cnsgnor(2) The following fields are used to identify the consignor for an item. When consignors are declared for each item the consignor is not declared at the header level. The same consignor must not be specified at the item level for every item. On EXS declarations either Trader ‘Id’ or the Name and Address details are required. Trader ‘Id’ is supplied when it identifies an EU EORI or 3rd country MRA Trader that is known to CHIEF and is active. Otherwise, Trader ‘Id’ is omitted and a Name and Address is required. This means there is no requirement to provide “GBPR” or “GBUNREG” when Private or Unregistered Traders are involved as the Name and Address is sufficient.
Id The Consignor’s TID. The TID must identify a known and active EORI Trader when the country code of the TID identifies an EU Member State or, when the country code identifies a 3rd country, a known and active MRA Trader, (see Reference [4], section 5.4.1).
Name Consignor’s name.
Language The code for the language in which the Consignor’s name and address is written.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 62 of 108
Version: 4.0
Street Consignor’s address – street.
City Consignor’s address – city.
Pstcde Consignor’s address – postcode.
Ctry Consignor’s address – country.
Cnsgnee(8) The following fields are used to identify the consignee for the item. When consignees are declared for each item the consignee is not declared at the header level. The same consignee cannot be specified at the item level for every item. On EXS declarations either Trader ‘Id’ or the Name and Address details are required. Trader ‘Id’ is supplied when it identifies an EU EORI or 3rd country MRA Trader that is known to CHIEF and is active. Otherwise, Trader ‘Id’ is omitted and a Name and Address is required. This means there is no requirement to provide “GBPR” or “GBUNREG” when Private or Unregistered Traders are involved as the Name and Address is sufficient.
Id The Consignee’s TID. This is optional. The TID must identify a known and active EORI Trader when the country code of the TID identifies an EU Member State or, when the country code identifies a 3rd country, a known and active MRA Trader, (see Reference [4], section 5.4.1.).
Name Consignee’s name.
Language The code for the language in which the Consignee’s name and address is written.
Street Consignee’s address – street.
City Consignee’s address – city.
Pstcde Consignee’s address – postcode.
Ctry Consignee’s address – country.
9.7 Cross-Field Validation Checks
The cross-field validation checks are defined in Section 3.2.
END OF SECTION 9
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 63 of 108
Version: 4.0
10. AEXD – Amend Export Entry
10.1 Business Description
This transaction allows you to amend the declaration details of an Export Entry which has been Legally Accepted or Pre-lodged, or to continue to amend data for such an Entry which was previously stored during amendment and has now been retrieved from store for this purpose. (Entries that have been stored prior to acceptance are amended using the appropriate Insert transaction that is invoked via LSTR.) The declaration may have been committed by any of the Export Entry insert transactions available to you (IEFD, IESP, IELP, IECR, IESD). All of the declaration details with the exception of key data (i.e. CHIEF Entry key fields and Declaration UCR/part) will be available for amendment. Goods Location is available for amendment whilst the entry is pre-lodged. Once goods arrival is notified CHIEF ignores any value of Goods Location supplied on amendment.
Where an entry is submitted inland and is found to require amendment whilst at the frontier, it is the Submitting Trader who must make the amendment, not a Handling Agent (e.g. port agent), even where one has been nominated to handle the consignment whilst at the frontier.
The Entry may be identified using one of the following keys:
Declaration UCR/part and optional Supplementary Declaration indicator
The latest Movement Reference Number (MRN) for the entry;
Entry reference (EPU, Entry number, Date of Entry).
The same Declaration UCR and Part number can be used for both the PSA and the Supplementary Declaration. The Supplementary Declaration indicator is provided to enable you to identify in such cases when the Supplementary Declaration is to be amended.
When you have identified the Entry and specified the reason for amendment, the system checks that the Entry exists and is eligible for amendment (e.g. not terminated, not cancelled, not ready for information transfer to other systems), and, if so, displays it for amendment with screen layouts appropriate to the Entry type (i.e. as for IEFD or IECR).
The transaction is available via EDI and at the HCI but the facility to store is available only in the HCI context. Only the Submitting Trader is permitted to make amendments to a DTI Export Entry.
Traders may freely amend their declarations while pre-lodged (i.e. yet to come under Customs control at the Office of Export). Once legally accepted, an amendment may be automatically authorised by CHIEF or referred to Customs for approval. The criteria for this decision reflect not only the declared data, but may also take account of the movement history of the consignment.
An Entry can normally be amended until it is finalised (for example cancelled) or until the conditions for transferring information to other systems have been established (e.g. clearance from the Office of Export and initial departure from UK notified (or assumed) and no other conditions preventing transfer (no detained movements, no outstanding queries, no cancellation requested, no amendments requiring approval)). Note, however, that Export Entries with CAP Refund Claims of Type 12 or 14 cannot be amended after the Final Claim Line version has been sent. This is usually some time before the conditions for transfer to other Systems are established.
The declaration is re-processed as a result of amendment. If the consignment has yet to be given permission to progress from the Office of Export, then it may possibly become subject to further Customs checks. If permission has already been given, then it will not be revoked but the consignment may be impacted at a subsequent location.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 64 of 108
Version: 4.0
10.1.1 Detailed Considerations
All of the declaration details with the exception of key data, for example the CHIEF Entry Reference or the Declaration UCR, are available for amendment. If a declaration is made with the wrong reference the Entry must be cancelled and the declaration inserted again. Any change to the Master UCR notified by the declarant is ignored after initial submission as the consolidation in which the consignment resides is under handling agent control.
It is possible to append additional Items to all types of Export Entry, except C21 declarations. This is accomplished by using the ‘add segment’ function which is described in Reference [2]. It is not permitted to physically delete an Item once it has been committed. It may be marked as deleted by replacing the Commodity Code with the letters ‘DEL’. For processing purposes it ceases to exist, but its previous existence continues to be recorded for enquiry and audit purposes. It is possible also, to reinstate a deleted Item by replacing the ‘DEL’ with a valid Commodity Code.
On an Entry, the CPC may not be amended in such a way that the Customs Procedure Scheme Type for the CPC Series changes, as this could change the Entry Type.
If the data originated from a Full Export Declaration or a Simplified Declaration then credibility checking is performed as part of secondary validation (see Reference [4]). If any FEC challenges are identified you may resolve them in this transaction by confirming the data ‘correct as input’, or by amending the data. Such failures may have been identified during original acceptance, or during amendment of the Entry.
Once the Entry is valid and free of unresolved credibility failures, it becomes a new version of an accepted Entry, either pre-lodged if goods have not yet come under Customs control at the Office of Export or legally accepted if they have. Confirmation of the acceptance is provided to the user by the Acceptance screen for the corresponding Entry insert transaction.
Depending on the circumstances, several of the following reports are generated as a result of this transaction: X1, X2, X4, X7, P2, P7 (see Reference [4]).
10.2 Starting the Transaction
You may enter this transaction by typing the command code ‘AEXD’ on the command line. Due to the complexity of the parameter screen the ability to request amendment using command line parameters is not provided.
You may also enter this transaction as a downward selection from the LSTR transaction (see Reference [5]) of an Entry that was previously stored by AEXD.
This transaction is entered automatically if you have notified CHIEF of Goods Arrival using the transaction AEAL and the Entry then fails reprocessing.
10.3 Document Data
This section shows how the data for this transaction appears as a Document on your screen. As the screens closely resemble those for the relevant insert transaction, only the Parameter Input screen is shown in this section.
After you have applied all the amendments to the data from the declaration and visually checked them for accuracy you should validate or commit the data. It first undergoes validation and any errors found are reported for correction. If errors are found you may store the Entry for subsequent retrieval and correction, or you may correct the errors and validate or commit the data again.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 65 of 108
Version: 4.0
a. AEXD – Parameter Input screen ]TRADER-ROLE O AMEND EXPORT ENTRY CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU []*** Entry number [ ] Date [ / / ]
DUCR / MRN [ ] DUCR Part [ ] Supp Dec? [ ]
Reason for amendment
[a ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
C10059 End of Document
PARAM,STORE,RETURN [PARA]
10.4 Document Structure
The repeating segments for the Parameter Input screen are shown in the table below. The structure of the rest of the Document is the same for the corresponding insert transaction and reference should be made to IEFD, IESP, IELP, IECR or IESD for full details.
Seg. Level
Seg. Id.
Segment Description Min Segs in
Set
Max Segs in Set
Add’l Segs
1 a Reason for Amendment 1 5 1
10.5 Field Completion Rules
The field completion rules for the Amend Entry transaction are the same as the completion rules for the relevant Insert Transaction and reference should be made as appropriate to IEFD, IESP, IELP, IECR, IESD or IEXS.
The following table only includes the parameter fields within the Document identifying whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply.
Field Name (SAD Box) Optionality Cross-field Validation Checks
Entry number/Date O DUCR & DUCR Part & Supp Dec? / MRN
O
Reason for amendment M
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 66 of 108
Version: 4.0
10.6 Field Details
The field details for the Amend Entry transaction are substantially the same as the field details for the relevant Insert Transaction and reference should be made to IEFD, IESP, IELP, IECR, IESD or IEXS, as appropriate. The initial parameter field validation is shown below. If the parameters supplied identify an Entry with a status that permits processing by the transaction, the entry data is presented. The key data on the presentation is protected and may not be amended. The field descriptions in Section 3 include any amendment considerations.
Details of the Parameter screen fields are given here.
One and only one of the following must be supplied to identify the Entry:
CHIEF Entry Reference (Entry Number and Date);
Declaration UCR/Part
Movement Reference Number.
Entry The Entry number and Date together with your EPU number identify the Entry you wish to amend. The fields must not be supplied as well as Decln UCR/Part. Decln UCR/Part should normally be used.
number the number allocated to the form when it was lodged with Customs. It includes the check character.
Date the date that the form was lodged with Customs.
DUCR & Part & Supp Dec? / MRN
The UCR and part number or MRN that identify the Entry you wish to amend. This is the normal way of identifying an Entry when a Declaration UCR/Part were supplied on the declaration. The fields must not be supplied as well as Entry Number and Date.
DUCR The UCR (see Reference [4]).
DUCR Part
The optional part number and check character for the UCR. The check character should be entered to avoid undetected keying errors.
Supp Dec?
Indicates when set to “Y” that the entry identified by UCR and Part is a Supplementary Declaration. It is required to identify a Supplementary Declaration that has the same Declaration UCR/Part as an SFD.
MRN The Movement Reference Number for the Entry. It will be rejected if it is not the latest MRN recorded for the entry.
Reason for amendment
A free format textual reason for the amendment must be entered.
10.7 Cross-Field Validation Checks
For details of all cross-field validation refer to the appropriate Entry insert transaction.
END OF SECTION 10
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 67 of 108
Version: 4.0
11. AEAL – Notify Export Arrival
11.1 Business Description
This transaction is also available via EDI.
This transaction is intended for use at locations that are not controlled by an Inventory system. The transaction will not permit explicit arrival notification at inland locations (trader’s premises and Customs approved warehouses) as arrival of goods at inland locations is scheduled at the goods available time notified on the LCP declaration. You must operate in an Inventory role (advised by Customs), to notify arrival of consignments at their location. Such consignments may represent single declarations or consolidations.
Arrival is allowed provided the status of the consignment permits. In the case of a CHIEF declaration the conditions are not already finalised, is error-free and is not cancelled, detained or terminated or more than 5 months (152 days) have elapsed since legal acceptance. The latter condition allows time for the arrival to be progressed before the overall threshold of 6 months is reached for the declaration (see Reference [4] para 3.2.4 of for further details). Arrival can also be notified before a declaration is received by CHIEF and this transaction will record the arrival and await input of the declaration.
Movement Arrival Advices (S5) are produced for the Submitting Trader and Handling Agents who have requested declaration progress reports. Handling Agents and the Submitting Trader will receive a report when the consignment does not achieve permission to progress on arrival. An S5 may be produced for the Submitting Trader for exports that are subject to CAP refund and have been declared inland (see Reference[4]).
Arrival may be notified by one of the following keys:
a. for a single declaration by means of:
either the Declaration UCR, and (optional) Part No, or
CHIEF IES entry reference (comprising EPU, Entry No and Date of Entry) or
the latest Movement Reference Number (MRN) for the entry.
b. for a consolidation by means of the Master UCR.
Where arrival is notified before the declaration is received by CHIEF, the arrival notification must be made using the UCR (and optional Part No).
11.1.1 Arrival of an Individual Declaration (Declaration UCR)
If the arrival notified at this location is the first arrival (anywhere) of an individual declaration (i.e. the initial arrival for a pre-lodged entry), then the legal acceptance date-time of the entry is established and validation performed on the declaration details. Provided all details are valid, an Office of Export is established and the declaration is subjected to Profiles - both National and those defined for the Office of Export. If the outcome of the profile checks is satisfactory then immediate permission to progress from the Office of Export is granted. Otherwise, documentary or physical checks will be required before Customs can grant permission to progress. In the case of goods entered into control inland the permission to progress is delayed until the intended departure time declared by the Trader has arrived.
If the arrival is notified before the declaration is received by CHIEF, the legal acceptance date-time of the entry is established when the declaration is received by CHIEF.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 68 of 108
Version: 4.0
Further arrivals can be at the Office of Export or other locations (Office of Exit). Multiple arrivals at a location should only occur for a split consignment. Special processing in CHIEF simplifies the handling by Customs of a split consignment at the Office of Export by relating the further movements to the Office of Export movement while it is awaiting permission to progress. Refer to Reference [4] for further details. If the arrival notified at this location is an arrival subsequent to the first arrival at an Office of Exit the declaration is re-processed, and is re-profiled using both National Profiles and those defined for the current location.
11.1.2 Arrival of a Consolidation (Master UCR)
This transaction also enables the user to notify CHIEF that a consolidation (identified by Master UCR), has arrived. CHIEF responds immediately to acknowledge a valid request but this does not advise the status of each individual declaration within the consolidation. Separately, and via a background process, CHIEF establishes the Route for each of the declarations within the consolidation(s), navigating any hierarchy of consolidations as required. To identify the status of individual declarations, the user will need to use transaction LMOV (see Reference [4]) to view their status. For each individual declaration achieving permission to progress, report X6 will be produced (see Reference [4]).
11.2 Starting the Transaction
This transaction can be invoked by typing the command code “AEAL” on the command line. Other information (to bypass the initial parameter input screen) can be provided as parameters, as shown in the following examples:
“AEAL” Causes the parameter screen to be displayed.
“AEAL 3GB112233431000-3BA059LN, 002” Causes details of the Export Entry having a Declaration UCR of 3GB112233431000-
3BA059LN and Part 002 to be displayed for arrival assuming it exists.
“AEAL 09GB01X00008001019” Causes details of the Export Entry having a Movement Reference Number of
09GB01X00008001019 to be displayed for arrival, assuming it exists.
“AEAL GB/CNS1-AJWQ1FAW3300100,002” Causes details of the consolidation identified under UCR
GB/CNS1-AJWQ1FAW3300100 to be displayed for arrival assuming it exists.
“AEAL ,,123,A12345A,12032001” Causes Entry Number A12345A input to EPU 123 on 12th March 2001 to be displayed
for arrival, assuming it exists.
11.3 Document Data
This section shows how the data for this transaction appears as a Document on the screen.
After the completion of the initial parameter screen, the Document is displayed, showing existing information and allowing the input of the Goods Location, Shed, Movement Reference Number, Master UCR and Intended Transport Details (which may be available when notifying arrival at the Office of Exit).
Confirmation of the arrival notification is provided by an Acceptance screen (generated by AEAL) as shown.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 69 of 108
Version: 4.0
Examples of the Acceptance Screen are shown to reflect arrival of a single declaration and arrival of a consolidation. Where a single declaration is arrived examples are shown to reflect the situation when permission to progress is immediately granted and when Customs action is required before the goods can progress.
11.3.1 Initial Parameter Screen
a. AEAL - Initial Parameter input screen ]TRADER-ROLE O NOTIFY EXPORT ARRIVAL CHIEF/CIES 01/10/09 12:15
INVMSG:1P
DUCR / MRN / MUCR [ ] DUCR Part [ ]
EPU [ ] Entry Number [ ] Date [ / / ]
C10059 End of Document
PARAM,RETURN [PARA]
11.3.2 Input and Acceptance Screens for Arrival of a Single Declaration
a. AEAL – Arrival Details input screen ]TRADER-ROLE O NOTIFY EXPORT ARRIVAL CHIEF/CIES 01/10/12:15
INVMSG:1P
UCR []*********************************** Part ****
Entry Ref EPU []*** Number []******* Date **/**/****
Arrival Date/Time. . [ / / ] [ : ]
Locn Goods (30). . . [ ] Shed [ ]
Movement Ref . . . . [ ]
Link to Master . . . [ ]
Intended Transport Details
Trpt Id (21) . . . . [ ]
Nat of Trpt (21) . . [ ]
Mode of Trpt (25). . [ ]
C10043 Declaration UCR or Entry to be processed
VALIDATE,COMMIT,ABORT [VALI]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 70 of 108
Version: 4.0
b. AEAL - Acceptance of Goods Arrival - Permission to Progress Granted ]TRADER-ROLE O NOTIFY EXPORT ARRIVAL CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []*********************************** Part ****
Entry Ref EPU []*** Number []******* Date **/**/****
Entry legally accepted on **/**/**** at **:**
Arrival Date/Time. . **/**/**** **:**
Locn Goods (30). . .[]*** Shed []***
Movement Ref . . . . *************************
Link to Master . . .[]***********************************
Intended Transport Details
Trpt Id (21) . . . . ***************************
Nat of Trpt (21) . .[]**
Mode of Trpt (25). . **
Route ** Immediate permission to progress granted on **/**/**** at **:**
C10004 Data successfully committed
AEAL,ABORT,PRINT [AEAL]
c. AEAL - Acceptance of Goods Arrival - Permission to Progress NOT Granted ]TRADER-ROLE O NOTIFY EXPORT ARRIVAL CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []*********************************** Part ****
Entry Ref EPU []*** Number []******* Date **/**/****
Entry legally accepted on **/**/**** at **:**
Arrival Date/Time. . **/**/**** **:**
Locn Goods (30). . .[]*** Shed []***
Movement Ref . . . . *************************
Link to Master . . .[]***********************************
Intended Transport Details
Trpt Id (21) . . . . ***************************
Nat of Trpt (21) . .[]**
Mode of Trpt (25). . **
Route ** Permission to progress not granted to this entry
C10004 Data successfully committed
AEAL,ABORT,PRINT [AEAL]
Where arrival notification occurs before the declaration is received by CHIEF certain fields on the above screen will not be completed (e.g. CHIEF entry reference, legal acceptance date).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 71 of 108
Version: 4.0
11.3.3 Input and Acceptance Screens for Arrival of a Consolidation
a. AEAL - Arrival Details input screen ]TRADER-ROLE O NOTIFY EXPORT ARRIVAL CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []************************** ********
Arrival Date/Time. . [ / / ] [ : ]
Locn Goods (30). . . [ ] Shed [ ]
Movement Ref . . . . [ ]
Link to Master . . . [ ]
Intended Transport Details
Trpt Id (21) . . . . [ ]
Nat of Trpt (21) . . [ ]
Mode of Trpt (25). . [ ]
C10042 Master UCR (consolidation) to be processed
VALIDATE,COMMIT,ABORT [VALI]
b. AEAL - Acceptance of Goods Arrival ]TRADER-ROLE O NOTIFY EXPORT ARRIVAL 01/10/09 12:15
INVMSG:1P
UCR []***********************************
Arrival Date/Time. . **/**/**** **:**
Locn Goods (30). . .[]*** Shed []***
Movement Ref . . . . *************************
Link to Master . . .[]***********************************
Intended Transport Details
Trpt Id (21) . . . . ***************************
Nat of Trpt (21) . .[]**
Mode of Trpt (25). . **
C10044 Consolidation processing accepted
AEAL,ABORT,PRINT [AEAL]
11.4 Document Structure
Segments cannot be inserted or deleted in this Document, and hence a segment table is not necessary.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 72 of 108
Version: 4.0
11.5 Field Completion Rules
This section shows whether each input field within the Document is optional (O) or mandatory (M), for each possible input phase, where optional may include conditional absence.
Field Name (SAD Box) Optionality DUCR / MRN / MUCR O Part O EPU O Entry Number O Date O Arrival Date/Time O Locn Goods (30) M Shed O Movement Ref O Link to Master O Trpt Id (21) O Nat of Trpt (21) O Mode of Trpt (25) O
11.6 Field Details
This section of the Guide gives, for each field on the Document used by AEAL, details of its business use and the data that should be entered.
One and only one of the following must be supplied to identify the entry:
UCR as Declaration UCR (including optional Part No) to identify an individual entry;
MRN to identify an individual entry;
UCR as Master UCR to identify a consolidation;
CHIEF entry reference (EPU, Entry Number and Date).
DUCR / MRN / MUCR
Provides a reference to an individual entry or consolidation (which may exist) using one of three types of identifier:
Declaration Unique Consignment Reference. The UCR for an individual entry.
Movement Reference Number. The latest MRN for an individual entry. It will be rejected if it is not the latest MRN recorded for the entry.
Master Unique Consignment Reference. The UCR for a consolidation. If input, it should contain the reference allocated to the goods movement by the Trader (maximum 35 characters).
This field may be supplied, with other key information, as a parameter on the command line.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 73 of 108
Version: 4.0
DUCR Part Optionally completed for a DUCR when more than one declaration is made to cover the goods identified by the same UCR and is supplied only when the declared UCR represents an individual Entry (Declaration UCR). The Part is made up of (up to) three (numeric) digits, and the item may also contain a one-character alphabetic check character, covering the UCR and any Part.
EPU This field (which identifies the Entry Processing Unit associated with the inputting role) is part of the (alternative) key to an Entry requiring processing, and is supplied together with the Entry Number and Date.
Entry Number This field is part of the (alternative) key. It includes the check character. When supplied, with EPU and Date, it is used to identify the Entry requiring processing. (This field may be supplied, with other key information, as a parameter on the command line). If it then identifies an Entry with a status that permits processing by the transaction, the parameter screen is bypassed.
Date This field is also part of the (alternative) key and must be completed (with the Entry Number and EPU) to identify the Entry to be processed.
Arrival Date/Time
Optionally completed with the Date and Time at which the goods arrived. To allow for a difference between the CHIEF and trade system clocks, the Arrival Date/Time can be 10 minutes ahead of CHIEF time. Defaults to ‘now’.
Locn Goods (30)
Location of Goods. Must be completed with the code representing the place where the goods are situated.
Shed Shed Identity. Optionally completed with a Transit Shed code when the Location of Goods needs to be more fully specified. The shed must be known to CHIEF.
Movement Ref Optionally completed with the Movement Reference Number of a particular split load which is the subject of the arrival (see Reference [4] para 3.6.1).
Link to Master Any input into this field is ignored. At previous releases this field was completed with the Master UCR for a consolidation with which the consignment is to be associated.
Trpt Id (21) Identity of Transport. Optionally completed with the intended transport identity if known on arrival (at the Office of Exit).
Nat of Trpt (21) Nationality of Transport. Optionally completed with a country code for the Active means of Transport if known on arrival (at the Office of Exit).
Mode of Trpt (25)
Border Mode of Transport. Optionally completed with the transport code for the Active means of Transport by which the goods will be exported if known on arrival (at the Office of Exit).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 74 of 108
Version: 4.0
11.7 Cross-Field Validation Checks
1. DUCR(& DUCR Part)/MRN/MUCR, CHIEF Entry reference (EPU, Entry Number, Date of Entry)
To identify the Export entry, one of the following must be supplied: DUCR & optional DUCR Part, MRN, MUCR; or CHIEF Entry reference (EPU, Entry Number, Date of Entry).
2. Locn Goods (30), Shed (30)
Shed must be valid for the goods location.
END OF SECTION 11
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 75 of 108
Version: 4.0
12. ACST – Change Consolidation Status
12.1 Business Description
This transaction is also available in EDI.
This transaction enables a Trader acting in the capacity of Exporter or Agent to shut a consolidation. Such Traders do not require the functionality provided by the Associate Export Consignments transaction to associate or disassociate declarations or consolidations. The identity of the consolidation is provided through the input of a Master UCR and such a consolidation must be ‘open’.
Once Shut, goods may no longer be declared directly into the consolidation by reference to its Master UCR.
12.2 Starting the Transaction
This transaction can be invoked by typing the command code “ACST” on the command line. Other information (to bypass the initial parameter input screen) can be provided as parameters, as shown in the following examples:
“ACST” Causes the parameter screen to be displayed.
“ACST GB/CNS1-AJWQ1FAW3300100” Causes the consolidation identified as GB/CNS1-AJWQ1FAW3300100 to be marked
as ‘shut’.
12.3 Document Data
This section shows how the data for the transaction appears as a Document on the screen. After the initial parameter screen has been completed to identify the reference to an existing consolidation, the document is displayed confirming the keyed information.
a. ACST – Initial Parameter input screen ]TRADER-ROLE O CHANGE CONSOLIDATION STATUS CHIEF/CIES 01/10/09 12:15
INVMSG:1P
Master UCR. . . [ ]
C10059 End of Document
COMMIT,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 76 of 108
Version: 4.0
b. ACST – Confirmation screen ]TRADER-ROLE O CHANGE CONSOLIDATION STATUS CHIEF/CIES 01/10/09 12:15
INVMSG:1P
Master UCR. . .[]***********************************
The Master UCR has been closed
C10004 Data Successfully committed
RETURN,PRINT [ ]
12.4 Document Structure
Segments cannot be inserted or deleted in this Document, and hence a segment table is not necessary.
12.5 Field Completion Rules
This section shows whether each input field within the document is optional (O) or mandatory (M) for each possible input phase.
Field Name (SAD Box) Optionality Master UCR M
12.6 Field Details
This section of the Guide gives details of the business use and the data that should be entered into each field on the Document used by ACST.
Master UCR Completed with a Master UCR identifying the consolidation. The consolidation identified must be ‘open’.
12.7 Cross-Field Validation Checks
None.
END OF SECTION 12
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 77 of 108
Version: 4.0
13. AEAC – Maintain Export Consolidation
13.1 Business Description
This transaction enables a Trader to perform the following operations on Export consignments:
Shut a consolidation;
Associate with a consolidation a series of consolidations and/or individual declarations (up to a maximum depth of 8);
Disassociate a consolidation or individual declaration from the owning consolidation.
A single invocation of the transaction permits both association and shut operations. Alternatively the transaction allows a single disassociate operation.
The transaction identifies the owning consolidation on which an associate or shut operation is effected by means of the field entitled Master UCR. Individual declarations or subordinate consolidations for the associate or disassociate operations are identified by means of the field entitled UCRs. Where UCRs is used to identify an individual declaration an optional Part number field is available to uniquely identify the consignment.
This transaction is also available in EDI with some minor differences (e.g. the EDI transaction permits association of a single UCR representing one individual declaration or consolidation with an owning consolidation). Refer to Reference [6] for full details.
13.1.1 Shutting a Consolidation
A consolidation is created in an ‘open’ state when it is first referenced either on a declaration, an arrival, anticipated arrival or through the association of a Master UCR with Declaration UCRs (see Reference [4] para 3.6.1). This transaction will shut a nominated Master UCR when a Shut Master action is requested. Once Shut, goods may no longer be declared directly into the consolidation by reference to its Master UCR.
13.1.2 Associating Consignments with a Consolidation
A Trader is able to associate with a specified consolidation up to 100 individual declarations or consolidations. Such declarations may not be finalised (see Reference [4] para 3.2.4) or more than 6 months elapsed since legal acceptance. The owning consolidation may be created (if not already known to CHIEF) or amended as a result of this transaction. An explicit split movement for a consignment (Movement reference) cannot be consolidated.
An individual declaration or consolidation can only reside in one (owning) consolidation at a time. Although the facility to associate an individual declaration with a consolidation is provided at time of declaration (see Sections 4, 5, 6 and 7), the Submitting Trader or Consolidator can only adjust the association until the consignment is both shut and arrived by an Inventory system.
Thereafter, only a user associated with the Inventory system (e.g. where the user is directly associated through session variable INVY-SYS-ID with the arriving Inventory System) can change the consolidation. Note that only the first 3 characters of the session variable is considered for the match.
Furthermore, if the Inventory System is so configured, a check is made that the role requesting the association change to an arrived shut Master either created a movement for the Master, or is the nominated agent role for such a movement (as specified on the arrival message).
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 78 of 108
Version: 4.0
13.1.3 Disassociation of a Consignment from its Owning Consolidation
Disassociation of an individual declaration or consolidation from its owner is achieved by specifying just the UCR / Part of the declaration/consolidation, which must exist and currently associated with a consolidation.
13.2 Starting the Transaction
This transaction is invoked by typing the command code “AEAC” on the command line. In view of the complexity and optional nature of the parameters the facility to request the transaction using command line parameters is not advised.
13.3 Document Data
This section shows how the data for the transaction appears as a Document on the screen. After the initial parameter screen has been completed to identify the reference to an existing individual declaration or consolidation, the document is displayed confirming the keyed information.
a. AEAC - Initial Parameter input screen ]TRADER-ROLE O MAINTAIN EXPORT CONSOLIDATION CHIEF/CIES 01/10/09 12:15
MAST:1P
Master UCR [ ] Shut Master? [ ]
UCRs to Associate Part
[a ] [a ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [ ]
UCR to Disassociate: [ ] Part [ ]
C10059 End of Document
COMMIT,RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 79 of 108
Version: 4.0
b. AEAC – Confirmation screen for action - Association of UCRs with Master ]TRADER-ROLE O MAINTAIN EXPORT CONSOLIDATION CHIEF/CIES 01/10/09 12:15
ACQEDET:1P
Master UCR []*********************************** Shut Master? *
UCRs to Associate: []*********************************** Part ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
[]*********************************** ****
The specified UCRs have been associated with the Master UCR
C10004 Data Successfully committed
RETURN,PRINT [ ]
c. AEAC – Confirmation screen for action - Disassociation of UCR from Master
]TRADER-ROLE O MAINTAIN EXPORT CONSOLIDATION CHIEF/CIES 01/10/09 12:15
ACQEDET:1P
UCR to Disassociate:[]*********************************** Part ****
The UCR / Part has been disassociated from ***********************************
C10004 Data Successfully committed
RETURN,PRINT [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 80 of 108
Version: 4.0
d. AEAC – Confirmation screen for action - Shut Master ]TRADER-ROLE O MAINTAIN EXPORT CONSOLIDATION CHIEF/CIES 01/10/09 12:15
ACQEDET:1P
Master UCR []*********************************** Shut Master? Y
The Master UCR has been shut
C10004 Data Successfully committed
RETURN,PRINT [ ]
13.4 Document Structure
A repeating segment is available for the specification of UCRs to be associated with the Master.
Seg. Level
Seg. Id.
Segment Description Min Segs in Set
Max Segs in Set
Add’l Segs
1 a UCRs to Associate 1 100 See Note a
10
Note:
a. At least one UCR must be specified for an association. Should you wish to request additional segments for the specification of UCRs, then your cursor must be placed on either the UCR or the Part number field and ‘Add segment’ requested.
13.5 Field Completion Rules
This section shows whether each input field within the document is optional (O) or mandatory (M) for each possible action required.
Field Name (SAD Box) Optionality for Shut Master
(Note a)
Optionality for Associate (Note a)
Optionality for Disassociate
Master UCR M M Shut Master M UCRs to Associate: UCR Part
M O
UCR to Disassociate: UCR Part
M O
Note:
a. The transaction permits both association and shut functions in a single invocation of the transaction.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 81 of 108
Version: 4.0
13.6 Field Details
This section of the Guide gives details of the business use and the data that should be entered into each field on the Document used by AEAC.
Master UCR Must be completed with a Master UCR of a consolidation for the Shut or Associate actions.
Shut Master? Must be completed with Y to request shutting of the specified Master UCR. The consolidation must not already be shut.
UCRs to Associate: UCR to Disassociate:
UCR Completed to identify either an individual declaration or consolidation as a subject of the association (or disassociation). The individual declaration or consolidation must already exist.
For an associate action a number of UCRs may be specified with the (owning) Master UCR. The declaration identified for association may not be finalised or more than 6 months elapsed from the date of legal acceptance. For a disassociate action only the UCR for disassociation is specified.
Part Optionally completed when the subject of the association (or disassociation) is an individual declaration (see UCR). A Part is required when more than one declaration using the same Declaration UCR has been made to identify particular goods. The Part is made of up to three (numeric) digits, and may also contain a one-character alphabetic check character, covering the UCR and Part.
13.7 Cross-Field Validation Checks
One of the following combinations of fields are permitted:
a. Master UCR and either Shut Master and/or at least one UCR for Associate.
b. UCR for Disassociate.
Note. For combination b, only the UCR for Disassociate (either Declaration UCR/Part or Master UCR) must be specified.
END OF SECTION 13
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 82 of 108
Version: 4.0
14. AEDL – Notify Export Departure
14.1 Business Description
This transaction is also available via EDI.
This transaction allows notification to be given that goods associated with an Export declaration have departed from the UK or are departed from this location to another location.
A Departure from the UK is indicated when border transport details are supplied. Absence of transport details indicates the goods are departed from this location to another within the UK and requires confirmation on the screen.
When the goods depart from the UK, the effect of this transaction can be to place the entry in a state where, if no further departures from the UK are notified, it will eventually become finalised (i.e. no further action will be allowed). On initial departure from the UK, if the entry meets the following conditions, it also causes Licence amounts which are already recorded as pending attributions to become actual attributions:
Clearance (i.e. Permission to progress from the Office of Export) granted;
No stored amendment is outstanding;
No queries outstanding;
No goods are detained;
No outstanding cancellation request.
If required, report S8 - Movement Departure Advice is also produced (see Reference [4]).
The transaction operates on all movements associated with the requested declaration or consolidation which have been granted permission to progress and are situated at the nominated Place of Loading. If the Place of Loading is qualified by a Shed then only the relevant movements at that Shed are departed. If a Shed is not supplied then all relevant movements at the location, regardless of shed, are departed. Where goods are departed to another location the transaction will be permitted provided there are movements for the nominated Place of Loading (with permission to progress).
Details of the entries where inconsistencies are detected (e.g. departure notified before permission to progress is granted from the Office of Export) will be logged on a regular report destined for Customs.
Departure of a single consignment may be notified by one of the following keys:
Declaration Unique Consignment Reference (UCR), and (optional) Part;
The latest Movement Reference Number (MRN) for the entry;
CHIEF IES entry reference (comprising EPU, Entry No and Date of Entry).
The declaration identified must exist and must not be finalised (see Reference [4] para 3.2.5). In addition, departure for a declaration where more than 6 months have elapsed since legal acceptance will be rejected.
Departure of a consolidation may be notified via:
Master UCR.
Where the processing of the consolidation detects a declaration which is finalised (or where more than 6 months have elapsed since legal acceptance) the departure of the declaration will not be recorded. Instead such events will be logged on a regular report destined for Customs.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 83 of 108
Version: 4.0
14.2 Starting the Transaction
The user may enter this transaction by typing the command code “AEDL” on the command line. Other information (to bypass the initial parameter input screen) can be provided as parameters, as shown in the following examples:
“AEDL” Causes the parameter screen to be displayed.
“AEDL 3GB112233431000-3BA059LN,00” Causes details of the Export Entry having a Declaration UCR of 3GB112233431000-
3BA059LN and Part 002 to be displayed for departure assuming it exists.
“AEDL 09GB01X00008001019” Causes details of the Export Entry having a Movement Reference Number of
09GB01X00008001019 to be displayed for departure, assuming it exists.
“AEDL ,,123,A12345A,12032001” Causes details of Entry Number A12345A input to EPU 123 on 12th March 2001 to be
displayed for departure, assuming it exists.
“AEDL GB/CNS1-AJWQ1FAW3300100” Causes details of consolidation identified by Master UCR
GB/CNS1-AJWQ1FAW3300100 to be displayed for departure, assuming it exists.
14.3 Document Data
This section shows how the data for this transaction appears as a Document on the screen.
The input screen should be completed to identify the Entry for which departure needs to be notified to the system.
14.3.1 Initial Parameter Screen
a. AEDL - Initial Parameter input screen ]TRADER-ROLE O NOTIFY EXPORT DEPARTURE CHIEF/CIES 01/10/09 12:15
INVMSG:1P
DUCR / MRN / MUCR [ ] DUCR Part [ ]
EPU [ ] Entry Number [ ] Date [ / / ]
C10059 End of Document
DISPLAY, RETURN [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 84 of 108
Version: 4.0
14.3.2 Input and Acceptance Screens for Departure of a Single Declaration
a. AEDL - Details input screen (Single Declaration) ]TRADER-ROLE O NOTIFY EXPORT DEPARTURE CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []*********************************** Part ****
Entry Ref EPU []*** Number []******* Date **/**/****
Date of Export . . . . . [ / / ]
Place of Loading (27) [ ] Shed [ ]
Where Transport details are not completed please confirm these goods are no
Longer being exported or will be exported from another UK location by entering
‘Y’ in the confirmation field. If goods have departed the UK complete all
Transport details otherwise official evidence will not support VAT zero rating
(omit confirmation field or enter ‘N’).
Border Transport Details
Trpt Id (21) . . . . . . [ ]
Nat of Trpt (21) . . . . [ ]
Mode of Trpt (25). . . . [ ]
Confirm return of goods . [ ]
C10043 Declaration UCR or Entry to be processed
VALIDATE,COMMIT,ABORT [VALI]
b. AEDL - Acceptance of Departure ]TRADER-ROLE O NOTIFY EXPORT DEPARTURE CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []*********************************** Part ****
Entry Ref EPU []*** Number []******* Date **/**/****
Date of Export . . . . . **/**/****
Place of Loading (27) []*** Shed []***
Where Transport details are not completed please confirm these goods are no
Longer being exported or will be exported from another UK location by entering
‘Y’ in the confirmation field. If goods have departed the UK complete all
Transport details otherwise official evidence will not support VAT zero rating
(omit confirmation field or enter ‘N’).
Border Transport Details
Trpt Id (21) . . . . . . ***************************
Nat of Trpt (21) . . . .[]***
Mode of Trpt (25). . . . **
Confirm return of goods . *
C10004 Data Successfully committed
RETURN,PRINT [RETU]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 85 of 108
Version: 4.0
14.3.3 Input and Acceptance Screens for Departure of a Consolidation
a. AEDL - Details input screen (consolidation) ]TRADER-ROLE O NOTIFY EXPORT DEPARTURE CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []***********************************
Date of Export . . . . . [ / / ]
Place of Loading (27) [ ] Shed [ ]
Where Transport details are not completed please confirm these goods are no
Longer being exported or will be exported from another UK location by entering
‘Y’ in the confirmation field. If goods have departed the UK complete all
Transport details otherwise official evidence will not support VAT zero rating
(omit confirmation field or enter ‘N’).
Border Transport Details
Trpt Id (21) . . . . . . [ ]
Nat of Trpt (21) . . . . [ ]
Mode of Trpt (25). . . . [ ]
Confirm return of goods . [ ]
C10042 Master UCR (consolidation) to be processed
VALIDATE,COMMIT,ABORT [VALI]
b. AEDL - Acceptance of Departure (consolidation) ]TRADER-ROLE O NOTIFY EXPORT DEPARTURE CHIEF/CIES 01/10/09 12:15
INVMSG:1P
UCR []***********************************
Date of Export . . . . . **/**/****
Place of Loading (27) []*** Shed []***
Where Transport details are not completed please confirm these goods are no
Longer being exported or will be exported from another UK location by entering
‘Y’ in the confirmation field. If goods have departed the UK complete all
Transport details otherwise official evidence will not support VAT zero rating
(omit confirmation field or enter ‘N’).
Border Transport Details
Trpt Id (21) . . . . . . ***************************
Nat of Trpt (21) . . . .[]***
Mode of Trpt (25). . . . **
Confirm return of goods . *
C10044 Consolidation processing accepted
RETURN,PRINT [RETU]
14.4 Document Data
You cannot insert or delete segments in this Document and hence a segment table is not necessary.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 86 of 108
Version: 4.0
14.5 Field Completion Rules
This section shows you whether each input field within the Document is optional (O) or mandatory (M) for each possible input phase, where optional may include conditional absence.
Field Name (SAD Box) Optionality Cross-field Validation Checks
DUCR & DUCR Part / MRN / MUCR,
O See 14.7 below
EPU, Entry Number, Date O See 14.7 below Date of Export O Place of Loading (27) M See 14.7 below Shed O See 14.7 below Trpt Id (21) O See 14.7 below Nat of Trpt (21) O See 14.7 below Mode of Trpt (25) O See 14.7 below Confirm return of goods O See 14.7 below
14.6 Field Details
This section of the Guide gives you, for each field on the Document used by AEDL, details of its business use and the data that you should enter.
DUCR / MRN / MUCR
References an individual entry or consolidation using one of three types of identifier –
Declaration Unique Consignment Reference. The UCR for an individual entry.
Movement Reference Number. The latest MRN for an individual entry. It will be rejected if it is not the latest MRN recorded for the entry.
Master Unique Consignment Reference. The UCR for a consolidation. If input, it should contain the reference allocated to the goods movement by the Trader (maximum 35 characters).
This field may be supplied, with other key information, as a parameter on the command line. If it then identifies an Entry or consolidation with a status that permits processing by the transaction, the parameter screen is bypassed.
DUCR Part Optionally completed. Where a Declaration UCR has been supplied any Declaration UCR Part allocated to the declaration must also be supplied. The Part is made up of (up to) three (numeric) digits, and the item may also contain a one-character alphabetic check character, covering the UCR and any Part.
EPU This field (which identifies the Entry Processing Unit associated with the inputting role) is part of the (alternative) key to an Entry requiring processing, and must be completed together with the Entry Number and Date.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 87 of 108
Version: 4.0
Entry Number This field is part of the (alternative) key. It includes the check character. When supplied, with EPU and Date, it is used to identify the Entry requiring processing. (This field may be supplied, with other key information, as a parameter on the command line). If it then identifies an Entry with a status that permits processing by the transaction, the parameter screen is bypassed.
Date This field is also part of the (alternative) key and must be completed (with the Entry Number and EPU) to identify the Entry to be processed.
Date of Export If no input is provided the current date is supplied by the system. Any input must not be in the future.
Place of Loading (27)
Place of Loading. Must be completed with the identity of the place of departure of the vessel or flight or other transport on which the goods left.
Shed (30) Shed Identity. Optionally completed with a Transit Shed code when the departure is limited to goods that were situated at a Shed. Only eligible goods situated at the declared Shed are departed.
The shed must be known to CHIEF and be valid for the location which it qualifies.
Border Transport Details
The following three fields must all be supplied to give details of the means of transport on departure from the UK. None of the fields are supplied to notify departure inland.
Trpt Id (21) Identity of Transport. Optionally completed with the transport identity of the Active means of Transport by which the goods are exported.
Nat of Trpt (21) Nationality of Transport. Optionally completed with a country code for the Active means of Transport by which the goods are exported.
Mode of Trpt (25)
Border Mode of Transport. Optionally completed with the transport code for the Active means of Transport by which the goods are exported.
Confirm return of goods
Must be set to ‘Y’ when notifying departure inland. Set to ‘N’ or leave blank when notifying departure from the UK.
14.7 Cross-Field Validation Checks
1. UCR(& DUCR Part), CHIEF entry reference (EPU, Entry Number, Date of Entry)
To identify the Export entry or consolidation, one of the following must be supplied;
DUCR (DUCR Part), MRN, MUCR; or CHIEF Entry reference (EPU, Entry Number, Date of Entry).
2. Place of Loading (27), Shed (30)
Shed must be valid for the Place of Loading.
3. Trpt Id (21), Nat of Trpt (21), Mode of Trpt(25)
To notify departure from the UK, Trpt Id (21) and Mode of Trpt(25) must be supplied along with Nat of Trpt(21) except for Modes of Transport 2, 5 and 7. None of the fields are supplied to notify departure inland.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 88 of 108
Version: 4.0
4. Trpt Id (21), Nat of Trpt (21), Mode of Trpt (25), Confirm return of goods.
If transport fields supplied then the ‘Confirm’ field must be ‘N’ or left blank. If transport fields not supplied then the ‘Confirm’ field must be set to ‘Y’.
END OF SECTION 14
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 89 of 108
Version: 4.0
15. DEVD – Display Entry Version Details
DEVD allows you to display declarations.
15.1 Business Description
This transaction is also available via EDI to Traders permitted full access to the entry via message DEV (i.e. the Submitting Trader). Only the Handling Agent view is available using EDI message DEM. See Reference [6] for further details.
This transaction allows details of the current, or a previous, version of the data relating to an Entry to be displayed. Only one version may be examined at a time. If the last attempt to amend an Entry was concluded by a ‘store’ command, then the latest version is the stored data, and the error messages relating to the errors it contains are also displayed. Where a version other than the latest is required, access via LIEV (List Entry Versions, see Reference [4]) simplifies the task of selecting the correct version. The LIEV transaction can be invoked by downward selection on an Entry Number displayed by other transactions. Handling Agents (i.e. those based at other locations) will have access to a subset of Entry Version Header level information only, as can be seen in Section 14.3 below.
An Entry may be displayed using any one of the following keys:
Entry reference (EPU, Entry number, Date of Entry);
CHIEF Entry key;
Declaration UCR/part and optional Supplementary Declaration indicator
the latest Movement Reference Number (MRN) for the entry.
You can access Entries input at EPUs other than the EPU to which you belong, subject to your access rights.
Without any other qualification the latest version of the entry will be displayed. Where a particular generation is required either a numeric generation identifier or Creation date/time may be supplied.
Once the required Entry has been identified you are presented with a Summary screen showing what other presentations are available. You may switch between presentations directly without going via the Summary screen by typing an ‘escape sequence’ (see Reference [4]).
In some situations the effect of the escape sequence depends on the position of the cursor. Except for a Customs Clearance Request (C21) the Summary screen displays a list of the Item numbers that exist for the Entry. To review details relating to an Item you should place the cursor on the required Item number and then select an alternative presentation. This results in the display of that Item in the selected presentation if it is appropriate.
Downward selection on an Entry Number invokes the LIEV (List Entry Versions) transaction (see Reference [4]).
Reporting of route
Normally the display of the allocated route on the Generated Data screens will show a positive route. Where however the route is not yet known, for example because another system or a CAP refund is being claimed, route 0 is reported (see Reference [4] para 3.7.4).
Reporting of Master UCR
The Master UCR displayed within option 4 is the identifier of the consolidation by which the consignment was arrived or the Master UCR declared by the Submitting Trader.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 90 of 108
Version: 4.0
15.2 Starting the Transaction
This transaction may be invoked by downward selection from, for example, LIEV or LMOV (see Reference [4]), in which case the Parameter Input screen is bypassed.
The DEVD transaction is invoked directly by typing the command code optionally followed by the required parameters on the command line, for example:
“DEVD” Causes the Parameter Input screen to be displayed. “DEVD 123,A12345A,010707” Causes the Summary screen for the latest version of Entry number A12345A input to
EPU 123 on 1st July 2007 to be displayed. “DEVD ,A12345A,010707” Causes the Summary screen for the latest version of Entry number A12345A input to
your own EPU on 1st July 2007 to be displayed. “DEVD 123,A12345A,010707,020707,1508” Causes the Summary screen for the version that was current at 3:08pm on 2nd July
2007 of Entry number A12345A input to EPU 123 on 1st July 2007 to be displayed. “DEVD ,,,,,,23453456” Causes the Summary screen for the latest version of the Entry with an Entry Key of
23453456 to be displayed. “DEVD ,,,020707,1508,,23453456” Causes the Summary screen for version that was current at 3:08pm on 2nd July 2007
of the Entry with an Entry Key of 23453456 to be displayed. “DEVD ,,,,,,, 02GB123456789001-REF123(01), 002” Causes the Summary screen for the latest version of the Export Entry carrying a
Declaration UCR “02GB123456789001-REF123(01)” and Part “002” to be displayed. Note, if there is a PSA and a Supplementary Declaration with the same Declaration UCR/Part the PSA is displayed.
“DEVD ,,,,,,, 09GB01X00008001019” Causes the Summary screen for the latest version of the Export Entry carrying a
Movement Reference Number (MRN) to be displayed. “DEVD ,,,02072007,1508,,, 2GB123456789001-REF123(01), 002,Y” Causes the Summary screen for the latest version at 3:08pm on 2nd July 2007 of the
Supplementary Declaration carrying a Declaration UCR of “2GB123456789001-REF123(01)” and Part “002” to be displayed.
In all cases where a valid parameter (that identifies an existing Entry) is provided, the initial parameter input screen is bypassed. Normally, a user would wish to omit inputting the EPU number – thereby enabling the system to take its own EPU as default.
“Movement No” is provided as a parameter to support downward selection from LMOV. It is not expected that you will use this parameter so it is not included in any of the above examples.
15.3 Document Data
This section shows how the data for this transaction appears as a Document on your screen. The transaction offers a number of display options depending on the Entry type and the declared data with restrictions for a Handling Agent request. Screen layouts are shown in sub-sections for Parameter Input, Summary Details and for each display option.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 91 of 108
Version: 4.0
Except for the Data as Input screen (see 14.3.5 below), the C21 screens follow a similar format to the SAD screens and are not reproduced here.
After the initial parameter screen has been completed (identifying the Entry version), the Document is displayed showing existing information in the format appropriate to the Entry type.
15.3.1 Initial Parameter Screen – All Entries
a. DEVD – Initial Parameter input screen ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADKEY:1P
EPU [ ] Entry Number [ ] Date [ / / ]
Created On [ / / ] At [ : ]
Generation Id [ ]
Or (if Entry No. not allocated)
Entry Key [ ]
DUCR / MRN [ ] DUCR Part [ ] Supp Dec? [ ]
Movement No [ ]
C10059 End of Document
DISPLAY,RETURN [ ]
15.3.2 Summary Screens ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADHDRV:1H
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
VERSION SUMMARY Prelodged on **/**/**** at **:**
Accepted on **/**/**** at **:**
Permission to Progress on **/**/**** at **:**
Displays available:
2 – GENERATED DATA 5 – REASON FOR ACTION
3 – ACCOUNT DETAIL
4 – DATA AS INPUT
Entry Items
[] *** [] ***
C10059 End of Document
DEVD,RETURN,PRINT [ ]
For Handling Agent display (DEMD from LMOV) the options are provided but some data is suppressed (e.g. for “4 - DATA AS INPUT” consignee, recipe code, supplementary declarations and ingredients are not shown). On the summary screen above the date-times for “Prelodged” and “Permission to Progress” are not shown.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 92 of 108
Version: 4.0
There are no “Entry Items” for Custom Clearance Requests (C21).
For Supplementary Declarations the “Prelodged” field is not shown.
15.3.3 Generated Data Screens
15.3.3.1 Exporters/Submitting Traders
a. DEVD – Generated Data screen (Header) ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADHDRV:1H
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
GENERATED DATA
MRN ****************** Entry Type **** ***
Allocated route []** Tax Point **/**/**** **:**
Status of Entry * Goods Arrived **/**/**** **:**
ICS Code. . . . . ** Permission to Progress on **/**/**** **:**
Off Export Locn []*** Shed *** Submitting Agent []************
Exit Result []** on **/**/**** at Office ******** Seals state *
EXPORT STOPPED
Stats Value . . . *************
RAR Codes : FAS * DAN * Agent * Exptr *
C10058 Beginning of Document
DEVD,RETURN,PRINT [ ]
Stats Value does not appear for a C21.
The Exit result date will report either the Exit Date or Stopped date advised by ECN+ via the exit message IE518. The optional message ‘EXPORT STOPPED’ is additionally reported when CHIEF is advised a stopped date.
b. DEVD – Generated Data screen (Item) ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADITKEY:1H
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
GENERATED DATA
ITEM No ***
Stats Val *************
DEVD,RETURN,PRINT [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 93 of 108
Version: 4.0
15.3.3.2 Handling Agents
a. DEVD – Generated Data screen (Header) ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADHDRV:1H
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version **
GENERATED DATA
MRN ****************** Entry Type **** ***
Allocated route []**
Status of Entry *
ICS Code. . . . . **
Off Export Locn []*** Shed ***
Exit Result []** on **/**/**** at Office ******** Seals state *
EXPORT STOPPED
C10058 Beginning of Document
DEVD,RETURN,PRINT [ ]
Stats Value does not appear for a C21.
The Exit result date will report either the Exit Date or Stopped date advised by ECN+ via the exit message IE518. The optional message ‘EXPORT STOPPED’ is additionally reported when CHIEF is advised a stopped date.
15.3.4 Account Details Screens – (Exporters/Submitting Traders only)
a. DEVD – Account Details screen (Entry Totals) ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
HDRMOP:1:1H
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
ENTRY ACCOUNT DETAILS
ENTRY TOTALS
Deferred MCD, DAN non-excise ****** Immed MCD *****
Deferred MCD, DAN excise ******
MOP Total Tax Type Amount
[]* *************
[]*** *************
[]*** *************
Tax Type Total
[]*** *************
[]*** *************
C10058 Beginning of Document
DEVD,RETURN,PRINT [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 94 of 108
Version: 4.0
b. DEVD – Account Details screen (Item Data) ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADITDRV:1:1P
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
ENTRY ACCOUNT DETAILS - Item No **
Stat Val *************
MOP Total Tax Type Amount
[]* *************
[]*** *************
[]*** *************
Tax Type Total
[]*** *************
[]*** *************
DEVD,RETURN,PRINT [ ]
15.3.5 Data As Input Screens
]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADHDR1:1H
EPU []*** EPS * Entry number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
DATA AS INPUT
The detailed screens are not depicted here as the layout is the same as for the corresponding insert transaction for the entry type with the data protected. For Handling Agent display some data is suppressed (e.g. consignee, recipe code, supplementary declarations and ingredients are not shown).
C10059 End of Document
DEVD,RETURN,PRINT [ ]
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 95 of 108
Version: 4.0
15.3.6 Reason for Action Screens – (Exporters/Submitting Traders only)
a. DEVD – Reason for Action screen ]TRADER-ROLE O DISPLAY ENTRY VERSION DETAILS CHIEF/CIES 01/10/09 12:15
SADAMRSN:1H
EPU []*** EPS * Entry Number []******* Date **/**/**** Time **:**
Version ** Created on **/**/**** at **:**
Reason for Action
**/**/**** **:** - RELEASE FROM DETENTION
**********************************************************************
**/**/**** **:** - DETENTION
**********************************************************************
**/**/**** **:** - AMENDMENT
**********************************************************************
C10059 End of Document
DEVD,RETURN,PRINT [ ]
15.4 Document Structure
Segments cannot be inserted or deleted in this Document, and hence a segment table is not necessary.
15.5 Field Completion Rules
The tables in the following sub-sections identify for each input field within the Document whether it is optional (O) or mandatory (M) and any cross-field validation checks that apply.
Field Name (SAD Box) Optionality Cross-field Validation Checks
(Entry Reference)EPU/ Entry number/ Date
O
Created On/At O Generation ID O Entry key O Decln UCR & Part, Supp Dec? / MRN
O
Movement No O
15.6 Field Details
This section gives details of the business use and data that should be entered into the parameter fields. This section also gives details of some of the generated data that is displayed where the meaning is not obvious.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 96 of 108
Version: 4.0
15.6.1 Parameter Fields
One and only one of the following must be supplied to identify the Entry:
CHIEF Entry Reference (EPU, Entry Number and Date);
CHIEF internal Entry Key;
Declaration UCR and Part;
Movement Reference Number;
Movement Number.
(Entry Reference)
The Entry Reference consists of the following fields which must all be supplied.
EPU the number of the EPU where the declaration was made. The field defaults to your EPU.
Entry number
the number of the Entry at the EPU. It includes the check character.
Date the date of the Entry.
Created A date and time at which the version or generation was current (i.e. any time from when it was created until the next generation was created). If not supplied the latest generation of the Entry is displayed.
On the date;
At the time.
Generation ID An internal field used when DEVD is invoked via LIEV.
Entry Key Access via the Entry Key is only required for DTI Entries that have been stored without ever having been accepted. It is shown on the Entry Acceptance screen of the Insert Entry transactions and can also be noted from the LSTR transaction (‘USER-REF’ column).
DUCR & DUCR Part & Supp Dec? / MRN
Identifier of the Entry you wish to access. One of two different types of identifier can be used: Either: the DUCR and DUCR Part or the MRN.
UCR The UCR (see Reference [4]).
Part The optional part number and check character. The check character should be entered to avoid undetected keying errors.
MRN Movement Reference Number. It must be the latest MRN for the Entry, otherwise it will be rejected.
Supp Dec?
Indicates when set to “Y” that the entry identified by DUCR and Part or MRN is a Supplementary Declaration. It is required to identify a Supplementary Declaration that has the same DUCR / DUCR Part as a PSA.
Movement No The unique identifier of a movement recorded on CHIEF. Movement No is provided as a parameter to support downward selection from LMOV. It is not expected that it will be used when invoking DEVD directly.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 97 of 108
Version: 4.0
15.6.2 Displayed Data Fields
Entry type Identifies the Entry type and declaration method. (field 1): the Entry type, e.g. ‘FDE’, ‘SDE’, or ‘LCP’. (field 2): the declaration method, i.e. ‘DTI’. (Off Export) The location where the goods being declared first arrived. Locn Goods location Shed Shed at the goods location (Exit Result) Details returned from the Office of Exit on the status of the goods. Exit
result Control Results code for the exit ‘A1’ Satisfactory ‘A2’ Considered Satisfactory ‘A4’ Minor irregularities ‘B1’ Not satisfactory
on Date when goods exited or were stopped at the Office of Exit at Office Identifier for the Office of Exit in the format –
CCnnnnnn where –
CC – Country code for the location of the Office of Exit nnnnnn – Six digit reference for the Office of Exit.
Seal state
State of the seal on the goods at the Office of Exit. ‘0’ Not OK. ‘1’ Ok.
EXPORT STOPPED
Displayed when the goods have been stopped at the Office of Exit
IRC The Inventory Return Code (IRC) received from the Inventory system. A blank field indicates that no code has been received. ‘000’ indicates that a match with the Inventory system has been achieved. Any other value indicates that a match has not been achieved.
RAR Codes The following fields identify any accounting failures for the Entry at the point of clearance. When supplied for a particular payment method the Reason for Accounting Rejection (RAR) codes have the following meanings:
‘1’ Security guarantee inhibited/not on file; ‘2’ Security guarantee account balance inadequate; ‘3’ DAN inhibited/not on file; ‘4’ DAN balance inadequate; ‘5’ DAN inhibited/not on file charges transferred to FAS; ‘6’ DAN balance inadequate charges transferred to FAS; ‘7’ FAS balance inadequate; ‘8’ FAS inhibited/not on file; ‘9’ Daily Account for the EPU not open; ‘A’ FAS specific entry payment required.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 98 of 108
Version: 4.0
15.7 Cross-Field Validation Checks
None.
END OF SECTION 15
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 99 of 108
Version: 4.0
16. RACD – Request Accompanying Document
16.1 Business Description
This transaction is used to request the data needed to produce an Export Accompanying Document (EAD) for an indirect Export Entry. The requested data is returned from CHIEF in an EDI CUSDEC message or in a printable form via EDCS.
The transaction allows the export entry to be identified by MRN or DUCR/part or Entry Reference (i.e. EPU, Number Date).
The Entry must be an indirect Export and can be identified by one of –
Declaration UCR (DCUR) and optionally DUCR Part
Movement Reference Number
Entry Number and Date
16.2 Starting the Transaction
This transaction is invoked by typing the command code “RACD” on the command line.
Other information (to bypass the initial parameter input screen) can be provided as parameters as shown in the following examples:
“RACD” Causes the parameter screen to be displayed.
“RACD 3GB112233431000-3BA059LN” Causes a report for the Export Entry having a Declaration UCR 3GB112233431000-
3BA059LN to be generated.
“RACD 3GB112233431000-3BA059LN,002” Causes a report for the Export Entry having a Declaration UCR of 3GB112233431000-
3BA059LN and Part 002 to be generated.
RACD 08GB10X12345678016” Causes a report for the Export Entry having an MRN of 08GB10X12345678016 to be
generated.
“RACD ,, A12345A,12032009” Causes a report for Entry Number A12345A input to the EPU defined for the user on
12th March 2009 to be generated.
In all cases where a valid parameter is provided, the initial parameter input screen is bypassed.
16.3 Document Data
This section shows how the data for the transaction appears as a Document on the screen.
After the initial parameter screen has been completed, confirmation is provided in the form of a screen with the same data content and layout as previous, but with all fields protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 100 of 108
Version: 4.0
a. RACD – Initial Parameter input screen ]TRADER-ROLE O REQUEST ACCOMPANYING DOCUMENT CHIEF/CIES 01/10/09 12:15
HEAD:1P
DUCR / MRN [ ] DUCR Part [ ]
EPU []*** Entry Number [ ] Date [ / / ]
C10059 End of Document
REPORT,RETURN [REPO]
b. RACD – Confirmation screen ]TRADER-ROLE O REQUEST ACCOMPANYING DOCUMENT CHIEF/CIES 01/10/07 12:15
HEAD:1P
DUCR []*********************************** DUCR Part ****
EPU []*** Entry Number []******* Date **/**/****
C2249 Requested report queued successfully
RETURN [RETU]
16.4 Document Structure
Segments cannot be inserted or deleted in this Document, and hence a segment table is not necessary.
16.5 Field Completion Rules
This section shows whether each input field within the Document is optional (O) or mandatory (M) for each possible input phase, where optional may include conditional absence.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 101 of 108
Version: 4.0
Field Name (SAD Box) Optionality DUCR / MRN O DUCR Part O Entry Number O Date O
16.6 Field Details
This section of the Guide gives details of the business use and the data that should be entered into each field on the Document used by RCP3.
DUCR / MRN
The Declaration UCR or Movement Reference Number (MRN) for Export Entry.
DUCR Part When a Declaration UCR has been input in the “DUCR / MRN” field, this field can be completed if more than one declaration has been made to cover the goods identified by the same DUCR. The Part is made up of (up to) three (numeric) digits, and the item may also contain a one-character alphabetic check character, covering the DUCR and Part.
Entry Number This field is part of the entry reference and includes the check character.
Date Date of the Export Entry, used to identify the Entry together with the Entry Number field
16.7 Cross-Field Validation Checks
1. Entry Number, Date
If one of these fields is entered, then both must be entered.
2. DUCR, DUCR Part
If DUCR Part is entered, then DUCR must also be entered.
3. Entry Number and Date, DUCR(/Part), MRN
If Entry Number, Date and either DUCR/DUCR Part or MRN are entered then they must identify the same Entry.
4. MRN
If an MRN is entered then DUCR Part must not be entered.
END OF SECTION 16
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 102 of 108
Version: 4.0
17. RCP3 – Request SAD COPY 3
17.1 Business Description
This transaction allows the user to request a SAD Copy 3 for an Export Entry.
The Entry may be identified by means of its DUCR or by its Entry reference.
The request is rejected if:
the Trader is not the Entry owner;
the Entry is cancelled or terminated;
the Entry is a C21;
the Entry is a Supplementary or Import Declaration.
17.2 Starting the Transaction
This transaction can be invoked by typing the command code “RCP3” on the command line. Other information (to bypass the initial parameter input screen) can be provided as parameters as shown in the following examples:
“RCP3” Causes the parameter screen to be displayed.
“RCP3 3GB112233431000-3BA059LN” Causes a report for the Export Entry having a Declaration UCR 3GB112233431000-
3BA059LN to be generated.
“RCP3 3GB112233431000-3BA059LN,002” Causes a report for the Export Entry having a Declaration UCR of 3GB112233431000-
3BA059LN and Part 002 to be generated.
“RCP3 ,,120,A12345A,12032003” Causes a report for Entry Number A12345A input to EPU 120 on 12th March 2003 to
be generated.
In all cases where a valid parameter is provided, the initial parameter input screen is bypassed.
17.3 Document Data
This section shows how the data for the transaction appears as a Document on the screen.
After the initial parameter screen has been completed, confirmation is provided in the form of a screen with the same data content and layout as previous, but with all fields protected.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 103 of 108
Version: 4.0
a. RCP3 – Initial Parameter input screen ]TRADER-ROLE O REQUEST SAD COPY 3 CHIEF/CIES 01/10/09 12:15
HEAD:1P
UCR . . . . . [ ] Part [ ]
EPU . . . . . [ ] Entry Number [ ] Date [ / / ]
C10059 End of Document
REPORT,RETURN [REPO]
b. RCP3 – Confirmation screen ]TRADER-ROLE O REQUEST SAD COPY 3 CHIEF/CIES 01/10/09 12:15
HEAD:1P
UCR . . . . .[]*********************************** Part ****
EPU . . . . .[]*** Entry Number []******* Date **/**/****
C2249 Requested report queued successfully
RETURN [RETU]
17.4 Document Structure
Segments cannot be inserted or deleted in this Document, and hence a segment table is not necessary.
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 104 of 108
Version: 4.0
17.5 Field Completion Rules
This section shows whether each input field within the Document is optional (O) or mandatory (M) for each possible input phase, where optional may include conditional absence.
Field Name (SAD Box) Optionality EPU O Entry Number O Date O Decln UCR O Part O
17.6 Field Details
This section of the Guide gives details of the business use and the data that should be entered into each field on the Document used by RCP3.
EPU This field is part of the CHIEF entry reference, and should be completed together with the Entry Number and Date.
Entry Number This field is part of the entry reference and includes the check character.
Date This field is also part of the entry reference.
Decln UCR The Declaration UCR is expected to provide the most common method of identifying an Export Entry. It should contain the (up to) 35-character reference allocated to the goods movement by the Trader.
Decln Part Optionally completed when more than one declaration has been made to cover the goods identified by the same Declaration UCR. The Part is made up of (up to) three (numeric) digits, and the item may also contain a one-character alphabetic check character, covering the Declaration UCR and Part.
17.7 Cross-Field Validation Checks
1. EPU, Entry Number, Date
If any of these fields is entered, then all must be entered.
2. Decln UCR, Decln Part
If Decln Part is entered, then Decln UCR must also be entered.
3. EPU, Entry Number and Date, Decln UCR(/Part)
If both sets of parameters are supplied, then they must identify the same Entry.
END OF SECTION 17
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 105 of 108
Version: 4.0
18. Glossary and References
18.1 Glossary
See STD 003 - GLOSSARY AND AUTHORISED ABBREVIATIONS
See USM 102 - CHIEF GLOSSARY AND ABBREVIATIONS
RPA – Rural Payments Agency
ECN+ EDI/CSI Node Plus. ECN+, is used by EU Member States to provide the necessary National Export Control Application (NECA) functionality required for ECS.
ECS Export Control System
18.2 References
RefNo.
Title Document Reference
1. INTRODUCTION TO CHIEF USER GUIDE USM 100
2. CHIEF GENERAL CONCEPTS USER GUIDE USM 101
3. CHIEF GLOSSARY AND ABBREVIATIONS USM 102
4. COMMON ENTRY TRADE USER GUIDE USM 239
5. COMMON USER FACILITIES USER GUIDE USM 520
6. TIS : EDI FOR EXPORTS DES 208
7. NOT USED
8. SYSTEM MANAGEMENT USER GUIDE USM 541
9. INTEGRATED TARIFF OF THE UNITED KINGDOM
END OF SECTION 18
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 106 of 108
Version: 4.0
APPENDICES
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 107 of 108
Version: 4.0
Document Control
Status: Author John Walker, CHIEF Design Status Approved
Change Log:
Version Date Change Reference
Comments (please include names of approvers in this section)
For previous history, see version 3.0 (Capgemini). 4.0 11/01/2016
CR115
General / Correction / see EARS 27685482
Document content transferred to HMRC template. Section 3.2 & Sections 4.5, 5.5, 6.5, 7.5, 8.5 & 9.5. Declarations for Ship or Aircraft supplies no longer required, so Specific Circumstance ‘B’ no longer used and AI Statement ‘SPCIB’ no longer accepted. Also updates / corrections to the cross-validation rules and where they are applied. Section 3.1.1. ‘EU’ Exports are not only for exports to EFTA countries, but also for exports to (non-EFTA) Common Transit countries.
Storage:
Master Copy USM305 Review Record USM305 Review Record
Document Reviewer List:
Reviewer Role Bernadette Holden BT Change Glen Robe BT Change CSG CHIEF Support Group
USM305: Export Entry Trade User Guide _______________________________________________________________________________________
_______________________________________________________________________________________
Filename: USM305 Page 108 of 108
Version: 4.0
END OF DOCUMENT
Statement of Confidentiality
© HM Revenue & Customs 2016.
All rights reserved.
