In order to produce a file of payment instructions for importing into Business Internet Banking (BIB), a file will be created for the extract of a file in the SWIFT (Society for Worldwide Interbank Financial Telecommunication) MT103 file format required for BIB.
The file will be created in a directory that is defined in a batch parameter, and will be uploaded.
The Bank Interface field on the JU1CN Bank Account Details screen is used to determine the payment mechanism to be used i.e. Same Day Payment (SDP), International Payment (IP), SEPA Credit Transfer (SCT) or Inter-Account Transfer (IAT), and hence the information required on the payment file.
Where an International Bank Account Number (IBAN) is required, then this will be captured as the Account Number.
When the BJU2BA_BIB_PYMNT_FILE Bank Interface batch job is executed, all of the transactions on the EFT INSTRUCTION table for which the STATUS is P (Pending) and the BANK INTERFACE is BIB will be read.
A sequential ASCII file will be created as per the table below.
Note:
When the BIB Bank Interface batch job is run and the transactions are extracted from the EFT Instruction table, the system will read the Deal Number on the on the Deal Exchange Rate table linked to the Business Transaction linked to the EFT Instruction record. If a value is found, the system will read the Exchange Rate and calculate the currency value to be paid. The value will be calculated as follows:
Amount on the EFT Instruction table X Exchange Rate
This value will be Include for the:32A: Payment Amount field in the BIB file and the Deal Number will be include for the :72: field.
If a Deal Number is not found and the Currency is not equal to the Scheme Currency, the system will read the exchange rate with an Effective Date equal to current date and calculate the foreign currency value using this rate and update the Exchange Rate field on the Business Transaction linked to the EFT Instruction.
If an Exchange Rate is not found, an error message will be written to the error log and the transaction will be excluded from the file.
Note:
The BIB File process is automated and the batch will run daily at the following times: 10h00, 13h00 and 16h00.
The STATUS for each record extracted will be updated to C (Created).
|
TAG |
FIELD NAME |
LENGTH |
TYPE |
MAN/ OPT |
DEFAULT / SYSTEM VALUE |
|
:20: |
Transaction Reference |
16 |
A/N |
M |
|
|
:32A: |
Value Date |
6 |
N |
M |
Date Effective date on EFT Instruction (YYMMDD) Note: The Date Effective is YYYYMMDD and therefore the century must be dropped |
|
Currency Code |
3 |
A/N |
M |
Currency on the Business Transaction linked to the EFT Instruction record |
|
|
Payment Amount |
14-n,n |
N |
M |
Amount on EFT Instruction
n = number of decimal places for the currency of the amount
Decimal comma separator must always be present even if there are no decimal places in the amount |
|
|
:50A: |
Ordering Customer |
35 |
A/N |
O |
Debit DTI Account Number on EFT Instruction preceded by / |
|
:53a: |
Sender’s Correspondent |
34 |
A/N |
M |
|
|
:57a: |
Swift BIC |
11 |
A/N |
O |
Line Number on Debit DTI Account. Mandatory if the Bank Interface on the Debit DTI Account is SCT or IP. If the Bank Interface is null then the payment mechanism will be assumed to be SDP. |
|
Routing Code |
33 |
A/N |
M |
|
|
|
Beneficiary Bank Name |
35 |
A/N |
O |
|
|
|
Beneficiary Bank Address 1 |
35 |
A/N |
O |
|
|
|
Beneficiary Bank Address 2 |
35 |
A/N |
O |
|
|
|
Beneficiary Bank Address 3 |
35 |
A/N |
O |
|
|
|
:59a: |
Beneficiary Bank Account Number |
34 |
A/N |
M |
Credit DTI Account Number on EFT Instruction preceded by / |
|
Beneficiary Name |
35 |
A/N |
M |
Payee Name on EFT Instruction |
|
|
Beneficiary Address 1 |
35 |
A/N |
O |
|
|
|
Beneficiary Address 2 |
35 |
A/N |
O |
|
|
|
Beneficiary Address 3 |
35 |
A/N |
O |
|
|
|
:70: |
Payment References 1 |
35 |
A/N |
O |
Description on EFT Instruction. |
|
Payment References 2 |
35 |
A/N |
O |
|
|
|
Payment References 3 |
35 |
A/N |
O |
|
|
|
Payment References 4 |
35 |
A/N |
O |
|
|
|
:71A: |
Charging Instructions |
4 |
A/N |
O |
|
|
:72: |
Payment Instructions |
35 |
A/N |
O |
|
|
Payment Instructions |
35 |
A/N |
O |
|
|
|
Payment Instructions |
35 |
A/N |
O |
|
|
|
Payment Instructions |
35 |
A/N |
O |
|
Note:
The :70: Payment References 1 field is currently used to load a unique payment reference that is then provided in the bank statement file and is used in the bank reconciliation.
Using this field for the Building Society Roll Number will therefore present a problem in the bank reconciliation and these transactions will have to be manually reconciled.