​​​​​​​The message specifications provided in the SDG have been developed by the Department from the EDIFACT standard messages of the UN EDIFACT 99B message syntax directory. The representations of messages in the SDG provide developers, and others, with the information necessary to transact business with theIntegrated Cargo System (ICS).

ICS Messages

This table links to the information necessary to develop EDI messages for use with the ICS.
Link to CCF Business Rules.

UN/EDIFACT Messages - An Overview

UN/EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport) is the International Standard for EDI (Electronic Data Interchange) and is administered by the United Nations. EDI is defined as the "computer-to-computer exchange of data related to business transactions using an agreed upon formats and networks". Besides being an acronym UN/EDIFACT is also:

• A set of rules
• Data elements, segments, codes, syntax rules
• Messages

There are over two hundred United Nations Standard Messages available. The Department will use eight UN/EDIFACT messages from the D.99b directory. A description of these of the messages is included below.

EDIFACT Message Types

The ICS will utilise the following UN/EDIFACT message types.

CONTRL (Syntax and Service Report)

The CONTRL (Control Message) is used to acknowledge a received interchange and list any interchange, functional group or message errors contained therein. Where a syntax error has been detected, the control message indicates the action to be taken by the recipient as a result of the check.

During a syntactical check, the interchange, or part of it, is checked for compliance with:

• the EDIFACT syntax rules (ISO 9735), including rules for use of service segments
  
  
• the syntactical aspects in specifications for the message type(s) received
• any additional agreements between partners regarding use of the syntactical rules. Such agreements shall conform with ISO 9735

Under the ICS the Department will use the CONTRL Message error response whenever an interchange containing a syntactical error is received at the EDI gateway. Such a Control Message will notify the user of any syntactical errors requiring correction before the interchange can be accepted for processing by the ICS.

CUSCAR (Customs Cargo Report)

The CUSCAR message is used to facilitate the transfer of data from the carrier of import/export cargo to a Customs administration for the purpose of meeting the legislative requirements of a particular Customs administration.

Under the ICS the CUSCAR message will be used to report single or multiple consignments of goods, prior to their arrival in Australia.

CUSDEC (Customs Declaration)

The CUSDEC message permits the transfer of data from a declarant to a Customs administration for the purpose of meeting legislative and/or operational requirements in respect of the declaration of goods for import, export or in transit.

Under the ICS importers, brokers, exporters or their agents will use the CUSDEC message to lodge import and export entries.

CUSPED (Customs Periodic Declaration)

The CUSPED message allows the transfer of data from a declarant to a Customs administration for the purpose of meeting the legislative requirements of the Customs administration in relation to the periodic declaration of goods being imported into, or from Australia.

Under the ICS the CUSPED message will be used by Customs Accredited Clients to provide Customs with additional information not provided by the declarant in the Request for Cargo Release message.

CUSREP (Customs Conveyance Report)

The CUSREP message permits the transfer of data from a carrier to a Customs administration for the purpose of meeting legislative reporting requirements in respect to the means of transport on which the cargo is to be carried.

The CUSREP message will be used to report both the impending and actual arrival of vessels/aircraft carrying cargo into Australia.

CUSRES (Customs Response)

The CUSRES message facilitates the transfer of data from a Customs administration to:

• Indicate whether the message received had errors when it was processed at the application level; and
• To inform message sender of the status of a Customs declaration or report.

Under the ICS Customs will use the CUSRES message to respond to importers, brokers, exporters, carriers and cargo handlers.

GENRAL (General Purpose Message)

The GENRAL message is used to facilitate early transmission testing, broadcasting known problem areas, transmission of text to clarify previous messages and transmission of small amounts of structured text. The message is intended to be independent of the business type or industry.

Under the ICS the Department will use the GENRAL message in relation to the control of cargo to be exported and to distribute reference files and relevant information business partners.

REMADV (Remittance Advice Message)

The REMADV message is a communication between trading partners providing a detailed accounting relative to a payment on a specific date. The message is intended to be independent of the business type or industry. Generally, the REMADV is a notice of a payment to be made.

Under the ICS Importers and brokers will use REMADV to advise the Department of payment for import entries.

ICS Messages​

Character Set for EDI Messaging

The character set required for all EDI Interchanges (inbound and outbound) is UNOC as defined by ISO 8859-1. The Department uses a sub-set of the full UNOC character set.

The syntax used is V3.

Data Representation Within the ICS

Where values are shown for the representation of data within this guide the following data value representations will be used:

If a value is to be indicated to be negative, it shall in transmission be immediately preceded by a minus sign e.g. -112

The minus sign should not be counted when computing the maximum field length of a data element. However, allowance has to be made for the character in transmission and reception.

Conditional and Mandatory Segments

The UN EDIFACT Standard Messages define segments within a message as being either Mandatory (M) or Conditional (C). To comply with the message standard. Entities defined as 'Mandatory' must be used at least once. Entities with the 'Conditional' designation are used as required.

The first column in the message specifications contains several codes, or usage indicators, which indicate the exact requirements for the construction of a valid message. The table below provides an explanation for these codes. They are:

Message Mapping Components

The Message Specifications contained in this guide detail the content and structure of the various messages being used by the ICS. For each of these messages, the required data items and the structure of the message are depicted using three different representations. These are the Message Specific Business Rules (Business Rules) , the Message Implementation Guidelines (MIG's) and the Data Dictionaries (User, Customs and Control) . The message specific information must be read in conjunction with the ICS Business Rules and the Data Dictionaries.

Message Mapping Representation

The presentation of Message Mapping information is provided in two parts. The first representation is the Message Segment Table, which provides an overview of the message structure. The second part is the segment definition, which provides guidance for the message segments utilised in the ICS.

The message segment tables detail the segments and segment groups used by the ICS. The table defines the requirement for inclusion of segments and provides a representation of segment group nesting.

Message segment tables are included with the message specifications. A table is included in the message specification for each business usage of a message.

This table uses the Impending Arrival Message (CUSREP) as an indicative example.

Segment Definitions

Segment Definitions are provided for every segment used in the ICS implementation. The definition of a segment lists all the data elements and composites and shows how each of these are to be used in the ICS. Segments which are not used in the ICS are not defined. An example of a segment definition is provided below.

DataElementSummary

V1.5 10 AUG 2004