AIRINT Business Rules I

​​ Message Mapping

User Data Dictionary

AIRINT - General Rules

1. The valid Message Function Codes for an AIRINT are:
   1. Original (9)
2. AIRINT messages must quote a unique Sender Reference Number. The ICS will use this number and the associated 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 AIRINT 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 AIRINT message will be reported in an AIRINT Response message (AIRINTR).
6. Any advice messages resulting from the AIRINT message will be reported in an AIRINTR Response message (AIRINTR).
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.

AIRINT - Processing Rules

1. AIRINT messages are sent by carriers, freight forwarders and service providers to the Department detailing the importation of air cargo consignments and an associated Underbond Movement Request.
2. Goods reported in an AIRINT are limited to single consignments of imported goods that include the following.
   1. Reportable Documents
   2. Personal Effects (PE's)
   3. Transhipment Cargo
3. An AIRINT provides details of cargo consignments that will be moved between licensed premises under Customs control.
4. AIRINT messages must be reported to the Department within a specified time of the aircrafts arrival. See Import Cargo Reporting Timeframes for more detail.
5. A Cargo Status Advice (CARST) will be generated when the following events occur.
   1. There is a valid AIRIAR relevant to the goods reported in the AIRINT.
   2. The aircraft has left its last overseas port of departure.
   3. The screening period has expired.
6. The information supplied in the AIRINT will be used to create separate Cargo Report and Underbond Movement Request records in the ICS.
7. The ICS will validate and process the Cargo Report before the Underbond Movement Request.
8. The entire AIRINT will be rejected if the Cargo Report fails the validation process.
9. If the Cargo Report validates successfully an attempt to validate the Underbond Movement Request will be undertaken.
10. The ICS will reject the Underbond Movement Request and generate an error message if the Underbond Movement Request fails to validate.
11. 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.
12. An AIRINT message will be rejected if the report is submitted with the same Unique Identifier as an existing Air Cargo Report. Air Cargo Reports are uniquely identified by:
    1. Airline Code;
    2. Flight Number;
    3. Date of Arrival;
    4. Master Air Waybill (MAWB); and
    5. House Air Waybill (HAWB) (if applicable)
13. Once the Cargo Report and the Underbond Movement Request have been validated, the AIRINT ceases to be an actionable document. Both documents can then only be amended separately via the corresponding AIRCR and UBMREQ messages.
14. Consignee, Consignor and Notify Party names and addresses can be provided in either structured or unstructured format.
15. All port references are to be supplied in UNLOCODE format.
16. For more rules relating to Air Cargo Reporting and Underbond Movement Requests refer to the rules for the AIRCR and UBMREQ messages.

Data Dependency Table

An Integrated Air 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 Business Specific Format (BSF) of the Integrated Air Cargo Report Document where the document is considered an "Original". The table defines the attributes that make up this document and details their structure within the Integrated Air Cargo Report Document.

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

V2.4 30 AUG 2005