Multidata is used for the processing of the EFT payments to the bank.
The system extracts the required data and places the file in a predefined folder on the production application server or on a folder that is known to Multidata.
Two-day service
The Sanlam Installments and Tax department utilizes the two-day service. The product type used is indicated in the file sent to Multidata in the same way as the current ACB format.
Cut-off time for Multidata files
The money and file will be with Multidata by 10h00 and two days before the payment date.
Stop payments
The payment can be stopped if the full amount originally on the file is paid into the Multidata bank account and hence will be refunded in full. This process is followed irrespective of when the stop payment is sent to Multidata.
File upload
The system places the file on the Sanlam FTP server.
Interchange, a Multidata system, will move the file from the server to the mainframe.
KOS input file
File name: TX999999.KOS (999999 = Company number)
Batch header
|
Field |
Position |
Length |
Value |
Comments |
|
Header |
1 – 2 |
2 |
BH |
|
|
Company number |
3 – 8 |
6 |
Numeric |
Multidata contract code |
|
Pay date |
9 - 14 |
6 |
YYMMDD |
|
|
Description |
15 - 24 |
10 |
Type of payment |
e.g. pension / salary |
|
Company name |
25 – 34 |
10 |
Alphabetic |
Name as registered with Multidata |
|
Language |
35 |
1 |
A = Afrikaans E = English |
|
|
|
36 – 41 |
6 |
Blank spaces |
|
|
Two-day-transaction |
42 |
1 |
J or a blank space |
o J = Indication of 2-day-transaction o Blank space = if position 42 is a blank space and a J is not entered in position 61, transaction will be dealt with as a 2-day-transaction |
|
|
43 - 48 |
6 |
Blank spaces |
|
|
Creation date |
49 - 54 |
6 |
YYMMDD |
The data will be over written once the transaction is dealt with by the Multidata KOS04 program. Suggestion is thus to fill this field with spaces. o Date when file is created o This field may be filled with spaces |
|
Creation time |
55 - 60 |
6 |
|
The data will be over written once the transaction is dealt with by the Multidata KOS04 program. Suggestion is thus to fill this field with spaces. o Time when file is created o This field may be filled with spaces |
|
One-day-transaction |
61 |
1 |
J or a blank space |
If the transaction is a one-day-transaction, a J must be entered in this position |
|
|
62 – 80 |
19 |
Blank spaces |
|
Transaction
|
Field |
Position |
Length |
Value |
Comments |
|
Bank code |
1 – 6 |
6 |
Numeric |
|
|
00 |
7 - 8 |
2 |
00 |
Fixed |
|
Account number |
9 - 21 |
13 |
Numeric |
Filled with leading zero’s |
|
Amount payable |
22 – 30 |
9 |
Numeric |
o Amount payable – no decimal e.g. RRCC (R21.10 will be 2110) o Filled with leading zero’s |
|
Type of account |
31 |
1 |
1, 2, 3 or 4 |
o 1 = Current o 2 = Savings o 3 = Transmission o 4 = Bond |
|
Payment type |
32 - 33 |
2 |
61 or 71 |
Example: o 61 = Salary o 62 = Pensions o 71 = Shares |
|
Name |
34 – 63 |
30 |
Alphabetic |
Name of bank account holder |
|
Reference |
64 – 72 |
9 |
Numeric |
Pay number / Policy number |
|
|
73 – 80 |
8 |
Blank spaces |
|
Note:
- All records are 80 characters
- The file must be sequential (CR / LF after each record)
The annuities for certain funds administered by ABSA and Alexander Forbes are insured with Sanlam. The annuities are paid to the individual annuitants by ABSA and Alexander Forbes and the value to cover the total of all the payments is recovered from Sanlam.
Although Sanlam does not pay the individual annuitants, they keep a record of the annuities to ensure that the amount paid to ABSA and Alexander Forbes each month is correct.
The annuitants are included in the monthly payment runs but not included in the file sent to Multidata, who create the files for BankServe (previously known as ACB), to transfer the payments into the annuitants’ bank accounts.
To prevent these annuitants from being included in the Multidata file, a different payment method of NO PAYMENT is used.
When the payment method is NO PAYMENT, the member business transaction for the payment is created with a different accounting activity for which the money movement indicator will be set to NO. This means that they will not be written to the EFT Instruction table and therefore won’t be included in the Multidata payment file.