MODCAR - MANIFESTS IN ASYCUDA++
Ó UNCTAD – SITE (V1.15)
5.12
For example - these T1s
T1 number
Item No
Commodity code
Gross mass
Number of packages
125
1
85
100
2
2
8502
200
5
126
1
85
100
1
2
850210
10
1
3
89
50
1
- will generate the following Bills of Lading:
B/L number
Commodity code
Gross mass
Number of packages
TRS1999-125/1
85
200
3
TRS1999-125/2
8502
200
5
TRS1999-125/3
850210
10
1
TRS1999-125/4
89
50
1
The Voyage number of the generated Manifest takes on the following structure:
TRS + Year of T1 + “-“ + Validation no. of T1 where the Year and Registration number come
from the first T1 tagged in the list.
The Bill of Lading number follows the following structure:
TRS + Year of T1 + “-“ + Validation no. of T1/1 where the final number is incremented for each
Bill of Lading.
In all cases, when a Manifest is generated from a T1, the type of Bill of Lading code is 950
according to International codification.
The status of the Bills of Lading will be ‘REGISTERED’ and the operation will be ‘FROM T1’.
Manifests Generated from TIR and FIP Documents
Manifests are generated in a similar manner for goods covered by TIR Carnet and the FIP
document. See Section 7 of the Reference Document for further details on Transit processes.
Saving a Manifest after Data Capture
Large Manifests are not always entered and completed in one session. As the Manifest is being
prepared it can be progressively stored and thus saved for further action at a later time.
Local Store
The Manifest can be ‘Locally stored’ on the disk of the user’s computer. Selecting from the
Manifest screen the ‘ Local menu’ gives access to the ‘Action’ sub-menu and the option ‘Local
store’. Selecting Local store opens the ‘Create a manifest file’ window. The user gives the file a
name following DOS naming conventions and accepts by clicking on ‘OK’ . The default directory for
storing Manifests is ‘..\ASY\CAR\’.