Customs Technical Work Session The Media Boardroom ...

Customs Technical Work Session The Media Boardroom, Megawatt Park, Sunninghill, Sandton

Wednesday, 20 June 2018

External Stakeholders Forthcoming Customs Technical Developments

Agenda Topics for Discussion

Customs Technical Work Session Wednesday, 20 June 2018

Topics for Discussion

Opening and Welcome ………………………………………………………….……..…...................Carl

1. Unique Consignment Reference (UCR)………………….……………………………………..Carl

2. Tactical Release 1: 2-Step Declaration Processing………………………………………….Carl/MikeP

3. SEA - Additional and changed Data Fields on CUSDEC………………………………….Carl

4. Reporting of Conveyances and Goods (RCG)

a) Sea – CUSCAR Data Element Changes……………………………..……………………………………………Andre/MikeL

b) Air – CUSDEC Validations………………………………………………………………………………………………Andre/MikeL

c) Deletion of Dummy Codes……………………………………………………………………………………………Andre/MikeL

d) Road Modality Part-shipment Management – RCG Phase 2A………………………………….……Andre/MikeL

5. PKI - Digital Certificates……………………………………………………………………………….Carl

6. X400 Communication………………………………………………………………………………….Carl

7. Testing in Live Environment…………………………………………………………………………Carl

Closure of Meeting………………………..……………………………………………….………………….Carl

Unique Consignment Reference (UCR)


Agenda Item 1

{Year} {Country Code} {Entity Code} {Reference Number}

last character of the year over a 10 year period [1 character]

Nationality of the supplier/consignor - Country ISO code (alpha-2 code)[2 characters]

Entity code of the supplier/consignor [8-13 characters]

{Entity Type} {Reference Type} {Scope}

Type of Entity code of the supplier/consignor [1 character]

Reference Type of the consignment [3 characters]

Unique reference for the consignment [14-19 characters]

Usage [1 character]

{Year}

{Country Code}

{Entity Code}

{Entity Type}

{Reference Type}

{Reference Number}

{Scope}

• INV = Invoice • PON = Purchase Order • CON = Contract • DEL = Delivery • OTH = Other • INF = Informal • CUS = Customs generated • DCL = Declarant generated

• S = Single Use • M = Multiple Use

• C = Customs Code • T = Tax Code [TIN] • I = Company Registration number • P = ID number / Passport number

UCR Introducing the SACU Unique Consignment Reference to be applied to all export and import declarations

5ZA00030004CINVIN000001S …an35

UCR is imperative to enable matching of the import declaration with ‘exchanged’ export data.

1.Rules for Import a) Direct Imports from BLNS b) Transit from BLNS c) Transit to BLNS d) Transit through RSA and through BLNS e) Warehouse movement to BLNS f) Temporary Import

2. Rules for Export

a) ALL destinations. b) Temporary Export.

3.Timelines

a) Commence Testing – 25 June 2018 b) Implementation into production – scheduled for 13 July 2018

Unique Consignment Reference (UCR)


Agenda Item 1

Port of Durban Ex

warehouse

All International Export Destinations

Tactical Release 1 – Incomplete/Provisional Supplementary


Agenda Item 2

1. Two-Step Usage • RID - only for exports • RPD – for both imports and exports • RID/RPD – to be followed by a supplementary clearance (RSD)

2. Concessionaires • SARS to engage concessionaire's regarding lead time for clearance – i.e. those parties unable

to meet the 7 + 7 day supplementary requirements. • On implementation concessionaire's to follow the RCD as current practice.

3. SARS to revert to trade on the following – • Application for extension process. • Alternative type/s of surety – in the event surety is required.

4. Timelines • Scheduled for November 2018

SEA - Additional and changed Data Fields on CUSDEC


Agenda Item 3

1. Transport Document Number - extract from SC-CF-04 [Customs Completion Manual] for consideration -

“The first part to reflect the Master Cargo Carrier Code (Four-digit Alpha Numeric Code) assigned by the Cargo Processing Systems (CPS) to the entity who issued the Master/Ocean Bill of Lading or Non-Negotiable Liner Waybill or the appointed agent of the applicable entity in South Africa.”

2. To ensure proper distinction of these parties, the current Transport Document Number field is to be split

according to the proposed EDI mappings -

3. New Code Tables • SARS to provide two specific code tables for Vessels Agent codes and Master Cargo Carrier codes,

respectively which will be effective on the day of implementation. • Registration requirements to be finalised.

4. Timeline

To be advised.

Master Cargo Carrier Code [Mandatory]

NAD+CA Carrier

OR

TDT C040 C

3127 Carrier identification C an..17

Vessel’s Agent Code [Optional]

NAD+CG Carrier’s Agent

Transport Document Number [Mandatory]

RFF+AAS Transport document number

A. OFFICE OF DESTINATION OR DEPARTURE

OFF. CODE MANIFEST NUMBER 15.2 District Office Code

VAC:YYYYMCC:XXXXTDN:123455555555555555555555.

15.26 Trasnport Document Date

15.27 Transport Documment Issued At

Represented as Box A2 SAD500

Note – Release authority messages will first look at ‘vessels’ agent’ and if not EDI enabled, use ‘master cargo carrier’ code.

Sea – CUSCAR Data Element Changes


Agenda Item 4a)

1. Verified Gross Mass (VGM)

We have had a lot of issues raised by shipping lines as a result of the different practices at load ports which could negatively impact the submission of VGM. We have taken those comments on board and have instituted a change to be made to RCG where “VGM” will become an optional data element.

Whilst we await the development and implementation thereof, cargo reporters can in the interim, duplicate the EQD (container) “gross mass” value in the “verified gross” mass field. We will amend the Message Implementation Guideline (MIG) and set the field to “optional” as soon as the systems development has been completed and the change has been implemented.

2. Terminal of Discharge

We have been informed of the difficulty in advising “terminal of discharge” on pre-loading and pre-arrival messages. As a result we are also in the process of making that field optional. A work-around that can be used in the interim is to populate that field with “ZT” code for “SARS Interim Terminal Code” which can be found in the “Outturn Provider Code Table” published on the RCG webpage - http://www.sars.gov.za/ClientSegments/Customs-Excise/AboutCustoms/Pages/Reporting-of-Conveyances-and-Goods.aspx

3. Depot of Unpack

Questions has been raised regarding the validity of “Depot of Unpack” for Sea freight FCL shipments reported on Advance Loading House (ALM) or Container House (COH) as a mandatory field as messages are rejected calling for Depot of Unpack to be provided.

The validation will be improved by testing against “Service Type” in the EQD segment and making “Depot of Unpack” only mandatory for multiple consignment containers. We will amend the Message Implementation Guideline (MIG) and set the field to “optional” as soon as the systems development has been completed and the change has been implemented.

http://www.sars.gov.za/ClientSegments/Customs-Excise/AboutCustoms/Pages/Reporting-of-Conveyances-and-Goods.aspx











Air – CUSDEC Validations


Agenda Item 4b)

1. Transport Document Number (TDN)

The transport document should be declared as follows:-

• The first three digits to identify the airline followed by a hyphen and then the waybill number consisting of eight numeric numbers. The number should be declared continuous e.g. 083-36301171.

• Non-IATA airlines have been issued with RCG codes e.g. ZA3 (Congo Airlines).

2. House Waybill Number The house air waybill number must be declared as follows:-

• The first 8 digits to identify the Cargo Carrier (e.g. freight forwarder) as assigned by the RCG system to the entity who issued the house air waybill.

• The second part must reflect the actual number of the air waybill number, for example where the Cargo Carrier Code = “ZZZ00001” and the transport document number = “123456” the house air waybill number must be declared as follows: ZZZ00001123456.

3. Next Steps

• Enforcement of the above validations to ensure successful matching between CUSDEC and CUSCAR by the RCG system (e.g. rejection of “000-Ex Courier”).

Deletion of Dummy Codes


Agenda Item 4c)

ZZZ99999 – Non Registered Cargo Reporter • Enough time has been given for all cargo reporters to register. • Mandatory submission of electronic cargo reports with effect from RCG implementation on

the 20 April 2018. • Enforcement from the 1 August 2018.

Road Modality Part-shipment Management – RCG Phase 2A


Agenda Item 4d)

Clearance and Cargo Reporting

LRN 1

LRN 1 CARN 1

LRN 1 CARN 4

LRN 1 CARN 3

LRN 1 CARN 2

CUSDEC

CUSCAR CUSCAR CUSCAR CUSCAR

RCG PHASE 2A – SEPTEMBER 2018



Agenda Item 1d)

Data Requirements

• “Cargo Status” indicator must be “5”. • Last truck “Cargo Status” indicator must be “10”.

• For part-shipment “Estimated Date of Arrival” is mandatory for arrival and departures. • Conditionality changes.



Agenda Item 1d)

Scenario 1 – LRN Status = “Released”

Declarant • CUSRES 40 Arrival • CUSRES 41 Exit

RCG

SARS ATP

CUSRES messages per truck

Carrier • CUSRES 40 Arrival • CUSRES 41 Exit



Agenda Item 1d)

Scenario 1 – LRN Status = “Proceed to Border”

Declarant • CUSRES 1 on Arrival • CUSRES 41 Exit

SARS ATP

CUSRES messages per truck

Carrier • CUSRES 40 Arrival • CUSRES 41 Exit

Business Rules • Part shipment validation • All trucks at border together. • Release status only revealed on arrival of

complete consignment at land border posts. • Officer can only mark LRN for arrival if all trucks

are present and one CARN has a Status 10. • Apportion weight.

PKI – Digital Certificates


Agenda Item 5

Date Number 2018-07 435

2018-07-23 3 2018-07-24 1 2018-07-28 39 2018-07-29 209 2018-07-30 181 2018-07-31 2

2018-08 423 2018-08-03 75 2018-08-04 89 2018-08-05 1 2018-08-06 79 2018-08-07 3 2018-08-10 158 2018-08-11 4 2018-08-12 12 2018-08-13 2

Grand Total 858

• Certificates expiring in July to be renewed in June – July

2018

• Certificates expiring in August to be renewed in July –

August 2018

• Codes to be emailed to service providers & direct

senders.

• Only those still active to be downloaded.

X400 Communication


Agenda Item 6

‘T’ minus 133 days…and counting!

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwjQiOnp79_bAhWaF8AKHS_wDncQjRx6BAgBEAU&url=https://sandbox.ilxor.com/sandbox/ThreadSelectedControllerServlet?showall%3Dtrue%26bookmarkedmessageid%3D28864%26boardid%3D146%26threadid%3D1483&psig=AOvVaw1UOXoYpMGkrwOEluSYnblm&ust=1529502729395777

Testing in Live Environment


Agenda Item 7

Be Warned

• 4 Service Providers connections have already been temporarily suspended after not heeding requests to correct issues timeously.

• Test in Test Environment.

• If issues are picked up in production, suspend and revert to last working version.


Thank You

Customs Technical Work Session The Media Boardroom ...

Documents

Transcript of Customs Technical Work Session The Media Boardroom ...