MODCAR - MANIFESTS IN ASYCUDA++ Ó UNCTAD – SITE (V1.15) 5.10 Information - Insert any additional remarks as required. Entering of the B/L data for one B/L is now complete. The cursor will return to the first field in the B/L screen. You may now close the Bill of Lading window to save the Bill and return to the Manifest. Inserting additional B/Ls    To add more Bills of Lading, select  ‘Local menu’, ‘Bill of Lading’, ‘New’  and  repeat  the  previous steps. Moving between B/L screens Activate  ‘Local  Menu’,  ‘Bill  of  Lading’  and  use  the  options  then  displayed  to  move  between individual B/Ls relating to the Manifest. The options are ‘New’, ‘Next’, ‘Previous’  and ‘Delete’. Moving between “List of B/Ls” and “Manifest General Segment” screens The  lists  of  B/Ls  and  the  Manifest  general  segment  are  on  one  form  with  the  Manifest  at  the  top, followed by the list of Bills of Lading. You may need to activate the screen scroll bars and then use the right hand scroll bar to move up or down the screen. Checking the Entered Data After entering all B/L data the cursor returns to initial field of the most recent B/L entered. Close the Bill of lading screen. This returns you to the  ‘Manifest - List of Bill of Lading screen’. Select ‘ Local Menu’, ‘Action’. Local and Server Checks From  the  Action  menu  you  have  the  choice  of   ‘Local   check’   or   ‘Check’.   As   in   declaration processing, ‘Local check’  validates your entered details against ASYCUDA++ reference tables on your client computer. Selecting  ‘Check’ means that you need to login to the server. With a server check  your  Manifest  and  Bill  of  Lading  details  will  be  checked  against  the  server  version  of  the reference tables. ‘Local check’  and  ‘Check’  will either confirm that your entered details are  ‘OK’, that there are no errors in the fields that use the reference tables and that the totals of the Bills of Lading match the Manifest summary totals or will display an error list on screen. Error Lists If an error list is displayed, rectify if possible or query with the carrier. The error list will show the error, (e.g. ‘# 0’ is the manifest, ‘# 3’ is Bill of Lading reference number 3), and the type of error. You can move directly to the error by double clicking on the error list item with the mouse. After correcting the error, recheck the manifest using  ‘Local check’  or  ‘Check’ .  If the manifest cannot be corrected immediately, store the manifest for attention at a later time. Generating a Manifest from Transit Documents Cargo Manifests may be generated from transit documents, to bring goods within normal Customs control procedures and to allow write off by declaration.  Manifests for transit goods are generated from  within  MODTRS.  Manifests  can  be  generated  from  documents  such  as  TIR  Carnets,  the  T1 Transit Document and the ASYCUDA++ First Import Procedure (FIP). See  Section  7  of  this  Reference  Document  for  full  details  of  National  Transit procedures using ASYCUDA++.