ISO 23355:2024

International
Standard
ISO 23355
First edition
Visibility data interchange among
2024-07
logistics information service
providers
Échange de données de visibilité entre fournisseurs de services
d'informations logistiques
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Abbreviated terms .2
4 Framework of logistics information service providers interconnection . 2
4.1 Interconnected relations .2
4.1.1 Overview .2
4.1.2 Regional LISP interconnection .3
4.1.3 Inter-regional LISP interconnection .3
4.1.4 Classification of parties in LISP framework .4
4.2 Features .4
5 Visibility data of logistics information service . 5
5.1 Logistics import/export process . .5
5.2 Logistics import/export status .6
5.2.1 Import .6
5.2.2 Export .7
5.3 Logistics visibility data interchange message .7
5.3.1 Overview .7
5.3.2 Interchange message .8
6 Messages of visibility data interchange between LISPs . 8
6.1 Message content attribute description .8
6.1.1 Description of character representations .8
6.1.2 Occurrence number of data elements .8
6.2 Messages .9
6.2.1 Transport means forecast information message .9
6.2.2 Transport means actual information message .17
6.2.3 Arrival report message .27
6.2.4 Tally message .45
6.2.5 Goods loading message . . 65
6.2.6 Transport means and goods release message . 85
7 Logistics visibility data element compilation .93
7.1 Overview . 93
7.2 Data element compilation table . 93
Bibliography .113

iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 154, Processes, data elements and documents in
commerce, industry and administration.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
Introduction
Visibility of logistics flow and a simple and trusted way to find the precise logistics information are very
important for logistics in international trade.
However, the logistics data to be obtained by the logistics operator is often provided by several logistics
information service providers (LISP) and other logistics parties. Although international standards (such as
UN/EDIFACT) have existed for decades and many national and regional systems have been implemented
based on these international standards, LISPs are often developed in isolation and fragmentation based on
its own business requirements; and this leads to different interpretations of standard messages. A logistics
information service framework should be specified for the visibility of logistics flow.
This document specifies a framework to clarify logistics visibility data and how it should be interchanged
among different LISPs. This document can be used by LISPs for establishing data connections with
other logistics information service systems and for satisfying different data providers’ and data users’
requirements. Logistics authorities and data users can also use this document to track the logistics flow and
optimize their services.
v
International Standard ISO 23355:2024(en)
Visibility data interchange among logistics information
service providers
1 Scope
This document specifies logistics visibility data, data elements, interchange message, and framework of
logistics information service providers (LISP) interconnection. This document is applicable to regional and
inter-regional logistics data interchange services of transport means and goods management in maritime,
road, air, and railway import/export transportation.
2 Normative references
There are no normative references in this document.
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1.1
data provider
party that provides logistics data to a logistics information service provider (LISP) (3.1.3)
3.1.2
data user
party that accesses logistics data from the logistics information service provider (LISP) (3.1.3) framework
3.1.3
logistics information service provider
LISP
party that provides the services of a platform for the electronic exchange of logistics information in the
supply chain for increased efficiency and effectiveness
3.1.4
logistics visibility data
data that constitute logistics event status in import/export logistics procedure, covering the event
data relating to the mode of transport, cargo and means of transport, B2B (business-to-business), G2B
(government-to-business), B2G (business-to-government), public or private interests
Note 1 to entry: Visibility data is sorted in each event.
3.1.5
logistics visibility data interchange
data interchange for accurate and efficient logistics tracking and traceability

3.1.6
interconnection
connected status between logistics information service providers (LISPs) (3.1.3)
Note 1 to entry: The visibility data interchanged among LISPs are interconnected, so the connected status among
LISPs is interconnection.
3.1.7
other receiver
party that receives a copy of a message when a document sender sends the message to a document receiver
3.2 Abbreviated terms
API application programming interface
CCS cargo community system
IMO International Maritime Organization
PCS port community system
UN/CCL United Nations Core Components Library
WCO World Customs Organization
4 Framework of logistics information service providers interconnection
4.1 Interconnected relations
4.1.1 Overview
As it is shown in Figure 1, the framework of LISP interconnection consists of regional LISP interconnection
and inter-regional LISP interconnection.
— A single LISP provides regional LISP interconnection.
— Multiple LISPs provide inter-regional LISP interconnection through APIs.

NOTE The connecting lines refer to APIs.
Figure 1 — Framework of LISP interconnection
4.1.2 Regional LISP interconnection
Regional LISP interconnection includes:
— LISP
— Data providers
— Data users
Data providers are connected to a LISP in the same region and provide the logistics data to the LISP. Data
users are connected to a LISP in the same region and access logistics data from the LISP. For example, there
are three regional LISP interconnections in Figure 1: LISP area A, LISP area B and LISP area C. In LISP area
A, data providers A provide the logistics data to LISP A, and data users A access logistics data from LISP A.
4.1.3 Inter-regional LISP interconnection
Inter-regional LISP interconnection includes:
— Multiple LISPs
— Data providers in different regions
— Data users in different regions
Inter-regional LISP interconnection can be provided by multiple LISPs through APIs. Data users connected
to a LISP can access logistics data from other regions by inter-regional LISP interconnection. For example,
as it shown in Figure 1, data users A can access logistics data from LISP area B and LISP area C, which are
provided by data providers B and data providers C.

4.1.4 Classification of parties in LISP framework
The parties in LISP framework are shown in Table 1.
Table 1 — Example of Parties in LISP Framework
Party Example of parties
a) PCS and CCS
LISP
b) Logistics data exchange platform
a) Maritime carrier
b) Freight forwarder
c) Port/Terminal operator
Data provider
d) Single window
e) PCS and CCS
f) Logistics data exchange platform
a) Maritime carrier
b) Freight forwarder
c) Port/Terminal operator
Data user
d) Single window
e) PCS and CCS
f) Logistics data exchange platform
4.2 Features
The framework of LISP interconnection should include 7 features.
a) Openness: Any of LISPs can participant in this network to provide and acquire logistics status
information mutually. They are information contributor, at the same time, they are information
consumer.
b) Confidentiality: To protect sensitive information of participated parties, information exchange shall be
conducted with the prerequisite of data providers’ consent.
c) Systematicness: APIs are used for authentication and providing/querying logistics status information
mutually. This feature reduces the cost of system implementation for both data providers and data users.
d) Distribution: Providing services with a distributed database, store and replicate data based on a
distributed framework.
e) Convenience: The latest logistics data sharing and query service between LISP in different regions can
be realized by using APIs.
f) Effectiveness: With the latest logistics status information, this framework can achieve the visual tracking
and traceability of logistics events, thereby ensuring accurate and efficient logistics information service
data interchange.
g) Inter-region: The logistics visualization data can be tracked across borders and regions to ensure
successful sharing and access of logistics event status data in different countries and regions.

5 Visibility data of logistics information service
5.1 Logistics import/export process
According to the general logistics import/export process, visibility data are streamlined as events in
chronological order. Integrating maritime, air, railway and road transport, there are 10 events on the import
process, as shown in Figure 2; on the export process, there are 9 events, as shown in Figure 3.
Figure 2 — Import process
Figure 3 — Export process
5.2 Logistics import/export status
5.2.1 Import
a) Transport means forecast information: Before the transport means enters the country (location), the
transportation enterprise shall pre-declare relevant dynamic data.
b) Transport means actual information: When the transport means enters the country (location), the
transportation enterprise shall declare relevant dynamic data.
c) Arrival at port (location): When the transport means enters the country (location), the transportation
enterprise shall declare the actual dynamic data of a transport means arrival (location).
d) Transport means declaration: When the transport means arrives at inbound location, the transportation
enterprise shall declare the transport means, passengers, crews, items and other information carried
by the transport means.
e) Goods arrival: When goods arrive the inbound location supervision site, the declaration of goods and
the corresponding transport means are carried out by the local enterprise.
f) Loading: When goods leave the inbound location supervision site, the declaration of goods and the
corresponding transport means are carried out by the local enterprise.
g) Tallying: When goods arrive at the designated supervision site, the site enterprise completes the
inventory and declares goods.
h) Transport means release: After customs formalities have been completed, the transport means carrying
import and export goods shall be released with the permission of the customs.
i) Goods release: After the customs accepts the declaration of import and export goods, examines
electronic data declaration forms, paper declaration forms and accompanying documents, examines the

goods, levies taxes or accepts guarantees, it shall make a decision to terminate the on-site supervision
of import and export goods and allow goods to leave the on-site supervision of the customs.
j) Customs clearance: Customs clearance is a procedure after customs release. After the goods enter the
country, the customs check the accuracy and authenticity of the imported cleaning manifest data and
confirms the verification manifest data.
5.2.2 Export
a) Arrival: When export goods arrive at the supervision site of the outbound location, the declaration of
goods and the corresponding transport means are carried out by the local enterprise.
b) Transport means declaration: When the transport means arrives at the outbound location, the
transportation enterprise shall declare the passengers, crews, items and other information carried by
the transport means.
c) Loading: When goods leave the supervision site of the outbound location, the declaration of goods and
the corresponding transport means are carried out by the local enterprise.
d) Tallying: When goods arrive at the designated supervision site, the site enterprise completes the
inventory and declares goods.
e) Transport means release: After customs formalities have been completed, the transport means carrying
export goods shall be released with the permission of the customs.
f) Goods release: After the customs accepts the declaration of export goods, examines electronic data
declaration forms, paper declaration forms and accompanying documents, examines the goods, levies
taxes or accepts guarantees, it shall make a decision to terminate the on-site supervision of export
goods and allow goods to leave the on-site supervision of the customs.
g) Transport means forecast information: Before the transport means enters the destination country
(location), the transportation enterprise shall pre-declare relevant dynamic data.
h) Transport means actual information: When the transport means enters the destination country
(location), the transportation enterprise shall declare relevant dynamic data.
i) Customs clearance: Customs clearance is a procedure after the export declaration. After the goods leave
the country, the customs check the accuracy and authenticity of the export cleaning manifest data and
confirms the verification manifest data.
5.3 Logistics visibility data interchange message
5.3.1 Overview
In logistics export/import process, 10 events on the import process and 9 events on the export process are
streamlined respectively. Regardless the direction of logistics flow, these 19 events are compiled into 6
messages, as shown in Table 2.
Table 2 — Process refinement into messages
Message name Import process Export process
Forecast information message Transport means forecast information Transport means forecast information
Actual information message Transport means actual information Transport means Actual information
Arrival report message Arrival at port (location) Arrival
Tally message Tallying Tallying
Goods loading message Loading Loading
Transport means and goods release Transport means release Transport means release
message
Goods release Goods release
5.3.2 Interchange message
Six kinds of logistics visibility data interchange massage should be used for logistics import/export
information service data interchange, as shown in Figure 4.
Figure 4 — Logistics visibility data interchange message
6 Messages of visibility data interchange between LISPs
6.1 Message content attribute description
6.1.1 Description of character representations
Table 3 provides the descriptions of the character attributes.
Table 3 — Descriptions of character representations
n numeric characters
an alphabetic and numeric characters
variable data unit size where "35" indicates the maximum number of available character
..35
positions
M mandatory
O optional
M/O
M/O, O/M appear in pairs in the table, two ways to fill in: choose one of the data items to fill
in, or choose both data items to fill in.
O/M
6.1.2 Occurrence number of data elements
The way to indicate the number of repetitions of data elements in messages is as follows:

a) 0.1 — The data element is optional and occurs once.
b) 0.n — The data element is optional and occurs multiple times.
c) 1.1 — The data element is mandatory and occurs once.
d) 1.n — The data element is mandatory and occurs multiple times.
e) 1/0.1 — Two input forms:
— these two data elements should be chosen one of them to fill in and occur once;
0/1.1
— both data elements can be filled in and occur once.
6.2 Messages
6.2.1 Transport means forecast information message
6.2.1.1 Basic requirements
6.2.1.1.1 Message name: forecast information message.
6.2.1.1.2 Message sender: transportation enterprises, such as shipping companies, consignors and freight
forwarders. Message receiver: destination units for transporting goods, such as ports, airports, railway
stations, freight stations and regulatory authorities.
6.2.1.1.3 The message should provide the forecast information about ships, trains, vehicles and aircrafts
arrival at the destination.
6.2.1.2 Message structure
6.2.1.2.1 Overview
Forecast information message shall consist of header, other receivers, transport means basic information,
calling location information and trailer. Figure 5 shows the general overview of the message.

Figure 5 — Overview of forecast information message
6.2.1.2.2 Header
The header of forecast information message should contain the data element items and descriptions shown
in Figure 6.
Figure 6 — Header of forecast information message
6.2.1.2.3 Other receivers and transport means basic information
Other receivers and transport means basic information of forecast information message should contain the
data element items and descriptions shown in Figure 7.

Figure 7 — Other receivers and part of transport means basic information of forecast
information message
6.2.1.2.4 Transport means basic information (continued)
Continued from Figure 7, transport means basic information of forecast information message should contain
the data element items and descriptions shown in Figure 8.

Figure 8 — Transport means basic information (continued) of forecast information message
6.2.1.2.5 Transport means basic information (continued) and calling information
Continued from Figure 8, transport means basic information and calling location information of forecast
information message should contain the data element items and descriptions shown in Figure 9.

Figure 9 — Transport means basic information (continued) and calling location information of
forecast information message
6.2.1.2.6 Trailer
The trailer of forecast information message should contain the data element items and descriptions shown
in Figure 10.
Figure 10 — Trailer of forecast information message
6.2.1.3 Message description
6.2.1.3.1 Header
Header of forecast information message is shown in Table 4.
Table 4 — Header of forecast information message
Record 00 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 00. M
2 Message type code an.6 Same as UNCL 1001 code ID M
3 Document description an.35 O
4 Document function code an.1 9 - original, 2 - addition, 3 - deletion, 4 - change M
5 Document sender name an.35 M/O
6 Document sender code an.17 O/M
7 Document receiver name an.512 M/O
8 Document receiver code an.17 O/M
9 Document creation date and time an.19 CCYYMMDDHHMMZHHMM M
10 Document issue date and time an.19 CCYYMMDDHHMMZHHMM M
11 Free text an.512 O
6.2.1.3.2 Other receivers
Other receivers of forecast information message are shown in Table 5.
Table 5 — Other receivers of forecast information message
Record 01 O
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 01. M
2 Document receiver name an.512 M/O
3 Document receiver code an.17 O/M
4 Free text an.512 O
6.2.1.3.3 Transport means basic information
Transport means basic information of forecast information message is shown in Table 6.
Table 6 — Transport means basic information of forecast information message
Record 10 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 10. M
2 Transport mode name an.17 M/O
3 Transport mode code an.1 O/M
4 Transport means name an.35 M/O
Ship is IMO number, aircraft is aircraft regis-
5 Transport means ID an.35 tration number, railway is train number, and O/M
vehicle is engine number + vehicle shelf number.
6 Import or export indicator code an.1 I-Import, E-Export M
7 Conveyance reference number an.17 M
8 Nationality code an.3 M
9 Transport means net weight measure n.14 Unit:  Ton (t) O
10 Transport equipment quantity n.6 Unit:  TEU O
11 Carrier name an.512 M/O
12 Carrier code an.17 O/M
13 Carrier address an.512 O
14 Carrier agent name an.512 M/O
15 Carrier agent code an.17 O/M
16 Carrier agent address an.512 O
17 Previous call location name an.256 M/O
18 Previous calling location code an.35 O/M
19 Next calling location name an.256 M/O
20 Next calling location code an.35 O/M
21 Estimated arrival date and time an.19 CCYYMMDDHHMMZHHMM M
22 Estimated departure date and time an.19 CCYYMMDDHHMMZHHMM O
23 Free text an.512 O
6.2.1.3.4 Calling location information
Calling location information of forecast information message is shown in Table 7.
Table 7 — Calling location information of forecast information message
Record 20 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 20. M
2 Port call sequence number an.10 M
3 Calling location name an.256 M/O
4 Calling location code an.35 O/M
5 Calling terminal name an.256 O
6 Estimated arrival date and time an.19 CCYYMMDDHHMMZHHMM O

6.2.1.3.5 Trailer
Trailer of forecast information message is shown in Table 8.
Table 8 — Trailer of forecast information message
Record 99 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 99. M
2 Total record document n.6 Including head record and trailer record M
6.2.2 Transport means actual information message
6.2.2.1 Basic requirements
6.2.2.1.1 Message name: actual information message.
6.2.2.1.2 Message sender: transportation enterprises, such as shipping companies, consignors and freight
forwarders. Message receiver: destination units for transporting goods, such as ports, airports, railway
stations, freight stations and regulatory authorities.
6.2.2.1.3 The message should provide the actual information about ships, trains, vehicles and aircrafts
arrival at the destination.
6.2.2.2 Message structure
6.2.2.2.1 Overview
Actual information message shall consist of header, other receivers, transport means basic information,
calling location information and trailer. Figure 11 shows the general overview of the message.

Figure 11 — Overview of actual information message
6.2.2.2.2 Header
The header of actual information message should contain the data element items and descriptions shown in
Figure 12.
Figure 12 — Header of actual information message
6.2.2.2.3 Other receivers and transport means basic information
Other receivers and transport means basic information of actual information message should contain the
data element items and descriptions shown in Figure 13.

Figure 13 — Other receivers and part of transport means basic information of actual
information message
6.2.2.2.4 Transport means basic information (continued)
Continued from Figure 13, transport means basic information of actual information message should contain
the data element items and descriptions shown in Figure 14.

Figure 14 — Transport means basic information (continued) of actual information message
6.2.2.2.5 Transport means basic information (continued)
Continued from Figure 14, transport means basic information of actual information message should contain
the data element items and descriptions shown in Figure 15.

Figure 15 — Transport means basic information (continued) of actual information message
6.2.2.2.6 Transport means basic information (continued)
Continued from Figure 15, transport means basic information of actual information message should contain
the data element items and descriptions shown in Figure 16.

Figure 16 — Transport means basic information (continued) of actual information message
6.2.2.2.7 Transport means basic information (continued), calling location information and trailer
Continued from Figure 16, transport means basic information, calling location information and trailer of
actual information message should contain the data element items and descriptions shown in Figure 17.

Figure 17 — Transport means basic information (continued), calling location information and
trailer of actual information message
6.2.2.3 Message description
6.2.2.3.1 Header
Header of actual information message is shown in Table 9.

Table 9 — Header of actual information message
Record 00 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 00. M
2 Message type code an.6 Same as UNCL 1001 code ID M
3 Document description an.35 O
4 Document function code an.1 9 - original, 2 - addition, 3 - deletion, 4 - change M
5 Document sender name an.35 M/O
6 Document sender code an.17 O/M
7 Document receiver name an.512 M/O
8 Document receiver code an.17 O/M
9 Document creation date and time an.19 CCYYMMDDHHMMZHHMM M
10 Document issue date and time an.19 CCYYMMDDHHMMZHHMM M
11 Free text an.512 O
6.2.2.3.2 Other receivers
Other receivers of actual information message are shown in Table 10.
Table 10 — Other receivers of actual information message
Record 01 O
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 01. M
2 Document receiver name an.512 M/O
3 Document receiver code an.17 O/M
4 Free text an.512 O
6.2.2.3.3 Transport means basic information
Transport means basic information of actual information message is shown in Table 11.
Table 11 — Transport means basic information of actual information message
Record 10 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 10. M
2 Transport mode name an.17 M/O
3 Transport mode code an.1 O/M
4 Transport means name an.35 M/O
Ship is IMO number, aircraft is aircraft reg-
istration number, railway is train number,
5 Transport means ID an.35 O/M
and vehicle is engine number + vehicle shelf
number.
6 Import or export indicator code an.1 I-Import, E-Export M
7 Conveyance reference number an.17 M
8 Nationality code an.3 M
Declaration agent representative per-
9 an.35 O
son name
10 Customs office of declaration code an.35 M

TTabablele 1 111 ((ccoonnttiinnueuedd))
Record 10 M
No. Name Format Unit/code of measurement Constraint
11 First arrival location name an.256 M/O
12 First arrival location code an.35 O/M
First arrival location in customs terri-
13 an.19 M
tory date and time
14 Customs office of exit code an.35 M
15 Customs office of transit code an.35 O
16 Transport means net weight measure n.14 Unit:  Ton (t) O
17 Transport equipment quantity n.6 Unit:  TEU O
18 Brief goods description an.256 O
19 Carrier name an.512 M/O
20 Carrier code an.17 O/M
21 Carrier address an.512 O
22 Carrier agent name an.512 M/O
23 Carrier agent code an.17 O/M
24 Carrier agent address an.512 O
25 Operator name an.35 M/O
26 Operator code an.17 O/M
27 Place of departure name an.256 M/O
28 Place of departure code an.35 O/M
29 Place of arrival name an.256 M/O
30 Place of arrival code an.35 O/M
31 Transport means stay reference an.35 O
32 Routing country code an.2 O
33 Previous calling location name an.256 M/O
34 Previous calling location code an.35 O/M
35 Next calling location name an.256 M/O
36 Next calling location code an.35 O/M
37 Estimated arrival date and time an.19 CCYYMMDDHHMMZHHMM M
38 Estimated departure date and time an.19 CCYYMMDDHHMMZHHMM O
39 Actual arrival date and time an.19 CCYYMMDDHHMMZHHMM M
40 Free text an.512 O
6.2.2.3.4 Calling location information
Calling location information of actual information message is shown in Table 12.

Table 12 — Calling location information of actual information message
Record 20 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 20. M
2 Port call sequence number an.10 M
3 Calling location name an.256 M/O
4 Calling location code an.35 O/M
5 Calling terminal name an.256 O
6 Estimated arrival date and time an.19 CCYYMMDDHHMMZHHMM O
6.2.2.3.5 Trailer
Trailer of actual information message is shown in Table 13.
Table 13 — Trailer of actual information message
Record 99 M
No. Name Format Unit/code of measurement Constraint
1 Record ID n.2 Record type is 99. M
2 Total record document n.6 Including head record and trailer record M
6.2.3 Arrival report message
6.2.3.1 Basic requirements
6.2.3.1.1 Message name: arrival report message.
6.2.3.1.2 Message sender: transportation enterprises, such as shipping companies, consignors and freight
forwarders. Message receiver: destination units for transporting goods, such as ports, airports, railway
stations, freight stations and regulatory authorities.
6.2.3.1.3 The message should provide the arrival information of transport means and goods.
6.2.3.2 Message structure
6.2.3.2.1 Overview
Arrival report message shall consist of header, other receivers, transport means basic information,
transport document information, calling location information, goods loading/unloading record, goods
item information, dangerous goods and reefer information, transport equipment information and trailer.
Figure 18 shows the general overview of the message.

Figure 18 — Overview of actual report message
6.2.3.2.2 Header
The header of arrival report message should contain the data element items and descriptions shown in
Figure 19.
Figure 19 — Header of arrival report message
6.2.3.2.3 Other receivers and transport means basic information
Other receivers and transport means basic information of arrival report message should contain the data
element items and descriptions shown in Figure 20.

Figure 20 — Other receivers and part of transport means basic information of arrival report message
6.2.3.2.4 Transport means basic information (continued)
Continued from Figure 20, transport means basic information of arrival report message should contain the
data element items and descriptions shown in Figure 21.

Figure 21 — Transport means basic information (continued) of arrival report message
6.2.3.2.5 Transport means basic information (continued) and transport document information
Continued from Figure 21, transport means basic information and transport document information of
arrival report message should contain the data element items and descriptions shown in Figure 22.

Figure 22 — Transport means basic information(continued) and transport document information of
arrival report message
6.2.3.2.6 Transport document information (continued)
Continued from Figure 22, transport document information of arrival report message should contain the
data element items and descriptions shown in Figure 23.
Figure 23 — Transport document information (continued) of arrival report message

6.2.3.2.7 Transport document information (continued) and calling location information
Continued from Figure 23, transport document information and calling location information of arrival
report message should contain the data element items and descriptions shown in Figure 24.
Figure 24 — Transport document information (continued) and calling location information of
arrival report message
6.2.3.2.8 Goods loading/unloading record
Goods loading/unloading record of arrival report message should contain the data element items and
descriptions shown in Figure 25.
Figure 25 — Goods loading/unloading record of arrival report message

6.2.3.2.9 Goods item information
Goods item information of arrival report message should contain the data element items and descriptions
shown in Figure 26.
Figure 26 — Goods item information of arrival report message

6.2.3.2.10 Goods item information (continued) and dangerous goods and reefer information
Continued from Figure 26, goods item information and dangerous goods and reefer information of arrival
report message should contain the data element items and descriptions shown in Figure 27.
Figure 27 — Goods item information (continued) and dangerous goods and reefer information of
arrival report message
...