SEAINT Business Rules

​ Message Mapping

User Data Dictionary

SEAINT - General Rules

1. The valid Message Function Codes for an SEAINT are:
   1. Original (9)
2. SEAINT 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 message must be set at 1 or greater.
4. Before the SEAINT message is processed at the application level:
   1. All leading and trailing non significant 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 SEAINT message will be reported in an SEAINT Response message (SEAINTR).
6. Any advice messages resulting from the SEAINT message will be reported in an SEAINTR Response message (SEAINTR).
7. The maximum number of errors and advices that can be reported will be 50. No further errors or advices will be processed once the maximum number allowed for the AIRINT has been reached.

SEAINT - Processing Rules

1. SEACR messages are sent by carriers, freight forwarders and service providers to the Department detailing the importation of sea cargo consignments and an associated Underbond Movement Request.
2. A SEAINT provides details of cargo consignments that will be moved between approved premises under customs control.
3. SEAINT messages must be reported to the Department within a specified time of the vessels arrival. See Import Cargo Reporting Timeframes for more detail.
4. The information supplied in the AIRINT will be used to create separate Cargo Report and Underbond Movement Request records in the ICS.
5. The ICS will validate and process the Cargo Report before the Underbond Movement Request.
6. The entire AIRINT will be rejected if the Cargo Report fails the validation process.
7. If the Cargo Report validates successfully an attempt to validate the Underbond Movement Request will be undertaken.
8. The ICS will reject the Underbond Movement Request and generate an error message if the Underbond Movement Request fails to validate.
9. If the Cargo Report component of the AIRINT validates successfully but the Underbond Movement Request fails validation then the Underbond Movement Request must be re-submitted in a separate UBMREQ request.
10. A SEAINT message will be rejected if the report is submitted with the same Unique Identifier as an existing Sea Cargo Report. Sea Cargo Reports are uniquely identified by:
11. 1. Vessel Identifier;
    2. Voyage Number;
    3. Ocean Bill of Lading; and
    4. House Bill of Lading (if applicable).
12. Once the Cargo Report and the Underbond Movement Request have been validated, the SEAINT ceases to be an actionable document. Both documents can then be individually updated and processed in accordance with their relevant business rules.
13. Consignee, Consignor and Notify Party names and addresses can be provided in either structured or unstructured format.
14. All port references are to be stated as a valid five (5) character UNLOCODE.
15. For more rules relating to Sea Cargo Report and Underbond Movement Request attribute processing, refer to the rules within SEACR and UBMREQ.

Data Dependency Table

An Integrated Sea Cargo Report Message can only be Created. The mechanism for carrying out this transaction 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

The following table models the data elements of the Integrated Sea Cargo Report Document where the document is considered an "Original".

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

V2.3 - 21 OCT 2004