Courses / South African Customs Declarations

Submitting, responses and after release

A CUSDEC goes out, CUSRES statuses come back, and the declaration lives on through amendments and records.

Module 5 of 63 lessonsAbout 40 minQuiz: 6 questions
ExecuteSettle

Lesson 1 · free to read

How a declaration reaches SARS: CUSDEC out, CUSRES back

South African declarations are sent by Electronic Data Interchange (EDI). Section 101A of the Act provides for it, and the Rules make it compulsory for anyone above SARS's small manual allowance (ten declarations a month of up to ten lines each).

The messages. SARS uses the UN/EDIFACT standard and publishes message implementation guidelines for each message.

MessageDirectionWhat it does
CUSDECTo SARSThe customs declaration, including the SAD 509 invoice and worksheet data
CONTRLFrom SARSAcknowledges that the file arrived and that its syntax is valid, or rejects it
CUSRESFrom SARSThe customs response: release, stop, rejection, request for documents and more

Think of CONTRL as the post office ("your letter arrived and is readable") and CUSRES as the reply ("here is what customs decided"). A CONTRL acceptance is not a release.

What happens after submission (SC-CF-55 and A09):

  1. The gateway checks the message format. A file that cannot be read is rejected with an error code.
  2. SARS's declaration system validates the content: mandatory fields, code lists, registered importer, VAT number, tariff check digits, calculations. A valid declaration receives a Movement Reference Number (MRN), which must be quoted in all later correspondence.
  3. If payment is due, the declaration waits for it. SARS notifies the declarant of a status, in general, only after payment.
  4. The risk engine either releases the goods or selects them for documents or inspection.

Two typical sequences from SARS's annexure on response messages:

ScenarioCUSRES statuses in order
Duty payable, no intervention7 (ready for payment), then 1 (release)
Selected for documents7, then 13 (supporting documents required), 33 (documents received), 1 (release), 34 (case closed)

Who sends it. The declarant's software, usually through a service provider, sends the CUSDEC under the declarant's EDI registration. SARS ties a sending profile to a registered client, so a clearing agent that changes software provider must make sure its EDI registration names the new sender.

A lesson from building SA declarations. In early testing against SARS's test gateway, every CONTRL came back accepted while the CUSRES rejected the declaration for content: an unregistered test importer, a VAT number SARS did not recognise, a container number with a wrong check digit, tariff codes without check digits, and a missing preference code on an A 11 00 line. Syntax passing tells you nothing about content. Validate content before you send.

The rest of this module

  1. Reading responses: release, stops, rejections and requests
    The CUSRES status code tells you what to do next; a police stop arrives by a different route.
  2. After release: amendments, cancellations and records
    Changes go through an amended declaration, and the file must be kept for at least five years.

Carry on with the course

The other lessons and the quiz are in the course itself, where your progress is saved and counts towards the certificate: South African Customs Declarations.

Next module: Hands-on in tradePhlo