AIRFREIGHT – IMPLEMENTATION GUIDE “EXPORT MANIFEST” – version 1.12
/ FederaleOverheidsdienst
FINANCIEN
ALGEMENE ADMINISTRATIE VAN DOUANE EN ACCIJNZEN
Implementation guidelines
- Message “EXPORT MANIFEST”
Version 1.12
24/06/2015
Message Name: EXPORT MANIFEST
Message Version: 1.12
Date Released: 24/06/2015
Responsible Agency: Belgian Customs
Message Type: XML
Document Information
Message “EXPORT MANIFEST”
Project Name / ECS
File name
Author / Martine De Doncker
REVISION HISTORY
Rev / Section / Date / Author / Changes
1.0 / All / 01/09/12 / Martine De Doncker / Draft version
1.1 / All / 18/12/12 / Martine De Doncker / Adaptation due to Sea freight
1.2 / All / 22/04/2013 / Pascal DUCHENE / Adaptation for the firms of Koerier
1.3 / All / 09/07/2013 / Pascal DUCHENE / Corrections
1.4 / All / 03/10/2013 / Martine De Doncker / Explanation message type 5 = modification
1.5 / All / 09/01/2014 / Klara Pasgang / Adding ‘status of the goods’
1.6 / All / 03/02/2014 / Klara Pasgang / modifying xml
1.7 / All / 10/02/2014 / Wim Baetens / Corrections xml
1.8 / All / 21/02/2014 / Klara Pasgang / Changing Manifest Items to 9999
1.9 / All / 18/03/2015 / Klara Pasgang / Adding “transport mode at border” to manifest registration
1.10 / All / 20/05/2015 / Klara Pasgang / Adjustment to message specification for manifest item
1.11 / All / 03/06/2015 / Wim Baetens / Modifications to the xsd
1.12 / All / 24/06/2015 / Klara Pasgang / Replace the XSD and sample XML package with a URL + modification Message Identifier an…40 to an…35
CONTENT
1. Introduction 5
2. Message “EXPORT MANIFEST” 5
2.1. Technical specifications 5
2.2. Message specifications 5
2.3. Functional specifications 8
3. XSD schema 11
4. Message “Customs response” 11
5. Example of a ‘EXPORT MANIFEST’ message 11
1. Introduction
This manual describes the message that should be used by the carrier to notify details of consignments loaded on a specific vessel to leave the European territory.
This message is intended to link the declared transport documents and commercial data to the declaration numbers (MRN).
Besides this MIG describes also a protocol / message layout that allows “piecemeal” changes to a manifest to be sent.
But it should be noted that this approach makes the processing of a manifest message dependent on the processing state of the previous manifest message sent for the same manifest (e.g. when changing/deleting a manifest item, the manifest message that adds the item must have been processed before). In other words, it implicitly assumes that manifest messages are processed one by one, in the order that they were sent. So the responsible party should only sent modifications or new data after he has received the customs answer on the previous export manifest message.
The message type 5 (modification) can be used per manifest item or for all manifest item which should be modified.
- In case a manifest item has to be deleted, then all related number of packages and gross mass must be equal to the value 0.
- In case commercial data should be added, then Manifest item/Transport document data/Commercial data including the previous communicated commercial data should be noted.
- In case commercial data should be deleted, then Manifest item/Transport document data/Commercial data including all previous communicated commercial data should be noted. The packages and gross mass must be equal to the value 0 related to the commercial data which has to be deleted.
Note:
1. In case a manifest item has to be added, than the message type 9 should be used.
2. The fields related to the Manifest registration should also always be noted when the message type 5 is used.
2. Message “EXPORT MANIFEST”
2.1. Technical specifications
The used message format is of the type XML. Web services are the only possibility to forward the messages.
2.2. Message specifications
MANIFEST REGISTRATION 1 x R
MANIFEST ITEM 9999 x R
TRANSPORT DOCUMENT DATA 1 x R
COMMERCIAL DATA 999 x C C1
TRADER AT EXIT (Carrier) 1 x R
CUSTOMS OFFICE Actual Office Of Exit 1 x R
MANIFEST REGISTRATION
Manifest number R an..22
Date of presentation R n8
Total number of manifest items R n..5
Total number of packages R n..7
Total gross mass R n..11,3
Transport mode at border R n1
MANIFEST ITEM
Manifest item number R n..4
TRANSPORT DOCUMENT DATA
Transport document reference R an..35
Status of the goods C an..3
Marks & numbers of Packages C an..42
Kind of packages C an2
Number of Packages C n..5
Gross mass C n..11,3
Commodity Code (HS) O an6
Goods description text O an..35
COMMERCIAL DATA
Commercial reference type R n1
Commercial reference number R an..32
Status of the goods R an..3
Marks & numbers of Packages C an..42
Kind of packages R an2
Number of Packages involved C n..5
Gross mass involved R n..11,3
TRADER AT EXIT (Carrier)
EORI R an..17
CUSTOMS OFFICE Actual Office Of Exit
Reference Number R an8
N° / Field / Form / Content / Rules / XML tag1 / Message / ExportManifest
1.1 / Message identifier / an..35 / Unique identification of the message / <messageIdentifier>
1.2 / Message type / a1 / Message type:
9 = first
5 = modification / R14 / function
2 / MANIFEST REGISTRATION / MANREG
2.1 / Manifest number / an..22 / Unique identification of the export manifest / R1 / ManNumHEA1
2.2 / Date of presentation / xs:date / The date of the manifest / <DatOfPreHEA1>
2.3 / Total number of
manifest items / n..4 / The total number of manifest items / R2 / TotNumOfManIteHEA1
2.4 / Total number of
packages / n..7 / The total number of packages of all consignments / R3 / TotNumOfPacHEA306
2.5 / Total gross mass / n..11,3 / The total gross weight of all consignments / R4 / TotGroMasHEA307
2.6 / Transport mode at border / n1 / Possible transport mode at border:
1 = Sea
4 = Air
3 / MANIFEST ITEM / MANITE
3.1 / Manifest item number / n..4 / R5 / ManIteNumMIT1
3.2 / TRANSPORT DOCUMENT DATA / TRADOCDATMANITE
3.2.1 / Transport document
Reference / an..35 / The reference of the transport document:
- Air freight: the MAWB
- Sea freight: the B/L / R8 / TraDocRefMTD1 >
3.2.2 / Status of the goods / an..3 / Possible status of the goods:
- T1 = external Community goods
- T2 = internal Community goods in relation with EFTA countries
- TF = internal Community goods in relation with different met fiscal territories
- C = Community goods
- X = community goods exported to 3rd country
- TD = already an official document available (T-doc, carnet ATA or NATO form 302) / R15 / StaOfTheGooMTD1>
3.2.3 / Marks & numbers of
Packages / an..42 / The marks and numbers of the packages / C2
R6 / MarNumOfPacMTD1
3.2.4 / Kind of packages / an2 / ISO code for packages (UNECE Recommendation No. 21) / C3
R6 / KinOfPacMTD1
3.2.5 / Number of Packages / n..5 / C2
R6 / NumOfPacMTD1
3.2.6 / Gross mass / n..11,3 / R6 / GroMasMTD1>
3.2.7 / Commodity Code (HS) / an6 / ComCodTarCodTDD1pe>
3.2.8 / Goods description text / an..35 / GooDesTexMTD1
3.2.9 / COMMERCIAL DATA / C1 / COMDATDD1
3.2.9.1 / Commercial reference type / n1 / The commercial reference type:
1 = Container number
2 = Permit number
3 = Unique RoRo number / ComrefnumType
3.2.9.2 / Commercial reference number / an..32 / Container number or permit number or unique RoRo number / ComrefnumDD1
3.2.9.3 / Status of the goods / an..3 / Possible status of the goods:
- T1 = external Community goods
- T2 = internal Community goods in relation with EFTA countries
- TF = internal Community goods in relation with different met fiscal territories
- C = Community goods
- X = community goods exported to 3rd country
- TD = already an official document available (T-doc, carnet ATA or NATO form 302) / < StaOfTheGooTDD1>
3.2.9.4 / Marks & numbers of
Packages / an..42 / The marks and numbers of the packages / C2 / MarNumOfPacTDD1
3.2.9.5 / Kind of packages / an2 / ISO code for packages (UNECE Recommendation No. 21) / R7 / KinOfPacTDD1
3.2.9.6 / Number of Packages involved / n..5 / C2 / NumOfPacTDD1
3.2.9.7 / Gross mass involved / n..11,3 / R11 / GroMasTDD1
4 / TRADER AT EXIT (Carrier) / TRAEXI >
4.1 / EORI / an..17 / R12 / TINTEX23 >
5 / CUSTOMS OFFICE -Actual Office Of Exit / ACEACE >
5.1 / Reference Number / an8 / R10 / RefNumACE1
2.3. Functional specifications
2.3.1. Functional Rules
R1 = In case of air freight: the manifest number is as follows:
- The scheduled departure flight date: jjmmdd, followed by
- The flight number.
In case of sea freight: the manifest number is as follows:
- The registration number of the port authority, followed by
- The IMO number of the vessel.
R2 = The total number of manifest items at MANIFEST REGISTRATION level must be equal to the number of manifest item number at MANIFEST ITEM level.
R3 = In case of air freight: The total number of packages at MANIFEST REGISTRATION level must be equal to the sum of the number of packages at MANIFEST ITEM/TRANSPORT DOCUMENT DATA level.
In case of sea freight: The total number of packages at MANIFEST REGISTRATION level must be equal to the sum of the number of packages at MANIFEST ITEM/TRANSPORT DOCUMENT DATA/COMMERCIAL DATA level.
The content of the field ‘Total number of packages’ can be equal to the value ‘0’.
R4 = In case of air freight: The total gross weight at MANIFEST REGISTRATION level must be equal to the sum of the gross weight at MANIFEST ITEM/TRANSPORT DOCUMENT DATA level.
In case of sea freight: The total gross weight at MANIFEST REGISTRATION level must be equal to the sum of the gross weight at MANIFEST ITEM/TRANSPORT DOCUMENT DATA/COMMERCIAL DATA level.
The content of the field ‘Total gross weight’ can be equal to the value ‘0’.
R5 = The 'manifest item number' is the sequential number (started with 1 and uninterrupted) of the listed items in the export manifest (within 1 flight, not within the message).
R6 = This field cannot be used in case of sea freight. In case of air freight this field must be used.
R7 = For sea freight: If the content of the field ‘Commercial reference type’ at MANIFEST ITEM/TRANSPORT DOCUMENT DATA/COMMERCIAL DATA level = ‘1’ and the kind of packages within the container is not known
THEN the content ‘Kind of packages‘= ‘CN’
ELSE the content ‘Kind of packages’ = the kind of packages within the container.
R8 = The transport reference document should be unique within the export manifest.
R10 = The office of exit must know by the ECS-system and for all the linked electronic MRN (export and EXS declarations or NCTS declarations) the office of exit (export and EXS declarations) or destination (NCTS declaration) must be the same.
R11 = For sea freight: If the content of the field ‘Commercial reference type’ at MANIFEST ITEM/TRANSPORT DOCUMENT DATA/COMMERCIAL DATA level = ‘1’
THEN the content of the field ‘Gross mass involved’ at MANIFEST ITEM/TRANSPORT DOCUMENT DATA/COMMERCIAL DATA level can be 0
ELSE the content of the field ‘Gross mass involved’ at MANIFEST ITEM/TRANSPORT DOCUMENT DATA/COMMERCIAL DATA level must be > ‘0’.
R12 = The EORI must be known by ECS (EORI DB).
R14 = The function type 5 can only be used to notify shortages and excesses.
R15 = This field may only be used for air freight.
2.3.2. Functional Conditions
C1 IF sea freight
THEN the data group ‘COMMERCIAL DATA' on MANIFEST ITEM/TRANSPORT DOCUMENT DATA level is used
ELSE ‘COMMERCIAL DATA' on MANIFEST ITEM/TRANSPORT DOCUMENT DATA level cannot be used
C2 IF ‘Kind of packages’ indicates ‘BULK’ (UNECE rec 21 : ‘VQ’, ‘VG’, ‘VL’,‘VY’,’VR’, ‘VS’ or ‘VO’)
THEN ‘Marks & numbers of packages’ = ‘O’
‘Number of packages’ (box 31) cannot be used
ELSE
IF ‘Kind of packages’ (box 31) indicates ‘UNPACKED’ (UNECE rec 21 : = ‘NE’, 'NF' or 'NG')
THEN ‘Marks & numbers of packages’ = ‘O’
‘Number of packages’ = ‘R’
ELSE ‘Marks & numbers of packages’ = ‘R’
‘Number of packages’ = ‘R’.
C3 = In case of air freight: The kind of packages must be the same as the package type of the master waybill of the message “Arrival of goods”.
2.3.3. Validation Rules
Rule / Comment / ErrorTRAEXI TINTEX23 > in (EOR) / EOR => EORI number as identification / UnknownCarrierType
- TRADOCDATMANITE KinOfPacMTD1
- TRADOCDATMANITE COMDATDD1
KinOfPacTDD1> / The type of package must be conform to UNECE Recommendation No. 21 / UnknownPackageType
ACEACE < RefNumACE1 / UnknownExit Office
3. XSD schema
The relevant XML Schema is ‘ExportManifest.xsd’ and its included XSDs. They can be downloaded as a package from http://plda.fgov.be/nl/documentatie-plda, section “Pakket 2 – Functioneel technische specificaties goederenstromen – Berichtspecificaties”, Luchtvracht
4. Message “Customs response”
On all received messages ‘EXPORT MANIFEST’ the customs system will send a reply to the carrier via the message ‘Customs response’.
The detail of the message ‘Customs response’ can be found in the document ‘MIG – Customs response’.
In case the trader at Exit is notified of the fact that the presented manifest is accepted, and consequently the goods are allowed to immediate leave the Community by the given means of transport.
In negative case, the trader at Exit must modify his export manifest and resend it to the office of exit before the goods are allowed to leave the Community by the given means of transport.
5. Example of a ‘EXPORT MANIFEST’ message
The relevant examples ‘sample_ExportManifest_01_valid.xml’ and ‘sample_ExportManifest_02_full.xml’ are included sample xml. They can be downloaded as a package from http://plda.fgov.be/nl/documentatie-plda, section “Pakket 2 – Functioneel technische specificaties goederenstromen – Berichtspecificaties”, Luchtvracht
3