EDI training online

UN/EDIFACT Message Data Mapping Guide (continued) The guidelines given below refer to each UN/EDIFACT message used in SARS EDI business communication. The first two portions were given in the previous blog posts. Find below the descriptions of more data elements. UNH MESSAGE HEADER (Mandatory 1) Specification of the beginning of each individual message and unique identification of the message. Read More →

EDI Mapping

SARS Mapping Guidelines: Interchange Header Segment Elements (Continued) Application Reference (0026) element may be used only if the interchange contains one message type. A reference to the specific systems’ application that will process all the messages in the interchange can be made here. Processing Priority Code (0029) Code denoting the processing priority for the interchange as assigned by Read More →

Mapping requirements

Mapping requirements for Interchange Header Segment (Sender, Recipient, Date, Time of Preparation) We continue to describe mapping guidelines for SARS EDI Documents. In the previous blog, we started speaking about Interchange Header Segment. Find below the next data elements description. Interchange Sender (S002) Sender identification (0004) Identifies the sender of the interchange by either name or a Read More →

mapping guides

South African Revenue Service (SARS) Mapping guides: UNB, Interchange Header (Mandatory) UNB, Interchange Header represents the specification of the beginning of a message interchange. It identifies the message syntax, the parties to the transmission, including details of password, communication, control, application and test conditions. The segment must always be used in a transmission and must Read More →

Application Process

PKI Application Process At SARS There are five steps to be followed when applying for PKI. The first two are given in the previous post. Find below the next steps to continue PKI integration at SARS. Step 3 Handle the application The application must be handed in at either the SARS Head Office in Pretoria Read More →

Integration Guidelines

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

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 →

EDI Training

Basic Definitions For PKI (SARS Requirements) Find below some basic definitions for using Public Key Infrastructure. Public-and-Private Key Pair In PKI (Public Key Infrastructure) systems, which are normally built on asymmetrical encryption schemes, the two keys of the key pair have different functions. One key is kept secret by its owner, and is known as Read More →

Public Key Infrastructure

Public Key Infrastructure: Basic Definitions Trading partners of SARS that make use of X.400 communications are not affected by the SARS PKI system as X.400 is considered to already be safe and secure. Find the PKI terminology below. Some of the terminology related to PKI (Public Key Infrastructure) systems is explained here for the sake Read More →

EDI public key

PKI Defined (SARS EDI Requirements) PKI can be defined as the architecture, organisation, techniques, practices, and procedures that collectively support the implementation and operation of a certificate-based public key cryptographic system. It includes a set of policies, processes, server platforms, software and workstations, used for the purpose of administering Digital Certificates and keys. A Public Read More →