The payment of benefit payments, fund expenses and investments via electronic fund transfer (EFT), using ABSA’s Linked Direct Control (LDC) Bank Interface service.
The bank account numbers for EFT payments made via the LDC Bank Interface service must be validated prior to the EFT file being processed.
The following batch job will be run several times a day to extract the bank account details for validation:
Batch Job 93 |
Account Holder Validation |
JU2AT_AHV\Bju2ato0.bat |
All bank account records with a status of NOT VALIDATED will be read and the following details will be extracted:
- Account Number
- Branch Code
- Name
An account holder validation (AHV) file will be created and placed in a folder with the name OUTGOING.
The AHV via LDC only validates account numbers for ABSA, First National Bank (FNB) and Standard Bank (SBSA).
Separate files will be created, one for the ABSA bank accounts and one for all other bank accounts.
Once the file has been extracted and processed, it will be moved to a folder with the name ARCHIVE.
When the EFT records are extracted in the EFT batch jobs, the system will read the value for Description on the Global Parameter with a Parameter Type of EFT CUT-OFF. If the current time is greater than the value found and the Date Effective on the EFT Instruction is less than or equal to current date, the value for Action Date on the EFT file will be set to the next working day.
Note:
Although these transactions might be authorised before the cut-off time, the EFT batch jobs may only be run after the cut-off time.
Currently the LDC batch job is scheduled to run in the batch schedule prior to 15h00 and therefore the transactions created before the cut-off should always be processed prior to the cut-off. However, this is only applicable to the LDC file and if for any reason the batch job does not complete prior to the cut-off or the batch job is run at a later time, the transactions will be rejected. .
Transmission Header Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / EXTRACT VALUE |
Record Identifier |
N |
1 |
3 |
000 |
Identifies the record as Transmission Header Record. Default to 000 |
Record Status |
A |
4 |
1 |
T or L |
Status of the record Default to L |
Transmission Date |
N |
5 |
8 |
|
Date on which the transmission to/from BI took place. Run Date |
Business Integrator User Code |
N |
13 |
5 |
|
Allocated BI Number (LD CODE) Value for Percentage on Global Parameter with a Type of AHV ABSA if the Bank Account is an ABSA account or AHV OTHER if the Bank Account is a non-ABSA account. |
Business Integrator User Name |
A |
18 |
30 |
|
BI User Name Administrator Name. Name on Client linked to a CAR with a CART of Administrator. |
Transmission Number |
N |
48 |
7 |
|
Identifies the transmission. Validation must be equal to last transmission stored on the ABSA parameter file +1 Read Transmission Number on Extract Control table for Extract Type of AHV. |
Destination |
N |
55 |
5 |
|
Validation: Zeroes Zeroes |
FILLER |
A |
60 |
119 |
Spaces |
Not used Spaces |
For User's Use |
A |
179 |
20 |
Spaces |
BI User's own use Spaces |
FILLER |
A |
199 |
2 |
Spaces |
Not used Spaces |
User Set Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION |
Record Identifier |
N |
1 |
3 |
30 |
Identifies the record as AHV Header Record Default to 30 |
Data Set Status |
A |
4 |
1 |
T or L |
Status of AHV User Set Default to L |
User Set Generation Number |
N |
5 |
7 |
|
Gen Number of this User Set This number will start at 0000001 and increment for each file submitted on a user code as long as the previous file has been accepted. If a file has been rejected the number will not increment. Read AHV User Generation Number on Extract Control table. |
Department Code |
A |
12 |
6 |
|
AHV Dept. Code LDC USER CODE |
Filler |
A |
18 |
183 |
Spaces |
Not Used Spaces |
Detail Transaction Record |
|
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION |
|
Record Identifier |
N |
1 |
3 |
031 |
Identifies the record as AHV Detail Record Default to 031 |
|
Record Status |
A |
4 |
1 |
T or L |
Status of AHV Detail Record Default to L |
|
Transaction Sequence Number |
N |
5 |
7 |
|
Transaction Sequence Number. Starts at 0000001, incremented by +1. For the first Account Number this value will be 0000001 and for each subsequent Account Number it will be the previous Account Number Transaction Sequence Number plus 1 |
|
Account Number |
N |
12 |
18 |
|
Account Number Account Number on Bank Account record. |
|
Identity Number |
A |
30 |
13 |
|
ID / Passport / Co Reg Number. Fill with spaces if not used. Spaces |
|
Initials |
A |
43 |
3 |
|
First 3 Initials of individual. No punctuation. Space filled if not used. First 3 characters of Name on DTI Account |
|
Name |
A |
46 |
60 |
|
Acc holder Name - Surname / Co Name Characters from fifth character (inclusive) of Name on DTI Account |
|
Return Code 01 |
N |
106 |
2 |
Zero |
Return code for the Acc Number. Value: Input from User =00.Output :00= Acc No exist. 01= Acc does not exist. Default to 00 |
|
Return Code 02 |
N |
108 |
2 |
Zero |
Return code for the ID Number. Value: Input from User =00.Output :00= ID No Match. 02= ID No Does Not Match.99= Acc No does not exist Default to 00 |
|
Return code 03 |
N |
110 |
2 |
Zero |
Return code for the Initials. Value: Input from User =00.Output :00= Initials Match. 02= Initials do not Match.99= Acc No does not exist Default to 00 |
|
Return Code 04 |
N |
112 |
2 |
Zero |
Return code for the Surname / Co Name Value: Input from User =00.Output :00= Surname Match. 02= Surnamedoes not Match.99= Acc No does not exist Default to 00 |
|
User Reference |
A |
114 |
30 |
|
For users own use Spaces |
|
Branch Code |
N |
144 |
6 |
|
Branch code for Account in field 12 for 18 Branch Code |
|
Originating Bank |
N |
150 |
2 |
|
User code for billing Spaces |
|
LD CODE |
A/N |
152 |
7 |
|
LD Code (LD00000) Depends on the Department Code used in the User Set Record. |
|
Filler |
A |
159 |
42 |
Spaces |
Not Used Spaces |
|
User Set Trailer |
|
|
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION |
||
Record Identifier |
N |
1 |
3 |
039 |
Identifies record as AHV User Set Trailer Record Default to 039 |
||
Record Status |
A |
4 |
1 |
T or L |
Status of AHV User Set Trailer Record Default to L |
||
Number of AHV Detail Records |
N |
5 |
7 |
|
Number of AHV Detail in this User Set Sum of Detail Transaction records. |
||
Hash Total of Account Numbers |
N |
12 |
18 |
|
Running total of the account numbers in the AHV Detail Records. |
||
Filler |
A |
30 |
171 |
Spaces |
Not Used Spaces |
||
Transmission Trailer Record |
|
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION |
|
Record Identifier |
N |
1 |
3 |
999 |
Identifies record as Transmission Trailer Default to 999 |
|
Data Set Status |
A |
4 |
1 |
T or L |
Status of record Default to L |
|
Number of records in transmission |
N |
5 |
9 |
|
Total Number of records in the transmission. Includes Header record (000) and Trailer Record (999) |
|
Filler |
A |
14 |
187 |
Spaces |
Not used Spaces |
|
Once the AHV file has been submitted and processed, a file with the return codes will be placed in a folder with the name INCOMING. The file will have the name REPLY.datetimestamp.
The format of the datetimestamp will be MMDDHHMMSS. The file will be in the same format as the file above but with values in the fields in the table below.
The following batch job will be run several times a day to read the AHV file that is returned:
Batch Job 93 |
Account Holder Validation |
JU2AT_AHV\Bju2ato0.bat |
The fields in the table below will be read for each bank account and the status field on the bank account record will be updated as per the details below.
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION |
Return Code 01 |
N |
106 |
2 |
Zero |
Return code for the Acc Number. 00= Acc No exist. 01= Acc does not exist. |
Return Code 02 |
N |
108 |
2 |
Zero |
Return code for the ID Number. 00= ID No Match. 02= ID No Does Not Match. 99= Acc No does not exist |
Return code 03 |
N |
110 |
2 |
Zero |
Return code for the Initials. 00= Initials Match. 02= Initials do not Match. 99= Acc No does not exist |
Return Code 04 |
N |
112 |
2 |
Zero |
Return code for the Surname / Co Name 00= Surname Match 02= Surname does not Match 99= Acc No does not exist |
If the value is equal to 00 for return code 01, 02, 03 and 04, the status will be updated to VALIDATED.
If the value for any one of return codes 01, 02, 03 and 04 is not equal to 00, the status will be updated to REJECTED.
The following LDC interface batch job will read all of the transactions on the EFT INSTRUCTION for which the status is not P (processed) and for which the interface Type is LDC:
Batch Job 80 |
LDC File Extract |
JU2AQ_LDC\Bju2aqo0.bat |
A file will be created with the values as per the table below. The file will be placed in a folder named OUTGOING.
Numeric fields must be right justified with leading zeroes. Alpha fields must be left justified with trailing blanks.
Transmission Header Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
000 |
The value 000 identifies the record as a Transmission Header Record. This must be the first record in the transmission or else an Error Message: "Invalid Transmission record / Transmission record not found" will be issued. Default to 000 |
Record Status |
A |
4 |
1 |
T or L |
The status of the record: T– Test data L – Live data. Default to L |
Transmission Date |
N |
5 |
8 |
|
Date on which a transmission to/from the Business Integrator User took place. FORMAT: CCYYMMDD. Validation: Must be the day's date, on which the transmission is done. As the service is available 24 hours a day and the time on all systems are different the system will accept a file with Yesterday's date, Today's date or Tomorrow's date, e.g. where a Business Integrator User'ssystem time is ahead of ABSA's system time the Business Integrator User's date can be one day ahead of ABSA's date or vice-versa. Run Date |
Business Integrator User Code |
N |
13 |
5 |
|
Allocated by ABSA on service application. Validation: Zeroes - For all data transmissions which originates within ABSA, i.e. files sent to a Business Integrator User / fetched by a Business Integrator User. The allocated Business Integrator User Code for all data transmissions send by the Business Integrator User to ABSA. Read value for Percentage on Global Parameter with a Type of LDC USER CODE |
Business Integrator User Name |
A |
18 |
30 |
|
Allocated by ABSA on service application. Is usually in accordance with the Business Integrator User’s Company name. Administrator Name. Name on Client linked to a CAR with a CART of Administrator |
Transmission Number |
N |
48 |
7 |
|
Identifies the transmission number so that duplication and lost transmissions can be identified. Is parameterised within the ABSA system. Validation: Must be equal to the last successful transmission number stored on the ABSA parameter file + 1. Exception: When it is a REPLY-file in respect of a REJECTED Business Integrator User file this field will be 0000000. Read Transmission Number on Extract Control table for Extract Type of LDC. |
Destination |
N |
55 |
5 |
|
Validation: Zeroes – For data from a Business Integrator User transmitted to ABSA. Payments and Collections User Code - For all data transmissions which originates within ABSA, being sent to a Business Integrator User / fetched by a Business Integrator User Default to 00000 |
FILLER |
A |
60 |
119 |
Spaces |
Filler – Not Used. Spaces |
For User’s use |
A |
179 |
20 |
Spaces |
For Business Integrator User’s own use. The data in this field will be returned in the transmission Header of the Reply-file. Spaces |
FILLER |
A |
199 |
2 |
Spaces |
Filler – Not used Spaces |
Transmission Trailer Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
999 |
The value 999 identifies the record as a Transmission Trailer. Default to 999 |
Data Set Status |
A |
4 |
1 |
T or L |
Default to L |
Number of records in transmission |
N |
5 |
9 |
|
Total Number of Records in Transmission Validated: Against the validation program calculated total number of records within this transmission. This number includes the Header Record (000) and Trailer Record (999) |
Filler |
A |
14 |
187 |
Spaces |
Filler – Not Used Spaces |
User Header Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
001 or 020 |
The Record Identifier identifies the type of transactions: 001 EFT Transactions Against Approved Limits 020 Payment Against Available Balance. Default to 020 |
Data Set Status |
A |
4 |
1 |
L or T |
Default to L |
BankServ Record Identifier |
N |
5 |
2 |
04 |
It is the first record of a User Header Record. It is the first record of BankServ EFT transactions. Should be the first record after a Transmission Header or a User Trailer record. Default to 04 |
BankServ User Code |
N |
7 |
4 |
|
BankServ / ABSA distribution User Code Validation: Against the registered ABSA User Codes for the Business Integrator User. Read value for Percentage on Scheme Parameter with a Type of ACB USER CODE |
BankServ Creation date |
N |
11 |
6 |
|
Date Creation date. FORMAT: YYMMDD Validation: Can be Yesterday's, Today's or Tomorrow's date. Run Date |
BankServ Purge Date |
N |
17 |
6 |
|
Equal to or later than the last action date of the transactions. Validation: Must be equal to or greater than the last action date of the Transactions for this User set. Last Action Date of transactions included in extract |
First Action Date |
N |
23 |
6 |
|
Earliest transaction action date of a transaction (Dr/Cr) to be processed in this User Set. Validation: May not be less than today's date. Earliest Action Date of transactions included in the extract |
Last Action Date |
N |
29 |
6 |
|
Latest transaction action date of a transaction (Cr/Dr) to be processed in this User Set. Validation: Must be equal to or greater than the First Action Date. Last Action Date of transactions included in the extract |
First Sequence Number |
N |
35 |
6 |
|
Sequentially assigned per BankServ User Code per transmission date. If this is the first file for the day then this value will be 000001. The next file for the same day will be 000002, etc. |
User Generation Number |
N |
41 |
4 |
|
The User Generation Number must be equal to the last accepted User Generation Number + 1. This number will start at 0001 and increment for each file submitted on a user code as long as the previous file has been accepted. If a file has been rejected the number will not increment. Read EFT User Generation Number on Extract Control table |
Type of Service |
A |
45 |
10 |
|
External Transactions: The service under which these transactions are to be processed at BankServ (i.e. external transactions), as at a minimum of 1 working day in the future: External transactions: CorpSSV: CORPSSV, SSV: SAMEDAY, 1 Day: ONE DAY , 2 Day: TWO DAY , 5 Day: FIVE DAY Internal transactions, the same as External transactions plus: Internal: INTERNAL, Early Debits: EARLY DR Payment Against Available Balance: BATCH. Read the Description for the Scheme Parameter EFT Service linked to the Scheme. |
Accepted Report |
A |
55 |
1 |
Y |
Y will trigger Accepted Report in the Reply File for EFT/AAF User Sets. Default to Y |
Account Type Correction |
A |
56 |
1 |
Y |
Y will trigger Account Type Correction for EFT & PAAF User Sets. Leave blank if this won’t be used. Default to Y |
Filler |
A |
57 |
144 |
Spaces |
Filler – Not Used. Spaces |
Standard Transaction Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
001 or 020 |
The Record Identifier identifies the type of transactions: 001 EFT Transactions Against Approved Limits 020 Payment Against Available Balance. Default to 001 |
Data Set Status |
A |
4 |
1 |
L or T |
Default to L. |
BankServ Record Identifier |
N |
5 |
2 |
|
Type of transaction: 10 - Direct Credit Transaction, 50 - Direct Debit transaction, Validation: Against above list. Default to 10 |
User Branch |
N |
7 |
6 |
|
Bank Branch code of the Business Integrator User’s nominated account. Validation: Against actual ABSA Branch codes.
Find Debit Bank Sort Code on the Bank Account record with the Account Number equal to the Debit DTI Account Number on EFT Instruction. |
User Nominated Account |
N |
13 |
11 |
|
Business Integrator User's ABSA nominated account number Validation: Against the ABSA lookup table (valid account file). Debit DTI Account Number on EFT Instruction |
User Code |
N |
24 |
4 |
|
As per the User Header’s BankServ User Code Validation: Against the User Header’s User Code. Read value for Percentage on Scheme Parameter with a Type of ACB USER CODE |
User Sequence Number |
N |
28 |
6 |
|
Must start with number equal to First Sequence number (in User Header) and thereafter incremented by 1. |
Homing Branch |
N |
34 |
6 |
|
Homing account Branch number Validation: Against BankServ list of Bank Branch Codes. Credit Bank Sort Code on EFT Instruction |
Homing Account Number |
N |
40 |
11 |
|
Homing Account Number Validation: Against BankServ supplied CDV and account number Validation Rules. Credit DTI Account Number on EFT Instruction. Note: If the account number is longer than 11 digits then this must be spaces and the Account Number must be put into the Non-standard Homing Account Number field (see position 135 below) |
Type of Account |
N |
51 |
1 |
|
Identifies the homing account type 1 – Current Account 2 – Savings Account 3 – Transmission Account 4 – Bond Account, 6 – Subscription Share Account Validated: Against above list Bank Account Type on EFT Instruction record. |
Amount |
N |
52 |
11 |
|
Monetary value of the Transaction Validation: Must be numeric Amount on EFT Instruction |
Action Date |
N |
63 |
6 |
|
Date on which transaction is to be actioned. Validation: Must be within the range of the First Action Date and the Last Action Date in the User Header Record. Date Effective on EFT Instruction. |
Entry Class |
N |
69 |
2 |
|
See ABSA File Specifications Business Integrator document Annexure 4 for list of codes. Default to 62 |
Tax Code |
N |
71 |
1 |
|
Default to 0 |
Filler |
A |
72 |
3 |
|
Filler – Not Used Spaces |
User Reference |
A |
73 |
30 |
|
Position 01-10: User’s Abbreviated Name – Compulsory Position 11-30: For Business Integrator User’s own use User reference Description of the transaction that must appear on the bank statement of the homing account. Concatenation of the following fields: 01-10: ACA spaces 11-30: EFT Ref Num on EFT Instruction. |
Homing Account Name |
A |
105 |
30 |
|
Homing Account Name Validation: Not to be left blank Credit Name on EFT Instruction This field allows for 40 characters. If it is greater than 30 characters concatenate it to 30 characters |
Non-standard Homing Account Number |
N |
135 |
20 |
|
Used for account numbers which cannot fit into the standard Homing Account number field e.g. Perm Account Numbers. Default value 20 zero’s. Validation: According to the BankServ CDV and account number rules. Credit DTI Account Number on EFT Instruction if it is longer than 11 digits. |
Filler |
A |
155 |
16 |
Spaces |
Default value. Spaces |
Homing Institution |
N |
171 |
2 |
21 |
21 – Participating Banks Validated: Must be 21 Default to 21 |
Filler |
A |
173 |
28 |
Spaces |
Filler – Not Used. Spaces |
A contra record will be created for each standard transaction record via the following batch job:
Batch Job 80 |
LDC File Extract |
JU2AQ_LDC\Bju2aqo0.bat |
Note:
Usually, a contra record is created for the sum of all of the transactions with the same user branch (USBR 130). This presents a problem for the bank reconciliation as the contra record is the transaction that appears on the user bank account, i.e. the scheme bank account, and therefore the entry that will be included in the ReconFocus bank statement file. The transaction created in the scheme's ledger is the individual EFT and therefore it will not be possible to reconcile the total transaction on the bank statement with the individual transactions in the scheme's ledger.
Contra Record (for each Standard Transaction Record) |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
001 or 020 |
The Record Identifier identifies the type of transactions: 001 EFT Transactions Against Approved Limits 020 Payment Against Available Balance. Default to 001 |
Data Set Status |
A |
4 |
1 |
L or T |
Default to L
|
BankServ Record Identifier |
N |
5 |
2 |
|
Type of transaction: 12 - Direct Credit Contra, 52 - Direct Debit Contra, Validation: Against above list. Default to 52 |
User Branch |
N |
7 |
6 |
|
Same as the User Branch on the transactions Records Validation: Against actual User Branch on all Transaction records. Same as Standard Transaction Record (Debit Bank Sort Code on the Bank Account record with the Account Number equal to the Debit DTI Account Number on EFT Instruction.) |
User Nominated Account |
N |
13 |
11 |
|
Business Integrator User's ABSA nominated account number Validation: Against the ABSA lookup table (valid account file). Same as Standard Transaction Record (Debit DTI Account Number on EFT Instruction) |
User Code |
N |
24 |
4 |
|
As per the User Header’s BankServ User Code Validation: Against the User Header’s User Code. Same as Standard Transaction Record (Value for Percentage on Scheme Parameter with a Type of ACB USER CODE) |
User Sequence Number |
N |
28 |
6 |
|
Validation: Applied to the sequence number on the transaction record. Same as Standard Transaction Record |
Homing Branch |
N |
34 |
6 |
|
Same as the User Branch on this record Validation: Against the User Branch on this record Same as User Branch on the Standard Transaction Record (Debit Bank Sort Code on the Bank Account record with the Account Number equal to the Debit DTI Account Number on EFT Instruction.) |
Homing Account Number |
N |
40 |
11 |
|
Same as the User Nominated Account Number on this record Validation: Against the User Nominated Account Number on this Record. Same as User Nominated Account on the Standard Transaction Record (Debit DTI Account Number on EFT Instruction) |
Type of Account |
N |
51 |
1 |
|
1 – Current Account Validation: Must be 1 Type of Account for Debit DTI Account on EFT Instruction. Must be 1 (Current). If not generate error message and stop creation of file. |
Amount |
N |
52 |
11 |
|
Same as Standard Transaction Record (Amount on EFT Instruction) |
Action Date |
N |
63 |
6 |
|
Date on which transaction is to be actioned. Validation: Must be within the range of the First Action Date and the Last Action Date in the User Header Record. Same as Transaction Record (Date Effective on EFT Instruction) |
Entry Class |
N |
69 |
2 |
|
Validation: Must be 10 Default to 10 |
Filler |
A |
71 |
4 |
|
Filler – Not Used Spaces |
User Reference |
A |
75 |
30 |
|
Position 01-10: User’s Abbreviated Name – Compulsory; Position 11-16: CONTRA Compulsory; Position 17-30: For Business Integrator User’s own use Validation: Must contain the BankServ specified minimum. 01-10: User Name (plus following spaces to fill) 11-16: CONTRA 17-30: First 7 characters of the Description on EFT Instruction. Refer to Note above. |
Filler |
A |
105 |
30 |
Spaces |
Default value. Spaces |
Filler |
A |
135 |
66 |
Spaces |
Filler – Not Used. Spaces |
User Trailer Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
001 or 020 |
The Record Identifier identifies the type of transactions: 001 EFT Transactions Against Approved Limits 020 Payment Against Available Balance. Default to 020 |
Data Set Status |
A |
4 |
1 |
L or T |
Default to L |
BankServ Record Identifier |
N |
5 |
2 |
04 |
Identifies the record to be a User Trailer Record Default to 04 |
User Code |
N |
7 |
4 |
|
Same as BankServ User Code in User Header Record. Validation: Against the BankServ User Code on the User Header Record. User Code in User Header Record |
First Sequence Number |
N |
11 |
6 |
|
Same as First Sequence Number on User Header Record Validation: Against First Sequence Number specified on the User Header Record. First Sequence Number on User Header Record |
Last Sequence Number |
N |
17 |
6 |
|
Same as User Sequence Number on User Header Record Validation: Against the User Sequence Number on preceding Contra record. User Sequence Number on User Header Record |
First Action Date |
N |
23 |
6 |
|
Same as First Action Date on the User Header record Validation: Against First Action Date specified on the User Header record. First Action Date on the User Header Record |
Last Action Date |
N |
29 |
6 |
|
Same as Last Action Date on the User Header record Validation: Against Last Action Date specified on the User Header record. Last Action Date on the User Header Record |
No Debit records |
N |
35 |
6 |
|
Number of Debit records including the Credit contra record Validation: Against the calculated number of Debit records (include the Credit contra). |
No Credit records |
N |
41 |
6 |
|
Number of Credit records including the Debit contra record Validation: Against the calculated number of Credit records (include the Debit contra). |
No contra records |
N |
47 |
6 |
|
Number of contra records in the User Data set Validation: Against the calculated number of contra records. |
Total Debit Value |
N |
53 |
12 |
|
Total value of Debit transactions including the Credit contra Validation: Against the calculated total value of Debit transactions (including the Credit contra value). |
Total Credit Value |
N |
65 |
12 |
|
Total value of Credit transactions including the Debit contra Validation: Against the calculated total value of Credit transactions (including the Debit contra value). |
Hash Total of Homing Account Numbers |
N |
77 |
12 |
|
Running total of all homing account numbers. Because overflow conditions are not treated in the same way by all makes of hardware, it is recommended that Business Integrator users generate the hash total in an 18-digit field in working storage and then move the twelve least significant digits from there into this field of the User Trailer Record. Note: The formula for addition routine is: Field 9 of Standard Transaction Record (11 digits) plus Field 18 of Standard Transaction Record (11 least significant digits) plus Field 9 of Contra Record (11 digits) Validation: Against the calculated hash total as explained above. |
Filler |
A |
57 |
144 |
Spaces |
Filler – Not Used. Spaces |
The following batch job will produce a file containing unpaid and rejected EFT’s:
Batch Job 94 |
Unpaid EFT and Rejections |
JU2AU_UNPEFT\Bju2auo0.bat |
The file containing the unpaid EFT’s and redirected EFT’s will be placed in a folder with the name INCOMING. The file will have the name ZR02388.OUTPUT.datetimestamp. The format of the datetimestamp will be MMDDHHMMSS.
If there are errors in the file, the file will be placed in a folder with the name ERROR.
Once the file has been processed successfully it will be moved to a folder with the name COMPLETED.
Note:
To re-process payments, the Replace EFT Payment sub-menu selection on the JU4BN Benefit Details screen can be used to re-process benefit payments for which the EFT payment has been rejected. This process creates a new disposal instruction and enables a new payment to be authorized for the payment that was rejected.
For all other payments the following Accounting Activity must be used to process the replacement payment:
Process |
Acc Activity |
S/holder |
Dr Account |
Cr Account |
MANUAL INITIATE |
UNPAIDEFTREP |
FUND |
UNPAID EFT |
BANK |
The format of the file is contained in the table below.
User Code Set Header Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
DUH-REC-ID |
N |
1 |
3 |
010 |
The value 010 identifies the record as an User Code Set Header Every User Code Set Header must be followed by transaction sets (Record Identifier 011-018) and then by a User Code Set Trailer Record Identifier 019). Validation: Must be 010. Will be checked to be in agreement with the rules above, i.e. a Header record must have an associated trailer record. |
Data Set Status |
A |
4 |
1 |
T or L |
The status of the record: T – Test data L – Live data. |
User Code |
N |
5 |
4 |
|
User Code: For files being referenced here which had both ABSA and External transactions on them, the User Code will be the BankServ User Code registered at BankServ for the Business Integrator User. For files being referenced here which had only ABSA transactions in them, this will be an ABSA Distribution User Code (it will not have been registered at BankServ). Validated: As defined above, the internal user codes and BankServ User Codes will be validated. |
BankServ Generation Number |
N |
9 |
7 |
|
Will be equal to the last BankServ Generation Number sent to the Business Integrator User + 1. |
BankServ Service |
N |
16 |
2 |
|
Business Integrator Services Validated: 01 – SSV 02 – 1 Day 03 – 2 Day 04 – Early Debits 06 – 5 Day 08 – CORP SSV 09 – Payment Against Available Funds. |
FILLER |
A |
18 |
183 |
Spaces |
Filler – Not used |
Unpaid - Set Header Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
011 |
The value 011 identifies the record as a Unpaid Set Header Record. Every Set Header must be followed by: Transaction records (Record Identifier 012 and 013) and then a Set Trailer (Record Identifier 014). |
Data Set Status |
A |
4 |
1 |
T or L |
|
BankServ User Code |
N |
5 |
4 |
|
BankServ User Code must be registered to the Business Integrator User. |
Business Integrator User’s Nominated Account’s Branch Code |
N |
9 |
6 |
|
The Branch Code for the Business Integrator User’s nominated account. |
Business Integrator User’s Nominated Account Number |
N |
15 |
16 |
|
The Business Integrator User’s Nominated Account for the User Code Set. |
Business Integrator User’s Nominated Account Type |
N |
31 |
2 |
|
For External transactions this will have to indicate a Current Account i.e. 01. For files consisting of ABSA transactions only, this can indicate one of the following account types: 01 – Current Account, 02 – Savings Account |
Action Date for Data Set |
N |
33 |
8 |
|
The Action Date of transactions in the User Code Data Set. FORMAT: CCYYMMDD |
Filler |
A |
14 |
187 |
Spaces |
Filler – Not Used |
Unpaid – Transaction |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
013 |
The VALUE 013 IDENTIFIES THE RECORD AS AN Unpaid Debit / Credit Transaction Record |
Data Set Status |
A |
4 |
1 |
L or T |
|
Transaction Type |
N |
5 |
2 |
50 or 10 |
Transaction Type: 50 - Debit Transaction 10 - Credit transaction |
Transmission Date |
N |
7 |
8 |
|
The date on which the Business Integrator User transmitted the transaction to ABSA. Format: CCYYMMDD |
Original Sequence No |
N |
15 |
6 |
|
Original Sequence Number as supplied by the Business Integrator User on the original Transaction. |
Homing Branch Code |
N |
21 |
6 |
|
Bank Branch Code of the Homing Account. |
Homing Account Number |
N |
27 |
16 |
|
Homing Account Number
|
Amount |
N |
43 |
11 |
|
Amount |
User Reference |
A |
54 |
30 |
|
Taken from the User Reference of the original transaction. |
Rejection Reason |
N |
84 |
3 |
|
Rejection Reason – Reason why the transaction unpaid. |
Rejection Qualifier |
N |
87 |
5 |
|
Qualifier that further explains the Rejection Reason |
Distribution Sequence No |
N |
92 |
6 |
|
Sequence Number as supplied by Distribution on the original Transaction |
FILLER |
A |
98 |
16 |
Spaces |
Filler – Not Used. |
Homing Account Name |
A |
114 |
30 |
|
Name of the Homing Account – taken from the original transaction received from the User. |
FILLER |
A |
144 |
57 |
Spaces |
Filler – Not Used. |
Unpaid – Set Trailer Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
014 |
The value 014 identifies the record as an Unpaid Set Trailer Record |
Data Set Status |
A |
4 |
1 |
L or T |
|
No of Debit records |
N |
5 |
9 |
|
Total Number of debit records within the User Code Set. |
No Credit records |
N |
14 |
9 |
|
Total Number of credit records within the User Code Set. |
Homing Account Hash Total |
N |
23 |
18 |
|
Total of all Homing Account Number |
Debit Amount Hash Total |
N |
41 |
14 |
|
Total value of all Debit transactions |
Credit Amount Hash Total |
N |
55 |
14 |
|
Total value of all Credit transactions |
Filler |
A |
57 |
144 |
Spaces |
Filler – Not Used. |
User Code Set Trailer Record |
|||||
FIELD NAME |
A/N |
OFFSET |
LENGTH |
FIX VAL |
DESCRIPTION / VALUE |
Record Identifier |
N |
1 |
3 |
019 |
The value 019 identifies the record as a User Code Trailer Record |
Data Set Status |
A |
4 |
1 |
L or T |
|
Number of Debit records |
N |
5 |
9 |
|
Total Number of debit records within the User Code Set. |
Number of Credit records |
N |
14 |
9 |
|
Total Number of credit records within the User Code Set. |
Homing Account Hash Total |
N |
23 |
18 |
|
Total of all Homing Account numbers in User Set. |
Debit Amount Hash Total |
N |
41 |
14 |
|
Total value of all Debit transactions in User Set. |
Credit Amount Hash Total |
N |
55 |
14 |
|
Total value of all Credit transactions in User Set. |
FILLER |
A |
57 |
144 |
Spaces |
Filler – Not Used. |