Loading

Departure Report (DEPART) Business Rules

Message Mapping

User Data Dictionary

Data Dependencies

  1. Departure Reports must be electronically reported.
  2. EDI generated DEPART messages must quote a unique Sender Reference. 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. Replacement or withdrawal of a DEPART message is restricted to the reporting party.
  5. A DEPART cannot be amended or withdrawn if it has already been withdrawn.
  6. Replacement DEPART messages require full data replacement, but with the message function code set to 5 (Replace).
  7. Each replacement DEPART message will be considered to be a new version of the message. For each version of a message the version number must be unique and increment upwards, to facilitate ICS processing.
  8. Up to 998 Replacement DEPARTs can be submitted.
  9. Replacements for which no original exist will be rejected by the ICS.
  10. When a replacement is received the ICS will compare the Sender Reference and Sender Reference version number with the most recent version of the report which is stored in the ICS. Where the Sender Reference version number is equal to or less than the existing report the ICS will reject the replacement and send a CUSRES notifying of the rejection, and the latest Sender Reference version number stored by the Department.
  11. The ICS will always accept and process replacements where the Sender Reference version number is greater than the existing stored report.
  12. Withdrawal DEPART messages require quotation of all data quoted in the most recent version of the DEPART message to be withdrawn. The message function code is to be set to 50 (Withdraw).
  13. Receipt of a DEPART message will generate a CONTRL response message, notifying CCF acceptance or rejection.
  14. Receipt of a DEPART message will start the 3 day count period for the reporting of the Export Main Manifest reporting.
  15. Before the DEPART message is processed at the application level:
    1. All leading and trailing blanks will be stripped;
    2. Multiple spaces will be compressed.
  16. All port references are to be stated as a valid five (5) character UNLOCODE.
  17. All dates/times quoted are to be given in the local date/time in the port or airport where the reported vessel or aircraft is departing from.

DEPART (Departure Report) - Data Dependencies

Data ElementUsageConditions
Header
Transaction TypeMandatory
Sender Reference Mandatory
Sender Reference VersionMandatory
Reporting Party IdMandatory
Mode of TransportMandatory
Departure CTO Establishment IdMandatory
Carrier Party IdConditional Conditional on 'Mode of Transport'.
  • Mandatory when Mode of Transport is Sea.
Date of DepartureMandatory
Vessel IdConditional Conditional on 'Mode of Transport'.
  • Mandatory when Mode of Transport is Sea.
Mandatory when Departure CTO Establishment Id is a Marine CTO.
Voyage NumberConditional Conditional on 'Mode of Transport'.
  • Mandatory when Mode of Transport is Sea
Flight NumberConditional Conditional on 'Mode of Transport'
  • Mandatory when Mode of Transport is Air
Airline CodeConditional Conditional on 'Mode of Transport'
  • Mandatory when Mode of Transport is Air
Destination PortMandatory
Time of DepartureMandatory

V1.4 07 Jun 2004