CUSTOMS
Implementation
Landscape
May 9
2012
This is a working document, subject to update and clarification, to facilitate a
common view and understanding of developments and changes occurring as part
of the Customs Modernisation Programme.
1
Roadmap for
external
stakeholders
Customs Modernisation Implementation Landscape – ver. 2012.05.09
Table of Contents
Information for Stakeholders.................................................................................................................. 4
1.
Customs Modernisation – Release 3 (BLNS implementation) .................................................... 5
2.
Supplementary Components for Release 3 .............................................................................. 13
3.
New Tariff Management System (TMS) .................................................................................... 16
ANNEX A – Customs Status Codes (Code List 14) ............................................................................. 17
ANNEX B – Status Code Scenarios for Kopfontein ............................................................................ 19
ANNEX C – Glossary .......................................................................................................................... 20
ANNEX D – Excerpt of SARS Customs CUSCAR Data Mapping Guide - v-20-20120309 .................... 22
2
Customs Modernisation Implementation Landscape – ver. 2012.05.09
Updates to this document
Current updates are reflected in orange print
Date
Description
2012.01.24







2012.02.06






Page 4 > Item 1– clarification the customs code 70707070 will no longer be permitted at
Kopfontein.
Page 6 > Item 3 – clarified the need for IM4,IM5 and IM6 type SACU clearances to reflect a
procedure measure (rebate code), respectively.
Page 6 > Item 4 – clarified ambiguity concerning consolidation of local and foreign origin
goods in SACU consignments.
Page 7 > Item 4 – clarification concerning the submission of trader-initiated VOCs.
Page 7 > Item 4 – carriers are required to reflect the LRNs of any non-SACU clearances
separately on their road manifests.
Page 7 > Item 4 – notifying SARS intent to introduce full import/export permit controls, as
well as collection of environmental levy, fuel levy and Road accident fund levy at a future
date.
Page 8 > Item 8 – insertion of a new item to clarify the use of ‘payment code’ for SACU
transactions.
Page 4 > Item 1 – insertion of a paragraph to clarifythe withdrawal of Code 70707070.
Page 5 > Item 1 – clarification on requirements in respect of a vehicle breakdown.
Page 6 > Item 3 – clarification of available rebate items for SACU CPCs.
Page 7> Item 3 – insertion of a statement concerning processing of amendments of CCA
transactions at Kopfontein, post 10 February.
Page 7 > Item 4 – clarification on submission of amendment VOCs.
Page 8 > Item 6 – insertion of a paragraph clarifying the issue of surety bonds for ‘registered
traders’.
2012.02.07

Page 9 > Item 7 – amending structure for ‘master transport document number’.
2012.02.14

Page 6 > Item 3 – temporary workaround for SACU temporary imports.
2012.02.21

Various –requirements for Ramatlabama, imposition of electronic Import and Export
Control, as well as hyperlinks to reference materials available on the SARS Customs
Modernisation webpage.
2012.04.17

Page 13 > Item 4 –Deleted item 8 under “Customs Modernisation Release 3”. Inserted new
item4 under “Supplementary Components for Release 3”.
Page 20 > Annex D – Inserted excerpt of CUSCAR DMG reflecting changes for cargo
reporting.

2012.05.09
3

Page 8 > Item 4 -a new item 4 has been inserted titled “Application of certain International
CPCs at BLNS Land Borders”.
Page 9 > Item 5 – a new item 5 has been inserted titled “Application of BLNS CPC codes at
BBR and KOM”.
Customs Modernisation Implementation Landscape – ver. 2012.05.09
Customs Modernisation Implementation Landscape
Information for Stakeholders
To provide Customs stakeholders insight for planning and migration activities concerning SARS
Customs’ planned Modernisation implementations. This document should be considered a ‘living
document’ subject to update and elaboration as required.
4
Customs Modernisation Implementation Landscape – ver. 2012.05.09
1. Customs Modernisation – Release 3 (BLNS implementation)
Expected date for Trader Testing
-
Expected date for Implementation
Phased implementation1
Abstract Brief Description
To introduce the new Service Manager front end capability for internal Customs users
andto enable electronic supporting document functionalityin the cross-border SACU
environment. Simultaneously, a newcargo automation solution will be piloted for road
freight. Road cargo carriers are in the process of registering for electronic cargo reporting
and EDI communication with SARS.
Detail
Scope Description and Impact
1.
Customs Clearance - Commercial and Simplified Processing

BLNS rollouttakes the modernisation programme a step further with the migration
of cross border commercial clearance processing from the current CCA system to
the mainstream CAPE and Export systems.

The CCA system will be switched off with implementation at Kopfontein and at
remaining BLNS land borders thereafter. All other Customs SACU border posts will
continue to operate the CCA system until rollout of CAPE/Export systems at these
border posts occurs.

Clearance of commercial goods for import into South Africa will require a full
clearance under the following conditions –
–
Where the trader is a non-South African, such entity must register as an
Importer. In addition, this registration is subject to a relationship between
the foreign entity and a local “Agent” who will assume full liability of the
foreign entity. This partywill likewise have to register as an Agent which will
be a new client type on RAS. It is understood that a local clearing agent may
in the interim performs this role. Only a South African licensed clearing agent
can affect clearance and release of goods.2
–
Where the trader is a South African entity with an established place of
business in the RSA and is registered as an Importer/Exporter with Customs,
full customs clearance can be accomplished by utilising the services of a
licensed South African customs clearing agent.
1
Refer to Item 9 – Indicative rollout schedule for land borders
Full details concerning application for the various client types will be provided as soon as these are finalised.
2
5
Customs Modernisation Implementation Landscape – ver. 2012.05.09

The 70707070 code was introduced by SARS some years ago as a general code
which importers/exporters could use temporarily until they received formal
registration. The code is to be abolished nationally and will be introduced
incrementally with the implementation of Release 3 of the Customs
Modernisation programme at Kopfontein and subsequently at all remaining BLNS
land borders. All importers and exporters, local and foreign, must register and
declare their registration details on their Customs declarations. In the case of a
foreign principal, a South African registered agent must in all instances be utilised
to conduct business with SARS.
References -available on SARS Modernisation Website:



2 February 2012 - Letter to Clients - Registration for SACU Rollouts
8 February 2012 - Letter to Clients - Customs Registration Clarificationand
10 February 2012 - SACU Land Borders - Registration FAQ
Should a vehicle break down before it reaches the border and the cargo is
transferred to another vehicle, an amendment must be made to the manifest
prior to arrival reflecting the new vehicle registration number.
NOTES:
 Pending amendments to the Customs Rules, Rebate Item 407.02 and Schedule 1 of
the VAT Act will provide the basis for the above.
 Pending amendment to the Customs Rules concerning security policy which
amends the requirement for clearing agents to furnish the R 10 000 bonds per
branch office allowing them to conduct business at any branch office and not only
the ones for which a bond was furnished.
 In regard to (b) above, discretion will be applied in so far as what constitutes
‘commercial goods’ as this cannot merely be based on value.
Payment requirements
 Declarants should not supply the current CCA deferment number in the
‘Deferment Number/Financial Account Number’ field as the declarants’ customs
Code number will be used to determine the deferment account, i.e. this is in line
with the current CAPE process.

2.
All payments will be accommodated on the CAPE cash desk. The implication of this
is that all payments must be done at Kopfontein, and subsequent BLNS land
borders upon implementation.
Declaration Form and Clearance requirements
Manual capture of customs import and export declarations will be permissible. A
stipulation, however, is that the trader present the SAD500 declaration for capture at
the BLNS Land border. Some key criteria needs to be noted in this regard:
 Manual capturing– willonly occur for paper clearances at BLNS land borders.

Manual clearance limitations –a declaration may not exceed 10 line items. Only
10 manual import/export declarations per trader will be allowed per month.
NOTE:
6
Customs Modernisation Implementation Landscape – ver. 2012.05.09
In consideration of the limitations indicated above, traders who prepare manual
clearances prior to arrival at Kopfonteinshould continue to do so in the SAD500 format.
When presenting themselves at Kopfontein, they will present the declaration to the
Customs official for capture on the Customs system.
3.

CN-1 Customs Status Notification – to be printed by the Customs Legacy system
for all clearances at Kopfontein (EDI or manual). The CN1 indicates the customs
status for a given transaction. Together with the CN2 it is only required for
presentation to an officer at the exit gate to permit transport of the goods to the
other side of the border.

CN-2Summary Declaration– On arrival at the border post (entrance gate), the
haulier’s road manifest containing a list of all the LRN’smust be presented to
customs. It must contain a summary of all the consignments LRN’s on the truck:
–
The road manifest number will be captured onto the customs system allowing
the customs officer to view the status of all the declarations associated with
the road manifest.
–
Upon arrival, the latest CUSRES status will be forwarded to the declarant.
–
Only once all the relevant consignments have been “released” or
“conditionally released”, a CN2 will be printed by Customs and the driver may
proceed to the exit gate. The CN2 will be used as the gate-pass to exit the
border post on the South African side.
–
In cases where relevant declarations are ‘stopped’the driver will proceed into
the control area for further processing. Once fully processed and all the
statuses have been updated to reflect “released” or “conditionally released”,
the CN2 will be printed at the control area permitting the driver to proceed to
the exit gate.
Declaration Changes contemplated for BLNS Land Borders.
Note: No changes to the CUSDEC DMG are anticipated at this stage.

“Document/message name, coded” (routing code) on the BGM for BLNSclearances
must now reflect “929” and 830” for imports and export respectively.
BGM
BEGINNING OF MESSAGE
M
C002
DOCUMENT/MESSAGE NAME
C
1001
Document/message name, coded
C
an..3
929 = Import
930 = Import - Cross Border
830 = Export
831 = Export - Cross Border
General
 Cross Border declaration data requirements will follow that of International
Imports and Export clearances – as indicated in the CUSDEC DMG.
7
Customs Modernisation Implementation Landscape – ver. 2012.05.09

Declarants entering goods destined for SACUcountries must enter the code of the
customs office from which the goods are exiting the Republic in the “Office of
Entry” data field. For example: for Kopfontein implementation it will be “KFN”.

Clearances of goods under IM5 (D37-00) and IM6 (I78-76) must for purposes of
the VAT Act reflect the appropriate procedure measure (rebate item).
IM 5 (D37-00)
IM6 (I78-76)

Until further notice please use item 490.90 for temporary imports.
Possible Rebate items: 409.01; 409.02; 409.04; 409.05; or 409.06.
Clearances under IM4 (A13, A14 and A15)should reflect the appropriate procedure
measure (rebate item), if applicable.
Refer to Guide for Application of Customs Procedure Codes– on the SARS website.

When a rebate item (procedure measure) is declared, the rebate user code must
be inserted and must be equal to the importer.

If an amendment (VOC) is made to an entry that was processed on CCA1 system, a
manual procedure will need to be followed.

As of 24 February 2012, cross-border clearance at borders operating Release 3 will
process permits in respect of Import and Export Control electronically. Traders
transacting clearances through affected Release 3border posts must ensure that
they have applied for any required permit or risk having their clearances rejected.
Traders should also take note that the requirement to specify a ‘new’ or ‘used’
indicator for specified goods is likewise applicable.
Refer to 16 February 2012 -SACU Land Borders - Import & Export Control Measures – on SARS website.
Provides the respective Import and Export Control Gazettes.
4.
Application of certain International CPCs at BLNS Land Borders
To ensure proper clearance and release formalities on international goods, SARS has
identified the following requirements which service providers to the trade and traders
themselves need to adopt to ensure a more expeditious process. Kindly note that
current CPCs in operation at BLNS borders remain in force.
The following international CPCs for goods declared for clearance at BLNS land borders
are listed according to the specified scenario –
a) Goods of ‘non-SACU origin’ arriving into South Africa via the BLNS for consumption
in the Republic –
- A10(OL),A11(DP), A13(GR), A14(GR), A15(GR)
- D35(GR)
- E40(WH), E42(WE)
- I77(GR)
- J80(GR)
- K85(IR)
- L91(GR)
b) Free circulation goods exported from South Africa via the BLNS for destination
‘beyond’ the SACU region –
8
Customs Modernisation Implementation Landscape – ver. 2012.05.09
-
D36(EIG)
F51(EAS)
H60(ELG), H62(EIG), H63(EIG), H64(EIG), H65(EIG)
I75(ELG)
J83(ELG)
L90(ELG)
General rules to bear in mind:
- A declarant may declare goods for any of the specified international CPC’s
above upon clearance at a land border.
- All prevailing licenses, permits, prohibitions and restrictions will apply.
- Where a rebate item (procedure measure) is applicable this must be applied.
5.
Application of BLNS CPC codes at BBR and KOM
All existing BLNS CPCs will be available at both Beit Bridge and Komatipoort/Lebombo
offices subject to current rules.
6.
How are Customs Status Codes affected by the new systems at BLNS land borders?
 Declarants will receive CUSRES Status Notifications according to Code List 14.

CUSRES message sequence will be the same as for international imports and
exports, except CUSRES Status 8 (Proceed to Border),which will in all instances,
precede the following statuses:
1
2
3
4
5
9
Release
Stop/Detain
Conditional Release
Detain Other (OGA)
Conditional release - Detain Other (OGA)

Declarants may initiate an amendment (VOC) upon receipt of a Status 8 response.
However, this will not be possible on a Status 13, because a case would already
have been opened. In essence, SARS will accept an amendment if there is no case,
or where a case has been opened and subsequently closed.

Please note that VOC’s that have a financial impact, i.e. where the VAT is reduced,
will be processed via the refund process if the client elects the VAT to be
refunded.

Customs “commercial” clearance processing at BLNS land borders permit
clearances for the under-mentioned BLNS CPCs –
– A12-00 [IM4]
– B22-00 [IM8]
– D37-00 [IM5]
– D38-37 [EX3]
– H61-00 [EX1]
– H66-12 [EX3]
– I76-00 [EX2]
– I78-76 [IM6]
Customs Modernisation Implementation Landscape – ver. 2012.05.09
Note: All goods in ‘free circulation’ for SACU clearance purposes (as per above),
i.e. local RSA goods and imported goods on which duties and taxes have been
paid, may be consolidated on a single declaration until further notice.

Declarations with the following CPC codes processed under the international
import/export procedures may arrive at a SACU border post for onward
movement beyond SACU. TheLRN/s of such clearancesmust appear on the
carrier’s road manifest. The manifest must differentiate between SACU and
international movements, i.e. where a vehiclecomprises a mix of cross border and
international cargo, the LRNs should be groupedunder separately specifying local
and international goods.
–
–
–
–
–
–
–
–
–

7.
B20-00 [RIB]
B21-00 [RIT]
E42-37 [WE]
E43-40/41/42/44 [XIB]
E45-00/46/47 [ZIB]
F52-00/46/47[ZES]
F53-40/41/42/44 [XE]
H67-40/41/42/44 [XE]
H68-00/46/47 [ZE]
The automated processing of import/export permits and the payment of
environmental levy, fuel levy and road accident fund are currently being finalised
and will be implemented at a later stage.
Electronic Supporting Documents

Traders involved in cross border trade will now be able to transmit supporting
documents electronically when required to do so. A status 13 message initiates
the process upon which the declarant scans and appends such documents to a
Customs Case No. and transmits to SARS using the E@syScan facility.
NOTE: Where a trader does not have access to the Easy@scan facility, he/she may
present the documents to one of the four regional hubs for scanning, or bring the
document to Kopfontein branch office where the case will be processed manually.
8.
Registration and Trader Validation
 SACU brokers/importers operating deferment accounts in South Africa are to be
terminated on the Customs RAS system. This will occur according to BLNS country.
Therefore, since Botswana is the first country affected by this change, all existing
Botswana deferment account holders will be terminated for the Kopfontein
implementation.

10
SACU importers, exporters and road hauliers must registered as “foreign” entities
on the Customs RAS system. Consideration is given to convert the current SACU
clients (importer, exporter & haulier) to foreign clients but to only activate a client
after the nomination of an agent, signed by both parties and received by SARS.
Customs Modernisation Implementation Landscape – ver. 2012.05.09

The new client type “registered agent” as reflected in the draft rules will not be
required to furnish a bond nationally or per port of operation at time of “first”
application to register as a registered agent. SARS retains the prerogative,
however, to re-assess the agent (clearing agent – Broker and registered agent) to
determine whether the client is compliant / low risk; and, if found to be a risk /
non-compliant then a national bond could be requested.
Difference between a South African and Foreign Importer and Exporter –



A South African importer/exporter may submit their own clearances.
A foreign importer/exporter must appoint an ‘agent’, and such agent must
contract a South African customs broker to make customs clearance.
All “foreign” registrants (importers, exporters, road hauliers) must establish a
business relationship with a South African ‘agent’ who will be fully liable and
responsible to SARS for the acts of such foreign entity.
– This constitutes a new client typethat will include registration as an ‘agent for a
foreign entity’ and the furnishing of surety as determined by SARS.
– A South African licensed clearing agent (now referred to as a Customs Broker) will
be permitted to apply for registration as an ‘agent representing a foreign
registrant’. In such instance the broker’s customs code (TIN) will appear twice
on the declaration.

For the interim, the new ‘agent’s customs code number will be carried in the
Additional Information field on line 1, as follows:
– When inserting an ‘Agent representing a foreignImporter or Exporter’, the code
‘AFT’ as well as the associated customs code number must be inserted under
Additional information (SAD500 Box 44).
– When inserting an ‘Agent representing a foreign Haulier’, the code ‘AFH’ as well as
the associated customs code number must be inserted under Additional
information (SAD500 Box 44)3.
 SACU warehouses and rebate usersregistered with SARS will still remain active on
the Customs RAS system to facilitate declaration validations, until further notice.It
must, however, be noted that these entities will likewise be terminated in the
future and no new registrations will be permitted.
9.
Payment Method codes for Kopfontein implementation
 The following table provides for codes which are utilised for customs accounting
purposes on the CAPE system Code
F
Description
Any original declaration or declaration amendment (including refund vouchers of correction)
on which no duties or VAT is payable must be marked “F”.
3
Code List 19 (Additional Information Codes) will be updated to include these changes.
11
Customs Modernisation Implementation Landscape – ver. 2012.05.09
C
Any original declaration or amending declaration on which duties and / or VAT is payable
and the clearer elects to pay the duty and/or VAT by cash, must be marked “C”.
D
Any original declaration or amending declaration on which duties only, VAT only, or duty and
VAT is payable, and the clearer elects to defer such amount(s) must be marked “D”.
V
Any original declaration or amending declaration on which duties and VAT are payable and
the clearer elects to ‘defer the VAT’ and pay the duty, must be marked “V”.
 For purposes of cross border clearance (imports), where VAT is exempt in terms of
the VAT Act, payment code ‘D’ must be used. Code “V” will not be valid
forKopfontein as there are no duties applicable.
 In the event where a clearance is submitted for goods where no duty or VAT is
applicable, e.g. transit, then payment code “F” must be applied.
 NOTE: Payment codes for all remaining BLNS offices using the CCA System remain
the same -“C” or “V” - until Release 3 is implemented at these offices.
10. Indicative Rollout Plan for Release 3 at BLNS Landborders
Border Post
Quachasneck
Caledonspoort
Van Rooyens
Mahamba
Jeppes Reef
Mananga
Golela
Ficksburg
12
Go-Live Date
22 April 2012
22 April 2012
5 May 2012
5 May 2012
5 May 2012
5 May 2012
12 May 2012
19 May 2012
Customs Modernisation Implementation Landscape – ver. 2012.05.09
2. Supplementary Components for Release 3
Expected date for Trader Testing
Expected date for Implementation
Abstract
Brief Description
To introduce a new Automated Cargo Management solution; Passenger Processing system;
a new declaration capture frontend; and a New Cash Desk for customs payments.
Detail
Scope Description and Impact
1.
New Passenger Processing System
The new Passenger Processing System (PPS) will be introduced. Customs clearance for
imported goods accompanying travellers will occur on a simplified basis, with the
payment of VAT on transactions exceeding R5000 in value. Travellers exiting the
country should be allowed to export goods of a nature usually used in a household to a
combined value not exceeding R5000. These goods must be declared at the port of
exit and proof of such declaration must be furnished to the traveller. The proof of
declaration must be furnished to the entity responsible for VAT refunds.
NOTE: SARS will apply a ‘3-hit rule’. This implies that once a trader is flagged for
consignments determined as being ‘commercial’, he/she will be allowed no more than 3
transactions in the traveller channel, after which he/she will be directed to the ‘commercial
channel’ to make a formal customs clearance.
2.
New Declaration Capture frontend (CD1)
Face-2-face declaration via the commercial clearance channel with a customs official at
the SARS front desk, where the customs official will capture the clearance to which the
importer must attest.
NOTE: In consideration of the limitations indicated above, traders who prepare manual
clearances prior to arrival at Kopfontein should continue to do so in the SAD500 format.
When presenting themselves at Kopfontein, they will present the declaration convey this
information verbally to the Customs official for capture on the Customs system. They will
attest (sign) the declaration once processed and printed by Customs.
3.
13
New Cash Desk for Customs Payments
Customs revenue accounting for Kopfontein will be administered on the new customs
cash desk for “financial clients” (i.e. cash payments, deferment, road and consignor
bonds, refund claims).
Customs Modernisation Implementation Landscape – ver. 2012.05.09
4.
What will be the impact of the implementation of the Automated Cargo
Management (ACM) system on road hauliers and the border process?
 The ACM system is SARS’s automated solution for the receipt and processing of
electronic cargo reports in respect of commercial cargo entering, transiting or
leaving the Republic.
 All road hauliers who are to cross a South African land border post with
commercial cargo must register as road hauliers for ACM cargo reporting
purposes.
 Cargo reports may only be submitted electronically to the SARS Automated Cargo
Management (ACM) system by means of Electronic Data Interchange (EDI) in the
prescribed UN/EDIFACT CUSCAR message standard.

ACM implementation for road freight is scheduled to commence on 12 May 2012
and envisaged to be activated at the following offices:
–
–
–
–
–
–
–
–
–
–
–


For the initial phase of the ACM implementation a hybrid solution will be
employed –
–
Road hauliers who have not submitted an electronic manifest to ACM will be
processed in terms of the manual Service Manager process as is currently the
case. SARS will compare clearance records against the goods listed on the
paper manifest and, where any discrepancy exists, the necessary corrective
measures will need to be performed by means of Vouchers of Correction
(VOC’s).
–
Road hauliers who have submitted an electronic manifest to ACM will be
processed on the basis of the information contained in the electronic
manifest. Provided that the information on the manifest is factually correct at
arrival of the truck at the border, discrepancies on bills of entry appearing on
that manifest (e.g. incorrect truck registration details) will not require VOC’s
from traders as a record of the correct information will be carried by SARS
against the appropriate clearances.
It is important for the successful implementation of the electronic Road Freight
Manifest solution that road hauliers ensure that–
–
14
Kopfontein
Ramatlabama
Nerston
Vioolsdrift
Nakop
Quachasneck
Caledonspoort
Mananga/Mahamba
Jeppes Reef
Van Rooyenshek
Golela
their manifest numbers remains unique for a period of two years from the
date of issue thereof; and
Customs Modernisation Implementation Landscape – ver. 2012.05.09
–
they compile and report their manifest numbers according to the following
prescribed format –

Road Haulier code assigned by SARS at registration - (8AN)

Manifest Number assigned by Road Haulier (AN27)

The CUSCAR Data Mapping Guide (DMG) has been updated (v-20-20120309) to
include Crew detail4. The mandatory crew detail was implemented in Production
on ACM on Saturday, 21 April 2012.

Further information about the ACM system, including a Frequently Asked
Questions (FAQ) document on the development of the Road Freight Manifest, as
well as the latest CUSCAR Data Mapping Guide (DMG) and downloadable
registration
forms
are
available
on
the
ACM
webpage
http://www.sars.gov.za/home.asp?pid=558
4
Refer to ANNEX D, page 22 for details.
15
Customs Modernisation Implementation Landscape – ver. 2012.05.09
3. New Tariff Management System (TMS)
Expected date for Trader Testing
Expected date for Implementation
Abstract
Brief Description
To introduce the new Tariff Management System.
Detail
Scope Description and Impact
5.
Replacement of current legacy loose leaf tariff system with the New Tariff
Management System (TMS) system
i. Check digits will be retained until further notice.
6.
Introduction of new PRODAT XML schema. Current EDIFACT PRODAT still available.
i. Will commence with the distribution of a full tariff master to
enable service providers to load for testing purposes.
ii. Will follow with regular tariff updates.
7.
Please note that the UN/EDIFACT PRODAT will be in exactly the same format as it is
currently, i.e. none of the new fields introduced into the PRODAT XML (XSD) will be
available.
Decision taken at Modernisation Strategic session 19 January 2012  A task team will be set up – at a point in time – to deal with PRODAT XML structure issues raised
by external stakeholders.
16
Customs Modernisation Implementation Landscape – ver. 2012.05.09
ANNEX A – Customs Status Codes (Code List 14)
With the implementation of Customs’ new inspection and case management workflow system (Service
Manager) under Release 2 of the Customs Modernisation Programme, new status codes were introduced to
provide increased visibility of declarations. Every inbound electronic submission (CUSDEC) by a trader to
Customs will result in one or more status response (CUSRES) message. Why status response messages? For
one, increased mechanisation means less physical contact or interaction with Customs. Status messages
therefore help to provide declarants with up-to-date information on the processing of their transactions. They
also assist the trader in pre-empting the next step so as to expedite the process.
5
6
What the Trader submits
[CUSDEC]
What Customs responds [CUSRES]
<< Customs Status Codes – Code List 14>>
Code
Code
Description
Description
IMP
EXP
9
An original declaration
1
Release
X
X
4
An amendment declaration
2
Stop / Detain for Customs
X
X
5
A replacement declaration
3
Conditional Release
X
X
1
A cancellation declaration
4
Detain Other (Other Government Agency)
X
X
5
Conditional Release (OGA)
X
X
6
Reject to Clearer
X
X
7
Ready for Cash Payment
X
8
Proceed to Border (BLNS clearances)
ORReceived and updated on Customs
system5
X
X
9
Already on Customs system
X
X
13
Query - Supporting documents required
X
X
14
Referred to Checking (Excise only)
X
X
23
Cancelling a CUSRES
X
X
24
Amending a CUSRES
X
X
25
Release Revocation6
X
X
Status 8 is now being introduced as a response i.r.o. SARS requested amendments (VOCs).
Status 25 will only be implemented in Release 4
17
Customs Modernisation Implementation Landscape – ver. 2012.05.09
What the Trader submits
[CUSDEC]
What Customs responds [CUSRES]
<< Customs Status Codes – Code List 14>>
Code
Code
Description
Description
IMP
EXP
26
Amendment notification (stop note advice)
X
X
27
Amendment granted
X
X
28
Cancellation granted
X
X
29
Replacement granted
X
30
Insufficient funds7
X
31
Information message to client
X
X
32
Goods seized
X
X
33
Supporting documents received
X
X
34
Case Closed
X
X
35
Warning of supporting docs not received
X
X
36
Booking confirmation for inspection
X
X
For more details refer to –
 The Manual for Completion of Declarations (SC-CF-04) available at http://www.sars.gov.za/home.asp?pid=326&toolid=65&itemid=63684
 SARS Modernisation Communication titled Customs Status Codes & Scenarios available at http://www.sars.gov.za/home.asp?pid=4150#Chart
7
Status 30 will only be implemented in Release 4
18
Customs Modernisation Implementation Landscape – ver. 2012.05.09
ANNEX B – Status Code Scenarios for Kopfontein
The following scenarios:
SEQUENCING OF CUSTOMS SCENARIOS IN REGARD TO STATUS CODES
No.
Scenario
Sequence of Status Codes
Kopfontein scenario 1
Entry submitted
> Proceed to border
>> Trader Initiated VOC
>>>Flagged for inspection
>>>> Supporting docs submitted
>>>>> Released
>>>>>>VOC accepted
8, 13, 33, 8, 1, 27
xx
Kopfontein scenario 2
Entry submitted
> Proceed to border
>> Released
>>> Trader Initiated VOC
>>>> VOC accepted
8, 1, 27
xxx
Kopfontein scenario 3
Entry submitted
> Proceed to border
>> Released
>>> Trader Initiated VOC
>>>> Flagged for inspection
>>>>> VOC accepted
8, 1, 13, ,33, 27
x
19
(Note: Trader Initiated VOC will not
receive a Status 8 unless the entry has
not been finalised)
Customs Modernisation Implementation Landscape – ver. 2012.05.09
ANNEX C – Glossary
On request of stakeholders, the following glossary is provided.
Term
Description
ACM
Automated Cargo Management system – Customs’
multi-modal cargo reporting and cargo accounting
system
CAPE
Customs Automated Processing of Entries system
(Imports)
X
CCA
Common Customs Area declaration processing
system
X
CD1
Customs Declaration Form – will replace the
SAD500.
CEI
Customs and Excise Information system
X
CER
Customs and Excise Refund processing system
X
CN1
Customs Status Notification Form – will replace the
customs release notification.
X
CN2
Customs Summary Declaration – customs
summary report confirming consignments (LRNs)
for a given road vehicle.
X
CPC
Customs Procedure Code. Implemented
November 2010 replacing purpose codes.
X
CRE
Customs Risk Engine
X
CUSCAR
SARS’ EDI Cargo Report message format
X
X
CUSDEC
SARS’ EDI Customs Declaration message format
X
X
EXPORT
Customs’ Export Processing system
X
IBAS
Customs’ In Bond Acquittal System
X
Interfront
International Front – being the name of the
development wing of SARS Customs new
integrated processing system. Replaces the TATIS
branding.
X
InterfrontC
MS
Interfront Customs Management Solution – being
the title for the new integrated customs solution.
Replaces the TATIScms branding.
X
LLT
Loose Leaf Tariff management system
PRODAT
SARS’ EDI Customs Tariff message format
X
PRODAT
XML
SARS’ XML Customs Tariff message format
X
20
New Environment
in
Legacy Environment
X
X
X
X
Customs Modernisation Implementation Landscape – ver. 2012.05.09
Term
Description
RAS
Registration and Accreditation System
SAP
SARS Financial Accounting system. Will replace
current legacy customs cash desk and revenue
accounting.
X
Single
Registration
SARS’
new
client
interface
providing
taxpayer/trader online facilities to create and
maintain taxpayer/trader account profiles. Will
replace RAS.
X
TATIS
Intellectual Property acquired by SARS for the
development of a new integrated customs
processing system. Brand since changed to
Interfront.
X
TBK
Tariff Book Engine – SARS new integrated tariff
look-up, validation, and duty calculation system
developed by Interfront
X
TIN
Tax Identification Number – same as a Customs
Code number.
X
TMS
Tariff Management System –will replace the LLT
system.
X
U3TM
Unified
Taxpayer,
Trader
and
Traveller
Management system. Will replace the RAS system.
SARS new client management system providing a
‘single view’ of the taxpayer/trader.
X
XML
Extensible Mark-up Language – being a structure
for data in the XML environment.
X
21
New Environment
Legacy Environment
X
Customs Modernisation Implementation Landscape – ver. 2012.05.09
ANNEX D – Excerpt of SARS Customs CUSCAR Data Mapping Guide - v-20-20120309
EDI
ID
EDI DATA ELEMENT/SEG NAME
NAD
NAME AND ADDRESS
C
3035
PARTY QUALIFIER
M
REQ
ELEN
an..3
EDI
QUALIFIER/DEFAULT
3039
1131
Party id. identification
Code list qualifier
22
Code list responsible agency,
coded
5
TYPE
ILEN
1
2
3
4
5
6
7
8
9
REMARKS
To specify the name/address and their related
function, either by C082 only and/or unstructured
by C058 or structured by C080 through 3207.
>A
X
X
X
>B
X
X
X
MS = Message sender
>C
X
X
X
AH = Transit principal's
agent / representative
>D
X
>E
M
Driver taking truck across border
>FGHI
O
Repeat for each additional occupant (Max 4)
X
X
X
X
X
X
X
X
X
X
X
X
C
M
C
an..35
an..3
172 = Carrier Code
A = Passport
D = Temporary Permit
E = Travel Document
F = Emergency Travel
Certificate
L = Departure Permit
M = Document for
Travel Purposes
N = Provisional Permit
P = Computer
Readable Passport
3055
9
DATA ELEMENT NAME
FZ = Grouping centre
FM = Crew member
PARTY IDENTIFICATION DETAILS
KEY
RL = Reporting carrier
DR = Driver
C082
OCC
C
an..3
20 = BIC (Bureau
International Des
Containeurs)
M
M
M
M
The party that issued the Master Ocean Bill/Master Air
Waybill or Master House Bill/Master House Air Waybill
in the case of sub-consolidations. For courier cargo
where no Master Air Waybill is issued by the carrier the
courier must reflect the code 000-. For Air, use the 3
digit numeric IATA Airline Code. For rail the rail carrier
code "TFR". For road the code assigned by SARS to
the remover / transporter must be reflected.
The party that issued the House Bill Of Lading/Air
Waybill.
The ID of the sender of the EDI message. For Air, use
the 3 digit numeric IATA Airline Code. For rail use
"TFR"
35
O
Customs code for foreign transporter. Mandatory
where foreign remover transports cargo
AN
35
M
Driver's Travel Document Number, i.e. please insert
the passport number, not the ID number.
AN
35
M
Crew Member's Travel Document Number, i.e. please
insert the passport number, not the ID number.
>A
901
MASTER CARGO
CARRIER CODE
AN
35
M
M
>B
935
CARGO CARRIER CODE
AN
35
O
M
>C
149
MESSAGE SENDER
AN
35
M
M
>D
FOREIGN REMOVER
AN
>E
DRIVER TRAVEL
DOCUMENT NUMBER
>FGHI
CREW TRAVEL
DOCUMENT NUMBER
>A
>EFGHI
X
TRAVEL DOCUMENT
TYPE
AN
X
M
M
X
M
M
X
3
>ABC
Customs Modernisation Implementation Landscape – ver. 2012.05.09
M
M
X
M
M
O
M
M
M
X
X
X
X
M
X
X
X
X
166 = US, National
Motor Freight
Classification
Association (SCAC
Code)
>ABC
X
X
X
X
ZZZ = South African
Revenue Service
>ABC
X
X
X
X
3 = IATA
C058
NAME AND ADDRESS
C
3124
Name and address line
M
an..35
3124
Name and address line
C
an..35
3124
Name and address line
C
an..35
3124
Name and address line
C
an..35
3124
Name and address line
C
an..35
C080
PARTY NAME
C
3036
Party name
M
an..35
3036
Party name
C
an..35
>AC
>E
>FGHI
>E
>FGHI
3036
Party name
C
an..35
>E
>FGHI
3036
Party name
C
an..35
3036
Party name
C
an..35
3045
Party name format, coded
C
an..3
23
>EFGHI
>EFGHI
X
X
X
X
X
DRIVER SURNAME
CREW MEMBER
SURNAME
AN
35
M
Driver's Surname
AN
35
M
Crew Member's Surname
DRIVER FULL NAMES
AN
35
M
Driver's Full Names
AN
35
M
Crew Member's Full Names
AN
35
M/O
Driver's RSA ID number. Required if SA Citizen.
AN
35
M/O
Crew Member's RSA ID number. Required if SA
Citizen.
CREW MEMBER FULL
NAMES
DRIVER RSA ID
NUMBER
CREW MEMBER RSA ID
NUMBER
DRIVER/CREW
ADDITONAL
INFORMATION 1
DRIVER/CREW
ADDITONAL
INFORMATION 2
AN
35
M
Travel Document Expiry Date (start=1, length= 8)
Format CCYYMMDD
Date of Birth (start=9, length=8) Format CCYYMMDD
Gender (start=1, length= 1)
F=Female
M=Male
space=Unknown)
Occupation (start=2, length=1)
G=Trade
Reason for Movement (start=3, length=1)
D=Work
E=Transit
Traveler Type (start=4, length=3)
SVR=Normal South African
VBK=Foreign Contract Worker
VBV=Normal Foreigner
VVP=Permanent Residence Holder
Country Of Residence (start=7, length=3)
ISO 3 character country code, for example ZAF.
Nationality (start=10, length=3)
ISO 3 character country code
Travel Document Country Of Issue (start=13,
length=3)
ISO 3 character country code
AN
35
Customs Modernisation Implementation Landscape – ver. 2012.05.09
M
--- All fields are required ---
C059
STREET
C
3042
Street and number/p.o. box
M
an..35
3042
Street and number/p.o. box
C
an..35
3042
Street and number/p.o. box
C
an..35
3164
CITY NAME
C
an..35
3229
COUNTRY SUB-ENTITY
IDENTIFICATION
C
an..9
3251
POSTCODE IDENTIFICATION
C
an..9
3207
COUNTRY, CODED
C
an..3
24
Customs Modernisation Implementation Landscape – ver. 2012.05.09