Public Service
FINANCE
TAXES AND TAX COLLECTION
Administration of Customs and Excise
Message implementation Guide CUSREP-D94A
Data exchange between the port authority and the PLCE
Paperless Customs and Excise
Version 1.2 3
30/07/201521/01/2016
Use of the model:
· Above all, the document shall be saved under a name pursuant to the following naming guidelines. To this end, the following menu option shall be used: “File, Save as”
· Adjust the “Properties” of the document. To this end, use the following menu option: “File, Properties”
o Tab “Summary”
§ Title
§ Subject
§ Author
o Tab “Adjusted”
§ The complete section “Properties”
· This part of the document is not included in the page numeration. You can start to work on the next page.
· Keep this page in your document until it is sent to the steering group. It may serve as a useful reminder for all persons working with you on this document.
Naming guidelines:
Projectcode_Phase_DeliverableCode_Title_(AuthorInitials)_Version_(LanguageCode)
Naming / Obligatory /Optional / SpecificationsProjectcode / Obligatory / Decision taken by the steering group at kick-off
Phase / Obligatory / According to the planning which has been approved by the steering group
DeliverableCode / Obligatory / - According to the planning which has been approved by the steering group.
- A decimal coding can be applied if more than one working document leads to the execution of the final delivery. In this case, the code 00 will be used for the final delivery and the working group will agree on the sub codes that will be assigned to the working documents when drawing up the planning.
Title / Obligatory / - Assigned by the author
- Restrict the length to no more than 30 characters. Avoid spaces. A separation of the words cannot be indicated by means of an alternation of lowercase and uppercase.
- Do not use underlining, it is used to introduce a new part of the document name.
AuthorInitials / Optional
Version / Obligatory / First part: status
0: subject
1: approved by the partners
2: approved for test version
3: approved for operational version
Separator: space
Second part: version start at 1 for the draft version and restart at 0 for each subsequent status.
Exemples:
PLD_01_01_ApplicationArchitecture_0 1
PLD_01_01.00_ApplicationArchitecture_ET_0 1_EN
PLD_01_01.01_RelevantProcesDescr_PR_0 1_NL
LanguageCode / Optional / - NL for Dutch
- FR for French
- EN for English
- DU for German
Please follow the above-mentioned guidelines and to not forget to:
- adjust the version number
o in the name of your file,
o in the “Properties” of the document Tab “Adjusted”;
- complete the version history of the document at the first page.
Stop at this paragraph in case of removal of this text before the document is sent to the steering group. If not, the section end will be removed and as a result also the page layout.
Document control
1 Version history of the document
Version / Date / Author / Remark0 1 / 20/11/2004 / Roger Beeckman / First draft
1 0 / 01/04/2005 / Roger Beeckman / Final
1.1 / 07/04/2014 / Martine De Doncker / Addition of additional elements with regard to the exit confirmation of an ocean vessel and revision of full MIG
1.2 / 30/07/2015 / Klara Pasgang / Adding rule to p29 to enforce the sending of only one location within the message instead of 99.
1.3 / 21/01/16 / Klara Pasgang / Adding remark 2 (p32) to 5.5 GROUP 5 (NAD data) concerning modification of the CUSREP message
Table of contents
1 Introduction 5
2 Format of the message 6
2.1 Version of the message 6
2.2. Initial scope of the message 6
2.2.1 Functional definition 6
2.2.2 Field application 6
2.2.3 Principles 6
2.2.4 References 6
2.2.5 Terms and definitions 6
2.2.6 Message definition 8
3 Use of the message 15
3.1 Introduction 15
3.1.1 Aim 15
3.1.2 Time of sending of the message – import movement (document name in code = 933) 15
3.1.4 Erroneous CUSREP message 15
3.2 Content of the message 15
3.2.1 Number of the document 15
3.2.2 Notification of a passage 16
3.2.3 Notification of mooring 16
3.2.4 Identification of the responsible shipping agent 17
3.2.5 Transport data 17
3.3 Data modification, extension or cancellation 17
3.3.1 Data modification 17
3.3.2 Data extension 17
3.3.3 Data cancellation 18
4 Technical description of the message 19
4.1 Used segments 19
4.2 Structure diagram 19
4.3 Description of the used segments 20
4.3.1 BGM – Beginning of message 20
4.3.2 Group 1/RFF – Reference 20
4.3.3 Group 2/LOC Identification of a place 21
4.3.4 Group 2/DTM Date and Time 22
4.3.5 Group 5/NAD Details with regard to the responsible shipping agent 23
4.3.6 Group 8/TDT details of the transport 24
5 Program specifications 26
5.1 The segment BGM 26
5.2 Group 1 27
5.2.1 Segment RFF 27
5.3 Group 2 28
5.3.1 Group 2 segment LOC 30
5.4 Group2/DTM Date and time 31
5.5 Group 5 32
5.5.1 Group 5/NAD Data with regard to the responsible shipping agent 32
5.6 Group 8 33
5.6.1 Group 8 segment TDT 33
6 Examples 34
6.1 Example of the (first) passage upon arrival 34
6.2 Example of mooring 34
6.2.1 The passage has not been notified 34
6.2.2 The passage has already been notified 34
6.3 Cancellation of all data of a message upon arrival 34
6.4 Cancellation of all data of a message upon departure 34
6.5 Cancellation of a passage upon arrival 34
6.6 Cancellation of a passage upon departure 35
6.7 Cancellation of the last passage upon departure 35
6.8 Cancellation of a mooring place 35
6.9 Cancellation of a mooring place 35
6.10 Modification of a passage place upon arrival 35
6.11 Modification of a passage place upon departure 35
6.12 Modification of a place code upon arrival 35
6.13 Modification of a passage place upon departure 36
6.14 Modification of the date and/or hour of passage upon arrival 36
6.15 Modification of the date and/or hour of passage upon departure 36
6.16 Modification of a shipping agent (at quay) upon arrival 36
6.17 Modification of a shipping agent (at quay) upon departure 36
6.18 Modification of the data of an ocean vessel upon arrival 36
6.19 Modification of the data of an ocean vessel upon departure 36
6.20 Addition of a quay 37
6.21 Addition of a country of destination upon departure 37
7 Enclosures 38
7.1 Enclosure 1: codes passages 38
7.1.1 Passages port of Antwerp 38
7.1.2 Passages port of Ghent 38
7.1.3 Passages port of Zeebrugge 38
7.2 Enclosure 2: codes of the quays 38
7.2.1 Quays in Antwerp 38
7.2.2 Quays in Ghent 38
7.2.3 Quays in Zeebrugge 38
7.3 Enclosure 3: the Iso alpha-II codes 38
Overview of the figures
Figure 1 : Title Fout! Bladwijzer niet gedefinieerd.
Overview of the tables
Table 1 : Title Fout! Bladwijzer niet gedefinieerd.
1 Introduction
This document is the Message Implementation Guide (MIG) for data exchange with regard to the notification of the places of passage and the final date of arrival and departure of an ocean vessel by the port authorities. The following message is the EDIFACT message CUSREP - version D94A.
In chapter 2 you will find an overview of the full message.
In chapter 3 you will find a brief explanation with regard to the use of the message.
In chapter 4 you will find a description of the segments and data elements which are required - compulsorily or not - by the Administration.
In chapter 5 the specifications with regard to the internal programming are listed.
In chapter 6 a few examples of the messages are given on the basis of the function of the message.
In chapter 7 the codes to be used are listed. If these codes are applied by multiple messages, reference is made to a separate document:
PLDA_05_codes messages_V0 1.doc
In case of international codes and if the code list is too extended, reference is made to the applicable website.
2 Format of the message
2.1 Version of the message
Message Type: CUSREP
Version: D
Release: 94A
Contr. Agency: UN
Status: 2
Revision: 1
Date: 94-09-21
2.2. Initial scope of the message
2.2.1 Functional definition
This Customs Conveyance Report Message (CUSREP) permits the transfer of data from a carrier to a Customs administration for the purpose of meeting Customs reporting requirements in respect of the means of transport on which cargo is carried.
2.2.2 Field application
This message may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.
2.2.3 Principles
It is envisaged that the Customs Conveyance Report Message may be initiated by the carrier to report details of the means of transport on which cargo is conveyed to a Customs administration. The message is transmitted upon arrival of the vessel, flight, etc., or where national legislation permits, prior to arrival. The data provides a means of establishing the basis of a cargo inventory report for the conveyance in question. Details of individual consignments carried on the conveyance will be subsequently transmitted to Customs using a CUSCAR message or a series of such messages. It also allows Customs to undertake selectivity processing in order to select high risk conveyances and shipments requiring examination. The message embodies reporting requirements of all modes of transport. Each message covers the data requirements for one conveyance. The message may be used for reporting empty containers as well as numbers of passengers and crew.
2.2.4 References
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. The full text of the references can be consulted via www.unece.org/trade/untdid/welcome.htm.
2.2.5 Terms and definitions
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - GeneralIntroduction, Section 2.
The terms and definitions can be consulted via www.unece.org/trade/untdid/welcome.htm.
2.2.6 Message definition
2.2.6.1 Data segment clarification
0010 UNH, Message header
A service segment starting and uniquely identifying a message. The message type code for the Customs conveyance report message is CUSREP.
Note: Customs conveyance report messages conforming to this document must contain the following data in segment UNH, composite S009:
Data element:
0065 CUSREP
0052 D
0054 94A
0051 UN
0020 BGM, Beginning of message
A segment to identify the report/voyage number, type of message (e.g. amendment) and date/time of message of creation.
0030 DTM, Date/time/period
A segment to indicate date/time of conveyance report to Customs.
0040 QTY, Quantity
A segment to identify the number of passengers, number of crew, number of bills.
0050 FTX, Free text
A segment to provide observations, remarks and reason for change.
0060 MEA, Measurements
A segment to specify the conveyance's gross tonnage, net tonnage, summer dead weight tonnage, containerized/non-containerized tonnage and overall length.
0070 GIS, General indicator
A segment to specify the import/export/transit indicator, prohibited/restricted goods indicator and unregistered spaces indicator.
0080 Segment group 1: RFF-DTM
A group of segments to specify references and dates/times related to the conveyance.
0090 RFF, Reference
A segment to specify reference numbers associated with the conveyance.
0100 DTM, Date/time/period
A segment to specify dates/times associated with the conveyance's reference numbers.
0110 Segment group 2: LOC-DTM
A group of segments to identify voyage itinerary.
0120 LOC, Place/location identification
A segment to specify the conveyance's voyage itinerary - ports of call/places.
0130 DTM, Date/time/period
A segment to specify dates/time associated with the itinerary.
0140 Segment group 3: DOC-RFF-DTM-LOC
A group of segments to specify supporting documentary requirements and associated reference numbers, dates/times and locations.
0150 DOC, Document/message details
A segment to specify supporting documentary requirements, including Certificate of Registry, Safety of Life at Sea Certificate, Maritime Health Declaration, Ship's Stores Declaration (FAL 3), Crew's Effects Declaration (FAL 4), Crew's List Declaration (FAL 5), Passenger List (FAL 6).
0160 RFF, Reference
A segment to specify reference numbers associated with a supporting documentary requirement.
0170 DTM, Date/time/period
A segment to specify dates/times/periods associated with a supporting documentary requirement.
0180 LOC, Place/location identification
A segment to specify locations associated with a supporting documentary requirement.
0190 Segment group 4: TAX-MOA-GIS
A group of segments to indicate duty/tax/fee details and monetary amounts payable related to the conveyance.
0200 TAX, Duty/tax/fee details
A segment to specify relevant duty/tax/fee information.
0210 MOA, Monetary amount
A segment to specify monetary amount.
0220 GIS, General indicator
A segment to transmit a processing indicator.
0230 Segment group 5: NAD-SG6-SG7
A group of segments to identify names, addresses, contacts and references relating to the message.
0240 NAD, Name and address
A segment to specify declarant's name and address, ship's agent name and address, and master's name.
0250 Segment group 6: CTA-COM
A group of segments specifying persons/departments and communication numbers associated with the party identified in NAD, group 5.
0260 CTA, Contact information
A segment to identify the person or department to whom communication should be directed.
0270 COM, Communication contact
A segment to identify communication numbers (i.e. telephone/ fax numbers) of departments or persons to whom communication should be directed.
0280 Segment group 7: RFF-DTM
A group of segments specifying persons/departments and communication numbers associated with the party identified in NAD, group 5.
0290 RFF, Reference
A segment to identify numbers associated with the named party or transaction.
0300 DTM, Date/time/period
A segment to specify dates/times associated with references.
0310 Segment group 8: TDT-TPL-DTM-SG9
A group of segments to indicate details related to each leg of transport.
0320 TDT, Details of transport
A segment to specify details of transport related to each leg, including name/number of vessel/vehicle/flight, nationality of ship, conveyance reference number, type of service identifier and carrier.
0330 TPL, Transport placement
A segment to specify placement of goods or equipment in relation to the transport used.