From R14,
In MT103+ whenever the Sender & Receiver Bank and (or) Account with
Bank country code is either ‘IL’ or belongs to the European union list of
Countries (maintained in a separate table) IBAN validations are made
mandatory. This is achieved through field 59A Beneficiary Customer, Subfield
Account in MT103+ namely, MT103.CONTROL
IBAN Generation
IBAN will be generated for a T24 account while opening the account if IBAN is
installed. System checks the Company table to retrieve the COUNTRY.CODE-
COMPANY.CODE to get the required data.
Based on the mapping defined for the bank code, branch code and account number
in the structure file, BBAN (Basic Bank Account Number) will be generated for the
account. Using IBAN generation algorithm, determine the Check digit of IBAN and
prefix BBAN with the Country code and Check digit to form complete IBAN
Once IBAN is created for the account, IBAN will be stored in ALT.ACCT.ID field
associated with ALT.ACCT.TYPE having T24.IBAN of Account record
The generated IBAN can be amended if required. In case of manual input, system can
validate the IBAN using check digit.
The IBAN related fields are available in the Funds.Transfer application. IBAN related
fields are also included in the Agency and Beneficiary application to ensure that the
IBAN of Agency records and also in Beneficary are also validated
The IBAN.BEN field contains the IBAN of the beneficiary account number.
BIC.IBAN.BEN - Is defaulted with the BIC code that is derived from the IBAN of the
Beneficiary blank for manual Input in case the BIC information is unable to be derived from the
IBAN of the Beneficiary. The BIC code of the valid IBAN of the Beneficiary is checked with the
BIC of the RECEIVER.BANK and in the absence of the same will be checked with the BIC of
the Credit Nostro Customer and if found to be different will be automatically defaulted by
appending ‘SW-‘ in the ACCT.WITH.BANK field.
BIC.IBAN.BEN.NAME - is defaulted with the Institution Name relevant to the BIC code. Blank
for manual Input in case the BIC information is unable to be derived from the IBAN of the
Beneficiary
BIC.IBAN.BEN.CTRY - is defaulted with the Country of the Bank relevant to the BIC code.
Blank for manual Input in case the BIC information is unable to be derived from the IBAN of the
Beneficiary
IBAN.BEN field contains IBAN number, the above three fields are optional. Even if one of the
above field is left blank – override message is displayed
BIC.IBAN.BEN.CITY - field BIC.IBAN.BEN.CTRY is renamed to BIC.IBAN.BEN.CITY of
the BIC.IBAN.BEN. The information will be mapped from the CITY field of the DE.BIC table
when defaulted.
BIC.IBAN.BEN.NAME - Can be manually input when no value in the field BIC.IBAN.BEN
BIC.IBAN.BEN.CITY - It is required that the values of these two fields be mapped in tag 57D.
A front end user can refer to ARC IB module on Bulk Processing for further details.
ACTIVE.PASSIVE.EXT
Transaction type used to handle transfer funds from ACTIVE account given in
FT.BULK.MASTER to NON T24’s PASSIVE account given in
FT.BULK.ITEM
Transaction type given here will be overridden when
FT.BLK.IT.TRANSACTION.TYPE is provided at FT.BULK.ITEM level
Mandatory for MULTI
Should be a Valid record in FT.TXN.TYPE.CONDITION
ACTIVE.PASSIVE.INT
This field holds the Transaction type used to handle transfer of funds from
ACTIVE account given in FT.BULK.MASTER to T24’s PASSIVE account
given in FT.BULK.ITEM
Used only for CREDIT processing
Transaction type given here will be overridden when
FT.BLK.IT.TRANSACTION.TYPE is provided at FT.BULK.ITEM level
BULK.TYPE.ID
Name of Bulk Update type.
Alphanumeric characters are allowed. Id should be meaningful, so that it reflects the
mode of bulk process (SINGLE or MULTI)
DD.PARAM.ID
A valid DD.PARAMETER id is given for DIRECT.DEBIT processing.
Not mandatory.
DESCRIPTION Free text field, which hold the information about bulk update type
Mandatory field
Text upto 35 characters of type A can be given
MODE.OF.TRANSFER
Holds the mode of transfer to be used in the payment process
Reserved for Future Use
PROCESSING.DAYS
Number of Working or Calendar days to be added with Today is given here. This will
be defaulted in FT.BULK.MASTER’s PROCESSING.DATE field.
This value can be overridden at Bulk Master Level
Values like 1C, 2W, etc are allowed
Mandatory Input
SINGLE.MULTI
Mode of Bulk update type is given.
SINGLE :
CREDIT - Initially funds are transferred from Active account to Wash account. And
then each Passive account given in FT.BULK.ITEM is credited from the Wash
account
MULTI :
CREDIT - Every time Passive account given in FT.BULK.ITEM is credited from the
Active account
DEBIT - Every time Active account is credited from the Passive account given in
FT.BULK.ITEM
The value given in this field can be overridden at Bulk Master Level
Mandatory Input
Only SINGLE or MULTI is allowed
VERSION
A version of Application, which will be used to do payment through OFS in Payment
process
Currently restricted to use FT version for Credit upload processing.
Mandatory Input
Valid record in VERSION
WASH.ACTIVE Holds Transaction type used to handle transfer funds between
ACTIVE and WASH account
Used for both DEBIT and CREDIT processing
Mandatory for SINGLE type
Should be a Valid record in FT.TXN.TYPE.CONDITION
WASH.PASSIVE.EXT
Transaction type used to handle transfer funds from WASH account given in
FT.BULK.MASTER to NON T24’s PASSIVE account given in FT.BULK.ITEM
Used only for CREDIT processing
Transaction type given here will be overridden when
FT.BLK.IT.TRANSACTION.TYPE is provided at FT.BULK.ITEM level
WASH.PASSIVE.INT
Transaction type used to handle transfer funds from WASH account given in
FT.BULK.MASTER to T24’s PASSIVE account given in FT.BULK.ITEM
Used only for CREDIT processing
Transaction type given here will be overridden when
FT.BLK.IT.TRANSACTION.TYPE is provided at FT.BULK.ITEM level
Mandatory for SINGLE type
Should be a Valid record in FT.TXN.TYPE.CONDITION
Items will include information such as the destination account, and amount.
Items may also indicate the payment type to be used (eg BACS or CHAPS),
which will be translated to different FT.TXN.TYPE.CONDITION records on
the ultimately generated FT.
Running totals include total valid amount, and total amount including invalid
items, are stored and updated on the bulk header. The users will be able to
amend any items, including invalid items, before the bulk is authorised –
which updates the bulk header totals accordingly.
Therefore, the Bulk Master will contain a total for the amount that a corporate
customer will be debited/credited, upon approval. It is possible to approve a
batch without all items being in a valid status – in this case, the invalid items
will not be processed.
Suppose the corporate customer wishes make payment for monthly expenses,
it will generate multiple credits. The customer is particular about having only a
single debit against the accounts for the bulk credit payments. Hence, the
Single Multi flag is set to ‘Single’
As the corporate customer requires a single payment to the ‘active’ account, a
‘wash account’ is required, to net all the payments and pass a single payment
to the ‘active’ account.
Once the Bulk Items are created, the user should also update the status as
‘Ready’.
Goto: User Menu -> Payment Services -> Bulk Payments -> FT Bulk Items ->
Input FT Bulk Item
To enter a bulk item, the user must enter the Bulk Master Id
Once the first item is committed, the user can continue to add additional items
using the same BULK.MASTER @ID.