Process Flow

The transaction management module helps the retail user initiate and manage different types of transactions which includes:

• Funds Transfer

• Payments

• Collections

The transaction management module depends on the following, that is, the following setup must be available before the transaction facility can be provided to the retail user.

Administrator Setup:

• Common codes setup for the application

• Property Manager setup for the application

• Menu profile setup for the user

• Financial Transaction Maintenance

1. Network Maintenance

2. Transaction Type Definition

3. Network Products

4. Network Properties

5. Correspondent Banks

6. Bank Repository

7. FT Rules

• Currency Maintenance

1. Currency Parameter Maintenance

2. Currency Holidays

• FX Maintenance

1. Transaction Rate Code Mapping

2. Exchange Rates

• Limits

1. Transaction Limits

2. Entry & Approval Limits

3. Accounts Limit

• Accounts Access for Users

• Country Parameter Maintenance

• Float Maintenance

• Spread Maintenance

The Transaction Support Services maintained by retail user which includes:

• Counter party maintenance for registering personal payees for payments and collections

• Manage mandates for collections

• Manage Billers for registering standard payees

With the above setup available in the e-Banking application, the retail user can perform the following activities:

• Initiate transactions (Funds Transfers, Payments and Collections). The transactions can be one time or recurring. The transactions can be instantaneous or scheduled

• The transaction date and the tentative value date of the transactions are decided based on the date calculation logic which is discussed in the following section

• The user can save the transaction and initiate it at a later point in time

• In case the transaction amount exceeds the amount required for RM approval, the initiated transaction needs to be approved by the relationship manager of the bank before further processing

• In case of funds transfer, if the transaction is instantaneous transaction, then the posting of the transaction occurs instantaneously in the backend (after all the required approvals are through). In case of scheduled transaction, batch programs (PROCSHLDS and MAKEPMTS) will be used to post the transactions on the scheduled date

• In case of payment transactions, the transaction could be within bank transaction or other bank transaction where the payee has an account in a different bank. If the payee has account within bank, then the settlement of the transaction happens within bank. In case of other bank transactions, the banking networks will be used to credit the payee. In case of scheduled payment transactions, batch programs (SETTLEMENT) will be used to post the transactions on the scheduled date

• In case of collection transactions, the transaction could be within bank transaction or other bank transaction where the debtor has an account in a different bank. If the debtor has account within bank, then the settlement of the transaction happens within bank. In case of other bank transactions, the banking networks will be used to credit the payee. In case of scheduled collection transactions, batch programs (PROCSHLDS and MAKEPMTS) will be used to post the transactions on the scheduled date. Mandates would be checked while initiating the collection transactions

Refer to operations manual to understand the batch programs PROCSHLDS and MAKEPMTS.

The process flow is diagrammatically depicted in Process Flow Diagram.

For details on date calculation logic, click Date calculation Logic.