Loading
 

RACEAN Business Rules

​ Message Mapping

User Data Dictionary

Data Dependencies

  1. A request for RACEANs must be electronically reported.
  2. Clients must be registered “Accredited Clients” or acting on behalf of registered “accredited clients” to transact the RACEAN message
  3. EDI generated RACEAN 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. RACEANs cannot be amended or withdrawn.
    1. RACEANs (ACEAN Accredited Client Export Authority Number) may be cancelled by the Accredited Client Managers.
  6. An RACEAN in error will be rejected with an error message.
  7. Receipt of an RACEAN will generate a CONTRL response message, notifying CCF acceptance or rejection.
  8. RACEAN messages will generate a business response (RACEANR) from the ICS containing:
    1. A list of valid ACEANs equal to the number requested in the RACEAN message.
  9. Up to 9999 ACEANs may be requested in a single message.
  10. An accredited client or the party representing them may not request more ACEANs during a transaction than the amount negotiated within their accredited client agreement.
  11. No ACEAN may be used after the expiry of a client’s accredited client agreement, or following the cancellation of the ACEANs by Customs.

RACEAN (Request ACEAN)​

Data Element Usage Conditions
Header
Sender Reference Mandatory
Sender Reference VersionMandatory
Reporting Party IdMandatory
Accredited Client Party IdMandatory
Agent Party IdOptional
Number of ACEANs Requested Mandatory

V 1.0 22 OCT 2002