CTOREM Business Rules

​ Message Mapping

User Data Dictionary

Data Dependencies

1. CTO Removal (CTOREM) Notices must be electronically reported.
2. A CTOREM may contain a maximum of 99 lines per transaction.
3. EDI generated CTOREM 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.
4. The version number for an Original (9) message must be set at 1 or greater.
5. Amendment, Replacement or Withdrawal of a CTOREM is restricted to the reporting party.
6. A CTOREM cannot be amended or withdrawn if it has already been withdrawn.
7. Replacement CTOREM messages require full data replacement, but with the message function code set to 5 (Replace).
8. Each Amendment, Replacement or Withdrawal CTOREM 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.
9. Up to 998 Amendment, Replacement and Withdrawal CTOREMs can be submitted.
10. Amendments, Replacements or Withdrawals for which no original exist will be rejected by the ICS.
11. When an Amendment, Replacement or Withdrawal 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 not greater than the existing report the ICS will reject the change and send a CUSRES notifying of the rejection, and the latest Sender Reference version number stored by the Department.
12. The ICS will always accept and process Amendment, Replacement or Withdrawal messages where the Sender Reference version number is greater than the existing stored report.
13. Receipt of a CTOREM will generate a CONTRL response message, notifying CCF acceptance or rejection.
14. Before the CTOREM message is processed at the application level:
    1. All non-significant leading and trailing blanks will be stripped;
    2. Multiple spaces will be compressed.
15. On completion of ICS processing the Department will return a CUSRES message to indicate ICS acceptance, rejection or error conditions:
    1. The Department will return a Header level status of Error or Clear.
16. Cargo Terminal Operators are required to report Removal of export cargo to the Department, within a prescribed timeframe of removal of the cargo from the CTO.
17. The CTO Establishment id is used to identify whether the consignment was intended to be exported by air, or by sea.
18. A CTOREM may be used to report the movement of up to 999 lines of cargo from a CTO premise.
19. CTOREM line numbers need not be contiguous, or sequential, however duplicate line numbers will result in rejection of that CTOREM message:
    1. Valid line numbers for a CTOREM are 1 to 9999;
    2. Deleted line numbers need not be re-used to keep the total number of lines at or below 999;
    3. The Department will identify line data by the line number reported to the Department in the CTOREM message.
20. 19. Each line of a CTOREM must have:
    1. one container, one break bulk shipment, or one air way-bill; reporting
    2. one Customs Authority Number (CAN) or one Exempt line code.
       1. A CAN may be an Export Declaration Number, a Consolidation Reference Number, a Transshipment Number or an ACEAN.
21. A CAN may be reported against multiple lines of multiple CTOREM messages:
    1. CRNs, ACEANs and Underbond EDNs may only be reported against a single CTO.
22. A CTO may only report removal of goods that were reported to Customs as being received at the CTO.
23. Line action codes are not required for Original or Replacement messages.
24. Where a Withdrawal CTOREM message is sent, all header information is to be reported, as line level information is not required for deletion.
    1. The withdrawal message is to quote a new version number for the CTOREM to be withdrawn.
    2. The message function code is to be set to 50 (Withdraw).
25. To amend a CTOREM the following data items are required:
    1. Full header details;
    2. The line number of any line/s to be inserted, amended or deleted;
    3. A line action code for each line/s to be inserted, amended or deleted;
    4. Full line details for each line/s to be inserted or amended.
26. Any attempt to insert a line that already exists, or to amend or delete a line that does not exist will result in rejection of the amending message.
27. To Delete a line reported on a CTOREM the line number and line action code are the only line level information required.
28. Deletion of a CTOREM line should only be undertaken for lines that were mistakenly reported to the Department.
29. On Deletion of a line the goods previously reported in that line will be seen as residing at the CTO.
30. When the ICS is unavailable a contingency exemption code will be required. A client wishing to export goods cannot submit an Export Declaration (EXD). Instead, they must obtain a contingency CAN from the Department.
31. If a consignment has been received at a CTO, once the system has been recovered the contingency exemption code and contingency CAN will be quoted on a CTO Removal Notice (CTOREM)
32. The format for the Contingency CAN is an14, this will be the only validation for the Contingency CAN.

CTOREM (CTO Removal Notice) - Data Dependencies

Header

Lines

V1.4 15 JUN 2004