MODTRS - TRANSIT CONTROLS USING ASYCUDA++ Ó UNCTAD – SITE (V1.15) 7.8 At Office of Departure (Issuing Office) On reception of the validation message containing the discharge of the Transit by the Office of Destination, the document is updated and is given the status ‘Cleared’ and the date of closure. Completion of documents that are not automatically closed is done manually by an authorised Customs Officer, by entering the reference of the disputed claim or the manual discharge details. Reports and Printouts The following lists or reports will be available for each type of transit document – TIR or T1. Reports and Printouts at Office of Departure (Issuing Office) Outstanding documents sent to the Office of Destination, Transit movement not yet discharged, Transit time delay not yet expired. Expired documents sent to the Office of Destination, Transit movement not yet discharged, Transit time delay expired. Cleared documents sent to the Office of Destination, Transit movement discharged during authorised Transit time delay period. Reports and Printouts at Office of Destination Outstanding documents message received from the Office of Departure, Transit goods not arrived, not yet discharged, Transit time delay not yet expired. Expired documents messages received from the Office of Departure, Transit goods not arrived, not yet discharged, Transit time delay expired. Cleared documents sent to Office of Departure, Transit goods arrived and discharged, message returned. Placing Goods under Customs Control (for Clearance) When the goods arrive at the Office of Destination where they are to be cleared, they can be placed under normal Customs control, awaiting Customs clearance through the SAD declaration process. In ASYCUDA++ this transfer, from Transit control to Customs control of unentered goods, is done by the creation of a Manifest. A Manifest and related Bills of Lading are created in the MODCAR database and details may be accessed in the same way as for any other Manifest. Server Apart from the initial entry (capture) of Transit documents, most Transit operations performed in ASYCUDA++ involve the transfer of messages over the ASYCUDA++ computer network. This means that you need a server connection and must be logged in. (Exceptions are Local store and Local check functions, which are carried out on the Client PC.) For details on Server Login, Logoff, Replication and passwords see Section 2 of the Reference Document ‘Finding your way around ASYCUDA++’.