REQDOC (REQUEST FOR DOCUMENT) SARS Explained The REQDOC message is used to request the last successful CUSRES of an entry. The LRN and or MRN must be provided in the REQDOC. A CUSRES will be sent to verify if the request can be fulfilled or not followed by the CUSRES in question if available. Note … Read More →
PRODAT (PRODUCT DATA) Message SARS Overview Tariffs are amended on a regular basis and get published in the Government Gazette. Agents then need to update their master files with the amended information in order to supply the correct tariff information on declarations. This is a time consuming, tedious capturing and checking effort. With the introduction … Read More →
CUSCAR: Customs Cargo Report (SARS EDI Guides) The CUSCAR message is used for supplying manifest information to SARS electronically. For each CUSCAR message received, SARS will return a CUSRES message with either a Status 6 (Rejected), Status 8 (Accepted) or Status 9 (Duplicate). Illustration below shows the relationship between EQD and SGP segments. To learn … Read More →
CONTRL (Syntax and service report message) (SARS EDI Transactions) Once a UN/EDIFACT message is received, the data is automatically translated to ensure the information received conforms to the UN/EDIFACT syntax rules. Once this is established, a CONTRL (Syntax and Service Report) message is sent to the sender of the UN/EDIFACT message, detailing the conformance, or … Read More →
SARS EDI Transactions: CUSRES (used in conjunction with CUSDEC (IMPORTS/EXPORTS) Once the CUSDEC message has passed translation successfully, it is mapped to the internal file format and passed on to the import / export system. There are various instances where a CUSRES (Customs Response) message could be created. These are: A CUSRES is generated denoting … Read More →
SARS EDI Transactions: CUSDEC (CUSTOMS DECLARATION) A CUSDEC (Customs Declaration) message must be received by customs for each declaration. This information will be received centrally at the SARS EDI facility at HeadOffice. Once received, the data is automatically translated to ensure the information received conforms to the UN/EDIFACT syntax rules. Once this is established, a … Read More →
Public Key Infrastructure Integration Guidelines The following steps need to be followed when applying for PKI. Step 1. Requesting Digital Certificate For clients that wish to use the Internet to transfer EDI data the client must complete a DA 185.4A6 to request a Digital Certificate from SARS. Although the applicant may already have completed this form … Read More →
Public Key Usage Basic Terms (SARS Explained) This blog gives one more list of useful definitions while using Public Key Infrastructure in EDI communication. Message Digest A string of digits (or string value) that is created by using a formula called a one-way hash function. The data for which the message digest is calculated is … Read More →
The Customs Act and EDI Release: SARS Explained This blog contains the Customs Act, Section 101A, Electronic communication for the purposes of customs and excise procedures as well as the Rules to Section 101A, for reference purposes. The first part – in the previous blog post. The Commissioner may set out in such agreement: (a) any … Read More →
Electronic Business Guidelines (New Hampshire) Starting up a new EDI system can be a complex endeavor. Make sure you understand all that is required before investing resources. Otherwise, you may end up with a collection of piecemeal fixes rather than a comprehensive solution. Guidelines below have the information needed to implement EDI in New Hampshire. Assign responsibilities for … Read More →