The BJU2BE Multidata Interface batch job runs daily at a scheduled time. The file must be received by Multidata by 10h00 and therefore the scheduled time to run this batch job will need to be sometime before 10h00.
When the batch job runs, the system will read the EFT Instruction table and extract the data for which the Interface Type for the Debit Bank Account is MULTIDATA, the Status is P and the Date Effective is the same, as per the existing EFT extracts (ACB, FNB, LDC, etc.).
The system will read the Batch Parameter MULTIDATA IN and create a file as per the table below with the name contained in the Batch Parameter.
If there is more than one record extracted from the EFT Instruction table for which the values for the following fields are the same, the amounts will be summed and one record will be created on the MultiData file with the total amount:
- Credit Bank Sort Code
- Credit Bank Account Number
- Type of Account
- Credit Name
- Description
Note:
The Description on the EFT Instruction table is populated with the Annuity Payment run sequence number followed by a comma and the Scheme Registered Name. As the payment records that are being combined will all have been created in the same Annuity Payment run and for the same Scheme they will have the same Description.
The following record will be created with values as per table below.
|
MultiData Field |
EFT Instruction Field |
|
NAME |
Credit Name |
|
BANK CODE |
Credit Bank Sort Code |
|
BANK ACCOUNT NUMBER |
Credit Bank Account Number |
|
AMOUNT |
Sum of Amounts |
|
REFERENCE |
Description |
BUSY will be added to the file name.
When the file has been created, the file will be transferred to the directory specified in the Batch Parameter.
When the file transfer has completed, BUSY will be removed from the file name and an email will be created to inform Multidata that the file has been placed in the folder. Refer to Email below.
Note:
Currently the Multidata server polls the FTP server every two and a half minutes and will pick up a file even if the download has not completed. It will not pick up files with the incorrect file name and therefore if BUSY is included in the file name while the file is being loaded, it will not be picked up. Once the file has completed and BUSY removed from the file name, it will be picked up.
The Document Number on the Business Transactions linked to the EFT Instruction record will be updated with the value for REFERENCE (see table below) i.e. Scheme Code and Membership Reference Number.
Batch Header
|
Data Field |
Start Pos. |
Length |
End Pos. |
Format |
Default / System value |
|
HEADER |
1 |
2 |
2 |
|
BH |
|
MULTIDATA CONTRACT NUMBER |
3 |
6 |
8 |
N |
128926 |
|
PAYDATE |
9 |
6 |
14 |
|
Date Effective on EFT Instruction in the format YYMMDD |
|
DESCRIPTION |
15 |
10 |
24 |
|
PENSIOEN |
|
COMPANY NAME |
25 |
10 |
34 |
A |
PENSION77 |
|
LANGUAGE |
35 |
1 |
35 |
|
A |
|
FILLER |
36 |
6 |
41 |
|
Spaces |
|
2 DAY INDICATION |
42 |
1 |
42 |
|
J |
|
FILLER |
43 |
6 |
48 |
|
Spaces |
|
CREATION DATE |
49 |
6 |
54 |
|
Spaces |
|
TIME OF CREATION |
55 |
6 |
60 |
|
Spaces |
|
ONE DAY INDICATOR |
61 |
1 |
61 |
|
Space |
Transaction
|
Data Field |
Start Pos. |
Length |
End Pos. |
Format |
Default / System value |
|
BANKCODE |
1 |
6 |
6 |
N |
Credit Bank Sort code on the EFT Instruction |
|
|
7 |
2 |
8 |
N |
00 |
|
BANK ACCOUNT NUMBER |
9 |
13 |
21 |
N |
Credit Account Number on the EFT Instruction |
|
AMOUNT |
22 |
9 |
30 |
|
Amount on EFT Instruction. No decimal and filled with leading zero’s. |
|
TYPE OF ACCOUNT |
31 |
1 |
31 |
|
Type of Account on EFT Instruction Current = 1 Savings = 2 Transmission = 3 Bond = 4 |
|
PAYMENT TYPE |
32 |
2 |
33 |
|
62 |
|
NAME |
34 |
30 |
63 |
A |
Credit Name on EFT Instruction |
|
REFERENCE |
64 |
9 |
72 |
N |
Scheme Code and Membership Reference Number |
|
|
73 |
8 |
80 |
|
Spaces |
Once the file has completed, the system will read the batch parameter MULTIDATA MAIL and generate an email with the email address in the batch parameter and with the following information:
|
Name of data set |
KOS.KOSACB.PEN |
|
Amount |
Sum of AMOUNT fields |
|
Transfer date |
PAYDATE in batch header |
|
Total of transaction volumes |
Total number of transaction records |
The Unpaid Multidata EFT batch job will run daily at a scheduled time.
When the batch job runs, the system will read the Batch Parameter MULTIDATA OUT.
The system will retrieve the file with the name defined in the Batch Parameter and in the directory defined in the Batch Parameter.
The format of the file is as per the table below:
Transaction
|
Data Field |
Start Pos. |
Length |
End Pos. |
Format |
Description |
|
ACCOUNT HOLDER NAME |
1 |
30 |
30 |
|
|
|
POLICY NUMBER / REFERENCE |
31 |
9 |
39 |
|
Scheme Code and Membership Reference Number |
|
PAYMENT DATE |
40 |
8 |
47 |
|
|
|
AMOUNT |
48 |
11 |
58 |
|
|
|
REASON FOR REJECTION CODE |
59 |
2 |
60 |
|
|
|
REASON FOR REJECTION DESCRIPTION |
61 |
30 |
90 |
|
|
|
OLD BANK CODE |
91 |
6 |
96 |
|
|
|
OLD BANK ACCOUNT NUMBER |
97 |
13 |
109 |
|
|
|
OLD BANK ACCOUNT TYPE |
110 |
1 |
110 |
|
|
|
NEW BANK CODE |
111 |
6 |
116 |
|
Will only appear if the payment has been redirected to a new account within the same bank |
|
NEW BANK ACCOUNT NUMBER |
117 |
13 |
129 |
|
Will only appear if the payment has been redirected to a new account within the same bank |
|
NEW BANK ACCOUNT TYPE |
130 |
1 |
130 |
|
Will only appear if the payment has been redirected to a new account within the same bank |
|
TRACE NUMBER |
131 |
18 |
148 |
|
Unique number compiled by using BANKSERV user code, date, unique number created when file for bank is compiled. |
|
FILLER |
149 |
2 |
150 |
|
Spaces |
If there are no values in the following fields it indicates that the payment has been rejected:
NEW BANK CODE
NEW BANK ACCOUNT NUMBER
NEW BANK ACCOUNT TYPE
When the BJU2BF MultiData Redirect batch job runs, the system will find the transactions on the EFT Instruction table for which the following fields are equal to the value on the MultiData file as per the table below.
|
MultiData Field |
EFT Instruction Field |
|
ACCOUNT HOLDER NAME |
Payee |
|
POLICY NUMBER / REFERENCE |
Document Number |
|
PAYMENT DATE |
Transfer Date |
|
OLD BANK CODE |
Credit Bank Sort Code |
|
OLD BANK ACCOUNT NUMBER |
Credit DTI Account Number |
The system will sum the Amounts for the transactions found and if the result is equal to the value for AMOUNT on the MultiData file, will process the individual transactions as per the current EFT rejection functionality i.e. for each transaction find the Business Transactions for each transaction on the EFT Instruction table and update the Reporting Table with the following information:
|
Report Type |
EFT Rejections |
|
Date |
REJECTION DATE |
|
Process |
BT – Process |
|
Accounting Activity |
BT – Accounting Activity |
|
Transaction Date |
BT – Transaction Date |
|
Scheme Code |
BT – Scheme Code |
|
Reference Number |
BT – Membership Reference Number (where applicable) |
|
Credit DTI Account Number |
BT – Credit DTI Account Number |
|
Credit Bank Branch Code |
BT – Credit Bank Sort Code |
|
Amount |
BT – Amount |
|
Payee |
BT – PAYEE |
|
User ID |
BT – User ID |
|
Rejection Reason |
Read the Description for the UDPV Object EFT Rejection Reason where the Text Value is equal to the value for REASON FOR REJECTION CODE |
If the sum of the Amounts does not equal the value for the Amount on the MultiData file, a message will be written to the error log to indicate that the record could not be processed.
Accounting Transactions
Where the Process on the BT is ANNUITY PAYMENT, Business Transactions with the following Accounting Activity will be created:
|
Process |
Accounting Activity |
Stakeholder |
Dr Account |
Cr Account |
|
ANNUITY PAYMENT |
MEMPENPAIDRV |
FUND |
ACB RETURNS |
O/SPENPAYMENT |
|
ANNUITY PAYMENT |
MEMPENPAIDRV |
MEMBER |
MEMDEPOSIT |
O/SPENPAYMENT |
The Accounting Activity will be created with the dates, amount and all other details equal to the details on the original Accounting Activity.
Note:
These Accounting Activities must not be created with the Money Movement Indicator set. These transactions must not be written to the EFT Instruction.
A message will be written to the error log to indicate that a report has been created and the Admin Branches for which the report has been created will be listed in the same way as for other EFT rejections.
This means that the information will be available on the existing EFT report page.
If there are values in the following fields, it indicates that the payment has been redirected by the bank to a different account within the same bank from the bank account that was included in the original Multidata file:
NEW BANK CODE
NEW BANK ACCOUNT NUMBER
NEW BANK ACCOUNT TYPE
For each of these transactions the system will find the Transactions on the EFT Instruction table for which the following fields are equal to the value on the MultiData file as per the table below.
|
MultiData Field |
EFT Instruction Field |
|
ACCOUNT HOLDER NAME |
Payee |
|
POLICY NUMBER / REFERENCE |
Document Number |
|
PAYMENT DATE |
Transfer Date |
|
OLD BANK CODE |
Credit Bank Sort Code |
|
OLD BANK ACCOUNT NUMBER |
Credit DTI Account Number |
The system will sum the Amounts for the transactions found and if the result is equal to the value for AMOUNT on the MultiData file, will process the individual transactions as per the current EFT rejection functionality i.e. for each transaction find the Business Transactions for each transaction on the EFT Instruction table and update the Reporting Table with the following information:
|
Report Type |
EFT Redirections |
|
Date |
REJECTION DATE |
|
Process |
BT – Process |
|
Accounting Activity |
BT – Accounting Activity |
|
Transaction Date |
BT – Transaction Date |
|
Scheme Code |
BT – Scheme Code |
|
Reference Number |
BT – Membership Reference Number (where applicable) |
|
Old Account Number |
BT – Credit DTI Account Number |
|
Old Bank Branch Code |
BT – Credit Bank Sort Code |
|
Amount |
BT – Amount |
|
New Account Number |
Rejection/Redirection file – NEW BANK ACCOUNT NUMBER |
|
New Bank Branch Code |
Rejection/Redirection file – NEW BANK CODE |
|
New Account Type |
Rejection/Redirection file – NEW BANK ACCOUNT TYPE |
|
Payee |
BT – PAYEE |
|
User ID |
BT – User ID |
If the sum of the Amounts does not equal the value for Amount on the MultiData file, a message will be written to the error log to indicate that the record could not be processed.
Bank Account Details
The system will read the Bank Account Number on the Bank Account record linked to the Membership record. If the Bank Account Number is the same as the Old Account Number in the file, the Bank Account details linked to the Membership record will be updated with the new Bank Account details.
Note:
It is possible that the Member’s bank account details could have been updated since the payment file was created based on new information supplied by the member and the new bank accounts details must not therefore be updated based on the redirection details.