Cargo List Report (CARLST) Business Rules

​​ Message Mapping

User Data Dictionary

CARLST - General Rules.

1. The valid Message Function Codes for a CARLST a
   1. Original (9)
   2. Change (4)
   3. Withdraw (50)
2. CARLST messages must quote a unique Sender Reference. The ICS will use this number and the associated Sender Reference Version Number to ensure duplicate messages are not processed.
3. The version number for an Original (9) message must be set at 1 or greater.
4. Before the CARLST message is processed at the application lev
   1. All non significant leading and trailing blanks will be stripped;
   2. Multiple spaces will be compressed;
   3. Illegal characters will be removed; and
   4. All nulls will be converted to blanks.
5. Any errors in an CARLST message will be reported in an CARLST Response message (CARLSTR).
6. Any advice messages resulting from the CARLST message will be reported in a CARLST Response message (CARLSTR).
7. The maximum number of errors and advices than can be reported will be 50. No further errors or advices will be processed once the maximum number allowed for CARLSTR has been reached.
8. A Change to an CARLST will be rejected if there is no difference between the Original and the Change CARLST.
9. Each Change CARLST message will be considered to be a new version of the message. For each version of a message the senders reference version number must be unique and incremented from the previous version.
10. Change or Withdraw CARLST messages for which no original exist will be rejected by the ICS.
11. The Withdrawal of an CARLST is for the entire record.
12. Once a Cargo List Report has been created, amended or withdrawn on line through the ICS Interactive Facility, future processing via EDI will not be permitted.
13. Where the Message Function Code is 9 (Original) , the valid Line Action Code is I (Insert).
14. Where the Message Function Code is 4 (Change) and the Line Action Code is populated, the valid codes are I (Insert), A (Amend) or D (Delete).
15. To insert a new line to an existing record, the Message Function Code is 4 (Change) and the Line Action Code is I (Insert).
16. To amend unprotected header details, the Message Function Code is 4 (Change) and the Line Action Code is not populated.
17. To amend a line record, the Message Function Code is 4 (Change) and the Line Action Code is A (Amend).
18. To delete a line record, the Message Function Code is 4 (Change) and the Line Action Code is D (Delete).

CARLST - Processing Rules

1. A CARLST allows a Cargo Reporter to report cargo on an international vessel that cannot be reported on a Sea Cargo Report (SEACR).
2. Cargo that qualifies for reporting via the CARLST includes:
   1. Cabotage (i.e. break bulk or containerised coastal cargo)
   2. Empty (i.e. empty containers)
   3. Domestic Export (i.e. break bulk or containerised cargo destined for discharge in Australia prior to exportation)
3. If the Cargo Type is not FCL then the Cargo Identifier is a Booking Reference Number or a Bill number identifying the Break Bulk or Bulk cargo.
4. The ICS will attempt to link the CARLST with the corresponding Impending Arrival Report (SEAIAR) by:
   1. Vessel Identifier;
   2. Voyage Number and
   3. Port of Discharge
5. The Customs Cargo Report Identifier for a CARLST is a concatenation of the:
   1. Vessel Identifier,
   2. Voyage Number;
   3. Port of Discharge; and
   4. Cargo Responsible Party ID
6. The Line Identifier for a CARLST is identified by the Cargo Identifier.
7. CARLST messages must be reported to the Department within a specified timeframe. See Import Cargo Reporting Timeframes for more detail.
8. The Cargo Responsible Party ID field must be populated with the Customs Client ID or the ABN of the Cargo Responsible Party when submitting a report on behalf of a Cargo List Reporter.
9. A Change to an original CARLST may only include changes to Cargo List Line information.
10. The Protected line attributes of a CARLST are:
11. 1. Cargo Type
    2. Cargo Code
    3. Cargo Identifier

Data Dependency Tables

A Cargo List Message can be Created, Changed or Withdrawn. The mechanism for carrying out these transactions utilises Message Function Code. The Message Function Code is a document level transaction indicator that is applied to the document.

Data Dependency Table for Original and Change

The following table models the data elements of the Cargo List Document where the document is considered an "Original" or a "Change".

Data Dependency Table for Withdrawal

NOTE: for further details in relation to a Business Term, refer to the User Data Dictionary.

V 2.5 5 DEC 2004