EXPED1 Business Rules

​ Message Mapping

User Data Dictionary

Data Dependencies

1. Exports Periodic Declarations Option1 (EXPED1) must be electronically reported.
2. An EXPED1 may contain a maximum of 300 lines per transaction (ie 300 ACEANs each with up to 99 AHECCs)
3. Multiple EXPED1 messages may be used to build a periodic declaration containing up to 999 lines.
4. EXPED1 messages may only be transacted by “accredited clients”, or parties representing them.
5. EXPED1 messages are used to report full details of goods exported on ACEANs.
   1. Multiple Periodic declarations may be created for the same settlement period.
6. AHECCs must be associated with the specific ACEAN to which they apply in EXPED1 messages.
7. The FOB Currency Code is to be reported once and nominates the currency code that will be used for line level FOB Value reporting.
8. If “aggregated” functionality is required an EXPED2 message must be used.
9. An EXPED1 message may include information relating to up to 300 lines (shipments)
   1. Multiple EXPED1 change messages may be used to build a periodic declaration detailing up to 999 lines (shipments)
   2. Valid line numbers are 1 ... 9999.
   3. The Department will use the line number as reported by the user.
10. EDI generated EXPED1 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.
11. The version number for an Original (9) message must be set at 1 or greater.
12. EXPED1 messages may not be withdrawn electronically.
13. Requests for the withdrawal of EXPED1 messages must be lodged manually with the Customs Accredited Client manager.
14. Change, Replacement, or Replace Heading Section EXPED1 message are restricted to the accredited client or the party representing them.
15. Replacement EXPED1 messages require full data replacement, but with the message function code set to 5 (Replace).
16. EXPED1 messages with “replacement to the heading section” allows changes to the information in all of the segments in the heading section. This includes position number 0010 UNH 0120 NAD and 1360 UNT
17. The message function code in a “heading section replace” must be set to 20
18. Each Change, Replacement, Replace Heading Section only EXPED1 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.
19. Up to 998 Change, Replacement, or Replace Heading Section only EXPED1 messages can be submitted.
20. Change, Replacement, or “Replace Heading Section only” EXPED1 messages for which no original exist will be rejected by the ICS.
    1. Withdrawal EXPED1 messages cannot be lodged electronically.
21. When a Change, Replacement, or “Replace Heading Section only” 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 .
22. An EXPED1 message cannot be Changed, Replaced, or have the heading section replaced if it has already been withdrawn.
23. The ICS will always accept and process Change, Replacement or Replacement of the Heading section messages where the Sender Reference version number is greater than the existing stored report.
24. Receipt of an EXPED1 will generate a CONTRL response message, notifying CCF acceptance or rejection.
25. Before the EXPED1 message is processed at the application level:
    1. All non-significant leading and trailing blanks will be stripped;
    2. Multiple spaces will be compressed
26. On completion of ICS processing the Department will return a EXPED1R message to indicate ICS acceptance, rejection or error conditions:
    1. The Department will return a Header level status of Error or Clear;
    2. The Department will return a validation status for each line reported to the Department .
    3. The Department will return a periodic declaration number.
27. All country references are to be stated as a valid two (2) character UN Country Code.
28. Line action codes are not required for Original or Replacement messages.
29. To amend an EXPED1 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.
30. 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.
31. Goods origin code is only to be reported for goods of foreign origin.

EXPED1 (Export Periodic Declaration Non-Aggregated) - Data Dependencies

Header

Line

V 1.4 19 MAR 2003