TECHNICAL SPECIFICATIONS · Web viewThe vendor will provide all relevant information (design,...

CORE BANKING REQUIREMENTS AND EVALUATION CRITERIA

Table of ContentsTECHNICAL SPECIFICATIONS.................................................................................2

1.0 Scope of the Solution........................................................................................21.1 Expectations from the Solution........................................................................21.2 Solution Requirements.....................................................................................21.3 Core Banking Functional Requirements..........................................................3

1.3.1 General Requirements...............................................................................31.3.2 Technical and Functional Requirements...................................................51.3.3 Loan Origination......................................................................................291.3.4 Loan Management...................................................................................381.3.5 Debt Management....................................................................................561.3.6 Risk Management and Compliance.......................................................681.3.7 Treasury Requirements............................................................................701.3.8 General Ledger Requirements.................................................................771.3.9 Customer Management............................................................................811.3.10 Deposits & Accounts Requirements.......................................................871.3.11 Clearing & Settlement...........................................................................971.3.12 Teller Operations.................................................................................1101.3.13 Trade Finance Requirements...............................................................1131.3.14 Safe Custody........................................................................................1251.3.15 Corporate Banking...............................................................................1261.3.16 Others..................................................................................................1271.3.15 Core Banking System Desired Features..............................................128

1.4 Implementation Requirements.....................................................................1282.0 EVALUATION CRITERIA.................................................................................131

2.1 Mandatory Evaluation..................................................................................1312.2 Technical Evaluation....................................................................................131

2.2.1 General Requirements Evaluation (19Mks)...........................................1312.2.2 Technical & Functional Requirements Evaluation (134Marks).............1322.2.3 Loan Origination Requirements Evaluation (81 Marks)........................1462.2.4 Loan Management Requirements Evaluation (271 Marks)...................1532.2.5 Debt Management Requirements Evaluation (211 Marks)....................1642.2.6 Risk Management & Compliance Evaluation (25 Marks)......................1722.2.7 Treasury Requirements Evaluation (168 Marks)...................................1742.2.8 General Ledger Requirements Evaluation (85 Marks)..........................1802.2.9 Customer Management Requirements Evaluation (130 Marks)............1842.2.10 Deposits & Accounts Requirements Evaluation (172 Marks).............1882.2.11 Clearing & Settlement Requirements Evaluation (300 Marks)...........1982.2.12 Teller Operations Requirements Evaluation (65 Marks).....................2112.2.13 Trade Finance Requirements Evaluation (306 Marks)........................2142.2.14 Safe Custody Evaluation (8 Marks)......................................................2252.2.15 Corporate Banking Evaluation (19 Marks)..........................................2262.2.16 Other Requirements Evaluation (10Marks).........................................2272.2.17 System Demonstration Evaluation (10Marks).....................................228

2.3 Overall Technical Evaluation........................................................................2282.3.1 Summary of Technical Evaluation.........................................................228

2.4 Financial Evaluation (30 Marks)..................................................................2282.5 Evaluation Method.......................................................................................2292.6 Response Format.......................................................................................229

of 274


2.6.1 Technical Proposal.................................................................................2292.6 2 Financial Proposal..................................................................................230

CBKL CORE BANKING REQUIREMENTS AND EVALUATION CRITERIA

TECHNICAL SPECIFICATIONS

1.0 Scope of the SolutionWith the advent of computer technology and the modern internet, banking systems around the world have undergone a massive transformation. In the past four decades, there has been a revolution of sorts that has introduced new methods of basic banking activities. The latest technological innovations have replaced traditional banking methods with modern and sophisticated systems. From simply a place to deposit money and lend money, the banks have emerged as an integral part of the economy and financial system of the world. They have grown to become an important institution in our society. This drastic change in the banking system occurred simply due to the evolution of banking technology. The key objective of implementing the core banking system is to improve the customer experience. This ensures customer convenience and allows “anytime and anywhere” banking. Previously, basic bank functions like maintaining records of the account holders, deposits, transactions, maintaining ledger records, customer information, loan accounts, and others were performed manually.

1.1 Expectations from the Solution

Banking and financial institutions have benefitted incredibly from the adoption of core banking systems. At the same time, customers are equally enjoying the aids of technology. For banks, core banking has become an integral part of their day-to-day functioning and offer great support. It has eliminated the need of performing tedious and redundant tasks manually. Assessing, managing and upgrading the data have become a lot simpler after the bank automation process has been introduced. Meanwhile, it has increased employee efficiency and productivity. Manpower and skills can now be put to better use. Broadly the expectations are that the core banking system will be able to handle Customer-On Boarding, Managing deposits and withdrawals, Transactions management, Interest, Payments processing (cash, cheques /checks, mandates, EFT, RTGS, PESALINK, Mobile Payments (MPESA) etc.),Customer relationship management (CRM) activities, Designing new banking products, Loans disbursal and management.CBKL invites interested parties that meet the qualifications listed in this document to submit proposals regarding their product and related service offerings. All information shall be submitted in the format stipulated in this RFP.

1.2 Solution Requirements

The bank (CBKL) is seeking to acquire a robust core banking solution to improve its banking operations and customer service offering. The procured Core Banking

of 274


Solution solution must be scalable, easy to manage and reconfigure, fault tolerant (hardware and software) and cost effective in order to achieve the objectives mentioned in this RFP and its subsequent addendums.The selected vendor is expected to provide the following hardware, software, installation, configuration, testing, integration services and training:

a. The vendor of the selected solution will install & mount, setup, configure and integrate the proposed solution with the identified systems, test and confirm the interoperability of the design.

b. The vendor will setup, configure and integrate the proposed solution to the bank’s objectives and specifications and fulfil the requirements published in this RFP.

c. The vendor will provide all relevant information (design, as-built configuration, disaster recovery information, etc.) for the installed solution. The provided information should be formatted to work in Microsoft Word and Excel.

d. The vendor will provide an operation & maintenance (O&M) manual that will cover all components and systems in a way that is easily understood.

e. The vendor will perform knowledge transfer of all programming to ensure CBKL can provide on-going maintenance for installed solution.

f. The vendor will provide sufficient training credits (for either online or premises based training) for 5 ICT staff to adequately operate the proposed solution.

The solution vision outlined above may evolve during the implementation period. All above configurations will require proposed systems to interface with existing bank systems. The selected vendor is required to study current environment (switch hardware and software configurations) and for successful implementation.In summary, the selected vendor will provide the software installation, configuration, testing, and configuration, software updates (if any), training, support and integration services for the proposed solution.Proposals that require computer hardware and server operating systems as part of their offering don’t need to cost out these components as a part of their proposal. These components will be procured by the bank’s Information Technology Services. However, the vendors must provide their recommended specifications and optimal configurations, including memory, number and type of CPUs, disk space for the proposed system hardware and all the necessary software in their proposals. The bank will separately procure the related necessary hardware to host any new management tool, as proposed by vendor.The proposed solution will be purchased through the proper channels of CBKL procurement. Once a contract has been reached, a contract will be issues and implementation of the new solution will begin. The system will be rolled out in a phased approach as estimated in the project timeline that is prepared by vendor as part of its proposal.

of 274


1.3 Core Banking Functional Requirements

1.3.1 General Requirements# General Feature Requirement

Criticality(Critical/ Nice to Have

Fully Supported / Partially Supported / Not Supported / To be customized

Vendor Comments

1 Availability of account / customer drill down details from all inquiry / transaction screens through the use of a hotkey enabling 360 degree view of the client, including limits and securities maintained delinquencies, relationship view, cheque return history, address change history, account snapshot.

Critical

2 Copy facility for transaction screens

Critical

3 Field level help options Nice to have4 Drill down enquiries to provide

consolidated details in one screen for all Retail Banking, Corporate Banking and Trade Finance information of a client

Critical

5 Unique codes for branches Critical6 Ability to define a single product

for multiple currencies instead of separate products for each currency

Critical

7 Availability of an in-built tool to facilitate creation of new reports independently by the bank without requiring a third party tool or vendor intervention

Critical

8 Maintenance of a business calendar with facility to change the business days as and when required.

Critical

9 Open source architecture to allow for integration of different systems in the bank

Critical

Hovering Facility10

System should support hovering facility at Start of Day/End of Day and Online. Hovering should

Critical

of 274


enable the system to recover charges/loan dues and installments automatically during EOD/SOD/.Online. .

11

Partial hovering should also be supported such that funds as they become available in the funding account, should be deducted by the system for credit to the charges/loan account

Critical

12

Provision to define Hovering Type (Manual, recovery of charges, recovery of loan installments, etc.)

Critical

13

Provision to define the account from which amount has to be withdrawn towards hovering

Critical

14

Provision to define the account into which the amount withdrawn has to be credited

Critical

15

Define the charge type for which Recovery is done

Critical

16

Define the charge on Amount with the applicable service tax amount

Critical

17

Date of Entry and Start date of Hovering

Critical

18

Text field for providing narration to be used for recovery transaction

Critical

19

Text field for providing hovering remarks

Critical

1.3.2 Technical and Functional Requirements#

Functionality

Requirement Criticality (Critical/Nice to Have)

Fully Supported / Partially Supported / Not Supported / To be customised

Vendor Comments

of 274


1 The system should comply with major international regulations such as UCP, URR, ISP, URDG and e-UCP, facilitating all standard Trade Finance operations.

Critical

2 The system should support multi country, multi-region and multi-branch (within a region) setups with different base currencies and different products, features, calendar and workflows local to the country/region/branch.

Critical

3 All processing rules should be parameterized so that the deviations mentioned in 1.3 can be achieved by parameter setting

Critical

4 All parameter settings (rules) should be able to do centrally

Critical

5 Facility to localize the business rules as per the country’s rules and regulations when operating in multiple countries.

Critical

6 For all customer transactions, customer details should be taken from the core system. But additional customer data like special email addresses and contact nos. etc. should be able to maintain in Trade Finance system

Critical

7 For all transactions, the system should generate and post the accounting entries automatically according to the rules defined (cost centre wise)All accounts related to the relevant customer should be popped up for selection and facility to select more than one account.

Critical

8 For each transaction, only the relevant charges should be mapped and the accounting entries pertaining to charges should get generated and posted online to all the respective accounts automatically on authorization of the transaction. There should be a facility to collect charges from any designated currency.

Critical

9 In each and every branch, multi- Critical

of 274


currency transactions should be possible. Charges and commission should be able to get from any designated currency

10 For each and every transaction, system should automatically get all the relevant rules (accounting, charge, commission rules etc.) linked to the transaction. There should NOT be any manual selections of the rules or manual calculations on charges, commissions etc.

Critical

11 For each and every data entry, validations for mandatory fields and a mechanism for error correction before final authorization without re-entering the whole data set again should be there. And also the modifications done should be highlighted for the authorizing officer.

Critical

12 Every authorization should show all the required details for the officer and with the authorization, posting of all the relevant accounting entries should be done automatically and the SWIFT messages created (if any) should be written to a pre-defined outside location

Critical

13 Updating of all accounts should be online on authorization of the transaction.

Critical

14 Exchange rates should automatically be linked to the transactions directly from the core banking/treasury system everywhere rates are applied

Critical

15 Separate facility should be available to create accounting entries outside a transaction with or without a transaction reference.

Critical

16 There should be a facility to read a pre-defined external location and initiate or apply transactions received through SWIFT messages with a single click.

Critical

17 There should be a facility to configure auto generation of

Critical

of 274


reminders at pre-defined dates or periods

18 Each & every country should be able to perform their Day–End process independently

Critical

19 Daily position with ref. No should be reported to treasury. For future transactions value date should also be reported.

Critical

20 Should provide online real time/batch interfaces( as mentioned in Interfaces section) for all required external systems such as Core Banking system, Treasury, Document Management system, SWIFT etc.

Critical

21 There should be a facility to maintain codes where ever possible. (Consignment, industry, H.S. Codes, collateral, etc.)

Critical

22 Facility should be there to define authority levels and restrict every transaction to an authority level

Critical

23 There should be a possibility to setup dual/higher authorization for any required transaction

Critical

24 All standard reports & queries (Outstanding reports, Customer exposure reports, income reports, profitability, volume reports etc.) should be inbuilt in the system and a separate user friendly report writing tool should be provided for ad-hoc report generation. Generated report should be able to export to commonly used formats such as Excel, Word, PDF, xml.

Critical

25 All advices, letters, reminders etc. should be generated by the system along with the relevant transaction or on pre-defined periods with the printing facility and/or, e-mailing facility and/or SMS facility

Critical

26 The system should provide a mechanism to predefined the formats of the above documents (in 1.29) with variables for customer and transaction specific values such as Name, address, transaction amount etc.

Critical

of 274


27 All documents generated by the system for other processing units like SWIFT messages should be consistence with their standard format. All possible validations for such formats should be embedded in the system.

Critical

28 Ability to highlight selected areas of advices generated by the system is preferable.

Critical

29 Transaction viewing facility with accounting entries and all other related data such as margin, credit line and exchange rate detail should be available in a single selection of the transaction. This view should also contain accounting entries created outside the transaction but related to it.

Critical

30 System should facilitate to create and maintain Local and Foreign Bank BIC Codes, Name and address.

Critical

31 The users should be able to view the accounting entries generated at transaction level.

Critical

32 There should be provision for transfer pricing in the system, so that the commission income of Trade Finance transactions are apportioned between the cost centers (separate GL)

Critical

33 For transactions under special schemes such as grants and ADB loans, a facility to define the liability at transaction level is preferable. Here, the charges must be recovered from the customer account.

Critical

34 For transactions of a non-Bank customer, there should be an ability to debit/credit designated GL accounts. (eg. Export LC advising for non-customers and LC advised through other banks)

Critical

35 Facility for inter-linking with shipping companies for electronic data exchange and comply with Bolero is preferable.

Critical

of 274


36 An online interface to the treasury, so that a request for a special exchange rate can be done within the transactions is preferable. Here, the acknowledgement should also be possible (accept or reject). If accepted, special rate should be automatically mapped to the specific transaction with the treasury reference number without any modification.

Critical

37 Dash Board Facility is preferable Critical38 Should provide system

documentation materials (data dictionary, Installation guide, technical manual, user manual, Installation manual, backup recovery procedure, system architecture etc.)

Critical

39 Should provide comprehensive user and technical training on the system as well as the trouble shooting sessions. Details of the training plan should be provided. (Site visits also preferred)

Critical

40 Training programs should be conducted annually by the vendor for Bank Technical and Functional staff on Bank request.

Critical

41 An issue reporting mechanism should be provided so that the status of the issues raised by the bank should be visible at any time.

Critical

42 Reported issues should be attended within a reasonable time period according to their criticality

Critical

43 Onsite technical support should be provided for implementation and post implementation until key issues are resolved.

Critical

44 Document management capabilities are preferable.

Critical

45 Black list checking facility is preferable

Critical

46 Facility to maintain special remarks at transaction level and auto pop-up of remarks at every retrieval of transaction is preferable.

Critical

of 274


47 The Trade Finance solution offered in this tender should have been using in at least one commercial bank (having at least 300 branches globally and operating in more than one country) in Asian region during last 3 years.

Critical

Data Requirement for Integrated Risk Management System

48 • There should be a facility to extract all details of the collateral maintained against Trade Finance facilities,

Critical

49 • all details of default Transactions,

50 • all Details of recovery51 • all details of Provisions to be

made52 • all details of guarantees granted

Functional Requirements - Imaging/Document Management capabilities

53 Document management facility is preferable

Nice to Have

54 Facility to Scan, Upload, View, remove and annotate documents to underline transaction and to specific event

Nice to Have

55 User defined Indexing and Categorization of scanned Images

Nice to Have

56 Facility to manipulate the image - zoom, rotate, print, invert etc.

Nice to Have

57 Should support limited bandwidth preferably encode the image and parameterized cache management capabilities.

Nice to Have

58 System should allow bank users to upload/attach documents directly from the transaction screens, at various events of the transaction lifecycle.

Critical

59 Support various document formats (Image, PDF, Word, Excel, tiff, others)

Critical

Technical Requirements60 The system should comply with

latest technology Critical

61 Application should support major Critical

of 274


RDBMS’s preferably IBM i DB2, Oracle(exadata), Sybase, Informix or SQL servers etc.

62 System should comply with banks Information Security Policy (ISP) rules security and Single Sign On

Critical

63 If the total solution is a web based one, dedicated API/Web Services should be provided to interact with other systems such as Core Banking, Exchange Rates, Treasury, Internet Banking, DMS..etc. as mentioned in Interfaces section

Critical64 Critical65 Critical

66 System should provide configurable batch processing and scheduling functions which ease to automate start of day and end of day operations

Critical

67 There should be a facility to purge history records with retention period. Option to take necessary reports and backups of purged data should be available. Also it should be clearly mentioned the archiving procedure of data.

Critical

68 System response time should be within acceptable industry standards

Critical

69 Should provide mechanism for data migration. Data should be migrated to the system, with the relevant validations.

Critical

70 On-site technical support should be available for implementation and post implementation until all key issues are resolved

Critical

71 Application should support proper version controls

Critical

72 There should be a roper way of handling application logs/traces/audit trails and should be able to extract in readable format whenever necessary.

Critical

73 Audit Trails should be available to identify all activities done in the system with the user ID, date and time together with the activity done.

Critical

74 System rollout should not contain Critical

of 274


any client side software installations

75 Parameter configuration should not be too complex

Critical

76 The software should have QA certification.

Critical

77 Bank logo should be displayed in the system display

Critical

Technical Requirements - Interfaces

78 Interface to debit/credit customer/GL accounts in core system.

Critical

79 This interface should support multi-currency, cost centers, and all types of accounts (CA/SA/DFC/RFC, GL, Nostro/Vostro etc.).

Critical

80 And also should support rounding-off facility and the remainder of the amount should be accessible.

Critical

81 Should be able to use the OD limit if available for current accounts

Critical

82 Should facilitate for forced debit also

Critical

83 GL entries to the core system should be able to either summarized/individually post as required

Critical

84 This should be an online real time interface.

Critical

85 Interface to get customer details from the core system.

Critical

86 This interface should get details of the customer in the core system through the unique identification number (CIF)

Critical

87 This should be an online real time interface

Critical

88 Interface for customer facility update in core system.

Critical

89 Relevant limit, sub limits and Overall limit of the customer should be updated accordingly

Critical

90 Interface to inquire a/c status & a/c balance for a given customer from the core system

Critical

91 This should be an online real time Critical

of 274


interface92 SWIFT interface should support

both Incoming and Outgoing message processing automatically.

Critical

93 This interface should be able to receive SWIFT messages from an outside location and should be able to create transactions or to apply the new requests to the relevant prevailing transactions with only single click

Critical

94 Interface to treasury for currency exchange rates

Critical

95 Online real time interface for treasury for special exchange rates from treasury

Critical

96 With this interface acknowledgement /rejection should be possible by transaction initiation party

Critical

97 if accepted, should apply to the transaction with the reference number given by the treasury

Critical

98 Interface for position reporting to treasury whenever a currency conversion takes place

Critical

99 Interface to e-mail server Critical100

This should be an online real time interface

Critical

101

Interface to SMS server Critical

102

This should be an online real time interface

Critical

103

Interface to - Interbank online Payment System‖ should facilitate pre-defined currencies separately.

Critical

104105

Interface with DMS should support all Trade Finance document handling

Critical

106

Common Interface for external servers which could be setup according to bank needs.

Critical

107

Through this interface it should be possible to transfer file/s to required external servers. e.g. for Customs, Central Bank

Critical

108

For all Interfaces system should cover data pull out and push in

Critical

of 274


from other software systems of the bank

Security and Control109

System should use the employee’s provident fund number as the user ID for the internal users. In addition, user details should be available in the system for Inquiry or report. For eg. name , creation date, user privileges, termination date, department.

Critical

110

Application Manager should be able to handle the access granting facility for application functions .According to the assigned privileges, user should either be able to access the function or he/she is restricted to access it.

Critical

111

Facility should be there to handle the following as parameters in order to cater bank’s password policy.

Critical

112 1 Length of the password Critical

113 2 Complexity of the password Critical

114 3 Duration of password expiration Critical

115

4 Number of invalid login attempts allowed

Critical

116

System should log all the unsuccessful login attempts with the attempted user ID, date, time, and the remote workstation.

Critical

117

System should compel the users to change the password at the initial login and whenever the password is reset by the administrator

Critical

118

System should encrypt all the confidential information when being stored in the database and while being transferred through networks.

Critical

119

System should maintain hash values of the passwords when being stored in the database.

Critical

12 System should be browser Critical

of 274


0 independent121

System should log all the activities performed by users including the system administrators, with the details such as user ID, Date, Time, action performed and work station ID, success or failure. In addition, all the interface transactions should be able to separately be identified.

Critical

122

System should facilitate auto archival of the log entries after a parameterized value of size/ number of days.

Critical

123

System should automatically logout the users after a predefined period of being idle.

Critical

124

System should allow parameterizing the time duration for session timeouts.

Critical

125

System should automatically lock the users who have not logged into the system for a predefined period and this period should be parameterized.

Critical

126

System should allow the administrators to manually lock the users/ unlock the users and all the events should be logged.

Critical

127

System should validate all the data input fields in order to prevent attacks such as SQL injections.

Critical

128

System should restrict to the users to log into the system only from one workstation at a time

Critical

129

System should allow the users to build queries and generate reports from database/ audit trails.

Critical

130

System should have flexibility of providing any exception report. This report should be accessible only for the authorized authorities.

Critical

131

A report should be generated indicating the success/ failure of the batch processes. Any failure should be recorded with the failed item and the reason for failure.

Critical

132

System should support segregation of duties. (The same user who makes the data entry should not be

Critical

of 274


allowed to authorize)133

System may maintain the sessions in a mechanism other than cookies.

Critical

134

No direct access to the database should be allowed for the application users.

Critical

133

End users should not be displayed the directory path of the resources while being accessed specially through web browsers.

Critical

134

Application should handle all possible exceptional and erroneous events and appropriate user friendly error messages should be displayed. i.e. server level messages should not be displayed to the end user

Critical

1.3.2.1 Other Technical Requirements

REQUIREMENT

Requirement

Criticality (Critical/N

ice to Have)

Fully Supported /

Partially Supported / Not Supported / To be customized

Comments

General and Mandatory requirementsThe system should run on the latest release of Oracle database, Application server(jboss or weblogic etc.).

Critical

The system should be compatible with Redhat and/or Oracle Linux Operating system.

Critical

The system should be Cloud ready, and allow for multitenant deployment - inhouse and on Public cloud

Critical

The system should support and integrate with ISO 8583 messaging Standards- Mandatory

Critical

The system should be Componentized designed

Critical

The system should support Critical

of 274


application Clustering at application levelThe system should have an Open API (Application Programming Interfaces ) interface to integrate with other existing and new 3rd party systems

Critical

The system should have automated code samples for all processes for ease of solution development and code re-use

Critical

The system should be able to integrate with any ATM switch/Payment gateway

Critical

The system should provide High Level Encryption of Customer Data both at rest and on transit

Critical

The system should provide Report Writer for building reports on demand basis

Critical

The system should be able to seamless integrate with Card Issuing System and provide a single interface for Customer records acquisition and validation

Critical

The system should be able to support card generation for joint account holders, and or account with many mandates

Critical

The system should be able to allow for automatic posting of Credits to customer accounts once Cheque truncation at Branch level

Critical

The system should be able to send Dr and Cr notifications to customers in real time and automatically

Critical

The system should be able to automate End of Day/ Start of Day Activities

Critical

The system should be able to integrate with (MFA)Multifactor Authentication Solutions for bank staff login.

Critical

The system should be able to integrate with SIEM solution for

Critical

of 274


event correlation and analysisThe system should be able to support biometric signature for over the counter customer transactions.

Critical

The system should support bulk file upload of transactions (Credits and debits)

Critical

The system should support transfer of accounts from one branch to another

Critical

The system should support charge waivers at product and account level

Critical

The system should support automatic mailing of statements during EOM

Critical

The system should capture unique transaction codes for all transactions(e.g. cash deposit, cash withdrawal etc.)

Critical

The system should enable transaction categorization data to be collected efficiently, using a simple interface and pre-defined lists of values for each category variable e.g. Cash deposit, EFT, etc.

Critical

Associate transactions with Profiles that define active data fields, default value logic for transactions.

Critical

The system should distinguish customer & system initiated transactions using unique transaction codes.

Critical

Ability to define a single product for multiple currencies instead of separate products for each currency

Critical

The system should be able to do validation for black listed customers

Critical

The system should allow multiple search criteria on customers(Id, Passport, Company registration number etc.)

Critical

The system should provide ability to view customer closed customer accounts data and past transactions.

Critical

of 274


The system should provide a user definable workflow for opening of Accounts

Critical

The system should provide ability to exempt Savings A/c’s below minimum balance from accruing interest

Critical

The system should provide a way of exempting some account above some amount from charges e.g. ledger fees

Critical

Facility to capture transaction description/narrative to be printed & viewed on customer statements and enquires

Critical

Possibility to classify accounts into different types

Critical

Restriction on Credit / Debit transactions at the account / product level

Critical

Automatic validation of exception conditions while performing transactions

Critical

End of Day checks for incomplete transactions during branch sign out.

Critical

End of Day checks on transactions posted but not authorized

Critical

Automatic processing of Inter Branch transactions

Critical

Automatic printing of vouchers and advices during transaction posting

Critical

Support the Multi Currency Account functionality - management of multiple currencies under a single account number

Critical


Critical

The system should create audit log entries for all configuration changes while retaining old values

Critical

of 274


Hardware and Software RequirementsThe system should scope and provide detailed requirements for both test and development, production, and DR site. This should form part of the solution pricing and to be delivered by the vendor; This includes: -

Critical

Server requirements consistent with System baseline configuration and various workloads - Number of Physical and virtual servers for both sites

Critical

Operating system licenses as per the solution baseline recommendations

Critical

Database systems and various licensing for the same

Critical

Central Data Storage scoping, and proposal for the same in line with best practice for the proposed system, and projected growth rates for both sites

Critical

Network scoping, and proposed network devices to support the solution. This includes SAN switching, and backbone network to support integrations at Primary Site and Disaster Recovery Sites

Critical

Tools and licensing to enable Clustered system configuration at application level

Critical

Tools and licensing to enable database active setup and replication to Disaster Recover sites

Critical

Business Continuity Planning

Redundancy and Business Continuity/Disaster Recovery

Critical

System server and client software shall maintain its integrity in case of power failures and abrupt shutdowns.

Critical

of 274


System shall be capable of restarting and recovering after system failure with no loss of data or software components.

Critical

System shall provide the capability to identify the existence of program and/or system discrepancies and issue an alert to the system administrator.

Critical

System shall provide ability to limit the types of operations (e.g., read, write, delete, data dictionary modification) that can be performed by individual users on given data or program files.

Critical

System shall provide Incremental, differential, and full backups and restore of the database, core and customized software, software and database configuration options, user preferences and rights, etc.

Critical

System shall provide a robust hardware infrastructure that can support high availability, load tolerance, real-time failover, as well integration into the bank offsite disaster recovery infrastructure. This includes:

Critical

Individual server configuration, e.g. clustering (physical and virtual)

Critical

Central data storage configuration (SAN), with High IOPs performance

Critical

Server and network configurationCritical

System shall provide a disaster recovery solution including a complete offsite server and networking installation that has the capability to roll from the primary site to this offsite location within a 24-hour recovery window. This roll over shall include all applications and data.

Critical

of 274


Scalability

The selected vendor shall analyze current and projected future system volumes. The selected vendor shall provide a system that shall accommodate anticipated transaction levels using these analysis results. The system, including programs, database, and ancillary hardware and software systems shall be able to retain its performance levels when adding additional users, functions, and data. Please indicate how your solution(s) would address the following scalability issues:

Critical

Maintaining a consistent throughput with increased transaction rates

Critical

Avoiding high levels of persistent disk I/O

Critical

Minimizing network traffic between the client application and the server

Critical

Balancing the response time needs of mission critical business with other applications

Critical

Cost-effective plan for implementing "Scale-Up" systems in the event of unexpected growth

Critical

Optimizing database indexing techniques

Critical

System Administration

System shall provide administration tools and procedures for the ongoing support and maintenance, including customization, of the proposed solution. This includes:

Critical

Database Administration Tools - Specify which tools are provided by the vendor and which are provided by the database vendor

Critical

of 274


O.S Administration Tools - Specify the tools provided by the contractor and which are provided by the system vendor

Critical

System Administration Tools - Specify any tools being proposed to support or supplement the application solution being proposed as well as for support of any third-party software

Critical

System shall provide ability for users who encounter usage or technical problems receive clear error messages relating to:

Critical

The exact status of the transaction

Critical

The options for on-line help

Critical

The options for additional help including reason and possible solution

Critical

SecurityThe system shall comply with all bank mandated security protocols and standards that apply.

Critical

The system shall provide the ability to encrypt selected data fields.

Critical

The system shall provide centralized user management (add, delete, change, access levels etc.).

Critical

The system shall provide users ability to change their own password.

Critical

The system shall provide integration with the system user logon ID and password and the existing operating system(s) (single logon).

Critical

The system shall support the use of directory services and authentication mechanisms such as MS Active Directory or LDAP.

Critical

The system shall provide automated Critical

of 274


mechanisms to logout users based on an inactivity/idle timeout period.The system shall support secure communications utilizing SSL over HTTPS for Internet based transactions and/or some form of data encryption for client/server transactions.

Critical

The system shall provide application level security, including how it handles user or group security access configuration and enforcement in the following areas of the system:

Critical

Row/field level on data elements in databases

Critical

Access to system functionality or modules

Critical

Access to specific fields or screens in the user interface

Critical

The system shall provide users ability to change their own password.

Critical

The system shall provide integration with the system user logon ID and password and the existing operating system(s) (single logon).

Critical


Critical

The system shall provide automated mechanisms to logout users based on an inactivity/idle timeout period.

Critical

The system shall support secure communications utilizing SSL over HTTPS for Internet based transactions and/or some form of data encryption for client/server transactions.

Critical

The system shall provide application level security, including how it handles user or group security access configuration and

Critical

of 274


enforcement in the following areas of the system:

Row/field level on data elements in databases

Critical

Access to system functionality or modules

Critical

Access to specific fields or screens in the user interface

Critical

The system should be securely accessed Via https if web based or secure connection if client is installed in user PCs. Passwords in configuration files should be encrypted

Critical

Security controls

Ability to restrict logins based on working times e.g. outside working hours

Critical

Ability to restrict multiple sessions in different workstations

Critical

System shall provide ability to easily upgrade to future operating systems, database and third party software and utilities.

Critical

System shall provide an open architecture for user and system interfaces based on current and industry-accepted standards, methods, and protocols such as HTTP, XML, SOAP, FTP, etc.

Critical

All database edits, notifications and customer transactions must be logged for audit. Users must be able to query the logs for specific events or recent activities and view filtered log reports, using a simple interface with fields for search and sorting parameters.

Critical

Licensing

of 274


State the licensing option(perpetual pricing or subscription pricing)

Critical

Data migration from previous systems

Critical

Interfaces

ATM / POS interface as per ISO 8583 Standard

Critical

ISO Interfaces for Mobile and internet banking systems

Critical

Interface with Cheque book printing machine - Linked server support functionalities

Critical

RTGS / SWIFT interfaceCritical

CTS (Cheque Truncation System)Critical

Interface with Financial Inclusion / hand held devices

Critical

Interface with MICR machineCritical

Open API Interface to handle any third party interfaces

Critical

Export transaction data to other systems on a daily basis

Critical

Provide Secure exchange of data between various systems in the Bank e.g. encryption of Data exchanges to Cheque clearing, SWIFT, and any other systems

Critical

User InterfaceSystem shall present data to users such that a minimum of navigational effort is required. The data elements required to complete a job function, whether to inquire/read only or data entry, must be readily available.

Critical

System shall provide a user Critical

of 274


interface that integrates information from multiple components into a unified display by business area or work type.System shall provide ability for the user to complete each step in the workflow process within a given screen (e.g., the user will not need to navigate multiple screens to complete a task in the workflow).

Critical

System shall provide ability to create multiple user levels based on user roles (e.g., Teller) and respond differently to each role

Critical

System shall provide a method to "drill down" to related data as needed by job function.

Critical

1.3.2.2 Reporting RequirementsRequirements. Requireme

nt Criticality (Critical/Nice to Have)

Fully Supported / Partially Supported / Not Supported / To be customized Comments

Comments

FeatureAbility of the system to generate online real time MIS(Management Information System) and ad-hoc reports

Critical

Ability to generate all CBK regulatory reports

Critical

Ability to link branches to the H.O for consolidated views.

Critical

Ability to collate information of various branches and its departments to the head office for MIS reporting.

Critical

Ability of the higher level to generate reports of the lower level(such as branch level), if

Critical

of 274


required.Ability to define any report / MIS printing at the Branch, region or H.O based upon defined parameters e.g. at the time of end-of-day, occurrence of a particular event, start-of-day.

Critical

Ability of the system to upload data received in any electronic format from branches outside the core banking system for consolidation and merging for reporting purposes.

Critical

Ability to define reports as compulsory report and print them at user definable periods e.g. end of day, beginning of day etc. The system should also provide an option to allow the user (Bank) to select the location of each report printing. (E.g. at the head office and branches or only at the branches.)

Critical

Ability to schedule spooling/printing of non – critical reports e.g. x report after every 10 days etc.

Critical

Specify the format and layout of reports

Critical

Summarize and total the information to be reported

Critical

Select records to be included in the report

Critical

Select details from each record to be included

Critical

Perform arithmetic calculation on the information selected

Critical

Download data to/from third party software.

Critical

Ability to download data to any user definable formats e.g. flat files, word documents, excel sheets etc.

Critical

Ability to print reports as on a particular date, any user defined date or range of dates for the selected criteria (e.g. stop payments, transaction details etc.)

Critical

Ability to interface with other banking application used by the

Critical

of 274


bank e.g. treasury, risk management etc. or 3rd party systems e.g. RTGS, etc. or legacy systems of the bank for periodic / on - line consolidation of MIS dataAbility to restrict access to reports based upon user privileges defined in the system

Critical

Ability to generate any adhoc report as required by the branches , departments, head office and management from time to time with least effort

Critical

Product - wise, scheme- wise, account - wise analysis detailing the performance of various accounts , products and schemes for a particular region / bank as a whole

Critical

Expense should typically cover interest expense, and fee & commission expense.

Critical

currency - wise, product / package - wise, branch - wise balances of all liabilities across the bank

Critical

customer / group profitability per product per customer / group per annum expressed in terms of net revenue earned through the customer

Critical

Report TypesCost of funds for each liability product and across all liability products

Critical

Net interest income analysis detailing the interest earned and paid

Critical

CBK regulatory reports Critical Return on assets Critical Return on equity Critical Earning on assets to total assets

Critical

Loans to deposits Critical Capital adequacy Critical Business / branch Critical

of 274


Gross profit / branch Critical Gross Non Performing Assets ratio

Critical

Basel Capital Accord CriticalAbility to accommodate multiple flagging codes at the customer account level in any sub ledger portfolio, to facilitate the various classification requirements of specific reports.

Critical

Ability to produce report of total deposits to and withdrawals from a given product portfolio over a given period (e.g. monthly).

Critical

Ability to extract relevant data from any sub ledger system and format according to requirements of specific statutory/MIS reports.

Critical

Ability to express balances of specific sub ledger asset and liability portfolios in given groups aged according to remaining maturity.

Critical

Ability to generate report of sub ledger liability accounts which are inactive for a given period formatted to show details of addresses, branch, opening date, currency, etc..

Critical

Ability to display customer balances in any sub ledger portfolio according to interest rate groups and in predefined economic sectors (by currency where required).

Critical

Ability to display all foreign currency assets and liabilities in a single designated foreign currency

Critical

Ability to calculate current period and historical trend must be available.

Critical

Ability to drill down from Group/Customer/Account level to detailed transaction level and to summarize from transaction to Group level.

Critical

Profitability should be based on actual comprehensive income and

Critical

of 274


expense including overheads. Source should be customer records/GL.Income should typically cover interest income, fee & commission income, exchange income, revaluation gain/loss, charges like statement charges, telex charges etc.,

Critical

All fee, commission, charges, interest waived must also be considered for assessing the profitability.

Critical

Option to calculate net interest income directly by applying a % margin on the loan balance or by applying pool rates i.e. cost of funding.

Critical

Ability to share income/expense between multiple business units based on user definable distribution matrix.

Critical

System should restate history for effects of back valuation and adjustments to balances, averages, income and expense.

Critical

Provide balance sheet daily average balances report / per business unit along P /L separately for each business unit.

Critical

Auto generation of specified reports on specific / predetermined dates

Critical

Generation of reports per RO/RM - productivity.

Critical

The solution should allow for 3rd party reporting tools to pull data from the solution to satisfy unanticipated reporting requirements

Critical

Where applicable, the end-user solution shall support either Google Chrome or Internet Explorer 11+ for the browser-based components of their solution.

Critical

of 274


1.3.2.3 Training RequirementsRequirements.



Comments

All training aids and manuals shall be provided in electronic format. Training may be provided as video recordings. CriticalApplication training for end Users, and additional training for Administrative Users. Provide one chapter of the training materials as an example. CriticalSystem training for ICT staff CriticalMaintenance and troubleshooting training for Application Support staff, for hardware interfaces and software. CriticalEnable the bank to configure a Training environment emulating the bank's production configuration, with simulated transactions. CriticalOn-site or online training as requested for functional topics, Refresher sessions, Updates and New Functions Critical

1.3.2.4 System Support RequirementsRequirements.



Comments

General application support to be available by online communication or telephone, during business hours.

Critical

Verify all hardware interfaces operate Critical

of 274


correctly with the new system.Updates to the application, manuals and help system must be supplied as they are released.

Critical

Updates must not break existing custom functionality.

Critical

High availability configuration with redundant servers to be commissioned and tested.

Critical

Coordinate with IT Support team to document hardware setup

Critical

Enable tests to be run with simulated transactions from a stored script in the Testing configuration.

Critical

Proponent must report regression testing results for fixes and new features. In particular, document issues with customizations.

Critical

Enable system monitoring and event logging for troubleshooting problems.

Critical

1.3.2.5 Documentation RequirementsRequirements.



Comments

All documents should be provided in electronic format, and hard copy format where available

Critical

of 274


The vendor shall provide all documents relating to project deliverables:- Project Implementation Plan and Schedule (PIPS) - Solution Design Document (SDD)- Solution Testing Plan (STP)- Solution Acceptance Criteria- Solution Administration Guide- Integration and API Procedures- User Training Documents- Solution Issues and Defect Report- Solution Test Results Report- Delivery Confirmation CriticalThe vendor shall include all documentation for their proposed solution including:a. End-user manualb. Installation of solution on servers and clientsc. Trouble-shooting common hardware problemsd. Administrative Guide: Installation, operation and maintenance of server solution including databasee. Configuration of the Solutionf. Integration methods - e.g. API, web servicesg. High Availability configuration and operation; failover testsh. Disaster Recovery Proceduresi. Data flow diagrams with security and encryption descriptions Critical

1.3.3 Loan OriginationRetail/ SME/ Micro-lending/ Corporate Loan Origination

Ref# Feature1 Search Requirement Fully

of 274


Criticality (Critical/Nice to Have)

Supported / Partially Supported / Not Supported / To be customized

1.1 Application search

Search based on the following fields1. Application Id or Passport Number or any other national ID2. First Name, Middle name, Last name or name in native language3. Person who recorded the application4. Application status 5. Account number or /and Client code for existing customers 6. Previously Declined/Deffered applications

Critical

2 Application Creation

2.01 Support for multiple types of loans and overdrafts

1. Supports loan applications for fresh loans /limits (i.e. Overdraft ,Guarantee , LPO line, Credit Line) as well as renewal of facilities, restructures, loan modifications (term extension, limit extension, rescheduling, change in interest rates)

Critical

2.02 Customer Search

1. Search associated with the CIF id field in the data entry screen. The Search URL is configurable to open the search page of any CRM system.2. Allows the user to search against the customer database maintained in the system during data entry3. If no matches are found, then the system facilitates and mandates creation of a CIF, at the time of application entry.

Critical

2.03 CIF Generation

Ability for the system to comprehensively capture customer details

Critical

2.04 Expandable / Collapsible Data Entry Screen

System to allow user navigation on various screens without exiting any

Critical

of 274


2.05 Multiple applicants to application

1. Supports multiple applicants, each with varying capacities and roles. 2. There should be a minimum of one applicant in the role of a borrower. 3. Applicant types can be defined in the system as per the business needs.4 Captures various details across personal, employment and address details.

Critical

2.06 Process identification based on product attributes

1. The Origination system facilitates defining different process flows for each super product, product and credit scheme. For instance, the process flow defined for Consumer goods and Mortgage can be different2. Process flow to product attribute mapping is configurable in the system.

Critical

2.07 Applicant details capture

1. Captures the personal , address and employment details for every applicant.2. Captures the family members' name and national id, and their relation to the applicant.3. Address Types - Office, Residence, Mailing (Address types are configurable)4. Feature to record details (name, address and national id) of 2 references. 5. Related/ Associated companies.

Critical

2.08 Pricing 1. Capture Interest rate, commissions, fees etc. . Able to support risk based pricing. Base rate plus a margin. As well as Variable/Fixed rates, Flat rate/Reducing balance interest rate

Critical

2.09 Asset details capture

1. Captures the asset type, location, and description of the Asset, OMV, and FSV, LTV and the valuation currency and the o/s loan commitment against each asset. The name of valuer and valuation date.

Critical

2.10 Liability Records Liability Type, Critical

of 274


details Originating FI, Liability amount, estimated monthly commitment, adjusted monthly/quarterly/ semi-annually/ annual/ balloon commitment.

2.11 Income Details

Records income source and currency, income frequency and the amount

Critical

2.12 Expense Details

Captures Expense type, amount and the applicable currency

Critical

2.13 Collateral capture

1. Captures the details of the primary collateral that would be linked to the loan account.2. Integrated with the Collateral module for creation/selection of an asset as a collateral

Critical

2.14 Support for Multiple collaterals types

1. Supports capture of multiple collateral types for the same application2. Supports in capturing detailed collateral related information like collateral type, location, description of the asset, OMV,FSV,LTV and charge status and the valuation currency and the o/s loan commitment against each asset. 3. Supports collaterals to be defined as sharable and non-sharable collaterals4. Supports restriction of collateral to a single credit line5. Supports collateralization of assets while collateral creation6. Capture of collateral specific information6. The following asset types can be collateralized (Can be configured) 1. Fixed Deposit 2. Guarantee 3. Pledge / hypothecation 4. Mortgage 5. Lien on stock and bad debts 6. Security Cheques 7. Vehicle

Critical

2.15 Single collateral supporting

Collateral ids can be linked to multiple applications subject to the sum total of percent of

Critical

of 274


multiple applications/ Linking of collateral to more than one account/guarantor

utilization of the underlying asset(s) not exceeding 100%

2.16 Application edit prior to contracting

Allow modifications to applications before the contract is finalized.

Critical

3 DeDuplication

3.01 Internal Dedupe function

1. Dedupe is done for all the parties to the application.2. Search strings are derived from the applicant data, after applying a series of formula/computations on the same3. More than one applicant data can be merged together to build a search string.4. Deduplication is an auto stage process.5. User interaction is at the review stage. While reviewing the matched records, the user can opt to accept a match, on which the CIF id of the selected match would replace the existing CIF id, if any, in the application data.6. Acceptance of a match, even for one party, is not mandatory for the application to be processed further.

Critical

4 Credit Approval

4.01 Objective Credit Policy Checks

1. System driven.2. Credit Policy rules can be configured using the Rules Engine module.3. Policy evaluation is automatically done by the system.4. Policy check can be executed at different stages depending the user requirement. 5. Different Policies for different products can be exercised.

Critical

4.02 History of credit policy

The Origination system maintains a history of all changes in the

Nice to Have

of 274


changes policy evaluation results, as a result of iterations and various modifications to the applications

4.03 LTV & PTI Calculation

1. Loan To Value (LTV) and Payment To Income (PTI) computations are done as a part of the Credit Score transaction. 2. Computation logic is configurable through the Rules Engine module.

Critical

4.04 Credit Scoring

1. System driven.2. Credit Scoring rules can be configured using the Rules Engine module.3. Score computation is automatically done by the system.4. Credit scoring can be done at different stages of an application for a product and different products can have different scoring sheets at the will of the user 5. Scoring module can be configured per product.

Critical

4.05 System recommended loan amounts

System recommended loan amount is computed as a part of the credit score transaction.

Critical

4.06 Existing Asset & Liability view

1. Details of all assets and liabilities that have been recorded during the data entry stage, is available as a link in the decision screens.

Critical

4.07 Neglist Results

1. Decisioning and Underwriting modules have a link to view neglist matches for all the applicants.

Critical

4.08 Credit Bureau Results

Ability of the system to interface with Credit Reference Bureau systems

Critical

4.09 Loan Terms and conditions review

1. The edit offer link in the credit decisioning stage provides the facility to edit or modify the terms and conditions for the loan to be approved.2. This feature of the Origination system provides a concise view of the loan amount requested, loan tenure, rate of interest, repayment frequency and mode of repayment.

Critical

of 274


4.10 Repayment schedule generation

1. Repayment schedule is supported during decisioning and underwriting stages.2. Supports generation various repayment schedules like equated, varying dates and amounts, Balloon payments etc.

Critical

4.11 Edit Data Entry

1. The Origination system supports the credit team’s decision to send back an application for correction of terms or addition/deletion of applicants.

2. The credit team can also edit the application details and proceed with decisioning.

Critical

4.12 Refresh of Scoring, Policy, LTV & PTI calculation

1. The user can manually initiate re-computation of scoring and policy evaluation, from the decisioning stages, using the 'Redo Score and Policy evaluation, as and when data is changed by using Edit data

Critical

4.13 Document collection

1. Can be updated at any stage of application processing.2. Checklist can be different for each applicant type.3. System mandates collection of mandatory documents to proceed with contracting.

Critical

5 Verification5.01 Rule based

Verification Grid Marking

Verification and grid marking rules configured in Rules Engine

Critical

5.02 Grid marking at application level

The user can override and waive verifications that have been marked for an application, through the grid marking process

Critical

5.03 Agency Allocation

1. Rules for agency allocation can be configured using the Rules Engine module.2. The user can select one of the shortlisted agencies and assign the verification for that application, to that agency.

Nice to Have

5.04 Sourcing details capture

1. Records the dealer who has sourced the application, the loan purpose and the sourcing channel.2. Loan purpose and Sourcing

Critical

of 274


channel can be defined based on business needs, at the time of implementation

6 Underwriting

6.01 System Recommendation

1. Origination computes the recommended loan amount for every application, based on the rules configured in Rules Engine.

Critical

6.02 User override 1. Override of the system recommended limit can be done by the credit approver.

Critical

6.03 Multiple levels of approvals both individual and group(committee)

1. System currently supports any number of level of underwriting (Users receive email alerts)2. Deviation entry level for underwriting is configured in the Rules Engine3. Approval from the entry level moves the application to Contracting stage.4. System also supports a recommend feature to escalate the application to the next level of underwriting. 5. The system should allow exceptional approval

Critical

6.04 Approve, Decline, Cancel, reinitiate credit approval.

1. The user can either approver or cancel or reject or push back an application to the credit approval stage.2. The reasons for the decisions of the approval from underwriter can be recorded 3. The system provides a maintainable list of decision linked reason codes, at each stage of decision making. The user can select one or more reason codes as applicable.

Critical

6.05 Approval history

All decision screens display the decision history and comments provided by the earlier decision makers.

Critical

6.06 Approval Authority Matrix

Business Rules Engine is used to configure the underwriting delegation matrix.

Critical

6.07 Application Referrals

1. System also supports a recommend feature to escalate the application to the next level of

Critical

of 274


underwriting.7 Reject

7.01 Reject Review Queue

1. Reject review queue displays the decision history.2. The user can select the mode of reject note communication.

Critical

7.02 Restart from Reject

1. Restart move the application to the credit approval stage.

Critical

8 Contracting and Disbursal

8.01 Approval for contracting

Contracting is the final stage of application processing in Origination. Approval at this stage hands off the details to the Lending system for disbursal.

Critical

8.02 Contract advices

Configured using the Custom module.

Critical

8.03 Disbursal handoff

All booking details are recorded at the contracting stage, through the booking module in the Lending system. This triggers a disbursal schedule for the application.

Critical

9 Master Maintenances

9.01 Document Master

1. Document codes are assigned to various documents.2. Each document can be classified as either as an income proof or address proof or as a ID proof.

Critical

9.02 Document Group

1. Different documents can be grouped together for a given combination of super product, product, customer type, applicant type and loan scheme.2. For each document added to a group, the collection mode(copy, original) and the collection frequency is defined.3. The system also allows to define mandatory and optional documents within the group scope.4. The system generated the document collection checklist based on this grouping.

Critical

of 274


9.03 General Parameter

A separate master is available to maintain the LOV for various field elements. These include applicant type, payment frequency, credit decisions,

Critical


1. System shortlists an agent by following a round-robin allocation logic. 2. The user can override the system allocation in the Pre-CPV stage

Nice to Have

9.05 Neglist maintenance

Masters provides an independent maintenance for Neglisted customers. The user can key in the details of neglisted customers using this module.

Nice to Have

10 Document Management & Imaging and Notepad

10.01

Document checklist generation

1. System generates separate document checklist for each applicant type.2. Document checklist generation is based the document group maintenance done for a given product and applicant type.

Critical

10.02

Document Receipt

The user marks a document as collected, there by acknowledging receipt of a document.

Critical

10.03

Document Waiver

Optional documents can be waived. Mandatory documents cannot be waived.

Critical

10.04

Document Deferral

1. When the user defers a document, the system mandates the deferred date to be entered.2. Collection of a document can be deffered to a date marked as deferred date.

Critical

10.05

Additional document

1. Documents that are not a part of the checklist but have still been collected, can be recorded under the additional documents section.2. The user can add any number of additional documents.

Critical

10.06

Mandatory & Optional classification for documents

Mandatory and optional classification is defined at the time of document grouping. The same is reflected in the collection checklist generated for every

Critical

of 274


application.10.0

7Upload of document images

There is a separate link for document upload. This is available from the document collection checklist and also independently, as a link in the page header at every stage.

Critical

10.08

Document image view

View image link is found in the document collection checklist and also as a link in the page header at every stage.

Critical

11 Customer Advice Generation

11.01

Advice Templates

1. Through the Customer Communication module, the system supports configuration of customer advices.2. These templates can be configured to embed application data (customer information, loan offer terms and the like)2. Customer advices can be viewed from the decision making stages.

Critical

11.02

Advice communication

The System supports the following communication modes1. E-Mail2. FAX3. SMS

Critical

12 MIS Reports12.0

1MIS Reports 1. MIS Reports can be configured

to suit the business needs, using the Reports tool.2. The report output can be in any one of the following formats a) CSV b) HTML c) PDF d) Excel e)Word

Critical

12.02

Data Handoffs

1. Reports can be used to configure data hand off files2. The handoff would be in an Excel/ PDF format.

Critical

13 Process Configuration

of 274


13.01

Business Process Setup

1. Workflow is used to configure the business process.2. The process studio is a graphics based canvas where the user can configure various stages of a business and sequence the same.

Critical

13.02

Parallel Processing

Workflow supports parallel processing wherein an application can be processed across more than one stage of activity

Critical

13.03

Access Control

Stage level access restrictions can be configured.

Critical

13.04

Version control

All versions of a process are available for viewing, at any given point of time.

Critical

13.05

Maker Checker facility

Any modification done in the Workflow, come into effect only after the same has been authorized. The maker and authorizer cannot be the same.

Critical

14 Utilities14.0

1Notes - Add Additional comments and

observation, can be recorded at every stage, by each user, using the Notepad - Add link.

Critical

14.02

View Notes 1. Comments and observations recorded by each user at each stage of application processing is tagged with the application id.2. Such recordings can be viewed by all users at all stages using the Notepad view link.

Critical

14.03

TAT Summary This is available as a link at all stages of application processing. The elapsed time at each stage is displayed. The summary includes stages where system has processed the application without any manual intervention.

Critical

15 Business Rules

1. Does the system have a inbuilt business rules engine to configure business rules.

Critical

2. Are the business rules configurable by bank users themselves without vendor intervention

Critical

of 274


3. How easy is to amend the rules in your system

Critical

4. Does the business rules system support versioning for easier rollback

Critical

5. Does the system have a inbuilt rule testing option to simulate the rules as part of mock testing

Critical

6. Is there any limitation to number of rules that can be configured as part of the system.

Critical

7. Does the system have a means to replicate business rules for easier configuration

Critical

8. Does the system have a maker checker concept for authorization of rules.

Critical

16Integration with other platforms

Interface with Bank’s AML/Blacklist and Risk based pricing model and any other systems

Critical

1.3.4 Loan Management

S.No FeatureRequirement Criticality (Critical/ Nice to Have)


1.1 The system should allow real-time centralized maintenance of various types of rates for products, including but not limited to:

1.1.1 Interest rate Critical1.1.2 Fee rate Critical1.1.3 Tax rate Critical1.1.4 Commission / bonus Critical1.1.5 Penalty interest Critical

1.2 Describe the mechanism and tools to allow users to define the terms applied for rates of credit products.

Critical

1.3 Describe the mechanism and tools for setting up rate calculation formulas/sets using different base rates that were pre-defined in the Common Functionality to be applied to credit products.

Critical

1.4 Describe the mechanism and tools for assigning interest margin to the base interest rate to determine

Critical

of 274


the applicable rate for customers.1.5 The system should allow waiver of

rates for any account.Critical

1.6 Ability to support calculation of compound interest (interest on interest) for loans.

Nice to Have

1.7 The system should provide the capability to calculate and handle various rates.

Critical

1.7.1 Interest rate Critical1.7.2 Fee rate Critical1.7.3 Tax rate Critical1.7.4 Commission / bonus Critical1.7.5 Penalty interest rate Critical

1.8 Describe the method of calculating rates for different currencies.

Critical

1.9 The system should allow various time-based calculations of the rates defined by users, including but not limited to the following times:

Critical

1.9.1 Daily Critical1.9.2 Weekly Critical1.9.3 Monthly Critical1.9.4 Quarterly Critical1.9.5 Termly (School Term) Critical1.9.6 Six monthly Critical1.9.7 Yearly (including leap years) Critical

2 Detailed Interest Rate Requirements

2.1 Ability to define different interest rates in a flexible way.

Critical

2.2 The system should support multi interest rate types and provide interest calculation, including but not limited to:

Critical

2.2.1 Fixed interest rate Critical2.2.2 Floating interest rate (periodically

or ad hoc)Critical

2.2.3 Fixed interest rate but the frequency/term is changeable

Critical

2.2.4 Progressive interest rate Nice to Have2.2.5 Simple interest Critical2.2.6 Compound interest Nice to Have2.2.7 Flat rate Critical

2.3 The system should allow various time-based calculations of the

of 274


interest rates as defined by users, including but not limited to the following times:

2.3.1 Daily Critical2.3.2 Weekly Critical2.3.3 Monthly Critical2.3.4 Quarterly Critical2.3.5 Termly (School Term) Critical2.3.6 Six monthly Critical2.3.7 Yearly (including leap years) Critical

2.4 The system should have the ability to define, set up and compute the following items at least:

2.4.1 The interest rate is set up for the loan and will not be changed throughout the life of the loan

Critical

2.4.2 The interest rate is set up for different periods of time for the loan. For example: a loan’s interest rate for the 1st year is x%, for the next two years it is y%, and for the last two years it is z%

Critical

2.4.3 Step-up Critical2.4.4 Step-down Critical

2.5 The system should have the ability to calculate interest rates for the instalment amounts on the following bases:

2.5.1 Daily Critical2.5.2 Weekly Critical2.5.3 Monthly Critical2.5.4 Termly (School Term) Critical2.5.5 Quarterly Critical2.5.6 Yearly Critical2.5.7 Bullet / balloon payment Critical

2.6 The system allows definition of base interest rate, ceiling and floor interest rate margin, interest rate for branches and head office by one or group of following criteria including but not limited to: - by % of base interest rate - by product- by customer group- by geographic areaThe Tenderer is to describe in detail in the proposed solution. The system allows definition of

Critical

of 274


base interest rate, ceiling and floor interest rate margin, interest rate for branches and head office by one or group of following criteria including but not limited to:- by % of base interest rate - by product- by customer group- by geographic area

2.7 Ability to simultaneously apply a variety of floating rate margins and define a variety of margins on one interest rate.

Critical

2.8 System allows definition of penalty interest rate, ceiling and floor penalty interest rate, penalty rates used by branches and head office by one or a group of the following criteria including but not limited to:

- by % of base interest rate- by product- by customer group

The Tenderer is to describe in detail the proposed solution. System allows definition of penalty interest rate, ceiling and floor penalty interest rate, penalty rates used by branches and head office by one or a group of the following criteria including but not limited to:

- by % of base interest rate- by product- by customer group- by geographic area

Critical

2.9 The system supports advance closure of loans with fixed interest rates.

Critical

2.10. Ability to automatically collect interest according to a defined schedule or at the time of doing the transaction.

Critical

2.11 The system supports calculating and re-posting if the product cycle is adjusted.

Critical

of 274


2.12 The system allows flexibly to adjust interest rate cycles.

Critical

3 Detailed Fee and Charge Requirements

3.1 Ability to allow users to define fees associated with loans

Critical

3.2 Ability to define and flexibly calculate fees and charges including but not limited to : flat, by proportion, by maturity, by min/max fee etc.

Critical

3.3 Ability to calculate and collect the service fee automatically at a predefined frequency e.g. daily, weekly, monthly, quarterly, bi yearly, yearly, etc. or to allow ad hoc collection at the time of transaction.

Critical

3.4 Ability to define, and auto calculate the fees related to any changes, amendment in the loan schedule (change of loan time, amount, and method) including but not limited to: commitment fee, pre-maturity repayment, early contract closing, co-sponsorship fee. The Tenderer is to describe this in detail.

Critical

3.5 Support the calculation of additional interest due to the difference between the rate at the time of disbursement and the rate at the time of principal and interest payment.

Critical

3.6 function to calculate and support partial payments

Critical

4CREDIT LIMIT MANAGEMENTCredit Limit Management for loan, guarantee, LC, overdraft, discount, factoring, corporate bond, credit card etc.

4.1 Describe in detail how to manage multi-dimensional limits according to the following criteria: products, customer, customer group, industry, collateral, economic region and internal customer.

Critical

of 274


4.2 Manage multiple dimensions by product, customer, customer, industry code, collateral, economic area, internal customer, bank structure (whole bank, area, branch).

Critical

4.3 System has the ability to set multiple-currency limits.

Critical

4.4 System should be able to manage credit limit by collateral, classification of limit by whole collateral, partly collateral or no collateral.The Tenderer is to describe in detail this function in the proposed solution.

Critical

4.5 Ability to automatically check credit limit against collateral linked to the loans (wholly or partly) as defined by the bank for customer, product, contract.

Critical

4.6 Ability to set up and manage multi-tier limits (main limit, limit by product, sub-limit, sub-sub-limit etc.).

Critical

4.7 Ability to automatically manage real-time reduction of the main limit by outstanding balance.

Critical

4.8 Ability to manage the limit by revolving or non-revolving methods or combining of both

Critical

4.9 Ability to adjust limit upwards and downwards during the validity period of credit limit.

Critical

4.10 System allows users to establish temporary limits with specific beginning and closing dates.

Critical

4.11 System has the ability to renew limits with back value dates.

Critical

4.12 System supports managing shared limits and non-shared limits. In shared limits, total sub-limits can be more than or equal to the main limit. In non-shared limits, the cumulative total of sub-limits must be less than or equal to the main limit.

Critical

4.13 Ability to manage limit by customer group, which is the total

Critical

of 274


limit that could be shared/non-shared among customers/subsidiaries in the group; ability to manage limits of main unit and limits of subsidiary units.

4.14 Ability to roll-up the limits to the parent limit.

Critical

4.15 Ability to post off-balance sheet for undisbursed amounts.

Critical

4.16 Ability to generate reports on expired limits; valid limits by customer, customer group.

Critical

4.17 Ability to transfer the credit limit from one contract to another.

Critical

4.18 Ability to suspend a limit where the Credit team deems so

Critical

5 REPAYMENT SCHEDULE/FREQUENCY SETUP Setup a GL Account Distribution Set

5.1 GL account distribution sets - Ability to allow the definition and automatic generation of accounting entries to the GL

Critical

5.2 In the case customers do not have enough balance in the account for payment, the system supports calculating and automatically collecting the payment a day later or any customized time or when the customers' accounts have sufficient balance for payment.

Critical

5.3 The system should allow for flagging of incoming payment for certain types of loans

Critical

5.4 Automatically send messages to remind customers of payment one week before the payment deadline.

Critical

6 PRODUCT SETUP/DEVELOPMENTLoan Products Setup/Definition

6.1 Provide the mechanism and tools to create diversified credit products with maximum level of automation and posting as required by the Bank including but

Critical

of 274


not limited to the following.6.1.1 Record automatically to GL system Critical6.1.3 Products designed by area, region,

branchCritical

6.1.4 Product attribute is inherited from product level to account level

Critical

6.2 The system should define the following criteria including but not limited to:

Critical

6.2.1 Product name Critical6.2.2 Product type Critical6.2.3 Product code Critical6.2.4 Loan term Critical6.2.5 Principal amount Critical6.2.6 Currency Critical6.2.7 Interest rates applicable (e.g.

normal interest, delinquent interest, fixed and floating rate for different periods)

Critical

6.2.8 Capitalized interest Critical6.2.9 Loan classification rules e.g. for

delinquency recognitionCritical

6.2.10 Staff loan Critical6.2.11 Product creator / owner Critical6.2.12 Transaction type Critical6.2.13 Product validity / expiry Critical6.2.14 Product criteria Critical6.2.15 Repayment mode Critical6.2.16 Interest calculation mode Critical6.2.17 Payment priority Critical6.2.18 Product limit Critical6.2.19 Loan purpose Critical6.2.20 Information of borrower Critical6.2.21 Support the input of one or

multiple collateral (of different currencies) to calculate the limits

Critical

6.2.22 Fee and charges type Critical6.3 System has the ability to create a

new product by selecting available characteristics and criteria from the existing products.

Critical

6.4 Ability to upload files related to contracts and agreements (for example: appraisal records).

Nice to Have

6.5 Describe the method of defining/setting up and flexibly monitoring different loan products

Critical

of 274


including but not limited to:6.5.1 Secured / collateralized loans Critical6.5.2 Unsecured loans Critical6.5.3 Revolving loans Critical6.5.4 Non-revolving loans Critical6.5.5 Syndicated loans Critical

6.6 Ability to input a pre-determined account for the automatic collection of due interest and principal.

Critical

6.7 Ability to distribute, monitor and post the amount of accrued interest receivable from customer into different GL accounts.

Critical

7 SPECIFIC REQUIREMENTS OF SOME LOAN PRODUCTSSyndicated Loan

7.1System has ability to manage and handle Syndicated Loan.

Critical

7.2 System has ability to manage limits of syndicated loans using different currencies.

Critical

7.3 Ability to manage customer credit limits for syndicated loans in which the bank is the focal point

Critical

7.4 Ability to manage and track all syndicated loan processes (tracking the money received from member banks, disbursing to customers, calculating distributed interest and fees, debt collection, risk handling, loan settlement…)

Critical

7.5 Ability to collect repayments from customers and distribute them to member banks.

Critical

7.6 Automatically generate notifications for repayments and send them to different participants through various channels such as email or fax etc…

Critical

7.7 Ability to support maintenance of overdue syndicated loans.

Critical

7.8 Ability to track member banks’ information (name, contributed amount, etc.)

Critical

of 274


8 OPERATIONS FOR CREDIT FUNCTIONSCreate and Manage Loans

8.1 Describe in detail the management mechanism for loan applications, loan contracts and accounts. Ability to create a unique loan account for each approved loan application (if any).

Critical

8.2 Ability to fast open account and fulfil account information in order to improve customer service speed.

Critical

8.3 Ability to provide the function to increase/ decrease the value of credit contracts.

Critical

8.4 Ability to allow credit position to be managed separately for each loan.

Critical

8.5 Ability to store all customers' loan files

Critical

Disbursement9.1 Allow report on the conditions that

the documents must comply with before disbursement (according to the Bank's regulations for each loan purpose/product) to identify which documents customers need to provide after disbursement (Disbursement Checklist)

Critical

9.1.2 Allows for creation a loan creation detail sheet prior to disbursement

Critical

9.2 System supports multiple methods of disbursement and users can define such methods, some example includes:

Critical

9.2.1 Single disbursement Critical9.2.2 Multiple disbursement Critical9.2.3 Disbursement in batch Critical9.2.4 Full disbursement Critical9.2.5 Disbursement following defined

scheduleCritical

9.2.6 Revolving Critical9.3 Ability to generate, re-generate

and manage disbursement schedule by amount and disbursement date.

Critical

9.4 Ability to support post-dated Nice to Have

of 274


disbursements.9.5 Ability to issue customer advices

letters upon configurationCritical

9.6 Ability to issue an annual e-loan statement to borrower

Critical

10 Loan Management10.1 Describe the mechanism for

processing and managing problems arising with loans. These problems must be controlled by at least two levels of authority, and it should be based on the processing authority by amount, times, due date... Problems may include but not be limited to:

Critical

10.1.1 Changes in interest (parameters, portion on current date, future date and back date for different methods of interest calculation)

Critical

10.1.2 Change in fee on the current date, future date and back dated for different loans and their fee calculation methods

Critical

10.1.3 Restructuring (change in loan amount, limit, term (date, repayment amount for each period, repayment date - support changing debt classification or not), loan renewal etc.

Critical

10.2 Ability to automatically define penalty interest amount on past-due repayments and inform customers of this.

Critical

10.3 Ability to waive, reduce interest (must be approved by authorized person).

Critical

10.4 Ability to define and manage the extension time of due date.

Critical

10.5 Ability to automatically collect penalty interest and the waive of penalty interest needs higher level approval

Critical

10.6 Ability to add additional conditions over and above the standard conditions during the approval period.

Critical

10.7 Ability to automatically define next Critical

of 274


date for repayment on the basis of loan payment schedule whereby the system will send it to the customers through pre-defined channels.

10.8 Ability to automatically send alerts periodically to customers on consequent treatment to be applied if they failed to repay due amounts timely.

Critical

10.8.1 Ability to alert the customer upon full redemption of the facility

Nice to Have

10.9 Ability to automatically define dates to review contract and date to adjust interest rates.

Critical

10.10. Ability to delay repayment until a specified time.

Critical

10.11 Allow for flagging of restructured loans

Critical

11 NPL (Non-Performing Loan) Account

11.1 Ability to support the generic requirements of past-due loan management

Critical

11.2 The system allows credit officers to downgrade or upgrade loan bucket manually

Critical

11.3 Ability to support the collections cycle (notifications, alerts, etc.) via SMS, e-mail (optional) for customers and credit officers.

Critical

11.4 Ability to automatically produce the notifications based on product-level parameters to both borrower and also to other parties such as guarantee entity, etc.

Critical

11.5 Allow for write off of NPLs and Write-down - transfer of loan facilities to off-balance sheet as recovery efforts are ongoing

Critical

12 Calculate and Make Loan Provision

12.1 Ability to calculate make general and specific provision

Critical

12.2 Ability to suspend interest upon downgrade of facility and release once corresponding loan principal is paid

Critical

12.3 Ability to automatically zero rate Critical

of 274


loan/overdraft account once indupulum limit has been reached

12.4 Ability to group related accounts according to prudential guidelines through the identifiers laid out by the bank

Critical

13 Loan Repayment/Pay Off13.1 Ability to define various repayment

types (interest only, principal only, bullet, balloon, step-up/down, auto allocation etc.)

Critical

13.2 Ability to support repayment during holiday period (collect later). In the case of collection of penalty interest, holiday is not counted.

Critical

13.3 Ability to waive interest for predefined period during marketing campaign (this is subject to the Bank’s approval, and the interest for a specified period can be waived, which eventually becomes a repayment waiver).

Critical

13.4 Ability to support fixed amount repayments, whereby any changes in interest rate have to be adjusted either by an increase in term or amount as per the customer's decision.

Critical

13.5 Allow the Bank to offer special treatment to customers for repayment to be applied at account opening or in the case after repayments have begun the borrower will be allowed flexibility to be waived an installment of repayment amount

Critical

13.6 Ability to automatically allocate the proceeds from repayment. On receipt of the proceeds, the system will allocate them to different repayment schedule as requested by customers.

Critical

13.7 Allow defining parameters in allocating the loan payments (monitor the sequence of allocation e.g. penalty interest, interest, principal, charges, fees etc. as required by the bank, including but not limited to:

Critical

of 274


13.7.1 Set by product type Critical13.7.2 Set by loan grading bucket Critical

13.8 Ability to record and manage on-maturity repayments, overdue repayments, pre-maturity repayments.

Critical

13.9 Ability to automatically send an alert to a customer (SMS, email) regarding changes to his/her loan against the pre-agreed conditions in the contract.

Critical

13.10. Ability to support loan repayment including but not limited to:

13.10.1

Premature repayment of a portion of the loan. The system should create a new repayment schedule to correspond with the new outstanding balance (reduced as a result of the premature repayment)

Critical

13.10.2

Premature repayment of a portion of the loan without affecting the loan payment schedule (payable amount will be deducted from the repayment on the next maturity date)

Critical

13.10.3

Flexible adjustment credit terms in contract when a customer makes premature repayment

Critical

13.11 Ability to support batch collections Critical13.12 Ability to make early notification of

a past-due loan. The Tenderer is to describe the mechanism in the proposed solution.

Critical

13.13 Ability to support establishment of different types of premature repayment, including but not limited to:

Critical

13.13.1 Principal Critical

13.13.2

Payable interest accrued as from the last repayment date

Critical

13.13.3 Charge on premature repayment Critical

13.14 Ability to calculate amounts repayable by customers, including principal, accrued interest receivable/past due interest.

Critical

13.15 Ability to automatically calculate Critical

of 274


maturity date of the contract using criteria defined based on users.

13.16 System should allow the bank to set up various loan repayment schedules including at least the following:

Critical

13.16.1 Amortization Critical

13.16.2 By specific schedule Critical

13.16.3

Capitalization (interest added to the principal)

Critical

13.16.4 Only principal Critical

13.16.5 One-off (balloon) Critical

13.16.6

Others (please describe if available)

Critical

13.16.7 Instalment payments Critical

13.16.8

Instalment payments over some first terms and a balloon payment at maturity

Critical

13.17 Allow product rules to be applied to determine the repayment schedules.

Critical

13.18 Allow for automated loan closure of loan account on full repayment

Critical

14 Diaries/Trackers.14.1 Allow monitoring of post-approval

covenants by way of alerts to various relationship managers

Critical

15 Report Creation/Reporting/Portfolio Monitoring

15.1 Allow for creation of pre-set reports to enable speedy creation of periodic reports

Critical

15.2 Allow for report building as per the user preference

Critical

15.3 Avail a business intelligence tool Critical15.4 Allow for creation of dashboards

for management reportingCritical

15.5 Allow for interfacing with external databases e.g. CRB to allow for uploading of data.

Critical

15.6 Allow for automation of reports Critical

of 274


generation and upload into relevant external databases

15.7 Base currency limits for clients with non-fund based credit lines to accommodate processing of multiple currency transactions under the same limit.

Critical

15.8 Availability of marking and processing limits for non-fund based transactions on corporate, SMEs, MSMEs and individual clients.

Critical

16 Collateral Management

16.1 The system supports controlling when the value of collateral decreases and is not sufficient to back up the loan:- Outstanding loan is considered secured when: + The value of the outstanding loan is smaller than the product of collateral value and the proportion of the asset used as collateral (scenario 1)+ The value of outstanding balance is smaller than portion of the asset used as collateral (scenario 2)- The application of scenario 1 or 2 depends on the type of collateral. The system supports controlling when the value of collateral decreases and is not sufficient to back up the loan:- Outstanding loan is considered secured when: + The value of the outstanding loan is smaller than the product of collateral value and the proportion of the asset used as collateral (scenario 1)

Critical

16.2 The system should allow the collateral to fully or partially secure the total credit limit and identify whether the asset is used as collateral for a credit contract or for the customer's whole liabilities.

Critical

16.3 The system supports releasing Critical

of 274


collateral in the case the asset is used as collateral for more than one customer/at different branches. Describe the mechanism to alert and confirm the agreement to release the collateral.

16.4 Allow one collateral to be shared for one or multiple loans; for customer credit limit of one or multiple customers at one or multiple branches. When a collateral is withdrawn, all the outstanding balances linked to the collateral must be zero or another asset whose value is enough to secure the current outstanding balance of customer is used as collateral according to the percentage defined by the Bank.Upon approval the system should be able to originate an addendum to the existing contract

Critical

16.5 Ability to store information about insurance contracts for insurance life and disability of the borrower

Critical

16.6 Ability to automatically post collateral value if any changes occur.

Critical

16.7 Ability to generate alerts if the collateral has been used as collateral at another branch of the Bank

Critical

16.8 Ability to generate alerts if the value of the loan exceeds the value of the collateral.

Critical

16.9 The system allows inputting the actual value of the outstanding balance and the value of collateral to calculate the loan proportion based on the value of the collateral.

Critical

16.10' The system allows filtering outstanding balances according to product types and collateral.

Critical

16.11 The system allows an asset to be used entirely or partially as collateral.

Critical

16.12 The system has a flexible Critical

of 274


mechanism (automatically/manually) to block collateral.

16.13 Allow for a depository of images of security documents and capturing of collateral details that is scalable

Critical

16.14 Allow for scanning and storing of collateral images in the repository and deletion upon approval

Critical

16.15 System should allow for partial release of collateral where more than one collateral is held or in cases where the collateral can be subdivided by the bank

Critical

16.16 The system supports the evaluation of collateral: information about collateral price history over time and the mechanism to update the prices of securities assets which are listed in the securities exchange market.

Critical

16.17 Ability to connect collateral to credit limit of customer, customer group, product and contract.

Critical

16.18 Ability to change collateral linked to customer credit limit and credit account throughout a loan's lifecycle.

Critical

16.19 Ability to manage collateral on the detailed characteristics of each type of collateral, of collateral group and classify for easy management.

Critical

16.20 Ability to manage collateral by its source of formation.

Nice to Have

16.21 Ability to manage collateral by its relationship with customer.

Nice to Have

16.22 Ability to automatically block collateral in the form of current account, or saving accounts.

Critical

16.23 Ability to block collateral at different levels (full blocking, partial blocking) on different collateral (current account, stock blocking, etc.).

Critical

of 274


16.24 Provide a mechanism for re-assessing collateral. The Tenderer is to describe this mechanism in detail.

Critical

16.25 Ability to produce reports or give alerts to users before maturity date or review date of collateral.

Critical

16.26 Allow one collateral to be shared for one or multiple loans; for customer credit limit of one or multiple customers at one or multiple branches. When a collateral is withdrawn, all the outstanding balances linked to the collateral must be zero or another asset whose value is enough to secure the current outstanding balance of customer is used as collateral according to the percentage defined by the Bank.

Critical

16.27 Ability to manage information about collateral owner, joint ownership including cases where collateral owner is the loan customer, owner is a third party, credit institution/guarantee issuing institution.

Critical

16.28 The system allows the Bank to define collateral types and information fields including the legal eligibility of the collateral.

Critical

16.29 The system allows filtering outstanding balances according to product types and collateral.

Critical

16.30 Ability to generate alerts if the interest rate on a deposit used as collateral is higher than the interest rate on the loan.

Critical

16.31 The system can generate alerts and update collateral, display the collateral history, fields for preliminary evaluation of collateral status.

Critical

16.32 Alert of collaterals that are required to have insurances and state the effective period of the insurance. Alerts to be sent to bank officers and the borrower

Critical

of 274


16.33 Ability to batch input with respect to collateral information.

Critical

16.34 Ability to update the value of a collateral if the value of a loan changes; ability to select and delete collateral.

Critical

16.35 Ability to define the reason for moving collateral out of the vault. Allow for an end to end process for request of release to return

Critical

16.36 Store of Information on collateral after it has been processed (prices, date of sale).

Critical

16.37 Ability to aid a library system for management of the vault

Critical

16.38 Ability to interface with external databases e.g. tracking companies for purposes of monitoring bank collateral

Nice to Have

16.39 Ability to manage external service providers e.g. Lawyers, Values, Tracking companies in terms of issuing instructions, indemnity cover limits and SLA

Critical

16.40 Ability to avail the security details to a customer 360 degree view to permitted users

Critical

16.41 System to allow for alerts on expiry of leases and Rent and Rates

Critical

16.42 Allow for interfacing with the capital market to enable immediate revaluation of money equivalent securities e.g. T-bills, Stocks, bonds etc.

Nice to Have

16.43 Allow for alerts for physical check of securities after a two year period

Nice to Have

16.44 Ability to alert the customer upon full redemption of the facility to collect the collateral

Nice to Have

16.45 Enable of collection of fees and commission for purposes of maintaining the collateral integrity.

Critical

of 274


16.46 Ability to transfer a security from Collateral status to Safe custody status and vise versa and allow for collection of commissions

Critical

17.0 Others17.1 Report on loans due in the next 7

days and ability to send alerts to the customers

Critical

17.2 Customers to be sent alerts on over dues and also prompt for loan repayment like 7 days to due date.

Critical

17.3 Ability to automate collateral, Valuations, Insurances etc.

Critical

17.4 Loans disbursed report to have different parameters e.g. product type, restructures, Moratorium, user ,RM etc.

Critical

17.5 Negotiation fees to be automated Critical17.6 Details of all bank assets captured

as security by the bank, their insurers, intermediaries, policy start date and expiry date

Critical

17.7 Ability to spool reports for existing insurance covers. The report should indicate the insurers where the covers were placed, the agencies through which the covers were placed, the policy start and end date

Critical

17.8 Link the CBS system to Insurancepro system where payments are made in the CBS and reflect in Insurancepro system

1 Mark

1.3.5 Debt ManagementRequirements Requiremen

t Criticality (Critical/Nice to Have)


Vendor comments

#

Modules / Features / Functionalities

Host Data Extraction1 Batch upload of files from Credit

Card, Finance System, Core Critical

of 274


banking System, digital platform and Customer Relation Management SystemData Mapping

2 Multiple product support Critical3 Flexibility in mapping data

received from Host System with the Collection System tables

Critical

4 Mapping data in the Collection System tables to various screens at different levels such as Customer level and Contract level

Critical

User Maintenance5 User Hierarchy definition -

Multiple level supportCritical

6 User information capture - Demographic information of each User with information such as Maximum Load and entitlements for downloading information

Critical

7 Agency user mapping - Mapping Collectors and the Agency they work for

Critical

Management of Portfolio8 Relationship view of customer Critical9 In a disparate eco System,

capability of the System to generate a common folio number for the purpose of Collection tracking

Critical

10 Single View of customer CriticalBucket StampingFinance

11 Bucket information from finance System

Critical

12 Stamping as per definition in Collection System - where the Buckets in the Collection process are different from the finance

Critical

13 Month end stamping Critical14 Daily (where no cycles) Critical15 Cycle as defined in the Loan

SystemCritical

Cards16 Bucket information from Card

SystemNice to Have

17 Cycle based as per definition in Credit Card System

Nice to Have

of 274


Broken Promise tracking18 Parameterized tracking for

Various products - Product based strategies

Critical

19 Grace days - for promised payments not received on promise to pay dates

Critical

20 Hold days - where the fate of the clearing cheque is not known immediately

Critical

21 % of amount to receive to qualify for promise kept

Critical

22 Different treatment for Cash CriticalPortfolio Segmentation & Work AllocationUser definable queries for the segmentation (Queuing). Product based strategies

23 Product - such as Personal finance, Cards, Mortgages and so on

Critical

24 Queuing based on customer attributes such as VIP, Skip, Fraud, Legal and so on

Critical

25 Account attributes - Buckets, Overdue amount, Outstanding amount, installment date and so on

Critical

26 Special attributes - Broken Promise, Cheque return and so on

Critical

27 A combination of all of these attributes

Critical

28 A hierarchy of Queues to avoid conflict - to avoid one account falling in multiple Queues when they satisfy multiple Queue logic

Critical

29 Difficulty index definition for each Queue for Load balancing based on the perceived difficulty

Critical

Allocation of Queues - Beginning of day - Back end process

30 Attaching Queues to Agencies according to skill sets

Critical

31 Assigning Queues to Collectors under respective Agencies - Dynamic movement of accounts satisfying a Queue logic

Critical

of 274


32 Assigning Queues to a pool of Collectors under an Agency

Critical

33 Reassigning Queues to another Collector / another Agency - escalation for effectiveness during operation

Critical

34 Reassigning accounts to Collector / another Agency - escalation for effectiveness during operation

Critical

Action based prioritization for follow up - Beginning of day Back end process

35 Rule (algorithm) based work list generation for the day, from actions such as

Critical

36 Call back, promise to pay, broken promise, cheque return, no follow-up

Critical

37 Fresh accounts where follow up is yet to begin

Critical

Work Prioritization38 Action code priority for calling Critical39 By products Critical40 For Finance Critical41 Account priority within the action

code groups by productsCritical

42 Priority based on Location for Field Collectors

Critical

Classification Process43 Special handling for designated

customer such as VIP, business partner etc. - By amount range - By delinquent days range (segment collection by days)

Nice to Have

44 The criteria setting for determine the classification parameter which can set up the new criteria of delinquent days range (the number of overdue days) in each buckets.

Critical

45 The working Queue within the classification by System parameter setting as flexible parameter setting for example: - The amount of overdue installment in each buckets - The number of overdue periods

Critical

of 274


in each buckets etc.46 The classification of accounts by

billing/ statement cycle for low level dunning on mild delinquent accounts - By delinquent days range (segment collection by days) - By segment - By amount range

Critical

47 Account under litigation recovery - By delinquent days range (segment collection by days) - By segment - By amount range

Critical

48 Classify collection accounts into geo-regional collection branches/ centers for better customer immediacy and turnaround

Critical

49 Account attributed such as setup of the classification - Product of combination of products - Amount Due - Nationality, due date delinquent days - Billing/ Statement cycle - Total Loan - Geo-regional branched or centers - Open date/ Relationship since - Utilization of credit limit/line - Other criteria ……

Critical

50 The dunning letters (reminder letter, terminate letter) / collection notice should be generated by the automatically and/or manual which depend on the classification of delinquent accounts such as overdue 1 period, overdue 2 periods etc.

Critical

51 The solution should have the facility to define function codes. Accounts will be classified into homogenous groups based on the function codes to facilitate collection efforts.

Critical

52 Movement of accounts should be governed by:• State Processors – which route accounts across functions based

Critical

of 274


on the parameters detailed in the location parameter table• State Assignment – these are rules based on which accounts are routed/rerouted on a daily basis to the states in which they are to be workedDue Follow-upOutbound Calling

53 Calling from the prioritized worklist of a Queue

Critical

54 Automatic pop up(Relationship screen) of accounts from the worklist in the set priority

Critical

55 Provision to capture follow up trails (actions - such as promise to pay, call back etc.) to the customer accounts

Critical

56 Provision to attach attributes such as Skip, Disputes, Legal, Employee etc. for segmentation and allocation

Critical

57 Referring accounts to fellow Collectors for help/advice

Critical

58 Routing (escalating) accounts to Supervisor in case of difficulty

Critical

Inbound Calling59 Receiving incoming calls from

delinquent customersCritical

60 Search based on standard fields Critical61 Configurable search label

definition by productCritical

62 Adding follow up trails (actions - such as promise to pay, call back etc.) to the customer accounts

Critical

Digital Loans63 Capability of the System to

generate a common folio number for the purpose of linking/ monitoring existing customers

Critical

64 Automated Text Messaging prompts before accounts become due

Critical

65 Automatic text Messaging for payment reminder of accounts on due date

Critical

66 Recognition of payments, with text generation, & exclusion from work list

Critical

of 274


67 Automatic pop up of deliquent accounts by set priority.

Critical

68 Integration with CBS, for funded account report, with sniffing capability

Critical

69 Automatic prelisting /listing text messaging within prescribed time limits

Critical

Field Referrals70 Statcard generation Critical71 Contents definable by product Critical72 Sorting by a field (Location / area) Critical73 Generation by Agency Critical74 Generation by Collector Critical

Legal Recourse75 Identification by rules - Queue

strategyCritical

76 Referral to Legal by Critical77 Collector Critical78 Customer action Critical79 Action result Critical80 Allocation of Legal accounts to

Legal officerCritical

Repossession81 Identification of accounts by rules

- Queue strategyCritical

82 Identification by action of customer

Critical

83 Identification by responses from customer

Critical

Initiation84 Notice to customer of his

continuing default - threat to force conditions of contract

Critical

85 Refer to repo Agency Critical86 Letter to Agency Critical87 Date of repossession Critical88 Communication to Local police Critical89 Name of Garage/warehouse where

storedCritical

90 Capture gist of Inspection report of repossessed asset for condition

Critical

91 Notice to customer informing him of the repossession with final call for payment

Critical

of 274


Sale of repossessed asset92 Capturing settlement figure on the

date of repossessionCritical

93 Capturing expenses incurred on repossession and amount incurred to transfer title to buyer, debited to customer

Critical

94 Letter to auction house with details of asset and upset price

Critical

Bidding details95 Capture highest bid details Critical96 Date of delivery of asset to the

highest bidder with documents for transfer of ownership

Critical

Short fall capture97 Capturing expenses incurred on

sale / garage rent / legal expenses to the account of the customer

Critical

98 Capturing short fall calculation after sale

Critical

99 Notice of Shortfall to customer with time limit for payment

Critical

100

Capture decision on legal proceedings for Short fall

Critical

Repossession Collection Efficiency Monitoring & Rule Based Escalation

101

By repetitive reply codes Critical

102

By no action Critical

103

By dates Critical

104

By definable conditions as per business requirement

Critical

105

By promise to pay amounts Critical

Backend Support for follow up106

Preparation of Dunning letters/SMS/email (Auto-dunning and Batch)

Critical

107

Multiple templates for each product

Critical

108

Multiple language templates Critical

109

Suppress communication / overrides

Critical

of 274


Operational activitiesGeneric

110

Capacity Planning vis-à-vis delinquency portfolio

Critical

111

Processing of small balances cleanup for reversals

Critical

Reports & Dashboards112

Bucket flow reports Critical

113

Payments and write Back Reports on Substandard Accounts

Critical

114

Detailed with drill down into the accounts

Critical

115

Summary with drill down into the accounts

Critical

116

Portfolio trend reports - with definable sections or cuts

Critical

117

Aging report Critical

118

Advocate monitoring report Critical

119

Collection efficiency report Critical

120

Collector Productivity report Critical

121

Staff Productivity Reporting(KPI) - Track collections efforts by Collector to determine productivity. The System should generate reports daily - total attempts made , total contacts established, total promise taken, total promised amount, total amount collected on kept promise, total accounts actually worked.

Critical

122

No Activity Report-This report gives the number of accounts where collections activity has not taken place in the last 1 week, 2 weeks, 3 weeks and over 3 weeks

Critical

123

No Contact Report-This report will contain only accounts that have been attempted and where contact has not been established with the customer.

Critical

124

Collectors Effectiveness Report-Collector Effectiveness Report, a monthly report is produced with an objective of measuring the

Critical

of 274


effectiveness of our Collectors. This is based on the kept promise ratio( contact/attempts)

125

Intensity MIS-This report describes the extent of coverage and no. of contacts made and their corresponding results.

Critical

126

Skip MIS - This gives the total number of accounts in skip Queue , Number of customer's contacted , pending for early write offs

Critical

127

Delinquency MIS – The Report that generates the details about delinquency rate - delinquency lag , coincident indicators for 30, 60, 90,120,180DPDs

Critical

128

Dunning letters- MIS on total letter sent

Critical

129

Producing weekly/monthly reports on Staff productivity based on actual file reviews.

Critical

130

Should generate reports for provisioned accounts as per the bank's requirements, detailing amount outstanding, provisions made and any interest/charges calculated but not levied on those accounts

Critical

131

The solution should provide reporting online reporting facility into the database and calendar.

Critical

132

Report and MIS should produce daily, weekly and monthly standard performance statistical reports to measure the collection performance as the individual team and agent (both HQ and branch)

Critical

133

System should have dashboards with filters to drill down. It should provide a holistic overview of the Portfolio performance, Collection efficiency etc.

Critical

Collection Agency Management134

Identification of accounts for allocation to Agency as per defined policies

Critical

13 Allocation of accounts to identified Critical

of 274


5 Agencies136

Generation of Agency Assignment Reports

Critical

137

Printing of Stat Cards for allocated accounts

Critical

138

Update of feedback on customer accounts

Critical

139

Monitoring of portfolio and resolution

Critical

140

Tracking of customer payments on portfolio

Critical

Monitoring of Productivity MIS of the agent

Critical

141

Generation of MIS Reports on Productivity and Effectiveness of callers

Critical

Computation of Agency Billing142

On Bucket flow - % of amount / actual amount of flow

Critical

143

On actual amounts collected Critical

144

Other parameters such as # of Promise Kept, # of contacts

Critical

145

On individual performance and team performance

Critical

146

On retainer basis Critical

Review of Agency performance147

Reports on Agency performance - Targets vs. Actuals

Critical

Receipt Books Management148

Issuance of Receipt Books to Agencies

Need to Have

Other requirements149

Collect System should support below Islamic product follow-upsIslamic Credit card, Murabaha, Tawarroq, Mudarabah, Musharakah, Ijara, Istisna and qard hassn, etc...

Nice to Have

150

Real Time interfacing from all financial applications to Collections System for Notification of payments

Critical

of 274


151

Behavior Score should be available in Collections System

Critical

152

Real time interface with Core banking System

Critical

153

Database and interface support for Arabic characters

Critical

154

Feature of user access and trend of access to provide intelligence

Critical

155

Ability to generate SMS and e-mail messages

Critical

156

Ability to set actions and priority to Queues and to import and utilize a Queue account assignment and generate customer communications (SMS/e-mail/letter) based on a batch file from the relevant parent processors

Critical

157

Support calculations of external Agency fees and commissions

Critical

158

Supervisor monitoring capability in real time through GUI screen that is easy to read and analyze and that allows supervisor to take appropriate action

Critical

Support limited inquiry capability for external collection Agencies

Critical

159

Dynamic re-assignment of high-priority accounts to collection personnel based on workflow

Critical

160

Support ad-hoc manual shifting of accounts from one Collector to another

Critical

161

System will support all consumer finance businesses – Credit Card, personal finance, Overdraft, etc.

Critical

162

Info security details in standard format has to be replaced with current requirement on security features wherever required

Critical

163

integration with Document Management system

Critical

164

Ability to handle repayment options as per policy of the Bank and ability to do recalculation whenever there is a change in the policy of the Bank/QCB.

Critical

165

Ability to support integration with single sign on system

Nice to Have

of 274


166

Ability to get feed from another system and store credit rating related information

Critical

167

Ability to see entire customer portfolio in one view

Critical

168

Ability to link to Integrated desktop system

Critical

Integration169

Integration with Core banking phoenix

Critical

170

Integration with GL Critical

171

Integration with Call Center & Dialer

Nice to Have

172

Have the ability to be installed in several channels (Branches, Call Center & Collection Department) with different authorization levels

Critical

173

Can interface through a middle-ware layer. Can be the IFX we are using currently or any other middle ware in the future

Critical

174

Can integrate with Multiple Core banking for multiple institutions

Critical

SecurityAccess Control

175

An access log should exists to review all the disabled accounts, user accounts with last login date

Critical

176

Ranges of user level access should be applied to reports, letters and contact management

Critical

177

The Access control privileges and its profiles should be documented (matrix) with the level of access to the Systems/forms etc.

Critical

178

Different login permission: with limited scope to clients and other points of contact with whom you wish to share case information. System should allow to share important information with clients while preserving privacy for company proprietary data such as financial information.

Critical

179

Different login permission: Group of Collectors based on user-defined criteria

Critical

18 The information System should Critical

of 274


0 have authorizations for controlling the flow of information within the System and between interconnected Systems in accordance with applicable business rules and policy

181

The information System should enforce a limit of consecutive invalid access attempts by a user during a time period. The information System automatically delays next login prompt according to when the maximum number of unsuccessful attempts is exceeded

Critical

182

Enabled Logs should contain the unsuccessful login attempts

Critical

183

The System log should determine the System use and it should be logged

Critical

184

The information Systems should limit to the concurrent sessions based on the capacity requirements

Critical

185

The information System should prevent further access to the System by initiating a session lock that remains in effect until the user reestablishes access using appropriate identification and authentication procedures

Critical

186

The information System automatically terminates a session after of inactivity

Critical

187

A method to supervise and reviews the activities of users with respect to the enforcement and usage of information System access controls should exist

Critical

Identification and Authentication

188

The information System should identify users uniquely. The mode of authentication can be a choice to the business requirement (subscribed user with strong password)

Critical

189

The information System should identify and authenticates specific devices before establishing a

Critical

of 274


connection190


Critical

Audit and Accountability191

The information System should provide the capability to compile audit records from multiple components throughout the System into a time-correlated audit trail.

Critical

192

The information System should provide the capability to manage the selection of events to be audited by individual components of the System

Critical

193

The organization allocates sufficient audit record storage capacity and configures auditing to prevent such capacity being exceeded.

Critical

194

In the event of an audit failure or audit storage capacity being reached, the information System alerts appropriate organizational officials and takes the following additional actions: [Assignment: organization-defined actions to be taken (e.g., shut down information System, overwrite oldest audit records, stop generating audit records)]

Critical

195

The System should have the required facility enabled for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations

Critical

196

The System should provide time stamps for use in audit record generation.

Critical

197

The System configuration should be enabled to protect audit information and audit tools from unauthorized access, modification, and deletion.

Critical

198

The Client IP address of the source should be captured as a part of log and accessible for review

Critical

of 274


Configuration Management199

The production System configuration should follow the process of baseline as part of release management

Critical

200

As per the Change management policy and procedures, Appropriate officials should approve information System changes

Critical

Contingency Planning201

The proposed solution should have a contingency plan for the information System addressing contingency roles, responsibilities, assigned individuals with contact information, and activities associated with restoring the System after a disruption or failure

Critical

202

The contingency plan for the information System to determine the plan’s effectiveness and the organization’s readiness to execute the plan should be prepared

Critical

203

The System backup plan should be in alignment with contingency plan of the System

Critical

Communication Channel204

The information System should protect the integrity of transmitted information. The communication flow should be end-to-end encrypted

Critical

205

The communication flow should be clear stating the Ports, Source/Destination required to function

Critical

System and Information integrity

206

The System should implement malicious code protection that includes a capability for automatic updates (Anti-Virus client and System Critical / Security Patches Updates)

Critical

of 274


Monitoring & Review207

The Application should have interface for the IT Security team to review access of the Systems to review user access / Modification / information of application usage

Critical

208

Support Escalation Matrix, followed by agreed SLA with Vendor

Critical

1.3.6 Risk Management and Compliance

General Requirement Criticality (Critical/Nice to Have)


1 Ability to change passwords for all generic accounts in the database

Critical

Know Your Customer and AML support requirements

2 System to provide fields for updating customer's specific nature of business and annual account turnover.

Critical

3 In instances where customer is employed, system to provide field for capturing Name of employer and position held

Critical

4 System to have tag notes to trigger staff if an account is missing any mandatory KYC particulars that the customer ought to avail or any other message that staff need to know before processing any transaction in a client's account

Critical

5 The system should have fields to append Risk Profile/Category of a customer. The same should be editable to take care of customer's changing profiles- from high, medium to low risk and vice versa as the case may be. Drop down preferred

Critical

6 System to enable account search using Name, Identity card number, Passport number, Certificate of incorporation number or Business Name

Critical

7 System to have fields for updating accounts with individuals and Corporates Personal Identity Numbers No’s, ID No’s and Huduma number

Critical

of 274


8 System to host watch-lists capable of being updated from time to time and screen against black listed customers at the point of account opening or initiating any transaction including Bankers cheque purchase etcetera. The watch lists to include but not limited to OFAC, UNSC, PEP, Acuity, World check, EU & HMT

Critical

9 System to support integration with AML solution

Critical

10 System should carry out reverse screening on existing data

Nice to Have

11 Provide a field for searching all customers’ accounts including related accounts where he is a party.

Critical

12 Provide a mandatory field which assist in populating all related accounts during account opening to help in grouping customer related accounts.

Critical

13 Provide for centralized secondary approval at both Dormant activation and amendment of KYC data.

Critical

14 Support making of mandatory KYC & AML data field compulsory at account Opening process.

Critical

15 System to allow IT support staff to be able to define all account opening KYC data as either mandatory or optional or by choice

Critical

16 Support mandatory customer data on Risk rating of Customers (High, Medium, Low)

Critical

17 Support marking of exact nature of business or professions such as Lawyers, Doctors, Forex Bureaus, Casinos, Contractors, Government agencies, Schools, Wholesalers, Pharmacists, Supermarkets, Petrol Stations, M-Pesa agents etc.This includes Main category and sub category where applicable.

Critical

18 Support integrating the system (data tables and fields) with transaction monitoring systems

Critical

19 Supports KYC & AML static data reports per Customer, Branch, Product, Risk rating, Nature of business

Critical

20 Supports reports on cash deposits & withdrawals transaction reports per user, per branch, per product, per risk rating

Critical

21 The system should avoid duplication of data capturing fields. i.e. within the system we

Critical

of 274


should have one reference table for all customer static data where any account created will be reading from and updating the same fields at account level. NB: No updating of static data at account level

22 The system should be able interphase with other systems, able to share customer details from CBS

Critical

23 The system should have controls to ensure any customer details amendment rights are tied to specific users

Critical

24 The system should support MIS Reports of any kind that can be developed internally without referring to the vendor, that is, report writing tool must be provided.

Critical

25 The system should be capable of one way automatic downgrade of loan accounts with only manual upgrade intervention.At the point of manual upgrade, it should be able to release provisions held together with interest in suspense.

Critical

1.3.7 Treasury Requirements# Requirement Requirements

Criticality (Critical/ Nice to Have)


1 Creation of multiple portfolios, business units Critical2 Supports automated and manual capture with

only manual amendments and cancellationsCritical

3 Each trade ticket should allow for free format text box

Critical

4 The platform includes standard templates for deal input containing all standard market input fields based on the product type.

Critical

5 The system should support customized input templates. Save multiple deal entry templates.

Critical

6 Dealer to be able to save multiple deal entry templates.

Critical

7 The platform has the ability to perform pre trade analytics before execution (counterparty, dealer limits, P&L, risk

Critical

of 274


checking)8 The system should allow entering of cash

flows from an external source.Critical

9 The system should allow entering of financial instruments and creation of cash flows in the system itself

Critical

10 The system should allow to seek referral where limits have been exceeded

Critical

11 Should support user defined workflows Critical12 Easy parameterization of the system covering

all possible scenariosCritical

13 The system should be able to allow definition of an unlimited number of term structures for a satisfactory coverage of the various markets (MM, bond and swap etc.) for specific currencies and countries

Nice to Have

14 Ability to flag broker on the trade and calculate the applicable brokerage on the deal as per specified pricing parameters

Nice to Have

15 Back office can never change trade details - they have to be processed by Front Office

Critical

16 System should have the ability to hold the dealing mandate details.

Critical

17 Integrate with Trading Platforms like Reuters FXT/Bloomberg and other online trading platforms/Core banking system and Swift.

Critical

Ability and willingness to set up structures to capture market data, where it is not available

Critical

18 Ability to calculate weighted average duration of fixed income portfolio wise

Critical

19 Audit trail of all activities Critical20 Ability to link amendments and

cancellations / reversals to original deal.Critical

21 System support market data from Reuters and Bloomberg

Critical

22 Pricing tools- the pricing tools must be able to cover all the required instruments and use standard market-accepted pricing algorithms.

Critical

23 Ability to store historical deal and rate set information

Critical

24 Ability of saving historical data and methods of restoring it in the future

Critical

25 Ability to download reports in common export formats ( excel, pdf, csv, html) either as a scheduled, batch or on-line request.

Critical

26 Each trade should have a unique transaction Critical

of 274


number.27 Rate Fixings (e.g. Libor) are automatically

saved each day and are applied to any Floating Rate instruments.

Critical

28 Ability to be able to set-up curves for stress testing.

Critical

29 The system should have the flexibility for choosing parameters for display and the methods for filtering and drilling down data and reports by trades, by dealer, by desk, by instrument, by entity, by portfolio, by product or counterparty.

Critical

30 Front Office personnel should not post accounting entries on general ledger accounts

Critical

31 System should support wide and flexible hierarchy structures including multi entity (branches) centralized trading.

Critical

32 System should provide user access controlled data viewing between branches / desks / units / traders

Critical

33 System should have the ability to interface with the core banking system for settlement, accounting, revaluation etc.

Critical


Critical

35 Ability to choose, assign, combine and link on the term structure the benchmark instruments quoted on the market for money market instruments loans / deposits, bonds, call , notice and term money

Critical

36 Ability to Incorporate industry standard calculation methods in yield curve generation functionality implied from FX Spot-Forward structure. Generate zero curve points from par curves using bootstrapping techniques.

Nice to Have

37 Ability to display charts of par, zero and forward curves.

Critical

38 Revaluation Critical39 Ability to save closing rates Spot, Forward

Points, Yield Curves, Volatility Curves, Bonds prices, Equities prices.

Critical

40 System should have the ability to use a number of valuation methods -set of Term Structures used in portfolio pricing and methodologies used in curves construction

Critical

of 274


41 Reports Critical42 The ability for users to configure reports

within the system according to their business needs.

Critical

43 The system should have list of pre designed reports that are based on best practice for both risk and P&L reporting

Critical

44 Real time position and P&L by dealer Critical45 Reports Dealer wise position report Critical46 Reports FX Financial report Critical47 Reports Revaluation reports with deal details Critical48 Reports System must provide the ability to

configure different types of reports as per business needs (in a user friendly way, without technical intervention)

Critical

49 Reports All deals done for the day Critical50 Reports All outstanding deals by maturity Critical51 Reports All outstanding deals by customer Critical52 Reports All outgoing messages by type Critical53 Reports Confirmation matching status Critical54 Reports List of deals reversed / deleted by

dateCritical

55 Reports Accounting entries by deal for the day or overall

Critical

56 Reports List of realized P/L report Critical57 Reports List of unrealized P/L report Critical58 Exception reports for off market rates Critical59 Exception reports for Limit breaches Critical60 Exception reports for negative P&L and

market exchangeCritical

61 Reports Accrued profit detail report CriticalForeign exchange

62 Instruments Spot Critical63 Instruments Outright Forward Critical64 Instruments FX Swap Critical65 Instruments Split Value FX Critical66 Instruments Internal deals between desks Critical67 Support segregation of FX positions from

CBS by originating unitsCritical

68 The Blotter should: Critical a) Pick branch

transactions done at the branch levels and be able to reflect the deals and the positions

created as branches input the deals.b) Provision for input of deals done on phone.

of 274


Provision for split deal dating.69 Ability to generate forward points for

revaluation based on yield curves.Critical

70 Ability to be able to view Positions and P&L at Portfolio level by Trader/Business Unit Level.

Critical

71 On-line blotter for position keeping. Critical72 On-line P&L transaction and position reports

with drill down to trade level to manage exceptions

Critical

Money Market73 Instruments Interbank

Placements/BorrowingsCritical

74 Instruments Repurchase Agreements and reverse repos

Critical

75 Instruments Treasury Bills Critical76 System should support roll over of money

market placements and borrowings -for deals to be rolled principal only, principal plus interest and part repayment.

Critical

77 System should support partial maturity or increase of principal.

Critical

78 System should support assigning Bonds and T-bills to a Repo Transactional.

Critical

79 System should support assigning multiple securities to a single repo.

Critical

80 System should be able to compute accruals on a daily basis.

Critical

1. The software should capture the following branchactivities for monitoring and management purposes:a) Major movement of deposits.b) Issuance of RTGS.c) Increases of overdrafts and advances to customers.d) Generate a report of expected maturities of fixed deposits

81 RTGS should be initiated at the branch and then flow to the back office. Front office should be able to view in real Time , the processed transactions.

Critical

82 System should be able to compute automatically the broker fees based on

Critical

of 274


predefined rules or allow for manual override.

Investment Operation83 Instruments Fixed/Floating Rate Bonds

Issued by Govt/Financial Institutions/Corporate

Critical

84 Market Data from Bloomberg/Reuters Critical85 Appropriate accounting treatment based on

bond classification.Critical

86 Inventory Processing should be as per Weighted Average Cost

Critical

87 Should support different calculation basis (A/364, A/360, 30/360, A/365)

Critical

88 Should support amortizing securities. Critical89 Should support effective interest rate

amortization of premium / discount of HTM securities.

Critical

90 Should support different bond calculators e.g. bond partial redemption.

Critical

91 Ability to generate market prices based on yield curve.

Critical

92 Ability to report all positions by issuer and country

Critical

Limit Management93 Solution should support the following limits Critical94 Counterparty limit Critical95 Settlement limits Critical96 Tenor limits Critical97 Solution should provide ability to define

limits which are split by counterparties and across branches with the total of all the limits adding up to the total limit amount

Critical

Business Unit Nice to HaveProduct type level (Treasury products only ) Nice to HaveTenor level CriticalCounterparty / Counterparty Group Nice to HaveCountry Nice to HaveIssuer Nice to HaveIndustry / sector Nice to Have

98 Solution should support limits check in real time or in batch mode

Critical

99 Solution should provide date range for limit defined

Nice to Have

of 274


100

Solution should provide flexibility to define limits for each branches

Nice to Have

101

Solution should provide the following types of limits;

102

Issue/Issuer Limits on Bonds Nice to Have

103

Is it possible to import/export limits in the solution? (automated upload of limits)

Nice to Have

104

The solution should generate alerts to multiple users whenever limits are breached in the system as well as email

Nice to Have

105

The solution should provide with excess management workflow.

Critical

106

Solution should convert all the exposures in different currencies to the currency of the limit

Critical

107

The solution should allow to identification of the counterparty interbank limit exceeded, the users that exceeded it and the users that allowed the surplus?

Critical

108

Does the solution allow booking a size of the counterparty credit risk for a period, where during this time, others desks and traders can't use this limit booked?

Nice to Have

109

Does the solution allow to set-up an expiry date to the counterparty interbank limit? Even after maturity is it possible to search the limits allocated and consumed?

Nice to Have

Exposure calculation110

Solution should provide the following methodologies for exposure calculationNotional CriticalMarket Value Critical

Market Risk111

The system should provide Basic Value-at-Risk engine to calculate market risks using Historical VaR method

Critical

112

Solution should support the following limits

Position limits CriticalStop/Loss limits CriticalTransaction limits CriticalRate tolerance limit Nice to HaveSensitivity limits Nice to HaveSolution should provide flexibility to define

of 274


limits byDesk CriticalPortfolio CriticalBranches CriticalDealer CriticalCurrency CriticalCurrency group CriticalCurrency pair CriticalSecurities CriticalTenor CriticalInstrument CriticalInstrument group CriticalCountry Risk Limits Nice to Have

113

Solution should support limits check in real time or in batch mode

Critical

114

Solution should support excess alert definition

Nice to Have

Limit management for reporting115

Solution should provide functionality for breaching limits reservation

Critical

116

Solution should provide monitors for exposure and limit utilization across treasury and investment

Critical

117

Solution should provide standard reporting on Limits / utilization / exposures at different aggregation levels

Critical

118

Solution should provide excess reports and excess authorization workflow

Critical

MonitoringCritical

119

Event Correlation ( pending, incomplete, same customer, etc.

Critical

120

System Alert capability Critical

121

Log generation Critical

Reporting

122

Detail reports available Critical

123

Easy report generation and customization Critical

12 Dashboards Critical

of 274


4125

Comprehensive audit trail - Read Only -Export to 3rd party application

Critical

126

Easy dashboard view customization Critical

127

State relation with, or dependence on other subsystems i.e. components of a suite

Critical

128

Solution should provide reports across multiple dimensions (individual Trade/book wise/trader wise/sector wise/strategy wise/portfolio/expiry wise)

Critical

129

Solution should provide PL reporting across multiple dimensions (individual Trade/book wise/trader wise/sector wise/strategy wise/portfolio/expiry wise)

Critical

130

Solution should provide cashflow bucketing reporting.

Critical

131

Solution should provide ability and ease for customization of reports

Critical

132

Should have a module for amalgamated Assets and Liability Management reports.

Critical

133

Solution should provide MTM reporting for all trades within treasury and investment

Critical

1.3.8 General Ledger Requirements# Requirements Requirements

Criticality ( Critical/ Nice to Have)


1 Support online update to GL accounts for all types of transactions.

Critical

2 Provide facility to generate the daily Trial Balance and balance Sheet in Bank’s Format.

Critical

3 Provide facility for reflecting in the General Ledger Balance the total of credit balances in current accounts on the liabilities side and total of debit balances in Cash Credit accounts on the asset sides respectively by taking into account the total of debit balances in current accounts on the assets side and total of credit balances in Cash Credit accounts on the liabilities side every day.

Critical

4 Provide ability to produce General LedgerBy Branch Critical

of 274


By Branch and its extension counter CriticalBy Centre CriticalBy Zone(as defined by bank)/ Regional

OfficeCritical

Bank as a whole Critical5 Support application of alternate methods for

generation of reports required for statutory purposes and for internal Management Accounting.

Critical

6 Provide facility to capture all financial transactions concurrently for

7 Transaction currency CriticalAccounting unit currency (‘local

currency’)Critical

7 Provide facility for fiscal year accounting. Critical8 Allow splitting of fiscal year as defined by

user.Critical

9 Support user-defined financial reporting periods other than fiscal year, e.g. 15 months or 9 months.

Critical

10 Support monthly / quarterly / half-yearly accounting periods within each fiscal year with facility for aggregation of monthly figures into quarterly / half-yearly figures.

Critical

11 Provide facility to automatically maintain and carry forward of period-end account balances to subsequent periods for

Each accounting period within a fiscal year

Critical

Across fiscal years / financial reporting periods

Critical

12 Allow postings pertaining to prior dates (Value Date) after authorization

Critical

13 Provide facility to continue operations into the new fiscal year with authorization even if due to some contingency, closing of accounts for the prior fiscal year remains incomplete.

Critical

14 Provide facility for detailed logging of all events related to ‘opening’ and ‘closing’ of accounting periods

Critical

15 Provide facility for acceptance and posting of only balanced journal entry transactions.

Critical

16 Support automatic calculation of ‘Retained Earnings’ for each fiscal year and its automatic carry forward to the next fiscal year.

Critical

17 Support defining organization hierarchy

of 274


allowing multiple levels reporting of ‘Financials’ (trial balance, balance sheet and profit and loss accounts). The hierarchy definition to support reporting at

Bank / Accounting Entity Level CriticalZonal Level CriticalBranch Level CriticalDistrict Level Critical

18 Provide facility for reporting of “Financials” at user-defined levels

Critical

19 Provide facility to define the chart of accounts allowing reporting of accounted transactions

Critical

20 Provide facility to define the individual general ledger accounts with following parameters, including but not limited to:

Effective dates of the account CriticalOverall blocking of account CriticalBlocking of an account for specific

accounting period / entity / location / branchCritical

Mapping of each general ledger account to any node (subsidiary heads) of the chart of account(s)

Critical

Mapping of each general ledger account to one or more interfacing chart of accounts (since multiple systems would be interfacing with the general ledger)

Critical

21 Provide facility to show break-up with /without sub account details for all applicable GL accounts

Critical

22 Support each general ledger account to be maintained in different currencies.

Critical

23 Provide facility to identify certain General Ledger accounts as bank / cash accounts.

Critical

24 Support recognizing, accounting and reporting of transactions with respect to various heads including, but not limited to:

Asset CriticalLiability CriticalIncome CriticalExpense CriticalContingent Critical

25 Provide facility for recognizing, accounting and reporting of transactions, which are not directly initiated by customer, such as interest recoverable, matured principle, provision for interest, etc.

Critical

of 274


26 Provide fully functional interface for affecting inter-branch / location, inter-bank accounts funds transfer with complete integration with general ledger functionality.

Critical

Transactions & Posting27 Provide facility for assigning and usage of

specific accounting vouchers (documents) for specific types of transactions.

Critical

28 Automatically generate and assign sequential numbers to accounting

Critical

Bank / Accounting entity CriticalLocation / Branch CriticalFiscal year Critical

29 Provide facility for direct posting of voucher and should not allow for keeping the voucher ‘on-hold’.

Critical

30 Provide facility for reversal of voucher / accounting document:

Critical

Individually CriticalCollectively based on, but not limited

to, parameters like voucher type, accounting entity, voucher reference number, location, user, etc.

Critical

Support capture of reason for every reversal.

Nice to Have

31 Ensure that reversal transactions should consider the effect in the analysis of accounts for the purpose of MIS.

Critical

32 Provide facility for faster creation of new voucher / documents using

Critical

Voucher / Document templates Critical33 Provide facility for creating recurring entries

that allocates one amount to multiple accounts based on user-definable rules.

Critical

34 Provide facility for setting of starting and ending date, period / year for recurring entries.

Critical

35 Provide facility to upload transaction in soft copy and auto posting of vouchers for these transactions.

Nice to Have

36 System to have capacity to support batch reversal

Critical

37 Provide facility for automatic / scheduled processing of recurring / repetitive Voucher documents for user definable dates and period e.g. monthly, bi-monthly, quarterly etc.

Critical

of 274


38 Provide facility for automatic recasting of balance in the main account whenever a transaction is posted in the sub-ledger account.

Critical

39 Support restriction of direct postings to main accounts where sub-ledger account is maintained.

Critical

40 Allow selecting desired general ledger accounts (such as employee loan accounts, travel advance, etc.) to provide similar functionality for clearing of open debit and credit transactions within the general ledger account.

Critical

41 Provide facility for defining for each account (which is chosen to offer the clearing functionality) what should be the nature of the originating transaction (debit or credit) and what should be the nature of clearing transaction (corresponding credit or debit). The system should enforce the definition.

Critical

42 Provide facility for capture of following dates per transaction (with automatic update by system wherever possible), but not limited to:

Date (and time) of transaction CriticalValue date CriticalDate (and time) of authorization CriticalDate (and time) when transaction was

changedCritical

Date when transaction was reversed CriticalExchange rate used for foreign

currency transactionCritical

43 Support recording of transaction across accounting entity / branch / location through one accounting document. (Multi Branch access with proper authorization)

Critical

44 Support defining rules for automatically calculating and accounting for, but not limited to:

Difference on clearing unbalanced open items

Critical

Exchange rate difference postings (at time of clearing of open transactions)

Critical

Income Tax (payable as well as recoverable)

Critical

Interest on over-due amounts CriticalService Charges CriticalCompute all bank Critical

of 274


charges/commission/fees….etc. on listed services.

45 Ensure correct on-line generation of automatic entries based on defined rules at the time of data-entry or batch update itself.

Critical

46 Allow option to de-activate automatic generation of entries for batch-uploaded transactions.

Critical

47 System to have capacity to restrict manual entries to certain GLs unless with authority eg Interest income /expense

Critical

48 System to limit GLs available to Branches (Avail GLs on a need to have basis)

Critical

49 System to support automatic revaluation of General Ledgers for foreign currency

Critical

1.3.9 Customer Management

# Requirement Requirements Criticality (critical/ Nice to Have)


1 Customer Management module will hold customer information / profile for all the customers of the branch across various products of the bank.

Critical

2 System should have facility to search for existing customer based on

Title+ Name CriticalTitle+ Name + DOB CriticalAccount Number CriticalCustomer Number CriticalID No CriticalHuduma No/Passport No. CriticalCertificate of Incorporation CriticalBirth Certificate No. CriticalTelephone No. CriticalKRA PIN Critical

3 Allow staged completion of the customer profiles creation process (e.g. create a customer with just a customer-id and name with the ability to add / modify additional details at a subsequent stage)

Critical

4 Name, ID/Passport, photo, signature, phone no, Critical

of 274


biometrics. Get product codes attached to client IDs so immediately ID is created account no. System to bar end of day unless remaining account opening processes are completed in the system

5 Provide facility for customer ID creation with limited information at branch

Critical

6 Allow combination of multiple customers into a single joint account and single Customer ID

Critical

7 Provide for de-duplication of customer ID based on various Standard / user-selectable parameters including Customer name (spelling, initials, first / middle / last names, phonetics etc.), address, contact person, etc. and provide alerts for probable duplication.

Critical

8 Should have facility for generating Welcome letters for the new customers

Critical

9 System should have facility of selecting customer type (individual/ non-individual ) at the beginning of customer creation process

Critical

10 Based on the selected customer type, system to follow pre-defined workflow/procedure

Critical

11 For existing customers, system to be capable of populating the customer information for viewing /modification

Critical

12 Provide facility to modify / update the customer details under maker checker and send notification to account holder

Critical

13 System should have ability to record structured profiles of each Customer of the branch including Retail, Corporate, Government etc. and able to auto-generate unique customer ID as specified by bank

Critical

14 Provide facility to auto assign the Branch code as per bank user login ID.

Critical

15 For individuals as single / joint account holder, proprietor, partner, director etc. as well as borrower, guarantor etc. Following details are required to be captured. The field length for capturing these customer details should be parameterized;

Critical

1 Salutation Critical1 Last name Critical

First name CriticalMiddle name CriticalTitle CriticalNext of Kin (Field to specify relationship) Critical

of 274


Name of father Nice to HaveName of Mother Nice to HaveNationality CriticalDate of birth CriticalGender – with drop down of Male, Female

orOther

Critical

Name of guardian in case of minor CriticalMarital status (Married, single, widower

etc.)Critical

Residential status CriticalCurrent address with pin code CriticalPermanent residential address Critical

116

Whether owned, rented, company provided quarters, family house etc.

Critical

City CriticalTelephone Number CriticalMobile Number CriticalE-mail address Critical

Current Banker Details CriticalRisk Profile ( High / Medium / Low) CriticalTDS / WHT Critical

TDS/WHT Exemption Reason CriticalTDS/WHT Percentage. Critical

KYC Complied (Y/N) CriticalKYC Document List Critical

17Passport details such as date of issue,

valid till, issued by, passport no.Critical

PAN / SSN/ NSSF Number and issuing authority

Critical

Address Proof Nice to HaveRelationship Manager Critical

18 OccupationEmployed/Self-employed CriticalProfession CriticalEmployers Name, If employed CriticalOffice address CriticalPhone number CriticalEmployed Since CriticalDesignation CriticalAnnual Income CriticalDetails of contact persons (with

relationship ),Critical

Other DetailsDate of Commencement of Customer Critical

of 274


relationManager, Power of Attorney Holder, etc. Critical

19 Specific Attributes (e.g. Physical Handicap, Senior citizen, Serviceman / Ex-Serviceman, Male / Female etc.)

Critical

20 Group Code for definition of Customer Hierarchy (used to flag individual within a group OR Family Code for grouping all members within a family) should Provide facility for at least two levels of Hierarchy.

Critical

21 Religion Critical22 In case of other than individuals the following

details be capturedName of Organisation Critical

23Constitution (e.g. Proprietorship,

Partnership, Private Ltd. Company, Public Ltd. Company, Club, Trusts, Government, Autonomous body etc.)

Critical

24Name (s) of proprietor, partners,

directors, promoters, Secretary, Chairman, President etc.

Critical

225

Name of beneficial owners and percentage ownership in the business

Critical

26Agents and Attorneys to Corporate

accountsCritical

227

Physical address Critical

228

Provide facility for particulars of proprietors / partners / directors / promoters etc.

Critical

29Addresses of registered / head office /

factory / local office Critical

Phone numbers - CriticalE-mail id CriticalSector / Segment CriticalIndustry Classification CriticalDate of Incorporation Critical

30Date of commencement of Business and

Commercial productionCritical

331

Whether enjoying credit facility from any other bank- Y / N

Nice to Have

332

If Yes, then name of bank, branch and address.

Nice to Have

33 Details of Introducer (another existing customer and in such case customer id of that customer

Critical

of 274


will do) such as name (three fields), Account No. etc.

34 Details of Introducer Critical35 Provide facility for additional 10 user definable

fields Critical

36 Records must be created and authorized by the supervisor as per maker-checker concept except system generated accounting entries. Necessary accounting entries must be passed in respective GL head. Provide option for Single / Dual authorization as per user requirement for any record / transaction level entry.

Critical

37 Validations for data entered as defined by bank for the respective field.

Critical

38 Mandatory field validations Critical39 Should have KYC compliance validation for

additional account holder.Critical

40 The customer data update at base level should be reflected at all other interfacing/related modules

Critical

41 Provide facility link all individuals operating individuals / non individuals accounts including Guarantor accounts to specific Customer ID.

Critical

42 Guarantor details – Name, ID No Critical43 Minor account Critical

Group Linkage44 Provide facility Group ID generation Critical45 Provide facility disable Group ID Critical46 Provide facility to link customers in a group Critical47 Provide facility to delink customer from a group Critical48 Comprehensive Single Window 360 degree view

of the all relationship of a client at both account level and client level covering the following details with drill down facilities

Critical

*Account Balance Critical*Account Statement Critical*Account Snapshot (Account Number, Currency Code, Product Code, Account Type, Relationship Manager ID, Account Opening Date Personal identification document type ad number, status of account, facilities enjoyed (cheque book, Teller, Call Center, Credit Cards, SMS, Overdraft, ATM, Internet Banking, Kiosk Banking, etc)

Critical

*Loan Account Status Critical*Account Photo/Signature Critical

of 274


*Account Cheque Return History Critical*Account Address Change History Critical*Notes Display Critical*Account Name Change History Critical*Customer Contact Details (Customer Number, Name, Spouse Name, Communication Address, Tel (Home, Office), Mobile, Email address, Office Address, Fax No. etc.)

Critical

*Customer Relationship View (Customer Number, Relationship Band, Review period from date to date, Deposits (product wise) with account balance and base currency balance, Advances (product wise) with currency, account balance, base currency balance, Total Business, Income Earned (with breakup of the various income GLs and amount), Net Income, Total Expenses with breakup of various expense GLs, net expense, Average Balances Maintained product code wise with average balances, etc.)

Critical

*Limit Line Enquiry Critical*Customer Delinquencies Critical*Customer Photo/Signature View Critical*Customer Cheque Return History Critical*Customer Address Change History Critical*Customer Notes Display Critical*Customer Operation Log Critical*Customer Data Log Critical

49 Under facility for search, include search based on National ID, Passport and others (Huduma number).

Critical

50 Allow persons opening a joint account to have all their details captured on a single client ID. Include a tab under the single customer ID that will enable capture the information

Critical

51 Allow Directors information e.g. name, ID/Passport number, contact details, contact details, physical address etc. t to be captured under the Corporate Client ID. Provide a tab under the corporate client ID for this purpose

Critical

52 Customer module to be scalable to enable the bank create local fields for capturing additional information required by the bank for certain specific purposes/regulatory requirements at no extra cost

Critical

53 System to support online or virtual opening of accounts

Critical

54 Alert for transactions not authorized in the Critical

of 274


system beyond X amount of time55 Automation of statement mailing using email

provided in the system Critical

56 Daily report on emailed statements Critical

57 Authorized Head Office users to be able to post transactions in branches e.g. revenue recovered at Head Office should be able to be booked at the branch at the time of recovery

Critical

1.3.10 Deposits & Accounts Requirements# Common Requirements Requirements



1 System should have facility to search for existing customer while opening the account

Name CriticalTitle + Name + DOB CriticalAccount Number CriticalCustomer Number Critical

2 Support various liability products, including but not restricted to:

3 Savings Bank (SB) - General, Staff, Salary Critical

Savings Bank Institutional Critical Current Deposit (CA) - General, Banks, Critical Call Deposit (deposit payable on demand not attracting interest).

Critical

Fixed deposit (General) where interest is paid out to the depositor periodically

Critical

Cumulative Fixed deposit (CFD) CriticalTerm Deposit (Short term/ Medium

Term /Long Term) Critical

Term Deposit (Cumulative / Non-Cumulative)

Critical

Term Deposit (Senior Citizen) CriticalTerm Deposit (Staff) CriticalTerm Deposit Critical

3Recurring Deposit (Predefined number

and amount of monthly deposits) Critical

4 Provide facility to stop opening a Critical

of 274


4 particular type of account / product type from a specified date. Existing account to continue unless & until closed or matured.

5 Daily Deposit Scheme Critical5 Allow auto-generation of a unique account

number for each and every deposit account (SB ,CA, TD, FD ….etc.) as per bank specification.

Critical

6 For opening FD (all products). After creation of customer ID and creation of account number, all FD receipts under that A/c should be open with a unique number

Critical

7 Provide facility for classification of accounts as per customer type / subtype

Critical

8 Provide facility for maintaining various codes as per Industry standard like Product code, account code….etc.

Critical

9 System to be capable of pre-populating the details from customer master for respective fields when creating a new account (Bank will provide and discuss the information details to be pre-populated with the selected Vendor at the time of Contract finalization)

Critical

10 Provide facility for capturing details including but not limited to:

Title of account CriticalName (First, Middle, Last name) with

salutation Critical

Father’s / Husband’s Name Nice to HavePostal Address CriticalTelephone CriticalMobile CriticalE-Mail CriticalDate of Birth CriticalGender CriticalKRA PIN Number CriticalPassport Number/ID No CriticalCertificate of Incorporation CriticalDetails of introducer. Critical

11 Provide facility for capturing mode of operation including but not limited to:

12For individuals: Singly, severally, jointly,

either or survivor, power of attorney (POA) holder, former or survivor. (JOINTLY OR SURVIVOR / S)

Critical

13For other than individuals e.g. Companies / Trusts / Clubs etc.: Any one, joint, an authorized operator and any one / more of the

Critical

of 274


rest of the authorized signatories. Also Provide facility for capture of modification with history

14Key in facility for: Date and names of authorized persons as per partnership deed / Memorandum & Articles of Association, Certificate of Incorporation and Resolution for opening account / Trust Deed etc.

Critical

15 To be able to add any other mode of operation Critical16 Provide facility for storing for specific number

of years, old account numbers (from earlier legacy system) with corresponding new account numbers.

Critical

17 For migrated accounts, there should be mapping of old account number to new account number and display wherever account number is used for easy identification

Critical

18 Support enquiry based on old account numbers.

Critical

19 Nomination for all accounts ( including Deposits):

Critical

20Provide facility for the capture of

following details including but not limited to:Name of the nominee CriticalAddress of the nominee CriticalRelationship with the account holder CriticalDate birth of the nominee (if minor). CriticalDate birth of the nominee / age of

nominee (ALL CASES)Critical

21Name of the person authorized to receive money in case of minor nomination

Critical

22Upon renewal, system should provide a facility to continue with existing nominees or change the nominees as requested.

Critical

223

Allow for modifications and cancellations of nominations with authorization.

Critical

24 Support recording of mode of deposit of the initial amount: Cash / Transfer / clearing.

Critical

25 Provide facility to automatically flag the account as a “New A / C” for a period

Critical

26 Provide a facility to automatically flag the account status based on account transactions, and below parameters as required by the bank

Critical

227

For first "xx" months from the account opening date the account status should be "NEW"

Critical

28

After "xx" months the account is in normal operations the account status should be "OPERATIVE"

Critical

of 274


29

Within "xxx" period not a single transaction done in the account (Considering all the transactions / operations excluding Cheque Return & charges debited) the account status should be "INOPERATIVE"

Critical

30System to send notifications to customers in inoperative category

Critical

31

Within "xxx" period after account become inoperative not a single transaction done in the account. (Considering all the transactions / operations excluding Cheque Return & charges debited) the account status should be "DORMANT"

Critical

32 Provide a facility to automatically debit the charges based on the account status as per the bank require configurations

Critical

33 Provide capability to group the various accounts of a corporate / individuals based on predefined parameters, e.g. common first account-holder for tax deduction at source.

Critical

34 Provide facility for applying concessions in charges to specific account / group of accounts.

Critical

35 System to support parameterized interest payments for different types of accounts in respect of period and rate of interest and recovery of excess interest already paid in case the deposit does not run for a minimum period.

Critical

36 System to support payment of interest at intervals e.g. Quarterly while the fixed deposit is still running even if for a year or not – drop down to choose

Critical

37 Fixed Deposit under lien to continue in books unless the lien is removed. System to disallow maturity

Critical

38 System to support accrual of interest with or without application at parametrized intervals on authorization. ( Rate of interest / Effective date )

Critical

39 Support mode of payment of interest like cash / electronic clearing / transfer / other remittance mode etc.

Critical

40 Support payment of proceeds by Pay Order / credit to designated account / conversion fully or partly to a fresh Term Deposit / Demand Draft etc. Payment by cash restricted to parameterized amount at product-level.

Critical

of 274


41 Closed accounts should be allowed only for enquiry and not for transactions.

Critical

442

In case of subsequent substitution / cancellation, original name should be retained with date of change as history and exception report to be generated.

Critical

43Support flagging of matured but unpaid term deposits as overdue and include the balances as demand deposits in General Ledger Balances.

Critical

44 Provide facility for storing, specific no of years, old account numbers (from earlier legacy system). To support enquiry based on old account no.

Critical

45 System to generate unique receipt numbers Critical46 Should have facility to generate the exceptional

report in case of duplicate receipt number for different customer.

Critical

47 Support blocking either credits or debits or both in any account.

Critical

48 Support for enquiry of transactions based on Amount (less than, in, more than a range), Customer No. / Account No./ Account / Transaction / Date / Channel type etc.

Critical

49 Provide facility for classification of accounts based on customer type / sub-type.

Critical

50 As of Date (Value dating) transaction Critical5

51Allow ‘value-dating’ all financial input posted Critical

52Provide automated process for re-calculating interest for an account taking into consideration effective balances after As Of Date( value dating)

Critical

53When authorizing a fixed deposit created, the system should allow the authorizer to view the interest rate at the same window

Critical

554

Signature capture to be allowed only at the domicile branch

Critical

Accounts55 Upon final authorization, system to support

immediate printing of the cheque book for current accounts for all currencies

Critical

56 Cheque Book facility:(Y/N) Critical57 if YES accept cheque from and to numbers. Critical58 Provide facility to issue counter cheques to

customers Critical

of 274


59 Support recording details of the cheque series & numbers of cheque leaves issued to customer for each account separately. Cheque register

Critical

60 Posting of cheques to be validated. Cheque Number to be within the range of cheques already issued and not paid.

Critical

61 Provide facility to provide loose cheques to customer for CC/ Current / OD and have field to record the cheques in the system before issuance

Critical

62 Provide facility for on-line checking of the amount of each cheque against the actual balance in the account at the time of data-entry, including during batch entry of multiple cheques.

Critical

63 Provide facility for rejection / override message in case the cheque amount exceeds the available balance in the account.

Critical

64 Support recovery of charges for issuing of cheque books & also permit exceptions

Critical

65 Allow setting of Account Parameters as per banks requirement

Critical

66 For Non-overdraft accounts, account balance cannot go negative. For exceptional cases, an alert/message should be displayed and transaction should be authorized by appropriate authority.

Critical

67 System to include a field to capture reason where a charge in an account has been waived

Critical

68 While posting debit transaction with cheque, the system must verify for the following but not limited to:

STOP PAYMENT instructions CriticalEar Marking flag, if any, on the balance,

if there is any.Critical

Already-paid cheques (same cheque cannot be paid once again).

Critical

Cheque number verification Critical

Postdated and Back dated cheques should not be allowed

Critical

A savings account should not overdraw or go below minimum balance

Critical

69 Search fee and cheque book charges for all current account types to be recovered automatically upon completion of account opening. Where there are no funds on the

Critical

of 274


account an exception report should be generated and the charge should continue to hover and be recovered once funds are available

70 Restricted operations:71 Allow for setting of account parameter

including but not limited to:7 Debits not allowed Critical

Credits not allowed CriticalDebit / credit not allowed Critical

72Allow earmarking with certain amount

and the reasonCritical

73 Provide facility for revocation of such restriction under authorization.

Critical

74 Provide facility to post BULK CREDIT entries from the electronic format for e.g. STAFF / Corporate clients, ECS Credit / Debit etc.

Critical

75 STOP PAYMENT instruction: -

76Provide facility for rejection of Stop Payment instruction if corresponding cheque number is already marked as paid.

Critical

77Provide facility for flagging of the relevant cheque when a Stop Payment instruction is entered.

Critical

78 Provide facility for recovery of charge @ KES.”x” per instruction and printing of debit advice based on amount & no. of leaves. (Bank will provide "x" parameter value at the time of configuration. The parameter set up must be flexible enough and can be changed as and when required as per the Bank's requirement by the Bank's application support staff.)

Critical

79Provide facility for revocation of Stop Payment instruction under authorisation.

Critical

80 Dishonored Cheques/ ECS :

81Provide facility for tracking dishonored

cheques / ECS in any accountCritical

82 Provide facility for recovery of charge @ KES.”x” per additional withdrawal over permissible number “n” per month. (Bank will provide "x" and "n" parameter values at the time of configuration. The parameter set up must be flexible enough and can be changed as an when required as per the Bank's requirement by the Bank's application support staff.)

Critical

83 Tracking balance falling below the minimum Critical

of 274


balance. When account has gone below minimum balance, system to have capacity to levy a charge

84 Recovery of charge @ KES.”x” per such occasion. (Bank provide "x" parameter value at the time of configuration. The parameter set up must be flexible enough and can be changed as an when required as per the Bank's requirement by the Bank's application support staff.)

Critical

85 Provide facility for override of the recovery of charge under authorization to be captured in exception report.

Critical

86 Allow a facility to create a current account with a predefined overdraft facility in case the amount in the savings account goes below the prescribed limit or is overdrawn.

Critical

87 Minimum Balance requirements:Allow defining of minimum balance based on the following but not limited to:

Critical

9 Customer type e.g. Staff, Pensioner, Individual, Firms and Companies etc.

Critical

9 Account type e.g. SB, CA. Critical0 Cheque facility available (SB account) Critical9 Cheque facility not available (SB account) Critical9 ATM Facility available Critical

Population category of the branch like Metropolitan, Urban, Semi-Urban, Zone and Rural, and / or location such as District Head Quarter, State Capital etc.

Nice to Have

188

Enable system to levy charges in case of default on instance-basis / period-basis.

Critical

89

Minimum Balance Charges must be levied before end of day is executed. If the balance in the account is not sufficient to charge Minimum Balance charges, a record must be kept and charges are to be recovered automatically whenever sufficient balance becomes available in the account.

Critical

Term Deposits90 Support flagging of matured but unpaid term

deposits as overdue and include the balances as demand deposits in General Ledger.

Critical

91 Capture deposit-scheme specific parameters e.g. minimum / maximum period and period and amount of deposit, rate / mode of payment of interest, maturity value etc.

Critical

of 274


92 Upon final authorization, system to support immediate printing of the deposit receipt

Critical

93 Should have facility for generating report log TD receipt printing done & pending for the day

Critical

94 Provide facility for generation of notices to be sent to customers in case of overdue installments for more than parameterized period for RD

Nice to Have

95 Provide facility for conversion of full or part of one type of deposit into another with facility of waiver of penal interest on premature payment of a term deposit converted into another term deposit.

Critical

96 Support maintenance of:CFD Interest Accrual Account for holding

CFD quarterly accruals.Critical

Interest Paid CFD Account for making payments of interest on CFD for current quarter.

Critical

Interest Accrued and Payable-Non-CFD for holding quarterly accruals in respect of other term deposits. The balance to be credited to Interest Paid-Non CFD on the same day

Critical

Interest Paid on TD for making payments of interest on TD for current quarter.

Critical

In case of premature payment Provide facility for reversal of recoverable interest from CFD account to CFD interest account.

Critical

Closure on maturity – Regular RD (RD is treated as regular on receiving all installments on or before due date and interest payment is for pre fixed maturity value arrived based on quarterly compounding of monthly installments

Critical

Closure on Maturity – Regular but Installment with default (In this case all installment received but some or all installments with delay – provision to pay full maturity value and deduct penalty for delayed installments from proceeds of maturity value or to pay interest on monthly product basis on half yearly the compounding together with collecting penalty.

Critical

Closure on Maturity – Irregular RD (If all installments are not received, it is treated as Irregular RD) – In such cases closure to pay interest on monthly product basis on half yearly the compounding together with

Critical

of 274


collecting penalty.97 Provide facility for capture of deposit-scheme

specific norms (parameterized) such as minimum period (e.g. x days for Fixed Deposits), maximum period (e.g. y months for all Term Deposits) as also other details such as period of deposit, amount of deposit, payment of interest and maturity value etc. where x and y are parameters.

Critical

98 System to support loan facility against deposit accounts with linking & lien marking with parameters like rate of interest, margin, purpose due date, installment etc. System to support lien marking for deposit accounts

Critical

99 Overdue Term deposits100

To support renewal of Overdue Term Deposits for overdue period

Critical

101

Should have facility for generating letters at predefined dates for renewal of Term Deposits.

Critical

102

Should have facility for generating letters of WHT/TDS

Critical

Standing Instruction103

Periodical Standing Instructions to be executed at the time at Start of day / End of day

Critical

104

Provide flexibility for setting up and processing any type of standing instructions as and when required with different parameters including but not limited to:

Critical

105

Fixed Amount Fixed Period / Variable amount / Variable amount with limit / Variable frequency / Event driven / Maintenance of balance

Critical

106

Provide facility for generation of Report on:

1 Standing Instructions executed, and Critical1 Standing Instructions failed in execution. Critical

107

Provide a facility to allow carry forward of the standing instructions, for some user-definable period, till the condition for processing the standing instruction is met or number of attempts made

Critical

108

For failed SI due to insufficient funds, the credit in the account should be made available for withdrawal and the full SI to be recovered when the sufficient credit is available to recover the SI.

Critical

109

Alert be generated for failed STO Critical

of 274


FDR Account110

System to have capacity to close Fixed Deposit account

Critical

Accounts With Zero Balances111

Account be closed within 'x' period of time Critical

Account Transfers112

System to allow account transfers from one branch to another

Critical

113

System to allow account number portability from one branch to another

Critical

Foreign currency cheques114

System to issue both local currency and foreign currency cheques and marking them in the system

Critical

Customer profitability115

Ability to generate profitability per customer Critical

Authorization116

Alert for transactions not authorized in the system beyond X amount of time

Critical

Signatory and mandate details117

System to allow for more signatories/signatures and photos to be displayed under joint or corporate client. The number of signatories should be as many as allowed under the company Act

Critical

118

System to allow only for scanning of signatures without having to crop the same. Cropping of signatures changes the quality of the images

Critical

119

When keying in the mandate, the system should provide for input of special/exceptional Mandate requirements e.g. introduction of Powers of Attorney or Agents

Critical

120

Account opening report to have an option of separating loans from deposit accounts as well as have ability to sort using diverse parameters

Critical

121

The AML watch list to be included in the system to allow for pop ups and alerts when transacting or account opening

Critical

of 274


1.3.11 Clearing & Settlement Common Requirements Requirements



1 Pro142vide facility for following categories of clearing:

Critical

2 MICR clearing Critical3 Non MICR clearing Critical4 High value clearing Critical5 National clearing Critical6 Cheque truncation-Image Based Clearing. Critical7 Electronic Clearing Service Critical8 Outstation clearing Critical9 System should support various types of

clearing under each of the above category:Critical

10 Inward clearing Critical11 Outward clearing Critical12 Clearing returns Critical13 Provide facility to capture Bank master - details

containing particulars of banks / branches participating in clearing at each center.

Critical

14 Provide facility to capture the following information for all categories of clearing, but not limited to:

Critical

15 Customer ID Critical16 Customer's account type and number Critical17 Customer name/ Joint names Critical18 Cheque number / Cheque date Critical19 City code Critical20 Branch code Critical21 Bank code Critical23 Type of instrument Critical24 Amount Critical25 Account number of issuing party Critical26 MICR code Critical27 Narration Critical28 Provide facility for capture of cheque image for

enabling capacity for cheque truncation.Critical

29 To Provide facility for more than one clearing per day in each of the above categories

Critical

of 274


30 There may be more than one Clearing zone in most of the Centers:

Critical

31 Customer accounts to be credited on a pre-defined working day

Critical

32 Customer may be allowed to utilize the funds after a pre-defined number of days as per the clearing norms at the center.

Critical

33 The system should provide for flexibility to allow the user to define these accounts and the amount to be credited to the accounts on the instruments being cleared.

Critical

34 Provide facility for on line posting, as well as batch posting. System should have measures for double-checking of batches posted to ensure correctness.

Critical

35 Provide facility for receipt of clearing data from the branches to service branches 'on line'.

Critical

36 Provide facility to handle of multiple cheques deposited under one Pay-in slip.

Critical

37 Provide facility to credit to multiple accounts from one cheque.

Critical

38 Provide facility for automatic transfer of net balance to Clearing account

Critical

39 Give daily status of net amount ‘due to’ or ‘due by' clearing house

Critical

40 Provide facility to upload external statement of clearing house for reconciliation.

Critical

41 To provide for handling of electronic funds transfers

Critical

42 Provide facility to begin and end of clearing cycle so that no instruments can be included after the end of the clearing cycle.

Critical

43 Allow the user to define the period by which credit has to be passed on to the branches for different types of clearing.

Critical

44 Provide facility for automatic transfer of net balance to clearing account / local clearing after proper authorisation

Critical

45 To provide facility for Critical46 Separate schedule Critical47 Separate code numbers and passing of contra

vouchersCritical

Outward clearing48 Support generation of list of instruments bank

wise (for inter-bank) and branch wise (for intra-bank) for each clearing (formats of the lists to

Critical

of 274


be defined by the user ).49 Allow defining the following dates: Critical50 Clearing data entry date, credit date and

clearing clear date:Critical

51 Posted date Critical52 Cleared date: funds are cleared and available

to the customer provided for crediting the entries in the account based on these dates and mark the balances as cleared etc.

Critical

53 Provide facility for marking for returned cheques and posting them automatically to the customer’s accounts along with charges.

Critical

54 Provide facility to charge interest only on available/clear balance in case of cheque returns and not the total balance from data entry date.

Critical

55 Provide flexibility to release / hold uncleared effects of the presented instruments at the option of the bank in the event of any bank not participating in clearing etc.

Critical

56 Provide facility for postponement of uncleared funds and not advancement in relation to pre-defined days / period.

Critical

57 Provide facility to user defined of clearing batch parameters at Bank and specific Branch level.

Critical

58 To provide for authorization of all entries. Critical59 Support automatic credit to customer’s

accounts for cheques that have been cleared.Critical

60 Ability to automatically reverse the entries in customer accounts and contra entries for cheques that have been returned unpaid.

Critical

61 Ability to debit the customer's account for recovery of the charges for unpaid cheques automatically.

Critical

62 Support re-present option for those cheques, which have been returned unpaid.

Critical

63 In case of multiple cheque deposited in single slip, there should be facility to enter cheque details separately.

Critical

64 In case of multiple cheque deposited in single slip, there should be facility to mark cheque status separately ( Delayed / returned /Cleared)

Critical

65 In case of multiple cheque deposited in single slip, there should be facility to pass credit entry in respective account for the cheque status marked as Cleared.

Critical

of 274


Inward clearing66 Support following functionality for all

categories of Inward clearing:Critical

67 Provide facility for validation of cheque number / date and stop payment instructions before the cheque is cleared for payment.

Critical

68 A cheque number once paid should not be allowed to be presented again for payment

Critical

69 In case of a batch posting, system should reduce the available balance dynamically from the Customer's account after every cheque.

Critical

70 Support generation of auto referral to the authorized persons in case of insufficient funds.

Critical

71 To generate voucher and Cheque Return Advice in respect of returned cheques containing the following details:

Critical

72 Service charges to be automatically debited to the customer's account.

Critical

73 Reason for return. Critical74 Cheque details. Critical75 Name of drawee / Presenting banker should be

mentioned on the return memoCritical

76 Provide facility to recover outstanding charges by debiting customer account and crediting respective charges account whenever the there is sufficient balance available.

Critical

77 To generate responding entries in respect of inward clearing.

Critical

78 To provide for all posting of cheques, account wise individually.

Critical

79 To provide for scrutiny of list and confirmation of cheques to be returned.

Critical

80 Provide facility for authorization of remaining entries excluding the deletion entries in respect of returned instruments.

Critical

81 Provide facility for configuring the parking account for inward clearing

Critical

82 Enable data upload of inward items to inward clearing based on the data received in soft copy from Clearing house or Input the data generated by the MICR reader at the service branch and also to modify cheque date and payee's name.

Critical

Remittances83 Remittance transactions involves funds transfer

which will include and is not restricted to Critical

of 274


Demand draft, Pay Order, Bank Order, Electronic Fund Transfer, Mail Transfer, Telegraphic Transfer (in local and foreign Currency), RTGS, NEFT. This includes inward and outward remittance.

84 Allow remittance for customers and non-customers

Critical

85 Provide creation of transaction type which include specific multi-purpose products like:

Critical

86 Demand Draft Critical87 Pay Order Critical88 Direct transfer of funds Critical89 Telegraphic Transfers Critical90 Electronic fund transfers (NEFT) Critical91 RTGS Critical92 Enable creation of a daily rate master for

definition of foreign currency conversion rates to be applied for retail transactions.

Critical

93 Provide maintenance of currency master history for user defined periods

Critical

94 Allow overriding default currency rates. Such overriding should be captured in exception report

Critical

95 Enable waiver / reduction of charges on specific transactions for any account with appropriate approval and inclusion in exception report

Critical

96 Enable online approval of transaction by auto referral to appropriate authority

Critical

97 Allow definition of maximum limit for cash transaction for each product for both issue and payment.

Critical

98 Enable processing of transactions in both on line and batch mode. Transaction entry should be possible in single input mode and bulk import of data.

Critical

99 Provide facility for issuance of DD / PO / EFT / TT against the following mode of payments-cash, debiting account of the customer at the same branch, debiting account of the customer at another branch (should support multi branch transactions). Internal debit note / voucher, bill negotiated / discounted and debiting third party account with proper authorisation.

Critical

100

Provide printing of instruments in user definable formats

Critical

101

Provide printing of instruments in preprinted Continuous Stationery

Critical

of 274


102

Provide maintenance of stock of instruments and issue of books / running stationery there against.

Critical

103

System should have facility to automatically pick up the next DD / PO instrument number from the stock

Critical

104

Provide input for name of the payee, amount and date.

Critical

105

Provide branch code and branch name in a drop down list box

Critical

106

Provide Drawee branch Name and Code in a drop down list box

Critical

107

Provide facility for account status at the time of posting of Voucher

Critical

108

Provide instant printing of DD / Pay Order / Bank Order.

Critical

109

Enable defining Service charges (parameters) Critical

110

Enable passing of Accounting entries / advice as per bank’s requirements

Critical

111

Provide facility for using one cheque for multiple remittances

Critical

112

Provide facility for Multiple Debits and Single/ Multiple Remittances

Critical

113

Facility for receipt and authorizing payment which will include but not restricted to:

Critical

114

Batch receipt of messages Critical

115

Validation of instruments noted for caution instruments reported lost (stop payments)

Critical

116

Validation for date of instrument (period to be parameterized)

Critical

117

Validation for duplicate issued Critical

118

Validation for instruments already paid Critical

119

Provide facility for payment on Instrument / instructions in case cancellation in the modes which include but not restricted to

Critical

120

Crediting account of customer at the same branch or another Branch

Critical

121

Issue of another instrument / remittance instructions like Bankers cheque

Critical

122

Crediting third party accounts and Internal accounts

Critical

12 Provide facility for cancellation of instruments Critical

of 274


3 against user determined conditions for Cancellation. Facility to cancel an instrument and credit customers’ accounts with proceeds with recovery of charges for cancellation.

124

Provide facility for validation of instrument numbers against stop payment instruction before actual pay out of the amount

Critical

125

Support validation of instruments before payment that will ensure that instrument / remittance are not paid twice or instruments cancelled / reported as lost are not honored. The validation will include (a) Instruments noted for caution. (b) Instruments reported as lost. (c) Instrument remittances paid. (d) Intra office suspense account.

Critical

126

Support issuance of duplicate / revalidation by the issuing branch. Period for allowing revalidation to be user definable with recovery of charges for the same.

Critical

127

Provide facility for transfer of outstanding instruments beyond the cutoff date / period to Head Office with related IBCN entries and user specific details

Critical

128

Allow facility to record pre-requisite conditions for duplicate issue. Validation against these conditions will include but is not restricted to:

Critical

129

Original issue reference Critical

130

Reported lost Critical

131

Stop instructions Critical

132

Duplicate already issued Critical

133

Receipt of nonpayment advice Critical

134

Receipt of indemnity bond Critical

135

Provide facility for referencing the original instrument / remittance while issuing a duplicate instruments / remittance

Critical

136

Provide facility for cancellation of DD(including cash DD) / Remittance on the date of issue after authorization.

Critical

137

Provide facility for cancellation of DD (including cash DD) / Remittance on subsequent dates

Critical

13 Provide facility for generation of accounting Critical

of 274


8 entries139

Ability to automatically issue instructions for canceling the validity of the original instruments on issuance of duplicate

Critical

140

Provide facility for generation of revalidated DD and remittance

Critical

141

Provide facility for generating the advice for duplicate and revalidation of DD / remittance

Critical

142

Provide facility for creation of differential service charge structure which should consider parameters like:

Critical

143

Customer Critical

144

Product (DD / MT / TT Issued / TT Discounted etc.)

Critical

145

Duplicate issuance Critical

146

Cancellation charges Critical

147

Amount Critical

148

Slab or tier charges Critical

149

Postal / Telegraph / Telecom charges Critical

150

Provide facility for status for specific instrument / remittance which may include but is not restricted to:

Critical

151

Unique reference number Critical

152

Transaction type Critical

153

Date Critical

154

Customer Critical

155

Branch Critical

156

Customer identification number Critical

157

Combination of any two or more of the above Critical

158

Do not allow modification of DD / Remittance once it is printed

Critical

159

Allow entries to be authorized by the officials Critical

160

Allow printing of DD / PO only on authorisation Critical

of 274


IBC/OBC (Bills)General requirements

161

Provide facility for:

162

Defining work flow requirements for authorizations based on hierarchy levels and amounts for different types of transactions.

Critical

163

Unique reference number generated for each transaction should be a combination based on branch ID, type of transaction, currency and Serial Number.

Critical

164

To provide user with appropriate messages with the solution to remedy any incorrect entries made.

Critical

165

To provide for creation of multi-level authorisation for the purpose of committing the transactions

Critical

166

To prompt the user before any transaction is completed

Critical

167

Not to allow the processing of the transaction where either credits or debits or both are blocked in any account.

Critical

168

To process all types of transactions and to provide for all types of facility to draw up the list of documents missing when the user is processing the transaction.

Critical

169

In case of any discrepancies during the validation of documents against the check list, the same should be forwarded to the next approving authority as per the work flow defined by the bank

Critical

170

To enable creation of new transaction by copying an existing transaction with the facility to change all fields

Critical

171

Provide facility for linking /passing entries of all transactions to day book, subsidiary and General Ledger.

Critical

172

Enable creation of methods of calculation of commission, interest and other charges based on:

Critical

173

Product category / sub category Critical

174

Account Status Critical

175

Usance period / validity period Critical

of 274


176

Returned instruments, Critical

177

Collecting Bank / Agency (sharing of commission etc.)

Critical

178

Amount Critical

179

Provide facility for charging of commission upfront or from drawee or on realization.

Critical

180

Provide facility to maintain register for the balance amount of commission, recovery of balance of commission along with interest

Critical

181

To enable user to manually overwrite the amount of commission and / or interest amount, any additional amounts automatically calculated by the system. Any such overwrite should be captured in the exception report.

Critical

182

To provide for verification against the limits available before accepting the application for purchase of instruments for processing and give appropriate messages / error messages. For this purpose the system should have access to

Critical

183

Sanctioned limits Critical

184

Limits utilized Critical

185

Limits available Critical

186

To ensure updating of customer limits on real time based on every new transaction, retirement or close out.

Critical

187

To enable picking up of customer information for all transaction from the data base

Critical

188

To provide capability to search a transaction based on various fields or a combination of fields such as

Critical

189

Customer ID Critical

190

Date of transaction / range of dates Critical

191

Reference number Critical

192

Type of transaction Critical

193

Amounts Critical

194

Selection criteria defined by the user Critical

of 274


195

To enable customization of new products as and when introduced by the bank

Critical

196

Provide facility to auto generate the contra entries upon the bill transaction is entered.

Critical

Outward bills /cheque for collection197

Provide facility for Critical

198

Our reference number Critical

199

Date of lodgment Critical

200

Name of party / account number Critical

201

Cheque / DD number with date Critical

202

Drawn on bank / branch with city Critical

203

Amount of cheque / instrument Critical

204

Drawee account no. and name Critical

205

Sent for collection to whom like service branch, our branch, other bank with address

Critical

206

Commission, postage Critical

207

Returned instruments with reasons thereof Critical

208

Provide facility for a separate head in P&L subsidiary “ Interest paid account on delayed collection”

Critical

209

Waiver of comm. From staff & quasi govt. bodies

Critical

210

Provide facility for printing Critical

211

Passing of contra voucher Critical

212

Reminders for unrealized instruments beyond specified number of days

Critical

Realization of cheque sent for Collection213

Provide facility for payment of interest for delayed collection of cheques beyond specified period in respect of state capitals and other places as per Goiporia Committee recommendations - specified period to be parameterized separately for state capital and other places.

Critical

214

Provide facility for realization register with the following details

Critical

of 274


215

Date Critical

216

Our number Critical

217

Amount realized and amount credited Critical

218

Our commission Critical

219

Other bank’s charges Critical

220

Postages Critical

221

Number of days taken for realization Critical

222

Interest for delayed period if any Critical

223

Sharing of commission 50% in case of instruments sent to other banks

Critical

224

Returned Instruments Critical

225

Generate control / de-control voucher and advices for the party

Critical

226

Transfer from Collection to purchase Critical

227

To provide for authorisation - Critical

228

Details of credit to be given Critical

229

Generate de-control vouchers Critical

Outward Bills for Collection Register230

To provide for collection register with the following details

Critical

231

Date of lodgment Critical

232

Our bill number Critical

233


234

Amount Critical

235

Drawee details Critical

236

Details of usance / due date Critical

237

Our commission and collecting Bank’s charges if any

Critical

238

Postage Critical

of 274


239

Interest charges / recovered as per drawers instructions

Critical

240

Details of documents enclosed like Invoice, Lorry / Railway Receipt / Airway Bill etc. with date / number / amount

Critical

241

Instruction to party (regarding commission, C form, overdue interest and disposal instructions)

Critical

242

To whom sent for collection Critical

243

Details of bill returned Critical

244

To generate-

245

Register for a given period Critical

246

Covering schedule along with necessary instructions.

Critical

247

Control vouchers Critical

248

Realisation of billsTo provide for register with following details

Critical

249

Bill number Critical

250


251

Date of realization Critical

252


253

Other Bank’s charges, our commission / postages

Critical

254

To search the bill from the bill number, date of lodgment and original bill amount

Critical

255

To generate de-control vouchers Critical

Inward cheques and bills received for collection

256

To provide for register with the following details:

Critical

257

Our number Critical

258

Date Critical

259

Their number Critical

260

Name of our customer / drawee Critical

of 274


261

Bill number / cheque number & date (date to be validated in case of cheque)

Critical

262

Amount Critical

263

From whom received with address- (a) From Branches (b) From others – the contra entries in respect of these two categories are to be shown separately in GL

Critical

264

Their commission and interest Critical

265

Our commission and postage Critical

266

Details of documents enclosed like Invoice, Lorry / Railway Receipt, Airway Bill etc. with date / number / amount / Transport Operator (validation of date of LR / RR with provision to override with exception report)

Critical

267

Due date Critical

268

To generate contra vouchers Critical

Realization of Inward bills269

To generate register with following details Critical

270

Date Critical

271

Name of customer / drawer / drawee Critical

272

Branch Critical

273

Amount of bill Critical

274

Amount remitted Critical

275

Our commission including charges on post parcels if any and postage / their charges

Critical

276

Interest details including number of days and rate of interest.

Critical

277

To generate realization register and contra voucher and remittance of proceeds as per instructions of drawer / bank. System should prepare DD in case of cheques / bills received other than from our own branches. In case of our own branches system should prepare IBCN. The amount to be remitted should be based on the instructions of the drawer.

Critical

ECS & NEFTECS

of 274


278

Master program to maintain Service Provider Code (Mandate details-Service Provider Code and Address)

Critical

279

Provision for handling ECS for Weekly Holiday Branches.

Critical

280

Updation of records by individual branches (provision to be made after the branch sign off)

Critical

281

Provision for Stopping the Mandates of account wise.

Critical

282

Charges have to be taken care for rejection with Insufficient Funds.

Critical

283

Report for viewing authorized ECS records, status for a day, ECS data uploaded detail, debit mandate details

Critical

284

Provide facility to interface with sms banking module to send sms for 'insufficient funds'

Critical

285

Provide facility to auto recover the ECS charges and should provide proper bifurcation of charges.

Critical

NEFT MODULE286

Program to maintain NEFT Batches Critical

287

Provide facility for mandatory validations while creating the NEFT batch file and should not allowed to proceed further without corrections.Data Entry Special CharactersTime slot

Critical

288

Provide facility to populate customer information when debit account number is entered with the facility to auto validation for data quality and edit the populated information for manually processing the NEFT transaction.

Critical

289

Provide facility to create separate batch files for processing net banking NEFT transactions and manual NEFT transactions.

Critical

290

Program for entry and authorization of transaction at branch level within the available Batch for transaction

Critical

291

For NEFT transaction, On receipt of inward remittances from API the accounts has to be credited to the beneficiary account in case of Customer Payment and respective General ledger in case of Inter Bank payments.

Critical

292

For NEFT transaction, Provide facility to check the rejection messages and upon changes & authorisation, amount to be credited to the beneficiary account in case of Customer Payment and respective General ledger in case

Critical

of 274


of Inter Bank payments.293

Provide facility to maintain Rejection parameter master for NEFT transactions.

Critical

294

Add new branches for NEFT on opening of new branches

Critical

295

Query and Reports to be provided to branches for smooth running of NEFT program

Critical

296

Provide facility to view the batch file processing branch wise (all or specific) status as and when required as per bank's parameters.

Critical

297

Provide facility for processing the high value NEFT transaction with proper authorisation of treasury dept.

Critical

298

Provide a facility for Origination of Direct Debits

Critical

299 System to have a direct debit module

Critical

Remittances300

System to support multicurrency transactions for local RTGSs and foreign TTs processed from customer accounts

Critical

301

System to support multicurrency transactions for local RTGSs and foreign TTs processed from bank GLs

Critical

302

Transactions processed by centralized units to collect commissions and fees chargeable to the customer's domiciled branch

Critical

303

Unique reference numbers generated for each transaction based on the defined parameters

Critical

304

System to generate relevant message types for remittances processed and upload to swift through STP

Critical

305

System to generate MT199 for all incoming RTGSs and TTs for automatic updating of the SWIFT Global Tracker

Critical

306

Provide a reconciliation modules for all the nostro accounts utilised in settlement

Critical

307

System to capture cross-currency transactions without converting to KES first

Critical

308

Purpose of payment to be captured Critical

309

System be able to capture customer forward deals and attach to relevant transactions

Critical

310

Interest accrue matches with market calculator Critical

311

Daily revaluation updates the position with relevant income/loss

Critical

of 274


312

Should be able to capture customer/bank treasury bonds/bills

Critical

1.3.12 Teller Operations# Common Requirements Requirements



1 Provide facility to define functions / operations, which can be performed by each teller / cashier:

Critical

2 Support limits for tellers based on:3 Type of transactions Critical4 Amount of transactions Critical5 Provide facility for the teller to view customer’s

signature at account level on screen for verification and account operating instructions.

Critical

6 Provide teller functions in local currency as well as foreign currencies.

Critical

7 Provide a facility to record ‘quantity’ of currency denominations for each transaction including for cash removal from safe deposit vault and depositing into safe deposit vault.

Critical

8 Support exchange of currency, denomination-wise, between two or more tellers / cashiers and head cashier.

Critical

9 Support tendering of change to customer, denomination-wise.

Critical

10 Support receipt of cash for issue of demand drafts, pay orders, bank orders, traveler’s cheques etc.

Critical

11 Provide for issue / printing of drafts, pay orders, bank orders etc. by the teller, after authorisation.

Critical

12 Allow for waiver of certain charges (for e.g. Overriding service charges), based on user- defined parameters). Such waivers / overrides must be captured in exception report.

Critical

13 Allow cash withdrawal across branches and validate for cheque number, cheque date, stop payments in case cheques are used for withdrawals, with facility to auto debit charges

Critical

14 Provide facility to enter transaction (e.g. Cheques) in batch mode or single transaction mode.

Critical

of 274


15 Support input of transactions affecting internal accounts like Cash-Remittance-in-Transit, Working Expenses, Sundry Debtors, Rent Payable etc.

Critical

16 Allow authorization of inputs, when done for a batch, only when the batch is balanced. Support for unbalanced batches based on entry / partial updation etc. in case of problems during entry / updation.

Critical

17 Allow marking of transactions as reversed (rather than passing contra entry to cancel the erroneous entry) which should be captured in exception report.

Critical

18 Support functionality to allow access to the above-mentioned facility only to predefined users

Critical

19 Support facility to authorize multiple transactions using a single function with overrides if any for transactions. Any overrides should be captured in exception report.

Critical

Cashier / Teller Operations20 Cashier to be able to query / call on terminal-

only cash transactions already authorized for payment, pay cash, enter denominations and flag transaction as “cash paid”.

Critical

21 Authorized users to monitor cash limits and receive alerts.

Critical

22 Tellers holding cash above their limit not to be allowed to proceed until they pay excess cash held

Critical

23 Provide for enquiring on status of transactions, whether entered, already authorized etc based on amount, account number and type etc.

Critical

24 Generation of cash scrolls, payment and receipt for end-of-day handing over of cash to Chief / Head cashier / Cashier in Charge.

Critical

25 Provide a facility for cash deposit to all permitted account types for credit of accounts across all CBS branches.(Subject to user defined changes over and above predefined limit of cash deposit.)

Critical

26 Support cheque deposit (and their classification for the purpose of printing of statements and monitoring) of the following types:

Critical

27 Cheque drawn on another customer of same branch.

Critical

28 Cheque drawn on another customer of same bank but different branch.

Critical

of 274


29 Cheque drawn on another customer of another bank in the same city.

Critical

30 Cheque drawn on another customer of another bank in different cities.

Critical

31 No use of withdrawal slips or vouchers for withdrawals form current accounts

Critical

32 Enable cash withdrawal from specified account type using withdrawal slips / vouchers at only home branch, subject to exceptions with proper authorisation. In case of exceptions charges can be levied at bank's discretion and generate exceptional transaction report.

Critical

33 Passbook layouts and transactions should be user-definable

Critical

34 In case of exceptions charges can be levied at bank's discretion and generate exceptional transaction report at the transacting branch

Critical

35 Support recording currency-wise deposits and withdrawals of foreign currency, denomination-wise.

Critical

36 Should be able to reflect position of foreign currency held, currency-wise and denomination-wise.

Critical

37 There should be a provision for storing a token numbers for each cash payment / cash receipt for customer transactions

Critical

38 Ability for individual teller to close off their till without affecting the other tellers under authorization

Critical

Chief / Head Cashier Operations39 Support facility to record open / close status of

vault Critical

40 Provide for vault to teller and teller to vault transaction, denomination wise

Critical

41 Enable recording of open / close status of each teller’s till.

Critical

42 Allow authorizing of the tills only after they have been balanced with physical cash.

Critical

43 Support automatic verification of Cash-on-Hand position (as per General Ledger) at end-of-day (EOD) with EOD cash inventory position and pop-up message in case of discrepancy. (EOD to be allowed to go ahead only if there is no difference in amount and denomination).

Critical

44 Should allow user for a teller function and a cashier function optionally.

Critical

of 274


45 Cashier should be able to receive / pay amounts with authorizations. At least two levels of authorizations must be provided for.

Critical

46 There should be a provision for storing a token numbers for each cash payment / cash receipt for vault transactions

Critical

47 Provide facility to monitor branch wise cash retention limit with excess cash alert at branch and branch wise summarized alert of all branches to head office.

Critical

48 Provide facility to record cash remittance register(Inward /outward)

Critical

49 Allow the Cash deposit module to be configurable to enable the bank define specific cash deposit modules for specific clients who request for capturing of specific information during cash deposit. Reports to be in various file formats i.e csv,pdf,xml to allow for file sharing/upload eg Schools, Water companies, KRA etc

Critical

50 System to support a cash scroll that captures a debit and credit

Critical

51 System to complete Teller transactions to enable printing of cash deposit or withdrawal receipt

Critical

52 System to have capacity to integrate with biometric system

Critical

53 System be scalable to include fields for capturing additional information

Critical

54 System to provide Teller with atleast last 10 transactions for all debits and credits

Critical

55 System to have inbuilt transaction Codes Critical

56 Teller module to support cross currency transactions

Critical

57 Automated cash withdrawal/deposit description (Drop down) but with also additional fields for additional narration

Critical

58 Provide ability to mark limits for different customers which will pop up when the Teller is transacting at the counter

Critical

59 Ability to print teller receipts after completion of transactions

Critical

60 Provide a field to capture Name of person depositing or withdrawing cash, their ID Number and Telephone Number

Critical

61 Alert for transactions not authorised in the system beyond x amount of time

Critical

of 274


62 System to have pop-ups to alert the teller when the account transacting exceeds the daily allowable deposit limit for declaration as per Central Bank of Kenya requirements on AML

Critical

63 Automate cheque deposits and print a slip for the same

Critical

64 System to pop up accounts with withdrawal restrictions under the mandate when the teller is performing the withdrawal process

Critical

65 The system should allow Teller cash summary to be printed in a format that cannot be edited

Critical

66 System should give offline balances whenever there is a downtime this will assist Tellers continue processing requests

Critical

1.3.13 Trade Finance Requirements# Cheque / Draft purchase Requirements



1 To provide for register with the following details for cheque /Draft purchase

Critical

2 Date Critical3 Our number Critical4 Name of party / account number Critical5 Staff / non-staff Critical6 Amount of Cheque and amount credited Critical7 Cheque number and date (date to be validated) Critical8 Drawee bank / branch Critical9 To whom sent for collection Critical10 Interest / commission / Service Tax /postage /

other bank’s charges if anyCritical

11 Date of realization Critical12 Provide facility to link customer ID with

Cheque/ Draft account.Critical

13 To generate covering schedule (Outstation Purchase only) for dispatch including remittance and dispatch instructions on realisation (e.g. TT / Courier ) as also necessary vouchers and provide for charging of commission upfront

Critical

14 Provision to maintain the ledgers party wise CriticalRealisation of cheques purchased

15 To generate register with the following details Critical

of 274


16 Date of realization Critical17 Our number Critical18 Amount realized / credited Critical19 Rate of interest Critical20 Amount of interest Critical21 Other bank’s charges Critical22 Column for returned instrument (to be debited

to Past due and dishonored bills account in case of insufficient funds in the party’s account) with reasons thereof

Critical

23 To provide facility for entries to park and convert these from parking account to respective account upon cheque realisation.

Critical

24 Provide facility to restrict total clean Cheque purchase amount limit upto Rs. X for a customer (X is parameter)

Critical

25 Provide facility to mark the customer as "Defaulter" when the cheque deposited and purchased is returned unpaid due to financial reason. System should restrict from providing cheque purchase facility to such Defaulter customers.

Critical

26 To provide facility for entries for converting Critical27 Cheque Purchase to Cheque Collection Critical28 Returning of cheques with reasons thereof Critical29 Charging of interest from day one with penal

interestCritical

30 Our bill number Critical31 Name of party / account number Critical32 Bill amount / Amount credited Critical33 Margin held Critical34 Drawee details Critical35 Whether documentary or clean bill Critical36 Details of demand bills (Demand bills

purchased are to be shown separately in general ledger (GL) under Inland Bills Purchased (Demand) account head)

Critical

37 Details of documents enclosed like Invoice, Lorry / Railway Receipt, Airway Bill etc. with date / number / amount / Transport Operator

Critical

38 Our commission and collecting Bank’s charges if any

Critical

39 Postage Critical40 Interest charges / recovered Critical41 Instruction to party (regarding commission,

overdue interest and disposal instructions)Critical

42 To whom sent for collection Critical

of 274


43 Date of realization Critical44 Details of returned instrument (to be debited to

past due and dishonored bills account in case of insufficient funds in the party’s account) with reasons

Critical

45 Provide facility for generating- Critical46 Register Critical47 Covering schedules for dispatch along with

instructions of the drawers of the billCritical

48 Vouchers Critical49 Party wise ledger Critical50 Party wise bills outstanding & cheque pending

for collection (provision to provide age wise analysis for a given period)

Critical

51 Maintenance of Bills Purchase Register and Bills Purchase Ledger party wise

Critical

52 Maintenance of parking account for margin held

Critical

53 Maintenance of list of IBA approved Transport Operators and validation thereof while purchasing Bills

Critical

Bills for discounting54 To generate register with the following details: Critical55 Date of Purchase Critical56 Bill number and Bill Date Critical57 Name of party / account number Critical58 Amount Critical59 Drawee Critical60 Details of Bill of Exchange number of days of

usance period and due dateCritical

61 Details of documents enclosed like Invoice, Lorry / Railway Receipt, Airway Bill etc. with date / number / amount

Critical

62 Insurance details Critical63 Discount, amount of discount Critical64 Commission / Service Tax /postage Critical65 Date of realization Critical66 Margin Deducted Critical67 Details of returned Instrument (to be debited to

Past due and dishonored bills account in case of insufficient funds in the party’s account) with reasons thereof

Critical

68 Provide facility to link customer ID with Bill Discount account.

Critical

69 To generate schedule for dispatch along with instructions

Critical

of 274


70 Maintenance of Bills Discounted Register and Bills Discounted Ledger party wise

Critical

71 Maintenance of parking account for margin held

Critical

72 Maintenance of list of IBA approved Transport Operators and validation thereof while purchasing Bills

Critical

73 Provide facility to process Bill discounting back by LC and all functionalities of BD and LC should be available

Critical

74 Provide facility to capture the discrepancies in the shipping document received

Critical

Realisation of discounted bills75 To provide for register with the following

detailsCritical

76 Date of realization Critical77 Name of party / Account number Critical78 Amount of bill and amount realized Critical79 Number of days Critical80 Rate of interest Critical81 Overdue interest Critical82 Penal Interest Critical83 Margin Deducted Critical84 Details of returned Instrument (to be debited to

dishonored bills account in case of insufficient funds in the party’s account) with reasons thereof

Critical

85 To generate realisation register Critical86 To provide facility for entries to park and

convert these from parking account to respective account upon cheque realisation.

Critical

87 Provide facility to calculate actual interest upon actual days of bill realisation, and if advance interest is more than actual interest, the excess interest should be credited back to customer account.

Critical

Advance against Bills in Course of Collection

88 Provide facility to capture following details Critical89 Name of the customer / party Critical90 Limit Critical91 Sanctioning authority Critical92 Date of sanction Critical93 Renewal date Critical94 Percentage of bills returned unpaid Critical95 Whether bank reimbursed immediately (yes /

no)Critical

of 274


96 To generate register with the following details Critical97 Date of lodgment Critical98 Bill No. Critical99 Name of the customer / drawer Critical100

Branch of Bank / branch / agency on whom it is drawn

Critical

101

Amount of bill Critical

102

Drawee details Critical

103

No. of days grace Critical

104

Due Date / Details of usance Critical

105

Our commission and collecting Bank’s charges Critical

106

Postage Critical

107


Critical

108

Whether documentary / clean bill Critical

109

Details of documents enclosed like invoice, lorry / railway receipts / airway bill etc. with date / number / amount

Critical

110

Details of usance / due date Critical

111

Our commission and collecting Bank’s charges if any

Critical

112

Postage Critical

113


Critical

114


Critical

115

To whom sent for collection and city Critical

116


117

Margin held Critical

118

Date of realization Critical

119

Details of returned Bills / Instruments (to be debited to Past Due and Dishonored Bills Account in case of insufficient funds in the party’s account) with reasons

Critical

12 Provide facility for generating—(a) register (b) Critical

of 274


0 covering schedules for dispatch along with instructions of the drawers of the bill (c) vouchers and (d) party wise ledger (e) Control vouchers

121

Maintenance of pointed account for margin held

Critical

122

To generate realization register Critical

123

To generate de-control vouchers Critical

124

Maintenance of list of IBA approved Transport Operators and validation thereof while allowing advance against bills in course of collection

Critical

Supply Bills Purchased125

System to provide validation for acceptance of the bill after verifying limits sanctioned (parameterized) documentation, creation of charge over the assets of the limited company and other documents.

Nice to Have

126

Provide facility for creating the definition for determining the due date calculation including that for supply bills.

Nice to Have

127

System to provide for acceptance of the bill after Manager’s approval

Nice to Have

128

System to provide for register with the following details for supply bills purchased

Nice to Have

129

Date of lodgment Nice to Have

130

Our bill number Nice to Have

131

Name of the Govt. Department on whom the bill is drawn

Nice to Have

132

Bill amount Nice to Have

133

Amount credited Nice to Have

134

Margin held Nice to Have

135

Drawee details Nice to Have

136

Details of documents enclosed like bill of exchange for the good supplied, inspection certificate, a contract acceptance note, a receipted Challan evidencing receipt of goods by the Department concerned.

Nice to Have

137

Our commission / Service Tax Nice to Have

138

Postage Nice to Have

of 274


139

Interest charges / recovered (System to provide for debit from the date of purchase to the date of receipt of proceeds by the bank)

Nice to Have

140

No. of days Nice to Have

141

Interest rate and Penal rate Nice to Have

142

Amount realized Nice to Have

143

Date of realization Nice to Have

144

Details of returned Instrument (to be debited to past due and dishonored bills account in case of insufficient funds in the part’s account) with reasons

Nice to Have

145

Maintenance of supply bills purchased register ledger party wise

Nice to Have

146

Maintenance of parking account for margin held

Nice to Have

147

Provide facility to link customer ID with Supply Bill account.

Nice to Have

Supply Bills Realisation148

To provide for register with the following details

Nice to Have

149

Bill number Nice to Have

150

Amount purchased / realized Nice to Have

151

Date of realization Nice to Have

152

Overdue interest Nice to Have

153

Amount Nice to Have

154

Number of days Nice to Have

155

Interest rate and Penal rate Nice to Have

156

Provide facility for realisation register and vouchers along with advice for party

Nice to Have

157

To provide for two fields for interest calculation Nice to Have

158

Upfront Nice to Have

159

At the time of realisation Nice to Have

160

To provide for penal interest at the time of overdue bills realization

Nice to Have

of 274


Bank Guarantee161

Provide facility to create & issue Bank Guarantee

Critical

162

Provide facility to capture following details for creating BG, but not limited to

Critical

163

Name Critical

164

Address Critical

165

Amount Critical

166

Security (Cash Margin) Critical

167

Security Details ( FD …etc.) Critical

168

Period Critical

169

Claim Period /Expiry date Critical

170

Commission Critical

171

Charges Critical

172

Name of payee Critical

173

Provide facility to capture required documents for processing Bank Guarantee

Critical

174

Provide Facility to create Installment schedule generation in case of Deferred Payment Guarantee (DPG)

Critical

175

Provide facility to invoking a Bank Guarantee and to capture required reasons for invoking Bank Guarantee

Critical

176

Provide facility to reversing Bank Guarantee and to capture required reasons for reversing Bank Guarantee

Critical

177

Provide facility to closing Bank Guarantee and to capture required reasons for closing Bank Guarantee

Critical

178

Provide facility to assign Bank Guarantee limit and/ or adhoc Bank Guarantee limit to the customer,

Critical

179

Provide facility to link customer ID with Bank Guarantee account.

Critical

180

Provide Facility for defining the guarantee number generation method. (Serial No. generation method to be defined with a parameter, whether Financial Year wise or Calendar year wise, whether the module is on

Critical

of 274


line or not, for each branch.)181

Provide facility for configuring parameters for maintaining various types of guarantee with brief description, whether it is a Financial/ performance/ bid bond/ Deferred payment guarantee.

Critical

182

For each type of Bank Guarantee, for given effective date, Base commission, rounding off parameter to be captured for issue of fresh Bank Guarantee amendment of existing Bank Guarantee, commission for issuing of Bank Guarantee (in % of the amount per quarter). If the Bank Guarantee is secured by our own Bank deposits then the rate of concession of normal commission in % to be captured. For refunding excess commission at the time of cancellation ofBank Guarantee no. of quarters to be reduced to be captured.

Critical

183

Parameter of GL/Sub GL/Brk up GL for voucher generation for issuance of BG, amendment of BG, Cancellation of BG, Commission collection credit, Other charges, Service Tax (both fixed and variable charges – to be parameterized)

Critical

184

Entry program for Issuing of BG (Bank Guarantee) which will generate the BG No., and vouchers on saving, which should be authorised separately.

Critical

185

Provide facility to capture Counter guarantee details to be captured within the issue program of BGs.

Critical

186

Provide facility to capture the % of lien for a BG which is backed by bank listed securities. (e. g. FD) and should allow to issue new BG against same securities ( FD )if the % line is not utilised to the full extent.

Critical

187

Entry of amendment of BG capturing the type of amendment and reason for amendment, with voucher generation and necessary authorization program to authorize the amendment.

Critical

188

Entry program and authorization program with voucher generation for cancellation of BGs

Critical

189

Provide facility to link devolved BG account with regular BG account.

Critical

190

Option for noting the receipt of invocation of a guarantee from the beneficiary of the guarantee which will be checked at the time of actual invocation of the guarantee.

Critical

19 Entry and authorization (with voucher Critical

of 274


1 generation) for invocation of guarantee provision to Debit the Customer account OR designated Bills account of the customer. Necessary voucher to be generated for payment and charges collected for invocation.

192

Report on BGs marked for revocation (letter received for invocation but pending for revocation in the system) as on a given date. Report of BGs invoked during a given period and as on a given date.

Critical

193

Provide facility to charge interest from the date of BG invocation.

Critical

194

Entry and authorization programs for making payment towards Deferred Payment Guarantees

Critical

195

Report on next due dates of payment of a given DPG or all the DPGs& DPGs due already and payment is not made.

Critical

196

Report on Commission & service tax received on various BGs and for a given BG for a period of time (date range)

Critical

197

Bank Guarantee register printing – containing the details of the guarantee like BG No., date of issue, amount of BG, beneficiary, Date of expiry, Comm. Collected up to, Margin held (portion of cash margin and deposit margin or both)

Critical

198

Security creation and Linking/Delinking for BGs. Entry of Creation of security, Linking (with % of linkage of the security) for a BG and De-linking of the security with authorization

Critical

199

Commission recovery entry and cash margin reversal entry, with relevant authorization.

Critical

200

Provide contingent/liability account creation Critical

201

Not allow any system entry other than bank guarantee issue entry to post entries to the contingent/liability accounts

Critical

202

Provide printing templates for all guarantee types issued

Critical

203


Critical

204

Provide date flexibility for bank guarantee issue entry, back value date, same date issue, future value date issue.

Critical

205

Provide system alerts and reports on all expired bank guarantees

Critical

of 274


206

Bank to bank guarantees to generate the relevant messages

Critical

207

Automatic refund of cash margin Critical

208

Auto generation of guarantee authentic/not authentic letters

Critical

Letter of Credit209

Provide facility to allow bank to define products for L/C (Import/ export), Bills payment and fund transfer

Critical

210

Provide facility to capture following details for opening/ creating L/c, but not limited to,

Critical

211

LC Opening Branch Critical

212

Customer Number Critical

213

Customer Name Critical

214

Method of payment Critical

215

Country of origin Critical

216

Major commodity & Sub commodity of the transaction

Critical

217

Currency Code Critical

218

Amount in local currency Critical

219

Amount in Foreign Currency Critical

220

Exchange Rate Critical

221

Exchange Charges Critical

222

SWIFT Charges Critical

223

Method of Shipment (FOB, C&F, CIF, etc.) Critical

224

Expiry / Validity date (Auto) Critical

225

Import Purpose Critical

226

Interest Critical

227

Commission Critical

228

Charges /Fee Critical

22 Margin paid Critical

of 274


9230

Earmarking for margin from CC account Critical

231

Earmarking amount for margin from CC account

Critical

232

Provide Flexibility for bank to define Commission/ Charges/ Interest /Fee as per Bank's requirement

Critical

233

Provide facility to modify the already defined Commission/ Charges/ Interest /Fee at time of contract booking.

Critical

234

Provide facility to capture LC details when LC's issued through 3rd party tie ups, but not limited to

Critical

235

Bank details Critical

236

Customer Name & ID Critical

237

Charges Critical

238

Breakup of charges Critical

239

Contra entries should be passed upon authorisation

Critical

240

Provide facility to modify / update LC details ( Like increase / Decrease in amount,

Critical

241

Provide facility to invoking a LC and to capture required reasons for invoking LC

Critical

242

Provide facility to reversing LC and to capture required reasons for reversing LC

Critical

243

Provide facility to LC extension and to capture required reasons for extending LC

Critical

244

Provide facility to closing LC and to capture required reasons for closing LC

Critical

245

Provide facility to pass relevant accounting /contra entries automatically whenever LC related events/ actions triggered or happened

Critical

246

Provide facility to auto populate the basic customer information when processing additional LC for the existing customer.

Critical

247

Provide provision to generate all relevant SWIFT messages for Import/ Export transactions as specified by SWIFT

Critical

248

Provide facility to retrieve LC details when LC number is entered

Critical

249

Provide facility to validate the regulatory requirements for opening LC for the particular customer. (e.g. Foreign exchange permit

Critical

of 274


validity )250

Provide facility to capture following details on receipt of shipping documents, but not limited to

Critical

251

LC Number Critical

252

Date the document arrived Critical

253

Amount in foreign currency Critical

254

Prevailing exchange rate Critical

255

Nominated Bank and their reference Critical

256

Reimbursing Bank Critical

257

Number and types of documents Critical

258

Margin Paid Critical

259

Advance amount in Local currency Critical

260

Provide facility to Customer ID with LC account Critical

261

Provide facility to capture the discrepancies in the shipping document received

Critical

262

Provide facility to generate LC letters /Documents and printing thereafter.

Critical

263

Provide facility to link devolved LC account with regular LC account.

Critical

264

Provide facility to capture LC confirmation details

Critical

265

L/C Number Critical

266

Date of confirmation LC sent Critical

267

Confirming authority name Critical

268

L/C confirmation Date Critical

269

Date of confirmation received Critical

270

Other details Critical

271

Provide facility to capture following data during the LC amendment

Critical

278

L/C Number Critical

of 274


279

Reason of amendment Critical

280

Amendment Commission/ Charges Critical

281

Amendment date Critical

282

Provide facility to capture following data during the LC settlement

Critical

283

L/C Number Critical

284

Date the document arrived Critical

285


286

Advance Exchange Rate Critical

287

Settlement date Critical

288

The date correspondent a/c debited or would be debited

Critical

289

Provide facility for Advance partial settlement with proper authorisation.

Critical

290

Provide facility to capture following data during the LC Cancellation

Critical

291

L/C Number Critical

292

Date L/C canceled Critical

293


294

Full or partial cancellation Critical

295

Reason for cancellation Critical

296

Provision to open protested bills account in case of bills received under LC or invoked LC's where parties have not Provide facility for funds

Critical

Letters of Credit297

Provide entry to collect margins both cash and deposit securing the LCs

Critical

298


Critical

299

Provide reports on commission and fees collected for LC issue and bill payment

Critical

of 274


300

Provide system alerts and reports on maturity dates of bills presented

Critical

301

Provide system alerts and reports on expiry dates of LCs

Critical

302

Provide printing templates of forwarding schedules for both import and export LCs

Critical

Additional requirements303

System to capture purpose of transaction field for both incoming and outgoing transfers

Critical

304

Guarantees to fall off upon maturity Critical

305

System to mark central bank deals e.g. Borrowings, etcetera

Critical

306

System to capture auto confirmation of guarantees

Critical

307

System to have ability to allocate income e.g. Commission of Guarantees to link to Branch ledgers

Critical

308

System to support automatic refund to customers upon maturity-without manual

Critical

309

System to allow cross currency transactions Critical

310

System capability to integrate with existing Systems

Critical

311

Intelligent Reporting tool to serve as Business Intelligence

Critical

312

Audit Logging for all activities in the system Critical

313

System Change Logs Critical

1.3.14 Safe Custody# Common Requirements Requirements



1 System to allow for creating of a safe custody account to be maintained.1.A safe custody account to be opened under a customer’s Client ID (say a ledger sort of) whereby records of his safe custody details will be listed. This account will in a way be linked to his main account where debits of the

Critical

of 274


annual/bi-annual/monthly safe deposit fees will be debited. This account will also be able to support the bank in managing the clients safe custody movement so that in a 360 degrees view, we can automatically see how many times the client has accessed his deposit and the charges (automated) thereof

2 The fees can be broken down into monthly/quarterly/bi-annual/annual fees subscription. This will assist in tracking of movement and revenue arising from the product.

Critical

3 A report showing branch wise safe custody accounts to be maintained/ available (active/ closed)

Critical

4 The auto generated Reference Number of the Safe custody to run until the items are discharged from safe custody. If the client wishes to return items after, then a new Reference number should be generated.

Critical

5 An alert should be sent to the customer if say his monthly subscription is about to end so that he can renew the subscription or withdraw. This will ensure we do not have items overstaying in safe custody. Furthermore, this will assist whereby the customers main accounts have gone dormant.

Critical

6 Customer information to Include a Next of kin who can access the safe custody in case of their demise or unfortunate incident, Details to include the relationship to the client and their phone numbers.

Critical

7 The system should be able to provide automated teller receipts where customers can sign upon access of their items(the customer will not need to write letters anymore on their intent to access the items).In case of a withdrawal, a receipt can also be generated for the client to sign. When signing up for safe custody, we can have a general information sheet for the customer to fill for hard copy back up and the information to supplement what we have in the system. This to be the only manual file the bank will hold on safe custody.

Critical

8 An auto generated receipt should be provided once the client has signed off for safe custody.

Critical

1.3.15 Corporate Banking# Common Requirements Requirements Fully

of 274



Supported / Partially Supported / Not Supported / To be customized

1 System to provide wholesale reports specific to each RO/RM in term of portfolio owned, income generated, liabilities, account performance in terms of PAR and NPL

Critical

2 Ability of each RM/RO to generate own reports. Critical3 Ability to generate Total Income earned per

customer, account turnovers, liabilities paid to the customer for specific requested periods

Critical

4 Ability to give reports of total facilities per customer from various branches whether personal accounts, partnerships or Limited liability accounts singly or jointly with other parties.

Critical

5 Generate reports of securities held in customer's account, last valuation date and value.

Critical

6 Ability to link related accounts and to generate a summary report of outstanding balances in group accounts

Nice to Have

7 Ability to capture approved limits for non-funded facilities, utilization and available room

Critical

8 The customer ID to show at a glance; total of approved facilities, limits and outstanding balances

Critical

9 Customer's account to capture physical addresses, emails, ID Nos, Registration Nos as well as phone numbers

Critical

10 Allow auto-generation of a unique account number for each and every deposit account fixed deposits/call deposits as per bank specification.

Critical


Critical

12 System to be capable of generating deposit receipts automatically upon creating any deposit.

Critical

13 Ability of each RM/RO to generate own deposit report as well as the FD corporate report indicating names of the client, start date for the deposit, closing date and interest rate and if the deposit is under lien or not.

Critical

of 274


14 System to allow amendment of details at the stage of inputting deposits in the system before authorization stage is complete.

Critical

15 System to allow generation of the deposit maturities for any specific month as per the requirements of the users.

Critical

16 System to allow generation of reports for deposits lifted, newly placed, uplifts for any specific month or any period as per the requirement of the user.

Critical

17 System to support payment of interest at intervals e.g Quarterly while the fixed deposit is still running even if for a year or not.

Critical


Critical


Critical

1.3.16 Others# Common Requirements Requirements



1 Scalable system to accommodate all kinds of products

Critical

2 System be able to measure product profitability Critical

3 System integration; System to easily integrate with other systems i.e. CRM and update customer information for ease of access.

Nice to Have

4 Transaction alerts; System to give alerts on Debits & Credits, Overdrawn accounts, Inactive accounts, Dormancy alerts, Unclaimed assets.

Nice to Have

5 Reports and Authentications; System to generate reports which can be used as authentic copies. For instance, Bid bond confirmation

Nice to Have

6 Customer information in one click; with a click we should be able to view crucial customer information, i.e Personal identity, contacts, accounts, loan accounts details and

Nice to Have

of 274


any relevant information on one page/screen.

of 274


1.3.15 Core Banking System Desired Features

Core banking platforms offer a myriad of features and applications. These key features of core banking software make the whole process of digital transformation absolutely worth it.

Customer onboarding: In a traditional banking scenario, customer onboarding is one of the most cumbersome tasks. Core banking applications make this process extremely easy. There is no hassle of endless paperwork and multiple verifications; the entire process is digitized and completed within a few clicks.

Digital cash management: Day-to-day cash transactions such as deposits, withdrawals, and transfers can be processed digitally without any in-person contact. This makes the mundane banking activities safe and efficient. This also includes other banking activities such as bill payments, credit card payments, and online retail transactions. This is particularly convenient during the times of Covid-19 when customer safety is vital.

Secure data management: Data migration and data management are two of the most critical aspects of the banking sector. Core banking platforms make data management both manageable and seamless. Consolidated information that showcases customer data, business data, and transactional data can help the bank make important decisions. Accurate data management can help a bank recommend the right financial products to its customers. Business and transactional data can help banks evaluate growth strategies and launch new products that benefit their customers.

Mobile applications: A mobile app has become an essential extension of a bank’s digital presence. Mobile applications and Net Banking facilities allow customers to access their account from anywhere. This ensures customers that they can carry out their banking activities without any interruptions. This also improves customer engagement in banking.

Advanced security integration: As banking activities continue to migrate online, money mismanagement and fraudulent transactions may occur occasionally. One of the key advantages of the core banking software is the top-notch security integration across all the verticals of a bank. Features such as dual authentication processes and digital identity management ensure tight security to both the banks and their customers.

1.4 Implementation Requirements The bank expects the selected vendor to provide industry best practices to the bank’s staff for the ongoing management of proposed system and any specifics related to the operation of the proposed solution. It is desired that the solution architecture is designed to accommodate future growth without requiring the bank to invest in expensive forklift replacement and infrastructure redesign.It is very important for vendors to understand the requirements of the proposed solution and come up with a plan showing proposed solution steps. The following requirements are mandatory:1. Testing, Staging and Deployment Schedule

Demonstrate the functional production solution showing the configuration as it communicates and collect data from the identified bank systems. This will show the operational effectiveness of the

of 274


proposed solution that just installed/implemented with minimal configuration effort (out of box).

Describe how the solution works during link and device failure. Vendors are required to submit a complete project plan with details and

action steps clearly specifying execution items. The vendors are required to provide the type and level of support that

they expect from the bank to complete their work as proposed. The vendor is required to provide product road map and its end of life

details. The vendor must provide a summary of known outstanding bugs

associated with the current software version if any. Vendors must work in such a manner that bank business is not affected

in any way. If emergency system down time is inevitable to deliver the proposed solution, at least 15 days prior written notice is required.

It is the vendor’s responsibility to install, configure and integrate the complete solution as per bank business schedule and on time.

2. Availability and Business ContinuityThe bank’s information systems operate as a ‘virtual campus’, where users access bank systems from any place at any time. The proposed design is expected to prevent possible single points of failure within the system.

3. Management and Monitoring The vendor must specify the recommended and minimum memory,

number of CPUs, and disk space for the proposed system hardware and operating system for the system. The system must be installed and updated by ICT personnel on CBKL owned hardware located in the bank’s data centre.

Describe how the system logs errors, what error data constituents are documented and how to view useable information from log errors:

o Describe any monitoring tools or plug-ins that exist to monitor the system.

o Describe how the system monitors status.

4. Security and AuditAs a principle, the proposed solution should not cause any security vulnerability to the bank systems.o Vendor must provide information about their responsible disclosure

program/process.o Vendor should provide procedures for patching of the proposed solution

including the third party components that the proposed solution relies on.

o List all third-party software that is necessary for the operation of the solution and will require down time of the proposed SIEM solution during patching.

5. Training Provide certified technical training for 5 CBKL employees to be trained to

configure, operate and maintain the proposed solution and any bank requested technology. The assumptions about the proficiency of the

of 274


CBKL personnel must be noted. CBKL may use these vouchers at any point in time.

Provide a list of digital documents for installation, operation, use, and administration of the whole solution. These documents must be structured, editable, portable, and searchable. All major sections of the content of these documents must be identified within the beginning of each document.

In addition to vendor’s official product support, if it is available, the vendor is expected to provide full access to its online forums/user community for the identified bank staff to get support from their peers from other institutions.

In addition to formal classroom training, the bank requires the vendor to provide on-site training of key concepts which are specific to the proposed solution. The vendor must specify the type of training provided.

Specify and describe any help files provided by the system, and whether they can be customized for CBKL.

6. SupportDescribe if and how you will provide 24 x 7 support and the time frame of guaranteed initial response time.

Specify whether you will provide on-site support of initial installation. Describe what type of work is expected from the bank staff in order to

implement the proposed Core Banking Solution ion. Please provide other services for maintaining the solution in a supported state

7. Scalability and adaptability The system should be able to support a minimum of 250 Users logged in

simultaneously. The system should have the capacity to support a minimum of 20 branches

with options to increase branches. System should be able to run reports by branch to show performance. System should be able to integrate with internal systems running of Oracle

and SQL databases.

of 274


2.0 EVALUATION CRITERIA2.1 Mandatory Evaluation

SN REQUIREMENT YES/NOa) Duly completed tender formb) Duly completed price schedulec) Duly filled and signed Confidential Business

Questionnaire.d) Tender validity period of 90 days after the date of

opening of the tender.e) Tender security of Kshs 2,000,000 or equivalent

amount in USD of the system value valid for a period of 120 days from the tender closing date

f) Certificate of Incorporation/Registrationg) Audited financial statements for the past two (2) yearsh) Manufacturer’s authorization letter/Authorized re-

seller/i) Evidence of Supply, Installation and Support of a core

banking system. Attach copies of contracts, LPOs and Completion Certificates

j) Bidders must paginate and serialize the entire document from the first to the last page

k) The solution provider should have at least 2 CBS sites in East Africa/Africa

l) Specify total Implementation Period in Months (From Commencement to Go Live)

2.2 Technical Evaluation2.2.1 General Requirements Evaluation (19Mks)# Evaluation Criteria Marls

1 Availability of account / customer drill down details from all inquiry / transaction screens through the use of a hotkey enabling 360 degree view of the client, including limits and securities maintained delinquencies, relationship view, cheque return history, address change history, account snapshot.

1 mark

2 Copy facility for transaction screens 1 mark3 Field level help options 1 mark4 Drill down enquiries to provide consolidated details in one

screen for all Retail Banking, Corporate Banking and Trade Finance information of a client

1 mark

5 Unique codes for branches 1 mark6 Ability to define a single product for multiple currencies

instead of separate products for each currency 1 mark

of 274


7 Availability of an in-built tool to facilitate creation of new reports independently by the bank without requiring a third party tool or vendor intervention

1 mark

8 Maintenance of a business calendar with facility to change the business days as and when required.

1 mark

9 Open source architecture to allow for integration of different systems in the bank

1 mark

Hovering Facility10

System should support hovering facility at Start of Day/End of Day and Online. Hovering should enable the system to recover charges/loan dues and installments automatically during EOD/SOD/.Online. .

1 mark

11

Partial hovering should also be supported such that funds as they become available in the funding account, should be deducted by the system for credit to the charges/loan account

1 mark

12

Provision to define Hovering Type (Manual, recovery of charges, recovery of loan installments, etc.)

1 mark

13

Provision to define the account from which amount has to be withdrawn towards hovering

1 mark

14

Provision to define the account into which the amount withdrawn has to be credited

1 mark

15

Define the charge type for which Recovery is done 1 mark

16

Define the charge on Amount with the applicable service tax amount

1 mark

17

Date of Entry and Start date of Hovering 1 mark

18

Text field for providing narration to be used for recovery transaction

1 mark

19

Text field for providing hovering remarks 1 mark

2.2.2 Technical & Functional Requirements Evaluation (134Marks)

#Evaluation Criteria

Marks

1 The system should comply with major international regulations such as UCP, URR, ISP, URDG and e-UCP, facilitating all standard Trade Finance operations.

1 mark

2 The system should support multi country, multi-region and multi-branch (within a region) setups with different base currencies and different products, features, calendar and workflows local to the country/region/branch.

1 mark

3 All processing rules should be parameterised so that the deviations mentioned in 1.3 can be achieved by parameter setting

1 mark

of 274


4 All parameter settings (rules) should be able to do centrally

1 mark

5 Facility to localize the business rules as per the country’s rules and regulations when operating in multiple countries.

1 mark

6 For all customer transactions, customer details should be taken from the core system. But additional customer data like special email addresses and contact nos. etc. should be able to maintain in Trade Finance system

1 mark

7 For all transactions, the system should generate and post the accounting entries automatically according to the rules defined (cost centre wise)All accounts related to the relevant customer should be popped up for selection and facility to select more than one account.

1 mark

8 For each transaction, only the relevant charges should be mapped and the accounting entries pertaining to charges should get generated and posted online to all the respective accounts automatically on authorisation of the transaction. There should be a facility to collect charges from any designated currency.

1 mark

9 In each and every branch, multi-currency transactions should be possible. Charges and commission should be able to get from any designated currency

1 mark

10 For each and every transaction, system should automatically get all the relevant rules (accounting, charge, commission rules etc.) linked to the transaction. There should NOT be any manual selections of the rules or manual calculations on charges, commissions etc.

1 mark

11 For each and every data entry, validations for mandatory fields and a mechanism for error correction before final authorization without re-entering the whole data set again should be there. And also the modifications done should be highlighted for the authorizing officer.

1 mark

12 Every authorization should show all the required details for the officer and with the authorization, posting of all the relevant accounting entries should be done automatically and the SWIFT messages created (if any) should be written to a pre-defined outside location

1 mark

13 Updating of all accounts should be online on authorization of the transaction.

1 mark

14 Exchange rates should automatically be linked to the transactions directly from the core banking/treasury system everywhere rates are applied

1 mark

15 Separate facility should be available to create accounting entries outside a transaction with or without a transaction reference.

1 mark

16 There should be a facility to read a pre-defined external location and initiate or apply transactions received through SWIFT messages with a single click.

1 mark

of 274


17 There should be a facility to configure auto generation of reminders at pre-defined dates or periods

1 mark

18 Each & every country should be able to perform their Day–End process independently

1 mark

19 Daily position with ref. No should be reported to treasury. For future transactions value date should also be reported.

1 mark

20 Should provide online real time/batch interfaces( as mentioned in Interfaces section) for all required external systems such as Core Banking system, Treasury, Document Management system, SWIFT etc.

1 mark

21 There should be a facility to maintain codes where ever possible. (Consignment, industry, H.S. Codes, collateral, etc.)

1 mark

22 Facility should be there to define authority levels and restrict every transaction to an authority level

1 mark

23 There should be a possibility to setup dual/higher authorisation for any required transaction

1 mark

24 All standard reports & queries (Outstanding reports, Customer exposure reports, income reports, profitability, volume reports etc.) should be inbuilt in the system and a separate user friendly report writing tool should be provided for ad-hoc report generation. Generated report should be able to export to commonly used formats such as Excel, Word, PDF, xml.

1 mark

25 All advices, letters, reminders etc. should be generated by the system along with the relevant transaction or on pre-defined periods with the printing facility and/or, e-mailing facility and/or SMS facility

1 mark

26 The system should provide a mechanism to predefined the formats of the above documents (in 1.29) with variables for customer and transaction specific values such as Name, address, transaction amount etc.

1 mark

27 All documents generated by the system for other processing units like SWIFT messages should be consistence with their standard format. All possible validations for such formats should be embedded in the system.

1 mark

28 Ability to highlight selected areas of advices generated by the system is preferable.

1 mark

29 Transaction viewing facility with accounting entries and all other related data such as margin, credit line and exchange rate detail should be available in a single selection of the transaction. This view should also contain accounting entries created outside the transaction but related to it.

1 mark

30 System should facilitate to create and maintain Local and Foreign Bank BIC Codes, Name and address.

1 mark

31 The users should be able to view the accounting entries generated at transaction level.

1 mark

of 274


32 There should be provision for transfer pricing in the system, so that the commission income of Trade Finance transactions are apportioned between the cost centers (separate GL)

1 mark

33 For transactions under special schemes such as grants and ADB loans, a facility to define the liability at transaction level is preferable. Here, the charges must be recovered from the customer account.

1 mark

34 For transactions of a non-Bank customer, there should be an ability to debit/credit designated GL accounts. (Egg. Export LC advising for non-customers and LC advised through other banks)

1 mark

35 Facility for inter-linking with shipping companies for electronic data exchange and comply with Bolero is preferable.

1 mark

36 An online interface to the treasury, so that a request for a special exchange rate can be done within the transactions is preferable. Here, the acknowledgement should also be possible (accept or reject). If accepted, special rate should be automatically mapped to the specific transaction with the treasury reference number without any modification.

1 mark

37 Dash Board Facility is preferable 1 mark38 Should provide system documentation materials (data

dictionary, Installation guide, technical manual, user manual, Installation manual, backup recovery procedure, system architecture etc.)

1 mark

39 Should provide comprehensive user and technical training on the system as well as the trouble shooting sessions. Details of the training plan should be provided. (Site visits also preferred)

1 mark

40 Training programs should be conducted annually by the vendor for Bank Technical and Functional staff on Bank request.

1 mark

41 An issue reporting mechanism should be provided so that the status of the issues raised by the bank should be visible at any time.

1 mark

42 Reported issues should be attended within a reasonable time period according to their criticality

1 mark

43 Onsite technical support should be provided for implementation and post implementation until key issues are resolved.

1 mark

44 Document management capabilities are preferable. 1 mark45 Black list checking facility is preferable 1 mark46 Facility to maintain special remarks at transaction level

and auto pop-up of remarks at every retrieval of transaction is preferable.

1 mark

47 The Trade Finance solution offered in this tender should have been using in at least one commercial bank (having

1 mark

of 274


at least 300 branches globally and operating in more than one country) in Asian region during last 3 years.

Data Requirement for Integrated Risk Management System

48 • There should be a facility to extract all details of the collateral maintained against Trade Finance facilities,

1 mark

49 • all details of default Transactions50 • all Details of recovery51 • all details of Provisions to be made52 • all details of guarantees granted

Functional Requirements - Imaging/Document Management capabilities

53 Document management facility is preferable 1 mark54 Facility to Scan, Upload, View, remove and annotate

documents to underline transaction and to specific event 1 mark

55 User defined Indexing and Categorization of scanned Images

1 mark

56 Facility to manipulate the image - zoom, rotate, print, invert etc.

1 mark

57 Should support limited bandwidth preferably encode the image and parameterized cache management capabilities.

1 mark

58 System should allow bank users to upload/attach documents directly from the transaction screens, at various events of the transaction lifecycle.

1 mark

59 Support various document formats (Image, PDF, Word, Excel, tiff, others)

1 mark

Technical Requirements60 The system should comply with latest technology 1 mark61 Application should support major RDBMS’s preferably

IBM i DB2, Oracle(exadata), Sybase, Informix or SQL servers etc.

1 mark

62 System should comply with banks Information Security Policy (ISP) rules security and Single Sign On

1 mark

63 If the total solution is a web based one, dedicated API/Web Services should be provided to interact with other systems such as Core Banking, Exchange Rates, Treasury, Internet Banking, and DMS..etc. as mentioned in Interfaces section

1 mark64 1 mark65 1 mark

66 System should provide configurable batch processing and scheduling functions which ease to automate start of day and end of day operations

1 mark

67 There should be a facility to purge history records with retention period. Option to take necessary reports and backups of purged data should be available. Also it should be clearly mentioned the archiving procedure of data.

1 mark

68 System response time should be within acceptable 1 mark

of 274


industry standards69 Should provide mechanism for data migration. Data

should be migrated to the system, with the relevant validations.

1 mark

70 On-site technical support should be available for implementation and post implementation until all key issues are resolved

1 mark

71 Application should support proper version controls 1 mark72 There should be a roper way of handling application

logs/traces/audit trails and should be able to extract in readable format whenever necessary.

1 mark

73 Audit Trails should be available to identify all activities done in the system with the user ID, date and time together with the activity done.

1 mark

74 System rollout should not contain any client side software installations

1 mark

75 Parameter configuration should not be too complex 1 mark76 The software should have QA certification. 1 mark77 Bank logo should be displayed in the system display 1 mark

Technical Requirements - Interfaces78 Interface to debit/credit customer/GL accounts in core

system. 1 mark

79 • This interface should support multi-currency, cost centers, and all types of accounts (CA/SA/DFC/RFC, GL, Nostro/Vostro etc.).

1 mark

80 • And also should support rounding off facility and the remainder of the amount should be accessible.

1 mark

81 • Should be able to use the OD limit if available for current accounts

1 mark

82 • Should facilitate for forced debit also 1 mark83 • GL entries to the core system should be able to either

summarised/individually post as required

1 mark

84 • This should be an online real time interface. 1 mark85 Interface to get customer details from the core system. 1 mark

86 • This interface should get details of the customer in the core system through the unique identification number (CIF)

1 mark

87 • This should be an online real time interface 1 mark88 Interface for customer facility update in core system. 1 mark89 • Relevant limit, sub limits and Overall limit of the

customer should be updated accordingly 1 mark

90 Interface to inquire a/c status & a/c balance for a given customer from the core system

1 mark

91 • This should be an online real time interface 1 mark92 SWIFT interface should support both Incoming and

Outgoing message processing automatically. 1 mark

of 274


93 • This interface should be able to receive SWIFT messages from an outside location and should be able to create transactions or to apply the new requests to the relevant prevailing transactions with only single click

1 mark

94 Interface to treasury for currency exchange rates 1 mark95 Online real time interface for treasury for special

exchange rates from treasury 1 mark

96 • With this interface acknowledgement /rejection should be possible by transaction initiation party

1 mark

97 • if accepted, should apply to the transaction with the reference number given by the treasury

1 mark

98 Interface for position reporting to treasury whenever a currency conversion takes place

1 mark

99 Interface to e-mail server 1 mark100

• This should be an online real time interface 1 mark

101

Interface to SMS server 1 mark

102

• This should be an online real time interface 1 mark

103

Interface to - Interbank online Payment System‖ should facilitate pre-defined currencies separately.

1 mark

104

1 mark

105

Interface with DMS should support all Trade Finance document handling

1 mark

106

Common Interface for external servers which could be setup according to bank needs.

1 mark

107

• Through this interface it should be possible to transfer file/s to required external servers. e.g. for Customs, Central Bank

1 mark

108

For all Interfaces system should cover data pull out and push in from other software systems of the bank

1 mark

Security and Control109

System should use the employee’s provident fund number as the user ID for the internal users. In addition, user details should be available in the system for Inquiry or report. For eg. name , creation date, user privileges, termination date, department.

1 mark

110

Application Manager should be able to handle the access granting facility for application functions .According to the assigned privileges, user should either be able to access the function or he/she is restricted to access it.

1 mark

111

Facility should be there to handle the following as parameters in order to cater bank’s password policy.

1 mark

112 1 Length of the password 1 mark

of 274


113 2 Complexity of the password 1 mark

114 3 Duration of password expiration 1 mark

115 4 Number of invalid login attempts allowed 1 mark

116

System should log all the unsuccessful login attempts with the attempted user ID, date, time, and the remote workstation.

1 mark

117

System should compel the users to change the password at the initial login and whenever the password is reset by the administrator

1 mark

118

System should encrypt all the confidential information when being stored in the database and while being transferred through networks.

1 mark

119

System should maintain hash values of the passwords when being stored in the database.

1 mark

120 System should be browser independent 1 mark

121

System should log all the activities performed by users including the system administrators, with the details such as user ID, Date, Time, action performed and work station ID, success or failure. In addition, all the interface transactions should be able to separately identified.

1 mark

122

System should facilitate auto archival of the log entries after a parameterized value of size/ number of days.

1 mark

123

System should automatically logout the users after a predefined period of being idle.

1 mark

124

System should allow parameterizing the time duration for session timeouts.

1 mark

125

System should automatically lock the users who have not logged into the system for a predefined period and this period should be parameterized.

1 mark

126

System should allow the administrators to manually lock the users/ unlock the users and all the events should be logged.

1 mark

127

System should validate all the data input fields in order to prevent attacks such as SQL injections.

1 mark

128

System should restrict to the users to log into the system only from one workstation at a time

1 mark

129

System should allow the users to build queries and generate reports from database/ audit trails.

1 mark

130

System should have flexibility of providing any exception report. This report should be accessible only for the authorized authorities.

1 mark

131

A report should be generated indicating the success/ failure of the batch processes. Any failure should be

1 mark

of 274


recorded with the failed item and the reason for failure.132

System should support segregation of duties. (The same user who makes the data entry should not be allowed to authorize)

1 mark

133

System may maintain the sessions in a mechanism other than cookies.

1 mark

134

No direct access to the database should be allowed for the application users.

1 mark

133

End users should not be displayed the directory path of the resources while being accessed specially through web browsers.

1 mark

134

Application should handle all possible exceptional and erroneous events and appropriate user friendly error messages should be displayed. i.e. server level messages should not be displayed to the end user

1 mark

2.2.2.1 Other Technical Requirements Evaluation (123 Marks)

Evaluation Criteria Marks

General and Mandatory requirements

The system should run on the latest release of Oracle database, Application server(jboss or weblogic etc.).

1 mark

The system should be compatible with Redhat and/or Oracle Linux Operating system.

1 mark

The system should be Cloud ready, and allow for multitenant deployment - inhouse and on Public cloud

1 mark

The system should support and integrate with ISO 8583 messaging Standards- Mandatory

1 mark

The system should be Componentized designed 1 markThe system should support application Clustering at application level 1 markThe system should have an Open API (Application Programming Interfaces ) interface to integrate with other existing and new 3rd party systems

1 mark

The system should have automated code samples for all processes for ease of solution development and code re-use

1 mark

The system should be able to integrate with any ATM switch/Payment gateway

1 mark

The system should provide High Level Encryption of Customer Data both at rest and on transit

1 mark

The system should provide Report Writer for building reports on demand basis

1 mark

The system should be able to seamless integrate with Card Issuing System and provide a single interface for Customer records acquisition and validation

1 mark

of 274


The system should be able to support card generation for joint account holders, and or account with many mandates

1 mark

The system should be able to allow for automatic posting of Credits to customer accounts once Cheque truncation at Branch level

1 mark

The system should be able to send Dr and Cr notifications to customers in real time and automatically

1 mark

The system should be able to automate End of Day/ Start of Day Activities

1 mark

The system should be able to integrate with (MFA)Multifactor Authentication Solutions for bank staff login.

1 mark

The system should be able to integrate with SIEM solution for event correlation and analysis

1 mark

The system should be able to support biometric signature for over the counter customer transactions.

1 mark

The system should support bulk file upload of transactions (Credits and debits)

1 mark

The system should support transfer of accounts from one branch to another

1 mark

The system should support charge waivers at product and account level

1 mark

The system should support automatic mailing of statements during EOM

1 mark

The system should capture unique transaction codes for all transactions(e.g. cash deposit, cash withdrawal etc.)

1 mark

The system should enable transaction categorization data to be collected efficiently, using a simple interface and pre-defined lists of values for each category variable e.g. Cash deposit, EFT, etc.

1 mark

Associate transactions with Profiles that define active data fields, default value logic for transactions.

1 mark

The system should distinguish customer & system initiated transactions using unique transaction codes.

1 mark

Ability to define a single product for multiple currencies instead of separate products for each currency

1 mark

The system should be able to do validation for black listed customers 1 markThe system should allow multiple search criteria on customers(Id, Passport, Company registration number etc.)

1 mark

The system should provide ability to view customer closed customer accounts data and past transactions.

1 mark

The system should provide a user definable workflow for opening of Accounts

1 mark

The system should provide ability to exempt Savings A/c’s below minimum balance from accruing interest

1 mark

The system should provide a way of exempting some account above some amount from charges e.g. ledger fees

1 mark

Facility to capture transaction description/narrative to be printed & viewed on customer statements and enquires

1 mark

Possibility to classify accounts into different types 1 markRestriction on Credit / Debit transactions at the account / product level

1 mark

of 274


Automatic validation of exception conditions while performing transactions

1 mark

End of Day checks for incomplete transactions during branch sign out.

1 mark

End of Day checks on transactions posted but not authorized 1 markAutomatic processing of Inter Branch transactions 1 mark Automatic printing of vouchers and advices during transaction posting

1 mark


1 mark


1 mark

The system should create audit log entries for all configuration changes while retaining old values

1 mark

Hardware and Software RequirementsThe system should scope and provide detailed requirements for both test and development, production, and DR site. This should form part of the solution pricing and to be delivered by the vendor; This includes: -

1 mark

Server requirements consistent with System baseline configuration and various workloads - Number of Physical and virtual servers for both sites

1 mark

Operating system licenses as per the solution baseline recommendations

1 mark

Database systems and various licensing for the same 1 markCentral Data Storage scoping, and proposal for the same in line with best practice for the proposed system, and projected growth rates for both sites

1 mark

Network scoping, and proposed network devices to support the solution. This includes SAN switching, and backbone network to support integrations at Primary Site and Disaster Recovery Sites

1 mark

Tools and licensing to enable Clustered system configuration at application level

1 mark

Tools and licensing to enable database active setup and replication to Disaster Recover sites

1 mark

Business Continuity PlanningRedundancy and Business Continuity/Disaster Recovery 1 markSystem server and client software shall maintain its integrity in case of power failures and abrupt shutdowns.

1 mark

System shall be capable of restarting and recovering after system failure with no loss of data or software components.

1 mark

System shall provide the capability to identify the existence of program and/or system discrepancies and issue an alert to the system administrator.

1 mark

System shall provide ability to limit the types of operations (e.g., read, write, delete, data dictionary modification) that can be performed by individual users on given data or program files.

1 mark

System shall provide Incremental, differential, and full backups and restore of the database, core and customized software, software and

1 mark

of 274


database configuration options, user preferences and rights, etc.System shall provide a robust hardware infrastructure that can support high availability, load tolerance, real-time failover, as well integration into the bank offsite disaster recovery infrastructure. This includes:

1 mark

Individual server configuration, e.g. clustering (physical and virtual) 1 markCentral data storage configuration (SAN), with High IOPs performance

1 mark

Server and network configuration 1 markSystem shall provide a disaster recovery solution including a complete offsite server and networking installation that has the capability to roll from the primary site to this offsite location within a 24-hour recovery window. This roll over shall include all applications and data.

1 mark

ScalabilityThe selected vendor shall analyze current and projected future system volumes. The selected vendor shall provide a system that shall accommodate anticipated transaction levels using these analysis results. The system, including programs, database, and ancillary hardware and software systems shall be able to retain its performance levels when adding additional users, functions, and data. Please indicate how your solution(s) would address the following scalability issues:

1 mark

Maintaining a consistent throughput with increased transaction rates 1 markAvoiding high levels of persistent disk I/O 1 markMinimizing network traffic between the client application and the server

1 mark

Balancing the response time needs of mission critical business with other applications

1 mark

Cost-effective plan for implementing "Scale-Up" systems in the event of unexpected growth

1 mark

Optimizing database indexing techniques 1 markSystem AdministrationSystem shall provide administration tools and procedures for the ongoing support and maintenance, including customization, of the proposed solution. This includes:

1 mark

Database Administration Tools - Specify which tools are provided by the vendor and which are provided by the database vendor

1 mark

O.S Administration Tools - Specify the tools provided by the contractor and which are provided by the system vendor

1 mark

System Administration Tools - Specify any tools being proposed to support or supplement the application solution being proposed as well as for support of any third-party software

1 mark

System shall provide ability for users who encounter usage or technical problems receive clear error messages relating to:

1 mark

The exact status of the transaction 1 markThe options for on-line help 1 markThe options for additional help including reason and

possible solution1 mark

of 274


SecurityThe system shall comply with all bank mandated security protocols and standards that apply.

1 mark

The system shall provide the ability to encrypt selected data fields. 1 markThe system shall provide centralized user management (add, delete, change, access levels etc.).

1 mark

The system shall provide users ability to change their own password. 1 markThe system shall provide integration with the system user logon ID and password and the existing operating system(s) (single logon).

1 mark


1 mark


1 mark


1 mark


1 mark

Row/field level on data elements in databases 1 markAccess to system functionality or modules 1 markAccess to specific fields or screens in the user interface 1 markThe system shall provide users ability to change their own password. 1 markThe system shall provide integration with the system user logon ID and password and the existing operating system(s) (single logon).

1 mark


1 mark


1 mark


1 mark


1 mark

Row/field level on data elements in databases 1 markAccess to system functionality or modules 1 markAccess to specific fields or screens in the user interface 1 mark

The system should be securely accessed Via https if web based or secure connection if client is installed in user PCs. Passwords in configuration files should be encrypted

1 mark

Security controlsAbility to restrict logins based on working times e.g. outside working hours

1 mark

Ability to restrict multiple sessions in different workstations 1 markSystem shall provide ability to easily upgrade to future operating systems, database and third party software and utilities.

1 mark

System shall provide an open architecture for user and system interfaces based on current and industry-accepted standards,

1 mark

of 274


methods, and protocols such as HTTP, XML, SOAP, FTP, etc.All database edits, notifications and customer transactions must be logged for audit. Users must be able to query the logs for specific events or recent activities and view filtered log reports, using a simple interface with fields for search and sorting parameters.

1 mark

LicensingState the licensing option(perpetual pricing or subscription pricing) 1 markData migration from previous systems 1 markInterfacesATM / POS interface as per ISO 8583 Standard 1 markISO Interfaces for Mobile and internet banking systems 1 markInterface with Cheque book printing machine - Linked server support functionalities

1 mark

RTGS / SWIFT interface 1 markCTS (Cheque Truncation System) 1 markInterface with Financial Inclusion / hand held devices 1 markInterface with MICR machine 1 markOpen API Interface to handle any third party interfaces 1 markExport transaction data to other systems on a daily basis 1 markProvide Secure exchange of data between various systems in the Bank e.g. encryption of Data exchanges to Cheque clearing, SWIFT, and any other systems

1 mark

User InterfaceSystem shall present data to users such that a minimum of navigational effort is required. The data elements required to complete a job function, whether to inquire/read only or data entry, must be readily available.

1 mark

System shall provide a user interface that integrates information from multiple components into a unified display by business area or work type.

1 mark

System shall provide ability for the user to complete each step in the workflow process within a given screen (e.g., the user will not need to navigate multiple screens to complete a task in the workflow).

1 mark

System shall provide ability to create multiple user levels based on user roles (e.g., Teller) and respond differently to each role

1 mark

System shall provide a method to "drill down" to related data as needed by job function.

1 mark

2.2.2.2 Reporting Requirements Evaluation (56 Marks)Evaluation Criteria Mar

ksAbility of the system to generate online real time MIS(Management Information System) and ad-hoc reports

1 mark

Ability to generate all CBK regulatory reports1 mark

Ability to link branches to the H.O for consolidated views.1 mark

of 274


Ability to collate information of various branches and its departments to the head office for MIS reporting.

1 mark

Ability of the higher level to generate reports of the lower level(such as branch level), if required.

1 mark

Ability to define any report / MIS printing at the Branch, region or H.O based upon defined parameters e.g. at the time of end-of-day, occurrence of a particular event, start-of-day.

1 mark

Ability of the system to upload data received in any electronic format from branches outside the core banking system for consolidation and merging for reporting purposes.

1 mark

Ability to define reports as compulsory report and print them at user definable periods e.g. end of day, beginning of day etc. The system should also provide an option to allow the user (Bank) to select the location of each report printing. (E.g. at the head office and branches or only at the branches.)

1 mark

Ability to schedule spooling/printing of non – critical reports e.g. x report after every 10 days etc.

1 mark

Specify the format and layout of reports1 mark

Summarize and total the information to be reported1 mark

Select records to be included in the report1 mark

Select details from each record to be included1 mark

Perform arithmetic calculation on the information selected1 mark

Download data to/from third party software.1 mark

Ability to download data to any user definable formats e.g. flat files, word documents, excel sheets etc.

1 mark

Ability to print reports as on a particular date, any user defined date or range of dates for the selected criteria (e.g. stop payments, transaction details etc.)

1 mark

Ability to interface with other banking application used by the bank e.g. treasury, risk management etc. or 3rd party systems e.g. RTGS, etc. or legacy systems of the bank for periodic / on - line consolidation of MIS data

1 mark

Ability to restrict access to reports based upon user privileges defined in the system

1 mark

Ability to generate any adhoc report as required by the branches , departments, head office and management from time to time with least effort

1 mark

Product - wise, scheme- wise, account - wise analysis detailing the performance of various accounts , products and schemes for a particular region / bank as a whole

1 mark

Expense should typically cover interest expense, and fee & commission expense.

1 mark

currency - wise, product / package - wise, branch - wise balances of all liabilities across the bank

1 mark

customer / group profitability per product per customer / group per annum 1

of 274


expressed in terms of net revenue earned through the customer markReport Types

Cost of funds for each liability product and across all liability products1 mark

Net interest income analysis detailing the interest earned and paid1 mark

CBK regulatory reports1 mark

Return on assets1 mark

Return on equity1 mark

Earning on assets to total assets1 mark

Loans to deposits1 mark

Capital adequacy1 mark

Business / branch1 mark

Gross profit / branch1 mark

Gross Non Performing Assets ratio1 mark

Basel Capital Accord1 mark

Ability to accommodate multiple flagging codes at the customer account level in any sub ledger portfolio, to facilitate the various classification requirements of specific reports.

1 mark

Ability to produce report of total deposits to and withdrawals from a given product portfolio over a given period (e.g. monthly).

1 mark

Ability to extract relevant data from any sub ledger system and format according to requirements of specific statutory/MIS reports.

1 mark

Ability to express balances of specific sub ledger asset and liability portfolios in given groups aged according to remaining maturity.

1 mark

Ability to generate report of sub ledger liability accounts which are inactive for a given period formatted to show details of addresses, branch, opening date, currency, etc..

1 mark

Ability to display customer balances in any sub ledger portfolio according to interest rate groups and in predefined economic sectors (by currency where required).

1 mark

Ability to display all foreign currency assets and liabilities in a single designated foreign currency

1 mark

Ability to calculate current period and historical trend must be available.1 mark

Ability to drill down from Group/Customer/Account level to detailed transaction level and to summarize from transaction to Group level.

1 mark

Profitability should be based on actual comprehensive income and expense 1

of 274


including overheads. Source should be customer records/GL. markIncome should typically cover interest income, fee & commission income, exchange income, revaluation gain/loss, charges like statement charges, telex charges etc.,

1 mark

All fee, commission, charges, interest waived must also be considered for assessing the profitability.

1 mark

Option to calculate net interest income directly by applying a % margin on the loan balance or by applying pool rates i.e. cost of funding.

1 mark

Ability to share income/expense between multiple business units based on user definable distribution matrix.

1 mark

System should restate history for effects of back valuation and adjustments to balances, averages, income and expense.

1 mark

Provide balance sheet daily average balances report / per business unit along P /L separately for each business unit.

1 mark

Auto generation of specified reports on specific / predetermined dates1 mark

Generation of reports per RO/RM - productivity.1 mark

The solution should allow for 3rd party reporting tools to pull data from the solution to satisfy unanticipated reporting requirements

1 mark

Where applicable, the end-user solution shall support either Google Chrome or Internet Explorer 11+ for the browser-based components of their solution.

1 mark

2.2.2.3 Training Requirements Evaluation (6 Marks)Evaluation Criteria MarksAll training aids and manuals shall be provided in electronic format. Training may be provided as video recordings. 1 markApplication training for end Users, and additional training for Administrative Users. Provide one chapter of the training materials as an example. 1 markSystem training for ICT staff 1 markMaintenance and troubleshooting training for Application Support staff, for hardware interfaces and software. 1 markEnable the bank to configure a Training environment emulating the bank's production configuration, with simulated transactions. 1 markOn-site or online training as requested for functional topics, Refresher sessions, Updates and New Functions 1 mark

2.2.2.4 System Support Evaluation (9 Marks)Evaluation Criteria. MarksGeneral application support to be available by online communication or telephone, during business hours.

1 mark

Verify all hardware interfaces operate correctly with the new system.

1 mark

Updates to the application, manuals and help system must be 1 mark

of 274


supplied as they are released.Updates must not break existing custom functionality. 1 markHigh availability configuration with redundant servers to be commissioned and tested.

1 mark

Coordinate with IT Support team to document hardware setup 1 markEnable tests to be run with simulated transactions from a stored script in the Testing configuration.

1 mark

Proponent must report regression testing results for fixes and new features. In particular, document issues with customizations.

1 mark

Enable system monitoring and event logging for troubleshooting problems.

1 mark

2.2.2.5 Documentation Requirements Evaluation (20 Marks)Requirements. MarksAll documents should be provided in electronic format, and hard copy format where available

1 mark

The vendor shall provide all documents relating to project deliverables:- Project Implementation Plan and Schedule (PIPS) - Solution Design Document (SDD)- Solution Testing Plan (STP)- Solution Acceptance Criteria- Solution Administration Guide- Integration and API Procedures- User Training Documents- Solution Issues and Defect Report- Solution Test Results Report- Delivery Confirmation

1 Mark per document(10 Marks)

The vendor shall include all documentation for their proposed solution including:a. End-user manualb. Installation of solution on servers and clientsc. Trouble-shooting common hardware problemsd. Administrative Guide: Installation, operation and maintenance of server solution including databasee. Configuration of the Solutionf. Integration methods - e.g. API, web servicesg. High Availability configuration and operation; failover testsh. Disaster Recovery Proceduresi. Data flow diagrams with security and encryption descriptions

1 Mark per Document (9 Marks)

2.2.3 Loan Origination Requirements Evaluation (81 Marks)

Evaluation Criteria Marks

Ref# Feature

of 274


1 Search1.1 Application

searchSearch based on the following fields1. Application Id or Passport Number or any other national ID2. First Name, Middle name, Last name or name in native language3. Person who recorded the application4. Application status 5. Account number or /and Client code for existing customers 6. Previously Declined/Deffered applications

1 mark

2 Application Creation

2.01 Support for multiple types of loans and overdrafts

1. Supports loan applications for fresh loans /limits (i.e. Overdraft ,Guarantee , LPO line, Credit Line) as well as renewal of facilities, restructures, loan modifications (term extension, limit extension, rescheduling, change in interest rates)

1 mark

2.02 Customer Search

1. Search associated with the CIF id field in the data entry screen. The Search URL is configurable to open the search page of any CRM system.2. Allows the user to search against the customer database maintained in the system during data entry3. If no matches are found, then the system facilitates and mandates creation of a CIF, at the time of application entry.

1 mark

2.03 CIF Generation

Ability for the system to comprehensively capture customer details

1 mark

2.04 Expandable / Collapsible Data Entry Screen

System to allow user navigation on various screens without exiting any

1 mark

2.05 Multiple applicants to application

1. Supports multiple applicants, each with varying capacities and roles. 2. There should be a minimum of one applicant in the role of a borrower. 3. Applicant types can be defined in the system as per the business needs.4 Captures various details across personal, employment and address details.

1 mark

2.06 Process identification based on product attributes

1. The Origination system facilitates defining different process flows for each super product, product and credit scheme. For instance, the process flow defined for Consumer goods and Mortgage can be different2. Process flow to product attribute mapping is configurable in the system.

1 mark

of 274


2.07 Applicant details capture

1. Captures the personal , address and employment details for every applicant.2. Captures the family members' name and national id, and their relation to the applicant.3. Address Types - Office, Residence, Mailing (Address types are configurable)4. Feature to record details (name, address and national id) of 2 references. 5. Related/ Associated companies.

1 mark

2.08 Pricing 1. Capture Interest rate, commissions, fees etc. . Able to support risk based pricing. Base rate plus a margin. As well as Variable/Fixed rates, Flat rate/Reducing balance interest rate

1 mark

2.09 Asset details capture

1. Captures the asset type, location, description of the Asset, OMV,FSV, LTV and the valuation currency and the o/s loan commitment against each asset. The name of valuer and valuation date.

1 mark

2.10 Liability details

Records Liability Type, Originating FI, Liability amount, estimated monthly commitment, adjusted monthly/quarterly/ semi-annually/ annual/ balloon commitment.

1 mark

2.11 Income Details

Records income source and currency, income frequency and the amount

1 mark

2.12 Expense Details

Captures Expense type, amount and the applicable currency

1 mark

2.13 Collateral capture

1. Captures the details of the primary collateral that would be linked to the loan account.2. Integrated with the Collateral module for creation/selection of an asset as a collateral

1 mark

2.14 Support for Multiple collaterals types

1. Supports capture of multiple collateral types for the same application2. Supports in capturing detailed collateral related information like collateral type, location, description of the asset, OMV,FSV,LTV and charge status and the valuation currency and the o/s loan commitment against each asset. 3. Supports collaterals to be defined as sharable and non-sharable collaterals4. Supports restriction of collateral to a single credit line5. Supports collateralization of assets while collateral creation6. Capture of collateral specific information6. The following asset types can be collateralized (Can be configured) 1. Fixed Deposit 2. Guarantee 3. Pledge / hypothecation 4. Mortgage

1 mark

of 274


5. Lien on stock and bad debts 6. Security Cheques 7. Vehicle

2.15 Single collateral supporting multiple applications/ Linking of collateral to more than one account/guarantor

Collateral ids can be linked to multiple applications subject to the sum total of percent of utilisation of the underlying asset(s) not exceeding 100%

1 mark

2.16 Application edit prior to contracting

Allow modifications to applications before the contract is finalised.

1 mark

3 DeDuplication

3.01 Internal Dedupe function

1. Dedupe is done for all the parties to the application.2. Search strings are derived from the applicant data, after applying a series of formula/computations on the same3. More than one applicant data can be merged together to build a search string.4. Deduplication is an auto stage process.5. User interaction is at the review stage. While reviewing the matched records, the user can opt to accept a match, on which the CIF id of the selected match would replace the existing CIF id, if any, in the application data.6. Acceptance of a match, even for one party, is not mandatory for the application to be processed further.

1 mark

4 Credit Approval

4.01 Objective Credit Policy Checks

1. System driven.2. Credit Policy rules can be configured using the Rules Engine module.3. Policy evaluation is automatically done by the system.4. Policy check can be executed at different stages depending the user requirement. 5. Different Policies for different products can be exercised.

1 mark

4.02 History of credit policy changes

The Origination system maintains a history of all changes in the policy evaluation results, as a result of iterations and various modifications to the applications

1 mark

of 274


4.03 LTV & PTI Calculation

1. Loan To Value (LTV) and Payment To Income (PTI) computations are done as a part of the Credit Score transaction. 2. Computation logic is configurable through the Rules Engine module.

1 mark

4.04 Credit Scoring

1. System driven.2. Credit Scoring rules can be configured using the Rules Engine module.3. Score computation is automatically done by the system.4. Credit scoring can be done at different stages of an application for a product and different products can have different scoring sheets at the will of the user 5. Scoring module can be configured per product.

1 mark

4.05 System recommended loan amounts

System recommended loan amount is computed as a part of the credit score transaction.

1 mark

4.06 Existing Asset & Liability view

1. Details of all assets and liabilities that have been recorded during the data entry stage, is available as a link in the decision screens.

1 mark

4.07 Neglist Results

1. Decisioning and Underwriting modules have a link to view neglist matches for all the applicants.

1 mark

4.08 Credit Bureau Results

Support integration with the Credit Reference Bureau system.

1 mark

4.09 Loan Terms and conditions review

1. The edit offer link in the credit decisioning stage provides the facility to edit or modify the terms and conditions for the loan to be approved.2. This feature of the Origination system provides a concise view of the loan amount requested, loan tenure, rate of interest, repayment frequency and mode of repayment.

1 mark

4.10 Repayment schedule generation

1. Repayment schedule is supported during decisioning and underwriting stages.2. Supports generation various repayment schedules like equated, varying dates and amounts, Balloon payments etc.

1 mark

4.11 Edit Data Entry

1. The Origination system supports the credit team’s decision to send back an application for correction of terms or addition/deletion of applicants. 2. The credit team can also edit the application details and proceed with decisioning.

1 mark

4.12 Refresh of Scoring, Policy, LTV & PTI calculation

1. The user can manually initiate recomputation of scoring and policy evaluation, from the decisioning stages, using the 'Redo Score and Policy evaluation, as and when data is changed by using Edit data

1 mark

of 274


4.13 Document collection

1. Can be updated at any stage of application processing.2. Checklist can be different for each applicant type.3. System mandates collection of mandatory documents to proceed with contracting.

1 mark

5 Verification5.01 Rule based

Verification Grid Marking

Verification and grid marking rules configured in Rules Engine

1 mark

5.02 Grid marking at application level

The user can override and waive verifications that have been marked for an application, through the grid marking process

1 mark


1. Rules for agency allocation can be configured using the Rules Engine module.2. The user can select one of the shortlisted agencies and assign the verification for that application, to that agency.

1 mark

5.04 Sourcing details capture

1. Records the dealer who has sourced the application, the loan purpose and the sourcing channel.2. Loan purpose and Sourcing channel can be defined based on business needs, at the time of implementation

1 mark

6 Underwriting

6.01 System Recommendation

1. Origination computes the recommended loan amount for every application, based on the rules configured in Rules Engine.

1 mark

6.02 User override 1. Override of the system recommended limit can be done by the credit approver.

1 mark

6.03 Multiple levels of approvals both individual and group(committee)

1. System currently supports any number of level of underwriting (Users receive email alerts)2. Deviation entry level for underwriting is configured in the Rules Engine3. Approval from the entry level moves the application to Contracting stage.4. System also supports a recommend feature to escalate the application to the next level of underwriting. 5. The system should allow exceptional approval

1 mark

6.04 Approve, Decline, Cancel, reinitiate credit approval.

1. The user can either approver or cancel or reject or push back an application to the credit approval stage.2. The reasons for the decisions of the approval from underwriter can be recorded 3. The system provides a maintainable list of decision linked reason codes, at each stage of decision making. The user can select one or

1 mark

of 274


more reason codes as applicable.6.05 Approval

historyAll decision screens display the decision history and comments provided by the earlier decision makers.

1 mark

6.06 Approval Authority Matrix

Business Rules Engine is used to configure the underwriting delegation matrix.

1 mark

6.07 Application Referrals

1. System also supports a recommend feature to escalate the application to the next level of underwriting.

1 mark

7 Reject7.01 Reject Review

Queue1. Reject review queue displays the decision history.2. The user can select the mode of reject note communication.

1 mark

7.02 Restart from Reject

1. Restart move the application to the credit approval stage.

1 mark

8 Contracting and Disbursal

8.01 Approval for contracting

Contracting is the final stage of application processing in Origination. Approval at this stage hands off the details to the Lending system for disbursal.

1 mark

8.02 Contract advices

Configured using the Custom module. 1 mark

8.03 Disbursal handoff

All booking details are recorded at the contracting stage, through the booking module in the Lending system. This triggers a disbursal schedule for the application.

1 mark

9 Master Maintenances

9.01 Document Master

1. Document codes are assigned to various documents.2. Each document can be classified as either as an income proof or address proof or as a ID proof.

1 mark

9.02 Document Group

1. Different documents can be grouped together for a given combination of super product, product, customer type, applicant type and loan scheme.2. For each document added to a group, the collection mode(copy, original) and the collection frequency is defined.3. The system also allows to define mandatory and optional documents within the group scope.4. The system generated the document collection checklist based on this grouping.

1 mark

of 274


9.03 General Parameter

A separate master is available to maintain the LOV for various field elements. These include applicant type, payment frequency, credit decisions,

1 mark


1. System shortlists an agent by following a round-robin allocation logic. 2. The user can override the system allocation in the Pre-CPV stage

1 mark

9.05 Neglist maintenance

Masters provides an independent maintenance for Neglisted customers. The user can key in the details of neglisted customers using this module.

1 mark

10 Document Management & Imaging and Notepad

10.01

Document checklist generation

1. System generates separate document checklist for each applicant type.2. Document checklist generation is based the document group maintenance done for a given product and applicant type.

1 mark

10.02

Document Receipt

The user marks a document as collected, there by acknowledging receipt of a document.

1 mark

10.03

Document Waiver

Optional documents can be waived. Mandatory documents cannot be waived.

1 mark

10.04

Document Deferral

1. When the user defers a document, the system mandates the deferred date to be entered.2. Collection of a document can be deffered to a date marked as deferred date.

1 mark

10.05

Additional document

1. Documents that are not a part of the checklist but have still been collected, can be recorded under the additional documents section.2. The user can add any number of additional documents.

1 mark

10.06

Mandatory & Optional classification for documents

Mandatory and optional classification is defined at the time of document grouping. The same is reflected in the collection checklist generated for every application.

1 mark

10.07

Upload of document images

There is a separate link for document upload. This is available from the document collection checklist and also independently, as a link in the page header at every stage.

1 mark

10.08

Document image view

View image link is found in the document collection checklist and also as a link in the page header at every stage.

1 mark

11 Customer Advice Generation

11.0 Advice 1. Through the Customer Communication 1

of 274


1 Templates module, the system supports configuration of customer advices.2. These templates can be configured to embed application data (customer information, loan offer terms and the like)2. Customer advices can be viewed from the decision making stages.

mark

11.02

Advice communication

The System supports the following communication modes1. E-Mail2. FAX3. SMS

1 mark

12 MIS Reports12.0

1MIS Reports 1. MIS Reports can be configured to suit the

business needs, using the Reports tool.2. The report output can be in any one of the following formats a) CSV b) HTML c) PDF d) Excel e)Word

1 mark

12.02

Data Handoffs

1. Reports can be used to configure data hand off files2. The handoff would be in a Excel/ PDF format.

1 mark

13 Process Configuration

13.01

Business Process Setup

1. Workflow is used to configure the business process.2. The process studio is a graphics based canvas where the user can configure various stages of a business and sequence the same.

1 mark

13.02

Parallel Processing

Workflow supports parallel processing wherein an application can be processed across more than one stage of activity

1 mark

13.03

Access Control

Stage level access restrictions can be configured. 1 mark

13.04

Version control

All versions of a process are available for viewing, at any given point of time.

1 mark

13.05

Maker Checker facility

Any modification done in the Workflow, come into effect only after the same has been authorized. The maker and authorizer cannot be the same.

1 mark

14 Utilities14.0

1Notes - Add Additional comments and observation, can be

recorded at every stage, by each user, using the Notepad - Add link.

1 mark

14.0 View Notes 1. Comments and observations recorded by each 1

of 274


2 user at each stage of application processing is tagged with the application id.2. Such recordings can be viewed by all users at all stages using the Notepad view link.

mark

14.03

TAT Summary This is available as a link at all stages of application processing. The elapsed time at each stage is displayed. The summary includes stages where system has processed the application without any manual intervention.

1 mark

15 Business Rules

1. Does the system have a inbuilt business rules engine to configure business rules.

1 mark

2. Are the business rules configurable by bank users themselves without vendor intervention

1 mark

3. How easy is to amend the rules in your system 1 mark

4. Does the business rules system support versioning for easier rollback

1 mark

5. Does the system have a inbuilt rule testing option to simulate the rules as part of mock testing

1 mark

6. Is there any limitation to number of rules that can be configured as part of the system.

1 mark

7. Does the system have a means to replicate business rules for easier configuration

1 mark

8. Does the system have a maker checker concept for authorization of rules.

1 mark

16Integration with other platforms

Interface with Bank’s AML/Blacklist and Risk based pricing model and any other systems

1 mark

2.2.4 Loan Management Requirements Evaluation (271 Marks)S.No Feature Marks

1.1 The system should allow real-time centralised maintenance of various types of rates for products, including but not limited to:

1.1.1 Interest rate 1 mark1.1.2 Fee rate 1 mark1.1.3 Tax rate 1 mark1.1.4 Commission / bonus 1 mark1.1.5 Penalty interest 1 mark

1.2 Describe the mechanism and tools to allow users to define the terms applied for rates of credit products.

1 mark

1.3 Describe the mechanism and tools for setting up rate calculation formulas/sets using different base rates that were pre-defined in the Common Functionality to be applied to

1 mark

of 274


credit products.1.4 Describe the mechanism and tools for assigning interest

margin to the base interest rate to determine the applicable rate for customers.

1 mark

1.5 The system should allow waiver of rates for any account. 1 mark1.6 Ability to support calculation of compound interest (interest on

interest) for loans.1 mark

1.7 The system should provide the capability to calculate and handle various rates.

1 mark

1.7.1 Interest rate 1 mark1.7.2 Fee rate 1 mark1.7.3 Tax rate 1 mark1.7.4 Commission / bonus 1 mark1.7.5 Penalty interest rate 1 mark

1.8 Describe the method of calculating rates for different currencies.

1 mark

1.9 The system should allow various time-based calculations of the rates defined by users, including but not limited to the following times:

1 mark

1.9.1 Daily 1 mark1.9.2 Weekly 1 mark1.9.3 Monthly 1 mark1.9.4 Quarterly 1 mark1.9.5 Termly (School Term) 1 mark1.9.6 Six monthly 1 mark1.9.7 Yearly (including leap years) 1 mark

2 Detailed Interest Rate Requirements2.1 Ability to define different interest rates in a flexible way. 1 mark2.2 The system should support multi interest rate types and

provide interest calculation, including but not limited to:1 mark

2.2.1 Fixed interest rate 1 mark2.2.2 Floating interest rate (periodically or ad hoc) 1 mark2.2.3 Fixed interest rate but the frequency/term is changeable 1 mark2.2.4 Progressive interest rate 1 mark2.2.5 Simple interest 1 mark2.2.6 Compound interest 1 mark2.2.7 Flat rate 1 mark

2.3 The system should allow various time-based calculations of the interest rates as defined by users, including but not limited to the following times:

2.3.1 Daily 1 mark2.3.2 Weekly 1 mark2.3.3 Monthly 1 mark2.3.4 Quarterly 1 mark2.3.5 Termly (School Term) 1 mark2.3.6 Six monthly 1 mark

of 274


2.3.7 Yearly (including leap years) 1 mark2.4 The system should have the ability to define, set up and

compute the following items at least:2.4.1 The interest rate is set up for the loan and will not be changed

throughout the life of the loan1 mark

2.4.2 The interest rate is set up for different periods of time for the loan. For example: a loan’s interest rate for the 1st year is x%, for the next two years it is y%, and for the last two years it is z%

1 mark

2.4.3 Step-up 1 mark2.4.4 Step-down 1 mark

2.5 The system should have the ability to calculate interest rates for the instalment amounts on the following bases:

2.5.1 Daily 1 mark2.5.2 Weekly 1 mark2.5.3 Monthly 1 mark2.5.4 Termly (School Term) 1 mark2.5.5 Quarterly 1 mark2.5.6 Yearly 1 mark2.5.7 Bullet / balloon payment 1 mark

2.6 The system allows definition of base interest rate, ceiling and floor interest rate margin, interest rate for branches and head office by one or group of following criteria including but not limited to: - by % of base interest rate - by product- by customer group- by geographic areaThe Tenderer is to describe in detail in the proposed solution. The system allows definition of base interest rate, ceiling and floor interest rate margin, interest rate for branches and head office by one or group of following criteria including but not limited to:- by % of base interest rate - by product- by customer group- by geographic area

1 mark

2.7 Ability to simultaneously apply a variety of floating rate margins and define a variety of margins on one interest rate.

1 mark

2.8 System allows definition of penalty interest rate, ceiling and floor penalty interest rate, penalty rates used by branches and head office by one or a group of the following criteria including but not limited to:

- by % of base interest rate- by product- by customer group

1 mark

of 274


The Tenderer is to describe in detail the proposed solution. System allows definition of penalty interest rate, ceiling and floor penalty interest rate, penalty rates used by branches and head office by one or a group of the following criteria including but not limited to:

- by % of base interest rate- by product- by customer group- by geographic area

2.9 The system supports advance closure of loans with fixed interest rates.

1 mark

2.10. Ability to automatically collect interest according to a defined schedule or at the time of doing the transaction.

1 mark

2.11 The system supports calculating and re-posting if the product cycle is adjusted.

1 mark

2.12 The system allows flexibly to adjust interest rate cycles. 1 mark3 Detailed Fee and Charge Requirements

3.1 Ability to allow users to define fees associated with loans 1 mark3.2 Ability to define and flexibly calculate fees and charges

including but not limited to : flat, by proportion, by maturity, by min/max fee etc.

1 mark

3.3 Ability to calculate and collect the service fee automatically at a predefined frequency e.g. daily, weekly, monthly, quarterly, bi yearly, yearly, etc. or to allow ad hoc collection at the time of transaction.

1 mark

3.4 Ability to define, and auto calculate the fees related to any changes, amendment in the loan schedule (change of loan time, amount, and method) including but not limited to: commitment fee, pre-maturity repayment, early contract closing, co-sponsorship fee. The Tenderer is to describe this in detail.

1 mark

3.5 Support the calculation of additional interest due to the difference between the rate at the time of disbursement and the rate at the time of principal and interest payment.

1 mark

3.6 function to calculate and support partial payments 1 mark4 CREDIT LIMIT MANAGEMENT

Credit Limit Management for loan, guarantee, LC, overdraft, discount, factoring, corporate bond, credit card etc.

4.1 Describe in detail how to manage multi-dimensional limits according to the following criteria: products, customer, customer group, industry, collateral, economic region and internal customer.

1 mark

4.2 Manage multiple dimensions by product, customer, customer, industry code, collateral, economic area, internal customer, bank structure (whole bank, area, branch).

1 mark

4.3 System has the ability to set multiple-currency limits. 1 mark4.4 System should be able to manage credit limit by collateral, 1 mark

of 274


classification of limit by whole collateral, partly collateral or no collateral.The Tenderer is to describe in detail this function in the proposed solution.

4.5 Ability to automatically check credit limit against collateral linked to the loans (wholly or partly) as defined by the bank for customer, product, contract.

1 mark

4.6 Ability to set up and manage multi-tier limits (main limit, limit by product, sub-limit, sub-sub-limit etc.).

1 mark

4.7 Ability to automatically manage real-time reduction of the main limit by outstanding balance.

1 mark

4.8 Ability to manage the limit by revolving or non-revolving methods or combining of both

1 mark

4.9 Ability to adjust limit upwards and downwards during the validity period of credit limit.

1 mark

4.10 System allows users to establish temporary limits with specific beginning and closing dates.

1 mark

4.11 System has the ability to renew limits with back value dates. 1 mark4.12 System supports managing shared limits and non-shared

limits. In shared limits, total sub-limits can be more than or equal to the main limit. In non-shared limits, the cumulative total of sub-limits must be less than or equal to the main limit.

1 mark

4.13 Ability to manage limit by customer group, which is the total limit that could be shared/non-shared among customers/subsidiaries in the group; ability to manage limits of main unit and limits of subsidiary units.

1 mark

4.14 Ability to roll-up the limits to the parent limit. 1 mark4.15 Ability to post off-balance sheet for undisbursed amounts. 1 mark4.16 Ability to generate reports on expired limits; valid limits by

customer, customer group.1 mark

4.17 Ability to transfer the credit limit from one contract to another. 1 mark4.18 Ability to suspend a limit where the Credit team deems so 1 mark

5 REPAYMENT SCHEDULE/FREQUENCY SETUP

Setup a GL Account Distribution Set5.1 GL account distribution sets - Ability to allow the definition and

automatic generation of accounting entries to the GL1 mark

5.2 In the case customers do not have enough balance in the account for payment, the system supports calculating and automatically collecting the payment a day later or any customized time or when the customers' accounts have sufficient balance for payment.

1 mark

5.3 The system should allow for flagging of incoming payment for certain types of loans

1 mark

5.4 Automatically send messages to remind customers of payment one week before the payment deadline.

1 mark

6 PRODUCT SETUP/DEVELOPMENTLoan Products Setup/Definition

of 274


6.1 Provide the mechanism and tools to create diversified credit products with maximum level of automation and posting as required by the Bank including but not limited to the following.

1 mark

6.1.1 Record automatically to GL system 1 mark6.1.3 Products designed by area, region, branch 1 mark6.1.4 Product attribute is inherited from product level to account

level1 mark

6.2 The system should define the following criteria including but not limited to:

1 mark

6.2.1 Product name 1 mark6.2.2 Product type 1 mark6.2.3 Product code 1 mark6.2.4 Loan term 1 mark6.2.5 Principal amount 1 mark6.2.6 Currency 1 mark6.2.7 Interest rates applicable (e.g. normal interest, delinquent

interest, fixed and floating rate for different periods)1 mark

6.2.8 Capitalized interest 1 mark6.2.9 Loan classification rules e.g. for delinquency recognition 1 mark6.2.10 Staff loan 1 mark6.2.11 Product creator / owner 1 mark6.2.12 Transaction type 1 mark6.2.13 Product validity / expiry 1 mark6.2.14 Product criteria 1 mark6.2.15 Repayment mode 1 mark6.2.16 Interest calculation mode 1 mark6.2.17 Payment priority 1 mark6.2.18 Product limit 1 mark6.2.19 Loan purpose 1 mark6.2.20 Information of borrower 1 mark6.2.21 Support the input of one or multiple collateral (of different

currencies) to calculate the limits1 mark

6.2.22 Fee and charges type 1 mark6.3 System has the ability to create a new product by selecting

available characteristics and criteria from the existing products.

1 mark

6.4 Ability to upload files related to contracts and agreements (for example: appraisal records).

1 mark

6.5 Describe the method of defining/setting up and flexibly monitoring different loan products including but not limited to:

1 mark

6.5.1 Secured / collateralized loans 1 mark6.5.2 Unsecured loans 1 mark6.5.3 Revolving loans 1 mark6.5.4 Non-revolving loans 1 mark6.5.5 Syndicated loans 1 mark

6.6 Ability to input a pre-determined account for the automatic collection of due interest and principal.

1 mark

of 274


6.7 Ability to distribute, monitor and post the amount of accrued interest receivable from customer into different GL accounts.

1 mark

7 SPECIFIC REQUIREMENTS OF SOME LOAN PRODUCTSSyndicated Loan

7.1 System has ability to manage and handle Syndicated Loan. 1 mark

7.2 System has ability to manage limits of syndicated loans using different currencies.

1 mark

7.3 Ability to manage customer credit limits for syndicated loans in which the bank is the focal point

1 mark

7.4 Ability to manage and track all syndicated loan processes (tracking the money received from member banks, disbursing to customers, calculating distributed interest and fees, debt collection, risk handling, loan settlement…)

1 mark

7.5 Ability to collect repayments from customers and distribute them to member banks.

1 mark

7.6 Automatically generate notifications for repayments and send them to different participants through various channels such as email or fax etc…

1 mark

7.7 Ability to support maintenance of overdue syndicated loans. 1 mark7.8 Ability to track member banks’ information (name, contributed

amount, etc.)1 mark

8 OPERATIONS FOR CREDIT FUNCTIONSCreate and Manage Loans

8.1 Describe in detail the management mechanism for loan applications, loan contracts and accounts. Ability to create a unique loan account for each approved loan application (if any).

1 mark

8.2 Ability to fast open account and fulfil account information in order to improve customer service speed.

1 mark

8.3 Ability to provide the function to increase/ decrease the value of credit contracts.

1 mark

8.4 Ability to allow credit position to be managed separately for each loan.

1 mark

8.5 Ability to store all customers' loan files 1 markDisbursement

9.1 Allow report on the conditions that the documents must comply with before disbursement (according to the Bank's regulations for each loan purpose/product) to identify which documents customers need to provide after disbursement (Disbursement Checklist)

1 mark

9.1.2 Allows for creation a loan creation detail sheet prior to disbursement

1 mark

9.2 System supports multiple methods of disbursement and users can define such methods, some example includes:

1 mark

9.2.1 Single disbursement 1 mark9.2.2 Multiple disbursement 1 mark9.2.3 Disbursement in batch 1 mark

of 274


9.2.4 Full disbursement 1 mark9.2.5 Disbursement following defined schedule 1 mark9.2.6 Revolving 1 mark

9.3 Ability to generate, re-generate and manage disbursement schedule by amount and disbursement date.

1 mark

9.4 Ability to support post-dated disbursements. 1 mark9.5 Ability to issue customer advices letters upon configuration 1 mark9.6 Ability to issue an annual e-loan statement to borrower 1 mark10 Loan Management

10.1 Describe the mechanism for processing and managing problems arising with loans. These problems must be controlled by at least two levels of authority, and it should be based on the processing authority by amount, times, due date... Problems may include but not be limited to:

1 mark

10.1.1 Changes in interest (parameters, portion on current date, future date and back date for different methods of interest calculation)

1 mark

10.1.2 Change in fee on the current date, future date and back dated for different loans and their fee calculation methods

1 mark

10.1.3 Restructuring (change in loan amount, limit, term (date, repayment amount for each period, repayment date - support changing debt classification or not), loan renewal etc.

1 mark

10.2 Ability to automatically define penalty interest amount on past-due repayments and inform customers of this.

1 mark

10.3 Ability to waive, reduce interest (must be approved by authorised person).

1 mark

10.4 Ability to define and manage the extension time of due date. 1 mark10.5 Ability to automatically collect penalty interest and the waive

of penalty interest needs higher level approval1 mark

10.6 Ability to add additional conditions over and above the standard conditions during the approval period.

1 mark

10.7 Ability to automatically define next date for repayment on the basis of loan payment schedule whereby the system will send it to the customers through pre-defined channels.

1 mark

10.8 Ability to automatically send alerts periodically to customers on consequent treatment to be applied if they failed to repay due amounts timely.

1 mark

10.8.1 Ability to alert the customer upon full redemption of the facility

1 mark

10.9 Ability to automatically define dates to review contract and date to adjust interest rates.

1 mark

10.10. Ability to delay repayment until a specified time. 1 mark10.11 Allow for flagging of restructured loans 1 mark

11 NPL (Non-Performing Loan) Account11.1 Ability to support the generic requirements of past-due loan

management1 mark

11.2 The system allows credit officers to downgrade or upgrade loan bucket manually

1 mark

of 274


11.3 Ability to support the collections cycle (notifications, alerts, etc.) via SMS, e-mail (optional) for customers and credit officers.

1 mark

11.4 Ability to automatically produce the notifications based on product-level parameters to both borrower and also to other parties such as guarantee entity, etc.

1 mark

11.5 Allow for write off of NPLs and Write-down - transfer of loan facilities to off-balance sheet as recovery efforts are ongoing

1 mark

12 Calculate and Make Loan Provision12.1 Ability to calculate make general and specific provision 1 mark12.2 Ability to suspend interest upon downgrade of facility and

release once corresponding loan principal is paid1 mark

12.3 Ability to automatically zero rate loan/overdraft account once indupulum limit has been reached

1 mark

12.4 Ability to group related accounts according to prudential guidelines through the identifiers laid out by the bank

1 mark

13 Loan Repayment/Pay Off13.1 Ability to define various repayment types (interest only,

principal only, bullet, balloon, step-up/down, auto allocation etc.)

1 mark

13.2 Ability to support repayment during holiday period (collect later). In the case of collection of penalty interest, holiday is not counted.

1 mark

13.3 Ability to waive interest for predefined period during marketing campaign (this is subject to the Bank’s approval, and the interest for a specified period can be waived, which eventually becomes a repayment waiver).

1 mark

13.4 Ability to support fixed amount repayments, whereby any changes in interest rate have to be adjusted either by an increase in term or amount as per the customer's decision.

1 mark

13.5 Allow the Bank to offer special treatment to customers for repayment to be applied at account opening or in the case after repayments have begun the borrower will be allowed flexibility to be waived an installment of repayment amount

1 mark

13.6 Ability to automatically allocate the proceeds from repayment. On receipt of the proceeds, the system will allocate them to different repayment schedule as requested by customers.

1 mark

13.7 Allow defining parameters in allocating the loan payments (monitor the sequence of allocation e.g. penalty interest, interest, principal, charges, fees etc. as required by the bank, including but not limited to:

1 mark

13.7.1 Set by product type 1 mark13.7.2 Set by loan grading bucket 1 mark

13.8 Ability to record and manage on-maturity repayments, overdue repayments, pre-maturity repayments.

1 mark

13.9 Ability to automatically send an alert to a customer (SMS, email) regarding changes to his/her loan against the pre-agreed conditions in the contract.

1 mark

of 274


13.10. Ability to support loan repayment including but not limited to: 1 mark13.10.1

Premature repayment of a portion of the loan. The system should create a new repayment schedule to correspond with the new outstanding balance (reduced as a result of the premature repayment)

1 mark

13.10.2

Premature repayment of a portion of the loan without affecting the loan payment schedule (payable amount will be deducted from the repayment on the next maturity date)

1 mark

13.10.3

Flexible adjustment credit terms in contract when a customer makes premature repayment

1 mark

13.11 Ability to support batch collections 1 mark13.12 Ability to make early notification of a past-due loan. The

Tenderer is to describe the mechanism in the proposed solution.

1 mark

13.13 Ability to support establishment of different types of premature repayment, including but not limited to:

1 mark

13.13.1 Principal 1 mark

13.13.2 Payable interest accrued as from the last repayment date 1 mark

13.13.3 Charge on premature repayment 1 mark

13.14 Ability to calculate amounts repayable by customers, including principal, accrued interest receivable/past due interest.

1 mark

13.15 Ability to automatically calculate maturity date of the contract using criteria defined based on users.

1 mark

13.16 System should allow the bank to set up various loan repayment schedules including at least the following:

1 mark

13.16.1 Amortisation 1 mark

13.16.2 By specific schedule 1 mark

13.16.3 Capitalisation (interest added to the principal) 1 mark

13.16.4 Only principal 1 mark

13.16.5 One-off (balloon) 1 mark

13.16.6 Others (please describe if available) 1 mark

13.16.7 Instalment payments 1 mark

13.16.8

Instalment payments over some first terms and a balloon payment at maturity

1 mark

13.17 Allow product rules to be applied to determine the repayment schedules.

1 mark

13.18 Allow for automated loan closure of loan account on full repayment

1 mark

14 Diaries/Trackers.

of 274


14.1 Allow monitoring of post-approval covenants by way of alerts to various relationship managers

1 mark

15 Report Creation/Reporting/Portfolio Monitoring15.1 Allow for creation of pre-set reports to enable speedy creation

of periodic reports1 mark

15.2 Allow for report building as per the user preference 1 mark15.3 Avail a business intelligence tool 1 mark15.4 Allow for creation of dashboards for management reporting 1 mark15.5 Allow for interfacing with external databases e.g. CRB to allow

for uploading of data.1 mark

15.6 Allow for automation of reports generation and upload into relevant external databases

1 mark

15.7 Base currency limits for clients with non-fund based credit lines to accommodate processing of multiple currency transactions under the same limit.

1 mark

15.8 Availability of marking and processing limits for non-fund based transactions on corporate, SMEs, MSMEs and individual clients.

1 mark

16 Collateral Management16.1 The system supports controlling when the value of collateral

decreases and is not sufficient to back up the loan:- Outstanding loan is considered secured when: + The value of the outstanding loan is smaller than the product of collateral value and the proportion of the asset used as collateral (scenario 1)+ The value of outstanding balance is smaller than portion of the asset used as collateral (scenario 2)- The application of scenario 1 or 2 depends on the type of collateral. The system supports controlling when the value of collateral decreases and is not sufficient to back up the loan:- Outstanding loan is considered secured when: + The value of the outstanding loan is smaller than the product of collateral value and the proportion of the asset used as collateral (scenario 1)

1 mark

16.2 The system should allow the collateral to fully or partially secure the total credit limit and identify whether the asset is used as collateral for a credit contract or for the customer's whole liabilities.

1 mark

16.3 The system supports releasing collateral in the case the asset is used as collateral for more than one customer/at different branches. Describe the mechanism to alert and confirm the agreement to release the collateral.

1 mark

16.4 Allow one collateral to be shared for one or multiple loans; for customer credit limit of one or multiple customers at one or multiple branches. When a collateral is withdrawn, all the outstanding balances linked to the collateral must be zero or another asset whose value is enough to secure the current outstanding balance of customer is used as collateral according to the percentage defined by the Bank.

1 mark

of 274


Upon approval the system should be able to originate an addendum to the existing contract

16.5 Ability to store information about insurance contracts for insurance life and disability of the borrower.

1 mark

16.6 Ability to automatically post collateral value if any changes occur.

1 mark

16.7 Ability to generate alerts if the collateral has been used as collateral at another branch of the Bank.

1 mark

16.8 Ability to generate alerts if the value of the loan exceeds the value of the collateral.

1 mark

16.9 The system allows inputting the actual value of the outstanding balance and the value of collateral to calculate the loan proportion based on the value of the collateral.

1 mark

16.10' The system allows filtering outstanding balances according to product types and collateral.

1 mark

16.11 The system allows an asset to be used entirely or partially as collateral.

1 mark

16.12 The system has a flexible mechanism (automatically/manually) to block collateral.

1 mark

16.13 Allow for a depository of images of security documents and capturing of collateral details that is scalable.

1 mark

16.14 Allow for scanning and storing of collateral images in the repository and deletion upon approval.

1 mark

16.15 System should allow for partial release of collateral where more than one collateral is held or in cases where the collateral can be subdivided by the bank.

1 mark

16.16 The system supports the evaluation of collateral: information about collateral price history over time and the mechanism to update the prices of securities assets which are listed in the securities exchange market.

1 mark

16.17 Ability to connect collateral to credit limit of customer, customer group, product and contract.

1 mark

16.18 Ability to change collateral linked to customer credit limit and credit account throughout a loan's lifecycle.

1 mark

16.19 Ability to manage collateral on the detailed characteristics of each type of collateral, of collateral group and classify for easy management.

1 mark

16.20 Ability to manage collateral by its source of formation. 1 mark16.21 Ability to manage collateral by its relationship with customer. 1 mark16.22 Ability to automatically block collateral in the form of current

account, or saving accounts.1 mark

16.23 Ability to block collateral at different levels (full blocking, partial blocking) on different collateral (current account, stock blocking, etc.).

1 mark

16.24 Provide a mechanism for re-assessing collateral. The Tenderer is to describe this mechanism in detail.

1 mark

16.25 Ability to produce reports or give alerts to users before maturity date or review date of collateral.

1 mark

16.26 Allow one collateral to be shared for one or multiple loans; for 1 mark

of 274


customer credit limit of one or multiple customers at one or multiple branches. When a collateral is withdrawn, all the outstanding balances linked to the collateral must be zero or another asset whose value is enough to secure the current outstanding balance of customer is used as collateral according to the percentage defined by the Bank.

16.27 Ability to manage information about collateral owner, joint ownership including cases where collateral owner is the loan customer, owner is a third party, credit institution/guarantee issuing institution.

1 mark

16.28 The system allows the Bank to define collateral types and information fields including the legal eligibility of the collateral.

1 mark

16.29 The system allows filtering outstanding balances according to product types and collateral.

1 mark

16.30 Ability to generate alerts if the interest rate on a deposit used as collateral is higher than the interest rate on the loan.

1 mark

16.31 The system can generate alerts and update collateral, display the collateral history, fields for preliminary evaluation of collateral status.

1 mark

16.32 Alert of collaterals that are required to have insurances and state the effective period of the insurance. Alerts to be sent to bank officers and the borrower

1 mark

16.33 Ability to batch input with respect to collateral information. 1 mark16.34 Ability to update the value of a collateral if the value of a loan

changes; ability to select and delete collateral.1 mark

16.35 Ability to define the reason for moving collateral out of the vault. Allow for an end to end process for request of release to return

1 mark

16.36 Store of Information on collateral after it has been processed (prices, date of sale).

1 mark

16.37 Ability to aid a library system for management of the vault 1 mark16.38 Ability to interface with external databases e.g. tracking

companies for purposes of monitoring bank collateral1 mark

16.39 Ability to manage external service providers e.g. Lawyers, Valuers, Tracking companies in terms of issuing instructions, indemnity cover limits and SLA

1 mark

16.40 Ability to avail the security details to a customer 360 degree view to permitted users

1 mark

16.41 System to allow for alerts on expiry of leases and Rent and Rates

1 mark

16.42 Allow for interfacing with the capital market to enable immediate revaluation of money equivalent securities e.g. T-bills, Stocks, bonds etc.

1 mark

16.43 Allow for alerts for physical check of securities after a two year period

1 mark

16.44 Ability to alert the customer upon full redemption of the facility to collect the collateral

1 mark

16.45 Enable of collection of fees and commission for purposes of 1 mark

of 274


maintaining the collateral integrity.16.46 Ability to transfer a security from Collateral status to Safe

custody status and vise versa and allow for collection of commissions

1 mark

17.0 Others17.1 Report on loans due in the next 7 days and ability to send

alerts to the customers1 mark

17.2 Customers to be sent alerts on over dues and also prompt for loan repayment like 7 days to due date.

1 mark

17.3 Ability to automate collateral, Valuations, Insurances etc. 1 mark17.4 Loans disbursed report to have different parameters e.g.

product type, restructures, Moratorium, user ,RM etc.1 mark

17.5 Negotiation fees to be automated 1 mark17.6 Details of all bank assets captured as security by the bank,

their insurers, intermediaries, policy start date and expiry date1 mark

17.7 Ability to spool reports for existing insurance covers. The report should indicate the insurers where the covers were placed, the agencies through which the covers were placed, the policy start and end date

1 Mark

17.8 Link the CBS system to Insurancepro system where payments are made in the CBS and reflect in Insurancepro system

1 Mark

2.2.5 Debt Management Requirements Evaluation (211 Marks)Marks

# Evaluation CriteriaHost Data Extraction

1 Batch upload of files from Credit Card, Finance System, Core banking System, digital platform and Customer Relation Management System

1 mark

Data Mapping2 Multiple product support 1 mark3 Flexibility in mapping data received from Host System with

the Collection System tables1 mark

4 Mapping data in the Collection System tables to various screens at different levels such as Customer level and Contract level

1 mark

User Maintenance5 User Hierarchy definition - Multiple level support 1 mark6 User information capture - Demographic information of

each User with information such as Maximum Load and entitlements for downloading information

1 mark

7 Agency user mapping - Mapping Collectors and the Agency they work for

1 mark

Management of Portfolio8 Relationship view of customer 1 mark

of 274


9 In a disparate eco System, capability of the System to generate a common folio number for the purpose of Collection tracking

1 mark

10 Single View of customer 1 markBucket StampingFinance

11 Bucket information from finance System 1 mark12 Stamping as per definition in Collection System - where the

Buckets in the Collection process are different from the finance

1 mark

13 Month end stamping 1 mark14 Daily (where no cycles) 1 mark15 Cycle as defined in the Loan System 1 mark

Cards16 Bucket information from Card System 1 mark17 Cycle based as per definition in Credit Card System 1 mark

Broken Promise tracking18 Parameterized tracking for Various products - Product

based strategies1 mark

19 Grace days - for promised payments not received on promise to pay dates

1 mark

20 Hold days - where the fate of the clearing cheque is not known immediately

1 mark

21 % of amount to receive to qualify for promise kept 1 mark22 Different treatment for Cash 1 mark

Portfolio Segmentation & Work AllocationUser definable queries for the segmentation (Queuing). Product based strategies

23 Product - such as Personal finance, Cards, Mortgages and so on

1 mark

24 Queuing based on customer attributes such as VIP, Skip, Fraud, Legal and so on

1 mark

25 Account attributes - Buckets, Overdue amount, Outstanding amount, installment date and so on

1 mark

26 Special attributes - Broken Promise, Cheque return and so on

1 mark

27 A combination of all of these attributes 1 mark28 A hierarchy of Queues to avoid conflict - to avoid one

account falling in multiple Queues when they satisfy multiple Queue logic

1 mark

29 Difficulty index definition for each Queue for Load balancing based on the perceived difficulty

1 mark

Allocation of Queues - Beginning of day - Back end process

30 Attaching Queues to Agencies according to skill sets 1 mark31 Assigning Queues to Collectors under respective Agencies - 1 mark

of 274


Dynamic movement of accounts satisfying a Queue logic32 Assigning Queues to a pool of Collectors under an Agency 1 mark33 Reassigning Queues to another Collector / another Agency -

escalation for effectiveness during operation1 mark

34 Reassigning accounts to Collector / another Agency - escalation for effectiveness during operation

1 mark

Action based prioritization for follow up - Beginning of day Back end process

35 Rule (algorithm) based work list generation for the day, from actions such as

1 mark

36 Call back, promise to pay, broken promise, cheque return, no follow-up

1 mark

37 Fresh accounts where follow up is yet to begin 1 markWork Prioritization

38 Action code priority for calling 1 mark39 By products 1 mark40 For Finance 1 mark41 Account priority within the action code groups by products 1 mark42 Priority based on Location for Field Collectors 1 mark

Classification Process43 Special handling for designated customer such as VIP,

business partner etc. - By amount range - By delinquent days range (segment collection by days)

1 mark

44 The criteria setting for determine the classification parameter which can set up the new criteria of delinquent days range (the number of overdue days) in each buckets.

1 mark

45 The working Queue within the classification by System parameter setting as flexible parameter setting for example: - The amount of overdue installment in each buckets - The number of overdue periods in each buckets etc.

1 mark

46 The classification of accounts by billing/ statement cycle for low level dunning on mild delinquent accounts - By delinquent days range (segment collection by days) - By segment - By amount range

1 mark

47 Account under litigation recovery - By delinquent days range (segment collection by days) - By segment - By amount range

1 mark

48 Classify collection accounts into geo-regional collection branches/ centers for better customer immediacy and turnaround

1 mark

49 Account attributed such as setup of the classification - Product of combination of products - Amount Due - Nationality, due date delinquent days - Billing/ Statement cycle

1 mark

of 274


- Total Loan - Geo-regional branched or centers - Open date/ Relationship since - Utilization of credit limit/line - Other criteria ……

50 The dunning letters (reminder letter, terminate letter) / collection notice should be generated by the automatically and/or manual which depend on the classification of delinquent accounts such as overdue 1 period, overdue 2 periods etc.

1 mark

51 The solution should have the facility to define function codes. Accounts will be classified into homogenous groups based on the function codes to facilitate collection efforts.

1 mark

52 Movement of accounts should be governed by:• State Processors – which route accounts across functions based on the parameters detailed in the location parameter table• State Assignment – these are rules based on which accounts are routed/rerouted on a daily basis to the states in which they are to be worked

1 mark

Due Follow-upOutbound Calling

53 Calling from the prioritized worklist of a Queue 1 mark54 Automatic pop up(Relationship screen) of accounts from the

worklist in the set priority1 mark

55 Provision to capture follow up trails (actions - such as promise to pay, call back etc.) to the customer accounts

1 mark

56 Provision to attach attributes such as Skip, Disputes, Legal, Employee etc. for segmentation and allocation

1 mark

57 Referring accounts to fellow Collectors for help/advice 1 mark58 Routing (escalating) accounts to Supervisor in case of

difficulty1 mark

Inbound Calling59 Receiving incoming calls from delinquent customers 1 mark60 Search based on standard fields 1 mark61 Configurable search label definition by product 1 mark62 Adding follow up trails (actions - such as promise to pay,

call back etc.) to the customer accounts1 mark

Digital Loans63 Capability of the System to generate a common folio

number for the purpose of linking/ monitoring existing customers

1 mark

64 Automated Text Messaging prompts before accounts become due

1 mark

65 Automatic text Messaging for payment reminder of accounts on due date

1 mark

66 Recognition of payments, with text generation, & exclusion from work list

1 mark

of 274


67 Automatic pop up of delinquent accounts by set priority. 1 mark68 Integration with CBS, for funded account report, with

sniffing capability1 mark

69 Automatic prelisting /listing text messaging within prescribed time limits

1 mark

Field Referrals70 Statcard generation 1 mark71 Contents definable by product 1 mark72 Sorting by a field (Location / area) 1 mark73 Generation by Agency 1 mark74 Generation by Collector 1 mark

Legal Recourse75 Identification by rules - Queue strategy 1 mark76 Referral to Legal by 1 mark77 Collector 1 mark78 Customer action 1 mark79 Action result 1 mark80 Allocation of Legal accounts to Legal officer 1 mark

Repossession81 Identification of accounts by rules - Queue strategy 1 mark82 Identification by action of customer 1 mark83 Identification by responses from customer 1 mark

Initiation84 Notice to customer of his continuing default - threat to force

conditions of contract1 mark

85 Refer to repo Agency 1 mark86 Letter to Agency 1 mark87 Date of repossession 1 mark88 Communication to Local police 1 mark89 Name of Garage/warehouse where stored 1 mark90 Capture gist of Inspection report of repossessed asset for

condition1 mark

91 Notice to customer informing him of the repossession with final call for payment

1 mark

Sale of repossessed asset92 Capturing settlement figure on the date of repossession 1 mark93 Capturing expenses incurred on repossession and amount

incurred to transfer title to buyer, debited to customer1 mark

94 Letter to auction house with details of asset and upset price 1 markBidding details

95 Capture highest bid details 1 mark96 Date of delivery of asset to the highest bidder with

documents for transfer of ownership1 mark

Short fall capture97 Capturing expenses incurred on sale / garage rent / legal

expenses to the account of the customer1 mark

of 274


98 Capturing short fall calculation after sale 1 mark99 Notice of Shortfall to customer with time limit for payment 1 mark100

Capture decision on legal proceedings for Short fall 1 mark

Repossession Collection Efficiency Monitoring & Rule Based Escalation

101

By repetitive reply codes 1 mark

102

By no action 1 mark

103

By dates 1 mark

104

By definable conditions as per business requirement 1 mark

105

By promise to pay amounts 1 mark

Backend Support for follow up106

Preparation of Dunning letters/SMS/email (Auto-dunning and Batch)

1 mark

107

Multiple templates for each product 1 mark

108

Multiple language templates 1 mark

109

Suppress communication / overrides 1 mark

Operational activitiesGeneric

110

Capacity Planning vis-à-vis delinquency portfolio 1 mark

111

Processing of small balances cleanup for reversals 1 mark

Reports & Dashboards112

Bucket flow reports 1 mark

113

Payments and write Back Reports on Substandard Accounts 1 mark

114

Detailed with drill down into the accounts 1 mark

115

Summary with drill down into the accounts 1 mark

116

Portfolio trend reports - with definable sections or cuts 1 mark

117

Aging report 1 mark

118

Advocate monitoring report 1 mark

119

Collection efficiency report 1 mark

of 274


120

Collector Productivity report 1 mark

121

Staff Productivity Reporting(KPI) - Track collections efforts by Collector to determine productivity. The System should generate reports daily - total attempts made , total contacts established, total promise taken, total promised amount, total amount collected on kept promise, total accounts actually worked.

1 mark

122

No Activity Report-This report gives the number of accounts where collections activity has not taken place in the last 1 week, 2 weeks, 3 weeks and over 3 weeks

1 mark

123

No Contact Report-This report will contain only accounts that have been attempted and where contact has not been established with the customer.

1 mark

124

Collectors Effectiveness Report-Collector Effectiveness Report, a monthly report is produced with an objective of measuring the effectiveness of our Collectors. This is based on the kept promise ratio( contact/attempts)

1 mark

125

Intensity MIS-This report describes the extent of coverage and no. of contacts made and their corresponding results.

1 mark

126

Skip MIS - This gives the total number of accounts in skip Queue , Number of customer's contacted , pending for early write offs

1 mark

127

Delinquency MIS – The Report that generates the details about delinquency rate - delinquency lag , coincident indicators for 30, 60, 90,120,180DPDs

1 mark

128

Dunning letters- MIS on total letter sent 1 mark

129

Producing weekly/monthly reports on Staff productivity based on actual file reviews.

1 mark

130

Should generate reports for provisioned accounts as per the bank's requirements, detailing amount outstanding, provisions made and any interest/charges calculated but not levied on those accounts

1 mark

131

The solution should provide reporting online reporting facility into the database and calendar.

1 mark

132

Report and MIS should produce daily, weekly and monthly standard performance statistical reports to measure the collection performance as the individual team and agent (both HQ and branch)

1 mark

133

System should have dashboards with filters to drill down. It should provide a holistic overview of the Portfolio performance, Collection efficiency etc.

1 mark

Collection Agency Management134

Identification of accounts for allocation to Agency as per defined policies

1 mark

135

Allocation of accounts to identified Agencies 1 mark

13 Generation of Agency Assignment Reports 1 mark

of 274


6137

Printing of Stat Cards for allocated accounts 1 mark

138

Update of feedback on customer accounts 1 mark

139

Monitoring of portfolio and resolution 1 mark

140

Tracking of customer payments on portfolio 1 mark

Monitoring of Productivity MIS of the agent 1 mark141

Generation of MIS Reports on Productivity and Effectiveness of callers

1 mark

Computation of Agency Billing142

On Bucket flow - % of amount / actual amount of flow 1 mark

143

On actual amounts collected 1 mark

144

Other parameters such as # of Promise Kept, # of contacts 1 mark

145

On individual performance and team performance 1 mark

146

On retainer basis 1 mark

Review of Agency performance147

Reports on Agency performance - Targets vs. Actuals 1 mark

Receipt Books Management148

Issuance of Receipt Books to Agencies 1 mark

Other requirements149

Collect System should support below Islamic product follow-upsIsalmic Credit card, Murabaha, Tawarroq, Mudarabah, Musharakah, Ijara, Istisna and qard hassn, etc...

1 mark

150

Real Time interfacing from all financial applications to Collections System for Notification of payments

1 mark

151

Behavior Score should be available in Collections System 1 mark

152

Real time interface with Core banking System 1 mark

153

Database and interface support for Arabic characters 1 mark

154


1 mark

155

Ability to generate SMS and e-mail messages 1 mark

156

Ability to set actions and priority to Queues and to import and utilize a Queue account assignment and generate

1 mark

of 274


customer communications (SMS/e-mail/letter) based on a batch file from the relevant parent processors

157

Support calculations of external Agency fees and commissions

1 mark

158

Supervisor monitoring capability in real time through GUI screen that is easy to read and analyze and that allows supervisor to take appropriate action

1 mark

Support limited inquiry capability for external collection Agencies

1 mark

159

Dynamic re-assignment of high-priority accounts to collection personnel based on workflow

1 mark

160

Support ad-hoc manual shifting of accounts from one Collector to another

1 mark

161

System will support all consumer finance businesses – Credit Card, personal finance, Overdraft, etc

1 mark

162

Info security details in standard format has to be replaced with current requirement on security features wherever required

1 mark

163

integration with Document Management system 1 mark

164

Ability to handle repayment options as per policy of the Bank and ability to do recalculation whenever there is a change in the policy of the Bank/QCB.

1 mark

165

Ability to support integration with single sign on system 1 mark

166

Ability to get feed from another system and store credit rating related information

1 mark

167

Ability to see entire customer portfolio in one view 1 mark

168

Ability to link to Integrated desktop system 1 mark

Integration169

Integration with Core banking phoenix 1 mark

170

Integration with GL 1 mark

171

Integration with Call Center & Dialer 1 mark

172

Have the ability to be installed in several channels (Branches, Call Center & Collection Department) with different authorization levels

1 mark

173

Can interface through a middle-ware layer. Can be the IFX we are using currently or any other middle ware in the future

1 mark

174

Can integrate with Multiple Core banking for multiple institutions

1 mark

SecurityAccess Control

of 274


175

An access log should exists to review all the disabled accounts, user accounts with last login date

1 mark

176

Ranges of user level access should be applied to reports, letters and contact management

1 mark

177

The Access control privileges and its profiles should be documented (matrix) with the level of access to the Systems/forms etc.

1 mark

178

Different login permission: with limited scope to clients and other points of contact with whom you wish to share case information. System should allow to share important information with clients while preserving privacy for company proprietary data such as financial information.

1 mark

179

Different login permission: Group of Collectors based on user-defined criteria

1 mark

180

The information System should have authorizations for controlling the flow of information within the System and between interconnected Systems in accordance with applicable business rules and policy

1 mark

181

The information System should enforce a limit of consecutive invalid access attempts by a user during a time period. The information System automatically delays next login prompt according to when the maximum number of unsuccessful attempts is exceeded

1 mark

182

Enabled Logs should contain the unsuccessful login attempts

1 mark

183

The System log should determine the System use and it should be logged

1 mark

184

The information Systems should limit to the concurrent sessions based on the capacity requirements

1 mark

185

The information System should prevent further access to the System by initiating a session lock that remains in effect until the user reestablishes access using appropriate identification and authentication procedures

1 mark

186

The information System automatically terminates a session after of inactivity

1 mark

187

A method to supervise and reviews the activities of users with respect to the enforcement and usage of information System access controls should exist

1 mark

Identification and Authentication188

The information System should identify users uniquely. The mode of authentication can be a choice to the business requirement (subscribed user with strong password)

1 mark

189

The information System should identify and authenticates specific devices before establishing a connection

1 mark

190


1 mark

Audit and Accountability191

The information System should provide the capability to compile audit records from multiple components throughout

1 mark

of 274


the System into a time-correlated audit trail.192

The information System should provide the capability to manage the selection of events to be audited by individual components of the System

1 mark

193

The organization allocates sufficient audit record storage capacity and configures auditing to prevent such capacity being exceeded.

1 mark

194

In the event of an audit failure or audit storage capacity being reached, the information System alerts appropriate organizational officials and takes the following additional actions: [Assignment: organization-defined actions to be taken (e.g., shut down information System, overwrite oldest audit records, stop generating audit records)]

1 mark

195

The System should have the required facility enabled for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations

1 mark

196

The System should provide time stamps for use in audit record generation.

1 mark

197

The System configuration should be enabled to protect audit information and audit tools from unauthorized access, modification, and deletion.

1 mark

198

The Client IP address of the source should be captured as a part of log and accessible for review

1 mark

Configuration Management199

The production System configuration should follow the process of baseline as part of release management

1 mark

200

As per the Change management policy and procedures, Appropriate officials should approve information System changes

1 mark

Contingency Planning201

The proposed solution should have a contingency plan for the information System addressing contingency roles, responsibilities, assigned individuals with contact information, and activities associated with restoring the System after a disruption or failure

1 mark

202

The contingency plan for the information System to determine the plan’s effectiveness and the organization’s readiness to execute the plan should be prepared

1 mark

203

The System backup plan should be in alignment with contingency plan of the System

1 mark

Communication Channel204

The information System should protect the integrity of transmitted information. The communication flow should be end-to-end encrypted

1 mark

205

The communication flow should be clear stating the Ports, Source/Destination required to function

1 mark

System and Information integrity206

The System should implement malicious code protection that includes a capability for automatic updates (Anti-Virus

1 mark

of 274


client and System Critical / Security Patches Updates)Monitoring & Review

207

The Application should have interface for the IT Security team to review access of the Systems to review user access / Modification / information of application usage

1 mark

208

Support Escalation Matrix, followed by agreed SLA with Vendor

1 mark

2.2.6 Risk Management & Compliance Evaluation (25 Marks)Evaluation Criteria Marks

1 Ability to change passwords for all generic accounts in the database

1 mark

Know Your Customer and AML support requirements

2 System to provide fields for updating customer's specific nature of business and annual account turnover.

1 mark

3 In instances where customer is employed, system to provide field for capturing Name of employer and position held

1 mark

4 System to have tag notes to trigger staff if an account is missing any mandatory KYC particulars that the customer ought to avail or any other message that staff need to know before processing any transaction in a client's account

1 mark

5 The system should have fields to append Risk Profile/Category of a customer. The same should be editable to take care of customer's changing profiles- from high, medium to low risk and vice versa as the case may be. Drop down preferred

1 mark

6 System to enable account search using Name, Identity card number, Passport number, Certificate of incorporation number or Business Name

1 mark

7 System to have fields for updating accounts with individuals and Corporates Personal Identity Numbers No’s, ID No’s and Huduma number

1 mark

8 System to host watch-lists capable of being updated from time to time and screen against black listed customers at the point of account opening or initiating any transaction including Bankers cheque purchase etcetera. The watch lists to include but not limited to OFAC, UNSC, PEP, Acuity, World check, EU & HMT

1 mark

9 System to support integration with AML solution 1 mark10 System should carry out reverse screening on existing

data 1 mark

11 Provide a field for searching all customers’ accounts including related accounts where he is a party.

1 mark

12 Provide a mandatory field which assist in populating 1 mark

of 274


all related accounts during account opening to help in grouping customer related accounts.

13 Provide for centralized secondary approval at both Dormant activation and amendment of KYC data.

1 mark

14 Support making of mandatory KYC & AML data field compulsory at account Opening process.

1 mark

15 System to allow IT support staff to be able to define all account opening KYC data as either mandatory or optional or by choice

1 mark

16 Support mandatory customer data on Risk rating of Customers (High, Medium, Low)

1 mark

17 Support marking of exact nature of business or professions such as Lawyers, Doctors, Forex Bureaus, Casinos, Contractors, Government agencies, Schools, Wholesalers, Pharmacists, Supermarkets, Petrol Stations, M-Pesa agents etc.This includes Main category and sub category where applicable.

1 mark

18 Support integrating the system (data tables and fields) with transaction monitoring systems

1 mark

19 Supports KYC & AML static data reports per Customer, Branch, Product, Risk rating, Nature of business

1 mark

20 Supports reports on cash deposits & withdrawals transaction reports per user, per branch, per product, per risk rating

1 mark

21 The system should avoid duplication of data capturing fields. i.e. within the system we should have one reference table for all customer static data where any account created will be reading from and updating the same fields at account level. NB: No updating of static data at account level

1 mark

22 The system should be able interphase with other systems, able to share customer details from CBS

1 mark

23 The system should have controls to ensure any customer details amendment rights are tied to specific users

1 mark

24 The system should support MIS Reports of any kind that can be developed internally without referring to the vendor, that is, report writing tool must be provided.

1 mark

25 The system should be capable of one way automatic downgrade of loan accounts with only manual upgrade intervention.At the point of manual upgrade, it should be able to release provisions held together with interest in suspense.

1 mark

of 274


2.2.7 Treasury Requirements Evaluation (168 Marks)# Evaluation Criteria Marks

1 Creation of multiple portfolios, business units 1 mark2 Supports automated and manual capture with only

manual amendments and cancellations1 mark

3 Each trade ticket should allow for free format text box 1 mark4 The platform includes standard templates for deal

input containing all standard market input fields based on the product type.

1 mark

5 The system should support customized input templates. Save multiple deal entry templates.

1 mark

6 Dealer to be able to save multiple deal entry templates. 1 mark7 The platform has the ability to perform pre trade

analytics before execution (counterparty, dealer limits, P&L, risk checking)

1 mark

8 The system should allow entering of cash flows from an external source.

1 mark

9 The system should allow entering of financial instruments and creation of cash flows in the system itself

1 mark

10 The system should allow to seek referral where limits have been exceeded

1 mark

11 Should support user defined workflows 1 mark12 Easy parameterization of the system covering all

possible scenarios1 mark


1 mark

14 Ability to flag broker on the trade and calculate the applicable brokerage on the deal as per specified pricing parameters

1 mark

15 Back office can never change trade details - they have to be processed by Front Office

1 mark

16 System should have the ability to hold the dealing mandate details.

1 mark

17 Integrate with Trading Platforms like Reuters FXT/Bloomberg and other online trading platforms/Core banking system and Swift.

1 mark

Ability and willingness to set up structures to capture market data, where it is not available

1 mark

18 Ability to calculate weighted average duration of fixed income portfolio wise

1 mark

19 Audit trail of all activities 1 mark20 Ability to link amendments and cancellations /

reversals to original deal.1 mark

of 274


21 System support market data from Reuters and Bloomberg

1 mark

22 Pricing tools- the pricing tools must be able to cover all the required instruments and use standard market-accepted pricing algorithms.

1 mark

23 Ability to store historical deal and rate set information 1 mark24 Ability of saving historical data and methods of

restoring it in the future1 mark

25 Ability to download reports in common export formats ( excel, pdf, csv, html) either as a scheduled, batch or on-line request.

1 mark

26 Each trade should have a unique transaction number. 1 mark27 Rate Fixings (e.g. Libor) are automatically saved each

day and are applied to any Floating Rate instruments.1 mark

28 Ability to be able to set-up curves for stress testing. 1 mark29 The system should have the flexibility for choosing

parameters for display and the methods for filtering and drilling down data and reports by trades, by dealer, by desk, by instrument, by entity, by portfolio, by product or counterparty.

1 mark

30 Front Office personnel should not post accounting entries on general ledger accounts

1 mark

31 System should support wide and flexible hierarchy structures including multi entity (branches) centralized trading.

1 mark

32 System should provide user access controlled data viewing between branches / desks / units / traders

1 mark

33 System should have the ability to interface with the core banking system for settlement, accounting, revaluation etc.

1 mark


1 mark

35 Ability to choose, assign, combine and link on the term structure the benchmark instruments quoted on the market for money market instruments loans / deposits, bonds, call , notice and term money

1 mark

36 Ability to Incorporate industry standard calculation methods in yield curve generation functionality implied from FX Spot-Forward structure. Generate zero curve points from par curves using bootstrapping techniques.

1 mark

37 Ability to display charts of par, zero and forward curves.

1 mark

38 Revaluation 1 mark39 Ability to save closing rates Spot, Forward Points, Yield

Curves, Volatility Curves, Bonds prices, Equities prices.

1 mark

of 274


40 System should have the ability to use a number of valuation methods -set of Term Structures used in portfolio pricing and methodologies used in curves construction

1 mark

41 Reports 1 mark42 The ability for users to configure reports within the

system according to their business needs.1 mark

43 The system should have list of pre designed reports that are based on best practice for both risk and P&L reporting

1 mark

44 Real time position and P&L by dealer 1 mark45 Reports Dealer wise position report 1 mark46 Reports FX Financial report 1 mark47 Reports Revaluation reports with deal details 1 mark48 Reports System must provide the ability to configure

different types of reports as per business needs (in a user friendly way, without technical intervention)

1 mark

49 Reports All deals done for the day 1 mark50 Reports All outstanding deals by maturity 1 mark51 Reports All outstanding deals by customer 1 mark52 Reports All outgoing messages by type 1 mark53 Reports Confirmation matching status 1 mark54 Reports List of deals reversed / deleted by date 1 mark55 Reports Accounting entries by deal for the day or

overall1 mark

56 Reports List of realized P/L report 1 mark57 Reports List of unrealized P/L report 1 mark58 Exception reports for off market rates 1 mark59 Exception reports for Limit breaches 1 mark60 Exception reports for negative P&L and market

exchange1 mark

61 Reports Accrued profit detail report 1 mark

Foreign exchange63 Instruments Spot 1 mark64 Instruments Outright Forward 1 mark65 Instruments FX Swap 1 mark66 Instruments Split Value FX 1 mark67 Instruments Internal deals between desks 1 mark68 Support segregation of FX positions from CBS by

originating units1 mark

69 The Blotter should: 1 mark a) Pick branch transactions done at the branch levels and be able to reflect the deals and

the positions created as branches input the deals.

1 mark

of 274


b) Provision for input of deals done on phone. 1 markProvision for split deal dating. 1 mark

70 Ability to generate forward points for revaluation based on yield curves.

1 mark

71 Ability to be able to view Positions and P&L at Portfolio level by Trader/Business Unit Level.

1 mark

72 On-line blotter for position keeping. 1 mark73 On-line P&L transaction and position reports with drill

down to trade level to manage exceptions1 mark

Money Market74 Instruments Interbank Placements/Borrowings 1 mark75 Instruments Repurchase Agreements and reverse

repos1 mark

76 Instruments Treasury Bills 1 mark77 System should support roll over of money market

placements and borrowings -for deals to be rolled principal only, principal plus interest and part repayment.

1 mark

78 System should support partial maturity or increase of principal.

1 mark

79 System should support assigning Bonds and T-bills to a Repo Transactional.

1 mark

80 System should support assigning multiple securities to a single repo.

1 mark

81 System should be able to compute accruals on a daily basis.

1 mark

1. The software should capture the following branch

1 mark

activities for monitoring and management purposes:

1 mark

a) Major movement of deposits. 1 markb) Issuance of RTGS. 1 markc) Increases of overdrafts and advances to customers.

1 mark

d) Generate a report of expected maturities of fixed deposits

1 mark

1 mark82 RTGS should be initiated at the branch and then flow

to the back office. Front office should be able to view in real Time , the processed transactions.

1 mark

83 System should be able to compute automatically the broker fees based on predefined rules or allow for manual override.

1 mark

Investment Operation

of 274


84 Instruments Fixed/Floating Rate Bonds Issued by Govt/Financial Institutions/Corporate

1 mark

85 Market Data from Bloomberg/Reuters 1 mark86 Appropriate accounting treatment based on bond

classification.1 mark

87 Inventory Processing should be as per Weighted Average Cost

1 mark

88 Should support different calculation basis (A/364, A/360, 30/360, A/365)

1 mark

89 Should support amortizing securities. 1 mark90 Should support effective interest rate amortization of

premium / discount of HTM securities.1 mark

91 Should support different bond calculators e.g. bond partial redemption.

1 mark

92 Ability to generate market prices based on yield curve. 1 mark93 Ability to report all positions by issuer and country 1 mark

Limit Management94 Solution should support the following limits 1 mark95 Counterparty limit 1 mark96 Settlement limits 1 mark97 Tenor limits 1 mark98 Solution should provide ability to define limits which

are split by counterparties and across branches with the total of all the limits adding up to the total limit amount

1 mark

Business Unit 1 markProduct type level (Treasury products only ) 1 markTenor level 1 markCounterparty / Counterparty Group 1 markCountry 1 markIssuer 1 markIndustry / sector 1 mark

99 Solution should support limits check in real time or in batch mode

1 mark

100

Solution should provide date range for limit defined 1 mark

101

Solution should provide flexibility to define limits for each branches

1 mark

102

Solution should provide the following types of limits; 1 mark

103

Issue/Issuer Limits on Bonds 1 mark

104

Is it possible to import/export limits in the solution? (automated upload of limits)

1 mark

10 The solution should generate alerts to multiple users 1 mark

of 274


5 whenever limits are breached in the system as well as email

106

The solution should provide with excess management workflow.

1 mark

107

Solution should convert all the exposures in different currencies to the currency of the limit

1 mark

108

The solution should allow to identification of the counterparty interbank limit exceeded, the users that exceeded it and the users that allowed the surplus?

1 mark

109

Does the solution allow to book a size of the counterparty credit risk for a period, where during this time, others desks and traders can't use this limit booked?

1 mark

110

Does the solution allow to set-up an expiry date to the counterparty interbank limit? Even after maturity is it possible to search the limits allocated and consumed?

1 mark

Exposure calculation111

Solution should provide the following methodologies for exposure calculationNotional 1 markMarket Value 1 mark

Market Risk112

The system should provide Basic Value-at-Risk engine to calculate market risks using Historical VaR method

1 mark

113

Solution should support the following limits

Position limits 1 markStop/Loss limits 1 markTransaction limits 1 markRate tolerance limit 1 markSensitivity limits 1 markSolution should provide flexibility to define limits byDesk 1 markPortfolio 1 markBranches 1 markDealer 1 markCurrency 1 markCurrency group 1 markCurrency pair 1 markSecurities 1 markTenor 1 markInstrument 1 markInstrument group 1 mark

of 274


Country Risk Limits 1 mark114

Solution should support limits check in real time or in batch mode

1 mark

115

Solution should support excess alert definition 1 mark

Limit management for reporting116

Solution should provide functionality for breaching limits reservation

1 mark

117

Solution should provide monitors for exposure and limit utilization across treasury and investment

1 mark

118

Solution should provide standard reporting on Limits / utilization / exposures at different aggregation levels

1 mark

119

Solution should provide excess reports and excess authorization workflow

1 mark

Monitoring

120

Event Correlation ( pending, incomplete, same customer, etc.

1 mark

121

System Alert capability 1 mark

122

Log generation 1 mark

Reporting

123

Detail reports available 1 mark

124

Easy report generation and customization 1 mark

125

Dashboards 1 mark

126

Comprehensive audit trail - Read Only -Export to 3rd party application

1 mark

127

Easy dashboard view customization 1 mark

128

State relation with, or dependence on other subsystems i.e. components of a suite

1 mark

129

Solution should provide reports across multiple dimensions (individual Trade/book wise/trader wise/sector wise/strategy wise/portfolio/expiry wise)

1 mark

130

Solution should provide PL reporting across multiple dimensions (individual Trade/book wise/trader wise/sector wise/strategy wise/portfolio/expiry wise)

1 mark

13 Solution should provide cash flow bucketing reporting. 1 mark

of 274


1132

Solution should provide ability and ease for customization of reports

1 mark

133

Should have a module for amalgamated Assets and Liability Management reports.

1 mark

134

Solution should provide MTM reporting for all trades within treasury and investment

1 mark

2.2.8 General Ledger Requirements Evaluation (85 Marks)# Evaluation Criteria Marks

1 Support online update to GL accounts for all types of transactions.

1 mark

2 Provide facility to generate the daily Trial Balance and balance Sheet in Bank’s Format.

1 mark

3 Provide facility for reflecting in the General Ledger Balance the total of credit balances in current accounts on the liabilities side and total of debit balances in Cash Credit accounts on the asset sides respectively by taking into account the total of debit balances in current accounts on the assets side and total of credit balances in Cash Credit accounts on the liabilities side every day.

1 mark

4 Provide ability to produce General LedgerBy Branch 1 markBy Branch and its extension counter 1 markBy Centre 1 markBy Zone(as defined by bank)/ Regional Office 1 markBank as a whole 1 mark

5 Support application of alternate methods for generation of reports required for statutory purposes and for internal Management Accounting.

1 mark

6 Provide facility to capture of all financial transactions concurrently for

1 mark

7 Transaction currency 1 markAccounting unit currency (‘local currency’) 1 mark

7 Provide facility for fiscal year accounting. 1 mark8 Allow splitting of fiscal year as defined by user. 1 mark9 Support user-defined financial reporting periods

other than fiscal year, e.g. 15 months or 9 months. 1 mark

10 Support monthly / quarterly / half-yearly accounting periods within each fiscal year with facility for aggregation of monthly figures into quarterly / half-yearly figures.

1 mark

11 Provide facility to automatically maintain and carry 1 mark

of 274


forward of period-end account balances to subsequent periods for

Each accounting period within a fiscal year 1 markAcross fiscal years / financial reporting

periods1 mark

12 Allow postings pertaining to prior dates (Value Date) after authorization

1 mark

13 Provide facility to continue operations into the new fiscal year with authorization even if due to some contingency, closing of accounts for the prior fiscal year remains incomplete.

1 mark

14 Provide facility for detailed logging of all events related to ‘opening’ and ‘closing’ of accounting periods

1 mark

15 Provide facility for acceptance and posting of only balanced journal entry transactions.

1 mark

16 Support automatic calculation of ‘Retained Earnings’ for each fiscal year and its automatic carry forward to the next fiscal year.

1 mark

17 Support defining organization hierarchy allowing multiple levels reporting of ‘Financials’ (trial balance, balance sheet and profit and loss accounts). The hierarchy definition to support reporting at

Bank / Accounting Entity Level 1 markZonal Level 1 markBranch Level 1 markDistrict Level 1 mark

18 Provide facility for reporting of “Financials” at user-defined levels

1 mark

19 Provide facility to define the chart of accounts allowing reporting of accounted transactions

1 mark

20 Provide facility to define the individual general ledger accounts with following parameters, including but not limited to:

1 mark

Effective dates of the account 1 markOverall blocking of account 1 markBlocking of an account for specific accounting

period / entity / location / branch1 mark

Mapping of each general ledger account to any node (subsidiary heads) of the chart of account(s)

1 mark

Mapping of each general ledger account to one or more interfacing chart of accounts (since multiple systems would be interfacing with the general ledger)

1 mark

of 274


21 Provide facility to show break-up with /without sub account details for all applicable GL accounts

1 mark

22 Support each general ledger account to be maintained in different currencies.

1 mark

23 Provide facility to identify certain General Ledger accounts as bank / cash accounts.

1 mark

24 Support recognizing, accounting and reporting of transactions with respect to various heads including, but not limited to:

1 mark

Asset 1 markLiability 1 markIncome 1 markExpense 1 markContingent 1 mark

25 Provide facility for recognizing, accounting and reporting of transactions, which are not directly initiated by customer, such as interest recoverable, matured principle, provision for interest, etc.

1 mark

26 Provide fully functional interface for affecting inter-branch / location, inter-bank accounts funds transfer with complete integration with general ledger functionality.

1 mark

Transactions & Posting27 Provide facility for assigning and usage of specific

accounting vouchers (documents) for specific types of transactions.

1 mark

28 Automatically generate and assign sequential numbers to accounting

Bank / Accounting entity 1 markLocation / Branch 1 markFiscal year 1 mark

29 Provide facility for direct posting of voucher and should not allow for keeping the voucher ‘on-hold’.

1 mark

30 Provide facility for reversal of voucher / accounting document:

Individually 1 markCollectively based on, but not limited to,

parameters like voucher type, accounting entity, voucher reference number, location, user, etc.

1 mark

Support capture of reason for every reversal. 1 mark31 Ensure that reversal transactions should consider

the effect in the analysis of accounts for the purpose of MIS.

1 mark

32 Provide facility for faster creation of new voucher / documents using

1 mark

Voucher / Document templates 1 mark33 Provide facility for creating recurring entries that 1 mark

of 274


allocates one amount to multiple accounts based on user-definable rules.

34 Provide facility for setting of starting and ending date, period / year for recurring entries.

1 mark

35 Provide facility to upload transaction in soft copy and auto posting of vouchers for these transactions.

1 mark

36 System to have capacity to support batch reversal 1 mark

37 Provide facility for automatic / scheduled processing of recurring / repetitive Voucher documents for user definable dates and period e.g. monthly, bi-monthly, quarterly etc.

1 mark

38 Provide facility for automatic recasting of balance in the main account whenever a transaction is posted in the sub-ledger account.

1 mark

39 Support restriction of direct postings to main accounts where sub-ledger account is maintained.

1 mark

40 Allow selecting desired general ledger accounts (such as employee loan accounts, travel advance, etc.) to provide similar functionality for clearing of open debit and credit transactions within the general ledger account.

1 mark

41 Provide facility for defining for each account (which is chosen to offer the clearing functionality) what should be the nature of the originating transaction (debit or credit) and what should be the nature of clearing transaction (corresponding credit or debit). The system should enforce the definition.

1 mark

42 Provide facility for capture of following dates per transaction (with automatic update by system wherever possible), but not limited to:

Date (and time) of transaction 1 markValue date 1 markDate (and time) of authorization 1 markDate (and time) when transaction was

changed1 mark

Date when transaction was reversed 1 markExchange rate used for foreign currency

transaction1 mark

43 Support recording of transaction across accounting entity / branch / location through one accounting document. (Multi Branch access with proper authorisation)

1 mark

44 Support defining rules for automatically calculating and accounting for, but not limited to:

Difference on clearing unbalanced open items 1 mark

of 274


Exchange rate difference postings (at time of clearing of open transactions)

1 mark

Income Tax (payable as well as recoverable) 1 markInterest on over-due amounts 1 markService Charges 1 markCompute all bank

charges/commission/fees….etc. on listed services.1 mark

45 Ensure correct on-line generation of automatic entries based on defined rules at the time of data-entry or batch update itself.

1 mark

46 Allow option to de-activate automatic generation of entries for batch-uploaded transactions.

1 mark

47 System to have capacity to restrict manual entries to certain GLs unless with authority e.g. Interest income /expense

1 mark

48 System to limit GLs available to Branches (Avail GLs on a need to have basis)

1 mark

49 System to support automatic revaluation of General Ledgers for foreign currency

1 mark

2.2.9 Customer Management Requirements Evaluation (130 Marks)# Evaluation Criteria Marks1 Customer Management module will hold customer

information / profile for all the customers of the branch across various products of the bank.

1 mark

2 System should have facility to search for existing customer based on

Title+ Name 1 markTitle+ Name + DOB 1 markAccount Number 1 markCustomer Number 1 markID No 1 markHuduma No/Passport No. 1 markCertificate of Incorporation 1 markBirth Certificate No. 1 markTelephone No. 1 markKRA PIN 1 mark

3 Allow staged completion of the customer profiles creation process (e.g. create a customer with just a customer-id and name with the ability to add / modify additional details at a subsequent stage)

1 mark

4 Name, ID/Passport, photo, signature, phone no, biometrics. Get product codes attached to client IDs so immediately ID is created account no. System to bar end of day unless remaining account opening processes are completed in the system

1 mark

of 274


5 Provide facility for customer ID creation with limited information at branch

1 mark

6 Allow combination of multiple customers into a single joint account and single Customer ID

1 mark

7 Provide for de-duplication of customer id. based on various Standard / user-selectable parameters including Customer name (spelling, initials, first / middle / last names, phonetics etc.), address, contact person, etc. and provide alerts for probable duplication.

1 mark

8 Should have facility for generating Welcome letters for the new customers

1 mark

9 System should have facility of selecting customer type (individual/ non-individual ) at the beginning of customer creation process

1 mark

10 Based on the selected customer type, system to follow pre-defined workflow/procedure

1 mark

11 For existing customers, system to be capable of populating the customer information for viewing /modification

1 mark

12 Provide facility to modify / update the customer details under maker checker and send notification to account holder

1 mark

13 System should have ability to record structured profiles of each Customer of the branch including Retail, Corporate, Government etc. and able to auto-generate unique customer ID as specified by bank

1 mark

14 Provide facility to auto assign the Branch code as per bank user login ID.

1 mark

15 For individuals as single / joint account holder, proprietor, partner, director etc. as well as borrower, guarantor etc. Following details are required to be captured. The field length for capturing these customer details should be parameterized.

1 Salutation 1 mark1 Last name 1 mark

First name 1 markMiddle name 1 markTitle 1 markNext of Kin (Field to specify relationship) 1 markName of father 1 markName of Mother 1 markNationality 1 markDate of birth 1 markGender – with drop down of Male, Female orOther

1 mark

of 274


Name of guardian in case of minor 1 markMarital status (Married, single, widower etc.) 1 markResidential status 1 markCurrent address with pin code 1 markPermanent residential address 1 mark

116

Whether owned, rented, company provided quarters, family house etc.

1 mark

City 1 markTelephone Number 1 markMobile Number 1 markE-mail address 1 mark

Current Banker Details 1 markRisk Profile ( High / Medium / Low) 1 markTDS / WHT 1 mark

TDS/WHT Exemption Reason 1 markTDS/WHT Percentage. 1 mark

KYC Complied (Y/N) 1 markKYC Document List 1 mark

17Passport details such as date of issue, valid

till, issued by, passport no.1 mark

PAN / SSN/ NSSF Number and issuing authority

1 mark

Address Proof 1 markRelationship Manager 1 mark

18 OccupationEmployed/Self-employed 1 markProfession 1 markEmployers Name, If employed 1 markOffice address 1 markPhone number 1 markEmployed Since 1 markDesignation 1 markAnnual Income 1 markDetails of contact persons (with relationship ), 1 mark

Other Details 1 markDate of Commencement of Customer relation 1 markManager, Power of Attorney Holder, etc. 1 mark

19 Specific Attributes (e.g. Physical Handicap, Senior citizen, Serviceman / Ex-Serviceman, Male / Female etc.)

1 mark

20 Group Code for definition of Customer Hierarchy (used to flag individual within a group OR Family Code for grouping all members within a family) should Provide facility for at least two levels of Hierarchy.

1 mark

of 274


21 Religion 1 mark22 In case of other than individuals the following

details be capturedName of Organization 1 mark

23Constitution (e.g. Proprietorship, Partnership,

Private Ltd. Company, Public Ltd. Company, Club, Trusts, Government, Autonomous body etc.)

1 mark

24Name (s) of proprietor, partners, directors,

promoters, Secretary, Chairman, President etc.1 mark

225

Name of beneficial owners and percentage ownership in the business

1 mark

26Agents and Attorneys to Corporate accounts 1 mark

227

Physical address 1 mark

228

Provide facility for particulars of proprietors / partners / directors / promoters etc.

1 mark

29Addresses of registered / head office / factory /

local office1 mark

Phone numbers - 1 markE-mail id 1 markSector / Segment 1 markIndustry Classification 1 markDate of Incorporation 1 mark

30Date of commencement of Business and

Commercial production1 mark

331

Whether enjoying credit facility from any other bank- Y / N

1 mark

332

If Yes, then name of bank, branch and address. 1 mark

33 Details of Introducer (another existing customer and in such case customer id of that customer will do) such as name (three fields), Account No. etc.

1 mark

34 Details of Introducer 1 mark35 Provide facility for additional 10 user definable fields 1 mark36 Records must be created and authorised by the

supervisor as per maker-checker concept except system generated accounting entries. Necessary accounting entries must be passed in respective GL head. Provide option for Single / Dual authorization as per user requirement for any record / transaction level entry.

1 mark

37 Validations for data entered as defined by bank for the respective field.

1 mark

38 Mandatory field validations 1 mark

of 274


39 Should have KYC compliance validation for additional account holder.

1 mark

40 The customer data update at base level should be reflected at all other interfacing/related modules

1 mark

41 Provide facility link all individuals operating individuals / non individuals accounts including Guarantor accounts to specific Customer ID.

1 mark

42 Guarantor details – Name, ID No 1 mark43 Minor account 1 mark

Group Linkage44 Provide facility Group ID generation 1 mark45 Provide facility disable Group ID 1 mark46 Provide facility to link customers in a group 1 mark47 Provide facility to delink customer from a group 1 mark48 Comprehensive Single Window 360 degree view of

the all relationship of a client at both account level and client level covering the following details with drill down facilities

1 mark

*Account Balance 1 mark*Account Statement 1 mark*Account Snapshot (Account Number, Currency Code, Product Code, Account Type, Relationship Manager ID, Account Opening Date Personal identification document type ad number, status of account, facilities enjoyed (cheque book, Teller, Call Center, Credit Cards, SMS, Overdraft, ATM, Internet Banking, Kiosk Banking, etc.)

1 mark

*Loan Account Status 1 mark*Account Photo/Signature 1 mark*Account Cheque Return History 1 mark*Account Address Change History 1 mark*Notes Display 1 mark*Account Name Change History 1 mark*Customer Contact Details (Customer Number, Name, Spouse Name, Communication Address, Tel (Home, Office), Mobile, Email address, Office Address, Fax No. etc.)

1 mark

*Customer Relationship View (Customer Number, Relationship Band, Review period from date to date, Deposits (product wise) with account balance and base currency balance, Advances (product wise) with currency, account balance, base currency balance, Total Business, Income Earned (with breakup of the various income GLs and amount), Net Income, Total Expenses with breakup of various expense GLs, net expense, Average Balances Maintained product code wise with average

1 mark

of 274


balances, etc.)*Limit Line Enquiry 1 mark*Customer Delinquencies 1 mark*Customer Photo/Signature View 1 mark*Customer Cheque Return History 1 mark*Customer Address Change History 1 mark*Customer Notes Display 1 mark*Customer Operation Log 1 mark*Customer Data Log 1 mark

49 Under facility for search, include search based on National ID, Passport and others (Huduma number).

1 mark

50 Allow persons opening a joint account to have all their details captured on a single client ID. Include a tab under the single customer ID that will enable capture the information

1 mark

51 Allow Directors information e.g. name, ID/Passport number, contact details, contact details, physical address etc. t to be captured under the Corporate Client ID. Provide a tab under the corporate client ID for this purpose

1 mark

52 Customer module to be scalable to enable the bank create local fields for capturing additional information required by the bank for certain specific purposes/regulatory requirements at no extra cost

1 mark

53 System to support online or virtual opening of accounts

1 mark

54 Alert for transactions not authorized in the system beyond X amount of time

1 mark

55 Automation of statement mailing using email provided in the system

1 mark

56 Daily report on emailed statements 1 mark57 Authorized Head Office users to be able to post

transactions in branches e.g. revenue recovered at Head Office should be able to be booked at the branch at the time of recovery

1 mark

2.2.10 Deposits & Accounts Requirements Evaluation (172 Marks)

Evaluation Criteria Marks1 System should have facility to search for existing

customer while opening the account Name 1 marksTitle + Name + DOB 1 marksAccount Number 1 marksCustomer Number 1 marks

2 Support various liability products, including but not restricted to:

3 Savings Bank (SB) - General, Staff, Salary 1 marks

of 274


Savings Bank Institutional 1 marks Current Deposit (CA) - General, Banks, 1 marks Call Deposit (deposit payable on demand not attracting interest).

1 marks

Fixed deposit (General) where interest is paid out to the depositor periodically

1 marks

Cumulative Fixed deposit (CFD) 1 marksTerm Deposit (Short term/ Medium Term

/Long Term)1 marks

Term Deposit (Cumulative / Non-Cumulative)

1 marks

Term Deposit (Senior Citizen) 1 marksTerm Deposit (Staff) 1 marksTerm Deposit 1 marksRecurring Deposit (Predefined number and

amount of monthly deposits)1 marks

4 Provide facility to stop opening a particular type of account / product type from a specified date. Existing account to continue unless & until closed or matured.

1 marks

5 Daily Deposit Scheme 1 marksAllow auto-generation of a unique account number for each and every deposit account (SB, CA, TD, and FD ….etc.) as per bank specification.

1 marks

6 For opening FD (all products). After creation of cuts ID and creation of account number, all FD receipts under that A/c should be open with a unique number

1 marks

7 Provide facility for classification of accounts as per customer type / subtype

1 marks

8 Provide facility for maintaining various codes as per Industry standard like Product code, account code….etc.

1 marks

9 System to be capable of pre-populating the details from customer master for respective fields when creating a new account (Bank will provide and discuss the information details to be pre-populated with the selected Vendor at the time of Contract finalization)

1 marks

10 Provide facility for capturing details including but not limited to:

Title of account 1 marksName (First, Middle, Last name) with

salutation1 marks

Father’s / Husband’s Name 1 marksPostal Address 1 marks

of 274


Telephone 1 marksMobile 1 marksE-Mail 1 marksDate of Birth 1 marksGender 1 marksKRA PIN Number 1 marksPassport Number/ID No 1 marksCertificate of Incorporation 1 marksDetails of introducer. 1 marks

11 Provide facility for capturing mode of operation including but not limited to:

12For individuals: Singly, severally, jointly,

either or survivor, power of attorney (POA) holder, former or survivor. (JOINTLY OR SURVIVOR / S)

1 marks

13For other than individuals e.g. Companies /

Trusts / Clubs etc.: Any one, joint, an authorized operator and any one / more of the rest of the authorized signatories. Also Provide facility for capture of modification with history

1 marks

14

Key in facility for: Date and names of authorized persons as per partnership deed / Memorandum & Articles of Association, Certificate of Incorporation and Resolution for opening account / Trust Deed etc.

1 marks

15 To be able to add any other mode of operation 1 marks16 Provide facility for storing for specific number of

years, old account numbers (from earlier legacy system) with corresponding new account numbers.

1 marks

17 For migrated accounts, there should be mapping of old account number to new account number and display wherever account number is used for easy identification

1 marks

18 Support enquiry based on old account numbers. 1 marks19 Nomination for all accounts ( including Deposits): 1 Mark

20Provide facility for the capture of following

details including but not limited to:Name of the nominee 1 marksAddress of the nominee 1 marksRelationship with the account holder 1 marksDate birth of the nominee (if minor). 1 marksDate birth of the nominee / age of nominee

(ALL CASES)1 marks

21Name of the person authorized to receive

money in case of minor nomination1 marks

Upon renewal, system should provide a 1 marks

of 274


22 facility to continue with existing nominees or change the nominees as requested.

23 Allow for modifications and cancellations of nominations with authorization.

1 marks

24 Support recording of mode of deposit of the initial amount: Cash / Transfer / clearing.

1 marks

25 Provide facility to automatically flag the account as a “New A / C” for a period

1 marks

26 Provide a facility to automatically flag the account status based on account transactions, and below parameters as required by the bank

1 marks

27 For first "xx" months from the account opening date the account status should be "NEW"

1 marks

28

After "xx" months the account is in normal operations the account status should be "OPERATIVE"

1 marks

29

Within "xxx" period not a single transaction done in the account (Considering all the transactions / operations excluding Cheque Return & charges debited) the account status should be "INOPERATIVE"

1 marks

30System to send notifications to customers in

inoperative category1 marks

31

Within "xxx" period after account become inoperative not a single transaction done in the account. (Considering all the transactions / operations excluding Cheque Return & charges debited) the account status should be "DORMANT"

1 marks

32 Provide a facility to automatically debit the charges based on the account status as per the bank require configurations

1 marks

33 Provide capability to group the various accounts of a corporate / individuals based on predefined parameters, e.g. common first account-holder for tax deduction at source.

1 marks

34 Provide facility for applying concessions in charges to specific account / group of accounts.

1 marks

35 System to support parameterized interest payments for different types of accounts in respect of period and rate of interest and recovery of excess interest already paid in case the deposit does not run for a minimum period.

1 marks

36 System to support payment of interest at intervals e.g. Quarterly while the fixed deposit is still running even if for a year or not – drop down to choose

1 marks

of 274



1 marks

38 System to support accrual of interest with or without application at parametrized intervals on authorization. ( Rate of interest / Effective date )

1 marks


1 marks

40 Support payment of proceeds by Pay Order / credit to designated account / conversion fully or partly to a fresh Term Deposit / Demand Draft etc. Payment by cash restricted to parameterized amount at product-level.

1 marks

41 Closed accounts should be allowed only for enquiry and not for transactions.

1 marks

442 In case of subsequent substitution / cancellation, original name should be retained with date of change as history and exception report to be generated.

1 marks

43Support flagging of matured but unpaid term

deposits as overdue and include the balances as demand deposits in General Ledger Balances.

1 marks

44 Provide facility for storing, specific no of years, old account numbers (from earlier legacy system). To support enquiry based on old account no.

1 marks

45 System to generate unique receipt numbers 1 marks46 Should have facility to generate the exceptional

report in case of duplicate receipt number for different customer.

1 marks

47 Support blocking either credits or debits or both in any account.

1 marks

48 Support for enquiry of transactions based on Amount (less than, in, more than a range), Customer No. / Account No./ Account / Transaction / Date / Channel type etc.

1 marks

49 Provide facility for classification of accounts based on customer type / sub-type.

1 marks

50 As of Date (Value dating) transaction 1 marks51 Allow ‘value-dating’ all financial input posted 1 marks

52Provide automated process for re-calculating

interest for an account taking into consideration effective balances after As Of Date( value dating)

1 marks

53When authorizing a fixed deposit created, the

system should allow the authorizer to view the interest rate at the same window

1 marks

54 Signature capture to be allowed only at the domicile branch

1 marks

of 274


Accounts55 Upon final authorization, system to support

immediate printing of the cheque book for current accounts for all currencies

1 marks

56 Cheque Book facility:(Y/N) 1 marks57 if YES accept cheque from and to numbers. 1 marks58 Provide facility to issue counter cheques to

customers1 marks

59 Support recording details of the cheque series & numbers of cheque leaves issued to customer for each account separately. Cheque register

1 marks

60 Posting of cheques to be validated. Cheque Number to be within the range of cheques already issued and not paid.

1 marks

61 Provide facility to provide loose cheques to customer for CC/ Current / OD and have field to record the cheques in the system before issuance

1 marks

62 Provide facility for on-line checking of the amount of each cheque against the actual balance in the account at the time of data-entry, including during batch entry of multiple cheques.

1 marks

63 Provide facility for rejection / override message in case the cheque amount exceeds the available balance in the account.

1 marks

64 Support recovery of charges for issuing of cheque books & also permit exceptions

1 marks

65 Allow setting of Account Parameters as per banks requirement

1 marks

66 For Non-overdraft accounts, account balance cannot go negative. For exceptional cases, an alert/message should be displayed and transaction should be authorized by appropriate authority.

1 marks

67 System to include a field to capture reason where a charge in an account has been waived

1 marks

68 While posting debit transaction with cheque, the system must verify for the following but not limited to:

1 marks

69 STOP PAYMENT instructions 1 marks70 Ear Marking flag, if any, on the balance, if

there is any.1 marks

71Already-paid cheques (same cheque cannot be

paid once again).1 marks

7 Cheque number verification 1 marks

72Postdated and Back dated cheques should

not be allowed1 marks

773

A savings account should not overdraw or go below minimum balance

1 marks

of 274


74 Search fee and cheque book charges for all current account types to be recovered automatically upon completion of account opening. Where there are no funds on the account an exception report should be generated and the charge should continue to hover and be recovered once funds are available

1 marks

75 Restricted operations:76 Allow for setting of account parameter including

but not limited to:Debits not allowed 1 marksCredits not allowed 1 marksDebit / credit not allowed 1 marks

77Allow earmarking with certain amount and

the reason1 marks

78 Provide facility for revocation of such restriction under authorization.

1 marks

79 Provide facility to post BULK CREDIT entries from the electronic format for e.g. STAFF / Corporate clients, ECS Credit / Debit etc.

1 marks

80 STOP PAYMENT instruction: -

81Provide facility for rejection of Stop Payment

instruction if corresponding cheque number is already marked as paid.

1 marks

82Provide facility for flagging of the relevant

cheque when a Stop Payment instruction is entered.1 marks

83

Provide facility for recovery of charge @ KES.”x” per instruction and printing of debit advice based on amount & no. of leaves. (Bank will provide "x" parameter value at the time of configuration. The parameter set up must be flexible enough and can be changed as and when required as per the Bank's requirement by the Bank's application support staff.)

1 marks

84Provide facility for revocation of Stop

Payment instruction under authorisation.1 marks

85 Dishonored Cheques/ ECS : 1 marks

86Provide facility for tracking dishonored

cheques / ECS in any account1 marks

87 Provide facility for recovery of charge @ KES.”x” per additional withdrawal over permissible number “n” per month. (Bank will provide "x" and "n" parameter values at the time of configuration. The parameter set up must be flexible enough and can be changed as an when required as per the Bank's requirement by the Bank's application support staff.)

1 marks

88 Tracking balance falling below the minimum 1 marks

of 274


balance. When account has gone below minimum balance, system to have capacity to levy a charge

89 Recovery of charge @ KES.”x” per such occasion. (Bank provide "x" parameter value at the time of configuration. The parameter set up must be flexible enough and can be changed as an when required as per the Bank's requirement by the Bank's application support staff.)

1 marks

90 Provide facility for override of the recovery of charge under authorization to be captured in exception report.

1 marks

91 Allow a facility to create a current account with a predefined overdraft facility in case the amount in the savings account goes below the prescribed limit or is overdrawn.

1 marks

92 Minimum Balance requirements:93 Allow defining of minimum balance based on the

following but not limited to:1 marks

94 Customer type e.g. Staff, Pensioner, Individual, Firms and Companies etc.

1 marks

95 Account type e.g. SB, CA. 1 marks96 Cheque facility available (SB account) 1 marks97 Cheque facility not available (SB account) 1 marks98 ATM Facility available 1 marks

99Population category of the branch like

Metropolitan, Urban, Semi-Urban, Zone and Rural, and / or location such as District Head Quarter, State Capital etc.

1 marks

110 Enable system to levy charges in case of default on instance-basis / period-basis.

1 marks

101

Minimum Balance Charges must be levied before end of day is executed. If the balance in the account is not sufficient to charge Minimum Balance charges, a record must be kept and charges are to be recovered automatically whenever sufficient balance becomes available in the account.

1 marks

Term Deposits102 Support flagging of matured but unpaid term

deposits as overdue and include the balances as demand deposits in General Ledger.

1 marks

103 Capture deposit-scheme specific parameters e.g. minimum / maximum period and period and amount of deposit, rate / mode of payment of interest, maturity value etc.

1 marks

104 Upon final authorization, system to support immediate printing of the deposit receipt

1 marks

of 274


105 Should have facility for generating report log TD receipt printing done & pending for the day

1 marks

106 Provide facility for generation of notices to be sent to customers in case of overdue installments for more than parameterized period for RD

1 marks

107 Provide facility for conversion of full or part of one type of deposit into another with facility of waiver of penal interest on premature payment of a term deposit converted into another term deposit.

1 marks

108 Support maintenance of:

109CFD Interest Accrual Account for holding

CFD quarterly accruals.1 marks

110 Interest Paid CFD Account for making payments of interest on CFD for current quarter.

1 marks

111

Interest Accrued and Payable-Non-CFD for holding quarterly accruals in respect of other term deposits. The balance to be credited to Interest Paid-Non CFD on the same day

1 marks

112Interest Paid on TD for making payments of

interest on TD for current quarter.1 marks

113In case of premature payment Provide facility

for reversal of recoverable interest from CFD account to CFD interest account.

1 marks

114 Closure on maturity – Regular RD (RD is treated as regular on receiving all installments on or before due date and interest payment is for pre fixed maturity value arrived based on quarterly compounding of monthly installments

1 marks

115 Closure on Maturity – Regular but Installment with default (In this case all installment received but some or all installments with delay – provision to pay full maturity value and deduct penalty for delayed installments from proceeds of maturity value or to pay interest on monthly product basis on half yearly the compounding together with collecting penalty.

1 marks

116 Closure on Maturity – Irregular RD (If all installments are not received, it is treated as Irregular RD) – In such cases closure to pay interest on monthly product basis on half yearly the compounding together with collecting penalty.

1 marks

117 Provide facility for capture of deposit-scheme specific norms (parameterized) such as minimum period (e.g. x days for Fixed Deposits), maximum period (e.g. y months for all Term Deposits) as also

1 marks

of 274


other details such as period of deposit, amount of deposit, payment of interest and maturity value etc. where x and y are parameters.

118 System to support loan facility against deposit accounts with linking & lien marking with parameters like rate of interest, margin, purpose due date, installment etc. System to support lien marking for deposit accounts

1 marks

119 Overdue Term deposits120 To support renewal of Overdue Term Deposits for

overdue period1 marks

121 Should have facility for generating letters at predefined dates for renewal of Term Deposits.

1 marks

122 Should have facility for generating letters of WHT/TDS

1 marks

Standing Instruction123 Periodical Standing Instructions to be executed at

the time at Start of day / End of day1 marks

124 Provide flexibility for setting up and processing any type of standing instructions as and when required with different parameters including but not limited to:

1 marks

125 Fixed Amount Fixed Period / Variable amount / Variable amount with limit / Variable frequency / Event driven / Maintenance of balance

1 marks

126 Provide facility for generation of Report on: 1 marks1127 Standing Instructions executed, and 1 marks1128 Standing Instructions failed in execution. 1 marks

129 Provide a facility to allow carry forward of the standing instructions, for some user-definable period, till the condition for processing the standing instruction is met or number of attempts made

1 marks

130 For failed SI due to insufficient funds, the credit in the account should be made available for withdrawal and the full SI to be recovered when the sufficient credit is available to recover the SI.

1 marks

131 Alert be generated for failed STO 1 marksFDR Account

132 System to have capacity to close Fixed Deposit account

1 marks

Accounts With Zero Balances133 Account be closed within 'x' period of time 1 marks

of 274


Account Transfers134 System to allow account transfers from one branch

to another1 marks

135 System to allow account number portability from one branch to another

1 marks

Foreign currency cheques136 System to issue both local currency and foreign

currency cheques and marking them in the system1 marks

Customer profitability136 Ability to generate profitability per customer 1 marks

Authorization137 Alert for transactions not authorized in the system

beyond X amount of time1 marks

Signatory and mandate details138 System to allow for more signatories/signatures and

photos to be displayed under joint or corporate client. The number of signatories should be as many as allowed under the company Act

1 marks

139 System to allow only for scanning of signatures without having to crop the same. Cropping of signatures changes the quality of the images

1 marks

140 When keying in the mandate, the system should provide for input of special/exceptional Mandate requirements e.g. introduction of Powers of Attorney or Agents

1 marks

141 Account opening report to have an option of separating loans from deposit accounts as well as have ability to sort using diverse parameters

1 marks

142 The AML watch list to be included in the system to allow for pop ups and alerts when transacting or account opening

1 marks

143 System to support charging a client if STO fails because of underfunding the account

1 marks

144 System not to charge tax on tax exempt accounts/ deposits on maturity

1 marks

2.2.11 Clearing & Settlement Requirements Evaluation (300 Marks)Evaluation Criteria Marks

1 Pro142vide facility for following categories of clearing: 1 mark2 MICR clearing 1 mark3 Non MICR clearing 1 mark4 High value clearing 1 mark5 National clearing 1 mark

of 274


6 Cheque truncation-Image Based Clearing. 1 mark7 Electronic Clearing Service 1 mark8 Outstation clearing 1 mark9 System should support the following types of clearing :10 Inward clearing 1 mark11 Outward clearing 1 mark12 Clearing returns 1 mark13 Provide facility to capture Bank master - details containing

particulars of banks / branches participating in clearing at each center.

1 mark

14 Provide facility to capture the following information for all categories of clearing, but not limited to:

1 mark

15 Customer ID 1 mark16 Customer's account type and number 1 mark17 Customer name/ Joint names 1 mark18 Cheque number / Cheque date 1 mark19 City code 1 mark20 Branch code 1 mark21 Bank code 1 mark23 Type of instrument 1 mark24 Amount 1 mark25 Account number of issuing party 1 mark26 MICR code 1 mark27 Narration 1 mark28 Provide facility for capture of cheque image for enabling

capacity for cheque truncation.1 mark

29 To Provide facility for more than one clearing per day 1 mark

30 There may be more than one Clearing zone in most of the Centers:

1 mark

31 Customer accounts to be credited on a pre-defined working day

1 mark

32 Customer may be allowed to utilize the funds after a pre-defined number of days as per the clearing norms at the center.

1 mark

33 The system should provide for flexibility to allow the user to define these accounts and the amount to be credited to the accounts on the instruments being cleared.

1 mark

34 Provide facility for on line posting, as well as batch posting. System should have measures for double-checking of batches posted to ensure correctness.

1 mark

35 Provide facility for receipt of clearing data from the branches to service branches 'on line'.

1 mark

of 274


36 Provide facility to handle of multiple cheques deposited under one Pay-in slip.

1 mark

37 Provide facility to credit to multiple accounts from one cheque.

1 mark

38 Provide facility for automatic transfer of net balance to Clearing account

1 mark

39 Give daily status of net amount ‘due to’ or ‘due by' clearing house

1 mark

40 Provide facility to upload external statement of clearing house for reconciliation.

1 mark

41 To provide for handling of electronic funds transfers 1 mark42 Provide facility to begin and end of clearing cycle so that no

instruments can be included after the end of the clearing cycle.

1 mark

43 Allow the user to define the period by which credit has to be passed on to the branches for different types of clearing.

1 mark

44 Provide facility for automatic transfer of net balance to clearing account / local clearing after proper authorisation

1 mark

45 To provide facility for46 Separate schedule 1 mark47 Separate code numbers and passing of contra vouchers 1 mark

Outward clearing48 Support generation of list of instruments bank wise (for inter-

bank) and branch wise (for intra-bank) for each clearing (formats of the lists to be defined by the user ).

1 mark

49 Allow defining the following dates:50 Clearing data entry date, credit date and clearing clear date: 1 mark51 Posted date 1 mark52 Cleared date: funds are cleared and available to the customer

provided for crediting the entries in the account based on these dates and mark the balances as cleared etc.

1 mark

53 Provide facility for marking for returned cheques and posting them automatically to the customer’s accounts along with charges.

1 mark

54 Provide facility to charge interest only on available/clear balance in case of cheque returns and not the total balance from data entry date.

1 mark

55 Provide flexibility to release / hold uncleared effects of the presented instruments at the option of the bank in the event of any bank not participating in clearing etc.

1 mark

56 Provide facility for postponement of uncleared funds and not advancement in relation to pre-defined days / period.

1 mark

of 274


57 Provide facility to user defined of clearing batch parameters at Bank and specific Branch level.

1 mark

58 To provide for authorization of all entries. 1 mark59 Support automatic credit to customer’s accounts for cheques

that have been cleared.1 mark

60 Ability to automatically reverse the entries in customer accounts and contra entries for cheques that have been returned unpaid.

1 mark

61 Ability to debit the customer's account for recovery of the charges for unpaid cheques automatically.

1 mark

62 Support re-present option for those cheques, which have been returned unpaid.

1 mark

63 In case of multiple cheque deposited in single slip, there should be facility to enter cheque details separately.

1 mark

64 In case of multiple cheque deposited in single slip, there should be facility to mark cheque status separately ( Delayed / returned /Cleared)

1 mark

65 In case of multiple cheque deposited in single slip, there should be facility to pass credit entry in respective account for the cheque status marked as Cleared.

1 mark

Inward clearing66 Support following functionality for all categories of Inward

clearing:1 mark

67 Provide facility for validation of cheque number / date and stop payment instructions before the cheque is cleared for payment.

1 mark

68 A cheque number once paid should not be allowed to be presented again for payment

1 mark

69 In case of a batch posting, system should reduce the available balance dynamically from the Customer's account after every cheque.

1 mark

70 Support generation of auto referral to the authorized persons in case of insufficient funds.

1 mark

71 To generate voucher and Cheque Return Advice in respect of returned cheques containing the following details:

1 mark

72 Service charges to be automatically debited to the customer's account.

1 mark

73 Reason for return. 1 mark74 Cheque details. 1 mark75 Name of drawee / Presenting banker should be mentioned on

the return memo1 mark

76 Provide facility to recover outstanding charges by debiting customer account and crediting respective charges account whenever the there is sufficient balance available.

1 mark

of 274


77 To generate responding entries in respect of inward clearing. 1 mark

78 To provide for all posting of cheques, account wise individually.

1 mark

79 To provide for scrutiny of list and confirmation of cheques to be returned.

1 mark

80 Provide facility for authorization of remaining entries excluding the deletion entries in respect of returned instruments.

1 mark

81 Provide facility for configuring the parking account for inward clearing

1 mark

82 Enable data upload of inward items to inward clearing based on the data received in soft copy from Clearing house or Input the data generated by the MICR reader at the service branch and also to modify cheque date and payee's name.

1 mark

Remittances83 Remittance transactions involves funds transfer which will

include and is not restricted to Demand draft, Pay Order, Bank Order, Electronic Fund Transfer, Mail Transfer, Telegraphic Transfer (in local and foreign Currency), RTGS, NEFT. This includes inward and outward remittance.

1 mark

84 Allow remittance for customers and non-customers 1 mark85 Provide creation of transaction type which include specific

multi-purpose products like:86 Demand Draft 1 mark87 Pay Order 1 mark88 Direct transfer of funds 1 mark89 Telegraphic Transfers 1 mark90 Electronic fund transfers (NEFT) 1 mark91 RTGS 1 mark92 Enable creation of a daily rate master for definition of foreign

currency conversion rates to be applied for retail transactions.

1 mark

93 Provide maintenance of currency master history for user defined periods

1 mark

94 Allow overriding default currency rates. Such overriding should be captured in exception report

1 mark

95 Enable waiver / reduction of charges on specific transactions for any account with appropriate approval and inclusion in exception report

1 mark

96 Enable online approval of transaction by auto referral to appropriate authority

1 mark

of 274


97 Allow definition of maximum limit for cash transaction for each product for both issue and payment.

1 mark

98 Enable processing of transactions in both on line and batch mode. Transaction entry should be possible in single input mode and bulk import of data.

1 mark

99 Provide facility for issuance of DD / PO / EFT / TT against the following mode of payments-cash, debiting account of the customer at the same branch, debiting account of the customer at another branch (should support multi branch transactions). Internal debit note / voucher, bill negotiated / discounted and debiting third party account with proper authorisation.

1 mark

100

Provide printing of instruments in user definable formats 1 mark

101

Provide printing of instruments in preprinted Continuous Stationery

1 mark

102

Provide maintenance of stock of instruments and issue of books / running stationery there against.

1 mark

103

System should have facility to automatically pick up the next DD / PO instrument number from the stock

1 mark

104

Provide input for name of the payee, amount and date. 1 mark

105

Provide branch code and branch name in a drop down list box 1 mark

106

Provide Drawee branch Name and Code in a drop down list box

1 mark

107

Provide facility for account status at the time of posting of Voucher

1 mark

108

Provide instant printing of DD / Pay Order / Bank Order. 1 mark

109

Enable defining Service charges (parameters) 1 mark

110

Enable passing of Accounting entries / advice as per bank’s requirements

1 mark

111

Provide facility for using one cheque for multiple remittances 1 mark

112

Provide facility for Multiple Debits and Single/ Multiple Remittances

1 mark

113

Facility for receipt and authorizing payment which will include but not restricted to:

1 mark

114

Batch receipt of messages 1 mark

115

Validation of instruments noted for caution instruments reported lost (stop payments)

1 mark

of 274


116

Validation for date of instrument (period to be parameterized) 1 mark

117

Validation for duplicate issued 1 mark

118

Validation for instruments already paid 1 mark

119

Provide facility for payment on Instrument / instructions in case cancellation in the modes which include but not restricted to

1 mark

120

Crediting account of customer at the same branch or another Branch

1 mark

121

Issue of another instrument / remittance instructions like Bankers cheque

1 mark

122

Crediting third party accounts and Internal accounts 1 mark

123

Provide facility for cancellation of instruments against user determined conditions for Cancellation. Facility to cancel an instrument and credit customers’ accounts with proceeds with recovery of charges for cancellation.

1 mark

124

Provide facility for validation of instrument numbers against stop payment instruction before actual pay out of the amount

1 mark

125

Support validation of instruments before payment that will ensure that instrument / remittance are not paid twice or instruments cancelled / reported as lost are not honored. The validation will include (a) Instruments noted for caution. (b) Instruments reported as lost. (c) Instrument remittances paid. (d) Intra office suspense account.

1 mark

126

Support issuance of duplicate / revalidation by the issuing branch. Period for allowing revalidation to be user definable with recovery of charges for the same.

1 mark

127

Provide facility for transfer of outstanding instruments beyond the cutoff date / period to Head Office with related IBCN entries and user specific details

1 mark

128

Allow facility to record pre-requisite conditions for duplicate issue. Validation against these conditions will include but is not restricted to:

1 mark

129

Original issue reference 1 mark

130

Reported lost 1 mark

131

Stop instructions 1 mark

132

Duplicate already issued 1 mark

13 Receipt of non-payment advice 1 mark

of 274


3134

Receipt of indemnity bond 1 mark

135

Provide facility for referencing the original instrument / remittance while issuing a duplicate instruments / remittance

1 mark

136

Provide facility for cancellation of DD(including cash DD) / Remittance on the date of issue after authorization.

1 mark

137

Provide facility for cancellation of DD (including cash DD) / Remittance on subsequent dates

1 mark

138

Provide facility for generation of accounting entries 1 mark

139

Ability to automatically issue instructions for canceling the validity of the original instruments on issuance of duplicate

1 mark

140

Provide facility for generation of revalidated DD and remittance

1 mark

141

Provide facility for generating the advice for duplicate and revalidation of DD / remittance

1 mark

142

Provide facility for creation of differential service charge structure which should consider parameters like:

1 mark

143

Customer 1 mark

144

Product (DD / MT / TT Issued / TT Discounted etc.) 1 mark

145

Duplicate issuance 1 mark

146

Cancellation charges 1 mark

147

Amount 1 mark

148

Slab or tier charges 1 mark

149

Postal / Telegraph / Telecom charges 1 mark

150

Provide facility for status for specific instrument / remittance which may include but is not restricted to:

1 mark

151

Unique reference number 1 mark

152

Transaction type 1 mark

153

Date 1 mark

154

Customer 1 mark

155

Branch 1 mark

15 Customer identification number 1 mark

of 274


6157

Combination of any two or more of the above 1 mark

158

Do not allow modification of DD / Remittance once it is printed

1 mark

159

Allow entries to be authorized by the officials 1 mark

160

Allow printing of DD / PO only on authorisation 1 mark

IBC/OBC (Bills)General requirements

161

Provide facility for:

162

Defining work flow requirements for authorizations based on hierarchy levels and amounts for different types of transactions.

1 mark

163

Unique reference number generated for each transaction should be a combination based on branch ID, type of transaction, currency and Serial Number.

1 mark

164

To provide user with appropriate messages with the solution to remedy any incorrect entries made.

1 mark

165

To provide for creation of multi-level authorisation for the purpose of committing the transactions

1 mark

166

To prompt the user before any transaction is completed 1 mark

167

Not to allow the processing of the transaction where either credits or debits or both are blocked in any account.

1 mark

168

To process all types of transactions and to provide for all types of facility to draw up the list of documents missing when the user is processing the transaction.

1 mark

169

In case of any discrepancies during the validation of documents against the check list, the same should be forwarded to the next approving authority as per the work flow defined by the bank

1 mark

170

To enable creation of new transaction by copying an existing transaction with the facility to change all fields

1 mark

171

Provide facility for linking /passing entries of all transactions to day book, subsidiary and General Ledger.

1 mark

172

Enable creation of methods of calculation of commission, interest and other charges based on:

173

Product category / sub category 1 mark

174

Account Status 1 mark

175

Usance period / validity period 1 mark

of 274


176

Returned instruments, 1 mark

177

Collecting Bank / Agency (sharing of commission etc.) 1 mark

178

Amount 1 mark

179

Provide facility for charging of commission upfront or from drawee or on realization.

1 mark

180

Provide facility to maintain register for the balance amount of commission, recovery of balance of commission along with interest

1 mark

181

To enable user to manually overwrite the amount of commission and / or interest amount, any additional amounts automatically calculated by the system. Any such overwrite should be captured in the exception report.

1 mark

182

To provide for verification against the limits available before accepting the application for purchase of instruments for processing and give appropriate messages / error messages. For this purpose the system should have access to

183

Sanctioned limits 1 mark

184

Limits utilized 1 mark

185

Limits available 1 mark

186

To ensure updating of customer limits on real time based on every new transaction, retirement or close out.

1 mark

187

To enable picking up of customer information for all transaction from the data base

1 mark

188

To provide capability to search a transaction based on various fields or a combination of fields such as

1 mark

189

Customer ID 1 mark

190

Date of transaction / range of dates 1 mark

191

Reference number 1 mark

192

Type of transaction 1 mark

193

Amounts 1 mark

194

Selection criteria defined by the user 1 mark

195

To enable customization of new products as and when introduced by the bank

1 mark

196

Provide facility to auto generate the contra entries upon the bill transaction is entered.

1 mark

of 274


Outward bills /cheque for collection197

Provide facility for 1 mark

198

Our reference number 1 mark

199

Date of lodgment 1 mark

200

Name of party / account number 1 mark

201

Cheque / DD number with date 1 mark

202

Drawn on bank / branch with city 1 mark

203

Amount of cheque / instrument 1 mark

204

Drawee account no. and name 1 mark

205

Sent for collection to whom like service branch, our branch, other bank with address

1 mark

206

Commission, postage 1 mark

207

Returned instruments with reasons thereof 1 mark

208

Provide facility for a separate head in P&L subsidiary “ Interest paid account on delayed collection”

1 mark

209

Waiver of comm. From staff & quasi govt. bodies 1 mark

210

Provide facility for printing 1 mark

211

Passing of contra voucher 1 mark

212

Reminders for unrealized instruments beyond specified number of days

1 mark

Realization of cheque sent for Collection213

Provide facility for payment of interest for delayed collection of cheques beyond specified period in respect of state capitals and other places as per Goiporia Committee recommendations - specified period to be parameterized separately for state capital and other places.

1 mark

214

Provide facility for realisation register with the following details

215

Date 1 mark

216

Our number 1 mark

217

Amount realized and amount credited 1 mark

218

Our commission 1 mark

of 274


219

Other bank’s charges 1 mark

220

Postages 1 mark

221

Number of days taken for realization 1 mark

222

Interest for delayed period if any 1 mark

223

Sharing of commission 50% in case of instruments sent to other banks

1 mark

224

Returned Instruments 1 mark

225

Generate control / de-control voucher and advices for the party

1 mark

226

Transfer from Collection to purchase 1 mark

227

To provide for authorisation - 1 mark

228

Details of credit to be given 1 mark

229

Generate de-control vouchers 1 mark

Outward Bills for Collection Register230

To provide for collection register with the following details

231


232

Our bill number 1 mark

233


234

Amount 1 mark

235

Drawee details 1 mark

236

Details of usance / due date 1 mark

237

Our commission and collecting Bank’s charges if any 1 mark

238

Postage 1 mark

239

Interest charges / recovered as per drawers instructions 1 mark

240

Details of documents enclosed like Invoice, Lorry / Railway Receipt / Airway Bill etc. with date / number / amount

1 mark

241


1 mark

of 274


242

To whom sent for collection 1 mark

243

Details of bill returned 1 mark

244

To generate-

245

Register for a given period 1 mark

246

Covering schedule along with necessary instructions. 1 mark

247

Control vouchers 1 mark

248

Realisation of billsTo provide for register with following details

1 mark

249

Bill number 1 mark

250


251

Date of realization 1 mark

252


253

Other Bank’s charges, our commission / postages 1 mark

254

To search the bill from the bill number, date of lodgment and original bill amount

1 mark

255

To generate de-control vouchers 1 mark

Inward cheques and bills received for collection256

To provide for register with the following details:

257

Our number 1 mark

258

Date 1 mark

259

Their number 1 mark

260

Name of our customer / drawee 1 mark

261

Bill number / cheque number & date (date to be validated in case of cheque)

1 mark

262

Amount 1 mark

263

From whom received with address- (a) From Branches (b) From others – the contra entries in respect of these two categories are to be shown separately in GL

1 mark

264

Their commission and interest 1 mark

of 274


265

Our commission and postage 1 mark

266

Details of documents enclosed like Invoice, Lorry / Railway Receipt, Airway Bill etc. with date / number / amount / Transport Operator (validation of date of LR / RR with provision to override with exception report)

1 mark

267

Due date 1 mark

268

To generate contra vouchers 1 mark

Realisation of Inward bills269

To generate register with following details 1 mark

270

Date 1 mark

271

Name of customer / drawer / drawee 1 mark

272

Branch 1 mark

273

Amount of bill 1 mark

274

Amount remitted 1 mark

275

Our commission including charges on post parcels if any and postage / their charges

1 mark

276

Interest details including number of days and rate of interest. 1 mark

277

To generate realisation register and contra voucher and remittance of proceeds as per instructions of drawer / bank. System should prepare DD in case of cheques / bills received other than from our own branches. In case of our own branches system should prepare IBCN. The amount to be remitted should be based on the instructions of the drawer.

1 mark

ECS & NEFTECS

278

Master program to maintain Service Provider Code (Mandate details-Service Provider Code and Address)

1 mark

279

Provision for handling ECS for Weekly Holiday Branches. 1 mark

280

Updating of records by individual branches (provision to be made after the branch sign off)

1 mark

281

Provision for Stopping the Mandates of account wise. 1 mark

282

Charges have to be taken care for rejection with Insufficient Funds.

1 mark

of 274


283

Report for viewing authorized ECS records, status for a day, ECS data uploaded detail, debit mandate details

1 mark

284

Provide facility to interface with sms banking module to send sms for 'insufficient funds'

1 mark

285

Provide facility to auto recover the ECS charges and should provide proper bifurcation of charges.

1 mark

NEFT MODULE286

Program to maintain NEFT Batches 1 mark

287

Provide facility for mandatory validations while creating the NEFT batch file and should not allowed to proceed further without corrections.Data Entry Special CharactersTime slot

1 mark

288

Provide facility to populate customer information when debit account number is entered with the facility to auto validation for data quality and edit the populated information for manually processing the NEFT transaction.

1 mark

289

Provide facility to create separate batch files for processing net banking NEFT transactions and manual NEFT transactions.

1 mark

290

Program for entry and authorization of transaction at branch level within the available Batch for transaction

1 mark

291

For NEFT transaction, On receipt of inward remittances from API the accounts has to be credited to the beneficiary account in case of Customer Payment and respective General ledger in case of Inter Bank payments.

1 mark

292

For NEFT transaction, Provide facility to check the rejection messages and upon changes & authorisation, amount to be credited to the beneficiary account in case of Customer Payment and respective General ledger in case of Inter Bank payments.

1 mark

293

Provide facility to maintain Rejection parameter master for NEFT transactions.

1 mark

294

Add new branches for NEFT on opening of new branches 1 mark

295

Query and Reports to be provided to branches for smooth running of NEFT program

1 mark

296

Provide facility to view the batch file processing branch wise (all or specific) status as and when required as per bank's parameters.

1 mark

297

Provide facility for processing the high value NEFT transaction with proper authorisation of treasury dept.

1 mark

298

Provide a facility for Origination of Direct Debits 1 mark

of 274


299 System to have a direct debit module

1 mark

Remittances300

System to support multicurrency transactions for local RTGSs and foreign TTs processed from customer accounts

1 mark

301

System to support multicurrency transactions for local RTGSs and foreign TTs processed from bank GLs

1 mark

302


1 mark

303

Unique reference numbers generated for each transaction based on the defined parameters

1 mark

304

System to generate relevant message types for remittances processed and upload to swift through STP

1 mark

305

System to generate MT199 for all incoming RTGSs and TTs for automatic updating of the SWIFT Global Tracker

1 mark

306

Provide a reconciliation modules for all the nostro accounts utilised in settlement

1 mark

307

System to capture cross-currency transactions without converting to KES first

1 mark

308

Purpose of payment to be captured 1 mark

309

System be able to capture customer forward deals and attach to relevant transactions

1 mark

310

Interest accrue matches with market calculator 1 mark

311

Daily revaluation updates the position with relevant income/loss

1 mark

312

Should be able to capture customer/bank treasury bonds/bills 1 mark

2.2.12 Teller Operations Requirements Evaluation (65 Marks)Evaluation Criteria Marks

1 Provide facility to define functions / operations, which can be performed by each teller / cashier:

1 mark

2 Support limits for tellers based on:3 Type of transactions 1 mark4 Amount of transactions 1 mark5 Provide facility for the teller to view customer’s signature at

account level on screen for verification and account operating instructions.

1 mark

6 Provide teller functions in local currency as well as foreign currencies.

1 mark

7 Provide a facility to record ‘quantity’ of currency denominations for each transaction including for cash removal from safe deposit vault and depositing into safe

1 mark

of 274


deposit vault.8 Support exchange of currency, denomination-wise, between

two or more tellers / cashiers and head cashier.1 mark

9 Support tendering of change to customer, denomination-wise.

1 mark

10 Support receipt of cash for issue of demand drafts, pay orders, bank orders, traveler’s cheques etc.

1 mark

11 Provide for issue / printing of drafts, pay orders, bank orders etc. by the teller, after authorisation.

1 mark

12 Allow for waiver of certain charges (for e.g. Overriding service charges), based on user- defined parameters). Such waivers / overrides must be captured in exception report.

1 mark

13 Allow cash withdrawal across branches and validate for cheque number, cheque date, stop payments in case cheques are used for withdrawals, with facility to auto debit charges

1 mark

14 Provide facility to enter transaction (e.g. Cheques) in batch mode or single transaction mode.

1 mark

15 Support input of transactions affecting internal accounts like Cash-Remittance-in-Transit, Working Expenses, Sundry Debtors, Rent Payable etc.

1 mark

16 Allow authorization of inputs, when done for a batch, only when the batch is balanced. Support for unbalanced batches based on entry / partial updation etc. in case of problems during entry / updation.

1 mark

17 Allow marking of transactions as reversed (rather than passing contra entry to cancel the erroneous entry) which should be captured in exception report.

1 mark

18 Support functionality to allow access to the above-mentioned facility only to predefined users

1 mark

19 Support facility to authorize multiple transactions using a single function with overrides if any for transactions. Any overrides should be captured in exception report.

1 mark

Cashier / Teller Operations20 Cashier to be able to query / call on terminal-only cash

transactions already authorized for payment, pay cash, enter denominations and flag transaction as “cash paid”.

1 mark

21 Authorized users to monitor cash limits and receive alerts. 1 mark

22 Tellers holding cash above their limit not to be allowed to proceed until they pay excess cash held

1 mark

23 Provide for enquiring on status of transactions, whether entered, already authorized etc. based on amount, account number and type etc.

1 mark

of 274


24 Generation of cash scrolls, payment and receipt for end-of-day handing over of cash to Chief / Head cashier / Cashier in Charge.

1 mark

25 Provide a facility for cash deposit to all permitted account types for credit of accounts across all CBS branches.(Subject to user defined changes over and above predefined limit of cash deposit.)

1 mark

26 Support cheque deposit (and their classification for the purpose of printing of statements and monitoring) of the following types:

1 mark

27 Cheque drawn on another customer of same branch. 1 mark28 Cheque drawn on another customer of same bank but

different branch.1 mark

29 Cheque drawn on another customer of another bank in the same city.

1 mark

30 Cheque drawn on another customer of another bank in different cities.

1 mark

31 No use of withdrawal slips or vouchers for withdrawals form current accounts

1 mark

32 Enable cash withdrawal from specified account type using withdrawal slips / vouchers at only home branch, subject to exceptions with proper authorisation. In case of exceptions charges can be levied at bank's discretion and generate exceptional transaction report.

1 mark

33 Passbook layouts and transactions should be user-definable 1 mark34 In case of exceptions charges can be levied at bank's

discretion and generate exceptional transaction report at the transacting branch

1 mark

35 Support recording currency-wise deposits and withdrawals of foreign currency, denomination-wise.

1 mark

36 Should be able to reflect position of foreign currency held, currency-wise and denomination-wise.

1 mark

37 There should be a provision for storing a token numbers for each cash payment / cash receipt for customer transactions

1 mark

38 Ability for individual teller to close off their till without affecting the other tellers under authorization

1 mark

Chief / Head Cashier Operations39 Support facility to record open / close status of vault 1 mark40 Provide for vault to teller and teller to vault transaction,

denomination wise1 mark

41 Enable recording of open / close status of each teller’s till. 1 mark42 Allow authorizing of the tills only after they have been

balanced with physical cash.1 mark

of 274


43 Support automatic verification of Cash-on-Hand position (as per General Ledger) at end-of-day (EOD) with EOD cash inventory position and pop-up message in case of discrepancy. (EOD to be allowed to go ahead only if there is no difference in amount and denomination).

1 mark

44 Should allow user for a teller function and a cashier function optionally.

1 mark

45 Cashier should be able to receive / pay amounts with authorizations. At least two levels of authorizations must be provided for.

1 mark

46 There should be a provision for storing a token numbers for each cash payment / cash receipt for vault transactions

1 mark

47 Provide facility to monitor branch wise cash retention limit with excess cash alert at branch and branch wise summarized alert of all branches to head office.

1 mark

48 Provide facility to record cash remittance register(Inward /outward)

1 mark

49 Allow the Cash deposit module to be configurable to enable the bank define specific cash deposit modules for specific clients who request for capturing of specific information during cash deposit. Reports to be in various file formats i.e. csv,pdf,xml to allow for file sharing/upload eg Schools, Water companies, KRA etc.

1 mark

50 System to support a cash scroll that captures a debit and credit

1 mark

51 System to complete Teller transactions to enable printing of cash deposit or withdrawal receipt

1 mark

52 System to have capacity to integrate with biometric system 1 mark

53 System be scalable to include fields for capturing additional information

1 mark

54 System to provide Teller with at least last 10 transactions for all debits and credits

1 mark

55 System to have inbuilt transaction Codes 1 mark56 Teller module to support cross currency transactions 1 mark57 Automated cash withdrawal/deposit description (Drop

down) but with also additional fields for additional narration1 mark

58 Provide ability to mark limits for different customers which will pop up when the Teller is transacting at the counter

1 mark

59 Ability to print teller receipts after completion of transactions

1 mark

60 Provide a field to capture Name of person depositing or withdrawing cash, their ID Number and Telephone Number

1 mark

61 Alert for transactions not authorised in the system beyond x amount of time

1 mark

of 274


62 System to have pop-ups to alert the teller when the account transacting exceeds the daily allowable deposit limit for declaration as per Central Bank of Kenya requirements on AML

1 mark

63 Automate cheque deposits and print a slip for the same 1 mark

64 System to pop up accounts with withdrawal restrictions under the mandate when the teller is performing the withdrawal process

1 mark

65 The system should allow Teller cash summary to be printed in a format that cannot be edited

1 mark

66 System should give offline balances whenever there is a downtime this will assist Tellers continue processing requests

1 mark

2.2.13 Trade Finance Requirements Evaluation (306 Marks)# Evaluation Criteria Marks1 To provide for register with the following details for

cheque /Draft purchase2 Date 1 mark3 Our number 1 mark4 Name of party / account number 1 mark5 Staff / non-staff 1 mark6 Amount of Cheque and amount credited 1 mark7 Cheque number and date (date to be validated) 1 mark8 Drawee bank / branch 1 mark9 To whom sent for collection 1 mark10 Interest / commission / Service Tax /postage / other bank’s

charges if any1 mark

11 Date of realization 1 mark12 Provide facility to link customer ID with Cheque/ Draft

account.1 mark

13 To generate covering schedule (Outstation Purchase only) for dispatch including remittance and dispatch instructions on realisation (e.g. TT / Courier ) as also necessary vouchers and provide for charging of commission upfront

1 mark

14 Provision to maintain the ledgers party wise 1 markRealisation of cheques purchased

15 To generate register with the following details 1 mark16 Date of realization 1 mark17 Our number 1 mark18 Amount realized / credited 1 mark19 Rate of interest 1 mark20 Amount of interest 1 mark

of 274


21 Other bank’s charges 1 mark22 Column for returned instrument (to be debited to Past due

and dishonored bills account in case of insufficient funds in the party’s account) with reasons thereof

1 mark

23 To provide facility for entries to park and convert these from parking account to respective account upon cheque realisation.

1 mark

24 Provide facility to restrict total clean Cheque purchase amount limit up to Rs. X for a customer (X is parameter)

1 mark

25 Provide facility to mark the customer as "Defaulter" when the cheque deposited and purchased is returned unpaid due to financial reason. System should restrict from providing cheque purchase facility to such Defaulter customers.

1 mark

26 To provide facility for entries for converting 1 mark27 Cheque Purchase to Cheque Collection 1 mark28 Returning of cheques with reasons thereof 1 mark29 Charging of interest from day one with penal interest 1 mark30 Our bill number 1 mark31 Name of party / account number 1 mark32 Bill amount / Amount credited 1 mark33 Margin held 1 mark34 Drawee details 1 mark35 Whether documentary or clean bill 1 mark36 Details of demand bills (Demand bills purchased are to be

shown separately in general ledger (GL) under Inland Bills Purchased (Demand) account head)

1 mark

37 Details of documents enclosed like Invoice, Lorry / Railway Receipt, Airway Bill etc. with date / number / amount / Transport Operator

1 mark

38 Our commission and collecting Bank’s charges if any 1 mark39 Postage 1 mark40 Interest charges / recovered 1 mark41 Instruction to party (regarding commission, overdue interest

and disposal instructions)1 mark

42 To whom sent for collection 1 mark43 Date of realization 1 mark44 Details of returned instrument (to be debited to past due and

dishonored bills account in case of insufficient funds in the party’s account) with reasons

1 mark

45 Provide facility for generating- 1 mark46 Register 1 mark47 Covering schedules for dispatch along with instructions of

the drawers of the bill1 mark

48 Vouchers 1 mark

of 274


49 Party wise ledger 1 mark50 Party wise bills outstanding & cheque pending for collection

(provision to provide age wise analysis for a given period)1 mark

51 Maintenance of Bills Purchase Register and Bills Purchase Ledger party wise

1 mark

52 Maintenance of parking account for margin held 1 mark53 Maintenance of list of IBA approved Transport Operators and

validation thereof while purchasing Bills1 mark

Bills for discounting54 To generate register with the following details: 1 mark55 Date of Purchase 1 mark56 Bill number and Bill Date 1 mark57 Name of party / account number 1 mark58 Amount 1 mark59 Drawee 1 mark60 Details of Bill of Exchange number of days of usance period

and due date1 mark

61 Details of documents enclosed like Invoice, Lorry / Railway Receipt, Airway Bill etc. with date / number / amount

1 mark

62 Insurance details 1 mark63 Discount, amount of discount 1 mark64 Commission / Service Tax /postage 1 mark65 Date of realization 1 mark66 Margin Deducted 1 mark67 Details of returned Instrument (to be debited to Past due and

dishonored bills account in case of insufficient funds in the party’s account) with reasons thereof

1 mark

68 Provide facility to link customer ID with Bill Discount account.

1 mark

69 To generate schedule for dispatch along with instructions 1 mark70 Maintenance of Bills Discounted Register and Bills

Discounted Ledger party wise1 mark

71 Maintenance of parking account for margin held 1 mark72 Maintenance of list of IBA approved Transport Operators and

validation thereof while purchasing Bills1 mark

73 Provide facility to process Bill discounting back by LC and all functionalities of BD and LC should be available

1 mark

74 Provide facility to capture the discrepancies in the shipping document received

1 mark

Realisation of discounted bills75 To provide for register with the following details 1 mark76 Date of realization 1 mark77 Name of party / Account number 1 mark78 Amount of bill and amount realized 1 mark

of 274


79 Number of days 1 mark80 Rate of interest 1 mark81 Overdue interest 1 mark82 Penal Interest 1 mark83 Margin Deducted 1 mark84 Details of returned Instrument (to be debited to dishonored

bills account in case of insufficient funds in the party’s account) with reasons thereof

1 mark

85 To generate realisation register 1 mark86 To provide facility for entries to park and convert these from

parking account to respective account upon cheque realisation.

1 mark

87 Provide facility to calculate actual interest upon actual days of bill realisation, and if advance interest is more than actual interest, the excess interest should be credited back to customer account.

1 mark

Advance against Bills in Course of Collection88 Provide facility to capture following details 1 mark89 Name of the customer / party 1 mark90 Limit 1 mark91 Sanctioning authority 1 mark92 Date of sanction 1 mark93 Renewal date 1 mark94 Percentage of bills returned unpaid 1 mark95 Whether bank reimbursed immediately (yes / no) 1 mark96 To generate register with the following details 1 mark97 Date of lodgment 1 mark98 Bill No. 1 mark99 Name of the customer / drawer 1 mark100

Branch of Bank / branch / agency on whom it is drawn 1 mark

101

Amount of bill 1 mark

102


103

No. of days grace 1 mark

104

Due Date / Details of usance 1 mark

105

Our commission and collecting Bank’s charges 1 mark

106

Postage 1 mark

107


10 Whether documentary / clean bill 1 mark

of 274


8109

Details of documents enclosed like invoice, lorry / railway receipts / airway bill etc. with date / number / amount

1 mark

110

Details of usance / due date 1 mark

111

Our commission and collecting Bank’s charges if any 1 mark

112

Postage 1 mark

113


114


1 mark

115

To whom sent for collection and city 1 mark

116


117

Margin held 1 mark

118


119

Details of returned Bills / Instruments (to be debited to Past Due and Dishonored Bills Account in case of insufficient funds in the party’s account) with reasons

1 mark

120

Provide facility for generating—(a) register (b) covering schedules for dispatch along with instructions of the drawers of the bill (c) vouchers and (d) party wise ledger (e) Control vouchers

1 mark

121

Maintenance of pointed account for margin held 1 mark

122

To generate realization register 1 mark

123

To generate de-control vouchers 1 mark

124

Maintenance of list of IBA approved Transport Operators and validation thereof while allowing advance against bills in course of collection

1 mark

Supply Bills Purchased125

System to provide validation for acceptance of the bill after verifying limits sanctioned (parameterized) documentation, creation of charge over the assets of the limited company and other documents.

1 mark

126

Provide facility for creating the definition for determining the due date calculation including that for supply bills.

1 mark

127

System to provide for acceptance of the bill after Manager’s approval

1 mark

of 274


128

System to provide for register with the following details for supply bills purchased

1 mark

129


130

Our bill number 1 mark

131

Name of the Govt. Department on whom the bill is drawn 1 mark

132

Bill amount 1 mark

133

Amount credited 1 mark

134

Margin held 1 mark

135


136

Details of documents enclosed like bill of exchange for the good supplied, inspection certificate, a contract acceptance note, a receipted Challan evidencing receipt of goods by the Department concerned.

1 mark

137

Our commission / Service Tax 1 mark

138

Postage 1 mark

139

Interest charges / recovered (System to provide for debit from the date of purchase to the date of receipt of proceeds by the bank)

1 mark

140

No. of days 1 mark

141

Interest rate and Penal rate 1 mark

142

Amount realized 1 mark

143


144

Details of returned Instrument (to be debited to past due and dishonored bills account in case of insufficient funds in the part’s account) with reasons

1 mark

145

Maintenance of supply bills purchased register ledger party wise

1 mark

146

Maintenance of parking account for margin held 1 mark

147

Provide facility to link customer ID with Supply Bill account. 1 mark

Supply Bills Realisation148

To provide for register with the following details 1 mark

14 Bill number 1 mark

of 274


9150

Amount purchased / realized 1 mark

151


152

Overdue interest 1 mark

153

Amount 1 mark

154

Number of days 1 mark

155

Interest rate and Penal rate 1 mark

156

Provide facility for realisation register and vouchers along with advice for party

1 mark

157

To provide for two fields for interest calculation 1 mark

158

Upfront 1 mark

159

At the time of realization 1 mark

160

To provide for penal interest at the time of overdue bills realization

1 mark

Bank Guarantee161

Provide facility to create & issue Bank Guarantee 1 mark

162

Provide facility to capture following details for creating BG, but not limited to

1 mark

163

Name 1 mark

164

Address 1 mark

165

Amount 1 mark

166

Security (Cash Margin) 1 mark

167

Security Details (FD …etc.) 1 mark

168

Period 1 mark

169

Claim Period /Expiry date 1 mark

170

Commission 1 mark

171

Charges 1 mark

17 Name of payee 1 mark

of 274


2173

Provide facility to capture required documents for processing Bank Guarantee

1 mark

174

Provide Facility to create Installment schedule generation in case of Deferred Payment Guarantee (DPG)

1 mark

175

Provide facility to invoking a Bank Guarantee and to capture required reasons for invoking Bank Guarantee

1 mark

176

Provide facility to reversing Bank Guarantee and to capture required reasons for reversing Bank Guarantee

1 mark

177

Provide facility to closing Bank Guarantee and to capture required reasons for closing Bank Guarantee

1 mark

178

Provide facility to assign Bank Guarantee limit and/ or adhoc Bank Guarantee limit to the customer,

1 mark

179

Provide facility to link customer ID with Bank Guarantee account.

1 mark

180

Provide Facility for defining the guarantee number generation method. (Serial No. generation method to be defined with a parameter, whether Financial Year wise or Calendar year wise, whether the module is on line or not, for each branch.)

1 mark

181

Provide facility for configuring parameters for maintaining various types of guarantee with brief description, whether it is a Financial/ performance/ bid bond/ Deferred payment guarantee.

1 mark

182

For each type of Bank Guarantee, for given effective date, Base commission, rounding off parameter to be captured for issue of fresh Bank Guarantee amendment of existing Bank Guarantee, commission for issuing of Bank Guarantee (in % of the amount per quarter). If the Bank Guarantee is secured by our own Bank deposits then the rate of concession of normal commission in % to be captured. For refunding excess commission at the time of cancellation of Bank Guarantee no. of quarters to be reduced to be captured.

1 mark

183

Parameter of GL/Sub GL/Brk up GL for voucher generation for issuance of BG, amendment of BG, Cancellation of BG, Commission collection credit, Other charges, Service Tax (both fixed and variable charges – to be parameterized)

1 mark

184

Entry program for Issuing of BG (Bank Guarantee) which will generate the BG No., and vouchers on saving, which should be authorised separately.

1 mark

185

Provide facility to capture Counter guarantee details to be captured within the issue program of BGs.

1 mark

186

Provide facility to capture the % of lien for a BG which is backed by bank listed securities. (e. g. FD) and should allow to issue new BG against same securities ( FD )if the % line is not utilised to the full extent.

1 mark

of 274


187

Entry of amendment of BG capturing the type of amendment and reason for amendment, with voucher generation and necessary authorization program to authorize the amendment.

1 mark

188

Entry program and authorization program with voucher generation for cancellation of BGs

1 mark

189

Provide facility to link devolved BG account with regular BG account.

1 mark

190

Option for noting the receipt of invocation of a guarantee from the beneficiary of the guarantee which will be checked at the time of actual invocation of the guarantee.

1 mark

191

Entry and authorization (with voucher generation) for invocation of guarantee provision to Debit the Customer account OR designated Bills account of the customer. Necessary voucher to be generated for payment and charges collected for invocation.

1 mark

192

Report on BGs marked for revocation (letter received for invocation but pending for revocation in the system) as on a given date. Report of BGs invoked during a given period and as on a given date.

1 mark

193

Provide facility to charge interest from the date of BG invocation.

1 mark

194

Entry and authorization programs for making payment towards Deferred Payment Guarantees

1 mark

195

Report on next due dates of payment of a given DPG or all the DPGs& DPGs due already and payment is not made.

1 mark

196

Report on Commission & service tax received on various BGs and for a given BG for a period of time (date range)

1 mark

197

Bank Guarantee register printing – containing the details of the guarantee like BG No., date of issue, amount of BG, beneficiary, Date of expiry, Comm. Collected up to, Margin held (portion of cash margin and deposit margin or both)

1 mark

198

Security creation and Linking/Delinking for BGs. Entry of Creation of security, Linking (with % of linkage of the security) for a BG and De-linking of the security with authorization

1 mark

199

Commission recovery entry and cash margin reversal entry, with relevant authorization.

1 mark

200

Provide contingent/liability account creation 1 mark

201

Not allow any system entry other than bank guarantee issue entry to post entries to the contingent/liability accounts

1 mark

202

Provide printing templates for all guarantee types issued 1 mark

20 Transactions processed by centralized units to collect 1 mark

of 274


3 commissions and fees chargeable to the customer's domiciled branch

204

Provide date flexibility for bank guarantee issue entry, back value date, same date issue, future value date issue.

1 mark

205

Provide system alerts and reports on all expired bank guarantees

1 mark

206

Bank to bank guarantees to generate the relevant messages 1 mark

207

Automatic refund of cash margin 1 mark

208

Auto generation of guarantee authentic/not authentic letters 1 mark

Letter of Credit209

Provide facility to allow bank to define products for L/C (Import/ export), Bills payment and fund transfer

1 mark

210

Provide facility to capture following details for opening/ creating L/c, but not limited to,

1 mark

211

LC Opening Branch 1 mark

212

Customer Number 1 mark

213

Customer Name 1 mark

214

Method of payment 1 mark

215

Country of origin 1 mark

216

Major commodity & Sub commodity of the transaction 1 mark

217

Currency Code 1 mark

218

Amount in local currency 1 mark

219

Amount in Foreign Currency 1 mark

220

Exchange Rate 1 mark

221

Exchange Charges 1 mark

222

SWIFT Charges 1 mark

223

Method of Shipment (FOB, C&F, CIF, etc.) 1 mark

224

Expiry / Validity date (Auto) 1 mark

225

Import Purpose 1 mark

22 Interest 1 mark

of 274


6227

Commission 1 mark

228

Charges /Fee 1 mark

229

Margin paid 1 mark

230

Earmarking for margin from CC account 1 mark

231

Earmarking amount for margin from CC account 1 mark

232

Provide Flexibility for bank to define Commission/ Charges/ Interest /Fee as per Bank's requirement

1 mark

233

Provide facility to modify the already defined Commission/ Charges/ Interest /Fee at time of contract booking.

1 mark

234

Provide facility to capture LC details when LC's issued through 3rd party tie ups, but not limited to

1 mark

235

Bank details 1 mark

236

Customer Name & ID 1 mark

237

Charges 1 mark

238

Breakup of charges 1 mark

239

Contra entries should be passed upon authorisation 1 mark

240

Provide facility to modify / update LC details ( Like increase / Decrease in amount,

1 mark

241

Provide facility to invoking a LC and to capture required reasons for invoking LC

1 mark

242

Provide facility to reversing LC and to capture required reasons for reversing LC

1 mark

243

Provide facility to LC extension and to capture required reasons for extending LC

1 mark

244

Provide facility to closing LC and to capture required reasons for closing LC

1 mark

245

Provide facility to pass relevant accounting /contra entries automatically whenever LC related events/ actions triggered or happened

1 mark

246

Provide facility to auto populate the basic customer information when processing additional LC for the existing customer.

1 mark

247

Provide provision to generate all relevant SWIFT messages for Import/ Export transactions as specified by SWIFT

1 mark

248

Provide facility to retrieve LC details when LC number is entered

1 mark

of 274


249

Provide facility to validate the regulatory requirements for opening LC for the particular customer. (e.g. Foreign exchange permit validity )

1 mark

250

Provide facility to capture following details on receipt of shipping documents, but not limited to

1 mark

251

LC Number 1 mark

252

Date the document arrived 1 mark

253

Amount in foreign currency 1 mark

254

Prevailing exchange rate 1 mark

255

Nominated Bank and their reference 1 mark

256

Reimbursing Bank 1 mark

257

Number and types of documents 1 mark

258

Margin Paid 1 mark

259

Advance amount in Local currency 1 mark

260

Provide facility to Customer ID with LC account 1 mark

261

Provide facility to capture the discrepancies in the shipping document received

1 mark

262

Provide facility to generate LC letters /Documents and printing thereafter.

1 mark

263

Provide facility to link devolved LC account with regular LC account.

1 mark

264

Provide facility to capture LC confirmation details 1 mark

265

L/C Number 1 mark

266

Date of confirmation LC sent 1 mark

267

Confirming authority name 1 mark

268

L/C confirmation Date 1 mark

269

Date of confirmation received 1 mark

270

Other details 1 mark

271

Provide facility to capture following data during the LC amendment

1 mark

27 L/C Number 1 mark

of 274


8279

Reason of amendment 1 mark

280

Amendment Commission/ Charges 1 mark

281

Amendment date 1 mark

282

Provide facility to capture following data during the LC settlement

1 mark

283

L/C Number 1 mark

284

Date the document arrived 1 mark

285


286

Advance Exchange Rate 1 mark

287

Settlement date 1 mark

288

The date correspondent a/c debited or would be debited 1 mark

289

Provide facility for Advance partial settlement with proper authorisation.

1 mark

290

Provide facility to capture following data during the LC Cancellation

1 mark

291

L/C Number 1 mark

292

Date L/C canceled 1 mark

293


294

Full or partial cancellation 1 mark

295

Reason for cancellation 1 mark

296

Provision to open protested bills account in case of bills received under LC or invoked LC's where parties have not Provide facility for funds

1 mark

Letters of Credit297

Provide entry to collect margins both cash and deposit securing the LCs

1 mark

298


1 mark

299

Provide reports on commission and fees collected for LC issue and bill payment

1 mark

of 274


300

Provide system alerts and reports on maturity dates of bills presented

1 mark

301 Provide system alerts and reports on expiry dates of LCs

1 mark

302

Provide printing templates of forwarding schedules for both import and export LCs

1 mark

Additional requirements303

System to capture purpose of transaction field for both incoming and outgoing transfers

1 mark

304

Guarantees to fall off upon maturity 1 mark

305

System to mark central bank deals e.g. Borrowings, etcetera 1 mark

306

System to capture auto confirmation of guarantees 1 mark

307

System to have ability to allocate income e.g. Commission of Guarantees to link to Branch ledgers

1 mark

308

System to support automatic refund to customers upon maturity-without manual

1 mark

309

System to allow cross currency transactions 1 mark

310

System capability to integrate with existing Systems 1 mark

311

Intelligent Reporting tool to serve as Business Intelligence 1 mark

312

Audit Logging for all activities in the system 1 mark

313

System Change Logs 1 mark

2.2.14 Safe Custody Evaluation (8 Marks)# Evaluation Criteria Marks

1 System to allow for creating of a safe custody account to be maintained.1.A safe custody account to be opened under a customer’s Client ID (say a ledger sort of) whereby records of his safe custody details will be listed. This account will in a way be linked to his main account where debits of the annual/bi-annual/monthly safe deposit fees will be debited. This account will also be able to support the bank in managing the clients safe custody movement so that in a 360 degrees view, we can automatically see how many times the client has accessed his deposit and the charges (automated) thereof

1 mark

2 The fees can be broken down into monthly/quarterly/bi-annual/annual fees subscription. This will assist in

1 mark

of 274


tracking of movement and revenue arising from the product.

3 A report showing branch wise safe custody accounts to be maintained/ available (active/ closed)

1 mark

4 The auto generated Reference Number of the Safe custody to run until the items are discharged from safe custody. If the client wishes to return items after, then a new Reference number should be generated.

1 mark

5 An alert should be sent to the customer if say his monthly subscription is about to end so that he can renew the subscription or withdraw. This will ensure we do not have items overstaying in safe custody. Furthermore, this will assist whereby the customers main accounts have gone dormant.

1 mark

6 Customer information to Include a Next of kin who can access the safe custody in case of their demise or unfortunate incident, Details to include the relationship to the client and their phone numbers.

1 mark

7 The system should be able to provide automated teller receipts where customers can sign upon access of their items(the customer will not need to write letters anymore on their intent to access the items).In case of a withdrawal, a receipt can also be generated for the client to sign. When signing up for safe custody, we can have a general information sheet for the customer to fill for hard copy back up and the information to supplement what we have in the system. This to be the only manual file the bank will hold on safe custody.

1 mark

8 An auto generated receipt should be provided once the client has signed off for safe custody.

1 mark

2.2.15 Corporate Banking Evaluation (19 Marks)# Evaluation Criteria Marks1 System to provide wholesale reports specific to each

RO/RM in term of portfolio owned, income generated, liabilities, account performance in terms of PAR and NPL

1 mark

2 Ability of each RM/RO to generate own reports. 1 mark3 Ability to generate Total Income earned per customer,

account turnovers, liabilities paid to the customer for specific requested periods

1 mark

4 Ability to give reports of total facilities per customer from various branches whether personal accounts, partnerships or Limited liability accounts singly or jointly with other parties.

1 mark

5 Generate reports of securities held in customer's account, last valuation date and value.

1 mark

6 Ability to link related accounts and to generate a 1 mark

of 274


summary report of outstanding balances in group accounts

7 Ability to capture approved limits for non-funded facilities, utilization and available room

1 mark

8 The customer ID to show at a glance; total of approved facilities, limits and outstanding balances

1 mark

9 Customer's account to capture physical addresses, emails, ID Nos, Registration Nos as well as phone numbers

1 mark

10 Allow auto-generation of a unique account number for each and every deposit account fixed deposits/call deposits as per bank specification.

1 mark


1 mark

12 System to be capable of generating deposit receipts automatically upon creating any deposit.

1 mark

13 Ability of each RM/RO to generate own deposit report as well as the FD corporate report indicating names of the client, start date for the deposit, closing date and interest rate and if the deposit is under lien or not.

1 mark

14 System to allow amendment of details at the stage of inputting deposits in the system before authorization stage is complete.

1 mark

15 System to allow generation of the deposit maturities for any specific month as per the requirements of the users.

1 mark

16 System to allow generation of reports for deposits lifted, newly placed, uplifts for any specific month or any period as per the requirement of the user.

1 mark

17 System to support payment of interest at intervals e.g. Quarterly while the fixed deposit is still running even if for a year or not.

1 mark


1 mark


1 mark

2.2.16 Other Requirements Evaluation (10Marks)# Evaluation Criteria Marks

1 Scalable system to accommodate all kinds of products 1 mark

2 System be able to measure product profitability 1 mark

3 System integration; System to easily integrate with other systems i.e. CRM and update customer information for ease of access.

1 mark

4 Transaction alerts; System to give alerts on Debits & 1 mark

of 274


Credits, Overdrawn accounts, Inactive accounts, Dormancy alerts, Unclaimed assets.

5 Reports and Authentications; System to generate reports which can be used as authentic copies. For instance, Bid bond confirmation

1 mark

6 Customer information in one click; with a click we should be able to view crucial customer information, i.e. Personal identity, contacts, accounts, loan accounts details and any relevant information on one page/screen.

1 mark

7. Presence of a local support office 1 mark

8. Valid Tax Compliance Certificate` 1 mark

9. Valid Kenya Business Permit 1 mark10. Local Billing option 1 mark

2.2.17 System Demonstration Evaluation (10Marks)As part of the technical evaluation bidders will be invited for demonstration to show case their proposed offering. It is expected that Core Banking Solution will be able to integrate with the existing channels system and the other existing systems seamlessly all of which run on Oracle and SQL Databases. The demo will be expected to be brief and to highlight unique features of the system and will be at the bidder’s cost. The bidder must consider their own connectivity arrangements if the demonstration is to be onsite. The total duration for the demonstration is a maximum of 2 hours and must be restricted to the unique features of the solution being offered. The total weighted score for the demonstration will be 10%.

2.3 Overall Technical Evaluation Overall Technical Score will be awarded from the Technical Desktop Evaluation and the demonstration evaluation.

2.3.1 Summary of Technical Evaluation Evaluation Subsection Maximum Score Actual Score

1 General Requirements 192. Technical & Functional

Requirements134

3. Other Technical Requirements 1234. Reporting Requirements 565. Training Requirements 66. System Support Requirements 97. Documentation Requirements 208. Loan Origination Requirements 819. Loan Management Requirements 27110.

Debt Management Requirements 211

11.

Risk Management & Compliance Requirements

25

1 Treasury Requirements 168

of 274


2.13.

General Ledger Requirements 85

14.

Customer Management Requirements

130

15.

Deposits & Accounts Requirements 172

16.

Clearing & Settlement Requirements 300

17.

Teller Operations Requirements 65

18.

Trade Finance Requirements 306

19.

Safe Custody Requirements 8

20.

Corporate Banking Requirements 19

21.

Other Requirements Evaluation 10

Totals 2218

2.4 Financial Evaluation (30 Marks)Financial bids shall be evaluated based on the total financial bids submitted. Financial bids shall be submitted in USD valueSf = 100 X FM/F where Sf is the financial score; Fm is the lowest priced financial proposal F is the price of the proposal under consideration.

2.5 Evaluation Method A bidder must obtain at least 70% (1,553 out if the possible 2,218) on the technical score to proceed to the next stage which is the demonstration and the opening of the financial proposal. The firm achieving the highest combined technical and financial score and whose references (site visits and presentations/demos) satisfy Consolidated Bank of Kenya Ltd will be invited for negotiations.

Weights of the Technical and Financial Evaluations Technical evaluation = 60%

Demonstration Evaluation = 10% Financial bid = 30% Final score for Evaluation of bids shall be calculated as under:

Final Score = (0.6 x Technical Score) + (0.3 x Financial Score) + Demonstration Score Where: -

of 274


Final Score = Overall evaluated marks (score) of Bidder under consideration Technical Score = Technical marks (score) for the Bidder under consideration Financial Score = Normalized financial marks (score) of the Bidder under consideration

Demonstration Score = The total score attained by vendor on demonstration of the system

2.6 Response Format

2.6.1 Technical Proposal Bidders are advised to ensure that all the requirements of the Technical evaluation criteria are addressed Bidders should use the Standard Forms and Templates to respond to the relevant categories.

of 274


2.6 2 Financial ProposalBreakdown of Costs Itemized costs of each service to be provided by the vendor for the entire fulfillment of the project and summary provided as per price schedule of goods.The bidder should ensure that as part of their technical proposal, they have identified the recommended hardware and software components for their solution if any.Itemized costs of each product/module as well as services to be delivered should be provided as follows:

SN ITEM COST IN USD

1. Core Banking System License Fee(All Software Initial Costs of the Core Banking System)

2. Implementation Fee3. Integration to 3rd Party Systems

(The cost to integrate to all the existing systems)4. Training Cost (inclusive of all incidental logistical

costs) Local training Overseas/remote training

5. Data Conversion Costs6. Annual License Fee (If Applicable)7. Additional User License Fee8. Additional Branches License Fees9. Database Costs10. Annual Maintenance Costs after warranty period

(5 Yearly fixed Amount)TotalVATGrand Total

NB: 1. Vendors to Include the payment plan options available if any.2. Vendors are expected to indicate the warranty period which

should be at least one year.3. Vendors are expected to indicate a fixed 5-year Annual

Maintenance Cost. Which will commence after expiry of the warranty period.

4. Vendors are expected to indicate the escalation rate which is expected to kick in after the 5 year fixed period.

5. The initial core banking license fees should be for a minimum of 250 Users and a minimum of 20 branches.

of 274

TECHNICAL SPECIFICATIONS · Web viewThe vendor will provide all relevant information (design,...

Documents

Transcript of TECHNICAL SPECIFICATIONS · Web viewThe vendor will provide all relevant information (design,...