Scoring Sheet - Allahabad Bank

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04









Functional RFP - Scoring Sheet

Instructions of Filling up of Annexure 8 Functional RFP - Addendum to Form 10

1 "Sr. No." - Serial Number of the Requirement Provided by the bank. The vendor must not change

any information in this column



2 "Particulars" - The detailed Requirement. The vendor must not change any information in this

column.



3 "BR" - Banks Ratings – The bank has classified each of the requirements as follows:

Ratings Classification Description

1 Required The requirement is necessary for efficient functioning

2 Most Critical The requirement must be satisfied in its entirety

The vendor must not change any information in this column.



4 "VS" - Vendor Scores – The vendor would be required to provide an appropriate score to each

requirement requested for as per the following Table

VS Description

0 Can be customised by the time 50 branches implemented on CBS

1 Can be customised by the end of Pilot Phase

2 Can be customised before first branch goes live

3 Can be customised before beginning of UAT

4 Is available as a work around

5 Is available as requested



3 "TL" - Team Leader - For all the requirements where the vendor provides a score of "0", "1",

"2" "3"or "4", the vendor also needs to provide the expected number of days required for

customization required in terms of Man Days of Team Leader.



4 "TM" - Team Member - For all the requirements where the vendor provides a score of "0", "1",

"2" , "3" or "4", the vendor also needs to provide the expected number of days required for

customization required in terms of Man Days of Team Member.



5 "VC" - Vendor Comments - The vendor is free to provide any Comments he wishes.

Notes



1 The vendor is expected to include the customisation effort required to provide the above

functionality in the price quoted, therefore the cost should include all the requirements where the

score provided is from 0 to 4.









Form 8

Scoring Sheet Page 1

2 For all the requirements where the vendor provides a score of '0' the actual effort required to

provide the said requirement must be provided in man days (Team leader and Team Member) and

approximate date when the same would be made available



3 For all the requirements where the vendor provides a score of '1', '2' '3' or '4' the actual effort required to

provide the said requirement must be provided in man days (Team Leader and Team Member).



4 Where the vendor proposes to provide an interface to the existing software of the bank for a

"Requirement" requested for the vendor must provide a score of "0".



5 In case the vendor fails to provide a "Vendor Score" against any of the "Bank Ratings" the

response would be considered as incomplete and the bank will consider a score of "5".



6 The vendor is expected to provide the response by filling up the columns "Vendor Score" and "Vendor

Comments" only. The vendor is advised not to make any changes to any information on the RFP documents

for example insert a row or delete a row or modify any other information like change bank ratings, change

the functionality required, etc. In case the vendor modifies any information in the RFP the response would

not be considered.



7 Every requirement where the bank has provided a "Bank Rating" needs to be treated as an

individual requirement and should not be clubbed with any other requirement and the vendor

needs to provide a "Vendor Score" for that individual requirement, in case the vendor clubs the

requirements the response would be treated as incorrect and would be assigned a "5". For Example





8.1 Sr. No. Particulars BR VS TM TL Vendor Comments

1.2 Customer Information File (CIF)

1.2.1 Individual Customer

1.2.1.1 Title (Mr. / Ms) 3 2 5 25 We are in the processes of customizing the

software for providing this requirement

1.2.1.2 First name 3 5 0 0 When 1.2.1.1 is provided this requirement

would be made available

1.2.1.3 Middle Name 3 5 0 0 When 1.2.1.1 is provided this requirement

would be made available

1.2.1.4 Surname 3 5 0 0 When 1.2.1.1 is provided this requirement

would be made available

1.2.1.5 Other name 3 5 0 0 When 1.2.1.1 is provided this requirement

would be made available



In case the vendor provides the above response it would be treated as incorrect and would be rejected.

In case of the above example the correct response is given below:

Sr. No. Particulars BR VS TM TL Vendor Comments

1.2 Customer Information File (CIF)









Form 8

Scoring Sheet Page 2

1.2.1 Individual Customer

1.2.1.1 Title (Mr. / Ms) 3 2 1 5 We are in the processes of customizing the

software for providing this requirement

1.2.1.2 First name 3 2 1 5 We are in the processes of customizing the

software for providing this requirement

1.2.1.3 Middle Name 3 2 1 5 We are in the processes of customizing the

software for providing this requirement

1.2.1.4 Surname 3 2 1 5 We are in the processes of customizing the

software for providing this requirement

1.2.1.5 Other name 3 2 1 5 We are in the processes of customizing the

software for providing this requirement



9 Some Other Examples of Incorrect Responses

9.1 Sr. No. Particulars BR VS TM TL Vendor Comments

1.2 Customer Information File (CIF) 5 0 0

1.2.1 Individual Customer

1.2.1.1 Title (Mr. / Ms) 3

1.2.1.2 First name 3

The above response is incorrect, the currect response for the same is given below

Sr. No. Particulars BR VS TM TL Vendor Comments

1.2 Customer Information File (CIF)

1.2.1 Individual Customer

1.2.1.1 Title (Mr. / Ms) 3 5 0 0

1.2.1.2 First name 3 5 0 0



9.2 Sr. No. Particulars BR VS TM TL Vendor Comments

1.2 The software should be able to support generation of 3 5 0 0 We would build an interface to your existing

swift message software that generates swift messages



The above response is incorrect, the currect response for the same is given below

Sr. No. Particulars BR VS TM TL Vendor Comments

1.2 The software should be able to support generation of 3 0 6 40 We would build an interface to your existing

swift message software that generates swift messages









Form 8

Scoring Sheet Page 3

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No Particulars BR VS TL TM Vendor

Comments

1 Generic Features

1.1 System should have single sign-on access 2

across application

1.2 System should have user acess level for data 2

entry, authorisation and viewing

1.3 System should have Online Help at any point 2

of time

1.4 System should have the system to handle an 2

unlimited number of reporting levels.

1.5 System should support Flexibilty to change the 2

hierarchy of departments and branches?

1.6 The system should provide for Quick data 2

entry screens (user friendly) to facilitate the

data entry operator to add data quickly

1.7 System should allow for additionally attaching 2

documents to the employee record including

word files, excel spreadsheets, pictures, etc

1.8 System should store history data kept on 2

employees without limitation?

1.9 System should support Multiple Location 2

(Offices / Branches)

1.10 System should support Multiple Modules like 2

PF, Pension,Payroll etc. detailed in functional

requirements.

1.11 System should support Multiple Indian 2

languages (Preference for Hindi)

1.12 System should have dual authorization and 2

maker checker facility required for all

transactions like Payroll, Leave etc.,

depending on : Nature of Operation

(transaction entry, change, deletion, blocking,

batch update, end-of-day processing, etc.)

1.13 System should have blocking of access to 2

users in case of more than pre-defined

unsuccessful attempts to log in

1.14 System should defining rounding off rules for 2

specific transactions (e.g.Pension payment,

interest etc.)

1.15 System should allow generation of a unique 2

reference number for each transaction

1.16 System should provide Log/Record of 2

transactions

1.17 System should have on-line validation of all 2

fields such as employee codes, classification

codes, transaction types, etc. in any

transaction/master and the on-line display of

description of code fields for visual verification



Form 8

HRMS Page 4 of 238

1.18 System should maintain calendar definition for 2

each location/branch within our Bank,

capturing Weekly holidays, Public Holidays,

Unscheduled Holidays

2 General Requirements with respect to HR

solutions

2.1 System should support the following in batch 2

2.1.1 Multiple debits single credits

2.1.2 Multiple credits single debits

2.1.3 Multiple debits and multiple credits

2.2 System should have separate offline module 2

for those users which may work offline due to

no network connectivity. In case of such

offline users, support to export/import data to

the central server

2.3 System should have in-build scanner, mail and 2

fax interfaces

2.4 System should store all the reports/datas in 2

XML, XLS, HTML and DBF formats

3 DETAILED FUNCTIONAL REQUIREMENTS

EMPLOYEE INFORMATION MASTER



3.1 System should record basic Master Data for 2

an Employee for following areas along with all

related and incidental information contains

atleast the following:

3.1.1 PF Number (For new employees who are on

probation should be provided with a temporary

number which can be shifted later to a

permanent PF Number)

3.1.2 Name

3.1.3 Father’s Name & Mother's Name

3.1.4 Husband / Wife’s name

3.1.5 Permanent Address

3.1.6 Address for Communication

3.1.7 Phone Numbers / Contact Information

3.1.8 Home Town

3.1.9 Home State

3.1.10 Domicile State

3.1.11 Sex

3.1.12 Marital Status

3.1.13 Position regarding CAIIB

3.1.14 Religion

3.1.15 Category (SC/ST/OBC/MINORITY/GENERAL)

3.1.16 Date of birth

3.1.17 Date of joining, probation period, date of

confirmation

3.1.18 Scanning and storing of Employee photo,

Signature with signature no.

3.1.19 Passport No.

3.1.20 PAN Number



Form 8

HRMS Page 5 of 238

3.1.21 Bank Account No.

3.1.22 Bank Branch Name and code

3.1.23 Blood group

3.1.24 Education Qualifications – should capture the

details of name of the examination passed,

university/Institute, month & year of passing,

percentage of marks obtained, grade/class

obtained

3.1.25 Present posting,

3.1.26 Present Job code/designation,

3.1.27 Present Grade/cadre,

3.1.28 Deputation, temporary transfers

3.1.29 Date of Increment

3.1.30 Date of joining in the present place of posting

3.1.31 Cadre ( OL,IT,LAW,MKTG etc.)

3.1.32 Date of Retirement

3.1.33 Major health problems with provision to

capture the details of sickness etc.,

3.1.34 Insurance details

3.1.35 Club memberships

3.1.36 Details of submission of Assets & Liabilities

statement

3.1.37 Name and address of referee

3.1.38 Previous employment details, Name of

Organization, position held, Duration in Years

& months

3.1.39 Details promotion – clerical to officer and scale

(cadre) wise thereafter

3.1.40 Professional Qualification

3.1.41 Languages known, with details of speak, read

and write separately

4 Additional informaton related to Employee

Master (Variable In nature and Multiple

Records)









4.1 System should record details of spouse – 2

name, name of the organization the spouse is

working with, type of organization (state

government, central government, public

sector, private sector, local body, own) and is

the spouse liable for transfer or not

4.2 System should record details of the 2

dependents including relationship, their date of

birth, studying in school/college, monthly

income/pension amount

4.3 System should record details of relatives in the 2

service of ALLAHABAD BANK including

name, Employee Code., branch/office where

working, designation and relationship



Form 8

HRMS Page 6 of 238

4.4 System should record previous posting details 2

in Allahabad Bank

4.5 System should record Date of 2

termination/restoration

4.6 System should record Union Information (if 2

applicable)

4.7 System should record History of trainings 2

attended like name of the course, name of the

STC/Institution, month & year of training,

duration of the course in days/weeks

4.8 System should record Awards received by the 2

employee including the name of the award,

year of award, in which discipline/filed and

date of receipt of award

4.9 System should record History of disciplinary 2

actions against the employee including date of

charge, nature of charge, amount of financial

loss to Bank, date of punishment and nature of

punishment

5 Payroll

5.1 System should be able to define multiple pay 2

structures

5.2 System should be able to define earning, 2

deduction, contribution and provision heads for

each pay structure

5.3 System should be support Multi-currency, 2

multi-language, Unicode supported

5.4 System should run multiple payrolls in a single 2

instance

5.5 System should maintain a single central 2

payroll depository and be Should run and

access payroll from any location in a

centralized or decentralized manner

5.6 System should define various pay elements 2

like earnings and deductions using a rules

based framework

5.7 System should group individual earning and 2

deductions and link them to employees as per

their eligibilities

5.8 System should run separate payrolls for 2

Officers and Staff depending on the eligibilities

and rules applicable for each category.



5.9 System should be able to define various 2

formulae and Should link them to other

calculation formula / elements such that when

there is a rule change only the component

5.10 Should compute the dearness allowance (DA) 2

using options such as Fixed DA, linkage to

consumer price index (CPI).





Form 8

HRMS Page 7 of 238

5.11 System should perform tax computation and it 2

should be handled as per Income Tax Act

without any need for repeated manual

calculations. The tax slabs, rates and

surcharges should be maintained by the

system and the tax should be computed

automatically

5.12 Should handle unlimited number of allowances 2

, deductions. Should be Should configure

characteristics for payment, taxability,

computation and so on to suit Banks

requirements

5.13 Should compute various benefits provided to 2

our employees such as Leave Travel

Allowance, Medical Reimbursement, Medical

Insurance, Furniture, House Rent Allowance,

Company Cars, Company Housing and other

long term reimbursements. Eligibility,

computation and taxability should be

considered

5.14 System should compute the Provident 2

Fund,Contributions, Labour Welfare Fund and

Professional Tax for all states where

applicable at the correct frequency

5.15 System should calculate Gratuity and 2

superannuation for multiple trusts and user

definable contributions.

5.16 System should give Statutory reports relating 2

to PF, Pension, Income Tax, Profession Tax

whether they are monthly, half yearly or annual

should be available.

5.17 System should capture/access all types of 2

loan details of an employee and the

outstanding balance overdue if any through

link with CBS system

5.18 System should be able to file E -TDS returns 2

through nominated agencies by enabling the

bank to compile the data at Branch/Office level

and transmission of data to RO in prescribed

format, consolidation of all records at RO and

filing the same through nominated agencies to

NSDL. Similar facility at HO also for HO TDS

records.

5.19 System should support passing of accounting 2

entries for salary payments and maintenance

of related books of accounts, registers.

Generation of month wise, quarterly wise, half-

yearly and yearly statements of accounts.

5.20 System should provide an impact analysis 2

tool for analysis of impact of salary revision







Form 8

HRMS Page 8 of 238

5.21 System should support payment of salary to 2

special appointees, temporary staff etc.

5.22 System should provide link with CBS system 2

to effect the credit of salary, loan installments

to their corresponding accounts directly

5.23 System should support Main, supplementary 2

and partial payroll run

5.24 System should support location based payroll 2

run

5.25 System should perform Pay slip number 2

generation based on user defined logic such

as category and pay mode

5.26 System should support to view pay details of 2

current month, pay history, net amount paid,

unpaid deductions – Employee-wise and

month-wise, financial year-wise

5.27 System should allow Payment of officiating 2

allowance based on user defined criteria

5.28 System should capture details of different 2

perks paid to the employees/executives. Perks

register and generation of perks statement for

ITO

5.29 System should support payment of 2

subsistence allowance in case of suspended

employees and facility for rephrasing various

staff loans when on loss of pay and

suspension

6 Deduction of Income tax, Professional

tax, etc.

6.1 System should calculate Income tax, 2

Professional tax etc in all modules which have

incidents of such taxes i.e Payroll, pension

etc. The system has to adequately support all

requirements of statutory tax deduction.

6.2 System should be configuring various tax 2

rules (e.g. Income tax, Professional taxes

etc.) announced by Govt. for time to time.

6.3 System should calculate and deduct Income 2

tax, Professional tax etc., at the time of:

System and Payment

6.4 Accrual should support for all statutory 2

reports/tax returns, based on, but not limited to

Classification of Taxes, Accounting entity,

location/branch, state and nature of

transaction (User modifiable format)

7 Leave Management

7.1 System should maintain all types of leave like 2

CL, PL, ML, SL extra-ordinary leave,

sabbatical leave, special leave, etc. for each

employee







Form 8

HRMS Page 9 of 238

7.2 System should maintain leave rules for 2

availing leave, encashing leaving, accrual of

leaves, lapsing of leaves, ceilings for

accumulation of leaves, rules for combination

of leave types, etc. for each categories of

employees

7.3 System should record leaves availed and 2

balance leave calculation at any point of time

7.4 System should link Leave record to payroll 2

and employee history

7.5 System should have leave cancellation,leave 2

extension/ amendments advancement and

postponement of leave

7.6 System should have fucntion of transfer 2

people from one leave structure to another

leave structure with balance of leave in

previous structure (on promotion from clerk to

officer)

7.7 System should support comprehensive leave 2

approval rules for

Barred combination of leave

Leave pre-fixing and suffixing with other leaves

Leave pre-fixing and suffixing with weekly-off

and paid holidays

Minimum and maximum no of days at a

stretch in a specific type of leave

7.8 System should process leave encashment 2

7.9 System should mainten Leave encashment 2

record

7.10 System should interface between attendance 2

captured with that of leave record

8 Training – Identification, Nomination and

Completion of training

8.1 System should maintain a single history of all 2

the training programs taken by the user

whether they are class room training or self

study through E - Learning

8.2 System should support for nominating 2

officers/award staff for various trainings given

by Banks own training college/centres, Outside

institutes with in the country and also abroad

based on skill requirement

8.3 System should compile nominations from 2

various Regional Offices for a particular

training program

8.4 System should capture the course content of 2

each training course along with the details of

the target group etc.









Form 8

HRMS Page 10 of 238

8.5 System should capture details of courses held 2

at different centers, batch-size, faculty and

participant details, participant attendance,

feedback and evaluation

8.6 System should capture and maintain history 2

data of external instructors

8.7 System should maintain minimum and 2

maximum number of candidates per course.

8.8 System should Automate the workflow of 2

training requisitions, approvals

9 Promotions / Career and Succession

Planning

9.1 Should create standard career paths in the 2

organization in terms of various possible

moves from the current level / grade in the

organization

9.2 Should define grade advancements within a 2

level on the basis of time based as well as

merit based criteria

9.3 Should define the rules for promotion eligibility 2

in terms of tenure, consistent achievement of

high performance grades, etc.

9.4 Should define additional rules specific to 2

service in terms of suspensions, disciplinary

actions.

9.5 System should administer written tests, 2

interviews, etc for the employees identified as

a part of the eligibility list

9.6 System should intimate employees of 2

promotion / rejection through mail / workflow /

letters

9.7 System should support full promotion 2

processes from sub-staff to clerical, clerical to

officer and from one scale to another amongst

officer/executive cadres (Provide for various

categories through parameterization among

Sub staff. So that promotions within Sub Staff

category can be effected)

9.8 System should support preparation of lists of 2

eligible candidates based on user-defined

criteria

9.9 System should support inviting applications 2

from eligible candidates and evaluate the

details

9.10 System should support preparation of lists for 2

Normal Track, Fast Track and issue of call

letters for interview/written test in specified

formats

9.11 System should capture marks for written test 2

and generate merit lists





Form 8

HRMS Page 11 of 238

9.12 System should capture interview performance 2

and generate list of candidates selected for

promotion based on the user-defined criteria

and category-wise (like general, SC/ST, OBC

etc.)

9.13 System should support obtaining clearance 2

from departments like audit, vigilance etc.

9.14 System should support preparation of seniority 2

list/ merit list / waiting list / empanelled list etc.

9.15 System should support advising salary fitment 2

on promotion. The fitment made should

automatically go to payroll module

9.16 System should have functionality of Issuance 2

of Posting orders on promotion and updating

promotion/posting details of employees

9.17 System should store all the informaton related 2

to promotion refusal/reversion and thereto

issue necessary letters to candidates who

refused promotion indicating the

consequances like barring to participate in

next process etc

9.18 System should maintain and track retirements, 2

resignations, other vacancy positions

10 Performance Appraisal Management

10.1 System should support performance 2

management tools, tracking & reporting.

10.2 System should record competencies and 2

proficiency required for each job matching with

the available competencies of employees. The

system should make competency assessment

on pre-designed metrics and should facilitate

in all employee development initiatives like

recruitment, training, succession planning,

appraisals etc

10.3 System should provide managers the 2

document performance objectives, goals and

development plans of potential appraisals

10.4 System should have functionality to compare 2

appraisee and appraiser ratings online?

10.5 System should support online secure access 2

to both staff as well as the officers to complete

performance appraisals?

10.6 System should be able to attach documents 2

regarding branch performance etc with the

appraisal template by accessing appropriate

database

10.7 System should support supervising official to 2

appraise the competencies of the subordinate

10.8 System should create Performance 2

documents for employees depending on the

cadre / grade in the organisation



Form 8

HRMS Page 12 of 238

10.9 System should be able to record superior’s 2

appraisal and approval for the appraisal

10.10 System should give weightage to each key 2

parameter and points against each rating

attained

10.11 System should support maintenance of history 2

of performance appraisals and promotions

10.12 System should have facility to release of

increments for qualifications acquired and also

for stagnation increments,FPA,PQA etc and it

should be integrated with the payroll module

and other relevent modules

10.13 System should have facility to support 2

generation of increments due for each month

or for user defined period for employees –

cadre wise/scale wise/ other user defined

combination

10.14 System should support for generation of 2

reminder letters / mails / workflows to the

employees/ appraising authorities in case of

non-submission of self-appraisals, etc.

10.15 System should support memo letters / mails / 2

workflows to be issued to the employee in

case of unsatisfactory performance

10.16 System should capture the details of assets & 2

liabilities as furnished by the officers at the end

of every year

10.17 System should support maintenance of history 2

of assets & liabilities details furnished by

officers

10.18 System should support to generate list of 2

officers defaulted from submitting the Assets

and Liability Statement and provision to

generate reminder letters to the officers

11 Management of Transfers & Postings

11.1 System should have automation of transfer 2

process and related workflow with facility to

configure rules

11.2 System should have facility for 2

Transfer/redeployment of officers based on

requirement/sanction strength of different

regions/zones

11.3 System should generate various reports based 2

on employee master data for transfer like user

defined critria, request transfer list, completed

3 years, transfer on promotion etc. ( As per the

bank's policy )

12 Management of LFC, Medical aid,

scholarships, etc.









Form 8

HRMS Page 13 of 238

12.1 System should Capture the employee-wise 2

LFC eligibility details like present LFC block,

when last LFC was availed etc with related

report as per Bank requirement.

12.2 System should maintain suspense account 2

registers for advances granted to employees

and bill processing & followup

12.3 System should maintain of employee-wise 2

medical aid details and giving automatic credit

of medical aid at the beginning of the year as

per the employee eligibility

12.4 System should accept the application for 2

Medical aid and processing the same

12.5 System should maintain hospital 2

reimbursement rates as per the Bank rules

(self and dependant eligibilities separately)

12.6 System should maintain list of hospitals having 2

tie-up facility with the Bank – with tie-up

details, payments made etc.

12.7 System should generate letters of admission 2

to hospitals and executive health checkup

letter

12.8 System should process the final hospitalization 2

bill and calculation of eligible amount as per

the eligibility (for self and dependant

separately)

13 Payment of Scholarships

13.1 System should capture details of various 2

scholarship schemes of the Bank

13.2 System should accept and process 2

applications for grant of scholarships.

Accepted & rejected application details and

related reports.

13.3 System should maintain record of scholarship 2

granted

14 PF & Terminal Benefit Management

14.1 System should support pooling the monthly 2

contribution of PF,VPF in to the PF

management system

14.2 System should Support PF settlement process 2

including generation of settlement sheets and

relevant vouchers for accounting

14.3 System should support calculation of periodic 2

interest and crediting the amount to the

accounts

14.4 System should perform PF application 2

processing, loan sanctioning, loan

disbursement, modification of loan

installments, loan short closure, recovery

through payroll, final settlement during

closing/transfer for different type of pf loan



Form 8

HRMS Page 14 of 238

14.5 System should have facility to Credit 2

sanctioned PF loan / withdrawal amount

directly to their respective accounts through

CBS System

14.6 System should Generate Form 15 AA for the 2

terminal benefits like PF/Gratuity/Pension

14.7 System should Generate all types of MIS 2

reports as per request of Bank (like pf ledger,

pf loan ledger etc.)

14.8 System should maintain nominee details and 2

payment to nominee in case of death of an

employee

15 Pension Management

15.1 System should have multiple pension 2

schemes so that Allahabad Bank's Pension

scheme & Industry Pension scheme available

in banking sector can be incorporated.

15.2 System should intimate the employees three 2

months before their retirement about their PF

subscription, PF Loan, Gratuity and Pension

claim forms etc.

15.3 System should support pension processing for 2

pensioners

15.4 System should maintain nominee details to 2

facilitate pension processing

15.5 System should support pension disbursement 2

and support multiple payment modes for

pension

15.6 System should calculate family pension and 2

payment

15.7 System should support all related accounting 2

procedures including generation of vouchers

and related reports

15.8 System should perform Income tax calculation 2

and deduction for pension payment as per

govt. guidelines and issuance of form 16

15.9 System should have function of Credit Pension 2

amount directly to their respective accounts

through CBS System. If a non CBC Br. or

other bank branch, advice/ DD Should be

prepared.

16 Gratuity Management

16.1 System should perform gratuity calculation, 2

provision & accounting employeewise

16.2 System should perform forfeiture of Gratuity in 2

case of dismissals etc.

16.3 System should generate gratuity payment 2

cheques

16.4 System should maintain nominee details and 2

payment to nominee in case of death of an

employee



Form 8

HRMS Page 15 of 238

16.5 System should generate all types of 2

reports/registers related to Gratuity

management

17 Manpower Planning

17.1 System should have function to define 2

requirement plans (periodic) in terms of

specific skills, Qualifications, experience,

designation, etc.

17.2 Facility to support to analyze the cadre-wise / 2

branch or office-wise / department –wise staff

strength – sanctioned/working strength and

the gap for which recruitment is required

17.3 System should capture the data relating to 2

resignations / retirements/ VRS/

Terminations/dismissals etc.

17.4 System should create a standard recruitment 2

template and host it on the Bank site for

receipt of web based applications

17.5 System should have function of attaching 2

documents / credentials in soft form as a part

of the application

17.6 System should capture detailed information of 2

applicant/candidate

17.7 System should be capable to define the 2

specifications of the vacancy in terms of

qualifications, work experience, location

considerations, skills/competencies required,

additional certifications / professional

qualifications etc.

17.8 System should facilitiate the bank to go for E - 2

Recruitment of all category of staff through an

appropriate module to be provided by the

vendor for the said purpose

17.9 System should support automation of 2

manpower requirement planning and

recruitment process

17.10 System should perform short-listing of 2

applicants based on required user-definable

selection criteria – like different criteria for

SC/ST/OBC and general candidates

17.11 System should have function to define the 2

evaluation criteria and generation of results of

evaluation

17.12 System should generate merit list of 2

candidates

17.13 System should support for generation of call 2

letters for written test/interview and offer letter

for finally selected applicants









Form 8

HRMS Page 16 of 238

17.14 System should facilitate to send letters to 2

previous employers/references etc., asking

about the conduct and character of the

applicant

17.15 System should record the acknowledgement 2

of offer letters, medical reports, verified and

authenticated testimonials, caste certificates

and other relevant certificates as per the user

defined check list

17.16 System should handle conversion of officers 2

from mainstream to specialist cadre and vice-

versa – as per the Bank's criteria and

adjustment of such officer’s seniority

accordingly

17.17 System should support co-ordination of 2

induction training of recruited officers/award

staff

17.18 System should have fucntionality to follow up 2

with police authorities for verification of

antecedents of candidates and caste

verification report from competent authorities

17.19 System should generate report for all the 2

above functionalities with a provision for user

definable queries

18 Management of Industrial Relations

matters Disceplinary action and

procedures

18.1 System should Issue memos to delinquent 2

employees, show cause , charge sheets and

capturing response from concerned employee.



18.2 System should have Rules and Officer Service 2

Regulations

18.3 System should support for enquiry proceeding 2

and findings of enquiry officer

18.4 System should capture and communicate 2

Decisions of Disciplinary Authority

18.5 Provisions for appeal to Appellate Authority 2

18.6 Appellate authority’s decisions 2

18.7 Referring cases having vigilance angle to 2

Vigilance Department

18.8 Support provisions for opinions of CVC 2

18.9 Reference to CVC for first stage advice 2

18.10 Provision for other related processes 2

18.11 System should support for appointment of 2

Enquiry Officer from CDE

18.12 System should capture related enquiry 2

proceeding

18.13 Findings of EO from CDE 2

19 CVC Related Matters





Form 8

HRMS Page 17 of 238

19.1 System should capture reporting of frauds by 2

Branches/ROs to CVO and their registration

with Govt. authorities.

19.2 System should capture details on closure of 2

fraud cases after due processes

19.3 System should maintain data in respect of 2

disciplinary action cases of all officers/award

staff –Region wise and total

19.4 System should maintain records in respect of 2

all cases under investigation, enquiry and

noting the periodic progress made

19.5 System should issue memos etc. to the staff 2

members involved, follow-up letters to the

Region

19.6 System should capture proceeding 2

details,punishment award,appeals preferred by

the staff members and recording of the

decisions given by competent authorities

19.7 System should be recording staff grievances 2

and follow up made in this regard

19.8 System should capture information about 2

suspension cases including suspension

revocation

19.9 System should maintain registers and 2

compilation of periodic statements about

pending cases, suspension cases, cases

dismissed, punishments awarded etc.

19.10 System should maintain data of cases pending 2

in Supreme Court, High Courts, Labour

Courts, Asst. Labour Commissioners, criminal

cases, CBI cases, Police cases in respect of

employee category wise and generation of

periodic reports

20 Resources and Project Management

20.1 System should maintain resource profiles 2

available with the Bank(like specialist officers,

Forex officers, faculty, IT Officers, ZCCs etc.,

Credit officers. Law officers, Marketing

officers, Dealers in Forex/Treasury

departments employee trained for various

products and services

20.2 System should maintain details of the 2

allocation of resources at various critical

departments

20.3 System should maintain details of special 2

projects under taken by the Bank ( eg.

Insurance , sale of policies (Life and Nonlife),

Mutual Fund, Units and Pension Plans etc.)

20.4 System should maintain details of resources 2

allotted to the special projects







Form 8

HRMS Page 18 of 238

20.5 System should perform cost benefit analysis of 2

the special projects

21 Executive Information system and tools

for planning and decision making

21.1 System should provide up-to-date employee 2

information viewing at a given time. Views like

date –wise, category-wise, qualification-wise,

experience-wise, male-female etc. and export

such information to other application if

required.

21.2 System should provide user-friendly, multi- 2

dimensional analysis and decision support

tools like Data Explorer, Data Analyze, to the

executives covering functionalities across the

Bank

21.3 System should provide high flexibility in 2

designing queries and accessing the key data

by the executives

21.4 System should have fucntion to define 2

important/key parameters in the HR database

that may need close monitoring

21.5 System should provide display and print the 2

data in tabular form or text form

21.6 System should display and print the data in 2

graphical form (2D,3D,PIE,LINE graphs etc.)

22 Issue of No Objection Certificates (NOC)

22.1 System should Issue NOC for Passport,VISA, 2

higher studies and any other purpose including

NOC for re-employment of retired employees

as well as existing employees.

22.2 System should Issue of No Objection letter for 2

availing loan from other Banks, financial

institutions or other entities.

23 Staff Welfare Schemes

23.1 System should maintain various staff welfare 2

scheme like medicalim, subsidised canteen

details and generation of relevant reports

23.2 System should capture Appointment and 2

capturing the details of contractors for the

canteens, Their Bill payment & reconcilation

23.3 System should maintain details of allowances 2

paid to each employee month-wise based on

the applications received like college fee,

school fee, and head wise monthwise detail

and consise report.

23.4 System should maintain details of identify 2

cards issued and cancelled

23.5 System should capture the details, 2

achivements of sports persons employed in

the bank, their designations, scales etc.,





Form 8

HRMS Page 19 of 238

24 Management of Power of Attorney (PA)

and Signatures of Authorised officials

24.1 System should capture details of PA 2

issued/Canceled to the employees along with

the facility to scan and store and view the

signatures of the officials issued with PA –

separately for PA

24.2 System should capture details of PA of 2

employees kept under suspension

24.3 System should Maintain signature of 2

authorised officials and their circulation

24.4 System should Maintain signature of 2

officer/staff under suspension/retired and their

circulation

25 Uniform & Leveries



25.1 System should maintain details of staff 2

members eligibility for uniforms, shoes etc.

track of past record when last issued also to

be maintained

25.2 System should perform processing and 2

sanction of uniforms, shoes etc. to the eligible

candidates and prepairing branch/office wise

related report

25.3 System should record the bill particulars 2

evidencing the purchase of uniforms

26 The following should be made available

through web enabled system

26.1 Should download forms and information 2

requirements through the Web

26.2 System should enable online filling of 2

application forms like leave application

26.3 Should direct information/ application forms to 2

the relevant department

26.4 Should generate acknowledgement receipt in 2

case of transactions request. The system

should allow the Bank to customize the

acknowledgementsNumberon the following

Acknowledgement based

Transaction type (if standard)

Date and Time (IST)

Name

Employee ID

Purpose

TOTAL









Form 8

HRMS Page 20 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Funds and Investments

1.1 Collection of daily RBI

balances from the branches:

1.1.1 General Ledger balances at the

designated branches:

1.1.1.1 The system should have

Generation of Balances of GL

Heads as per the

Codes(parameter) – Branch-

wise, Zone-wise, Consolidated

summary at Central Office level

for any date. 2

1.1.1.2 System should have functionality

of viewing statement of the

balance of any GL Head of any

branch at Head Office, viz RBI

Balance. 2

1.1.2 RBI Account Reconciliation:

1.1.2.1 System should have the facility

for feeding RBI daily statement

for reconciliation of the entries in

the RBI ledger head. 2

1.1.2.2 System should have provision for

reconciliation of unmatched

entries in the RBI account and

the respective daily statement of

the RBI. 2

1.1.2.3 System should have facility of

generation of reports of

unmatched entries: 2

a. Entrywise – Date wise

b. Agewise -Amount wise

1.1.2.4 System should allow the

branches to feed the statement

details provided by DAD, RBI on

daily basis OR send a scanned

copy of Reserve Bank Statement

to Head Office immediately after

receipt. 2

1.1.2.5 System should have the

branches to advise RBI account

reconciliation process with

comments on un-responded or

outstanding entries. 2

1.1.2.6 System should have proper

tracking of RBI Cheques issued /

received. 2









Form 8

Funds Page 21 of 238

1.1.2.7 System should have connectivity

with Service Branch and RBI

account maintaining branch for

capturing all transactions in RBI

account and their reconciliation. 2

1.1.3 Preparation of daily funds

position:

1.1.3.1 System should have Automated

report of all clearing centres

regarding inward and outward

clearing position in all types of

cheque clearing. 2

1.1.3.2 System should have detailed

enquiry listing branch-wise - for

proper monitoring of funds inflow

and outflow 2

1.1.3.3 System should have Provision for

branches to report future outflows

and inflows date-wise for use of

fund managers. 2

1.1.3.4 System should ascertaining

surplus / deficit of funds in

consolidated RBI account vis-à-

vis CRR requirement. 2

1.1.4 Data related to computation of

NDTL (Weekly Abstracts) and

Preparation of Form A:

1.1.4.1 The system should allow storage,

consolidation and transmission /

retrieval of data related to trial

balances, weekly data

incorporating all assets and

liabilities at branch / office level. 2

1.1.4.2 System should have provision for

generation of reports related to

Foreign Currency accounts,

Overseas Investment, assets

with banks / others in foreign

currency and external liabilities

fully subject to CRR prescription 2

1.1.4.3 System should show Summary of

Liabilities with proper segregation

as demand and time / short term

and long term as per RBI norms

2

1.1.4.4 System should show Summary of

Capital and Reserves of the bank

with record of changes made

date-wise. 2

1.1.4.5 System should show Balances of

PF Pronote of the bank with date-

wise change details. 2







Form 8

Funds Page 22 of 238

1.1.4.6 System should show Details of

Assets and Liabilities to the

Banking System . 2

1.1.5 Data related to maintenance of

SLR requirement:

1.1.5.1 The system should extract data

showing daily balances of all

branches showing:

1.1.5.1.1 Daily Cash Balances. 2

1.1.5.1.2 Daily Balances with SBI/Other

Notified Banks and Financial

Institutions 2

1.1.5.1.3 Daily Outstanding of Approved

Investments with Accrued

Interest and Amortisation. 2

1.1.6 Submission of Form VIII and

Special Fortnightly Return to

RBI:

1.1.6.1 System should report Cash

Balances actually maintained with

RBI vis-à-vis Average

Requirement on fortnightly basis. 2

1.1.6.2 System should report Particulars

of short term commercial bills

discounted with banks / other

institutions. 2

1.1.6.3 System should report Particulars

of Inter Bank Participation (IBPs) 2

1.1.6.4 System should report Issue of

Certificates of Deposit (CDs) 2

1.1.6.5 System should report Balances

held abroad and loans in Foreign

Currency 2

1.1.6.6 System should report Bank's

Interest Rate on Domestic and

Foreign Currency Term Deposit,

effective rates for premature

withdrawals and records of date

of change regarding the same. 2

1.1.7 Other Refinanace facilities:

1.1.7.1 System should Determine

eligilbilty for NABARD/ SIDBI /

Other Refinanace 2

1.1.8 Refinance Availment – General



The system should capture data

related to refinance availment for

accounting, report generation,

audit and RBI Inspection. The

different parameters are listed

below:

1.1.8.1 Date of availing 2







Form 8

Funds Page 23 of 238

1.1.8.2 Sanctioning and Authorising

Authority 2

1.1.8.3 Persons authorised to draw the

refinance on behalf of the bank 2

1.1.8.4 Amount availed vis-à-vis

Eligibility. 2

1.1.8.5 Centre and Branch of Availment 2

1.1.8.6 Generation of availment advice

and booking of the amount at

Head Office 2

1.1.8.7 Rate of interest: normal or back

stop facility. 2

1.1.8.8 Date of repayment 2

1.1.8.9 Amount of interest paid, booking

of interest and generation of

advice. 2

1.1.8.10 Generation of reports associated

with refinance drawal. 2

1.1.9 Monitoring of submission of

Weekly Returns (for Non-CBS

branches):

1.1.9.1 System should monitor Date of

submission of weekly returns and

entry in RO / Nodal Centres. 2

1.1.9.2 System should monitor Period of

default - Region-wise break-up 2

1.1.10 Data to be processed on basis

of branch abstracts / weekly

data:

System should generate on

demand -Week-wise / Region-

wise / District-wise / State-wise /

Category-wise variations of the

following :

1.1.10.1 Position of deposit and advances

of the branches. 2

1.1.10.2 Position of cash / SBI / Other

Bank balances. 2

1.1.10.3 Position of flabby assets / other

assets. 2

1.1.10.4 Position of other liabilities. 2

1.1.10.5 Achievement of targets vis-à-vis

Business Plan 2

1.1.10.6 System should generate fresh

deposits received over a given

amount say 5.00 crore & above

with in a specified period say one

week giving the rate of interest,

tenor, maturity date etc. 2

1.1.10.7 System should generate reports

of high value deposits maturing

say next one month. 2







Form 8

Funds Page 24 of 238

1.1.10.8 Accounting of Transaction as per

bank's accounting system and

booking of interest / swap gain /

swap charges / brokerage. 2

1.1.11 Reports:

1.1.11.1 System should generate counter-

party-wise / centre-wise / broker-

wise / day-wise reports with full

details. 2

1.1.11.2 System should perform

Calculation of Average Amount

Lent / Borrowed from overseas

market and Average Gain /

Expenditure for any specified

period. 2

1.1.11.3 System should Maintain

Overseas Investment Ledger 2

1.1.11.4 System to have provision for

instructions to be generated for

compliance of the executing

branch. 2

1.1.12 Interest on CRR balances

System should generate the

following for preparation of CRR

Interest Claim at specified

interest claim at specified

intervals (at present monthly):

1.1.12.1 System should recognise

reporting fortnight dates and

acceptance of data for the

reporting dates 2

1.1.12.2 System should determine CRR

requirement of the bank based

on the following inputs: 2

1.1.12.3 DTL and NDTL on the reporting

dates (2nd previous fortnight, as

per present norms) 2

1.1.12.4 The system should prepare day-

wise CRR maintenance

statement and summary for CRR

Interest Computation as per RBI

norms. 2

1.1.13 Cash Transactions of Rs.10

lakhs and above with :

1.1.13.1 System should generate report

on cash transactions over Rs.10

lac giving details like dateof

transaction, branch name &

code, type of transaction (Dr/Cr),

type of account etc 2

1.1.14 Sources and Uses of Funds

from the general ledger:







Form 8

Funds Page 25 of 238

1.1.14.1 System should generate report

on the sources and uses of fund

required at periodic intervals

(fortnightly, monthly, quarterly)

giving the inflow of funds from

various sources and the

corresponding uses vis-à-vis the

outflow of funds for varied

obligations / reasons. 2

1.1.14.1 System should Calculate

Variance with reference to 31st

March of the previous accounting

year and also variation from last

months / last reporting fortnight

position in respect of the

following: 2

1.1.15 Issuance of e-money:

1.1.15.1 System should allow Liabilities

accepted under multipurpose

prepaid cards to be included in

demand liabilities and classified

thus for NDTL calculation, ALM

report generation and

consequent corporate analysis. 2

1.1.15.2 System should capture up to

date position of fresh liabilities (by

e-monetisation) by the bank,

compilation of monetary statistics

and regular reporting to RBI. 2

1.1.15.3 System should consider Deposits

accepted as part of e-money for

deposit insurance and cost of

issuance to be regularly

monitored considering the

insurance premium payable. 2

1.1.15.4 System should help monitoring

funds position on daily basis with

due regulation of inflow and

outflow. 2

1.1.16 Investment

1.1.16.1 The system should be able to

provide interface with the existing

system at Treasury, Mumbai,

which is e-Treasury of TCS. 2

1.1.16.2 System should provide facility at

all the branches to create RTGS

messages. 2

1.1.16.3 The system should be able to

trace inter branch movement of

securities. 2









Form 8

Funds Page 26 of 238

1.1.16.4 System should have fucntion of

Transfer of interest on securities

& dividends to the Treasury

branch , Mumbai online from the

CBS connected branches. 2

1.1.16.5 System should have feature for

maintaining CSGL accounts for

constituents. 2

1.1.16.6 System should keep track of

interest received on CSGL

holdings. 2

TOTAL 140









Form 8

Funds Page 27 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 General

1.1 System should request for authorization

by a higher authority when transaction

exceeds the specified limits 2

1.2 System should display the details of all

limits outstanding, overdues and

customer-wise utilization. 2

1.3 System should provide for recovering

processing charges as per defined

parameters. 2

1.4 System should provide for

interchangeability of limits by proper

authorization. 2

1.5 System should provide for entering

document details especially with

reference to collateral securities

recording of date of EM and registration

of charges with ROC. 2

1.6 System should generate formats for

notification to ECGC in cases of new /

modification of limits. 2

1.7 System should provide for lodgement of

ECGC claims for both pre and post

shipment credit within 30 days from

becoming past-due 2

1.8 System should generate an alert in

case of under-insurance 2

1.9 System should support revaluation of

contingent liabilities based on revised

Market/Notional rates. 2

1.10 System should provide for

parameterization of the ECGC premium

rates 2

1.11 Provision should be available in the

system for SWIFT interface and access

for all the Message Types. 2

2 Pre-shipment Finance

2.1 System should provide for releasing PC

against particular order or LC in

installments and in case the application

for PC is more than order value, the

system should generate an alert. 2

2.2 System should generate reports for

overdue PC reports customer wise and

date wise. 2

2.3 System should provide for generation of

reports based on the various due dates

of PC's released customer wise. 2









Form 8

Forex and Trade Finance Page 28 of 238

2.4 System should provide for charging of

interest on monthly basis and

automatically debit the operative

account without requiring further

authorization. 2

2.5 System should provide for incorporating

the details of restricted cover countries,

and in case any PC is to be released

against such orders, system should

permit the same only after proper

authorization. 2

2.6 System should provide alerts to the

user if any of the bill of a particular

buyer has been returned in the past/ or

over due at the time of granting PC. 2

2.7 System should provide an alert at the

time of entering a duplicate purchase

order in case of PC disbursements. 2

2.8 System should provide for releasing PC

in FC and charge interest in FC and

convert the same in INR for accounting

purpose also provide a provision to

account at notional rate. 2

2.9 System should provide for generation of

entries automatically at the time of

releasing PCFC and also to calculate

interest at LIBOR+/- BPs? 2

2.10 System should provide alerts to the

user when an export bill is sent in

collection against PC released in FC(no

ECGC cover) 2

2.11 System should provide for calculation of

amount of PC to be released based on

FOB and CIF value. 2

2.12 For combined limits say PC cum CC

cum PS, system should provide alerts

in case the balance exceeds the limits,

in INR as well as in FC. 2

2.13 System should facilitate

prepayment/repayment of PC out of the

funds held in EEFC. 2

2.14 System should provide facility to

convert rupee PC to PCFC and 2

2.15 System should support back to back LC

based on the export LCs advice by the

Bank/other banks, by apportioning the

PC sanction to the party. 2

2.16 System should support releasing of PC

as a running facility and account for the

same when export bills are tendered on

LIFO/ FIFO basis. 2

2.17 System should support calculation of

PC to be released based on FOB & CIF

value. 2









Form 8

Forex and Trade Finance Page 29 of 238

2.18 System should allow adjustment of PC

against bill drawn under same LC, only

in the case of order specific PC. 2

2.19 System should support calculation of

DP based on the lowest of order/LC

Based and physical stock based as

required by the Bank. 2

2.20 System should generate reminders to

exporters in case of OD PC. 2

2.21 System should support charging of

interest on slab rate system. 2

2.22 System should charge interest at MLR

+ 2% penal rate when PC (INR / FC) is

exhausted, not out of export proceeds 2

3 POST SHIPMENT CREDIT

3.1 The system should store buyers’ details

and should pick up the details with easy

help keys. 2

3.2 System should provide for the details of

correspondent banks to be picked up

automatically at the time of negotiation /

discount /purchase of export bills. 2

3.3 System should provide for overriding

the limits after proper authorization. 2

3.4 System should provide for charging

ECGC premium to the debit to P/L

directly without any further 2

3.5 System should provide for crediting only

the net amount after adjustment of PC. 2

3.6 System provides for generation of

vouchers for all transaction giving the

details so that the same can be the

customer copy. 2

3.7 System should provide for an alert in

case the export is being made to

restricted cover countries by ECGC. 2

3.8 System should provide for buyer wise

limit details and alert should be

provided in case the value of the bill

exceeds the buyer wise limit. 2

3.9 System should provide for calculation of

interest upto the value date and refund

in case the bill is realized earlier. 2

3.10 System should support entry of multiple

currencies within the same bill for

exports. 2

3.11 System should support extension of

due dates for export bills. 2

3.12 System should support calculation of

differential interest to be recovered in

case of extension of due dates. 2

3.13 System should support linking of

crystallized bill for calculation of ECGC

Premium under WTPSG. 2

3.14 System should support auto

crystallization/auto liquidation. 2









Form 8

Forex and Trade Finance Page 30 of 238

3.15 System should provide for calculation of

overdue interest in case the bill is not

paid on due date. 2

3.16 System should provide for calculation of

overdue commission in case of

collection bills which are outstanding

every quarter to the debit of parties

account. 2

3.17 System should provide for adjustment

of export bills proceeds to EEFC

account. 2

3.18 System should provide for change of

buyer. 2

3.19 System should provide for reduction in

invoice value and recover the

differences from the exporters. 2

3.20 System should provide for handling

third party export bills. 2

3.21 System should provide for generation of

export bills realization certificate and

transmit to DGFT in the EDI system. 2

3.22 System should provide for linkage of

PC to the export bills purchased/

negotiated / collection for order of

PC/LC 2

3.23 System should provide for apportioning

of interest for different half years. 2

3.24 System sould provide for crystallization

of bills with overriding authority and

notice to be sent to the party with

appropriate interest charges, which

should be linked to calculation of ECGC

premium on post shipment. 2

3.25 System should support revaluation of

Foreign Currency collection bills and

vouches for the difference in amount. 2

3.26 System should support release of GR in

case of advance remittances with FIRC. 2

3.27 System should accept partial remittance

and generate report accordingly – R

Return, balance outstanding in the bill

to be displayed. 2

3.28 In case of correspondent bank charges,

system should debit parties account

and adjust export bills and show the

same as a sale of FC for R return

purpose. 2

3.29 System should facilitate charging of

interest from the drawer on the export

bills to debit to their accounts. 2

3.30 System should permit extension of due

date and recover interest accordingly

depending upon the tenor. 2

3.31 System should support part

crystallization. 2









Form 8

Forex and Trade Finance Page 31 of 238

3.32 System should support slab exchange

rate system based on turnover. 2

3.33 System should allow handling bills in

currency, which bank is not handling

and such cases will the system facilitate

granting of PC / PS. 2

3.34 System should allow handling bills in

multiple currency and multiple tenor. 2

3.35 System should allow modification of

tenor subsequent to lodgment. 2

3.36 System should allow release of GR

form against Bill of entry in case of

dishonor or export bill if the goods are

re-imported 2

3.37 System should allow handling of export

bills without shipping documents. 2

3.38 System should support uniform system

of numbering of export bills branch wise

particularly when the bill shifted from

one portfolio to other. 2

3.39 System should provide a facility to

define the prescribed period for

realization of export proceeds customer

wise, country wise and commodity wise

and also restrict the facility to certain

period. 2

3.40 System should generate an

alert/warning message in the event of

export bills sent for collection against

PC released in FC.( No ECGC cover in

such cases) 2

3.41 System should keep track of agency

commission payable on export and link

it up to remittance subsequently made. 2

3.42 For EBRD, The system should calculate

the interest in FC and the convert the

same to INR for debit to the party a/c. 2

3.43 Sytem should provide vouching of

EBRD at notional rates and automatic

generation of vouchers and updation of

GL 2

3.44 System should facilitate sharing of

interest in EBRD and PCFC with CO

based on parameters. 2

3.45 System should provide for discrepancy

charges in export bills as per LC to be

recovered automatically 2

3.46 System should provide for digital

scanning documents and transmitting to

the branch for processing. 2

3.47 System should have a provision to take

the exchange margin to separate

nominal account at the time of

negotiation, which should be reversed

automatically at the time of realization

of bill 2









Form 8

Forex and Trade Finance Page 32 of 238

3.48 System should provide an alert for

obtaining credit report of new overseas

buyers in case of purchase of export

bills. 2

3.49 System should generate contra

vouchers in case of bills sent for

collection. 2

3.50 System should calculate swap charges

for bills realized before / late deliveries. 2

3.51 System should make appropriate

changes / reportings when a collection

bill is subsequently purchased /

negotiation ? 2

3.52 System should generate a unique

reference number for advance

payments received and relate them to

the bills submitted by the exporter at a

later date 2

3.53 System should support partial

discounting of bills 2

3.54 System should permit parameterization

of GR form submission based on

amount of the bill 2

3.55 System should track the nostro

statements with fuzzy logic about the

realization of export bills and inform /

alert the respective B-category

branches. 2

3.56 System should alert the state stamps

act requirement while entering usance

(number of days )of a bill 2

3.57 System should have facility to handle

third party export bills. 2

3.58 System should have a provision for

handling bills under SEZ/EPZS / 100%

EOU 2

3.59 System should have provision for

providing trade discounts. 2

3.60 System should have provision to write

off unpaid collection / purchase bills. 2

3.61 Write off of bills to track notification of

Enforcement Directorate’s Scrutiny --

and during scrutiny period the system

should not allow write-off of such bills. 2

3.62 System should provide for transfer

pricing mechanism for sharing of

interest in EBRD and PCFC with Head

Office. 2

3.63 System should generate reminders for

overdue bills to exporters as well as to

collecting banks 2

4 LC-Exports

4.1 System should provide for linkage with

export bill for LCs adviced by us. 2









Form 8

Forex and Trade Finance Page 33 of 238

4.2 System should display a list where the

LC is restricted for negotiation to a

particular branch 2

4.3 System should support multiple transfer

of export LC 2

5 Imports

5.1 System should provide for opening

different types of LCs as standby LC. 2

5.2 System should provide for mapping the

relevant details of Advising bank,

confirming bank and negotiating bank. 2

5.3 System should provide for generation of

LC reference number automatically. 2

5.4 System should provide for pre defined

LC clauses. 2

5.5 The system should also provide for

clauses specific to the customer

requirements. 2

5.6 System should generate a warning

message in case the limit is exceeded 2

5.7 The system should automatically

generate usance, commitment, and

other charges. 2

5.8 System should generate necessary

vouchers 2

5.9 System should provide for picking up

the exchange rate loaded in the system

for passing contra entries. 2

5.10 System should provide for

apportionment of charges for different

half years. 2

5.11 The system should display the margin

recovered customer wise, bill wise/

order wise 2

5.12 The system should display the LCs

getting expired say one week before the

due date. 2

5.13 System should provide facility to make

amendments , when there is

amendment to the amount the system

should alert for recovering the

additional margin and charges, also

with in limit of sanction. 2

5.14 System should generate follow up

letters, payment messages and advises 2

5.15 System should have a provision to

validate operationally critical checks like

buyers caution list ,banned import item

list, list of defaulters etc. 2

5.16 System should support the functionality

of back to back Inland/Import LC’s. 2









Form 8

Forex and Trade Finance Page 34 of 238

5.17 System sould have a provision to

display whether notice of discrepancy

has been sent with 7 working days after

receipt of documents, if not system

should generate an alert at least 2 days

in advance 2

5.18 System should provide for

crystallization of bill to be done on due

dates with over riding authority. 2

5.19 System should provide for Liability

monitoring to be done LC wise and

party wise. 2

5.20 System should have a provision for

generating release order. 2

5.21 System should not release the margin

amount at time of closure of LC in case

of insufficient funds 2

5.22 System should generate Bill of entry

reminders 2

5.23 System should generate Bill of entry

statement 2

5.24 System should have a provision for

recording multiple bill of entries against

an import bill. 2

5.25 System should generate Form A1 along

with the exporter importer code

numbers. 2

5.26 The system should display the accounts

in which buyers credit has been availed

and the necessary statement to be

generated to be submitted to ID. 2

5.27 System should generate covering

schedules for the bills received under

LC/Collection basis 2

5.28 System to generate conta entries for

Import bills under collection 2

5.29 System to generate due date statement

in case of acceptance bills 2

5.30 System should facilitate Revaluation of

Foreign Currency bills and vouch for the

difference. 2

5.31 System should provide for debiting

party’s EEFC/PCFC or FCNR B loan,

account for payment of import bill by

recovering necessary charges. 2

5.32 The system should charge interest from

the date of debit to Nostro a/c till the

date of payment in case of import LCs

where reimbursement is already

claimed by negotiating bank. 2

5.33 System should check permissibility of

the commodity for imports as per HS

code. 2









Form 8

Forex and Trade Finance Page 35 of 238

5.34 System should have ability to calculate

the commission based on set

parameters even on interest amount

and + or – tolerance. 2

5.35 System should keep track of all

amendments made to the LC and

charges recovered by the Bank and

also by the correspondent bank. 2

5.36 System should validate the direct import

bills against such entities. – public

sector, pvt. Ltd. Co., pub. Ltd. Co., govt.

co. 2

5.37 System should check for the limitation

set for remittance in case of advance

remittance against imports 2

5.38 System should provide alterations in LC

after authorization but before

transmission of LC 2

5.39 System should automatically cancel

expired / un-utilized LCs after

parameterable number of days from the

date of expiry (provided there is no

outstanding) 2

5.40 System should generate outstanding

import bills under LC country-wise and

commodity-wise 2

5.41 Air imports –delivery order generated(at

bank’s request). Routing of such

document be through FAB (Airway bill)

the realization / retirement of bill / entry

will be from the suspense receipts first

and then other account. 2

5.42 System should calculate the

commission at appropriate rates for

import payment made out of EEFC

funds. 2

5.43 System should segregate Advance

remittance for which BOE has been

received /not received. 2

5.44 System should support interest

calculation for reimbursement under 2

5.45 System should support debiting

commission on payment out of EEFC

Funds for Import payments. 2

5.46 System should ensure that interest is at

normal lending rate for non-priority

sector advances from lodgment of FAB

till retirement 2

6 Inward Remittance

6.1 Syatem should have a provision to allot

a unique number for each IR. 2

6.2 System should check for entering

duplicates in the IRs – same ref no.

same beneficiary – to give an alert for

caution. 2









Form 8

Forex and Trade Finance Page 36 of 238

6.3 System should have provision to advise

the beneficiary of the IR credits. 2

6.4 System should generate FIRC for

advance remittance for export 2

6.5 In case of other transactions, if

required, system should generate FIRC

and recover charges automatically 2

6.6 System should have provision for

placing the funds in EEFC/NRE/FCNR. 2

6.7 Purchase of currency and TCs--System

should have a provision for recording

the details of CDF in case the purchase

exceeds prescribed limits. 2

6.8 System should have provision for

recovering necessary charges (only net

amount to be credited) 2

6.9 In case of inward remittances to other

branches the system should generate a

declaration form to be obtained from

the beneficiary in case of amounts

exceeding Rs.1 lac , along with the

credit advice. 2

6.10 System should alert the user incase of

remittances under FOCRA where

organization are listed 2

6.11 System should pass necessary

vouchers for IRs at a given rate,

identified by the A-Cat branch , in favor

of a B-Cat branch. 2

6.12 System should keep a list of banned

entities and should caution the user

when a remittance is received from one

such entities. 2

6.13 System should have a provision to

enter an IR received in physical format (

and funds received in NOSTRO ) 2

7 Clean Instruments collection and

purchases

7.1 Where the instrument represent export

proceeds, system should facilitate

adjustment of the proceeds to PC/PS

finance and linking of the corresponding

GR form release. 2

7.2 System should facilitate crediting

realization of the instruments to various

accounts of the customer such as

FCNR/NRE/NRO/ based on defined

parameters. 2

7.3 System should generate an alert in

case local funds are credited to NRE

account. 2

7.4 System should have a provision for tax

deducted at source provided in NRO

a/c. 2









Form 8

Forex and Trade Finance Page 37 of 238

7.5 System should allow opening/ crediting

FCNR/EEFC/NRE/ RFC before the

instrument is realized 2

7.6 In case of instrument sent for collection

the system should facilitate giving credit

to the customer account during the

reserved period. 2

7.7 The system should open RFC,

domestic RFC accounts based on

certain criteria. In case the criteria are

not met with the system should not

open the account. 2

7.8 The system should have a cooling-

period provision for showing a check

collected in NOSTRO account as

“realized”. The cooling period should be

parameterised. 2

7.9 Credit advices should be generated by

the system for credits to non-CBS

branches for Checks collected. 2

7.10 In case of return of purchased

instruments, the charges levied in the

NOSTRO account should be debited to

beneficiary’s account and advise

accordingly. 2

8 Outward Remittance

8.1 System should maintain Limits for

different purposes as per RBI. 2

8.2 System should generate Form A2 and

form A1 2

8.3 System should facilitate checking of

KYC – Money laundering norms 2

8.4 System should recover value from

EEFC /RFC account. 2

8.5 System should display a list of all

advance remittance for imports where

bill of entry has been received/ not

received 2

8.6 System should automatically calculate

commission and charges. 2

8.7 System should not accept cash more

than Rs.50000/- in case of current /

capital account transactions. 2

8.8 System should allow issuance of

DD/TT/TC/Currency with in the

prescribed limits to a single customer

and outsiders. 2

8.9 System should maintain a DD – stock

register. 2

8.10 System should facilitate Auto printing of

DD. 2

8.11 system should have a provision to

generate vouchers for various

transactions including inter branch. 2

8.12 System to maintain TC – stock register. 2









Form 8

Forex and Trade Finance Page 38 of 238

8.13 System should generate caution letter

for DD/TC lost or stolen along with

advice. 2

8.14 System should generate automatically

reimbursement draft on the nostro

account form MT 240 2

8.15 System should generate an alert for

Sale of Currency wnen limits are

exceeded 2

8.16 System should provide for issue of

DD/BC/Pay order for the currency

purchase form authorized

moneychangers. 2

8.17 At a given rate, system should debit

party’s account and credit mirror for FC

transaction. – vouching 2

8.18 System should allow release of

TC/Currency/DD for cheque sent on

collection by approval. 2

8.19 System should maintain stock of

currency notes and marks of the sale to

public and others. 2

8.20 System should provide for tax on

outward remittance. 2

9 Forward Contracts

9.1 System should allow booking cross

currency forward contracts with regular

FWCs. 2

9.2 System should allow booking FWCs for

NRE a/cs. 2

9.3 System should provide for cancellation

of overdue contracts after expiry of the

specified period maturity date. Alert

should be generated for the same 2

9.4 System should generate an alert when

bill is processed against FWCs. 2

9.5 System should provide booking FWCs

for FCNR loan/ PCFC etc. 2

9.6 System should calculate exchange

difference on cancellation of FWC and

generate voucher at the expiry of the

contract. 2

9.7 System should calculate exchange

difference on early / late delivery and

generate vouchers. 2

10 Exchange Rates

10.1 Downloading card rates from treasury--

System sould provide online rates and

chat facility that can be printed for

voucher purposes. 2

10.2 In case transaction amount is less than

$5000 or equivalent the system should

apply card rate and the user should

have a choice to apply special rates for

specific cases. 2









Form 8

Forex and Trade Finance Page 39 of 238

10.3 System should provide a facility to apply

notional rates with a provision to

change to market rates as and

required. 2

10.4 Define Multiple Referential Rate based

on currency. 2

10.5 Identify active base rate for a given

currency. 2

10.6 Define multiple referential rate based

on type of account, currency, rate type

(Whether Debit Rate or Credit Rate). 2

10.7 Modify referential rates for a given type

of accounts. 2

10.8 Allows maintenance of special buying 2

and selling rates.

11 Guarantees

11.1 Issuing guarantees with in limits –

interchangeability. System should

tecover charges upfront within set

parameters. 2

11.2 Margin requirement in INR and FC

computed at selling exchange rate and

cross rate, or mark for non collection of

margin – interest on margin should be

parameterized. 2

11.3 System should support Duty drawback /

Duty exemption- mechanism 2

11.4 Issuance of export performance

guarantee under ECGC covered,

system should generate alert – caution

list ECGC, RBI, countries banned. 2

11.5 System should support linking of

remittance module and deferred

payment guarantee. 2

11.6 Margin to be collected our to loan,

EEFC,/FD and earmarking CC 2

11.7 System should permit

cancellation/reversal of expired

guarentee list after grace period 2

11.8 System should permit bifurcation into

performance, financial bid bond,

advance payment, Mobilization

Advance(for fund raising), retention

money, shipping guarantees(100%

cover) - in FC and INR at notional rate

and automatic recovery of commission. 2

11.9 System should generate statement

bifurcating expired and outstanding

guarantees margin wise, etc. 2

11.10 System shoud provide link between

guarantees – bid bond, performance,

advance money. 2

11.11 System should permit cancellation of

guarantee after receipt of the original

documents or after due authorization. 2









Form 8

Forex and Trade Finance Page 40 of 238

11.12 System should provide vouching of FCs

in base currency and at notional rate

and regular vouching. 2

11.13 System should have facility to

incorporate comfort letters from

corporate and other comfort

documents. 2

11.14 System should permit amendments with

required authorization with log details. 2

11.15 System sould generate standardized

letters i.e intimating honor of claim

notice to opener, reminders,

cancellation, opening form etc, notice of

disclaimer for expired guarantees 2

11.16 System should take into consideration

Expiry period, claim period, reversal

after notice period, and revalidation,

extension after original expiry date 2

11.17 System should support Apportionment

of commission earned to different

quarter, half year etc. 2

11.18 DPG – export / imports - issuance and

maintenance of record, payments.

Linked to imports of goods licensed.

RBI approval No. date. 2

11.19 System should pass liability / contra

vouchers for FBGs? 2

11.20 Sytem should allow marking of lien on

FDRs/collaterals of a different branch

for margin/security purposes – for

issuing of LCs/FBGs. The system

should allow deletion of lien only after

the original guarantee is returned or

expired. 2

11.21 System should generate outstanding

FBG – country-wise / commodity-wise 2

11.22 System should maintain a close link

between bid bond, performance

guarantee, and advance money

received. 2

11.23 Where necessary, the system should

allow collection of commission on a

periodic mode (other than upfront) 2

11.24 The BG from date and to date should

be mandatory 2

12 System should provide for

generation of statements / returns

12.1 R RETURNs 2

12.2 XOS 2

12.3 BEF 2

12.4 MONTHLY TURNOVER (TFD) 2

12.5 IBSBR 2

12.6 ECGC Claims / renewal of limits 2

12.7 IBS (international banking statistics) 2

12.8 Export Bills Written off. 2

12.9 FDS11 2









Form 8

Forex and Trade Finance Page 41 of 238

12.10 STAT 5, 8 , 9 ,10 2

12.11 ALM (forex) 2

12.12 BSR 2

12.13 DSB –IV and V 2

12.14 BAL 2

12.15 MAP & SIR 2

12.16 Export Credits (Weekly) 2

12.17 Format –C 2

13 Back-end support

13.1 System should provide for centrally

defined charges, commission, interest,

exchange, profits, product wise and

have the ability to override such after

approval. 2

13.2 System should provide for opening

FCNR B loans in FC rollover calculation

of interest in FC and converting the

same in INR and accounting at notional

rate 2

14 System should provide for

14.1 RBI circular updating. 2

14.2 UCPDC , URR,URC. 2

14.3 Exim policy – hand book of procedures. 2

14.4 Caution list of RBI. 2

14.5 Specific approval list of ECGC. 2

14.6 ALMANAC 2

14.7 BIC – SWIFT 2

14.8 Courier services software compatible. 2

14.9 Bank circulars. 2

14.10 Bank Manual 2

14.11 Branch directory 2

14.12 Signature album by authority of bank

and corresponding banks. 2

14.13 NOSTRO /VOSTRO 2

14.14 Exchange of SWIFT key arrangements

– list of banks having keys with us. 2

15 Deposit Accounts

15.1 System should have provision to open

various types of non-resident (both

rupee and fc) under SB/Term/Current

schemes. 2

15.2 The system should be able to support

all types of existing deposits products

and to be able to add new products

from time to time through changing the

appropriate parameters. 2

15.3 System should support conversion

from NRE to NRO and Ordinary deposit

accounts as and when required. 2

15.4 System should facilitate printing of

deposit receipts. 2

15.5 The system should ask for the purpose

of remittance while accepting a credit

into a deposit account. 2

16 Bullion Trade









Form 8

Forex and Trade Finance Page 42 of 238

16.1 System should record and maintain

stock of bullion acquired by the branch /

bank on consignment basis and import

on payment / loan basis. System should

record bullion delivery on outright basis

and loan basis for each customer 2

16.2 System should record London AM and

PM fixing on each working day 2

16.3 System should record bullion deals

entered with supplier (s) abroad, on

loan basis with record of value date.

Payment mechanism for outright

purchase, with maximum x days

(parameterisable) and loan basis as per

current EXIM policy / RBI regulations.

Payment 2

16.4 System should facilitate maintenance of

customer accounts of loan deliveries

(BLSE) along with charging of and

recovery of interest 2

16.5 System should faclitate maintenance of

Bank's mirror account with the supplier

abroad , calculation of interest at

agreed rates and support reconciliation

of loan account 2

16.6 System should support reconciliation of

stocks with suppliers 2

16.7 System should facilitate maintenance of

margin accounts customer - wise in

case of out right sale basis release of

margin. Reconciliation of margin

account 2

16.8 System should have provision to define

special zones without import duty 2

16.9 System should record export proof in

SEZ and treatment thereof 2

16.10 System should support automatic

voucher posting 2

16.11 System should generate invoices,

delivery challans, and necessary

receipts, payment of sales tax, octroi

wherever applicable 2

16.12 System should support generation and

submission of statutory and other

returns like Forms 3 & 4 2

16.13 System should facilitate maintenance of

insurance of stocks, due date policy

records and renewal reminders 2

16.14 System should facilitate maintenance of

fidelity guarantee 2

16.15 System should facilitate maintenance of

delivery register. 2

16.16 System should have provision to pay

bullion imports in FC through market

purchase or disbursement of PCFC /

PSFC. 2









Form 8

Forex and Trade Finance Page 43 of 238

17 Domestic Foreign Currency Loans

(DFC)

17.1 System should have provision for

granting foreign currency loans for PC

and Bills Discounting. 2

17.2 System should have provision for

granting loans against FCNR(B) for

Term Loan and Working capital 2

17.3 System should have provision for

recovery through IRs/Export proceeds. 2

17.4 System should record ODA submitted

by the customer for investment in

WOS/JV abroad by Indian Company.

Recode approval from RBI for specific

amount in FC. Effect remittance in FC

in one go or in installments and

maintain records and reconciliation.

Club the remittances affected through

Branch /AD and submit ODR to RBI in

prescribed format. 2

17.5 System should have provision to record

ECB arranged by the borrower and to

record the approval by RBI. Record pre-

payments, reporting in R-Returns and

reconciliation / maintenance of

accounts and calculation of interest

thereon. 2

17.6 System should have provision for

interest calculation frequencies

(mly/qly/hly or at maturity of loan etc) 2

17.7 System should have provision to

generate reminders to the borrower

requesting funding of accounts towards

the ECB installments. 2

17.8 System should have provision to define

the NOSTRO account in which the

borrower would fund for repayments of

the loans. 2

TOTAL 578









Form 8

Forex and Trade Finance Page 44 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. Particulars BR VS TL TM Vendor

No. Comments

1 System should be capable of maintaining master

details of owned premises / immoveable assets

and moveable assets such as date of ownership,

lease period, lease exipry date, location of lease

agreements, value of asset (original value and

present book value), location etc. 2

2 System should capture details of leased out

premises like ownership details, location, date of

lease, amonut of lease, lease expiry, nature of

lease, value, square ft. etc. 2

3 System should support different types of

depreciation methods such as strainght line,

reducing balance method, written down value

method etc. 2

4 System should support parameterisation of the

depreciation percentages for each asset / type of

asset 2

5 System should compute the depreciation as per

the method and pertcentage of depreciation as

specified in the parameter 2

6 System should specify / capture tax details for

calculation of applicable tax as per law of the land 2

7 System should maintain master details of AMC

and contractors e.g. nameof the vendor, AMC

amonut, period of contract, next service date,

AMC expiry date etc.Arrange to issue warning

messages before expiry of warranty. 2

8 System should sub-classify both movable and

immovable assets 2

9 System should support movement of assets from

one location to another 2

10 System should provide for specifying insurance 2

System should asset

11 details for each generate warning messages for

expiry / renweal of insurance x (parameterisable)

number of days prior to actual expiry / renewal

date 2

12 System should maintain asset inspection details

such as last inspection date, next inspection date,

inspection comments etc. 2

13 System should support generation of asset

inspection report along with comments of 2

14 inspector

System should link each asset with a unique asset

number / inventory number

2

15 System should support alpha numeric asset /

inventory number

2

16 System should maintain details on asset litigation

2

17 System should generate a list of movable and

immovable assets based on the user defined

parameters.

2

18 System should generate a listof assets transfered

/ moved from one location to another along with

details such as description of asset, inventory

number etc. and should transfer the book value

through CBS System . 2

19 System should generate depreciation report giving

details of book value, year to year depreciation

and residual value 2

20 System should generate age-wise analysis report

of assets 2









Form 8

Fixed Assets Page 45 of 238

21 System should generate warning messages for

service contracts due x (parameterisable) number

of days prior to such service dates. 2

22 System should record the details of order /

purchase contract, performance gurantee for all

assest procured by the vendor 2

23 System should specify the service level

agrements and link them to a particular asset 2

24 System should support billing and payment 2

25 System should upload / enter bill of material

details along with part numbers, quantity, unit

rate, total rate etc. 2

26 Should support entering of asset details

dispatched to a particular location and track the

movement of the same 2

27 System should record details of asset

acceptance, PDI and note discripiancies in the

asset inspection 2

28 System should generate an asset inspection

report giving details of asset type, asset

description, part number, adverse remarks etc. 2

29 System should capture the asset installation

details for movable assets (e.g. date of

installation, inspection date etc.) 2

30 System should support parameterisation of the

payment terms (no. of months, percentage of

payment) and validate the same at the time of

genrating the invoice in case of leased assets 2

31 System should specify the minimum

requirememts (e.g. documents, compliance to

service level check, authrisation from authority) to

be verified before release of any payment to the

vendors / contractors 2

32 System should record bill / invoice details

submitted by the vendor

33 System should generate a payment advice for

payment to be made by the bank to the vendor 2

34 System should support access to the solution at

the branches / department as per user rights

defined 2

35 System should permit branches / offices to enter

data of assets installed / purchased 2

36 System should have capabilities to group all

assets across the bank to generate a single view

of all assets 2

TOTAL 70









Form 8

Fixed Assets Page 46 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

Delivery channels

1 Internet Banking & PC Banking

1.1 General Requirements

1.1.1 System should allow transaction in 2

Multi – currency

1.1.2 System should allow down load data 2

from the database to selected PC

format e.g. excel, MS money, word

etc)

1.1.3 System should provides user based 2

Report writing options and the ability to

customise all reports

1.1.4 System should interface (seamless 2

integration) with the Core Banking

software, Treasury, Trade Finance,

SWIFT, Credit Card systems,

Customer Relationship software,

RTGS, ATM Switch, DP Cell etc.

1.1.5 The system should be able to offer all 2

services / transactions offered by the

Bank for domestic as well as foreign

currency accounts at the discretion of

the Bank

1.1.6 The system should have the facility to 2

allocate a separate ID / Password

combination for View and Transaction

processing using internet banking

1.1.7 The system should allow the Bank to 2

select / specify menu options that

require a Transaction ID and password



1.1.8 The system should have the facility to 2

create more than one user with

different access privileges and link

them to a particular account / accounts

1.1.9 System should link more than one 2

account to a particular user ID

1.1.10 System should define limits for various 2

transactions for various user ID’s in

line with the customers organisation’s

policy (e.g. fund transfers limits etc.)

1.1.11 The system should facilitate “Maker” 2

“Checker” concept (dual authorisation)

for corporate customers. (e.g. multiple

levels of authorisation within the user’s

organisation for a financial transaction

/ transactions which require such a

type of authorisation.)









Form 8

Delivery Channels Page 47 of 238

1.1.12 System should have “Maker” 2

“Checker” concept (dual authorisation)

at the bank's ends for all transactions.

1.1.13 Should facilitate “Store” and “Forward” 2

mechanism to record off – line

transactions

1.1.14 The system should be able to display 2

a confirmation message with a unique

reference number to the customer

after successful completion of all

transaction on – line and appropriate

alerts to the customers for

transactions not successful

1.1.15 System should store the unique 2

transaction number generated by the

Internet Banking system for all

transactions in the core banking

system and link them to the particular

transaction effected in the core

banking system

1.1.16 System should update the Internet 2

Banking Database as defined by the

user (Bank) i.e. at the time of day –

end, user defined time intervals (every

hour, every updation etc.)

1.1.17 The system should have the facility to 2

define the criteria for update of data to

the Internet Banking Database e.g.

closed accounts, accounts with zero

balances etc.)

1.1.18 Facility to upload data in the 2

respective tables through electronic

mediums such as floppy, file transfers

with proper checks and validity

1.1.19 The system should have the facility to 2

allow the Bank to design its own

template to capture of information from

the customer for any transactions.

1.1.20 The system should allow transactions 2

in a customer account as per the

operating instructions entered at the

time of account opening (e.g. single /

double authorisation required at

customers end for a particular

transaction)

1.1.21 System should send intimation, 2

approval / decline messages to

partner sites e.g. railways etc.

1.1.22 System should support PC banking 2

through remote customer terminal









Form 8

Delivery Channels Page 48 of 238

1.1.23 System should identify transaction 2

done through internet banking and

apply charges to customers account

for the particular activity / transaction

based on the delivery channel

1.1.24 System should show the same 2

account balances across all delivery

channels at any point in time

1.1.25 System should show a geeting 2

message e.g. "Happy Birthday etc." on

the screen if the day on which the user

interacts/transacts is his/her birthday.

2

1.2 Security

1.2.1 The system should be able to 2

automatically check the passwords

with the password policy, which can be

customised by the bank.

1.2.2 The system should be able to store 2

the user ID password in an encrypted

mode/ a compressed mode / unclear

text within the Internet Banking

application.

1.2.3 The system should be capable of 2

encrypting data (e.g. password,

financial data etc.) during transit.

1.2.4 The Internet Banking system should 2

only be accessed by SSL enabled

browsers

1.2.5 The system should be able to 2

generate audit trails of all transactions

done as on any particular date. The

minimum fields that should be

captured in the audit trail are: -

Ø Account Number

Ø Date & time stamp

Ø Transaction ID

Ø Operator ID

Ø Authorised By (ID)

1.2.6 The system should be also capable of 2

generating exception reports on a

daily basis as a part of the day – end

activity. It should also be able to

print/display exception reports for any

defined date .The exception listing

should capture the following

Ø Those transactions that require

approvals from higher authorities other

then the normal authorisation level

Ø All cancelled transactions

Ø Any changes made to the global

parameter files etc.









Form 8

Delivery Channels Page 49 of 238

1.2.7 The system should display the 2

following fields in the exceptional

transaction report

Ø Account Number

Ø Date & time stamp

Ø Transaction ID

Ø Operator ID

Ø Transaction Details (before

changes)

Ø Transaction Details (after

changes)

Ø Referred by ID (referring officer

in case of higher approvals)

Ø Authorising Personnel ID

Ø Remarks if any

1.2.8 System should print / view audit trails / 2

exception reports conditionally (e.g.

range of accounts, type of

transactions, user ID etc.)

1.2.9 The system should generate a 2

transaction log of all transactions done

during the day.

1.2.10 System should define messages to be 2

displayed for different types of errors.

1.2.11 The system should generate a list of 2

all rejected transaction and the reason

for rejection



1.3 Account Services

1.3.1 The system should be able to display 2

all the accounts of the customer after

login. (e.g. deposit accounts, loan

accounts, credit cards etc.)

1.3.2 The system should have the ability to 2

display the account balance of a

particular account selected by the

customer (i.e. available balance, un -

cleared funds, total balance, limits,

holds)

1.3.3 The system should have the facility to 2

display the last 7 to 10 transactions for

the account selected by the user

1.3.4 The system should also be able to 2

accept from the user a specific date

range for the statement of accounts to

be displayed

1.3.5 The system should facilitate the user 2

to query for a particular transaction

based on amount, transaction date,

currency, instrument number etc.

1.3.6 The system should be able to display 2

the account details (master details) for

the selected account.







Form 8

Delivery Channels Page 50 of 238

1.3.7 The system should have the facility to 2

download the statement of account for

any date range as specified by the

user to a PC based format (e.g. MS

money, excel, word etc.)



1.4 Deposits

1.4.1 System should allow a customer to 2

request for receipt opening. The

system should display the applicable

interest rates, with holding tax (if

applicable), maturity period, maturity

amount at the time of request

1.4.2 The system should facilitate opening 2

of a new fixed deposit for the schemes

offered by the bank, by debiting the

customers account (rupee / foreign

currency) on – line

1.4.3 At the time of opening the deposit the 2

system should be able to capture the

details such as debit account number,

deposit tenure, deposit amount,

currency, interest pay out mode,

maturity instructions, branch etc.

1.4.4 The system should have an interest 2

calculator to enable the user to view

the maturity value and tax to be paid

before opening a fixed deposit for a

particular scheme.

1.4.5 The system should also allow the user 2

to request for modification of selected

1.4.6 The system should allow the user to 2

request for closure of the term deposit.

(either on maturity / pre mature)

1.4.7 The system should allow the user to 2

view the total Withholding Tax to be

paid by him / her for all fixed deposits

held by him for the current / previous

financial years

1.4.8 The system should allow the user to 2

view the term deposit details for the

selected term deposit account (e.g.

date of deposit opening, interest rate,

maturity value, hold amount, tenure,

name of deposit holder, joint names

etc.)

1.4.9 The system should allow a user to 2

request for part / full renewal of



1.5 Loans









Form 8

Delivery Channels Page 51 of 238

1.5.1 The system should have the facility to 2

enable a user to view all the different

loan schemes offered by the bank

along with their interest rates.

1.5.2 The system should have the option of 2

an EMI calculator to enable the user to

view the EMI payable for a particular

retail loan scheme

1.5.3 The system should have the facility to 2

enable a user to fill in the loan

application form on – line and submit

the same or download the loan

application form

1.5.4 The system should have the facility to 2

calculate the maximum amount that

can be disbursed, effective interest

rates and EMI schedule based on the

information entered by the customer

e.g. income, tenor, capacity to pay

EMI + tenor.

1.5.5 The system should have the facility to 2

accept part or full payment from the

user by debiting his / her account

maintained with the bank.

1.5.6 The system should have the facility to 2

display the payment schedule for the

loan account selected

1.5.7 The system should have the facility to 2

display the last 7 to 10 transactions for

the account selected by the user

1.5.8 The system should also be able to 2

accept from the user a specific date

range for the statement of accounts to

be displayed.

1.5.9 The system should have the facility to 2

download the statement of account for

any date range as specified by the

user to a PC based format (e.g. MS

money, excel, word etc.)

1.5.10 The system should have the facility to 2

display the break up of EMI for both

principal and interest



1.6 Payments

1.6.1 The system should allow the user to 2

register on – line / download the

registration form for account transfers.

1.6.2 The system should only allow the user 2

to debit / credit the particular accounts

that he / she has registered for

1.6.3 The system should be able to facilitate 2

fund transfers on - line between









Form 8

Delivery Channels Page 52 of 238

Accounts of the customer in the same

branch

Between accounts of the customer

across branches

1.6.4 System should request for payment : 2

Transfer to third party accounts in the

same branch on request

Transfer to third party accounts across

branches on request

Between the customer and another

bank / financial institution on request

1.6.5 The system should enable the user to 2

enter the details of the beneficiary (i.e.

all the relevant fields for the purpose

of fund transfers) e.g. name of

beneficiary, branch where account

held, account number etc.

1.6.6 The system should be able to capture 2

the beneficiary details for a minimum

of x (to be decided by the bank)

beneficiaries

1.6.7 The system should allow the user to 2

modify selected details (as decided by

the bank) of the beneficiary

1.6.8 The system should prompt the user for 2

confirmation before execution of the

fund transfer.

1.6.9 The system should allow the user to 2

drop / delete a beneficiary from his list

of beneficiaries

1.6.10 The system should allow the user to 2

inquire the beneficiary details by

specifying user defined criteria (e.g.

name, account number, branch where

account held etc)

1.6.11 The system should allow the user to 2

disable the service of funds transfer

through an option

1.6.12 The system should be able to debit 2

and credit the customer’s accounts on

– line for fund transfers effected.

1.6.13 The system should allow the user 2

(bank) to design the template for

transfer of funds through standing

orders

1.6.14 The system should allow the user to 2

request for a standing instruction by

filling up the relevant details on – line

1.6.15 The system should allow a user to 2

modify selected fields of the standing

order









Form 8

Delivery Channels Page 53 of 238

1.6.16 The system should allow a user to 2

request for cancel / discontinue a

standing order.

1.6.17 The system should be able to intimate 2

the user after execution of the

standing instruction by mail, fax, sms

1.6.18 The system should automatically 2

generating a unique transaction

number for every transaction, along

with a short message / narration (user

definable) which should be returned to

the customer after the transaction is

effected.

1.6.19 The system should identify each 2

transaction I.e. direct debit, credit card

debit etc. for each type of service e.g.

electronic ticketing etc.

1.6.20 The system should generate a list of 2

all transaction effected in the core

banking through internet banking as

per the type of transaction / service or

both e.g. electronic ticketing

transactions done through credit cards

1.6.21 System should record / pass 2

transactions from partner sites e.g.

railways etc.



1.7 Correspondence

1.7.1 The system should have the facility to 2

send mails to or receive mails from the

customer relationship managers. The

system should have the facility to link

customers to a particular customer

relationship manager

1.7.2 The system should have at least the 2

following options for correspondence

Compose

Send

Inbox

Read

Delete

Send to Trash

View Trash



1.8 Utility Bill Payment

1.8.1 The system should allow the user to 2

register on – line / download the

registration form for utility bills

payment.

1.8.2 The system should only allow the user 2

to debit the particular accounts that he

/ she has registered for









Form 8

Delivery Channels Page 54 of 238

1.8.3 The system should be capable to 2

maintain a list of registered utility

companies with the bank

1.8.4 The system should be able to upload 2

billing data / files received from the

registered utility companies into the

application

1.8.5 The system should allow the user to 2

select only those companies

registered by him for payment

1.8.6 The system should at least display the 2

bill number, bill amount, bill date, due

date, amount due upon selecting the

company .

1.8.7 The system should have the facility to 2

accept the bill amount from the

customer.

1.8.8 The system should have the facility to 2

accept or reject a transaction for short

payment (i.e. amount entered is less

than amount displayed)

1.8.9 The system should allow the user to 2

select his debit account number

through the bill payment option.

1.8.10 The system should have the facility to 2

send a mail before the due date

(parameterisable) in the event the bill

has not been paid.

1.8.11 The system should be able to debit the 2

customer account on – line on

conclusion of the transaction

1.8.12 The system should have the facility to 2

display to the customer the amount

paid, unpaid, penalty, charge amounts

etc. utility company - wise or amount

wise

1.8.13 The system should allow the user to 2

schedule payments for future dates.

1.8.14 System should have the facility to give 2

a standing instruction for payment of

bill on a due date

1.8.15 The system should have the facility to 2

intimate the customer through mail,

fax, sms or email, about the success /

failure of the transaction.

1.8.16 The system should enable a user to 2

request for termination of the bill

payment service for a particular utility

company by filling in the Request for

Cancellation form on – line.









Form 8

Delivery Channels Page 55 of 238

1.8.17 The system should be able to intimate 2

the customer about the cancellation of

the facility once authorised by the

Bank.



1.9 Personalised Account Information

1.9.1 The system should allow a user to 2

customise his / her front – end (e.g.

set date formats, account formats, e-

mail id for correspondence, set

primary account, favorites etc.)

1.9.2 The system should allow a user to set 2

a limit (minimum balance to be

maintained) for all / specific accounts

held with the bank.

1.9.3 The system should be able to 2

generate appropriate warning

messages upon crossing the specified

1.9.4 The system should be able to display 2

the customisations done, limits,

utilisation, current balance etc. through

the view option for the account

selected.



1.10 Customer Service & Information

1.10.1 The system should allow a user to 2

request for a statement of account by

fax, e-mail etc. for the selected

customer account by specifying the

date range.

1.10.2 The system should display the fax 2

number of the customer as specified in

the customer master at the Core

Banking solution and also request the

customer to enter a new fax number

he / she wishes the statement to be

1.10.3 The system should be able to fax the 2

customer statement based on the

number specified by the customer

1.10.4 The system should allow a user to 2

request for a cheque book on – line.

1.10.5 The system should allow a user to 2

view the cheque books issued to his /

her account for the selected account

and date range.

1.10.6 The system should allow the user to 2

inquire the status of a cheque leaf

(e.g. paid, stopped, not issued, not

paid etc.)









Form 8

Delivery Channels Page 56 of 238

1.10.7 The system should allow the user to 2

check for the status of the cheque

book issued to him for a particular

account (number of leaves, total paid,

unpaid, stopped etc.)

1.10.8 The system should have the facility to 2

process a stop payment request by a

customer on - line / on request

1.10.9 The system should be able to display 2

the instruments pending for clearing

(outward clearing) for the selected

account.

1.10.10 The system should allow an existing 2

customer to fill in and submit the

Account Opening Form on – line or

download the same.

1.10.11 The system should have the facility to 2

upload the interest rates for various

deposit schemes, loan schemes,

current accounts etc. to enable the

customer to view the same.

1.10.12 The system should have the facility to 2

enable a user to change his / her

passwords

1.10.13 The system should allow the customer 2

to request for a pay order / bankers

cheque / draft , any other instrument

by debiting his account online

1.10.14 The system should be capable of 2

accepting the disposal information for

the requested pay order / bankers

cheque / draft i.e. courrier, personal

collection from the branch etc.

1.10.15 The system should be able to print the 2

pay order / bankers cheque / draft at

any location of the Bank I.e. Data

Center, regional central processing

units, designated branches etc.

1.10.16 The system should allow a user to 2

view the details of a pay order,

demand draft, banker’s cheque, any

other instrument.

1.10.17 The system should allow the user to 2

update his / her customer profile on –

line (e.g. employers name, address

etc.). The Bank should have the ability

to define the fields / information that

can be directly changed by the user

1.10.18 The system should allow the user to 2

request for change in his / her address

by filling up all the required details on

– line









Form 8

Delivery Channels Page 57 of 238

1.10.19 The system should allow the user to 2

view all charges, commission etc.

applicable for various products /

services offered by the bank.

1.10.20 The system should allow a user to 2

view the various products / services

offered by the bank.

1.10.21 The system should allow a user to 2

query on the status (success / failure)

of any transaction / request by

specifying the date range, activity etc.

1.10.22 System should allow registration on – 2

line for services offered by the bank

(e.g. phone banking)

1.10.23 The system should be capable to 2

upload the day’s gold selling / buying

rates for different gold products

offered by the Bank

1.10.24 The system should allow the bank to 2

display messages / bulletins for

example advertising new products

launched by the bank, important bank

news, financial results of the bank,

awards won by the bank etc.

1.10.25 System should have functionality for 2

reporting loss of ATM, debit card etc.

1.10.26 System should have functionality 2

related to handling request for ATM,

debit cards etc.

1.10.27 System should download forms for 2

ECS.

1.10.28 System should request for issue of 2

Phone banking PIN

1.10.29 System should request for advance 2

booking of tickets for visit to pilgrimage

centers

1.10.30 System should on - line request for 2

train, bus reservation

1.10.31 System should subscribe for any 2

investment options offered by the bank

with the facility of on - line debit

1.10.32 System should process request for 2

payment of school fees, college fees

etc.

1.10.33 System should automatically disable 2

the customer account in the event the

customer has not logged in for x

number of days (parameterisable)

1.10.34 System should enable customer 2

accounts which have been disabled

due to non-use for specified period









Form 8

Delivery Channels Page 58 of 238

1.10.35 System should automatically generate 2

an intimation letter or intimate the

customer through e-mail, SMS etc.

informing him about non usage of his

created account before automatically

disabiling the account

1.10.36 System should be able to 2

accommodate and incorporate any

other utility services in future.



1.11 Credit / Debit card Transactions

1.11.1 The system should have seamless 2

integration with the credit / and debit

card systems.

1.11.2 The system should be able to display 2

the card details of the customer for the

card selected (credit / debit) for

example current balance, limit,

utilisation, name of card holder,

address etc.

1.11.3 The system should be able to display 2

the current statement for the card

selected

1.11.4 The system should be able to display 2

and download (standard formats e.g.

Excel) transactions between two dates

as specified by the customer

1.11.5 The system should allow the user to 2

subscribe for payment of credit card

bills by filling the relevant detail on –

line or should have the facility to

download the same.

1.11.6 The system should have the facility to 2

display the current unbilled

transactions to the user for the

account selected.

1.11.7 The system should have the facility to 2

display to the user, the total

accumulated loyalty points for the

credit / debit card selected

1.11.8 The system should have the facility to 2

maintain the list of items / products

that are offered by the bank for

redemption against the respective

1.11.9 System should request for redemption 2

of loyalty points for both debit / credit

cards

1.11.10 System should request for PIN change 2

for both debit / credit cards.

1.11.11 System should report for loss / stolen 2

card for both debit / credit cards

1.11.12 System should request for limit 2

enhancement







Form 8

Delivery Channels Page 59 of 238

1.11.13 System should download forms for 2

add-on cards, supplementary or new

cards

1.11.14 The system should be capable of 2

permitting user to make payments for

various services availed through credit

cards

1.11.15 The system should be capable of 2

generating a report of all transactions

done using a credit card.



1.12 Demat Services

1.12.1 System should view the holding for the 2

selected account.

1.12.2 System should view the status of the 2

shares / securities given for demat

(e.g. pending, rejected), for the

selected account.

1.12.3 System should search for the 2

International Securities Identification

number (ISIN) based on the company

selected.

1.12.4 System should view the transaction in 2

the account as per the date range

specified or current transactions i.e.

last 7 or 10 transactions.

1.12.5 System should specify debit account 2

for recovery of demat charges

1.12.6 System should view the master details 2

of the selected account.

1.12.7 System should allows the user to view 2

the details such as settlement number,

settlement period, market type, pay –

in date etc. of the stock exchange

selected.

1.12.8 System should allow download of 2

forms for “Demat Request”

1.12.9 System should view broker accounts 2

for settlement details of BSE, NSE,

NSDL etc.



1.13 Trade Finance

1.13.1 The system should have the facility to 2

allow the Bank to design its own

template for capturing details for LC

opening.

1.13.2 The system should allow a user to 2

request for opening a Letter of Credit

by filling up the necessary LC template

on – line or should enable the user to

download the template









Form 8

Delivery Channels Page 60 of 238

1.13.3 The system should have the facility to 2

enable a user to modify of specific

details of the LC before authorisation.

1.13.4 System should define limits for various 2

transactions for various user ID’s in

line with the customers organisation’s

policy (e.g. LC opening limits,

modification rights etc.)

1.13.5 The system should allow the user to 2

search for a particular LC based on LC

number, date, amount, currency etc.



1.13.6 The system should have the facility to 2

view LC status

1.13.7 The system should allow the user to 2

request for an amendment in the LC

after appropriate authorisation from

the designated authority

1.13.8 The system should enable a user to 2

request for opening a Bank Guarantee

by filling up the necessary details on –

line or should enable the user to

download the same

1.13.9 The system should have the facility to 2

enable a user to modify specific details

of the Bank Guarantee

1.13.10 The system should allow the user to 2

search for a particular Bank

Guarantee based on Guarantee

number, date, amount, currency etc.

1.13.11 The system should allow the user to 2

view the status of import bills on - line

(e.g. lodged, accepted, correspondent

bank payment, settled.

1.13.12 The system should allow the user to 2

view the status of export bills on - line

(e.g. negotiated, purchased,

discounted etc.

1.13.13 The system should allow the user to 2

view the margin details on - line (e.g.

LC margin, bill margin, shipping

guarantee / parcel guarantee.

1.13.14 The system should enable the user to 2

view all outstanding on - line (e.g.

Import bill outstanding, export bills

unrealised, loan outstanding etc along

with interest accrued)

1.13.15 The system should accept instructions 2

for outward remittence up tp a

prescribed limit by allowing a template

for SWIFT MT-100 format.









Form 8

Delivery Channels Page 61 of 238

1.13.16 The system should accept instructions 2

for issue of Draft on our NOSTRO

Accounts. The necessary and

relevant template for this should be

provided to the user.

1.13.17 The system should enable a user to 2

request for extending the due date of

the bills sent for collection, bills

purchased.

1.13.18 The system should allow the user to 2

view and/or download the complete

history of the bills settled.



1.14 Electronic Ticketing

1.14.1 System should link to partner sites 2

(railways / bus authorities) for

processing of payments for booking of

tickets (advance railway / bus journey

reservations ) though internet banking

1.14.2 System should process payment 2

requests from partner sites

1.14.3 System should support payments to 2

be made through direct debit from

various accounts linked to the

particular customer / credit cards

issued to the particular customer

1.14.4 System should pass on the 2

confirmation message to the linked

partner site informing about the

success / failure of the transaction on -

line

1.14.5 System should generate a unique 2

transaction number for payments

made through internet Banking and

inform the same to the customer along

with the conformation message

1.14.6 System should automatically debit the 2

customers account on - line in the core

banking solution / credit card system

for the payment made and credit the

respective partner accounts

(consolidated single entry / per

transaction (parameterisable))

1.14.7 System should link the transactions 2

passed in the customers account in

the core banking solution, credit card

system, partner site with the unique

transaction number generated and

returned to the customer

1.14.8 System should query on a particular 2

transaction based upon the unique

transaction number and other

parameters.







Form 8

Delivery Channels Page 62 of 238

1.14.9 System should interface with the credit 2

cards systems for processing

payments made through the credit

cards

1.14.10 System should print a report of all 2

transactions made through the internet

banking package, mode of payment -

wise / consolidated along with the

unique transaction number and details

of the transaction as on a particular

date / range of dates and other

parameters



1.15 Tax Collection Services - on - line

1.15.1 System should link to partner sites (tax 2

/ government authority sites) for

processing of payments of taxes for

Bank's customers having internet

banking facilities though internet

banking

1.15.2 System should process payment 2

requests from such partner sites

1.15.3 System should pass on the 2

confirmation message to the linked

partner site informing about the

success / failure of the transaction on -

line / batch mode

1.15.4 System should generate a unique 2

transaction number for payments

made through internet Banking and

inform the same to the customer along

with the conformation message

1.15.5 System should automatically debit the 2

customers account on - line in the core

banking solution for the payment

made and credit the respective partner

accounts (consolidated single entry /

per transaction (parameterisable))

1.15.6 System should link the transactions 2

passed in the customers account in

the core banking solution, partner site

with the unique transaction number

generated and returned to the

customer

1.15.7 System should query on a particular 2

transaction based upon the unique

transaction number









Form 8

Delivery Channels Page 63 of 238

1.15.8 System should consolidate all 2

collections made through internet

banking at the data centre / parent

branch (where the tax account is

maintained) along with other

collections made through the

branches.

1.15.9 System should print a report of all

transactions made through the internet

banking package, mode of payment -

wise / consolidated along with the

unique transaction number and details

of the transaction as on a particular

date / range of dates and other

parameters



1.16 Collection Services

1.16.1 System should support collection of 2

school fees , college / university fees,

taxes etc.

1.16.2 System should maintain tables of fees, 2

charges etc. based upon institutions

tied up with

1.16.3 Download Forms designed for 2

capturing information for payment of

fees as desired by the Bank

1.16.4 System should accept details of the 2

challan for payment of taxes

1.16.5 System should display the total fees to 2

be charged based upon the institution

selected

1.16.6 System should support payments to 2

be made through direct debit from

various accounts linked to the

particular customer / credit cards

issued to the particular customer

1.16.7 System should generate a unique 2

transaction number for payments

made through internet Banking and

inform the same to the customer along

with the conformation message.

1.16.8 System should automatically debit the 2

customers account on - line in the core

banking solution / credit card system

for the payment made and credit the

respective institutions accounts

(consolidated single entry / per

transaction (parameterisable))









Form 8

Delivery Channels Page 64 of 238

1.16.9 System should link the transactions 2

passed in the customers account in

the core banking solution, credit card

system, partner site with the unique

transaction number generated and

returned to the customer

1.16.10 System should query on a particular 2

transaction based upon the unique

transaction number

1.16.11 System should interface with the credit 2

cards systems for processing

payments made through the credit

cards

1.16.12 System should print a report of all 2

transactions made through the internet

banking package, mode of payment -

wise / consolidated along with the

unique transaction number and details

of the transaction as on a particular

date / range of dates institution - wise

for total collections made (taxes, fees

etc.)



2 Phone Banking

2.1 General Requirements

2.1.1 System should interface (seamless 2

integration) with the Core Banking

software, Credit Card systems etc.

2.1.2 The system should be able to offer all 2

services / transactions offered by the

Bank for domestic as well as foreign

currency accounts at the discretion of

the Bank

2.1.3 The system should have the facility to 2

allocate a separate ID / PIN

combination for announcements

(query ) and announcements with

Transactions (transaction ID)

2.1.4 The system should allow the Bank to 2

select / specify options that require a

Transaction ID and password

2.1.5 The system should have the facility to 2

create more than one user with

different access privileges and link

them to a particular account / accounts

2.1.6 System should link more than one 2

account to a particular user ID

2.1.7 System should define limits for various 2

transactions for various user ID’s in

line with the customers organisation’s

policy (e.g. fund transfers limits etc.)

2.1.8 System should handle off- line 2

transactions







Form 8

Delivery Channels Page 65 of 238

2.1.9 Should facilitate “Store” and “Forward” 2

mechanism to record off – line

transactions

2.1.10 The system should be able to 2

announce a confirmation message

with a unique reference number to the

customer after successful completion

of all transaction on – line and

appropriate alerts to the customers for

transactions not successful

2.1.11 System should store the unique 2

transaction number generated by the

Phone Banking system for all

transactions in the core banking

system and link them to the particular

transaction effected in the core

banking system

2.1.12 System should update the Phone 2

Banking Database as defined by the

user (Bank) i.e. at the time of day –

end, user defined time intervals (every

hour, every updation etc.)

2.1.13 The system should have the facility to 2

define the criteria for update of data to

the Phone Banking Database e.g.

closed accounts, accounts with zero

balances etc.)

2.1.14 Syste shoud have facility to upload 2

data in the respective tables through

electronic media

2.1.15 The system should allow transactions 2

in a customer account as per the

operating instructions entered at the

time of account opening (e.g. single /

double authorisation required at

customers end for a particular

transaction)

2.1.16 System should announce a greeting 2

message e.g "Good Morning / Evening

etc." based on the time

2.1.17 System should identify transaction 2

done through phone banking and

apply charges to customers account

for the particular activity / transaction

based on the delivery channel



2.2 Security

2.2.1 The system should be able to 2

automatically check the user ID’s and

PIN with the phone Banking Database.









Form 8

Delivery Channels Page 66 of 238

2.2.2 The system should be able to store 2

the user ID’s and PIN in an encrypted

mode/ a compressed mode / unclear

text within the Phone Banking

application.

2.2.3 The system should be capable of 2

encrypting data (e.g. password,

financial data etc.) during transit.

2.2.4 The system should be able to 2

generate audit trails of all transactions

done as on any particular date. The

minimum fields that should be

captured in the audit trail are: -

Ø Account Number

Ø Date & time stamp

Ø Transaction ID

Ø Operator ID

Ø Authorised By (ID)

2.2.5 The system should be also capable of 2

generating exception reports on a

daily basis as a part of the day – end

activity. It should also be able to

print/display exception reports for any

defined date .The exception listing

should capture the following

Ø Those transactions that require

approvals from higher authorities other

then the normal authorisation level

Ø All cancelled transactions

Ø Any changes made to the global

parameter files etc.

2.2.6 The system should at least display the 2

following fields in the exceptional

transaction report

Ø Account Number

Ø Date & time stamp

Ø Transaction ID

Ø Operator ID

Ø Transaction Details (before

changes)

Ø Transaction Details (after

changes)

Ø Referred by ID (referring officer

in case of higher approvals)

Ø Authorising Personnel ID

Ø Reasons for exception

2.2.7 System should print / view audit trails / 2

exception reports conditionally (e.g.

range of accounts, type of

transactions, user ID, date range etc.)

2.2.8 The system should be capable of 2

generating a transaction log of all

transactions done during the day.







Form 8

Delivery Channels Page 67 of 238

2.2.9 System should define messages to be 2

displayed for different types of errors.

2.2.10 The system should be able to 2

generating a list of all rejected

transaction and the reason for

rejection



2.3 Account Services

2.3.1 The system should allow a user to 2

select any of his / her accounts after

calling e.g. deposit accounts, loan

accounts, credit cards etc.)

2.3.2 The system should announce the 2

account balance of a particular

account selected by the customer (i.e.

available balance, un - cleared funds,

total balance, limits, holds)

2.3.3 The system should have the facility to 2

announce the last 5 to 7 transactions

for the account selected by the user



2.4 Payments

2.4.1 The system should debit / credit the 2

particular accounts that he / she has

registered for

2.4.2 The system should be able to facilitate 2

fund transfers on - line between

2.4.3 Accounts of the customer in the same 2

branch

2.4.4 Between accounts of the customer 2

across branches

2.4.5 System should request for payments 2

2.4.6 System should have the function of 2

Transfer to third party accounts in the

same branch on request

2.4.7 System should have the function of 2

Transfer to third party accounts across

branches on request

2.4.8 The system should prompt the user for 2

confirmation before execution of the

fund transfer.

2.4.9 The system should allow the user to 2

disable the service of funds transfer

through an option

2.4.10 The system should be able to debit 2

and credit the customer’s accounts on

– line for fund transfers effected.

2.4.11 The system should be capable of 2

generating and announcing a unique

transaction number for every

transaction done trough phone

banking









Form 8

Delivery Channels Page 68 of 238

2.4.12 The system should be able to 2

generate a report of all transaction

effected in the core banking through

phone banking



2.5 Customer Service & Information

2.5.1 The system should allow a user to 2

request for a statement of account by

fax, e-mail etc. for the selected

customer account.

2.5.2 The system request the customer to 2

specify an alternate fax number in the

event the customer wishes the

statement to be faxed to the alternate

fax number.

2.5.3 The system should be able to fax the 2

customer statement based on the

number specified by the customer

2.5.4 The system should allow a user to 2

request for a cheque book

2.5.5 The system should allow the user to 2

inquire the status of a cheque leaf

(e.g. paid, stopped, not issued, not

paid etc.)

2.5.6 The system should allow the user to 2

inquire for the status of the cheque

book issued to him for a particular

account (number of leaves, total paid,

unpaid, stopped etc.)

2.5.7 The system should have the facility to 2

process a stop payment request by a

customer

2.5.8 The system should be able to 2

announce the instrument pending for

clearing (outward clearing) for the

selected account.

2.5.9 The system should have the facility to 2

announce the interest rates for various

deposit schemes, loan schemes,

current accounts etc.

2.5.10 The system should announce the EMI 2

to be payable base on amount of loan,

tenor

2.5.11 The system should be able to 2

announce the total outstanding

against a particular loan / advance

account as selected by the user.

2.5.12 The system should have the facility to 2

enable a user to change his / her PIN

2.5.13 The system should announce the 2

status (success / failure) of any

transaction / request by specifying the

date, instrument number, amount etc.







Form 8

Delivery Channels Page 69 of 238

2.6 Trade Finance

2.6.1 The system should have the facility to 2

announce LC status

2.6.2 The system should announce the 2

status of export bills (e.g. negotiated,

purchased, discounted etc.

2.6.3 The system should announce 2

outstandings (e.g. Import bill

outstanding, export bills unrealised,

loan outstanding etc along with

interest accrued) for the particular LC

2.6.4 The system should announce the due 2

dates for D/A Bills for both export and

import.



3 Mobile Banking

System should provide the following

facilities to customers through WAP or

GPRS or CDMA

3.1 Balance Inquiry 2

3.2 Mini Statement (last 5 transactions) 2

3.3 Statement Request 2

3.4 Cheque Book Request 2

3.5 Stop Payment 2

3.6 Cheque Status 2

3.7 Fixed Deposit Inquiry 2

3.8 Bill Payment 2

3.9 Demat balance inquiry 2

3.10 Demat Statement (last 3 transactions) 2



4 SMS Banking

System should provide the following

facilities to customers using SMS

4.1 Balance Inquiry 2

4.2 Mini Statement (last 5 transactions) 2

4.3 Statement Request 2

4.4 Cheque Book Request 2

4.5 Stop Payment 2

4.6 Cheque Status 2

4.7 Fixed Deposit Inquiry 2

4.8 Bill Payment 2

4.9 Demat balance inquiry 2

4.10 Demat Statement (last 3 transactions) 2

4.11 Reward Point Balance 2

4.12 Help on usage 2

4.13 Reload Pre-paid Sim Card 2

System should automatically generate

and send SMS alerts for:

4.14 Due date Reminders 2

4.15 Confirmation and summary of 2

Statement sent

4.16 Confirmation of payments made 2







Form 8

Delivery Channels Page 70 of 238

4.17 Credit Card Alerts 2

4.18 Alerts for transactions above 'x' value 2

(parameter to be set by the customer)

4.19 Limit Usage 'x' % of total limit 2

(parameter to be set by the customer)

4.20 Greetings on special occasions / 2

promotional campaigns

TOTAL 608









Form 8

Delivery Channels Page 71 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Asset Liability Management

1.1 Risk Measurement Tools 2

1.2 Gap Analysis 2

1.3 Liquidity Risk Management 2

1.4 Dynamic Liquidity Management 2

1.5 Interest Rate Sensitivity 2

1.6 Proprietary Gaps 2

1.7 Gap Ratios 2

1.8 Dynamic Gap Analysis 2

1.9 Variance Analysis 2

1.10 Duration Analysis 2

1.11 Mark to Market 2

1.12 Simulation and Scenario Analysis 2

1.13 Rate Shock Analysis 2

1.14 Trend/Historical Analysis 2

1.15 Capital Adequacy Measuring 2

1.16 Multiple Currency Solution 2

1.17 MIS & Risk Reports 2

1.18 Variance Analysis 2

1.19 Bucket-wise average interest rate

and maturity for deposits and

advances 2

1.20 Bucket-wise comparison of

mismatches net present of

mismatches and duration gaps 2

1.21 Average balances branch-wise,

product-wise based on historical

data 2

1.22 Actual interest paid/received (in %)

on deposits & advances as

compared to weighted average

interest 2

1.23 Contractual maturity-wise interest

rate distribution 2

1.24 Impact on account of payment &

receipt of interest 2

1.25 Data Analysis Tools 2

1.26 Structural Liquidity Gap 2

1.27 Interest Rate Gap 2

1.28 Net Interest Income/Margin 2

1.29 Tolerance Analysis 2

1.30 Cost to Close 2

1.31 Key Ratio Builder 2

1.32 Trend Analysis 2

1.33 CRR/SLR Calculator 2

1.34 Comparative Analysis 2

1.35 PV Analysis 2

1.36 Forward Analysis 2

1.37 Scenario Analysis 2

1.38 Regulatory Reports 2

1.39 Drill Down in Graphs 2

1.40 ALM Gateway 2

1.41 Data Normalisation 2

1.42 Data Merging 2

Form 8

ALM Page 72 of 238

1.43 Security system 2

1.44 System should support collection

of ALM data from the branches 2

1.45 Definition of Account should

include ALM Requirements 2

1.46 The system should provide for

entry of ALM data for opening new

accounts/ defining existing

accounts for proper classification

of accounts according to needs for

forecasting as given below:

1.47 System should support

differentiation between wholesale

and retail accounts 2

1.48 System should incorporate the

reference to earlier accounts

(being renewed), age of

association with the banks,

reference to other deposit/

advance/ DP / other accounts 2

1.49 System should capture type of

interest payment (floating or fixed),

type of currency and starting

interest rate in all accounts 2

1.50 In Term Deposit accounts:

1.51 System should capture the dates of

maturity (all dates and amounts

maturing in case of multiple pay

dates) 2

1.52 System should capture Frequency

of interest accrual, compounding

frequency (monthly, quarterly, half-

yearly, etc.), interest booking

frequency (monthly, quarterly, half-

yearly) and projected balances (for

fixed interest rate) should be

available for data extraction. 2

1.53 For flexible payment or withdrawal

schemes, the system should

calculate the interest effect in fixed

and floating rate regimes 2

1.54 System should consider the effect

of regular payment and that of

default in payment (penal interest,

etc.) for Recurring deposits 2

1.55 In case of term loans or loans

repayable in Instalments,

1.56 System should record of due dates

for payment, amounts of

repayment expected, maturity

dates and fund flow projections to

be generated. 2

1.57 System should record the effect of

regular payment - in both floating

and fixed rate scenario- and non-

payment of EMIs/ Instalments. 2







Form 8

ALM Page 73 of 238

1.58 System should record frequency of

interest accrual, compounding

frequency (monthly, quarterly, half-

yearly, etc.), interest booking

frequency (monthly, quarterly, half-

yearly) and projected balances (for

fixed interest rate). 2

2 Generation of ALM Reports -

Field Level

2.1 System should support generation

of Maturity Pattern Statement

interest rate wise for Term

Deposits as per REMAINING

maturity on any given date. 2

2.2 System should support generation

of Maturity Pattern Statement

interest rate wise for Term

Deposits according to ORIGINAL

maturity on any given date. 2

2.3 System should support generation

of Maturity Pattern Statement

interest rate wise for Term Loans

as per REMAINING maturity on

any given date. 2

2.4 System should support generation

of Maturity Pattern Statement

interest rate wise for Term Loans

according to ORIGINAL maturity

on any given date. 2

2.5 System should support

classification of assets and

liabilities into precise time buckets

and generation of Maturity Profile /

Liquidity Profile branch-wise/

region-wise / District-wise as per

contractual maturity. 2

2.6 System should support generation

of behavioral maturity pattern

based on behavioral pattern / past

data / empirical studies and

resultant classification. 2

2.7 System should support

classification of retail deposits and

retail loans on the basis of

behavioral maturity into appropriate

buckets. 2

3 Analysis and Risk Management:



3.1 Liquidity Risk Management:

3.2 System should provide maturity

Pattern of Deposits and Advances

and Cash Flow Mismatch 2

3.3 System should provide maturity

Pattern / Duration / Modified

Duration / Revaluation of

Investment Portfolio 2

3.4 Currency Risk:





Form 8

ALM Page 74 of 238

3.5 System should generate statement

of Currency Mismatch and

determination of exchange

positions on daily basis. 2

3.6 System should support Value at

Risk calculation associated with

forward exposures. 2

3.7 Interest Rate Risk

3.8 Duration Gap Analysis 2

3.9 Simulation 2

3.10 Value at Risk of advances /

investment portfolio 2

3.11 System should support calculation

of Earnings at Risk and / or Net

Interest Margin 2

3.12 System should support calculation

of Periodic Returns 2

3.13 System should support Stress Test

on Investment Portfolio 2

3.14 System should generate Statement

of Projected Short Term Dynamic

Liquidity taking into account

projected inflows and outflows in

different time buckets. 2

3.15 System should generate Statement

of Structural Liquidity showing

movement of Balance Sheet items

in time buckets from 1 to 14 days

stretching up to 5 years. 2

3.16 System should generate statement

of Interest Rate Sensitivity

considering both rate sensitive and

non-sensitive items. 2

3.17 System should support Economic

Value Analysis: Change in

economic value of assets and

liabilities resulting from an

assumed percentage change in

interest (say 2%). 2

3.18 System should support calculation

of modified duration based Market

Risk of advances and investment

portfolio as per new RBI

guidelines. 2

4 The system should be capable

of :

4.1 System should have functionality to

determine the unavailed portion of

CCOD. 2

4.2 System should support Roll in and

roll over of Term Deposits. 2

4.3 System should support Embedded

option – Premature withdrawal of

Deposits. 2

4.4 System should support Interest

rate wise as well as maturity wise

classification of Deposits &

advances. 2

Form 8

ALM Page 75 of 238

4.5 System should support Product

Pricing of Deposit & Advances 2

4.6 System should support Attainment

of optimal mix of maturity profile of

incremental assets & liabilities. 2

4.7 System should support Inflow &

outflow on account of Bills

rediscounted. 2

4.8 System should support Lines of

credit extended. 2

4.9 System should support

Invocation/devolvement of bank

Guarantee/LCs. 2

4.10 System should generate Report on

Large Corporate Loans with

maturity beyond 5 years. 2

5 Earning at Risk-

5.1 System should have functionality to

assess Impact of change in the

interest rate on bank’s NII(Net

Interest Income) and NIM(Net

Interest Margin). 2

5.2 System should provide Time-

Bucket wise mismatches of cash

flow as %age to outflow 2

5.3 System should provide Time-

bucket wise mismatches(RSA-RSL

as %age to total equity) 2

TOTAL 180









Form 8

ALM Page 76 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 MIS

1.1 System to segregate branches for 2

consolidation based upon defined

criteria (e.g. n number of branches in

Mumbai, size of braches etc.) and

map them to nodal / link branches

(e.g. n number of branches in Mumbai

to be consolidated at nodal / link

1.2 System to map all nodal / link 2

branches to the HO for consolidated

1.3 System to collate information of 2

various branches / departments linked

to the nodal / link departments and the

1.4 System to generate individual branch 2

reports at any interval at the nodal /

1.5 System to define any report / MIS 2

printing at the Branch, nodal /link

department, H.O based upon defined

parameters e.g. at the time of

1.6 System should upload data received 2

in any electronic format from branches

outside the core banking system for

1.7 System to support manual feeding of 2

data at the nodal / link departments or

Head Office for consolidation and

1.8 System to define reports as 2

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

1.9 System to schedule printing of non – 2

critical reports e.g. n report after every

1.10 System should provide fucntion where 2

user to define print layout (horizontal /

vertical etc.) and other print setting

1.11 System to provide a flexible report 2

writer with the following minimum

1.12 · Specify the format and layout of

1.13 · Summarise and total the

1.14 · Selected records to be included in

1.15 · Selected details from each record

1.16 · Perform arithmetic calculation on

1.17 System should Download data 2

1.18 to/from third party software. a

System to print reports as on 2

particular date, any user defined date

or range of dates for the selected

1.19 System to print all reports in bi-lingual 2

format i.e. English, Hindi/other official









Form 8

MIS Page 77 of 238

1.20 System to define reports for 2

scheduled printing at the branch level,

Zonal Office level, Head Office, nodal

branches etc. e.g. printing of n1

number of reports at day - end at the

1.21 System to restrict access to reports 2

based upon user privileges defined in

1.22 System to have the capability of 2

scheduling report printing

(parameterisable) from the data

centre for the various branches, Zonal

Offices etc. which should be

automatically printed at the designated

1.23 System should check whether Credit 2

Monitoring statement of large borrowal

accounts – Part B – Accounts with Rs.

2 crores and above (parametrisable)

is generated.

1.24 a. Debit and credit summations 2

1.25 b. Overdue bills (Number and 2

1.26 c. Excess /Adhoc allowed, date of 2

1.27 d. Details of guarantee invoked etc 2

1.28 System will be able to generate the 2

above statement for different amounts

viz. Rs. 1 Crore and above etc.

1.29 System should generate the report for 2

balance sheet analysis as per DBOD

RBI guidelines which include tier 1,

tier2 capital, total risk weight assets,

details of loan assets and investment

1.30 The frequencies of generation of 2

these reports /statements can be

parameterised e.g. Quarterly to

Monthly to weekly and vice- versa

1.31 System should feed qualitative 2

comments/notes manually without

affecting the sanctity of report to

explain the reason wherever fields

(e.g. remarks /comments etc.) exist in

a particular report /statement and

1.32 System should segregate accounts 2

quantum wise ( 1 lacs some

head is to be debited for credit of

customer & for cancellation of DD <

1 lac another head is debited for

credit of customer.

2

1.4.4 For cancellation/PAYMENT of

Ddsystem should have the facility to

----------

1.4.4.1 a) Pay cash to the customer

over the counter as per defined

limits and rules. 2

1.4.4.2 b) Credit his account maintained

with the bank. 2

1.4.4.3 c) Pay by bankers cheque.

2

after canceling the draft and

recovering the cancellation charges.

2

1.5 PAYMENT OF DEMAND DRAFT



1.5.1 System should automatically display

the details of the draft captured by

the issuing branch on entering the

key details at the paying branch 2

1.5.2 The system should support payment

of drafts issued by other

correspondent banks on our bank’s

branches after verifying the details

and the status of the drafts (i.e. Stop

payment / Cancellation) from the

drafts uploaded in the centralised

banking system and print related

reports. Also the system should

have the capSystem should

calculate the agency commission for

Draft drawing arrangement. 2

1.5.3 The system should generate a

report of all drafts paid on behalf of

a correspondent bank. 2

1.5.4 System should facilitate issuance

multiple DDs against one single

credit or one DD against multiple

credits. 2

1.5.5 System should be capable of

preventing issuance of DDs already

issued. 2

1.5.6 System should be able to issue

stock of DDs to counter clerk &

maintain the stock. 2

1.6 Telegraphic Transfer









Form 8

Remittance Page 178 of 238

1.6.1 The system should support auto

generated TT manifold and advice

with mailing address 2

1.6.2 The system should support facility

for TT paid.

2

1.6.3 The system should support facility of

reconciliation for the TT’s paid by

paying branch and print a report of

outstanding TTs.

2

1.6.4 In case of missing /duplicate TT

serial number the system should

flash warning signal.

2

1.6.5 At the time of TT issued the system

should generate vouchers

automatically. 2

1.6.6 System should have the capacity to

interface with SFMS services for

sending TTs/RTGS etc. 2

1.6.7 Provision for restricting branches for

sending TTs.

2

1.6.8 Penalty clause in case of delayed

payment of TT 2

1.7 GIFT CHEQUE

1.7.1 Recording and maintenance of

stock receipt/ issue at central office

level/ branch level and update the

stock upon issue.

2

1.7.2 System should be able to print a

report at head office / branch level

as defined for gift cheques issued at

a particular date / range of date

amount wise.

2

1.7.3 System should print stock register of

gift cheques denomination wise.

2

1.7.4 At the time of uploading stock from

central office the corresponding

entries should be released

automatically for updating the stock.

2

1.8 TRAVELLERS CHEQUE

1.8.1 System should issue / accept Indian

rupee travellers cheques issued by

the bank. 2

1.9 OBC/IBC

1.9.1 Facility to enter outward/inward 2

Commission, full details

1.9.2 cheques with Postage, Exchange, 2

other charges Max/Min.should be in

1.9.3 Auto generated schedules, for 2

1.9.4 banks/branchwise.

Facility for modification/deletion of 2

bills.









Form 8

Remittance Page 179 of 238

1.9.5 Conversion from collection to 2

purchase.

1.9.6 Capacity to generate overdue 2

position of unpaid cheques and

1.9.7 Facility for auto generated reminder 2

/ fate enquiry of cheques / received,

1.9.8 Facility to store bank address 2

book/directory of other bank

branches published by RBI whether

1.9.9 System should be able to generate

a report of all instruments grouped

for upcountry clearing with at least

1.9.9.1 *Presentation date, 2

1.9.9.2 *Schedule date, 2

1.9.9.3 *Schedule number, 2

1.9.9.4 *Instrument number, 2

1.9.9.5 *MICR code, 2

1.9.9.6 *Sender bank and branch code 2

etc.

1.10 System should be able to:

1.10.1 1) Allow the user to key in 2

data/upload the same through any

electronic medium at the collection

1.10.2 centre for upcountry clearing

2) Generate a special collection 2

schedule for all other cheques

1.11 ROB/POB Accounts

1.11.1 System should open ROB/POB

(with both debit/ credit balances)

accounts eg. Accounts which are

specifically for the dividend warrant

payments etc.

2

1.11.2 The system should have the System

should classify the entries agewise

& any amount beyond a certain time

has to be shifted to Head Office.



2

1.12 UTILITY BILLS

1.12.1 System should have an option of bill

payment for customers at the bank

and other delivery channels of

remittances. 2

1.12.2 System should interface / have

direct connectivity with the system of

the utility companies / upload data

provided in electronic format in any

medium for bill and payment details

.

2

1.13.3 The system should have the facility

to maintain the list of all registered

utility companies with the bank. 2









Form 8

Remittance Page 180 of 238

1.13.4 The system should have an option

to accept utility bill payments for non

customers of the bank in form of

cash , bankers’ cheque / through

cheques ,.

2

1.14 BANKER’S CHEQUE

1.14.1 System should support issuance of

bankers cheque with full details i.e.

Name of the beneficiary, date of

issue, serial number, amount in

continuous stationery and reconcile

entries at the time of payment.

2

1.14.2 The system should be able to

generate following reports:

1.14.2.1 1. Agewise/ amount wise o/s

entries. 2

1.14.2.2 2. Status wise list of Bankers

Cheques (paid/issued/stale etc.)

2

1.14.2.3 3. Bankers cheques issued/paid

in a period. 2

TOTAL 158









Form 8

Remittance Page 181 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Teller Operations

1.1 System should display customer

balance during transaction posting

and authorization as (cleared

balance, uncleared balance,

drawing power liens, holds available

transaction balance) 2

1.2 System should display overdrawn /

below minimum balances in different

colors. 2

1.3 System should be capable for

balancing of teller and branch cash

denomination wise. 2

1.4 System should display the cash

position of the branch or teller-wise,

on line at any point of time. 2

1.5 System should define floor limits for

teller operations 2

1.6 System should display warning

messages to the teller / authorizing

authority or reject transactions for at

least the following

1.6.1 1. No available balance 2

1.6.2 2. Over and above limits 2

1.6.3 3. Against clearing 2

1.6.4 4. Dormant / inoperative accounts 2

1.6.5 5. Stop cheques 2

1.6.6 6. Cheques not issued 2

1.6.7 7. Cheque already en cashed 2

1.6.8 8. Account restrictions 2

1.6.9 9. Stale / post dated cheques 2

1.7 The system should allow the teller,

cashier, head cashier to enter cash

received from the vault, tellers /

head cashiers etc denomination –

wise and currency – wise. 2

1.8 System should permit deposit /

withdrawals of cash/gift cheques/DD

etc. denomination – wise 2

1.9 The system should be capable of

generating the warning messages

informing the teller/head teller about

the shortage of cash in hand

(denomination – wise) depending

upon the cash retention parameter 2

1.1 System should transfer amounts

between tellers. Track denomination

details for cash deposits and

withdrawals by individual tellers,

cashiers / head cashiers 2

1.11 System should print the end of day

teller log./ Date wise /Teller wise 2









Form 8

Teller Transactions Page 182 of 238

1.12 System should print the end of day

cash analysis report 2

1.13 System should link multiple user ID /

groups / user levels for the defined

workflow e.g. in the event of

authrisation required for an

exceptional transaction / transaction

beyond the power of x automatically

route the transaction as per the

defined workflow to multiple user

say y & z who are authorised to

pass the particular transaction. 2

1.14 System should have a process of

authorization of all the teller entries

vide a batch or individual basis as

per requirement .[No maker checker

for teller] however there must be a

provision for authorization later. 2

1.15 For all transactions, the system

updates the position figure for each

teller and the amount involved. For

each type of position (cheque/

cash), totals are held which can be

used to reconcile with the branch's

General Ledger. 2

1.16 Facility to view cash position for

each teller at any point of time.

Similarly, facility to view

consolidated cash position for the

branch at any point of time (without

closing cash position). 2

1.17 A report on branch totals is to be

produced when all the tellers in the

branch have completed the 'Final

sign off'.' 2

1.18 At start of the day, facility for teller to

authorize the 'Opening cash

position' and the breakdown by

denomination. 2

1.7 Reconciliation of cash as per

system with cash in hand.

Difference to be automatically sent

to appropriate authority for approval. 2

1.19 This can be a stand alone service or

form an integral part of teller

platform for deposit & withdrawal.

All facilities available for domestic

teller operations should also be

available for Foreign Currency Teller

transactions. 2

1.2 Transaction can be of the following

types :

1.20.1 1. Currency tendered or asked for is

same as the currency in customer's

account (e.g. deposit or withdrawal

of dollar from a dollar denominated

account.) 2









Form 8

Teller Transactions Page 183 of 238

1.20.2 2. Currency tendered or asked for is

different from the currency in the

account (e.g. deposit of dollar in

rupees savings account, or

deposit/withdrawal of pound in dollar

account) 2

1.20.3 3. The customer sells one currency

and wants to purchase another

currency. In this case, the system

to support base currency 2

1.21 System should provide facility to

input whether the transaction is a

buy or sell deal and the relevant

currency code. 2

1.22 System should automatically display

the relevant rate and calculate the

details of the deal. 2

1.23 When deal is accepted by the teller,

system should print deal slip giving

relevant details. 2

1.24 When deal is accepted by the teller,

system should automatically update,

necessary accounts and stock

positions. 2

1.25 The current exchange rate displayed

should be amendable at the base

level as well as on a per transaction

basis, with superior authority 2

2 TRANSACTION PROCESSING

2.1 System should support at least the

following type of transactions as

defined for a particular accounts,

products, schemes in base as well

as any foreign currency viz.

2.1.1 Ø Cash 2

2.1.2 Ø Transfer / RTGS 2

2.1.3 Ø Clearing / RTGS 2

2.2 System should select fields for down

load of data from the database to

selected format e.g. DBF, Excel,

Word, text file etc. 2

2.3 On – line help across all modules

even for fields 2

2.4 Facility of messaging between

defined users. (e.g. chat etc.) 2

2.6 System should support off- line 2

transaction processing

2.7 System should have “Store” and

“Forward” mechanism to record off – 2

line transactions (for business

2.8 System should map all nodal / focal 2

branches to the link branch (i.e. the

2.9 System should maintain off - line

limits for branches and enforce the

same in the event of off - line mode. 2









Form 8

Teller Transactions Page 184 of 238

2.1 System should update information

on a periodic basis (as per

parameters set) from non - core

banking branches for payment of

divident , interest warrants, drafts on

agency arrangement etc. , to the

core banking application through the

nearest regional office / core

banking branch. Once upladed the 2



2.11 Maintaining a record for signatures 2

changed / cancelled for a particular

2.12 System should allow the user (Bank)

to define the different types of

transactions (cash, clearing, transfer

etc.) permissible for defined

activities (e.g. deposits /

withdrawals) along with

corresponding transaction limits for

particular accounts, products,

schemes in base as well as any

foreign currency. 2

2.13 System should define and

segregate transactions as:Codes to

be user definable e.g. e, s ETC.

N- normal 2

E – exceptional 2

S – System Generated 2

IB - Internet Banking 2

PB- Phone Banking 2

I- Inter branch 2

A – ATM etc. 2

2.14 Caution letter in case of cheque

returns and where no of dishonours

is more than 3 times

2.15 Facility of the system to define

account-wise, customer ID-wise

limits for ATM transactions, These

limits set at the account

level/customer ID-wise should over-

ride the global limits set 2

2.16 System should generate and store

reference numbers for defined 2

transaction types (parameterisable)

2.17 System should maintain rate tables,

conversion rates, cross currency

rates etc. at a global level for

different currencies as designate by

the bank 2

2.18 System should perform currency

and cross conversion 2

2.19 System should define limits for

transactions, based upon type of

transaction, branch size, nature of

transaction etc. 2









Form 8

Teller Transactions Page 185 of 238

2.2 Restrict / allow different transactions

based on the status of an account

e.g. dormant accounts etc. 2

2.2 System should define floor limits for

authorizing authorities 2

2.21 System should display all details of

the transaction at the time of

authorization of a particular

transaction with signature/

Photograph. 2

2.22 System should display all un-

authorized transaction and print a

report for the same. System should

only display all unauthorised entries

only pertaining to the individuals

user ID 2

2.23 System should authorize a single

transaction / batch of transactions 2

2.24 System should capture the details

(user ID) of the data entry personnel

(operator) as well as the authorizing

authority and print the same. 2

2.25 System should display appropriate

warning / error messages (as

defined) in the event of insufficient

balances, with the option to override

with appropriate authority 2

2.26 System should validate cheques /

any other instruments (e.g. DD / PO

etc.) for stop payments, already

encashed, date of instrument,

instrument number etc. before

effecting the transaction 2

2.27 System should validate holds, liens,

any special instruction before

effecting the transfer 2

2.28 The system should have the ability

to restrict the types of transactions

permitted for different type of

accounts. For example cash deposit

in local currency in NRE accounts

should not be allowed. 2

2.29 System should query on details of a

particular transaction by specifying

transaction number / type of

transaction/ date of transaction/

instrument number/ amount / a

combination of some inputs. 2

2.3 System should post transactions for

data received through soft copies in

the desired formats (e.g. floppy

uploads, FTP, downloads form sites

etc.) 2

2.31 System should define authorisaton

workflows for any type of transaction

base upon user defined parameters

e.g. amounts, types of transactions,

customer, branch etc. 2









Form 8

Teller Transactions Page 186 of 238

2.32 System should bypass the workflow

defined with appropriate

authorisation and the same should

be captured in the exceptional

reports and audit trails 2

2.33 System should automatically

generate advices in the desired

format for transactions effected in

the core banking system on non -

core banking branches System

should track, respond / reconcile all

such advices generated for non -

core banking branches 2

TOTAL 152









Form 8

Teller Transactions Page 187 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Lockers

1.1 System should provide 2

standardized document –processing

1.2 System should capture customer

details upon entering customer ID in

to locker register. 2

1.3 Linking the deposit account or

operative accounts for recovery rent 2

1.4 System should calculate the rent to

be charged based on defined rules

e.g type / size of the locker /

customer type 2

1.5 System should waive off rent /

charges at account level 2

1.6 System should specify +/- amounts

or percentage to be applied at

account level 2

1.7 Locker Operations – Time in , Time

Out, Access Log Register, Officer

handling the customer 2

1.8 Allow multiple nominations in locker 2

1.9 System should display locker

numbers available to be allotted to

the customer based on the type of

locker selected 2

1.10 System should display locker

operation instruction / signatures etc

on the entry of the locker number

and also due / outstanding charges 2

1.11 System should capture the system

time for the “time in” field and does

not allow to change. 2

1.12 Display last visit details on the entry

of locker number and dues /

charges outstanding if any 2

1.13 Option to maintain waiting list for

lockers and keep track of revised

waiting list after locker allotted on

first waiting person 2

1.14 System should attach remarks such

as ‘rent overdue’, ‘key lost reported’

to the lockers 2

1.15 System should capture ‘time out’

field at the time of locking the vault. 2

1.16 Trigger warning message , if locker

is being accessed after a gap of ‘X’

months 2

1.17 System should change the type of

lockers and net amount payable /

receivable from / to the customer

should be automatically displayed 2

1.18 Parameter to fix grace days for

payment of rent. Flexible Parameter. 2









Form 8

Lockers Page 188 of 238

1.19 System should debit directly to

customer a/c for rent 2

1.20 Automatic recalculation rent in case

of advance rent payment and refund

to customer 2

1.21 Generation of reminder letters in

case of overdue rent 2

1.22 Automatic adjustment of rent on

receipt of credit to the account ( any

where is it allowed) 2

1.23 Parameter to define penal charges /

commission 2

1.24 Option to waive the penal charges at 2

1.25 account level

1.26 After settling the dues only system

should allow to close 2

1.27 System should parameterize the

reason for closure of the locker 2

1.28 Update locker available list after the

closure 2

1.29 Facility to refund amount after

surrendering the locker – pro rata

rent and deposit amount 2

1.3 System should provide flagging of

the locker with ‘key lost’ tag 2

1.31 Ability capture the investigator ,

witness and authorizing bank official

details in the case of locker is break

open 2

1.32 System should calculate charges

for loss of locker keys as defined in

the parameter 2

1.33 System should allow change of key

and update the locker master details 2

1.34 System should define minimum

deposit to maintained based on the

location of the branch & rent also. 2

1.35 System should maintain history of

the lost keys 2

1.36 System should provide triggers for

alerting when locker for reported lost

key is accessed by the customer 2

1.37 System should interface with

electronic locker system 2

1.38 Reports on lockers issued, closed

along with reason, lockers broke

open rent dues, rent receivable ,

locker accessed, lockers

availSystem should be provided 2

1.39 Alert for authorized access – E/O/S

etc. – Display of Names. 2

1.4 Restrictions for allotment (Minors

etc.) 2

1.41 Waiting List for proposed locker

hirer. 2

1.42 Recording of changes of hirers –

addition / deletion. 2

1.43 History of Changes 2







Form 8

Lockers Page 189 of 238

1.44 Option to freeze operation. 2

1.45 Display of photos and signature 2

1.46 Locker No & Related Key register. 2

1.47 Password requirement. 2

1.48 Recording of Power of attorney

name etc. & alerts 2

1.49 System should send

acknowledgement of locker

nomination. Nomination should be in

favor of Individuals only. 2

1.5 Rejection of locker operation in case

rent is not paid. 2

1.51 Linking FD account to locker for rent

purpose. 2

1.52 Provision for noting the charges to

be recovered (Postal charges /letter

etc.) 2

1.53 Rent due intimation, one month in

advance of due date. Continuous

notices till rent is recovered at

periodical intervals. 2

1.54 Loss of key – Operation to be

freezed. 2

1.55 Provision /flexibility for changing key

number. 2

TOTAL 108









Form 8

Lockers Page 190 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Interest Calculation

1.1 System should calculate interest on

Simple, Compound and Equated

installment methods for various

schemes offered by the bank in

base currency or foreign currency. 2

1.2 System should display accrued

interest at all points of time. Facility

to apply accrued interest at any time

and also at the time of the closure of

account. 2

1.3 Facility to apply different rate to

special accounts (e.g. staff

accounts) 2

1.4 Interest application frequency

should be a parameterized value,

for any type of account or 2

1.5 Savings Interest on credit balance

should be calculated on the

minimum balance maintained

between a pre-defined period, both

days inclusive. 2

1.6 Interest should be credited to

account as per the parameterized

frequency. 2

1.7 Automatic application of overdraft

interest (debit interest) in case

account is overdrawn. Interest on

debit balance is calculated on daily

balance and applied either as per

the parameterized frequency or

when balance is in credit. 2

1.8 Calculation and application of debit

interest. No credit interest payment. 2

1.9 Debit interest should be calculated

on daily balance, but debited as per

parameterized frequency or when

balance is in credit, whichever is

earlier. 2

1.10 System should also provide

flexibility to waiver charge for an

individual transaction 2

1.11 System should allow user to define

whether service charges can be

debited below minimum balance 2

1.12 Allow the bank to define, modify,

delete, or inquire about the service

charge rates, fees and other

additional costs applicable to

specific types of transactions. 2

1.13 System should define add – on

rates (+ / -) at the account level

upon appropriate authorization 2









Form 8

Interest, Commission and Charges Page 191 of 238

1.14 System should define interest rates

for a particular account, product /

scheme as:

1.14.1 Ø Flat rate 2

1.14.2 Ø Percentage basis 2

1.14.3 Ø Slab (tiers) 2

1.14.4 Ø Combination of the above 2

1.14.5 Ø Defined addon rates (+/-) at

A/C level upon appropriate

authorisation. 2

1.15 System should define fixed or

floating interest rates associate with

a particular type of account, product

/ scheme 2

1.16 System should pick up rate of

interest on new accounts, as a

default value, based on:

1.16.1 Ø Benchmark rates 2

1.16.2 Ø Global interest rates / tables

for the particular account, 2

product / scheme 2

1.16.3 Ø Approved limit, 2

1.16.4 Ø Credit / risk rating, 2

1.16.5 Ø Type of account 2

1.16.6 Ø Security Provided etc. 2

1.16.7 Ø Any other benchmark rates as

specified by the bank 2

1.17 System should calculate interest

based on product type and user

definable parameters such as

1.17.1 Ø Minimum balance concept for

Savings account 2

1.17.2 Ø Cleared balance for current

accounts 2

1.18 Yearly, monthly, quarterly high -low

balances 2

1.19 Daily closing, average monthly,

quarterly, yearly closing balances

etc. 2

1.20 System should display the total

interest accrued for an account,

range of accounts or products as on

any particular date for accounting

purposes 2









Form 8

Interest, Commission and Charges Page 192 of 238

1.21 System should have ability for back

valuation and subsequent

adjustment of interests posted with

different interest rates. The system

should be able to recalculate the

interest with retrospective effect

(even though interest has been

already applied) and automatically

adjust the interest payments . i.e.

the system should compare the

current interest calculate and

compare the same with that applied

to the account at various intervals

and automatically credit / debit the

accounts with the differences. The

system should also be able to print

a report of the entries passed along

with the details of each transaction

2

along with the adjusted amounts.

1.22 System should automatically

generate a report for the interest

posted to a particular account,

product / scheme with the option of

printing the same at the branch level

/ central level as desired by the

Bank. 2

1.23 System should calculate & display

notional interest for user definable

accounts / schemes with credit

balances. 2

1.24

1.25 System should print Interest

Certificates for interest accrued /

charged / credited to accounts. The

interest application should not be

clubbed with month end / qtr end/

year end. 2

1.26

2 Commission & Charges

2.1 System should globally map defined

charges / commission types to type

of account, product, schemes

transaction, events etc. (user

definable) 2

2.2 There should be no limit on number

of charge types which can be

defined 2

2.3 Tightly integrated module across the

core banking package 2

2.4 System should define charges /

commission types as per the Bank’s

guidelines. The system should at

least support the following

2.4.1 Ø Minimum balance 2

2.4.2 Ø Cheque book fee 2

2.4.3 Ø Passbook fee 2

2.4.4 Ø Statement generation fee 2









Form 8

Interest, Commission and Charges Page 193 of 238

2.4.5 Ø Dormant charges 2

2.4.6 Ø Stop payment charges 2

2.4.7 Ø Cheque return charges 2

2.4.8 Ø Duplicate statement/pass book

charges 2

2.4.9 Ø Folio charges 2

2.4.10 Ø Withdrawal against cheques in

clearing 2

2.4.11 Ø Standing orders 2

2.4.12 Ø Non-execution of standing

orders 2

2.4.13 Ø No operations in PPF 2

2.4.14 accounts

Ø Locker rent 2

2.4.15 Ø DD/PO/TT/MT charges 2

2.4.16 Ø Adhoc charges e.g. courier 2

2.4.17 Ø Loss of locker keys 2

2.4.18 Ø Export Duty Draw Back 2

2.4.19 Ø Account closure 2

2.4.20 Ø LC/Bills/GU/UBD/Cheque

discount 2

2.4.21 Ø Correspondent bank charges,

commission etc 2

2.5 System should define the method of

calculation of charges and

commission for any account,

scheme, product viz.

2.5.1 Ø Flat rate 2

2.5.2 Ø Slab – wise / tiered rate 2

2.5.3 Ø Percentage 2

2.5.4 Ø Combination of the above (e.g.

fixed amount + certain percentage) 2

2.6 System should define the minimum

and maximum amount of charges /

commission for any account,

scheme, product. 2

2.7 System should nominate any

account / accounts held by a

customer (or a group) for debiting

charges / commission applicable

with appropriate authorization upon

request of the customer and System

should recover charges by way of

2.7.1 Ø Cash 2

2.7.2 Ø Transfer 2

2.7.3 Ø Cheque 2

2.7.4 Ø Combination. 2

2.8 System should display the

calculated applicable charge /

commission at the time of

transaction posting, authorization 2

2.9 System should define add – on

charges rates (+ / -) charges at

group level/Customer level/account

level upon appropriate authorization 2

2.10 System should accrue charges /

commission and apply after a

parameterisable time period 2









Form 8

Interest, Commission and Charges Page 194 of 238

2.11 System should generate the

separate report for each type of

charge / commission applied 2

2.12 System should automatically

recalculate and adjust charges,

commission in the event the

charges / commission rates are

changed with retrospective effect 2

2.13 System should store recoverable

charges in the event an account is

below minimum balance, in negative

/ above sanction limit 2

2.14 System should print a notional loss

report for a customer / group in the

event charges have been waived to

the particular accounts / special

rates have been specified for those

particular accounts vis – a – vis the

set global charges (as per Bank’s

policy) 2

2.15 System should identify transaction

as customer initiated, system

generated, transactions through

delivery channels etc. and

parameterise charges /

commissions as per the type of

transaction e.g a customer may be

charges in the instance customer

initiated withdrawal done at a

branch. 2

2.16 System should define sub - charges

/ commission and assign the same /

different method of calculation for

the same e.g. under demand issue

charges a different charge /

commission and method of

calculation for drafts issued by cash

and drafts issued by way of account

transfer 2

2.17 System should support discounted

charges / commissions on fixed rate

basis, percentage discounts or slab -

wise discounts based on defined

rules e.g. charges for a stop

payment Rs. 25/- per leaf but

charges for stopping an entire

cheque book of 10 leaves may be

Rs. 100/- only. 2

2.18 Interest Calculation Related

Features

2.19.1 1. Rates based on period/amount 2

2.19.2 2. Compounding Flexibility 2

2.19.3 3. Interest calculation (ad hoc run) 2

2.19.4 4. Interest Calculation (broken

period interest) 2

2.19.5 5. Interest Versions Facility 2

2.19.6 6. Interest on temporary Over

drawings 2







Form 8

Interest, Commission and Charges Page 195 of 238

2.19.7 7. Back Dated Interest Change

Calculations 2

2.19.8 8. Periodic Application of Interest 2

2.19.9 9. Penal/Overdraft Interest 2

2.20 Capable of automatically calculating

accrued interest up to the time of

closure/termination of accounts 2

2.21 Facility to calculate interest on a

daily basis and store it in a separate

field which can be used for

querying/printing purposes 2

2.22 Facility to re-calculate interest on

change in tenor of the deposit (e.g.

premature closure) 2

2.23 The system should not apply

interest in the event the deposit

account is closed/uplifted before the

minimum deposit period as

mentioned in the parameter file for

the particular scheme of deposit

(parameterisable) 2

2.24 Interest Calculation

2.25 System should have facility to

recalculate commission/ charges &

the effect the same in all accounts

as on a back date/current date. 2

2.26 System should calculate interest at

the time of account opening - for

calculation of tax liability and

arriving at the maturity value 2

2.27 Customisable interest rates and

interest calculation, depending on

deposit period, deposit type, etc. 2

2.28 Facility to apply different rates to

special accounts (e.g. staff deposits) 2

2.29 Interest normally calculated on

quarterly basis - both financial

quarter and quarter ending from

deposit date. System should also

be able to calculate interest for any

period defined by the end-user (e.g.

daily, quarterly, etc.) and as and

when required 2

2.30 Facility to support interest payments

for Recurring accounts. 2

2.31 Facility to adjust interest payments

in the event of pre/part payment

automatically for Recurring. 2

2.32 Facility to automatically adjust

Recurring table with changes in the

interest slabs taking into

consideration the effective dates for

such interest rate changes. 2

2.33 Interest adjustment should be

supported in case of backdated

transactions. 2









Form 8

Interest, Commission and Charges Page 196 of 238

2.34 Ability for back valuation and

subsequent adjustment of interest

posted with different interest rates. 2

2.35 Facility to charge customer for

statement sent by other than

ordinary post, duplicate statements,

and ad-hoc statements.

2.35.1 1. Flat fee charged against the

account balance 2

2.35.2 2. A percentage of transaction

amount 2

2.35.3 3. A factor of a percentage 2

2.35.4 4. Tiered flat fee 2

2.35.5 5. Tiered flat percentage with

minimum and maximum amount

charges 2

TOTAL 214









Form 8

Interest, Commission and Charges Page 197 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Issue of Cheque Books

1.1 System should specify the accounts

/ products for issue of cheque books

for defined number of cheque 2

1.2 System should maintain the stock

of cheque books at the branch /

central level 2

1.3 System should issue cheque

books at the branch / central level 2

1.4 System should generate requisition

for cheque books if a

parameterizable no of leaves are

consumed. 2

1.5 System should accept cheque

books with alpha series. 2

1.6 System should perform all validation

(stop payments, transaction entry

etc.) on the alpha series + cheque

number for cheques issued with

alpha series. 2

1.7 Recording of stock receipt and issue

details. 2

1.8 System should check for duplicate

cheque numbers at the time of stock

entry of cheque books in the 2

1.9 System should automatically update

the stock of cheque book upon

issue. 2

1.1 System should maintain safety

levels (parameterizable) of cheque

book stock. 2

1.11 System should generate warning

messages when the stock of cheque

books reaches the safety levels. 2

1.12 Parameterization of cheque book

charges which will be debited on

issue of the cheque books 2

1.13 System should waive cheque book

charges with parameterized level of

authority. 2

1.14 System should define charges as

per product (e.g. savings, current

etc.) 2

1.15 System should recover charges (as

defined in the charges and

commission module) from the same

customer account / any other

account specified by the customer

for charges recovery 2

1.16 System should view the status / fate

of a cheque leaf /range of cheques /

cheque books for a particular

account 2









Form 8

Cheque Book and SI Page 198 of 238

1.17 System should mark stop payment

of cheque numbers of a given range

for lost cheque book. 2

1.18 Check against the account opening

details for option cheque book

required or cheque book not

required while issuing the cheque

book 2

1.19 While issuing cheque book an

option should be provided to capture

alpha series for cheque book 2

1.2 System should issue cheques in

multiples of 10, 20, 25, 50, 100 etc. 2

1.21 Facility to allow withdrawal

transaction with withdrawal slips 2

1.21 System should query on customer

details / information based on

cheques number. 2

1.22 When high value customers are

printing their own cheque, system

should accept the series in the

system and update stock position in

respect of those accounts, with

System should check duplication of

the series 2

2 Stop / Revoke cheques

2.1 System should accept stop payment

instructions for any type of account

(Savings, Current, TOD, POD,

Foreign Currency etc.) in the

currencies offered by the bank 2

2.2 System should stop / revoke a

cheque / series of cheques 2

2.3 System should check whether the

cheque to be stopped is issued to

the account and whether the cheque

has already been paid. 2

2.4 System should generate a stop

payment reference number on

entering the stop payment 2

2.5 System should parameterize stop

payment charges according to

reason of stop payment, flat rate,

percentage etc. 2

2.6 System should apply stop charges

automatically upon authorisation of

the stop payment instruction. 2

2.7 System should parameterise the

reasons for stop payment instruction

(e.g. no funds, lost, cancelled etc,) 2

2.8 System should maintain stop

payment information such as stop

payment date, reason, (should be

based on defined codes in the

system), date and time stamp etc..

and generate reports accordingly 2









Form 8

Cheque Book and SI Page 199 of 238

2.9 System should generate a stop

payment advice for the customer

indicating cheque numbers and the

amount of stop payment charges

debited, stop payment reference

number etc. (for customers purpose)

from any branch connected to the

core banking 2

2.11 System should show alerts when the

stop cheque comes for processing 2

2.12 System should revoke a stop

payment instruction 2

2.13 System should generate letter of

confirmation upon receipt of stop

payment/revocation instruction from

the account holder 2

3 Reports

3.1 Cheque books issued to a particular

customer. 2

3.2 cheque books issued stock wise/

customer wise/ usage wise/ 2

3.3 Stop Cheques issued/ revoked in a

period. 2

4 Standing Instructions

4.1 System should capture Standing

Instructions details both in base

currency as well as in foreign

currency. The minimum details to be

captured are:

4.2.1 Ø Account number to be

debited/credited 2

4.2.2 Ø Amount 2

4.2.3 Ø Name of beneficiary 2

4.2.4 Ø Account number of beneficiary 2

4.2.5 Ø Frequency 2

4.2.6 Ø Start date for standing

Instructions 2

4.2.7 Ø Expiry date of Standing

Instructions 2

4.2.8 Ø Charges to be applied 2

4.2.9 Ø Currency 2

4.2 System should pick up the

commission, charges, postage etc.

from the parameter file 2

4.3 System should directly debit the

charges after the execution of

standing Instructions 2

4.4 Facility to at least interface with the

following solutions for setting up of

standing Instructions

4.4.1 Ø ATM 2

4.4.2 Ø Internet banking 2

4.4.3 Ø Mobile banking 2

4.4.4 Ø Phone-Banking 2

4.5 Facility to parameterize the

execution time of standing

Instructions









Form 8

Cheque Book and SI Page 200 of 238

4.5.1 Ø Beginning of the day 2

4.5.2 Ø End of the day 2

4.5.3 Ø User defined time frequency 2

4.5.4 Ø Manual 2

4.6 System should generate Branch

Advice /Pay Order/ Drafts or any

other mode of delivery as per the

format of the bank in the event the

beneficiaries account is in the other

bank or in the branch not connected

to the Core Banking Solution 2

4.7 System should retry for a

Parameterisable number of attempts 2

4.8 System should capture and print

any changes made to the Standing

Order instructions etc. 2

4.9 Facility to maintain the history of

amendments to the standing

Instructionss 2

4.1 System should generate

acknowledgement informing the

customer about receipt of standing

Instructions. 2

4.11 System should generate warning

letters at user definable time

intervals (paramerisable) e.g. after 2

retries generate a warning letter 2

4.12 System should automatically

generate a letter informing the

customer to make the payment

upon crossing the parameterisable

number of retries 2

4.13 Option to automatically adjust the

next payment date in the event the

customer has made the payment

through any other mode of payment. 2

4.14 Option to recover (all / maximum

recoverable) dues for all rejected /

failed standing Instructions when

funds are sufficient in the account /

next payment dates have not been

adjusted 2

4.15 System should reject execution for

certain pre defined reasons e.g.

insufficient funds etc 2

4.16 System should generate report of

executed / non-executed standing

Instructions on a particular day or

period. 2

4.17 System should display all standing

Instructionss rejected by the system

and permit passing the same upon

appropriate authorsation 2

4.18 System should generate a report for

all such standing Instructions

rejected by the system but passed

with higher level of authority. 2









Form 8

Cheque Book and SI Page 201 of 238

4.19 System should automatically cancel

the standing Instructions upon

exceeding a user definable time

interval (e.g.. standing Instructions

not executed for x consequent

months) / closure of account

etc.(parameterisable) 2

4.2 System should check for existence

of any standing Instructionss for a

particular customer ID before

account closure 2

4.21 System should generate letters to

customers against non – execution

and cancellation of Standing

Instructions 2

4.22 System should mark a Standing

Instruction / Instructions for

compulsory execution (even though

insufficient funds / over drawing)

and generate appropriate reports for

the same 2

4.23 Option to set priority of executing

the standing Instructions in case of

shortage of funds. The system

should be capable of processing the

standing Instructions in the

sequence of priority 2

4.24 Facility to verify the account number

and the account status of the

beneficiary, if the beneficiary

maintains the account at the bank 2

4.25 If beneficiary account is one of the

Bank’s accounts connected online

to the same application, that

account should be credited online

on execution of standing 2

4.26 System should either be System

should view or print any standing

Instructions by giving the account

number or name 2

4.27 Option to delete / cancel Standing

Instructions with proper 2

4.28 Option to execute the standing

Instructions with temporary over

draft with proper authorization 2

4.29 System should reactivate a

cancelled standing Instructions upon

appropriate authorisation 2

4.3 System should transfer user

definable amounts beyond a defined

limit in a particular account (user

definable ) to other accounts,

products / schemes at user

definable time periods / intervals as

mentioned in the parameter for the

particular account 2









Form 8

Cheque Book and SI Page 202 of 238

4.31 System should support generation

of desired message formats for inter

bank transactions to be passed on

to the RTGS / respective systems

for direct inter bank transfers / 2

4.32 Intimation to customer that last SI

executed if tenor based. Indicate

maturity date and seek instructions 2

4.33 On closure of base account, system

should check for any SI is not

pending for that account for

credit/debit. 2

5 Reports

5.1 List of standing Instructions entered

during the day 2

5.2 List of standing Instructions

executed during the day 2

5.3 List of standing instructions

amended during the day 2

5.4 List of standing instructions deleted /

cancelled during the day 2

5.5 List of standing Instructions not

executed / rejected along with the

reason for non- execution / rejection

of the same 2

5.6 Exception report during standing

Instructions execution 2

5.7 Standing Instructions expired 2

5.8 Standing Instructions transferred to

Ineffective standing Instructions 2

5.9 Standing Instructions status

transferred from ineffective to cancel 2

5.1 Accounts debited and credited in

other branches along with complete

transaction details in the event of

inter branch transactions 2

5.11 System should generate inter

branch transaction report with detail

like : account name, account

number, nature of transaction,

transaction code, amount, name of

maker, name authorizer, time etc., 2

TOTAL 192









Form 8

Cheque Book and SI Page 203 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Account Opening

1.1 Facilities to open account either by

cash, cheque or transfer from

another branch with parameterized

amount. (Minimum amt etc.) 2

1.2 Automatic generation of account no.

at the time of opening an account. 2

1.3 A customer can have various

accounts, at many branches, in

different currencies, of different

types, and they can be accessed by

a unique customer number. 2

1.4 Up to a maximum of six (6)

signatories for Joint Accounts. 2

1.5 Grouping of accounts for offsetting

balances and calculating interests

and charges. 2

1.6 Provision for User Defined alerts like

“New Account” etc. 2

1.7 Facility to set the maximum deposit

amount permitted for minor

accounts, and validate the same at

transaction level 2

2 Account closing

2.1 Allow online closing of account upon

request from customer by law or

discretion of the bank 2

2.2 Before closing provide check for

atleast the following

2.2.1 1. Unused cheque leaves are

recovered 2

2.2.2 2. Lien is reversed 2

2.2.3 3. Hold amount 2

2.2.4 4. Standing instructions cancelled 2

2.2.5 5. Outstanding balances in any

other accounts 2

2.2.6 6. Lockers 2

2.2.7 7. Effect of cheques sent for

clearing has been given 2

2.2.8 8. Transactions in a pipeline 2

2.2.9 9. Debit balance in related accounts 2

2.2.10 10.All signatories have given

approval for closing account 2

2.2.11 11. All limits /facilities relating to the

account granted to the customer are

closed 2

2.2.12 12. ATM card /debit card issued flag

disabled 2

2.2.13 13. All other facilities cancelled e.g.

internet banking tele banking ATM/

Debit Cards etc 2









Form 8

General Banking Page 204 of 238

2.3 Facility to parameterise account

closure charges( flat amount,

percentage) in the event the

account is closed before a stipulated

time period as mentioned in the

product definition 2

2.4 Facility to maintain data

(static/transaction) for all closed

accounts and generate a statement

for the same if required. 2

2.5 Facility to parameterize the reasons

for closure (e.g. dissatisfaction,

moving of residence etc.) 2

2.6 Advance against Clearing Facility 2

2.7 Settings of different passbook

printout for different account

products. 2

2.8 Multiple accounts may sweep into or

out of a simple target account. 2

3 Currency Management

3.1 The Core Banking software should

have a module to cater to head

office currency maintenance (notes /

coins) in base currency / any other

foreign currency. 2

3.2 The system should be capable of

recording the details of currency

(notes / coins) in base currency /

any other foreign currency at the

cash vault denomination wise. 2

3.3 This system should be capable to

maintain the details of all the

currencies (notes / coins), sent to

branches denomination wise. 2

3.4 The system should maintain the

maximum cash retention limits at

branches, for all currencies (amount

and currency parameterisable) 2

3.5 The system should be capable to

update the stock of currencies

(notes / coins) dispatched / received

from the branches / departments

upon authorisation of currency

details entry transaction. 2

3.6 The system should generate

appropriate warning messages

informing the branches/

departments and also the currency

chest about excess / shortage of

cash depending upon the cash

retention parameter branch - wise. 2

3.7 System should be able to print a

cash requisition/surplus form

depending on the requirement of the

branch. 2









Form 8

General Banking Page 205 of 238

3.8 The system should be able to

generate a unique reference

number (user definable) for each

cash requisition / surplus form

printed at the branches. The

reference number so generated by

the system has to be printed on the

cash requisition / surplus form. 2

4 Inquiries

4.1 Transaction history inquiries/

instrument search/amount

search/trns of a particular date. 2

4.2 System should give the position of

charges by account on Department/

Branch/ Bank level . 2

5 Interfaces

5.1 Summary distribution of

income/charges of various delivery

channels & facility to interface with

all other Banking Application eg.

CIF, Treasury, RTGS, Delivery

Channels. 2

5.2 Facility to consolidate accounts into

5.2.1 a) branch groups 2

5.2.2 b) department groups 2

5.2.3 c) product groups 2

6 Bank Product Supported

6.1 The system should allow creation

and definition of banking products to

be controlled and effected by the

authorized business user. Products

should be defined. 2

7 SAVING BANK specific queries

7.1 Specify restrictions on no. of

withdrawals for SB A/c. and track

no. of withdrawals on monthly/

quarterly basis. Flexibility to levy or

waive charge if withdrawals exceed

restricted amount. 2

7.2 Accrue interest based on ledger

balance or negative balance 2

8 Liability Product

8.1 NR/FCNR Accounts Facility and

generating necessary reports 2

8.2 Integration with Forex, Remittances

and other modules 2

8.3 System should open FCNR-B

Deposit. 2

8.4 System should open NRE/NRO A/c 2

8.5 The system should not allow Indian

currency operation in NRE a/c 2

8.6 Extended Limit Facility in Current

A/c 2

9 SISHUMANGAL YOJNA









Form 8

General Banking Page 206 of 238

9.1 System should be capable of

handling KYC requirements-who

can open the a/c e.g. Indian

resident in age of 1 year to 15 years

& mature at 21 years age. 2

9.2 MONTHLY INCOME PLAN

9.2.1 1. System to parameterize

minimum amount & maximum

period. 2

9.2.2 2. The system should have the

facility to calculate discounted rate

of interest for monthly Income. 2

9.3 RECCURING DEPOSIT

9.4 System to parameterize the period

and also 2

9.5 Payment criteria on maturity

including penal charges clause. 2

9.6 System should be able to handle

delayed payment of installment and

also impose a penalty in case of

delayed payment. 2

9.7 System should be able to calculate

penal interest in case the recurring

deposit is closed prematurely. 2

9.8 The system should have the System

should handle transfers of RD

account from non-CBS branches &

interest part & principal should be

dealt accordingly. 2

9.9 AL – AYUSMAN BIMA YOJNA

9.10 System should parameterize age

criteria and calculation of premium

based on date of commencement. 2

9.11 Marking of subscribing of the

scheme at the account opening

level. 2

9.12 The system should have the System

should auto-renew the scheme as

per customer’s requirements. 2

10 CURRENT PLUS Scheme

10.1 System should provide sweep

facility to current account or any

other product of the bank. The

designated amount should be

transferred to an interest fetching

account for a designated period

which could be swapped back to

main account on need basis. 2

11 Flexi-Fix Product

11.1 The whole deposit to be held in

units of user definable amount. 2

11.2 Every unit to be held as a separate

account on the system. The

account numbers for each unit

should be auto generated by the 2

11.3 Passbook is to be generated for

entire deposit amount, instead of

one receipt for each unit. 2







Form 8

General Banking Page 207 of 238

11.4 For premature withdrawal, only

requisite number of units required to

honor the amount to be broken.

The balance will earn the original

rate of interest. 2

11.5 System should apply penal rate for

units withdrawn and recalculate

interest amount 2

11.6 System should allow any no. of units

to be broken at a time, without

breaking the entire deposit. The

units to be broken should be chosen

by the user. 2

11.7 Payment to be made for principal

amount of units withdrawn and

interest earned on same. 2

11.8 Facility to allot many instruments for

a single deposit and printing of

multiple receipts for a single account 2

12 Miscellaneous

12.1 Breakdown of single deposit amount

to different bills payments and fund

transfers 2

12.2 Automatically generate Credit

Memo/Debit Memo request form for

approval. 2

13 Minimum Balance - SB or Current

13.1 Define minimum balance to be

maintained on each type of account

. The minimum balance

requirement may vary between

customer's accounts having

checkbook and those not having

checkbook. Must be a provision of 2

14 Reports

14.1 Report continue or recovery option

in case of Interrupted Printing. 2

14.2 Spooled Printing of Reports. 2

14.3 Generation of letter of thanks to

customer / introducer (user

definable) after opening of account 2

14.4 Deposit Receipt printing/Pre-printed

format to be available on opening

and rollover 2

14.5 Support for user definable layout of

Deposit Receipt 2

14.6 The system should be able to

generate report as per bank’s

requirements. And also there should

be a provision to select some fields

and perform statistical calculations

on those chosen fields. Also there

should be a provision to club

accounts on the basis of customer

ID & calculate all the income/

business generated by him. 2

14.7 generating letter confirming receipt

of cheque book by account holder 2







Form 8

General Banking Page 208 of 238

14.8 Automatic generation of customer’s

statements at defined frequency for

each account. 2

14.9 To send statement of accounts by

way of email. 2

14.10 Choice to customers of

passbook/statement. This choice

can be for each account of a single

customer. 2

14.11 System should print a report as on a

particular date / range of dates for

all transactions/ modification etc. at

a particular branch (say x branch)

for transaction done by other

branches on that particular branch

(x branch), and all transactions done

by the particular branch (x branch)

on other branches along with all

details of the transactions including

inputer details, authrisation details,

referred by details (in the event of

higher authrisation requirements),

narration, special notes etc. 2

14.12 System should schedule reports for

printing I.e. day-end, month-end,

year end etc. 2

14.13 Specification of form size while

printing statements of accounts. 2

15 Dormancy Processing

15.1 Feasibility of generating a report

with an agewise analysis of dormant

and inoperative accounts. 2

15.2 Automatically convert accounts to

dormant / inoperative depending

upon user defined parameters.

Generate an advice and Dormant /

inoperative Account Report and vice

– versa. 2

15.3 Define the transactions permitted in

dormant accounts 2

15.4 Restrict viewing signatures of

dormant / inoperative accounts to

the data entry operator 2

15.5 System should automatically group

all dormant / inoperative accounting

and the balances of these accounts

under the designated GL head.

Further the system should also

support reclassificaton and updation

of the GL heads once the account is

reclassified 2

16 Back Dating

16.1 Back-dating Transaction Process 2

16.2 Back Value interest and Fees

Calculation. 2

17 Term Deposits









Form 8

General Banking Page 209 of 238

17.1 Auto renewal of deposits on maturity

if requested by the customer. (Only

Principal/ Only Interest/ any other

amount specified by the custoer.) 2

17.2 Alert messages should be displayed

at the time of closure if a duplicate

receipt has been issued so that only

duplicate receipt is accepted. 2

17.3 System should trigger an alert if

loan against FD is outstanding at

the time of maturity / premature

closure of FD. Loan amount to be

adjusted against maturity proceeds

before making payment. System

should not allow to make the

payment if loan against FD is 2

17.4 Support payment of principal into

one or more account, (cash or

cheque) 2

17.5 New rate of interest to be applied

from date of renewal. Penal interest

to be waived if period of renewal

exceeds left over period from

previous deposit. 2

17.6 Principal given to the customer on

maturity, but interest credited

monthly to customer account. 2

17.7 Facility to define a minimum period

before which if the deposit is

withdrawn, the customer will not be

entitled for any interest. 2

17.8 Check for holds, liens and special

instructions before allowing

premature withdrawal. 2

17.9 Support payment of interest into one

or more account, (cash or cheque).

these accounts can be different from

the accounts for principal payment 2

17.10 System should support automatic

rollover as per the terms of standing

instructions (e.g. Interest &

Principal, interest only, interest and

part of principal, principal only, etc.) 2

If no settlement instructions given by

depositor, system should support

rollover on the existing terms and

conditions or allow transfer to

overdue account. 2

17.11 There should be a facility for

parameterising penal charges for

premature withdrawals. 2

17.12 System should be capable of

calculating and displaying the

maturity amount along with

deductible TDS amount if any as

defined in the TDS module 2









Form 8

General Banking Page 210 of 238

17.13 Facility to renew a deposit within a

specified grace period (as per

parameter set) from its maturity

date, and calculate overdue interest

for the overdue period at user-

defined simple/compound (as per

parameter set) rates as specified

(as per parameter set). 2

17.14 At time of opening, Face Value,

Deposit Value (discounted value)

and maturity date to be calculated,

based on principal of discounting

eg. MIP, QIP 2

17.15 The formula for discounting and

calculating the Face value should be

user-definable and modifiable 2

17.16 System should open term deposit

accounts with zero rate of interest 2

17.17 Interface to loan module to avail

loan against the deposit. 2

17.18 Facility to stop closure of deposit

account if loan is outstanding. User

definable alert or override support. 2

17.19 Facility to attach fixed deposits to

other loans by the account manager

at any time during loan period or

deposit period 2

17.20 System should trigger an alert if

loan against FD is outstanding at

the time of maturity / premature

closure of FD. Loan amount to be

adjusted against maturity proceeds

before making payment. System

should not allow to make the

payment if loan against FD is 2

17.21 System should provide facility to

Capture the following

renewals/settlement instructions and

renew/settle Deposit Account as per

instruction automatically on maturity

date. 2

17.22 System should provide facility to

store minimum deposit amount and

minimum and maximum time period,

for each type of deposit 2

17.23 At time of opening, maturity date

and maturity value should be

calculated, with and without taking

into account tax to be paid, where 2

17.24 Facility to maintain and view at

transaction time, the operating

instructions for an account 2

17.25 Support for marking multiple liens

on term deposit account 2

18 Know you Customer









Form 8

General Banking Page 211 of 238

18.1 If cheque is submitted for opening

deposit account, account should be

opened only after cheque is cleared

(value dating of transaction) 2

18.2 facility to open Deposit with a value

date. 2

18.3 System should restrict the extent for

period allowed for back value 2

18.4 System should restrict introduction

from accounts opened less than 12

months 2

18.5 System should block accounts

where letter of thanks is returned

undelivered 2

18.6 System should restrict type of

operation in the account till

acknowledgement of address

confirmation is received 2

18.7 System should give choice account

number as per demand of customer 2

18.8 Pop ups for new messages / alerts /

schemes /also for terrorist

organizations. 2

19 Foreign Currency Accounts

19.1 Support all the features mentioned

above, if the account is maintained

in any foreign currency. 2

20 Tax deducted at source

20.1 Calculate Tax-Deduction at Source

and automatically adjust account 2

20.2 Interest calculation for TDS purpose

should include all term deposit

accounts held by the customer at

the branch. User should be able to

define whether a type of deposit is

to be considered for TDS calculation

or not. 2

20.3 Tax Deduction to be parameterise to

include at time of credit of the

account/ time of payment, whichever

is earlier. 2

20.4 System should first credit the

interest account with the full interest

and debit the TDS account with the

tax amount, rather than crediting the

new amount to the interest account. 2

20.5 Facility of the system to display and

print the projected Tax deducted

amount at the opening of deposit.

The system should consider all the

deposit accounts / Term deposits

held by the customer with the

branch / bank. 2

20.6 Withholding tax adjustments. 2

21 SYSTEM REQUIREMENTS









Form 8

General Banking Page 212 of 238

21.1 System should support commit or

roll back (in the event the relevant

data bases could not be updated

due to any reason) 2

21.2 System should automatically /

manually purge data (static /

dynamic) at user definable intervals

(e.g. end of every month, specific

date, year end etc.) based on user

definable criteria (parameterisable)

(e.g. all data (static & dynamic for a

given date range, only transactions

between date ranges, closed

accounts, accounts with 0 balance

etc.). By default no data should be

purged 2

21.3 System should archive data base on

user definable parameter (e.g. from

and to dates for transactions, closed

accounts, accounts with zero

balances)

2

21.4 System should confirm with ISO

messaging standards (e.g. ISO

8583, XFS protocol). 2

21.5 User definable screens for data

capture 2

21.6 System should define fields as

mandatory / non – mandatory in the

system for data capture (These

fields are apart from fields which are

key fields used internally by the

application for processing purposes)



2

21.7 System should highlight mandatory

fields in a different color. 2

21.8 System should support user

definable date and amount formats 2

21.9 Facility for adding new fields for

additional data capture as required

by the Bank in each module,

product / scheme

2

21.10 System should integrate / interface

with all the delivery channels in such

a way that at any point all the

channels, including the Core

Banking Host show the same status,

for example the balance shown on

internet banking should be same as

that shown on the ATM and that in

the Branch at the any particular

point in time. 2

21.11 System should mark reports as

mandetory and non mandetory for

prinitng at the branch / business

units 2









Form 8

General Banking Page 213 of 238

21.12 System should schedule reports for

printing I.e. day-end, month-end,

year end etc. 2

21.13 System should maintain a calender

file for all branchs, regions and head

office. Further the system should

have the capabilty to define holidays

for each branch / region

2

TOTAL 294









Form 8

General Banking Page 214 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 General features

1.1 System should support multiple

channles-Internet, mobile etc and

should support interface with

dispariate host systems and third

party applications 2

1.2 The system should have at least the

following modules:

1.3 Accounts and transfers 2

1.4 Payments 2

1.5 Collections 2

1.6 Liquidity management 2

1.7 Reconciliation 2

1.8 EIPP-electronic invoice presentment

and payment

1.9 Reports 2

1.10 Alerts and Messaging

2 Accounts and transfers

2.1 System should provide account

information and basis transfer

facilities for moving funds: 2

2.2 Checking accounts 2

2.3 Loan accounts 2

2.4 Deposit accounts 2

2.5 Funds transfers 2

2.6 Multi currency support 2

2.7 Loan and Deposit calculators 2

2.8 Basic alerts 2

2.9 Reports 2

2.10 System should support one-to

many, many-to one, one to one

account transfers



3 Payments

3.1 System should support interbank,

intrabank, domestic and

international payments 2

3.2 ACH, BACS, CHAPS 2

3.3 Local transfers 2

3.4 International wire transfer 2

3.5 Bulk transfers, bulk payments 2

3.6 Counterparty maintainence 2

3.7 Positive pay and controlled

disbursements 2

3.8 Debit transfers 2

3.9 Payment alerts

3.10 Standing Instructions

3.11 Payment framework to support new

payment systems 2

3.12 System should support initiation,

verification and authorization of all

payment activities from any location









Form 8

Cash Management Page 215 of 238

3.13 System should support cheque

inquiry with sophisticated image

viewing

3.14 System should support filter and

sorting options

3.15 System should support stop

payment for a single item or a

complete range

4 Collections

4.1 System should provide the

infrastructure required to manage

collections: 2

4.2 Direct debit mandate maintainence 2

4.3 Local collections 2

4.4 Forecign collections 2

4.5 Bulk collections 2

4.6 Collection alerts 2

4.7 Collection reports

4.8 Lockbox interface 2

5 Liquidity management

5.1 The system should support:

5.2 Notional pooling 2

5.3 Pooling with interest adjustment

5.4 Account sweeping 2

5.5 Account aggregation 2

6 Reconciliation Reporting 2

6.1 The system should support

reconciliation of the payables and

receivables book of a corporate with

the accounting book of the Bank

6.2 Payable reconciliation 2

6.3 Receivable reconciliation

6.4 Generation and viewing of bank

reconciliation statement 2

7 EIPP-electronic invoice

presentment and payment 2

7.1 System should enable the bank to

offer invoice and bill payment

functionalities to end customers

7.2 Billing company registration 2

7.3 Support for closed user groups of

payers-payee 2

7.4 Bill payment 2

7.5 Information and reporting 2

7.6 Billing company reports 2

7.7 Bill database 2

7.8 EIPP alerts

8 Alerts and Messaging 2

8.1 System should provide two way

multi channel(SMS, Email, fax,

WAP) alerts

8.2 System should have capability of

generating event based alerts from

any of the transaction processing

systems 2

9 Infrastructure 2









Form 8

Cash Management Page 216 of 238

9.1 System should provide flexible

infrastructure management ability :

9.2 Internal secured mail 2

9.3 Imaging 2

9.4 Straight through processing

interface 2

9.5 Multi lingual infrastructure 2

9.6 Relationship manager functionality 2

9.7 File upload infrastructure

10 System should support: 2

10.1 Comprehensive auditing-System

should maintain complete audit trail

of all transactions and adjustments 2

10.2 account level access control 2

10.3 Multi level approval workflow

10.4 setting Transaction limits 2

10.5 parameterization

10.6 System should provide extensive

inquiry capabilities, including drill

downs to the source of original

transactions and instant information 2

11 Information and reporting 2

11.1 balance and transaction detail

information 2

11.2 Current day,r day and historical

information reporting 2

11.3 Cash forecasting and reconciliation

tools 2

11.4 Special reporting features,

customized reports, multi bank,

multi currency , data exchange

reporting, batch and real time 2

TOTAL 126









Form 8

Cash Management Page 217 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor Comments

1 Inspection & Audit

1.1 System should provide Inspection & Audit Module 2

2 Ability to record/provide at least the following

information for synopsis of Inspection report of the

branch as on date of inspection :

2.1 Branch code & name, district, state, zone/region date of 2

opening, Name of Br. Mgr, staff strength cadre wise

2.2 Date of inspection, Name of inspecting officer, period of 2

inspection

2.3 No. of irregularities - Advances & Routine (Major & 2

Minor in both)

2.4 Rating of the branch on various parameters like 2

profitability, deposits, advances,house keeping,

rectification of Irregularities,Image of branch etc.

2.5 Overall rating with % and grade 2

2.6 Deposits & Advances with classification as on date of 2

inspection , as on date of Br. Mgr took charge and as on

date of last 2 financial years.

2.7 Deposit & advances growth - satisfactory/Not 2

satisfactory

2.8 Documentation status - satisfactory/Not satisfactory 2

2.9 Clean/unsecured/unauthorised advances - Dr. balance 2

in SB/CT a/cs - No. of a/cs and total amount.

2.10 Time barred a/cs - no. & amount 2

2.11 NPA postion ( a/cs and amount) as on last 2 financial 2

years .

2.12 Classification of assets (STD/SST/D/L) as on date of 2

last 2 fin. Years

2.13 DICGC/ECGC claims lodged since last inspecion - a/cs 2

& amount

2.14 Suit filed a/cs & amount (including decreed a/cs) 2

2.15 Decreed a/cs & amount (including E.P. filed cases) 2

2.16 E.P. filed cases - a/cs & amount 2

2.17 RC issued cases - a/cs & amount 2

2.18 Working results as on date of last 3 fin.years - Income, 2

Expenditure, Profit/Loss etc.

2.19 Rectificaion of irregualrities of last inspection - % (within 2

3/6 months & uptodate)

2.20 Postion of Balancing of Books of different ledgers -Up- 2

to-date/In-arrear. If in arrear - no. of ledgers, months,

lock-up difference etc. in each type of personal/im-

personal ledgers

2.21 O/s balance in flabby accounts like Draft Ex-advice, 2

POB, ROB, Debit Note receivable, Bills remitted, sundry

creditors , Banker's cheqe, suspense etc.

2.22 Cash retentiion limit and cash position, quarterly avg. of 2

cash bal. since last inspection

2.23 Reconciliation of clearing a/c and a/c with other banks 2

e.g. SBI/RBI

2.24 Position of arrear locker rent - no. of lockers, amount of 2

arrear rent

2.25 Daily compairing - Done/Not done 2

2.26 Maintenance of important registers - Done/Not done 2

2.27 Submission of various returns - satisfacory/Not 2

satisfactory

2.28 Customer service - satisfactory / not satisfactory 2









Form 8

Inspection Page 218 of 238

2.29 Fraud/Forgery/Dacoity- if any give details 2

2.30 Brief summary of adverse features in routine matters in 2

some memo field

3 Inspection process

3.1 Provision to view details (such as terms & condition of 2

sanction, security documents, sanction limit, intt. Rate

etc.) of all loan a/cs one by one in the prescribed order

like sanction authority-wise/scheme-wise etc.

3.2 System should have provision to record inspector's 2

comment on irregularity in some memo field attached

with the respective a/c and the same should be flashed

or displayed through popup at each occasion whenever

that a/c is accessed without effecting the transaction

made in the a/c.

3.3 Provision for recording Manager's comment for 2

rectification of irregularity in the above field.

3.4 While on line reviewing the Manager' comment on 2

rectification of irregularity a/c wise the controlling office

should have provision to mark in the said field as

rectified. If not treated as rectified, then controlling

office's comment should be recorded there.

3.5 System should not flash the irregularity any more if it 2

marked as rectified by controlling office.

3.6 List of pending irregualrities, a/c wise, with comments 2

should be made available to

inspector/manager/controlling office including H.O.

whenever required.

3.7 Provision for defining various formats (such as Jilani's 2

committee, questionaire on securities, customer service

etc.), as per Bank's requirement, related to inspection of

the branch where inspector can record/mark his

observation.

4 At least following user definable reports (based on

specified selection criteria e.g. selective branch/all

branches, date range, product/scheme code,

min./max. amount etc.) should be made available

directly thru some additional menu (user definable)

to help in carrying out the inspection & audit of the

branch :

4.1 Ability to print/view synopsis of inspecion report as on 2

particular inspection date giving comparitive of previous

& present inspection . The report should be prepared

on selected data (user definable).

4.2 Exeptional transaction list 2

4.3 Debit balances in SB/CT accounts. 2

4.4 Clean Over draft with age (parameterisable) 2

4.5 Age-wise (parameterisable) outstanding in various 2

flabby a/cs such as suspense, sundry, POB etc.

4.6 List fo activities performed in dormat/inoperative a/cs. 2

4.7 Large (parameterisable) deposits/withdrawls in new a/cs 2





4.8 Overdrawing above limits 2

4.9 Delegation of powers to each user for different type of 2

transactions such as cash, transfer, clearing etc.

4.10 List of active user ID's 2

4.11 List of frequency of password changes (password 2

change history)

4.12 List of deactivated user ID's 2

4.13 Un-reconciled entries/GL heads 2









Form 8

Inspection Page 219 of 238

4.14 Signatures & photos not captured in the system 2

4.15 Initital a/c opening by way of clearing/transfer 2

4.16 Balance of security stationery for physical verification 2

4.17 Debit transaction in income heads such as commission, 2

exchange, etc.

4.18 Discount / waivers given to custormers, if any 2

4.19 Revoking of lien having o/s balance in linked a/cs at the 2

time of revoking

4.20 List of npa a/cs having details like NPA date, security 2

details, leg. Section balanace, record sanction balance,

recovery since the date of NPA etc.

4.21 List of w/o acccounts - prudential, compromised, not 2

recoverable - and recovery made if w/o a/cs, if any

4.22 No. of times (parameterisable) a customer has defaulted 2

in payment of interest/principal/charges

4.23 List of a/cs having overdue instalments with no. of 2

instalments & amount

4.24 Details of the linked a/cs of the NPA party/defaulting 2

borrower where the said customer is either a joint holder

or guarantor

4.25 Loan a/cs where intt. To be applied flag is marked as 2

'N', if any

4.26 Deposit a/cs where differential intt. Rate/special intt. 2

Rate has been provided

4.27 Loan a/cs where discounted intt. Rate has been 2

provided

4.28 Cash withdrawls in CC a/cs 2

4.29 No.(parameterisable) of cheque return for a particular 2

customer along with his loan a/c details e.g. no. of loan

accounts, sanction limit, o/s balance, no. of times

default in payment etc.

4.30 No.(parameterisable) of guarantees invoked for a 2

particular customer along with loan a/c details as

mentioned above

4.31 A/cs where TDS flag is marked as 'N', if any 2

4.32 Cash retentiion limit vs cash position, 2

fortnightly/monthly/quarterly avg. of cash bal. since last

inspection

4.33 Loan receipt receipt / disposal register - full and where 2

branch exceeded the specified time frame for

processing loan application

4.34 Documents/securities expired but limit continued 2

4.35 Isurance expired a/cs 2

4.36 Stock statement non - submission report 2

4.37 A/c statements of some desired a/cs (on given specified 2

criteria) for sample checking of intt. Application,

charges application, penal intt. Etc.

4.38 Sanction limit more than the value of security, if any 2

4.39 Report on unutilised limits beyond x (parameterised) 2

period - so that commitment charges etc. may be

applied or to check whether the same has been applied

4.40 Amount of foreign currency held in the branch along 2

with the no. of days held (i.e. the date received till the

date sold to the local money exchangers)

4.41 Inter branch transaction above a given amount 2

4.42 Age-wise list of un-reconcilied transactions 2

4.43 ALM reports 2

4.44 A/cs opened and closed within a specified period with 2

details of transactions









Form 8

Inspection Page 220 of 238

4.45 Commission/charges changedwaived by the user, if 2

any, giving details of the a/cs for which the same has

been changed/waived

4.46 Un-reconciled DDs/BC's above x (parameterisable) no. 2

of days

4.47 Log of any transaction in which inspector/auditor 2

observes some irregularity

4.48 B/S & P/L items - comparitive list for last 3 financial 2

years or given dates

4.49 Details of large borrowal a/cs 2

4.50 Cost of deposit & yield on advances for last 3 fin. Year 2

4.51 Business & profit per employee for last 3 fin . Years 2

4.52 DDs/Bancker's Cheque issued agianst cash deposit of 2

Rs. 50000 or more (parameterisable) without PAN

number

4.53 List of a/cs opened without valid introduction 2

4.54 Bio-data of the stafff of the branch through interface 2

with HRMS

4.55 Ledgers of flabby accounts/impressional a/cs 2

4.56 DCB register 2

4.57 Target vs achievement of various schemes in last 3 fin. 2

Years

4.58 Age-wise overdue export bills 2

TOTAL 192









Form 8

Inspection Page 221 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor

Comments

1 Data Ingestion

1.1 Support for sourcing transactional and 2

customer data from various

banking/payment systems for

ingestion into the AML system

1.2 Support for online data exchange 2

1.3 Support for selective on-line checks as 2

desired by the bank and trigers e.g.

transaction blocking

1.4 Support for the data ingestion in 2

following formats:

- CSV

- XML

- Message Queues

1.5 Support for data cleansing and 2

validation features

2 Watchlists

2.1 List Management 2

Support for list maganagement (e.g.

automated loading, automated

updates, real-time updates, user

maintainability)?

2.2 Support for periodic scanning of 2

account/customer database against

watch lists

2.3 Support for name matching during the 2

account opening process, i.e. upon

opening of a new account and data

transfer to the AML solution, will the

latter immediately flag a match

2.4 Support for advanced search 2

techniques like Phonetic and Fuzzy

Logic

2.5 Support for exclusions of names to 2

avoid multiple false hits



2.6 Support to accept names defined by 2

users into a watch list for more

detailed scrutiny and store the names

for prospective searches?

2.7 Support for prebuilt watch lists lists 2

with capability to scan specific watch

lists



3 KYC

3.1 Support for replication of selective 2

customer data based on the

requirements of the systems for

survelance and monitoring

3.2 The system should validate the CIF 2

data and warn the user for missing

data elements and support

modification for missing data elements









Form 8

AML Page 222 of 238

3.3 The AML system should provide a list 2

manager that will be used to manage

various lists like OFAC-SDN and

Politically Exposed Peoples (PEPs).

Users should be able to maintain

internal Watch-lists to monitor their

customers. Users should be able to

add a watchlist and customers to that

watchlist. The list manager should

have a scan feature where in user

should be able to check all the

customers added against the lists.

3.4 The AML system should enable the 2

users to define checklists on the

Customer / Account Static Data and to

generate reports on mandatory

information required for different type

of accounts. This mandatory

information could either have been

prescribed by the regulatory authority

of the country or required as a part of

the Bank’s internal policies.

3.5 The AML system should provide for 2

completely customizable Mandatory

Fields Template allowing the user

complete flexibility in case any

changes / additions are required in

mandatory fields.

3.6 After setting the Fields for each 2

customer type, the user should be

able to generate Mandatory Fields

Missing Report from the system, which

should provide the user with a list of

names of those customers whose

accounts need to be monitored

closely, and from whom the BANK

needs to get more information.

3.7 The Mandatory Fields Missing Report 2

should provide details of Mandatory

Fields Static Data, which will allow the

user to capture unfilled mandatory

fields in customer data. This

Mandatory Fields Static Data should

contain the list of all the mandatory

fields for a particular customer type,

under a particular product and with a

particular account status. The report

should display the names of those

customers, which have not provided

any information about themselves to

the BANK.

3.8 The AML system should provide a Link 2

Tracer that defines and tracks a

multitude of relationships between

customers. The Link Tracer should

enable the compliance officer to

analyze the complexity of a

relationship and associations.

3.9 When a user’s name is entered in the 2

Link Tracer, and the option for

checking the published lists databases

is enabled, the AML system should

scan for the customer’s name among

all the stored published lists system

databases.









Form 8

AML Page 223 of 238

3.10 The user should also have a provision 2

to search for Duplicate Data regarding

a customer, when compared to

another customer of the BANK.

3.11 The user should also be able to 2

search Static Databases based on

parameters such as Address,

Introducer’s Name, PAN, Phone No.,

etc. The result of the search should be

a list of customer’s personal /

geographical relationships with other

customers in the BANK.

3.12 A search made on a customer’s 2

Transactional Data by the users,

should result in a list of relationships of

that customer with all those who are

transacting with him / her.

3.13 Once these relationships are found, 2

the user should have a facility in the

system to “Establish” a

relationship , and this relationship

should be saved in the system along

with the customer’s other static data.

The user should also have the option

of changing this saved relationship

later if he / she so chooses.

3.14 The AML system should enable the 2

user to refine the search criteria from

Exact Match to Similar Sounding,

Partial Name Search, Initials Search,

and Sub String search. The user

should be able to restrict the number

of search results by entering a figure

as the “Hit Limit”.

4 Customer Profiling

4.1 The system should support customer 2

risk assessment as per the bank’s

standard risk grading/rating criteria

4.2 The system should support 2

classification of customers into

risk/behavioral categories based on

his risk classification

4.3 The system should support 2

computation of customer's expected

behavior based on his CIF details and

risk profiling

4.4 The system should support 2

reassessment of customer risk,

reclassification and recreation of

customer behavioral profile

5 Transaction Monitoring

5.1 The system should support detecting 2

implicit and hidden relationships

between:

o Different accounts of the same

customer

o Different customers

o Customers and non customers

5.2 The system should support automated 2

relationship identification between

linked accounts

5.3 The system should support monitoring 2

transactions at relationship and

individual account level









Form 8

AML Page 224 of 238

5.4 The system should behavorial analysis 2

and support detecting and alerting the

user in the event of deviation of

customer from

- the expected behavior (based on

peer group)

- historical behavior

5.5 The system should be able to known 2

Money laundering patters and fraud

patterns like structuring, circulation of

fund etc. The system should have no

limits to parameterise these patterns

based on the banks experiencies in

mony laundering and fraud

5.6 The system should support 2

paramterising regulatory threshold

limits and alert the users on vilolation /

breach of these set limits

5.7 The system should support artifiicial 2

intellegence to setup and tune the

transaction monitoring logic in run

time.

5.8 The system should support defining 2

customer / group level exceptions at

any stage e.g. account opening, etc.

5.9 The AML system should perform 2

transactions monitoring by analyzing

transactions and comparing them

against set Benchmarks. Any

deviation from benchmark should

result in an Alert, which should be then

tracked to resolution.

5.10 The AML system should provide for 2

monitoring all amount-based

transactions, whether for the current

day or historical by filtering the

transaction data. Filters should be

available in the system that will enable

a user to monitor any type of

transaction, whether for one or all

customers.

5.11 The AML system should provide the 2

user to generate a suspicious

transaction report and fill up all the

requisite information as per the format

provided by regulation and to submit

the same. The user can submit the

report to the higher ups for review and

final submission to the concerned

regulatory authorities.

5.12 The AML system should provide the 2

user an option to view all the STRs

generated and update the status as it

moves from review to submission.

6 Alert Management

6.1 The system should support alert 2

justification recognition i.e. the user

should be able to ascertain the reason

behind the alert

6.2 The system should be able to 2

escalate/highlight long pending alerts

to the higher authroities as

paramterised in the solution

6.3 The system should support configuring 2

alerts based on product/branch etc.









Form 8

AML Page 225 of 238

6.4 The AML system should enable the 2

user to effectively manage the alerts

generated by the system, from time of

generation till such time an appropriate

action is taken. When an alert is fired,

the system should display the

weighted Customer, Instrument and

Product based alerts in the respective

Alert Manager window. Complete

description of the alert and the details

of entities on which it is generated

should also be displayed by the

system.

6.5 The AML system should have an 2

Alerts Behavior Monitor, which will be

a list of alerts. The real time and non

real time alerts should be pre-

definable and the user should be able

to change only select parameters. The

alerts shall be fired based on the

benchmarks set. The alerts should be

real time alerts and/or non real time

alerts.

6.6 Real time Alerts –The Real time Alerts 2

should be fired at the same time as an

abnormality occurs.

6.7 The following alerts should be

incorporated in the AML system as

real time alerts. The list below is

indicative and not exhaustive, the

system should provide for configuring

all other alerts that shall be required by

the BANK as real time alerts.

6.7.1 Withdrawal to Previous Withdrawal 2

Ratio

6.7.2 Deposit to Previous Deposit Ratio 2

6.7.3 Current Deposit Account reaching 2

Minimum Balance

6.7.4 Savings Account reaching Minimum 2

Balance

6.7.5 More than X % of Account Drained in 2

a Day

6.7.6 Huge Cash Transactions 2

6.7.7 High / Low Deposit to Withdrawal 2

Ratio

6.7.8 High Amount Transaction by DD, WT 2

6.7.9 Huge Cash Deposits 2

6.7.10 FCN, TC Limits Crossed 2

6.7.11 Transaction in Dormant or Sensitive 2

Account

6.7.12 Frequent transfers in related parties 2

accounts

6.7.13 Cash deposits / withdrawals beyond 2

parameterisable values

6.7.14 Blackisted customers, introducer, 2

guarantor check

6.8 The system should be able to triger 2

events based on the alerts e.g. in case

of deposit of over 50,000/- in cash

over the counter the system should

prompt the user for entering the PAN

number or residential address









Form 8

AML Page 226 of 238

6.9 Non Real time Alerts - These alerts 2

should be fired only when a command

is generated, after collecting the data.

The output of these alerts should be

available in the form of a report.

6.10 The following alerts should be

incorporated in the AML system as

non real time alerts. The list below is

indicative and not exhaustive, the

system should provide for configuring

all other alerts required by the BANK

as non real time alerts.

6.10.1 Deposit or Withdrawal in Newly 2

Opened Accounts

6.10.2 Minimum Account Balance 2

6.10.3 Frequent Transactions Just Under 2

Reporting Threshold

6.10.4 Successive Withdrawals from ATM 2

using Consecutive Cards

6.10.5 Credits and Debits within a certain 2

period

6.10.6 Frequent Cash purchases of TCs, 2

CCs, and MOs

6.10.7 High Cash Deposit or Withdrawal 2

6.10.8 Large Number of Transactions in a 2

Day

6.10.9 Foreign Exchange Transactions 2

6.11 Subjective Alerts – These alerts 2

should be primarily based on

observations made by the teller, user

or any other employee of the BANK.

The AML system should allow the

BANK to parameterize subjective

alerts based on requirements and to

modify and add alerts as and when

required.

6.12 The AML system should have an Alert 2

Management tool, which should allow

the user to perform the following

operations:

6.12.1 The user should be able to assign the 2

alert generated to the various

surveillance officers of the BANK. The

system should change the statuses of

an alert automatically in the course of

assigning an alert to a user or adding

notes to the alert. The user should be

able to enter the various actions to be

taken against the customer and

maintain record of the status of the

alerts.

6.12.2 The AML system should enable the 2

user to view complete details of alerts

fired on customers, instruments and

products, and transactional details

with respect to a particular customer

or customers.

6.12.3 The user should also have the option 2

to filter alerts based on various

parameters such as time, customer,

instrument, product and alert type.









Form 8

AML Page 227 of 238

6.13 The AML system should allow the 2

users to pre-assign alerts to single or

multiple users. Complete audit trail

should be maintained in the AML

system for the alerts assignment from

one user to another.

6.14 The Reports should also provide 2

information to management on the

alerts status. The AML system should

provide for an alert assigned report

allowing the user to view the alerts and

the user/users to whom these alerts

have been assigned and also provide

for an alert statistics report to allow the

user to view the alert statistics and the

user/users to whom these alerts have

been assigned.

6.15 The AML system should provide for 2

other reports to be generated as

required by the BANK at a later date.

7 Case Management

7.1 The system should support Case 2

Management

7.2 The system should have the flexibility 2

to allow the user to creat a case by

clubbing various alerts from cases

7.3 The system should support recording 2

the actions taken on each case

7.4 The system should support entering 2

comments and attach supporting

evidence, i.e. check image, list of

transactions etc, to the cases

7.5 The system should support analytical 2

capabilities for analysis and

investigation of cases



7.6 The AML system should provide for a 2

Case Manager that should enable the

user to store any kind of information in

the folders that he may feel worthy in

the course of investigation. The Case

Manager should serve the user to

undertake a paperless case

investigation and enable him to share

and electronically transfer case

information with other surveillance

officers in the BANK. The user should

be able to create cases and store alert

and non-alert information such as text

files, graphs (bitmaps), transactional

information of a customer or

customers.

7.7 Any folder in the Case Manager 2

cannot be deleted once created. The

users should be able to create their

folders. The folders should enable the

users to store alert info, non-alert info,

and graphics. The user should be able

to move the data from one folder to

another.

8 Reporting

8.1 The system should support all 2

regulatory reporting requireemnts as

mandetated by the regulatory and

statutory authorities from time to time









Form 8

AML Page 228 of 238

8.2 The system should support generation 2

of various management information

system and adhoc reports as required

by the bank from time to time in the

format as desired by the bank.

8.4 The system should support archieving 2

of reports for future reference / use

8.6 The system should support tagging 2

the case, supporting documents,

comments etc, based on unique

identifier



9 System Accessibility

9.1 The system should support 2

deployment of the solution centrally

with a centralise data base



10 Suspicious Activities

10.1 Transaction beyond threshhold limits 2

specified in accounts

10.2 Operations in Dormant accounts 2

10.3 Immediate withdrawal/Transfer of 2

inward remittances.

10.4 Adhoc loans to employees. 2

10.5 Transactions made by specified 2

category of users.

10.6 Frequent deposit of soiled notes by an 2

account holder

10.7 Frequent transactions in round-sums, 2

especially in respect of bills.

10.8 Capability to find out number of cash 2

transactions, amount per day per party

/ group.

10.9 Single Substantial cash deposit of 2

small denomination note.

10.10 Cash credit to multiple account of the 2

same party.

10.11 Large number of credits to same 2

account.

10.12 High velocity of fund balance, frequent 2

in and out of large amounts to various

names

10.13 Frequent and large debit to account 2

for overseas payment and vice versa

10.14 Unexpected repayment to sticky or 2

problemtic account

10.15 Structuring 2

10.16 Flow-through 2

10.17 Circulation of funds 2





11 Benchmarking









Form 8

AML Page 229 of 238

11.1 Default Benchmarks – The AML 2

system should allow for benchmarks

to be fixed based on the general

behavior of entities (Customers,

Products, and Instruments etc.). The

Default Benchmarks should be

definable in the AML system for all

customers based on the Customer

Category (Individual, Corporate,

Institution, NRI, etc.) and the Amount

range in which they are operating. The

user should be able to create, and

even edit an existing benchmark.

11.2 Visual Benchmarking – The AML 2

systems should provide for a simple

and effective tool to fix benchmarks for

any alert. The system should enable

historical behavior of the selected

entity plotted as a graph on the screen

and the user should be able to identify

the benchmark that is appropriate for

that customer. The system should

allow the user to change the

parameters and view the number of

alerts that would get fired. The user

should then be able to set the required

benchmark through specific

benchmarking features

11.3 Specific Benchmarking feature in 2

the AML system should provide the

user an effective way of monitoring an

account, the user should be able to set

specific benchmark to the account for

the applicable alerts.



12 Graphical Analysis Tools

12.1 The AML system should provide for a 2

Regulatory Compliance graph that will

enable the users to view all

transactions on any given day of all or

specific customers who have

breached the benchmark set by the

user in the Parameters table. The bar

graph should display the aggregate of

all transactions in a particular

instrument that have breached the

benchmark set by the user.

12.2 The user should be in a position to 2

view the debit and credit transactions

by way of another chart preferably pie

chart below the bar chart.

12.3 The AML system should provide for a 2

Customer Peer Review graph that

should enable the user to make peer

comparison between one or more

customers on the basis of their

transactional data. The user should be

able to select multiple customers from

the menu provided and make a peer

comparison between customers

during a selected period across

instruments used by the customers

and across the parameters provided in

the system menu.









Form 8

AML Page 230 of 238

12.4 The parameters that should be 2

provided by way of a menu options are

Total Debit and Credit transaction,

Minimum Credit transaction, Maximum

Credit transaction, Total Credit

transaction, Average Credit

transaction, Minimum Debit

transaction, Maximum Debit

transaction, Total Debit transaction,

Average Debit transaction, Count

Total transactions, Count Debit

transactions, Count Credit

transactions, Minimum Account

Balance, Maximum Account Balance,

and Average Account Balance.

12.5 Using the customer peer review graph 2

the user should be able to make

comparison between two or more

customers on any of the above-

mentioned parameters.

12.6 The AML system should provide for an 2

Account Behavior graph that will

provide the user with an overview of

all the transaction made in that

account. The graph should display the

aggregate deposit transactions and

aggregate day wise withdrawal

transactions during the selected

period.

12.7 The AML system should provide for a 2

Customer Behavior Graph that will

provide the user with an overview of

all banking transactions made by a

single customer. The graph should

display the aggregate deposit

transactions and aggregate day wise

withdrawal transactions during the

selected period.

12.8 The user should be able to view all the 2

deposit and withdrawal transactions,

which have taken place for that

customer on a specific day.

12.9 The user should also be in a position 2

to view the day wise opening and

closing account balances by way of a

line for opening account balances and

a line for closing account balances for

the given period selected by the user.

12.10 The user should also have the option 2

to view the account balance

movement for any given day in the

graph. In this manner the user should

be in a position to track the account

balance movement of a customer as

and when required.

12.11 The above graph should enable the 2

user to display the Total Transactional

Value between given periods as

specified by the user on a time slice

basis. In this manner the user should

be able to make a comparison of

various instruments across days and

within a specified time period.









Form 8

AML Page 231 of 238

12.12 The user should be able to view the 2

table, which would display the list of

customers who have transacted

through the instrument selected. The

user should also be able to view the

account no, debit transaction, credit

transaction alongside the customers

name.

12.13 The user should be able to view the 2

aggregate debit or credit transaction

for the particular instrument by way of

a another chart preferably pie chart.

12.14 The AML system should provide for a 2

Post Transaction Analysis graph that

will allow the user to query the AML

system Data-warehouse in an ad-hoc

manner and get information in form of

graphs.

12.15 The AML system should provide for a 2

graphical representation of the alerts

fired on all customers across the

BANK. This graph should enable

users to focus on the customers

whose alert weightage are high. Alert

weightage for customers should be

based on all the alerts fired, their

priority and number of times each alert

is fired.

12.16 The AML system should provide for a 2

graphical representation of the alerts

fired on the all instruments across the

BANK. This graph should enable

users to focus on the instruments

whose alert weightage are high. Alert

weightage on instruments should be

based on all the alerts fired, their

priority and number of times each alert

is fired.

12.17 The AML system should provide for a 2

graphical representation of the alerts

fired on the all products across the

BANK. This graph should enable

users to focus on the products whose

alert weightage are high. Alert

weightage on products should be

based on all the alerts fired, their

priority and number of times each alert

is fired.

12.18 The AML system should provide for 2

Flip Tables through which the user

should be able to conduct a multi-

dimensional analysis of the Banking

information – Customers, Products,

and Instruments.

12.19 The user should be able to view any 2

customer’s data on the Flip Table by

selecting the customer flip link

provided on the customer’s name from

any module right across the AML

system.









Form 8

AML Page 232 of 238

12.2 The Customers Flip Table should 2

display the customers, products,

instruments in which they have

transacted and the respective

transactions that have taken place.

User should be able to create their

own templates and add customers to

the same to monitor closely. All the

watch lists created in the list manager

should become a system-defined

template.

12.21 The Product Flip Table should allow 2

the user to view the transactional

details Product wise- Customer wise -

Instrument wise. The system should

maintain primary difference between a

product and instrument wherein a

product is a service provided by a

BANK whereas an instrument is a

mode of transferring, depositing or

withdrawing cash, with specific

instruments being assigned for each

product.

12.22 The Instruments Flip Table should 2

display the instruments, customers

and the respective transactions that

have taken place.

12.23 The AML system should have a 2

feature that enables a user to view the

most active customers of the BANK

for a specified day or period. The Most

Active By parameter in the AML

system should offer several options to

the user such as Deposit Amount,

Deposit Frequency, Average Deposit

Amount, Withdrawal Amount,

Withdrawal Frequency, Average

Withdrawal Amount, Transaction

(Gross of Deposit and Withdrawal)

Amount, Transaction Frequency and

Average Transaction Amount.



13 Tools

13.1 The AML system should provide 2

generation of offline reports by

selecting the parameters through

remote access.

13.2 The AML solution should support a

powerful report writer for for report

generation having featues like

13.2.1 Drag and drop 2

13.2.2 Arithmatic computations 2

13.2.3 Page layouts 2

13.2.4 Fonts 2

13.2.5 Presentation layouts 2





14 Security









Form 8

AML Page 233 of 238

14.1 The AML system should have 2

surveillance software to prevent

malpractices. The system should

provide for a foolproof security system.

The built-in Security System in the

software should ensure that the

sensitive data that the system handles

is protected from unauthorized access

and misuse. It should provide the

Supervisor with a high degree of

control over assigning system access

rights to users. The system should

provide for the users to be assigned

individual rights or may be grouped

together and given common rights.

Hierarchical Security, Access level

Security, Singular Log-in per user at

any given point of time, are some of

the security features that should be

supported by the AML system.

14.2 The AML systems should maintain 2

comprehensive Audit Trails detailing

every user activity. Audit Trail reports

should be generated and may be

viewed on-screen and/or printed.



15 Help

15.1 Complete Online context sensitive 2

help should be provided in the AML

system to aid the user. The help

feature should invoke from any

module or screen with the help of a

mouse click or a function key.



16 Integration

16.1 The AML solution should be tightly 2

integrated with the banks core banking

solution, other payment systems,

treasury etc.

16.2 The solution should support both 2

online and off line data validations and

alerts









Control Total 294









Form 8

AML Page 234 of 238

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor Comments

6 Document Imaging

6.1 Scanning

6.1.1 Ability to support scanning for paper files 2

6.1.2 A document-imaging scanner should have an Automatic 2

Document Feeder (ADF). This device allows stacks of

paper to be placed into a tray and automatically fed one

page at a time into the scanner, speeding up the

scanning process.

6.1.3 Ability to handle variety of paper sizes 2

6.1.4 Ability to handle 150 – 200 pages per minute 2

6.1.5 Ability to support duplex scanning of documents i.e. 2

both sides of a two-sided document to be scanned in a

single pass.

6.1.6 Ability to support multiple scan stations 2

6.1.7 Ability to support “Portable Volumes” i.e. documents 2

scanned by 3rd party agencies can be incorporated into

the “Live” system without interrupting or – re-indexing

existing work.

6.1.8 Ability to share documents scanned across several 2

offices / departments.

Control Total 16



6.2 Conversion

6.2.1 Ability to transform electronic word processor or 2

spreadsheet documents into a permanent raster

(picture) image format for storage within an imaging

system.

6.2.2 Ability to generates a complete text file, while retaining 2

the visual formatting and layout of the original file. This

text file can then be used for full-text indexing of the

document to assist with later retrieval.

Control Total 4



6.3 Importing

6.3.1 Ability to support “ Electronic Document Management”. 2

It is a method for bringing electronic files, such as office

suite

6.3.2 Documents, graphics, audio clips or video files, into a 2

document imaging system. Files can be “dragged and

dropped ”into an imaging system, but are modifiable

and remain in their native

6.3.3 format. These files can be viewed in their original format 2

by either launching the originating application or by

using an embedded file viewer from within the imaging

system.

6.3.4 Ability to “drag and drop ”files into an imaging system. 2

6.3.5 Ability to view these files in their original format by either 2

launching the originating application or by using an

embedded file viewer from within the imaging system.

Control Total 10









Form 8

Document Imaging Page 235 of 239

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor Comments



6.4 Storing Documents

6.4.1 Ability to be able to use any storage device currently

available —as well as those on the horizon —to provide

long-term document storage.

6.4.2 Ability to at least support the following storage options 2

6.4.2.1 Ø Magnetic Media (Hard Drives) 2

6.4.2.1 Ø Magneto – Optical Storage 2

6.4.2.1 Ø Compact Discs 2

6.4.2.1 Ø DVD’s 2

6.4.2.1 Ø WORM 2

6.4.2.1 Ø Briefcases 2

Control Totals 14







6.5 Indexing Documents

6.5.1 Ability to support at least the following 3 primary ways to

organize documents in an imaging system

6.5.1.1 Ø Index Fields 2

6.5.1.2 Ø Full – text Indexing – with the facility to perform 2

Optical Character Recognition

6.5.1.3 Ø Folder / File Structure 2

Control Totals 6







6.6 Retrieving Documents

6.6.1 Ability to find any document within the system based on 2

a user knows about the document. E.g.

6.6.1.1 In some cases, this means browsing through folders 2

6.6.1.2 In other cases it could mean conducting index field 2

searches.

6.6.1.3 A word or phrase the document contains 2

6.6.1.4 A full text search to find the relevant file. 2

6.6.1.5 Fuzzy Logic search 2

6.6.1.6 Wildcard search 2

6.6.1.7 Boolean Operator 2

6.6.1.8 Proximity search 2

6.6.1.9 Lines of context 2

6.6.1.10 Highlighted search words 2

6.6.1.11 Indexed key words 2

6.6.1.12 User definable template fields 2

6.6.1.13 Combination of the above 2

Control Totals 28



6.7 Access Control

6.7.1 A full-featured imaging system must provide these 2

different users with appropriate levels of access, without

compromising confidentiality or security.

6.7.1.1 Availability of Fundamental features, like: 2

6.7.1.1.1 Ø Broad Availability 2





Form 8

Document Imaging Page 236 of 239

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor Comments

6.7.1.1.2 Ø Comprehensive Security 2

6.7.1.2 Ability to access documents through the users desktop 2

6.7.1.3 Ability to provide a client-based user interface that 2

enables the scanning, indexing and retrieval of

documents.

6.7.1.4 A comprehensive security system must allow the 2

system administrator to control what folders and

documents users can see, and what actions they can

perform on those documents (edit, copy, delete, etc.)

6.7.1.5 This system must control access to folders, documents 2

and even redacted images and text in a simple and

complete manner. (I.e. blackout or whiteout) which

allows security to be controlled down to the individual

word level)

6.7.1.6 Ability to make document imaging available to every 2

authorized person, whether in an office, at a remote

location , all without compromising system security.

Ability to make document imaging available to every 2

authorized person over the Web, all without

compromising system security.

6.7.1.7 System should allow user set up to be controlled by a 2

specific system administration module.

6.7.1.8 Ability to capture employee details such as name, 2

designation, employee code etc.

6.7.1.9 Ability to automatically generate a unique user ID upon 2

authorization of the employee details.

6.7.1.10 Ability of the system to allow the user (Bank) to define

password policies for accessing the system. The

minimum password policies to be defined are:

6.7.1.10.1 Ø Minimum password length 2

6.7.1.10.2 Ø Maximum password length 2

6.7.1.10.3 Ø Alpha numeric combination of password 2

6.7.1.10.4 Ø Compulsory use of special characters 2

6.7.1.10.5 Ø Minimum password age 2

6.7.1.10.6 Ø Password expiry period 2

6.7.1.10.7 Ø Repeat passwords etc. 2

6.7.1.11 All password policies defined should be 2

parameterisable.

6.7.1.12 System to permit access only through password 2

verification

Control Total 44







6.8 Other Features

6.8.1 Ability to support typical document imaging annotations

which include:

6.8.1.1 Ø Highlighting images and text in various colors to 2

emphasize words or sections

6.8.1.2 Ø Redacting (blacking-out or whiting-out) images 2

and text to preserve confidentiality







Form 8

Document Imaging Page 237 of 239

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor Comments

6.8.1.3 Ø Stamping images with words such as FAXED or 2

CONFIDENTIAL, or with signatures denoting approval

or denial

6.8.1.4 Ø Attaching sticky notes that contain additional 2

comments

6.8.2 An imaging system ’s security should control who can 2

view

6.8.3 Annotations such as highlighting, stamps or sticky 2

notes, and who can see through redaction. All

annotations should be overlaid and not change the

actual image.

6.8.4 Ability to support Printing, faxing and e-mailing 2

documents

6.8.5 Imaging systems should at least support the most 2

common printer and fax drivers and be able to print

images, text and annotations.

6.8.6 Imaging systems should have options that allow images 2

to be easily sent with any MAPI (Mail Application

Program Interface)-compliant e-mail system and read

by recipients who do not have imaging systems.

6.8.7 Ability to track who is using the system, what 2

documents are being viewed, what actions are being

performed on the documents, and when these actions

are being performed.

6.8.8 Ability to support batch processing of documents 2

6.8.9 Ability to automatically separate and index documents 2

using bar codes.

6.8.10 Ability to support zone Optical Character Reader ('OCR 2

')

6.8.11 Ability to support documentation workflow 3

Control Total 29







6.9 System Compatibility

6.9.1 Compatibility is the ability of an imaging system to work 2

with existing computer and network systems. To

maximize the likelihood of compatibility with your

existing systems, an

6.9.1.1 Imaging system should: 2

6.9.1.1.1 Ø Work with existing operating systems, such as 2

Novell or Windows NT servers, and Windows desktops

6.9.1.1.2 Ø Communicate using popular network protocols 2

such as IPX/SPX or TCP/IP

6.9.1.1.3 Ø Have the capability to find and view documents 2

over the web.

6.9.1.1.4 Ø Use an open architecture and non-proprietary 2

database

6.9.1.1.5 Ø Use client/server architecture with client-side 2

image compression/decompression and server-side

searching and indexing to minimize traffic loads on the

network

6.9.1.1.6 Ø Store files in industry-standard formats 2



Form 8

Document Imaging Page 238 of 239

Centralised Banking Project RFP

Ref No: HO: DIT: CBS: 2005-06:04

Sr. No. Particulars BR VS TL TM Vendor Comments

Control Total 16



Worksheet Total









Form 8

Document Imaging Page 239 of 239