Form 08 - Functional RFP

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
Form 8
Scoring Sheet Page 1
score provided is from 0 to 4.
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
1.2.1.4 Surname 3 5 0 0 When 1.2.1.1 is provided this requirement
1.2.1.5 Other name 3 5 0 0 When 1.2.1.1 is provided this requirement
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:
Form 8
Sr. No. Particulars BR VS TM TL Vendor Comments
1.2.1.1 Title (Mr. / Ms) 3 2 1 5 We are in the processes of customizing the
1.2.1.2 First name 3 2 1 5 We are in the processes of customizing the
1.2.1.3 Middle Name 3 2 1 5 We are in the processes of customizing the
1.2.1.4 Surname 3 2 1 5 We are in the processes of customizing the
1.2.1.5 Other name 3 2 1 5 We are in the processes of customizing the
9 Some Other Examples of Incorrect Responses

1.2 Customer Information File (CIF) 5 0 0
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
1.2.1.1 Title (Mr. / Ms) 3 5 0 0
1.2.1.2 First name 3 5 0 0

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
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
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
Form 8
Page 4 of 248
HRMS
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
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)
Form 8
Page 5 of 248
HRMS
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
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)
Form 8
Page 6 of 248
HRMS
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
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 functionality
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
Form 8
Page 7 of 248
HRMS
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
which has undergone a change will be
5.10 Should compute the dearness allowance (DA) 2
effected
using options such as Fixed DA, linkage to
consumer price index (CPI).
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.
Form 8
Page 8 of 248
HRMS
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
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.
Form 8
Page 9 of 248
HRMS
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:
6.4 Accrual and Payment
System 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
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
Form 8
Page 10 of 248
HRMS
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.
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
Form 8
Page 11 of 248
HRMS
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
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.
Form 8
Page 12 of 248
HRMS
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
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
Form 8
Page 13 of 248
HRMS
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.
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
Form 8
Page 14 of 248
HRMS
12.8 System should process the final 2
hospitalization 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
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.
Form 8
Page 15 of 248
HRMS
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 2
Pension 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
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.
Form 8
Page 16 of 248
HRMS
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
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
Form 8
Page 17 of 248
HRMS
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
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
Form 8
Page 18 of 248
HRMS
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
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.
Form 8
Page 19 of 248
HRMS
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.,
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
Form 8
Page 20 of 248
HRMS
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
acknowledgements based on the following
Acknowledgement
requirements: Number
Transaction type (if standard)
Date and Time (IST)
Name
Employee ID
Purpose
TOTAL
Form 8
Page 21 of 248
HRMS
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
Form 8
Page 22 of 248
Funds
1.1.2.6 System should have proper
tracking of RBI Cheques issued /
received. 2
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
Form 8
Page 23 of 248
Funds
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
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
Form 8
Page 24 of 248
Funds
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
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
Form 8
Page 25 of 248
Funds
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
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
Form 8
Page 26 of 248
Funds
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:
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
Form 8
Page 27 of 248
Funds
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
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
Page 28 of 248
Funds
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
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
Page 29 of 248
Forex and Trade Finance
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
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 viceversa. 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
Page 30 of 248
2.18 System should allow adjustment of PC
against bill drawn under same LC, only
in the case of order specific PC. 2
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
authorization.
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
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
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
Form 8
Page 31 of 248
3.14 System should support auto
crystallization/auto liquidation. 2
overdue interest in case the bill is not
paid on due date. 2
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
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
Form 8
Page 32 of 248
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
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
Form 8
Page 33 of 248
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
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
Form 8
Page 34 of 248
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
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
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
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
Form 8
Page 35 of 248
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
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
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
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
Form 8
Page 36 of 248
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
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 LC. 2
5.45 System should support debiting
commission on payment out of EEFC
Funds for Import payments. 2
Form 8
Page 37 of 248
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
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
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
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
Form 8
Page 38 of 248
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
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
Form 8
Page 39 of 248
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
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
Form 8
Page 40 of 248
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
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
Form 8
Page 41 of 248
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
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
Form 8
Page 42 of 248
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
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
Form 8
Page 43 of 248
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
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
margin accounts customer - wise in
case of out right sale basis release of
margin. Reconciliation of margin
account 2
Form 8
Page 44 of 248
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
insurance of stocks, due date policy
records and renewal reminders 2
fidelity guarantee 2
delivery register. 2
16.16 System should have provision to pay
bullion imports in FC through market
purchase or disbursement of PCFC /
PSFC. 2
17 Domestic Foreign Currency Loans
(DFC)
granting foreign currency loans for PC
and Bills Discounting. 2
granting loans against FCNR(B) for
Term Loan and Working capital finance. 2
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
interest calculation frequencies
(mly/qly/hly or at maturity of loan etc) 2
Form 8
Page 45 of 248
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
Page 46 of 248
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
11 details
Systemfor each generate
should asset 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 inspector 2
14 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
Page 47 of 248
Fixed Assets
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
Page 48 of 248
Fixed Assets
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

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.)
Form 8
Page 49 of 248
Delivery Channels
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.)
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 a 2
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.)
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 respective 2
tables through electronic mediums
such as floppy, file transfers with
proper checks and validity
allow the Bank to design its own
template to capture of information from
the customer for any transactions.
Form 8
Page 50 of 248
Delivery Channels
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
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 account 2
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 the 2
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 generate 2
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)
Form 8
Page 51 of 248
Delivery Channels
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.
1.2.7 The system should display the 2
following fields in the exceptional
transaction report
Ø Account Number
Ø 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 all 2
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.)
Form 8
Page 52 of 248
Delivery Channels
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)
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 to 2
query for a particular transaction based
on amount, transaction date, currency,
instrument number etc.
the account details (master details) for
the selected account.
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 of 2
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
(as desired by the bank) deposit
information. Form 8
Page 53 of 248
Delivery Channels
1.4.6 The system should allow the user to 2
request for closure of the term deposit.
(either on maturity / pre mature)
view the total Withholding Tax to be
paid by him / her for all fixed deposits
held by him for the current / previous
financial years
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 deposit
1.5 Loans
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
enable a user to fill in the loan
application form on – line and submit
the same or download the loan
application form
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.

accept part or full payment from the
user by debiting his / her account
maintained with the bank.
display the payment schedule for the
loan account selected
display the last 7 to 10 transactions for
the account selected by the user
Form 8
Page 54 of 248
Delivery Channels
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.
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.)
display the break up of EMI for both
principal and interest
1.6 Payments
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
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
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.
Form 8
Page 55 of 248
Delivery Channels
drop / delete a beneficiary from his list
of beneficiaries
inquire the beneficiary details by
specifying user defined criteria (e.g.
name, account number, branch where
account held etc)
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
request for a standing instruction by
filling up the relevant details on – line
modify selected fields of the standing
order
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 or e-mail
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 all 2
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.
Form 8
Page 56 of 248
Delivery Channels
1.7 Correspondence
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

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
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
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 .
accept the bill amount from the
customer.
accept or reject a transaction for short
payment (i.e. amount entered is less
than amount displayed)
select his debit account number
through the bill payment option.
Form 8
Page 57 of 248
Delivery Channels
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
display to the customer the amount
paid, unpaid, penalty, charge amounts
etc. utility company - wise or amount
wise
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
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.
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

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.
appropriate warning messages upon
crossing the specified limit.
the customisations done, limits,
utilisation, current balance etc. through
the view option for the account
selected.
1.10 Customer Service & Information
Form 8
Page 58 of 248
Delivery Channels
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
faxed.
1.10.3 The system should be able to fax the 2
customer statement based on the
number specified by the customer
request for a cheque book on – line.
view the cheque books issued to his /
her account for the selected account
and date range.
inquire the status of a cheque leaf (e.g.
paid, stopped, not issued, not paid
etc.)
check for the status of the cheque
book issued to him for a particular
account (number of leaves, total paid,
unpaid, stopped etc.)
process a stop payment request by a
customer on - line / on request
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.
upload the interest rates for various
deposit schemes, loan schemes,
current accounts etc. to enable the
customer to view the same.
enable a user to change his / her
passwords
Form 8
Page 59 of 248
Delivery Channels
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
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.
view the details of a pay order,
demand draft, banker’s cheque, any
other instrument.
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
request for change in his / her address
by filling up all the required details on –
line
view all charges, commission etc.
applicable for various products /
services offered by the bank.
view the various products / services
offered by the bank.
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
Form 8
Page 60 of 248
Delivery Channels
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
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.
Form 8
Page 61 of 248
Delivery Channels
the card details of the customer for the
card selected (credit / debit) for
example current balance, limit,
utilisation, name of card holder,
address etc.
the current statement for the card
selected
and download (standard formats e.g.
Excel) transactions between two dates
as specified by the customer
subscribe for payment of credit card
bills by filling the relevant detail on –
line or should have the facility to
download the same.
display the current unbilled
transactions to the user for the account
selected.
display to the user, the total
accumulated loyalty points for the
credit / debit card selected
maintain the list of items / products that
are offered by the bank for redemption
against the respective loyalty points
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
1.11.13 System should download forms for 2
add-on cards, supplementary or new
cards
permitting user to make payments for
various services availed through credit
cards
generating a report of all transactions
done using a credit card.
1.12 Demat Services
Form 8
Page 62 of 248
Delivery Channels
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

allow the Bank to design its own
template for capturing details for LC
opening.
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
enable a user to modify of specific
details of the LC before authorisation.
policy (e.g. LC opening limits,
modification rights etc.)
search for a particular LC based on LC
number, date, amount, currency etc.
Form 8
Page 63 of 248
Delivery Channels
view LC status
request for an amendment in the LC
after appropriate authorisation from the
designated authority
request for opening a Bank Guarantee
by filling up the necessary details on –
line or should enable the user to
download the same
enable a user to modify specific details
of the Bank Guarantee
search for a particular Bank Guarantee
based on Guarantee number, date,
amount, currency etc.
view the status of import bills on - line
(e.g. lodged, accepted, correspondent
bank payment, settled.
view the status of export bills on - line
(e.g. negotiated, purchased,
discounted etc.
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.
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.
request for extending the due date of
the bills sent for collection, bills
purchased.
view and/or download the complete
history of the bills settled.
Form 8
Page 64 of 248
Delivery Channels
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 be 2
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.
1.14.9 System should interface with the credit 2
cards systems for processing
payments made through the credit
cards
Form 8
Page 65 of 248
Delivery Channels
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
with the conformation message
banking solution for the payment
made and credit the respective partner
accounts (consolidated single entry /
per transaction (parameterisable))
core banking solution, partner site with
the unique transaction number
generated and returned to the
customer
transaction number
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.
Form 8
Page 66 of 248
Delivery Channels
1.15.9 System should print a report of all
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 be 2
made through direct debit from various
accounts linked to the particular
customer / credit cards issued to the
particular customer
with the conformation message.
banking solution / credit card system
for the payment made and credit the
respective institutions accounts
(consolidated single entry / per
transaction (parameterisable))

core banking solution, credit card
system, partner site with the unique
transaction number generated and
returned to the customer
transaction number
Form 8
Page 67 of 248
Delivery Channels
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
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
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
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
policy (e.g. fund transfers limits etc.)
2.1.8 System should handle offline 2
transactions
2.1.9 Should facilitate “Store” and “Forward” 2
mechanism to record off – line
transactions
Form 8
Page 68 of 248
Delivery Channels
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
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.)
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
automatically check the user ID’s and
PIN with the phone Banking Database.
Form 8
Page 69 of 248
Delivery Channels
2.2.2 The system should be able to store the 2
user ID’s and PIN in an encrypted
mode/ a compressed mode / unclear
text within the Phone Banking
application.
encrypting data (e.g. password,
financial data etc.) during transit.
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
Ø 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
transaction report
Ø Account Number
Ø 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.)
Form 8
Page 70 of 248
Delivery Channels
generating a transaction log of all
transactions done during the day.
2.2.9 System should define messages to be 2
displayed for different types of errors.
generating a list of all rejected
transaction and the reason for rejection
2.3 Account Services

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)
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.
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.
Form 8
Page 71 of 248
Delivery Channels
generating and announcing a unique
transaction number for every
transaction done trough phone banking

a report of all transaction effected in
the core banking through phone
banking
2.5 Customer Service & Information

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
request for a cheque book
inquire the status of a cheque leaf (e.g.
paid, stopped, not issued, not paid
etc.)
inquire for the status of the cheque
book issued to him for a particular
account (number of leaves, total paid,
unpaid, stopped etc.)
process a stop payment request by a
customer
announce the instrument pending for
clearing (outward clearing) for the
selected account.
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
Form 8
Page 72 of 248
Delivery Channels
announce the total outstanding against
a particular loan / advance account as
selected by the user.
enable a user to change his / her PIN
status (success / failure) of any
transaction / request by specifying the
date, instrument number, amount etc.
2.6 Trade Finance

announce LC status
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 selected
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
Form 8
Page 73 of 248
Delivery Channels
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
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
Page 74 of 248
Delivery Channels
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
Form 8 Page 75 of 248
ALM
1.41 Data Normalisation 2
1.42 Data Merging 2
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
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

ALM
1.57 System should record the effect of
regular payment - in both floating
and fixed rate scenario- and non-
payment of EMIs/ Instalments. 2
1.58 System should record frequency of
interest accrual, compounding
yearly, etc.), interest booking
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
interest rate wise for Term
Deposits according to ORIGINAL
maturity on any given date. 2
interest rate wise for Term Loans
as per REMAINING maturity on
any given date. 2
interest rate wise for Term Loans
according to ORIGINAL maturity
on any given date. 2
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
of behavioral maturity pattern
based on behavioral pattern / past
data / empirical studies and
resultant classification. 2
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
ALM
3.3 System should provide maturity
Pattern / Duration / Modified
Duration / Revaluation of
Investment Portfolio 2
3.4 Currency Risk:
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
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
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
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
ALM
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
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
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

ALM
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
departments (e.g. Mumbai zonal office
1.2 System
etc.) Thetosystemmap allshould
nodal support
/ link any 2
branches to the HO for
number of hierarchal consolidations consolidated
1.3 views.
i.e.
System Zonal toOffices
collate to Head Office
information of etc. 2
various branches / departments linked
to the nodal / link departments and the
1.4 nodal
System / link departments
to generate to thebranch
individual Head 2
Office for MIS reporting.
reports at any interval at the nodal /
1.5 link
System departments
to define andany Head
reportOffice
/ MIS if 2
required.at the Branch, nodal /link
printing
department, H.O based upon defined
parameters e.g. at the time of day–
end, occurrence of a particular event,
1.6 System should upload data received 2
day–begin(user-defined)
in any electronic format from branches
outside the core banking system for
1.7 consolidation
System to support and amalgamation
manual feeding forof 2
reporting purposes
data at the nodal / link departments or
Head Office for consolidation and
1.8 amalgamation
System to define of data
reports received
as by 2
manual branches.
compulsory report and print them at
user definable periods e.g. end of day,
beginning of day etc. The system
should also provide an option to allow
the user (Bank) to select the location
1.9 System
of each reportto schedule
printing.printing of the
(e.g. at non – 2
critical
Head Office and branches or onlyevery
reports e.g. n report after at
1.10 10
thedays
System etc
should
branches.) provide fucntion where 2
user to define print layout (horizontal /
vertical etc.) and other print setting
1.11 (paper
Systemsize, marginaetc.)
to provide through
flexible report 2
menu driven options
writer with the following minimum
1.12 features:
· Specify the format and layout of
1.13 reports
· Summarise and total the
1.14 information
· Selected to be reported
records to be included in
1.15 ·theSelected
report details from each record to
1.16 ·bePerform
included.arithmetic calculation on
1.17 the information
System should selected
Download data 2
1.18 to/from third party
System to print reports software.
as on a 2
particular date, any user defined date
or range of dates for the selected
1.19 criteria
System(e.g. stop
to print allpayments,
reports in bi-lingual 2
transaction
format i.e. English, etc.)
details Hindi/other official
languages
Form 8
Page 80 of 248
MIS
1.20 System to define reports for scheduled 2
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
branch, n2 number at day - begin at
1.21 System
the HeadtoOffice
restrictetc.
access to reports
and also based 2
based
on activities like day-begin, defined
upon user privileges day-end,in
1.22 the system
System
month to have the
begin/end capability of
etc. 2
scheduling report printing
(parameterisable) from the data
centre for the various branches, Zonal
Offices etc. which should be
automatically printed at the
designated branches, Zonal Offices
1.23 System should
etc. based check whetherrules
on parameterised Credit
e.g. 2
Monitoring statement of large
on day-end, on day-begin, month end,borrowal
accounts – Part B – Accounts with Rs.
year end etc.
2 crores and above (parametrisable)
is generated.
1.24 a. Debit and credit summations 2
1.25 b. Overdue bills (Number and Amount) 2
1.26 c. Excess /Adhoc allowed, date of 2
1.27 adjustment
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 (defaulters list) generate the report for
System should 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
and details of earnings along with
1.30 The frequencies
financial ratios asofrequired
generation of
by the 2
these reports /statements
statutory authorities can be
parameterised e.g. Quarterly to
Monthly to weekly and viceversa
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
facility to configure to see that the
1.32 System
respective should segregate
department aloneaccounts
at 2
quantum
Controlling Office can view. lac, etc. )
wise ( < 1 lac, 1-5
1.33 possible
System should generate scheme 2
wise progress reports as per
1.34 periodicity
System should defined by thewith
compare Bank.
previous 2
week/ month/ quarter/ half year/ year
possible or comparison for a given
1.35 period/
Systemperiodical
should feeedprogressive reports.
in information 2
from non-core branches at any point
for amalgamation and generation of
1.36 MIS
Systemas required by the Bank
should generate reports for 2
branches category wise/ population
1.37 wise etc.should
System on different parameters.
calculate averages of 2
Deposit/ Advances/Business etc. per
employee/per branch
Form 8
Page 81 of 248
MIS
1.38 System should calculate Income/ 2
Expenditure/ Profit/ Loss per
1.39 employee/per
System shouldbranch
calculate cost of 2
funds/ yield on advances branch-wise
1.40 System should calculate the Break 2
even analysis of profitability.
1.41 System should generate exposure to 2
– Sensitive sector, Capital market,
1.42 Commodity
System shouldsector, Real estate
calculate etc.
Deposit 2
1.43 Insurance
System premium
should generate reports/ 2
statements as per new Basle Capital
Accord.
Total 76
Form 8
Page 82 of 248
MIS
Comments
1 General Ledger
1.1 System should have Details of
deposits of branches and variance
analysis 2
1.2 System should generate statement of
interest paid to the branches and
customers 2
1.3 System should generate statement of
interest received form the branches
and customers 2
1.4 Effective rate of interest on deposits
classified in terms of different deposits
1.5 System should generate the monthly
progress report branch-wise and
consolidate the same for various
branches at the nodal/link
departments and Head Office 2
1.6 System should do sensitivity analysis
(Impact of 1% drop in the deposit
rates on the Balance Sheet) 2
1.7 System should Report on Weekly
reserve requirement 2
1.8 Bank statistics to different
departments of RBI such as Rupee
deposits held by different customer
categories etc. 2
2 Consolidation
2.1 System should Print financial
performance analysis by division,
department and corporate structure 2
2.2 System should Consolidate, providing
flexible reporting of user-defined
financial ratios compared to similar
ratios for the previous period, the
same period last year and year-to-
date
2
3 Reports
3.1 Interfaced Transactions - System
should Lists all transactions received
from automated interfaces and any
related balancing or exception errors 2
3.2 System should Increase and decrease
over similar balances to the previous
year and also show budget variances
2
3.3 System should generate reports such
as journals, logs, audits trails,
transaction reports and account based
reports 2
Form 8
General Ledger
3.4 Summary Trial Balance - System
should summarise listing of all
account activity for the accounting
period, including open and posted
transactions. 2
3.5 Transaction Register -System should
lists transactions by user-specified
ranges of periods, accounts,
transaction types, transaction dates,
amounts or any combination thereof 2
3.6 Ad Hoc reports - System should
provide an interactive tool for creating
user- specified report that access,
select and sort on any field within the
database, calculate values including
arithmatic's percentages, variances
and statistics, create new fields and
compare between columns, create
multiple subtotals and grand totals,
access current period, prior period
and prior year data, print to printer,
screen or disk , save and modify
versions, and download in standard
PC/Mac spreadsheet or database
format.
2
3.7 System should provide Differences in
inter-branch reconciliation 2
3.8 System should have a function where
in Sundry creditors / Impersonal
accounts, reversal of entry beyond 1
year should be authorized by two
officials.
3.9 System should perform operation of
any Entry outstanding more than 3
years in sundry A/C to be transferred
to HO A/c 2
3.10 No debit entry to be accepted by the
system on HO A/c except Transfer
price and P&L A/c. 2
Total 36
Form 8
General Ledger
Comments
1 Application Security
1.1 System should be able to define user
profiles (Capabilities/ Rights) 2
1.2 System to facilitate creation of the
user ID’s at a central level / branch
level as desired by the Bank 2
1.1 System to attach the user ID of the
employee to each and every action
done in the system 2
1.4 System to check for duplicate record
based on employee name (first + last
name), employee code etc. 2
1.5 System should set a default password
upon creation of the user ID. 2
1.6 System should allow the user (Bank)
to define password policies. The
minimum password policies to be
defined are: 2
1.6.1 Ø Minimum/ Maximum password
length
1.6.2 Ø Alpha numeric combination of
password
1.6.1 Ø Compulsory use of special
characters
1.6.4 Ø Minimum password age
1.6.5 Ø Password expiry period
1.6.6 Ø Repeat passwords etc.
1.6.7 Ø Repeat passwords period etc.
1.7 The system should be able to
automatically check the passwords
with the password policy, which can
be customised by the bank. 2
1.8 System should enforce changing of
the default password set by the
system (at the time of creation of user
ID) when the user 1st logs on to the
system. The system should enforce all
password policies as defined at the
time of first change.
2
1.9 System should have the capabilities to
provide dynamic password usage i.e.
use of smart card for authentication of
users. 2
1.1 System to define hierarchical
password structure 2
1.11 System to permit access only through
password verification 2
Form 8
Page 85 of 248
Application Security
1.12 System should store User ID's and
passwords in an encrypted /
compressed format in the respective
files or tables 2
1.11 System to define overrides for certain
set of transaction errors / warnings
and link transactions to specific user
ID’s. All such overrides should be
recorded for Audit trail. Also levels of
password to be decided for override.
1.14 System to define password negatives
at a global level 2
1.15 System to form user groups and link
rights to such defined groups 2
1.16 System to restrict user access to 2
1.16.1 Ø Menus
1.16.2 Ø Sub- menus
1.16.1 Ø Screens
1.16.4 Ø Fields
1.16.5 Ø Reports
1.16.6 Ø Combination of the above
1.17 System should perform all restrictions
& accesses at the Central level only. 2
1.18 Systems should have all restrictions to
be placed within the application with
the help of menu driven options. 2
1.19 System to define levels of
authorisation, while ensuring minimum
two levels.. How teller payments will
be authorised. 2
1.2 The system should be capable of
encrypting the password / other
sensitive data during transit. 2
generate audit trails of all
transactions. The minimum fields that
should be captured in the audit trail
are: 2
1.21.1 Ø Date & time stamp
1.21.2 Ø Transaction ID linked to every
transaction / activity. Transaction ID
has to be unique and should not be
duplicated. Further the transaction ID
should be generated whether the
transaction is successful,
unsuccessful / rejected.
1.21.1 Ø Operator ID
1.21.4 Ø Authorised By
1.21.5 Ø Overridden By
1.22 System to define conditions for
transactions to be treated as
exceptional transactions 2
Form 8
Page 86 of 248
1.21 For each exception, system to define
the system should generate a warning
message or proceed with
authorization or reject the transaction. 2
1.24 System to define level and number of
authorizations required to pass an
exceptional transaction 2
1.25 The system should generate
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
2
1.25.1 Ø Those transactions that require
approvals from
higher authorities other then the
normal
authorisation level
1.25.2 Ø All rejected and cancelled
transactions along with
reasons for the same.
1.25.1 Ø Any changes made to the global
parameter files
1.26 The system should at least display the
transaction report 2
1.26.1 Ø Date & time stamp
1.26.2 Ø Transaction ID
1.26.1 Ø Operator ID
1.26.4 Ø Transaction details (before
changes)
1.26.5 Ø Transaction details (after
changes)
1.26.6 Ø Referred by ID (referring officer
in case of higher approvals)
1.26.7 Ø Authorising Personnel ID
1.26.8 Ø Remarks if any
generating a supplementary of all
transactions done during the day 2
1.28 The system should allow users to
define error messages
(parameterisable) for a particular
transaction 2
1.29 System to restrict employees to post
and also authorise transactions in his /
her own accounts or those of his / her
relatives accounts. 2
1.1 System to restrict access to critical
accounts / information to a particular
user id / or a group of users. 2
Form 8
Page 87 of 248
1.11 The system should not allow any
changes to be made to the details of
the transaction after authorisation by
the officer. 2
1.12 The system should not permit the
same individual to modify and
authorise the same transaction.
Except Teller Window 2
1.11 System should restrict access to post
directly to the Profit and loss account
heads 2
1.14 System should restrict access to any
teller / officer / branch personnel to
change global parameters 2
1.15 System should enforce "Maker"
"Checker" concept for all types of
transaction entry, modification ,
deletions, static data entry,
modifications, deletions 2
1.16 System should define Maximum
Inactive Time (parameterisable) after
which a user should be automatically
logged out of the system. 2
1.17 System should suspend or cancel a
user ID defined time frame. 2
1.18 System must revoke suspended user
Ids. 2
1.19 System must have the provision to
assign a user ID with highest access
level for querying with no financial
transaction authority. 2
1.4 System should allow only those
transactions to be deleted that are
unauthorised and capture audit trail
for such deletions 2
1.41 System to capture signatures of
employees having user-ids in the
system 2
1.42 System should support tracking of all
the System administration activities
within appropriate system log 2
1.41 System should report active users in
the system branchwise or bank wise. 2
1.44 System should have Log report of
users logging in & out of the system
throughout a period of time. 2
1.45 System to support validation of user id
and password with customized
dictionary for rejections 2
1.46 System to support definnig separate
menue options with view / query
options for auditors etc. 2
Form 8
Page 88 of 248
1.47 System to support geographic
regionwise,branchwise,account type
wise,transaction type wise facility for
fixation of teller/ single window limits. 2
1.48 System should support online
surveillance from a remote place
(Data Center) about the activities
performed by users in various
locations. 2
1.49 System should parameterise different
business hours,working hours, weekly
offs, holidays etc. for different
branches 2
1.5 System should support dual
passwords for assess to critical
functionalities. 2
1.51 System should track the changes
made in parameter files along with
detailed audit trail 2
1.52 System should generate reports for
login access , staff with multiple level
access, ,use Ids
disabled,suspended,cancelled users. 2
1.51 System should support creation of
temporary user id's and access rights
based on number of days, months
restrictions or time based restrictions
(minutes, hours) 2
1.54 System should define users as free /
captive users e.g. a free user is a user
who can access accounts / data of
another branch and can pass
financial transactions in the other
branch from his home branch
depending upon the access right and
levels. A captive user is a user who
cannnot either view any other branch
data nor pass any financial
transactions in other branches
2
1.55 System should definine fields as
modifiable / not based on defined
access levels / rights 2
Total 108
Form 8
Page 89 of 248
Comments
1 General Banking
1.1 Multi-currency system. The system
should have the facility to open,
operate, transact and monitor all
accounts, products, schemes in base
currency or any other foreign currency
the Bank deals in.
2
1.2 It should be a bilingual system 2
1.3 All software modules integrated (e.g.
customer information, account
opening, transaction processing, teller
operations, interest calculation,
charges etc.) 2
1.4 System should be able to support
Extension Counter and Recovery
Branch functioning and accounting 2
1.5 System to specify cut - off times for
transactions branch - wise /
department -wise after which the
transactions should be recorded in the
system with the next working date
2
1.6 Should support online real time &
batch operations
2
1.7 Provide support for scheduling and
defining of Jobs
2
2 Customer Information and Services
2.1 System should generate a unique

account number for the customer as
defined by the Bank 2
2.2 System should have customer to
Account Relationship 2
2.3 System should automatically link all
accounts of the customer to his/her ID 2
2.4 System should identify and print
reports of customers category-wise
as: Staff, Senior Citizen, Resident
Indian, NRE, NRO, Pensioner, HUF
etc., with facility to define any number
of categories
2
Form 8
Page 90 of 248
General S/W Requirements
2.5 System should capture information
of Individual Customer : Information
about the customer contain extensive
parameterized data like a) Customer
Types, Introducer details,
identification, mode of operation,
signatories, nominees, occupation,
nationality, etc.
2
2.6 System should capture information
of Corporate Customers
Information about the customer
contain extensive parameterized data
like a) Customer Types, Introducer
details, identification, mode of
operation, signatories, nominees,
occupation, nationality, Company
Type (Partnership/ Ltd. Liability/
Public/ State corp. etc.),Line of
Business, Industry Sector etc.
2
2.7 System should capture capture minor
details if customer is a minor and
generate a letter for minor at attaining
majority. 2
2.8 System should generate a Group ID
for various groups of customers,
including individuals and corporate
customers 2
2.9 System should have facility to define
customer to account relationship as
follows for example it should be
possible to generate the list of all
accounts maintained by a customer
with the bank and it's relationship type
such as: Single, Joint, Guardian,
Introducer, Guarantor etc.
2
2.10 System should have facility to define
relationship for joint account holders /
nominee to the parent account holder.
Such as Spouse, Guardian, Introducer
etc. 2
automatically change account status
(non-performing, sub-standard,
doubtful loss etc.) as defined in the
credit monitoring module 2
2.12 System should Capture Operating
Instruction (Mode of operations) . 2
2.13 System should capture details of
Mandate Holder or Power of Attorney
Holder 2
2.14 System should Capture customer
signature (for all authorised
signatories) 2
Form 8
Page 91 of 248
2.15 System should display the
signature/phone scanned of the
customers, joint account holders,
authorised signatories etc. at all times
upon pressing hot keys 2
2.16 System should allow bank-defined
number of nominees to be nominated
by the account holder. Capture the
following minimum details for each
Nominee: 2
2.17 System should Print thank you letters,
welcome letters and other customized
letters. 2
2.18 System should provide options to
select customer's account information
ordered by : Account/ Facility type,
Relationship Type, Pre-defined
attribute 2
2.19 System should store and update all
type of accounts and facilities that the
customer maintains with the bank 2
2.20 On-line help for security administration
features 2
2.21 Facility of the software to confirm with
ISO messaging standards (e.g. ISO
8583, XFS protocol) 2
2.22 Facility to support Remote connectivity
to designated bank employees upon
appropriate authorisations. (View &
Transact) 2
2.23 The system to update transaction of a
real time, on-line basis for all
transaction effected through delivery
channels 2
3 EOD/BOD Processing
3.1 System should support the following
features in EOD/BOD
User-Definable / fully parameterisable
3.1.1 EOD/BOD processing 2
3.1.2 Error logging of EDO/BOD errors 2
3.1.3 Fully automated EOD/BOD
Processing 2
3.1.4 User-definable action in case of errors
2
3.1.5 Facility to restart EOD/BOD from point
of failure - automatic and manual 2
3.1.6 Different Processing at Month-End,
Year-End and Holidays 2
3.1.7 Holiday Processing 2
Form 8
Page 92 of 248
Total 74
Form 8
Page 93 of 248
Comments
1 Appraisal & General Issues
1.1 Facility to incorporate date of receipt
of application & other particulars of
application. 2
1.2 Facility to generate
acknowledgement letter on receipt of
application incorporating therein date
of receipt, expected date of
conveying Bank’s decision, the
contact official for enquiry etc and
flexibility to modify the draft letter as
per Bank’s standard format.
2
1.3 System should generate reminder
for the sanctioning authority in case
disposal of loan application exceeds
the prescribed timeframe for
disposal of application as per Bank’s
lending policy.
2
1.4 System should provide Access to the
customers to enquire present status
of the loan application submitted by
them. 2
1.5 System should check whether
customer information contains all
relevant information including net
worth & other requirements as per
KYC norm 2
1.6 System should capture details on
guarantor contains all relevant
information including net worth &
other requirements as per KYC
norms 2
1.7 Customer and guarantor information
should meet CIBIL requirement 2
classify the borrower as per
constitution (individual, private ltd.,
public ltd, co-operative society, trust
etc.). 2
further categorise all loans/advances
as – Soverign (domestic/foreign),
Bank (Scheduled/others), Corporate
(PSEs, Project finance, Object
finance, Primary dealers etc.), retail
portfolio and Loan against mortgage
backed securities (residential
mortgages/commercial real estate/
others) i.e. as per BASEL – II norms.
2
Form 8
Page 94 of 248
Loans and Advances
facility-wise classification of
Advances like Demand/ Term/Cash
Credit/WCDL/WCTL/BP etc 2
Sector-wise classification like
priority/ non-priority/ SSI/Agriculture
etc. they should further be
categorized as Direct Finance &
Indirect Finance.
2
Scheme-wise classification. 2
1.13 Classification of borrowal Accounts
into SC, ST, Minority Community,
OBC, Phy. Handicapped, Women. 2
1.14 For Agriculture advances, system
should provide landholding wise
breakup of advances granted to
agriculturist 2
1.15 In case of manufacturing activities,
Provision for incorporating type of 2
industries, viz Steel, Cement etc.
1.16 System
System should
should determine
have flexibility to
borrower/GroupWise exposure
modify group of industries 2
1.17 System should determine industry
wise exposure 2
1.18 System should have a warning
system to indicate that exposure limit
in a particular industry / borrower /
group has exceeded or likely to
exceed 2
1.19 System should have scope for
incorporating list of prohibited
activities of lending 2
1.20 System should incorporate activity /
sector lending to which require HO
approval 2
1.21 Provision to interface with Credit
Appraisal, stock feeds and credit
rating agencies. 2
1.22 Provision to access the appraisal
note and accord on line approval by
the delegated authority. 2
1.23
System should have a Risk Rating
System compatible with our system
or have a provision to provide
interface with Banks existing risk
rating model. It should be flexible so
that parameters may be modified as
per bank’s policy? There should also
be provision to feed risk rating
manually. 2
incorporate external rating of rating
agencies (e.g. CRISIL/ICRA) along
with our rating 2
Form 8
Page 95 of 248
Loans and Advances
1.25 System should provide for setting
minimum and maximum limits of
Loan and it should be flexible for
various lending schemes 2
1.26 System should provide facility for
appraisal for Retail Lending
Schemes (as per eligibility and
repaying capacity norms) and be
flexible 2
1.27 Audit trail of modifications to Master
details should be available. Status of
any Loan account as on any date if
queried on a later date, the same
position prevailing on that date
including master details should
reflect.
2
1.28 System should support Lending style
Sole/Consortium/syndication
System should have appraisal etc 2
1.29 frame-work contains
turnover/MPBF/Cash Budget
methods etc. 2
1.30 System should feed financial details
of the customers for arriving at the
financial strength related to the
advance. (Current Ratio, Debt equity
ratio, Debt service coverage ratio,
Internal rate of return (IRR), Break
even point etc)
2
1.31 CMA Data should be available in the
system. 2
1.32 Assessment as per turnover method.
(Projected Sales, 25% of projected
sales, 5% margin, NWC projected/
available. EBF etc) should be
available 2
1.33 Balance sheet and ratio analysis
should be incorporated in appraisal
frame work as per MPBF method 2
1.34 System should have separate
framework/format for credit limit
assessment under cash budget
system 2
incorporating eligibility norms and
other key features for specialised
schemes 2
1.36
System should regulate discretionary
authority (Lending) at various levels. 2
1.37 Retail Lending Schemes, various
schemes for agriculture credit, other
specialised schemes should be
parameterized. 2
1.38 Provision to specify maximum period
for any type of loan. 2
Form 8
Page 96 of 248
Loans and Advances
1.39 Provision to feed land record and
cropping pattern details etc. in case
of Agriculture advances 2
1.40 Sectorwise / Currency-wise
exposure with Security Value /
Insurance value 2
1.41 Provision for Hire Purchase and
Leasing finance 2
1.42 Provision for Project Finance draw
down schedule. 2
1.43 Proper Parameterisation for
sanctioning authorities according to
the scheme 2
1.44 Provision to modify terms of sanction
viz. rate of interest, security, margin,
interchangeability of facility and
there should be details of the
sanctioning authority (Name,
Designation etc)
2
1.45 System should handle Kisan Card
Limits, Swarojgar cards, Laghu-
udyami cards, Artisan cards etc.
(repayment-Kharif/rabi seasons,
Composite loan) 2
1.46 Availability of Commodity-wise
exposure under Selective Credit
Control System other features 2
1.47 System should define Country
Limits, Region Limits. System should
tightly integrate with the trade
finance module for automatic
updating of limits as per utilizations. 2
1.48 System should automatically make
the DP of a customer as 0 upon
expiry or non -receipt of the
documents/stock statement after the
grace day period has lapsed. 2
1.49 System should show loan products
Viz. AllBank – Rentals (Loan against
Rent Receivables) 2
1.50 System should allow
interchangeability from one fund
based limit to another and one Non-
fund based to another within overall
sanctioned limit 2
1.51 The system should capture and
generate code for various
activities/sectors as per BSR forms. 2
1.52 System should record grace periods
for submission of at least the
following: Stock statements, Book 2
debts statements, Periodical
1.53
statements, Annual balance sheets,
1.54 System
Profit andshould generate appropriate
loss statements, CMA
warning
data form.messages / letters before 2
the due date for the above
1.55 mentioned statements. Check for the
parameter to generate warning
messages / letters.
Form 8
Page 97 of 248
Loans and Advances
1.56 System should maintain and track
post sanction review details. (e.g.
documents to be reviewed,
frequency, comments etc.) 2
details of consortium / bankers
meeting details (e.g. meeting dates,
frequency, comments, next meeting
date etc.) 2
1.58 System should define criteria (user
definable) for an account going out
of order. Check for the parameters to
define the same. 2
1.59 Map and define drop – downs for
selection of sub-categories based on
type of advance selected. E.g. if the
category of advance is selected as
Priority sector advance then the
system should only show those sub-
categories that are applicable to
priority sector advances
2
1.60 Provision to Calculate the DP for
multiple securities having different
margins linked to a particular a/c and
vice versa (e.g.different margins for
stocks & book debts of different age
wise).
2
1.61 System should record sanction of
Overdraft limits to certain accounts,
as secured and unsecured and
capture the sanctioning limit. 2
1.62 System should maintain and monitor
the exposure to sensitive sectors.
Sectors should be paramaterised. 2
1.63 System should Parameterise adhoc
sanctions 2
1.64 Facility to generate individual Branch
reports at any interval at the Zonal
Office/ Head Office level. 2
1.65 Facility of the system to upload data
received in any electronic format
from branches outside the core
banking system for consolidation
and amalgamation for reporting
purposes.
2
1.66 Facility to support manual feeding of
data at the Zonal office for
consolidation and amalgamation of
data received from manual
Branches. 2
1.67 System should have provision of
classification Priority Sector
Advances as per MPR formats
(giving outstanding and
disbursement) of the Bank. 2
Form 8
Page 98 of 248
Loans and Advances
1.68 Facility for drawing-up
projected/estimated balance-
sheet/P&L statement on the basis of
past actual for last two years or more
pertaining to the borrower. 2
1.69 While assessing working capital
requirement of a specific project,
system should have facility to access
some other a/cs of established unit
of the same sector can assist in
realistic assessment.
2
1.70 Facility for generation of unique loan
a/c no on the basis of its nature and
function for doing changes according
to the user's choice. 2
1.71 Facility to define status of an entry in
any a/c such as " New Transaction",
" Amendment " or " Deletion of
transaction" along with the
corresponding effect on outstanding. 2
1.72 Automatic transfer of customer's
profile along with the details of loans,
sub limit, value of security, etc at the
time of transfer of any a/c from one
branch to another. 2
1.73 Provision to link various loan
schemes with insurance coverage
wherever provided for in the Bank’s
scheme. There should also be
provision for paying the insurance
premium as per terms of the policy
(either one-time premium payment
or yearly renewal) & provisions of
the scheme. E.g. PAIS,
Grihamangal, Crop Insurance etc.
2
1.74 System should link standard remarks
/ add new remarks for comparison of
actuals v/s benchmarks, estimates,
projections etc.
2
1.75 System should highlight criteria for
not meeting the benchmarked levels. 2
1.76 System should interface with other
3rd party systems for downloading
data and facilitate industry analysis /
data, risk analysis, trends in
industries etc. 2
1.77 System should print the proposal
along with system generated
remarks / comments in the format
and stationer as desired by the
Bank. 2
1.78 System should support definitions of
band of variances differently for each
ratio under industry comparison. 2
Form 8
Page 99 of 248
Loans and Advances
1.79 Powerful on-line enquiry utilities
allows different access path to the
information which includes the
current loan details as well as the
historical information. 2
1.80 To adjudge any deviation from
Bank’s lending policy at the time of
sanction/review of loan. 2
1.81 System should support refinance
(NABARD/SIDBI). 2
1.82 system sould support syndication of
loans. 2
1.83 system should support subsidy
received. 2
1.84 system should support consortium
advance. 2
1.85 system should support securitization
of future receivables. 2
1.86 system should support multiple
financing. 2
1.87 system should support Deferred
payment guarantee. 2
1.88 system should supports multi-
divisional companies under
same/different consortium with
different method of lendings. 2
1.89 system should support factoring
/Pass through Certificate/
Participation certificate. 2
1.90 system should support securitization
through SPV 2
1.91 system should support the venture
capital 2
1.92 system should support take out
finance 2
1.93 system should support Inter Bank
Participation Certificate 2
1.94 system should support maintenance
of Trust and Retention
account/ESCROW mechanism. 2
2 DOCUMENTATION
2.1 Provision for checklist of documents
for various purposes or activities/
Parameterisation of Loan Document
generation. document should
marked as mandatory/non-
mandatory. system should restrict to
proceed if mandatory documents are
not received.
2
2.2 -System should by pass document
marked as mandatory by higher
authority. 2
2.3 System should migrate required
data from loan application/process
note to loan documents 2
Form 8
Page 100 of 248
Loans and Advances
2.4 System should link to the
documentation management module
for documentation & monitoring. 2
2.5 System should capture details &
print standard loan documents in the
prescribed format as desired by
bank. (Hyp.deed, G’tee deed, P/N,
Sanct.Letter etc.) 2
2.6 Provision for Borrower wise details
of various documents executed
along with date of the execution and
also due date for renewal of
document. System should define
grace x-days for document renewal.
2
2.7 System should accept opening of the
account after the execution of
mandatory documents. 2
2.8 System should not accept the initial
debit transaction without due
authorization by the appropriate
authority. 2
2.9 Realisation of cheque return charges
along with applicable taxes to be
debited by the system itself and
related debit advice for customer as
well as the corresponding voucher to
be generated simultaneously.
2
2.10 Holding levels accepted for sanction
of limits vis-à-vis the actual position
at the year end to be generated. 2
2.11 In case of schematic lending the
eligibility criteria including the
quantum of eligible finance to be
generated after entering the relevant
informations/particulars furnished by
the proponent through loan
application form.
2
2.12 In case of project finance detailed
data related to locations and cost of
project, means of finance, schedule
of implementations, comparisons of
progress/ status of implementations
are to be maintained in the system
and report generation facility at any
point of time.
2
2.13 In case of project finance year-wise
accepted DSCR including particulars
of repayment obligations to all the
creditors individually should be
maintained. 2
Form 8
Page 101 of 248
Loans and Advances
2.14 In case of project finance monitoring
and review of actual DSCR position
as at the year end including inter-alia
particulars of repayment made to
different creditors vis-à-vis over due
position as also variations occurring
due to change in the rate of interest
should be generated as and when
required.
2
2.15 In case of Project finance value of
Bank’s share in the security (net
block excluding evaluation) created
out of the project finance considering
outstanding liabilities with different
project financers to be made
available from the system.
2
2.16 Facility for calculating asset
coverage ratio to assess the security
coverage of the proposed loan
asset. 2
2.17 Provision to allow multiple
disbursements from a same account
simultaneously against single debit
by means of issuance of Bankers
cheque / DD / RBI cheque / RTGS /
Credit advice.
2
2.18 System should migrate required 2
2.19 data from loan application
Parameterisation /process-
of Loan Document 2
note to
2.20 generation.loan documents.
all filled in Loan documents should
be generated based on application
and sanction terms 2
3 SECURITY
3.1 There should be a system for
recording primary security &
Collateral Security with details of
each security viz. date of valuation,
value of security etc. These
securities should be categorized as
per regulatory (BASEL –II) norms so
that risk weightage can be calculated
properly viz loan against mortgage of
residential properties, loan against
mortgage of commercial property
etc.
2
3.2 There should be a distinct system for
recording eligible financial collateral
as defined by RBI (Basel-II). 2
3.3 Exclusive Security maintenance
system with parameters of margin,
depreciation rate, appreciation rate,
period for valuation etc globally
maintained 2
3.4 Provision to revaluate the securities
periodically. 2
Form 8
Page 102 of 248
Loans and Advances
3.5 Loan against equity:- Facility to store
database on permitted shares and
verify shares offered against
database in relation to scrip, margin,
etc. 2
automatically carrying out the
following activities as and when
specified by the user :- 2
3.7 Recalculate drawing power - as per
cycle, based on input of market
value of portfolio or on withdrawal of
the securities. In case of reduction in
drawing power, update the same in
account.
2
3.8 If amount due within new drawing
power, compute interest and
generate interest intimation advice 2
3.9 If not, generate requisite deposit
advice or additional securities
requirement advice 2
3.10 Update Account with amount
deposited or record additional
securities offered. 2
3.11 Periodical revaluation on mark to
market basis should be done in case
of those securities which are largely
affected by market factors viz.
Shares etc. 2
3.12 Security-wise exposure should be
available at branch / HO level. 2
3.13 Proper Drawing power calculation
taking into account the Stock
statement, Book debt statement,
Shares, Properties etc. 2
3.14 System should show value of
collaterals, margin and O/s
Liabilities. 2
3.15 System should link securities
charged to particular account as
continuing security for other limits.
e.g Security of Machineries charged
to Term loan taken as a continuing
security for BG/LC/WC limits.
2
3.16 System should warn for valuation of
Stock /Book debts/ Machinery/
Building etc. when next valuation
falls due. 2
3.17 System should prompt and update
Insurance premiums for loans
against LIC policies. 2
Form 8
Page 103 of 248
Loans and Advances
3.18 System should define criteria for
(user definable) conduct of stock
audit (e.g. for accounts with sanction
limit of over defined amount etc).
Details to be captured are: Stock
audit date, Name of Chartered
Accountant / Company or audit firm,
Stock Audit sanction date, Next audit
date, Status of audit report (e.g.
closed, open etc.), Action points /
comments by the auditor.
2
3.19 System should parameterize
frequency of stock audit as per
Bank’s policy. 2
3.20 System should define asset code for
classification of assets based upon
user definable parameters (for
example Asset Code 'X' as standard
for delinquent for less than 90
days,). Further the system should
have the facility to define sub - asset
codes within a defined asset code
e.g. under standard assets sub -
asset code regular /irregular / out of
order / weak standard etc.
2
3.21 System should define the number
(parameterisable) of days upon
which the system should generate
warning messages / print reports for
accounts out of order / irregular
based upon user definable criteria
e.g. display warning messages for
those accounts where interest is
outstanding for x number of days.
Check for the existence of the
parameter.
2
3.22 Provision to enter details of the
goods pledged in case of advance
against pledge and other details
based on the nature of the a/c and
also link of the amount of loan with
the value of goods security.
2
3.23 MARGIN
3.24 Collection of Margins prior to release
of loan. 2
3.25 Facility of marking lien on the Margin
amount / subsidy received from
various agencies in lieu of margin,
where the margin/subsidy is to be
maintained separately till
continuation of facilities viz LC, BG,
Govt. sponsored schemes etc.
2
3.26 Provision to promptly release the
Margin amount collected by the bank
to keep in lien account, on discharge
of liability by the customer. 2
Form 8
Page 104 of 248
Loans and Advances
3.27 Provision to prompt the availability of
Margin amount collected by the
bank while classifying as NPA a/c. 2
3.28 Handling of Refinances if any. 2
3.29 Proper system to maintain ECGC
covers 2
3.30 Display facility of total margin
amount along with the details for
each type of loan product / scheme 2
3.31 Display facility of total subsidy
amounts for each type of loan
product / scheme. 2
4 INTEREST RATE
4.1 Calculate interest on Simple,
Compound and Equated installment
methods for various schemes
offered by the bank in base currency
or foreign currency 2
4.2 All types of interest/Special types
interest such as Housing loan of
staff. Interest liability should be
separately maintained so that
interest portion with rate/type of any
loan should be available. Intt. And
Principal should be separately
shown in account carrying SI such
as Staff Housing Loan.
2
4.3 A provision to apply simple interest
for a specified period and thereafter
compound interest. 2
4.4 System should define slab interest
rates at account level 2
4.5 System should link one of the slabs
in a tier to the benchmark rate, the
other slabs at actual rates or either
of the same for all slabs. 2
4.6 Calculate interest on outstanding on
a daily or monthly basis. In case of
monthly basis accounting, the user
should be able to specify which
balance should be reckoned for
example average bal, highest bal,
balance between two dates etc.
(Hsg.loan)
2
4.7 A provision to link interest rate with
Credit Risk Rating at option of the
Bank. 2
4.8 A provision to apply interest rates for
every product offered by the bank for
different currencies based upon
defined criteria e.g. type of account,
category etc 2
4.9 A provision to apply interest rate
based on RAROC. 2
Form 8
Page 105 of 248
Loans and Advances
4.10 Interest rates linked to
PLR/Benchmark rate/PTLR etc
should be related to type of account
globally. 2
4.11 Interest rates related to loan against
time deposits should change
automatically according to deposit
rate of interest on renewal of
deposit. 2
4.12 Provision to define grace/moratorium
period & recover
interest/principal/EI/EMI etc.
accordingly. 2
4.13 Back dated recalculation of interest
with/types slabs should be available
and balance to be recovered, should
be recover automatically. (This is
required OTS of NPA accounts) 2
4.14 System should define interest rates
i.e. whether linked / not linked to
benchmark rates, 2
4.15 Changing of rate of Interest
Globally/Individually
backdated/future. 2
4.16 ROI below PLR should be accepted
only for authorized loan products
accounts. 2
4.17 The penal interest should be applied
considering parameterised Penal
rate of Interest and list of
exemptions. Wherever waived, the
same should reflect in the audit trail
report to verify revenue leakage.
2
4.18 Recalculation of Interest/Penal
interest for back dated revaluation of
securities. (e.g. Intt.tobe reckoned
from first day of the month by the DP
as per the stock statement is entered
on 21st).
2
4.19 Charging of interest on withdrawals
against unclear effect of cheques. 2
4.20 system should have provision of
autocharging of commitment
charges on unutilized portion of
credit limit with flexibility for
exemption under proper
authorisation.
2
charging auto-penal interest for
delayed submission of monthly stock
statement/QIS/Renewal of limits
periodically and auto-generate debit
advice for customers.
2
Form 8
Page 106 of 248
Loans and Advances
4.22 Define instances where interest is to
be calculated as defined for that
product, scheme / account but not
be applied to the account e.g.
accounts marked as NPA accounts,
broken accounts, suit filed / decreed
loan accounts etc. The interest
accrued should always be visible at
the time of transaction processing,
authorizing etc
2
4.23 Automatic posting of interest into
“Memorandum of Interest” for non-
performing accounts (record section)
2
4.24 Provision for automatic reversal of
unrealized interest from the account
on account becoming NPA and
booking of income from URI account
on recovery in the account. 2
4.25 System should raise principal +
interest demands on due dates 2
4.26 Effect of changes in the interest
demand date and loan re payment
schedule in case of changes in
moratorium period/gestation. 2
4.27 Provision for interest receivable
account and no compounding of
current dues applicable for
agricultural loans and DRI 2
Advances.
4.28 Provision for report on interest
received during a given period
against lending under various
products / schemes/sectors etc. 2
4.29 In case of floating whether linked to
LIBOR, MIBOR- In case of LIBOR &
MIBOR system should directly
capture ROI on daily basis. 2
4.30 In case of loan against FDR- facility
to link the loan ROI to Specific
Deposit a/c (FDR rate+ …%) 2
4.31 Interest accrual Report- Details of
interest accrued but not charged
(other than NPA accounts) 2
4.32 Calculation of Prepayment penalty
with flexibility for waivement with due
authorization. 2
4.33 Provision for calculation of interest in
any loan accounts with retrospective
effect or on accrual basis at future
date and to generate report thereof. 2
4.34
Facility to capitalise interest as per
parameter set for a defined
loan(such as capitalisation of interest
in case of construction co/project) in
case of graded installment. 2
Form 8
Page 107 of 248
Loans and Advances
4.35 While applying interest in respect of
borrowers whose loan account is
distinct from the subsidy account,
the interest should be applied after
netting the subsidy amount. 2
4.36 Application of interest in case of
TOD (without any regular limit) as
and when the accounts comes in to
credit. 2
5 INSTALLMENT / REPAYMENT
5.1 Provision for fixation of equated
installments based on periodicity of
payment, viz. EMI for monthly
repayment, EHI for half-yearly
installment, EAI for annual
repayment.
2
5.2 Provision for monthly installment
computation based on concept of
“Progressive Monthly Installment”
(PMI) where monthly installments
may be less during initial period of
repayment and will be more
afterwards.
2
5.3 Provision for recovery of principal at
one frequency and Interest in a
different frequency. (Staff Housing
Loan) 2
5.4 Option to adjust EMI table with
changes in the interest slabs taking
into consideration the effective dates
for such interest rate changes 2
5.5 Different types of Interest during the
Moratorium Period. 2
5.6 Alert when customer initiated
transaction in one account which
happens to be related to NPA a/c. 2
5.7 Rebate on Interest for regular
payment . 2
5.8 Verify for Ad hoc rescheduling, for
example the customer makes a lump
sum payment of three installments at
a time in advance and wants waiving
of auto recovery of installment of
next three months, should be
possible and also not to generate
demands for next three months.
2
5.9 Provision to calculate Prepayment
charges. 2
5.10 Transfer periodical Deposit Interest
and maturity amount to Loan 2
5.11 account
Provision to re-schedule in case of
bulk payment/overdue and adjust
interest payments in the event of pre
/ part payment automatically for EMI. 2
Form 8
Page 108 of 248
Loans and Advances
5.12 Provision to define moratorium
period. Check for the parameters for
the same. moratorium period should
be defined for only interest, only
principal, equated monthly
installment.
2
5.13 System should specify any deposit
account maintained by the customer
in any branch of the Bank for the
purpose of loan recovery through
standing instruction. Verify for a loan
recovery through a standing
instruction. If it is not possible verify
the execution of the Standing
instruction.
2
5.14 On repayment, the relevant loan limit
of the customer to be updated(e.g.
OD a/c against multiple security). 2
5.15 Functionality to recover interest first
in case of partial recovery. The
system should also have the System
should apportion the installment
amount between principal and
interest .
2
5.16 Provision to adjust the loan amount
outstanding with the margin amount
if held in separate account with the
bank. 2
5.17 Provision for auto rescheduling after
moratorium / holiday period or after
final disbursement has also taken
place. 2
5.18 Post dated cheques maintenance
and tracking a/c wise. 2
5.19 EMI to be re-fixed automatically- In
case of change in ROI depending
upon remaining period of repayment.
2
5.20 Facility to generate an EMI schedule
giving break up of principal, interest
and balance o/s for the tenure of the
loan. 2
5.21 Facility for adjustment of payment
towards - a) Interest first, b) principal
first, c) other charges first. 2
6 TRANSACTIONS
6.1 The schedule of disbursement (to be
disbursed in full at a time or
disbursed in given number of
phases), mode of disbursement etc
should be parameterised. 2
6.2 Display arrears charge / commission
if any, at the time of transaction/
posting/ authorization etc.
2
Form 8
Page 109 of 248
Loans and Advances
6.3 Recover charges applicable to an
account when the account has a
favorable balance and store the
unrecovered portion and recover the
same as soon as the account comes
to favorable balance.
2
6.4 There sould be provision to modify /
waive any charge for a particular
customer as sometimes Bank
charge less than the normal rates for
various services or even waive the
same in case of high value
customers.
2
6.5 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
6.6 Ability of the system to define
charges to be effected in the
customers account based on the
source of the transaction e.g.
branch, delivery channels etc. 2
6.7 Inter-operability of group/borrower
limit to various accounts/account
level - security, margin, , for each
limit and overall limits, - transactions
to first check with respect to
individual limits and later by overall
limits - flashing of messages on limit
expiry, document expiry, insurance
expiry,under insurance, stock
statement non-submission after the
due date – provision to apply penal
interest on any of these conditions
2
6.8 Provision to Collect Interest Tax or
any other type of predefined tax.
Proper accounting of such Taxes for
verifications. 2
6.9 Value-dating for the transactions in
respect of responding Cr & Dr
advices. 2
6.10 Provide details of
commission/Interest amounts etc
received from one account to decide
value of connection in order to
consider concessional service
charges.
2
6.11 Facility for providing alarm on
exceeding DP, sanctioned
limits/excess drawings in any
account at the time of doing any
transaction. 2
Form 8
Page 110 of 248
Loans and Advances
6.12 Facility for on-line approval for
allowing such facilities from the
higher and appropriate authority.
This authorization must be by a
parameterised level of user
authority.
2
adjustment of balances in various
Loan accounts against which deposit
accounts are pledged on its due
dates and adjust the balances if any
from the credit balances in
CC/SB/CA of the borrower.
2
auto charging of service charges
including service tax as per Bank’s
guidelines on various
products/services. 2
auto debit of ECGC premium on
export credit and preparation of pay-
order or draft in favour of ECGC on
monthly basis. 2
payment of maturity proceeds of
FDR/RD pledged to other branches
on due dates for adjustments of their
loan accounts. 2
automatic generation of debit/credit
advices to the customers at the time
of day-end. 2
6.18 Limit tracking and validation at the
time of transaction positing 2
6.19 System should prompt pending
insurance renewal and other type of
obligations of the Customers. 2
6.20 System should have provisions to
add comments / notes for all
transactions referred to higher
authorities for approvals . 2
6.21 Provision to notify the
account(borrowal/deposit/others) in
which operational loss has occurred
along with provision to sub-
categorise the respective
transactions depending upon the
loss event type.
2
7 REPORTS
7.1 Provision to generate report on
sanction made by respective
sanctioning authority at Branch /
Controlling office level during a
month or any given period (MDA
statement).
2
Form 8
Page 111 of 248
Loans and Advances
7.2 Provision to generate disbursal
report for a given period for various
products / sectors / schemes. There
should be flexibility to generate
report in desired manner viz.
branchwise / zonewise /statewise.
2
7.3 Provision to generate outstanding
balance report for a given period for
various products / sectors /
schemes. There should be flexibility
to generate report in desired manner
viz. branchwise / zonewise
/statewise.
2
7.4 Provision to generate overdue report
for a given period for various
products / sectors / schemes. There
branchwise / zonewise /statewise.
2
outstanding NPA as also provision
and uncharged interest on a given
date for various products / sectors /
schemes. There should be flexibility
to generate report in desired manner
/statewise/borrowerwise.
2
7.6 Provision to generate report on fresh
slippage to NPA during a given
period for various products /
sectors / schemes. There should be
flexibility to generate report in
desired manner viz. branchwise /
zonewise /statewise/borrowerwise.
2
accounts showing warning signals /
threat for slippage to NPA as on a
given date for various products /
zonewise /statewise/borrowerwise.
2
7.8 Provision to generate AOD/Balance
confirmation / Insurance reminders. 2
7.9 Provision to generate cheque return
memo in case of return of cheques. 2
7.10 Provision to generate Interest
due/Installment arrears notices. 2
Form 8
Page 112 of 248
Loans and Advances
7.11 Provision to generate statuary/
regulatory Reports/Certificate to be
submitted to RBI/Govt. (BSR,DCB,
SCC, LBR, Govt. sponsored
schemes, Special Agricultural Credit
Plan, Minority Community, Report on
Kisan Credit Card, SSI without
collateral security, CGTSI, SGSY,
PMRY etc.)
2
7.12 Provision to check for interest/loans
not recovered due to insufficient
balance, the system automatically
generate a report showing all
account balances of the customer so
that the management can decide on
recovering the loan from another
account of the customer. Check for
the report.
2
Industrywise exposure / commodity-
wise exposure. Flexibility to classify
the industries as per Bank’s lending
policy to generate report on desired
line.
2
7.14 Provision to generate facilitywise /
productwise income generated. 2
7.15 Provision to generate report on the
Limitation dates of loan documents
according to the period. Till proper
action is initiated with proper
authentication the entries should
reflect in the list on a daily basis as
one of the day-end report.
2
7.16 Provision to generate Interest
Certificate for loans, Letter of thanks,
Letter of frequent cheque return,
Limit due date, Non-submission of
stock/Book debt/ QIS/ Annual return/
CMA date, Balance confirmation
2
7.17 System should generate a report as
on a particular date / range of dates
on exercise of delegated powers by
each of the Sanctioning authorities
during their entire tenure in a
particular branch, department, office
etc. for monitoring as to whether the
sanctioning authority has exceeded
delegated powers and to highlight
such discrepancies along with the
details of the entire transaction.
2
Form 8
Page 113 of 248
Loans and Advances
interest earnings/commission for a
given period for various products /
zonewise /statewise.
2
amount potentially written-off during
a given period for various products /
zonewise /statewise.
2
7.20 Provision to generate report on LC
devolved & BG invoked during a
given period giving therein date of
devolvement / invocation, amount of
devolvement / invocation, recovery,
present dues. There should be
zonewise /accountwise.
2
expired BG but not deleted from the
system as on a particular date,
giving therein date of expiry, amount,
name of the beneficiary. There
branchwise / zonewise /accountwise.
2
outstanding unsecured advances as
on a given date. There should be
zonewise /accountwise/productwise/
sectorwise/asset classificationwise
/riskgradewise.
2
outstanding advances as per asset
classification & provision there
against as on a given date. There
branchwise / zonewise
/accountwise/productwise/
sectorwise/asset classificationwise
/riskgradewise.
2
7.24 Provision to generate advance sheet
of the branch as on a given date and
consolidation of the same –
zonewise/bank as a whole. 2
Form 8
Page 114 of 248
Loans and Advances
7.25 Provision to generate conductsheet
of various a/cs containing there in all
relevant parameters such as name
of the a/c, facilitywise credit limit &
present o/s, average utilization,
credit turnover in the a/c, maximum
& minimum balance, overdue
interest / installment, devolvement or
invocation of LC or BG / returning of
cheques or bills etc. for a given
period of time, there should be
flexibility to generate reports in
desired manner viz report for a
particular a/c, report for group of
borrowers under given range of
credit size / product / sector /
industry / a combination of above
parameters. There should also be
flexibility to modify the format of
conductsheet in line with various
returns of the Bank(e.g. E1, E2, E3,
post sanction reporting card) for this
purpose to be parameterized.
2
7.26 Provision to generate reports on
interest ratewise deployment of
credit (below PLR, At PLR, Above
PLR) as on a particular date for
branch/zone/bank as a whole. There
should also be flexibility to modify
such reporting formats to get desired
statistics viz productwise
/sectorwise/industrywise/riskgradewi
se etc.
2
7.27 Provision to generate reports on
interest ratewise disbursement of
credit (below PLR, At PLR, Above
PLR) during given dates for
branch/zone/bank as a whole. There
should also be flexibility to modify
such reporting formats to get desired
statistics viz sanctioning
authoritywise/ productwise
/sectorwise/
industrywise/riskgradewise etc.
2
sectoral deployment of fund on RBI
format. 2
deployment of fund under sensitive
sector. 2
Form 8
Page 115 of 248
Loans and Advances
migration of loan assets, either
upward or downward over the risk-
rating scale during a given period of
time. There should be flexibility to
generate reports in desired manner
viz report for group of borrowers
under given range of credit size /
product / sector / industry / a
combination of above parameters.
2
7.31 Provision to generate watch list as
per globally parameterised norms
(such list may include accounts
graded as high risk and also a/cs
identified as PNPA). There should
be flexibility to generate reports in
desired manner viz report for group
of borrowers under given range of
credit size / product / sector /
industry / a combination of above
parameters.
2
migration of standard loan assets
from a particular risk-grade to default
grade. There should be flexibility to
generate reports in desired manner
viz report for group of borrowers
under given range of credit size /
product / sector / industry / a
combination of above parameters.
2
7.33 Provision to generate report on yield
on advances as on a given date.
There should be flexibility to
generate report in desired manner
/accountwise/productwise/
sectorwise/ riskgradewise.
2
generating exceptional transactions
list of advances at the day-end as
also capturing daily list register. 2
borrowers enjoying multiple credit
facility and / or enjoying credit facility
from more than one branch. 2
recasting of statement of accounts
notionally on the basis of changed
ROI retrospectively and
refunding/charging difference of
interest thereof.
2
parameterise the quarterly review of
accounts. 2
Form 8
Page 116 of 248
Loans and Advances
capturing drawing power register. 2
generate data on cash withdrawal
frequency in CC account during a
particular period. 2
booking income based on mercantile
system. 2
printing (forwarding schedule) for
collection items (Cheques, Bills ). 2
capturing various loans granted to a
single or multiple borrowers against
the same security as primary or
collateral. 2
parameterising as well as automatic
generation of monthly progress
reports on priority sector credit. 2
generation of no-dues certificate in
case of closure of loan account. 2
generating facility as well as limit
wise outstanding certificate to
customers as and when sought. 2
7.46 Facility for providing the list of
defaulters and actions if any taken
against them (to be displayed with a
flash). 2
7.47 Account wise master Report
containing all the relevant details. 2
7.48 Security Register to be captured
from relative security data. 2
7.49 On line enquiry abount - a) Product
specific EMI, b)O/s Balance, c)
Overdue installment / interest,d) all
accounts pertaining to customer be
listed altogether. 2
7.50 Flexibility for generating designable
reports. 2
7.51 Account-wise particulars of recovery
in w/off accounts 2
7.52 System should be capable of
retaining pre- audit position
submitted by the bank along with
post audit position after incorporating
changes as per MOC. 2
7.53 System should generate warning
signals for other linked accounts
when repayment is overdue in one
a/c. 2
Form 8
Page 117 of 248
Loans and Advances
7.54
System should generate warning
signals /alerts x days before
accounts coming under technical
NPAs due to non submission of
stock statements, review of a/c, in
excess of certain specified period. 2
7.55 Facility in the system to arrive at the
compromise amount/ calculation of
bench mark sum as per the
parameters of the particular module. 2
7.56 System should intimate the
branches/ Zos for the acceptance/
rejection of proposals in respect of
loans/compromise/ w.off proposal
etc. 2
7.57 Provisional as well as actual
certificate on interest application in
Housing Loan account for income
tax purpose. 2
maintenance of stock register with all
previous and new details of
stock/drawing power. 2
8 AUDIT
8.1 Audit module at ZO/HO should be
able to look into the details of the
new loan accounts 2
8.2 HO should be able to browse
exceptional transactions. 2
8.3 HO should be able to review/browse
waiver of Income at branch levels
with the details of the authorized
persons. 2
8.4 System should generate a report
showing excess over limit, number of
time over drawn, TOD, number of
time bills purchased without limit for
all types of loan / advance account
as on a particular date / range of
dates for a particular party / group.
2
8.5 System should generate list of audit
irregularities / adverse remarks
made by RBI inspectors in each
account and also gauge the overall
adverse impact of such irregularities
on the account based on weightage
(parameterisable) assigned to each
type of irregularity
2
9 CREDIT MONITORING & NPA
9.1 MANAGEMENT
System should classify operative
accounts like SB/CA where ad-hoc
(TOD) remaining unadjusted and
Bills/cheque purchased and credit
cards dues (without limit) after
specified time can be classified as
NPA.
2
Form 8
Page 118 of 248
Loans and Advances
classify all borrowal a/cs of a
customer as NPA if any account of
that borrower turns NPA. 2
9.3 If an NPA account becomes regular
at a later date, the other accounts
classified as NPA by virtue of being
accounts of the same borrower,
should automatically become regular
accounts if otherwise in order.
2
9.4 System should provide Listing of
accounts, which are standard, but
are classified as NPA by virtue of
one or more account/s of the same
borrower becoming NPA. 2
9.5 System should support reporting of
all or selective NPA accounts with
multiple selections like Region-wise,
Branch-wise, Asset-wise, Facility-
wise, Sector-wise, Segment-wise,
etc. in any order of preference.
2
9.6 System should support breaking up
of balance outstanding into different
blocks like
secured/unsecured/guarantee
portions as required, taking into
account other particulars available.
2
showing the NPA position as
reported by branch as well as after
incorporating the
suggestions/changes suggested by
Auditors at various levels without
overriding the earlier position.
2
classifying SA/SSA as DF-3/Loss
Account directly where the security 2
available is less than 5% /10%
9.9 System should support identifying a
(preferably parameter enabled) of
set of accounts that need not be
the outstanding balance.
classified as NPAs, despite being
NPA as per recovery norms. (D/L
against NSC/FDR/LIC, Staff loan) 2
9.10 System should support storing the
MOI related particulars without
disturbing the base NPA data. 2
9.11 System should support in selective
cases, (depending on the nature of
liquid securities), NOT transferring
the account to NPA even if interest is
not paid, so long as the balance
outstanding is less than the value of
the security minus margin if any.
2
9.12 Provisioning for Standard Assets at
Head Office level. 2
defining Country Risk Rating. 2
Form 8
Page 119 of 248
Loans and Advances
9.14 System should support putting flag
for Stand-Still Clause which would
be helpful for Corporate Debt
Restructuring. 2
9.15 System should keep track of erosion
in security value and classification of
asset thereof. 2
9.16 system should support
classification / Re-classification of an
account consequent to rescheduling. 2
9.17 In case of Export project, the asset
classification to be done only after
one year if the payment/realization is
held up for reasons other than non-
payment. 2
9.18 Classification of accounts and
provisioning for accounts where
advances are sanctioned against
central Government Guarantees
while Guarantee is invoked. 2
9.19 system should support distinction
between advances granted before
rehabilitation and after rehabilitation
for purpose of classification /
provisioning. 2
9.20 moratorium period for repayment of
interest if any in case of accounts
under rehabilitation. 2
9.21 system should keep record of
cumulative as well as progressive
provisioning. 2
9.22 Based on present classification,
forecasting with projected asset
classification and projected
provisioning for any given future
date. 2
9.23 system should be capable of
reversing the interest from P/L, if an
asset is subsequently reclassified by
the auditors. 2
Form 8
Page 120 of 248
Loans and Advances
classification of the accounts as NPA
as per prudential norms for
example : (i) if Interest and/ or
installment of principal remains
overdue for a period more than 90
days in respect of a term loan, (ii)the
account remains out of order for a
period of more than 90 days in
respect of an Overdraft/Cash Credit,
(iii) The bill remains overdue for a
period of more than 90 days in the
case of bills purchased and
discounted, iv) Interest and/or
installment of principal remains
overdue for two harvest seasons but
for a period not exceeding two half
years in the case of an overdue
granted for agricultural purposes, or
v) any amount to be received
remains overdue for a period of
more than 90 days in respect of
other accounts.
2
9.25 system should classify borrowal
accounts into SSA/DA/LA
automatically as per age of NPA. 2
9.26 System should automatically
calculate the required provisioning
for SSA/DA-1/DA-2/DA-3/LA. 2
9.27 System should provide provide for
Sectoral Deployment Codes like
Agriculture/ SSI/ OPS/ Medium and
Large Scale Industry/Wholesale
Trade/ Govt. Sponsored
Schemes/Retail Lending and other
sub-classifications.
2
9.28 System should retain the details
relating to provisioning already made
in respect of SSA/DA/LA while
upgradation of NPA and also
recalculation of provision required. 2
9.29 system should credit the interest
accrued, if any on Term Deposits to
the loan accounts against FDR.
Also, the TD itself on maturity if
consented. 2
9.30 System should provide for global
portfolio of NPA reporting. 2
9.31 System should allow reduction in
amount of prudential write off from
the outstanding gross advances and
gross NPAs to eliminate any
distortion in the quantum of NPAs
being reported.
2
Form 8
Page 121 of 248
Loans and Advances
9.32 System should warn that the
account/ limit will become NPA in
case irregular drawings are
permitted in the account for a
continuous period of 90 day norms. 2
9.33 System should provide for automatic
deduction of installments/interest
from credit balances to the loan
accounts at the end of
moratorium/gestation periods. 2
9.34 In case of take over of an asset from
outside the institution, system should
retain the actual date of NPA as well
as the date of take over of the asset. 2
9.35 system should provide for deducting
the amount lying in Interest
Suspense Account/URI/Other credit
balances from the relative advances
and thereafter provisioning to be
made as per the norms.
2
9.36 System should calculate provision
required to be made for NPA after
the realizable value of the securities
is deducted from the outstanding
balance in respect of the amount
guaranteed by DICGC /ECGC.
2
9.37 In case the advance is covered by
the CGTSI (credit guarantee trust for
small industries) 2
9.38 Guarantee and becomes NPA, no
provision need be made towards the
guaranteed portion. The amount
outstanding in excess of guaranteed
portion is to be provided for. System
should take care of this aspect
2
9.39 system should generate all the NPA
related year end schedules, statutory
returns etc. to RBI and other related
statements automatically on their
due dates. 2
importing the presently available
NPA data at our bank and can be
migrated to the new software. 2
compilation of comprehensive data
region-wise, branch-wise in respect
of NPA/MOI/Provisioning etc. at one
go, which may be required by the
Statutory /Concurrent Auditors.
2
9.42 System should provide aggregate
amount of prudentially written off and
Book Balance in case part of the
NPA is written off. 2
Form 8
Page 122 of 248
Loans and Advances
9.43 System should calculate interest on
simple or compound basis at the
specified rate of interest on
aggregate amount of MOI and book
balance. 2
9.44 System should calculate the amount
of “sacrifice” as per the recovery
policy (Notional amount due less
compromised amount) 2
9.45 System should provide for down
payment of X% and monthly
installments for the remaining Y%
with PLR linked rate of interest. 2
9.46 System should be capable to
parameterise the Module Approach
for compromise cases. 2
compromise proposal /
memorandum to be placed before
the appropriate sanctioning authority
as per the recovery policy. 2
9.48 System should provide
comprehensive report of NPA
accounts on the basis of size/ age/
sector/ segment / scheme-wise,
either with or without including MOI. 2
appropriate any recoveries made in
NPA accounts as per bank’s
recovery policy for eg. firstly towards
reduction of balance in NPA,
secondly towards reduction of
balance held in MOI and lastly
towards interest.
2
9.50 System should split balances in NPA
into different blocks like Secured/
Unsecured/ Guaranteed balances
depending on extent of security
available and other particulars
available in the account master.
2
9.51 System should recalculate interest
based on defined parameters on
decreed and compromised proposal
accounts as the terms of the decree /
compromise terms. 2
9.52 system should arrive at a
compromisable amount across
multiple schemes given the interest
details for NPA accounts / any other
method of calculation as desired by
the Bank.
2
Form 8
Page 123 of 248
Loans and Advances
9.53 System should generate appropriate
warning messages / letters x number
of days (parameterisable) before the
due date for submission of stock
statements and date of expiry of
documents. Check for the parameter
to generate warning messages /
letters.
2
9.54 System should automatically apply /
recover penal interest for out of
order accounts as defined in the
charges / commission module.
Check for the availability of the
feature.
2
9.55 System should identify the account
status transfer / retransfer
information (E.g. Date on which the
account was transferred from
doubtful to loss etc.) 2
messages / alerts in respect of
accounts coming under technical
NPA's, due to overdue reviews,
stock statements in excess of x
(parameterisable) months vintage,
valuation reports in respect of
collaterals being in excess of 3 years
vintage.
2
9.57 System should generate list of
accounts going out of order /
frequency of such out of order
position, at any given point of time. 2
9.58 System should generate list of
accounts wherein adhoc / overlimit /
TOD sanctioned, along with
frequency of such sanctions in each
account, due date for regularisation
and warning message regarding
overdue position.
2
warning messages about frequent
(parameterisable) return of cheques
in a particular account. Check for the
parameter to specify the number of
returns after which an alert is to be
generated.
2
9.60 System should verify whether an
account has been referred to CDR
mechanism or BIFR and generate
statements of such accounts with
other desired parameters (user
definable).
2
Form 8
Page 124 of 248
Loans and Advances
9.61 System should generate list of audit
irregularities / adverse remarks
made by RBI inspectors in each
account and also gauge the overall
adverse impact of such irregularities
on the account based on weightage
(parameterisable) assigned to each
type of irregularity
2
9.62 System should analyses movement
in various financial parameters over
the past period and forecast the
prospects of the account in terms of
Asset Code for the next six months
based on the analysis.
2
9.63 System should group accounts
under different asset classification
e.g. NPA, sub - standard, loss etc.
under particular account heads,
industries, sector / sub - sector,
credit ratings, interest rates etc. e.g.
NPA's under Cash Credit Accounts
2
9.64 System should generate a branch -
wise list of NPA accounts (with the
details as defined by the Bank)
beyond and cut - off amount as on
any date / range of dates 2
9.65 Ability to record receipt of NPA
review statements and to
automatically update the next review
dates. Further the system should
automatically generate warning
messages and escalate the matter
upwards as defined in the event the
review statements have not been
submitted on time. (Period to be user
definable). Check for support of this
feature (e.g. BIFR/CDR).
2
9.66 System should allow the credit /
recovery/ credit operations
department to enter steps /
suggestions / advice to be taken by
the branch for each loan / advance
which has either gone bad or on the
verge of going bad. (Check for the
support this feature).
2
9.67 System should identify units as sick
units and maintain them under
nursing program with all details as
desired by the Bank 2
9.68 System should define sanctioning
authorities for compromise / write -
offs based upon amounts, customer,
type of loan etc. Check for the
support of the feature. (Discretionary
authority)
2
Form 8
Page 125 of 248
Loans and Advances
9.69 System should capture the details of
the compromise / write - off as
desired by the bank. Check for the
support of the feature. 2
9.70 System should capture the
recommendations of the
compromise committee. Check for
the support of the feature. 2
9.71 System should intimate the
branches / regional offices for the
acceptance / rejection of the
compromise / write off. Check for the
support of the feature. 2
generate reminders where the
compromise amounts are due
(period to be parameterisable).
Check for the support of the feature. 2
9.73 System should generate various
letters, reports, statements in the
desired formats related to
compromise / write – offs. Check for
the support of the feature. 2
9.74 System should specify the NPA
targets, branch - wise , region wise
etc. System should compare the
actual with the target and highlight
and print a report of differences
along with the percentage and
amount difference. Check for the
support of the feature.
2
9.75 System should specify targets for
recovery and benchmark them
against the actual and highlight
difference. Check for the targets to
specify the recoveries. 2
9.76 System should track and display
status of claims on the Bank not
acknowledged as debts. 2
9.77 System should store date of posting
of cases and a short description of
court proceedings and next posting
date as well as particulars of
recovers if any. 2
9.78 System should support partial write-
off. 2
9.79 System should maintain a master list
of lawyers (City wise/Region wise)
for each type of subject matter eg.
Criminal, Civil, DRT, High Court 2
9.80 System should mark accounts
referred to BIFR 2
Form 8
Page 126 of 248
Loans and Advances
9.81 System should classify accounts as
“Suit Filed” as defined in the account
hold and restriction module for the
particular type of account, product /
scheme. Further the system should
be able to capture the details for the
suit filed case such as name of the
lawyer, case presentation date,
additional notes, lawyers notes etc.
for each suit file account, success
rate for each case. Further Classify
the suit filed account slabwise
(amount parameterised) Secured/
Unsecured suitfiled.
2
9.82 Provision to alert system for due
date of court proceedings. 2
9.83 Latest position of suit filed cases,
decreed cases, value of security etc. 2
monitor/conduct the account for
operation on reduction basis
whenever recovered. 2
maintenance of ledger balance and
record sections in NPA accounts
etc. and appropriation of recoveries
and calculation of
notional/uncharged interest in NPAs.
2
monitoring on the basis of
annual/quarterly targets under
various key parameters vis-à-vis
achievement thereof. (advances
/NPA reduction/derocgnised interest/
write-off)
2
maintaining write-off accounts and
notional interest along with history. 2
maintain relevant data pertaining to
certain key performance levels
based on which limits are sanctioned
and also to monitor variations on
those at the year end or at any point
as desired.
2
9.89 Automatic classification of accounts
in to NPA based on overdue position
for term loan, cash credit etc. and re-
classify to performing accounts on
payment of overdues. 2
9.90 system should have provision to
calculate notional interest to arrive at
amount of sacrifice as and when
required in connection with
compromise proposals. 2
Form 8
Page 127 of 248
Loans and Advances
9.91 Provision for calculating delayed
payment interest of the delay in
repayment of dues as per the terms
of sanction of compromise proposal. 2
9.92 Provision to calculate future interest
where the compromise sum is
payable over a period of time in
installment. 2
9.93 System should identify the account
eligible for action under SAROFA
and serving of 60days notice,
possession notice and notice of sale.
2
9.94 Provision to process compromise
proposal as per various compromise
modules of Bank for placing before
the competent authority. It should
take in to account partial written-of
balance if any along with ledger
balance in such compromise
proposal.
2
identify and generating requisite
information required on accounts
eligible for sale to asset
reconstruction companies.
(ARC/ACRIL)
2
9.96 Generation of branchwise / zonewise
/ bankwise Ann. A/ Annx- B slabwise
outstanding balances with provision
to modify as per MOC suggested by
the Auditors. 2
9.97 Record of Suit filed accounts with
provision to classify based on age,
amount, suit filed, decreed,execution
filed 2
9.98
Follow up of Suit filed/ DRT cased
-a) Name of the court, b) Suit No and
amount, c) Ledger Balance, d) Name
of the Advocate and Address, e)
Status of Suit, f) Details of legal
expenses, g) next date with
provision to give advance
information on daily basis prior to the
date of suit. 2
9.99 Identification of accounts eligible for
filing DRT suits by clubbing all the by
all the facilities. 2
9.100 Identification of accounts eligible for
waiver of legal action and
preparation of proposals for placing
before the competent authority 2
9.101 Identification of eligible accounts for
write off and preparation of
proposals for placing before the
competent authority 2
Form 8
Page 128 of 248
Loans and Advances
9.102 Proposal for Write off in Approved
Compromise cases 2
9.103 Automatic credit in the concerned
a/c on approval of w/off proposal by
the competent authority 2
9.104 Generation of consolidated
statement of suit filed accounts 2
9.105 Generation of consolidated
statement of DRT Suit a/cs. 2
9.106 Generation of Weekly statement of
NPA reduction / recovery 2
9.107 Generation of Monthly progress
Report on NPA management 2
9.108 System should generate reminders
for the installments in compromised
sanctioned accounts 2
9.109 Facility to mark accounts as suit
filed, decreed, RC issued / DRT
cases, etc and no debit to be
permitted without proper
authorisation. 2
9.110 System should maintain the record
of claims against the Banks not
acknowledged as debts and
preparation of statements as per
Banks format 2
9.111 Facility to alarm the list of accounts
to adjust back end subsidy on
account becoming NPA. 2
9.112 System should generate report of all
the accounts of borrowers as well as
guarantors. 2
9.113 Provision to calculate the amount of
eligible incentive and payment of the
same to the enforcing agency or
recovery agent 2
9.114 Remittance of Proportionate share of
recovery to ECGC. 2
9.115 Provision and maintenance of
subsidy reserve fund (Back ended
subsidy e.g. in PMRY, KVIC,etc. 2
9.116 In Retail lending salary tied up
accounts to be grouped organization
wise for effective follow up. 2
9.117 Separate Menu for customers as per
their constitutions. 2
9.118 Record of follow up to be recorded
directly in system against individual
accounts. 2
Form 8
Page 129 of 248
Loans and Advances
9.119
At the time of data conversion the
system should compute overdue
amount and asset classification(i.e.
whether NPA, date of NPA) on the
basis of date and amount of
advance, gestation period, rate of
interest, repayment schedule and
present outstanding. 2
9.120 System should have separate
menus for different retail lending
schemes. 2
9.121 In case of advance against Bank
deposits borrowal accounts should
be clubbed with deposit a/c and both
can be managed together. 2
9.122 Details of balance confirmation
obtained as also fresh documents to
be updated. 2
9.123
Provision for calculation of sacrifice
to be borne by the bank in case of
such restructuring and by way of a
provision to be made by a bank for
this sacrifice in case of BIFR/CDR
mechanism. 2
tracking and regulating industry-wise
exposure norms both individual as
well as group. 2
cheque referred register. 2
capturing detailed position of
accounts including sublimits
allocated to other branches on the
following parameters.
9.127 1. Nature of facility. Funded or non-
funded 2
9.128 2. Type of facility. CC, TL etc. 2
9.129 3. Limits sanctioned.
Date/Amt/Authority. 2
9.130 4. Value of security.
(Primay/Collateral) 2
9.131 5. Margin (Stipulated/held) 2
9.132 6. Dr.Balance. 2
9.133 7. Nature of irregularity. 2
9.134 8. ROI 2
9.135 9. Average utilization. 2
details of consortium / bankers
meeting details (e.g. meeting dates,
frequency, comments, next meeting
date etc.) 2
Form 8
Page 130 of 248
Loans and Advances
9.137 System should define criteria (user
definable) for an account going out
of order. Check for the parameters to
define the same. 2
9.138 System should accept re-scheduling
of any loan with proper
authentication and there should be
details of the sanctioning authority
(Name, Designation etc). 2
9.139 Sacrifice of Interest amount during
rescheduling/OTS etc should have
the details of the sanctioning
authority (Name, Designation etc) 2
9.140 Verify for maintenance of history for
rescheduling 2
9.141 Record of Pre-credit visits and post
credit verification of security
including collateral security. 2
9.142 Provision to inform the amount
involved under unsecured advances
and to give a warning signal when
the stipulated limit is likely to exceed.
2
9.143 System should link daily market
price share etc. in respect of
advances granted against shares. 2
system alert for expiry of limitation
period and generate report of time
barred account. 2
9.145 Provision to bifurcate the advances
under capital market exposure into
individual, stock brokers, market
makers etc. Similarly provision to
sub categorise the advances under
real estate as – commercial real
estate, residential real estate,
builders/developers real estate etc.
2
9.146 Provision to record customer-wise
details of legal expenses paid by
debit to charges account 2
9.147 Provision to maintain record of
accounts closed through
compromise/OTS. 2
9.148 Record of failed compromise. 2
9.149 System should earmark sub-limits
allocated to non-CBS branches and
CBS branches. 2
9.150 System should generate report at
the time of day-end for bills received
for collection /falling due for payment
on next working date and PDCs to
be presented in next working day. 2
Form 8
Page 131 of 248
Loans and Advances
9.151 Provision to generate information on
various incentive schemes under
given parameters for accessing
performance. 2
9.152 System should automatically group
the data entered / uploaded under
the various account heads as
defined in the Proforma. 2
9.153 Provision to derive information of
relationship of the Borrower with
director/senior executive of the
Bank(if any). 2
9.154 System should parameterized the
review frequency for each document. 2
9.155 System should generate the
warning message x no.of days prior
to review date and parameterise
review period. 2
9.156 System should generate a letter to a
customer x no.of days prior to
review/expiry of documents
requesting him to renew the
documents. 2
9.157 System should generate the warning
message x no. of days prior to due
date of liquid security pledged to the
Bank.(LIC/NSC/ Bonds etc.) 2
10 BILLS/LETTER OF CREDIT/ BANK
10.1 GUARANTEE
All the details of the Bills should be
accepted (Date, Drawer, Drawee,
Payee, Tenor, Due date, Amount,
ROI, Commission, Postage, To
whom sent, etc) 2
generating bills
discounted/Purchased with all
relevant information regarding
recording of due dates etc. showing
register.
2
10.3 Provision to issue warning if
drawees of the bill have earlier not
paid bills on due date. 2
10.4 System should show FC & INR and
combined liabilities of a customer
(with Margin money if any) 2
10.5 System should have proper
accounting for Overdue Bills. 2
10.6 liability entries should be
automatically generated by the
system on authorization of a
transactions for guarantees and LCs.
2
10.7 Interest charging on Bills should be
parameterized 2
10.8 (from due date - date of discount till
due date etc) 2
Form 8
Page 132 of 248
Loans and Advances
10.9 Supply Bills – Display of DP on daily
basis 2
10.1 Supply bills- System should delete
beyond stipulated period and excess
over DP should be charged with
Penal interest. 2
10.11 Co-acceptance Bills- System should
display the due dates in advance 2
10.12 Co-acceptance Bills-DD/Payment
should be generated in favour of
principal Banker only. 2
10.13 Provision for shifting Documentary
Bills from collection status to
Purchase status. 2
10.14 System should define criteria for
devolvement of L/Cs and Bank
Guarantees. Check for the
parameters. 2
warning messages / letters 'x'
number of days (parameterisable)
before such LC payment. Check the
parameter to specify the number of
days.
2
squaring-up liability on account of LC
on retirement of Bills. 2
opening and maintaining
inward/outward bills for collection
and auto-generation liability
vouchers for GL on date of incurring
liability and paying of liability.
2
10.18
Provision for maintenance of data
relating to issuance of different
types of L/c and BGs( to be
parameterised) and calculation of
due dates, effective dates, expiry
dates,etc. and generation of
contingent liability voucher. 2
10.19 Calculation of L/c commission based
on the nature of Lc (DA/DP) and
usance period and generation of
voucher/debit advises for the
customers 2
10.2
Calculation of B/G
commission(including claim period)
based on the nature of BG
(Performance/ financial , etc) and
generation of voucher/debit advices
for the customers 2
10.21 Provision for printing hard copy of
LC. 2
Form 8
Page 133 of 248
Loans and Advances
10.22 Acceptance and record of bills
received under L/c and calculation of
due dates, generation of due date
confirmation advice 2
10.23
Retirement/ payment of bills
received under L/c including
calculation of the interest for the
usance period and commission if
any (as per terms of L/c), generation
of vouchers 2
10.24 Provision for warning regarding due
date of payment of bills under L/c
and expiry of B/g 2
10.25 Provision for Cancellation of
unexpired LC/BG at any point of time
and reversal of contingent liabilty
voucher, commission. 2
10.26 Provision to generate notice to the
beneficiary to return guarantee after
expiry of validity. 2
10.27 System should extend period of
guarantee/due date of LC and
enhance or reduce the amount of
guarantee/LC& provision for
amendment of terms 2
10.28 Cancellation of guarantee and
reversal of contingent liability
voucher after receipt of G'tee. 2
10.29 In case of non-availability of
sufficient balance at the time of
payment of LC , a separate LC
devolved account to be debited and
whenever there will be balance in
customer’s regular account the
balance in LC devolved amount to
be adjusted against regular
CA/CC/OD a/c along with uptodate
interest.
2
10.3 In case payment of LC is made to
the debit of LC devolved account
system should give warning at the
time of operation in th regular
CA/CC/OD a/c. 2
10.31 Provision for IBA approved list of
Transport operators 2
10.32 Provision for report generation for
outstanding bills purchased/sent for
collection as per user's choice. 2
10.33 Provision for entering details of
documents related to the bills
purchased/ sent for collection. 2
Form 8
Page 134 of 248
Loans and Advances
10.34
Provision to adjust the proceed of
the bills in the corresponding bill
purchase outstanding and automatic
generation of vouchers and
debit/credit advises for the
customers 2
10.35 Generation of Reports- Position of
outstanding bills, overdue bills,
reminder in case of non receipt of
the bills on the due date,etc.
according to user's choice. 2
10.36 system should provide accountwise
information of expiry of BG. 2
recording Lien on FDR/RD/SB/CA
balances against non-fund
facilities(BG/LC) and Loans granted
by other branches. 2
TOTAL 952
Form 8
Page 135 of 248
Loans and Advances
Comments
1 COMPUTATION OF RISK
WEIGHT ASSETS
1.1 There should be a system
of computing Risk-weight
for various natures of
Claims/exposures as per
RBI draft guidelines for
capital calculation under
standardized approach.
There should also be
flexibility to modify future
changes in norms.
2
1.2 The risk weight should be
assigned by the system in
line with RBI guidelines.
Viz.
1.2.1 a) While applying risk-
weight for claims secured
by residential properties, it
should apply 75% risk-
weight respectively for
houses meant for
residential property if it’s
value is 25% over the loan
amount. Other loans
against residential property
should carry risk-weight of
100%. There should also
be flexibility to modify
future changes in norms.
2
1.2.2 b)100% RW for
commercial real state. 2
1.2.3 c) 20% RW for scheduled
Banks and 100% for other
Banks. 2
1.2.4 d) For PSEs and primary
dealers as per corporate. 2
Form 8
Page 136 of 248
Basel II Comliance
1.2.5 e) Zero for Central/State
direct exposure, 0% & 20%
respectively for guarantee
exposure for Central/state.
2
1.2.6 f) 0% to 150% for foreign
sovereign based on risk
rating by international
rating agencies. However
20% if exposure in foreign
currency funded in that
very currency.
2
1.2.7 g) 0% to 150% for
corporate based on risk
rating by recognized rating
agencies. 2
There should be flexibility
to modify the norms. 2
1.3 Provision for providing risk-
weight in case of NPA
account based on –
1.3.1 a) unsecured portion vis-à-
vis provision 2
1.3.2 b) secured portion vis-à-vis
provision. 2
1.4 The parameters for the
risk-weightage will be as
per RBI norms. 2
1.5 Provision for risk-
weightage for foreign
currency & interest rate
derivatives is done by
assessing the exposure by
periodical calculation of the
current replacement cost
by marking these contracts
to markets.
2
1.6 foreign contract & interest
rate contracts should
include all the exposures
as per RBI definition. 2
Form 8
Page 137 of 248
Basel II Comliance
1.7 System for tracking &
monitoring the credit risk
exposure arriving from
unsettled transaction as
appropriate for producing
management information
that facilitates action on a
timely basis.
2
1.8 Provision to assess
exposure and assign risk-
weight for fail foreign
exchange and security
transaction as it would
convert into a fund-based
exposure on the relevant
counterparty.
2
1.9 Provision to apply hair-cuts
to eligible financial
collateral and also
exposures for setting of
market volatility &
assessing net exposure for
assigning risk-weightage.
The system should be as
per RBI guidelines for
standard supervisory
haircuts & there should
also be provision own
estimate haircuts. There
should also be provision to
apply haircuts if collateral
is baskets of assets.
2
1.10 When the credit protection
by a guarantee is
denominated by a currency
different from that in which
the exposure is
denominated (currency
mismatch), there should be
provision to apply haircuts
to amount of credit
protection as per RBI
norms & accordingly
RWAs should be
computed.
2
Form 8
Page 138 of 248
Basel II Comliance
1.11 Provision for considering
maturity mismatch of
exposure vis-à-vis
collateral while computing
RWAs. The collateral with
maturity mismatches to be
only recognized when
there original maturities are
greater than or equal to
one year and in all cases
collateral having a residual
maturity of three months or
less are not to be
recognized. The
adjustment in respect of
maturity mismatch should
be done as per RBI norms.
2
1.12 The prescribed risk-weight
for each category of
exposure /claim should be
multiplied with respective
exposure to arrive at RWA
on credit.
2
1.13 Provision to compute RWA
of off-balance sheet items
after applying credit
conversion factor
prescribed by RBI. 2
1.14 The package should
properly defined the
trading books for the
purpose of market-risk so
that it includes all
instruments as per RBI
guidelines. Viz – HFT,
AFS, Open gold position
level, open FE position
limit, trading position in
derivatives, derivatives
entered into for hedging
trading books.
2
1.15 The package should
estimate market-risk in
Bank’s book on an ongoing
basis i.e. at close of each
business day. 2
Form 8
Page 139 of 248
Basel II Comliance
1.16 The capital charge for all
interest rate related
instruments, equities in the
trading group should be
calculated as per
regulatory norms.
2
1.17 Foreign-exchange risk
(including open position)
through the Bank (both
Banking & Trading Books)
should be computed
separately.
2
1.18 The system should
compute capital charge for
– 2
A) Specific risk B) General
risk
1.19 The risk-weight for specific
risk (adverse movement in
the price of security owing
to factors related to issuer)
should be consistent with
those used for calculating
capital required in Banking
books. Thus, as Banks in
India will initially adopt
standardized approach for
credit-risk in Banking
books, the computation of
capital for risk in the
trading books will also be
based on standardised
approach.
2
1.20 Specific risk charge for
each security, which is akin
to the conventional capital
charge for credit risk, both
for short (short position is
not allowed in India except
derivatives) & long position
should be computed.
Form 8
Page 140 of 248
Basel II Comliance
1.21 The package, in addition to
compute specific risk-
charge for OTC derivatives
in trading books should
calculate counter-party
credit risk charge for OTC
derivatives as part of
capital for credit risk as per
the standardised approach.
2
1.22 The capital charge for
general market-risk should
cover –
1.22.1 A) The net short (short
position not allowed in
India except derivatives) or
long position in the whole
trading book. 2
1.22.2 B) A small portion of the
match position in each time
band (vertical
disallowance) 2
1.22.3 C) A larger portion of the
matched position across
different time band
(horizontal disallowance). 2
1.22.4 D) A net change for
positions in options, where
appropriate. 2
1.23 As RBI has approved
standardised duration
method for calculation of
capital charge on general
market-risk, there should
be provision to follow
under mentioned
mechanics prescribed by
RBI –
1.23.1 A) Price sensitivity

(modified duration) of each
instruments. 2
Form 8
Page 141 of 248
Basel II Comliance
1.23.2 B) Then apply the
assumed changes in yield
to the modified duration of
each instrument between
0.6 and 1.0 percent point
as per table prescribed by
RBI.
2
1.23.3 C) Slot the resultant
capital charge measure
into a maturity ladder as
per RBI prescribed table. 2
1.23.4 D) Subject long & short
positions (short position
not allowed in India except
derivatives) in each time
band to a 5% vertical
disallowance designed to
capture basis risk.
2
1.23.5 E) Carrying forward the net
position in each time band
for horizontal
disallowances set out in a
separate table prescribed
by RBI.
2
1.24 The measurement for
capital charge on market
risk should cover all
interest rate derivatives
and off-balance sheet
instruments in the trading
book & derivatives entered
into for hedging trading
book exposure like –
FRAS.
2
Form 8
Page 142 of 248
Basel II Comliance
1.25 A provision to calculate
capital charge on equity
(presently additional risk-
weight of 2.5%). Capital
charge for specific risk on
equity will be 9% and
general market risk charge
will also be 9% on gross
equity position – sum of
the long term & short term
equity position (short
position not allowed in
India).
2
1.26 Provision to apply
prescribed risk-weight
(presently 100%) on open
position of gold & foreign
exchange. The capital
charge will be 9% at
present. The open position
will be taken as limits or
actual which ever is higher.
2
1.27 All market risk, i.e. capital
charge on - interest rate
(general market risk &
specific risk), equity
(general market risk &
specific risk), foreign
exchange & gold should be
added to arrive at
aggregate capital charge
on market risk.
2
1.28 The total Capital charge for
various categories of
market risk exposure
should be converted into
RWA by multiplying the
total capital charge with
100 and dividing the
product by the rate of
capital charge i.e. 9 at
present.
2
Form 8
Page 143 of 248
Basel II Comliance
1.29 Provision to compute
capital charge on
operational risk by basis
indicator method which is –
“ALPHA” multiplied by
average of three year
gross income. ALPHA at
present will be 15% and
gross income will be : Net
profit (+) Provisions &
contingencies (+) operating
expenses (Schedule 16) (-)
profit on sale of HTM
investment (-) income from
insurance (-)
extraordinary / irregular
item of income (+) loss on
sale of HTM investments.
2
1.30 The capital charge on
operational risk will be
converted into RWA in the
same manner as in market
risk. 2
1.31 There should be a
provision for computing
exposure amount after risk
mitigation by way of
various collateral. There
should be system for
applying a standard
supervisory haircut or
Bank’s own estimate
haircut to various securities
so that risk weight may be
applied on net exposure.
Form 8
Page 144 of 248
Basel II Comliance
Comments
1 Government Functionalities
1.1 General features
1.2 Financial transaction enquiry 2
1.3 Reconciliation 2
1.4 Clearing regularization process/
report 2
1.5 Turn over commission calculation 2
1.6 Module closure process 2
1.7 Provision to credit the collection of
the day to link cell branch Nagpur 2
1.8 Provision to start BOD Process 2
1.9 Performance and duties of Data
Collecting Admin. & user 2
1.10 Facility to define commission rates in
different Govt. Business Module 2
1.11 Definition of RBI code mapping for
Bond scheme/allied business. 2
1.12 Facility for migration of existing data
for Bond/ PPF/SCSS 2004/Pension
scheme with reports 2
2 Taxes
2.1 Provision to add multiple tax
collected at different collecting
branches 2
2.2 Facility for tax collection as
transferred/cash/clearing transaction 2
2.3 Provision to submit branch wise
/scheme wise/ major head code wise
turn over (monthly/quarterly) 2
2.4 Transfer of funds from collecting
branch to focal point /nodal branch
and nodal branch to link cell branch. 2
3 CENTRAL BOARD OF EXCISE &
CUSTOM
3.1 System should support collection of
CBEC taxes. 2
3.2 System should support upload of
various masters provided by CBEC
in the core banking solution for
verification purposes (presently
masters are provided for assessed,
commissioner ate code, branch bank
code)
2
3.3 System should define any specific
rules for government accounts for
submission of data to respective
agencies. 2
3.4 System should define different
commissionerate zones for collection
of service CBEC revenues.
2
Form 8
Page 145 of 248
Government Business
3.5 System should map all collecting
Branches to Nodal and Nodal to Link
cell Branch. 2
3.6 System should capture details as per
CBEC prescribed refunds / forms at
the branch nodal / link branch and
Collecting branch. 2
3.7 System should capture all challan
details. 2
3.8 System should capture Focal
point/Nodal / Link branch bank code 2
3.9 Scroll Number should be generated
from the 1st April to 31st March.
Separate for collecting branch and
nodal branch.
2
3.10 System should generate separate
Scroll Number at collecting &
focal /Nodal branch level. 2
3.11 System should capture scroll date at
collecting & focal /Nodal branch
level. 2
3.12 System should facilitate validation
based on utilities/validations
software provided by statutory
authorities i.e. RBI / CBEC etc. 2
reconciliation between the different
tiers of the system. For ex.
Reconciliation between collecting
branches and nodal branch and the
nodal branches with link cell branch.
Focal Point branch should be
reconciled with the respective PAO.
2
3.14 System should have the facility to
reconcile between the total amount
received through challans and the
funds remitted by the collecting
branch to Nodal Branch. 2
generate March Residual Scroll No.
up to 15th April of the Next financial
Year in addition to the scroll
generated for the current financial
year.
2
3.16 System should print a report of all
UN-reconciled item at each level i.e.,
nodal / link branch and Collecting
branch etc., 2
Form 8
Page 146 of 248
Government Business
3.17 System should generate an ASCII
file for collection made by the branch
as per defined flat file structures and
file naming convention. Provision for
modification/addition/deletion in the
columns/fields should be available
as per requirement of the Govt. File
naming convention should be
modified as per Govt. requirements.
2
upload /download ASCII file
received/transmitted from/to Non-
CBS branches. 2
3.19 System should generate ASCII files
in the desired formats at the
collecting branch level and
consolidated ASCII file at Focal
Point branch level. 2
3.20 System should be able to offer “E-
Payment facility” for Central Excise
and Service Tax payers. 2
3.21 System should be able to show list
of activities for providing E-Payment
facility to CBEC taxpayers. 2
3.22 System should be able to interface
with Internet Banking facility having
following basic features of the E-
Payment. 2
3.23 The taxpayer will log on to Bank site
after security validation (user ID,
Password). 2
3.24 Taxpayer may or may not be
account holder of the Bank. 2
3.25 Provision of online filling of challan
form. 2
3.26 Directory of essential information,
validation should be available to tax
payer for entering in the challan 2
3.27 form.
System should be able to debit
taxpayer account or other means to
accept E-payment. 2
3.28 Remitting the funds to RBI as per
normal procedure. 2
3.29 System should be able to print
challan form and also able to print
copies of challan for PAO, Assessee
and Range Officer. 2
3.30 System should be able to accept
payment of tax through Debit/Credit
Cards for the taxpayers who are not
maintaining account with the Bank. 2
3.31 System should be able to remit
funds and do settlements with
government. 2
Form 8
Page 147 of 248
Government Business
3.32 System should have the System
should transfer funds electronically
to CBS branches/nodal branches. 2
4 Report Generation at collecting
branch level
4.1 Major head wise receipt scroll for
CBEC. 2
4.2 Date wise monthly statement. 2
4.3 Daily memo 2
5 At Focal/Nodal branch level
5.1 Major head wise main receipt scroll
for CBEC. 2
5.2 System should generate main scroll
number for each type of major-head. 2
5.4 System should reconciliation with
the collecting branches. 2
6 Central Board of Direct Taxes
6.1 System should support collection of
CBDT revenues. 2
6.2 System should support upload of
various masters provided by CBDT
in the core banking solution for
verification purposes (presently
masters are provided for PAN/TAN &
Branch Code)
2
6.3 System should define any specific
rules for government accounts. 2
6.4 System should define different zonal
accounts office (ZAO) for collection
of CBDT revenues. 2
6.5 System should map all collecting
Branches to Nodal and Nodal to Link
Branches. 2
should accept the challan
particulars by e-filing. 2
6.7 Scroll Number should be generated
from the 1st April to 31st March.
Separate for collecting branch and
nodal branch.
2
6.8 System should generate separate
Scroll Number at collecting &
focal /Nodal branch level. 2
6.9 System should capture scroll date at
collecting & focal /Nodal branch
level. 2
should accept the payment through
e-banking. 2
information of the assesse given in
the challan by the collecting
branches 2
Form 8
Page 148 of 248
Government Business
6.12 System should be able to capture all
challan details and the following of
the respective collecting/nodal
branches :
Major and minor head code 2
Receiving Bank Scroll date 2
Date of tender
(Cash/Clearing/Transfer) 2
Date of realization 2
Collecting Branch Bank Code 2
Challan Identification Number (CIN) 2
Amount 2
Nodal branch Bank code 2
Nodal branch scroll number 2
Accounting month 2
Serial number 2
Nodal branch scroll date 2
6.13 System should facilitate validation
based on Utilities/validation software
provided by statutory authorities i.e.
RBI / NSDL/ Income Tax Dept., Govt
of India. 2
reconciliation between the branches
and the nodal / link branches,
between the nodal / link branches
and the collecting branch and
between the collecting branch and
remitting authorities (CBEC).
2
6.15 System should print a report of all
UN reconciled item at each level i.e.
nodal / link branch and collecting
branch etc 2
6.16 System should generate an ASCII
file for collection made by the branch
in RT01, RT02 and RT08 (error file
if any) and transmit the same to
nodal branch at the end of the day. 2
6.17 System should also have the System
should accept the fund transmitted
electronically from collecting branch
to nodal branch in case of non-CBS
branch. 2
should upload/download RT01,
RT02 & RT08 at the nodal branch
level including its own RT01, RT02 &
RT08 and transmit the same to link
cell branch as RT01, RT03 & RT08.
2
Form 8
Page 149 of 248
Government Business
should consolidate the RT01, RT02
& RT08 files received from the
collecting branches including its own
and System should generate and
transmit the consolidated RT01,
RT03 & RT08 file to link cell branch.
2
6.20 System should generate error /
defaulters list at nodal branch level. 2
should consolidate the RT01, RT03
& RT08 files received from the nodal
branches and System should
generate and transmit the
consolidated RT01, RT04 & RT08
file to NSDL/CAS, RBI Nagpur.
2
6.22 System should generate error /
defaulters list at link cell branch 2
6.23 level.
System should transmit the fund to
CAS,RBI Nagpur electronically. 2
6.24 Facility to allocate budget to
collecting branches, ZO wise. 2
7 Report Generation at collecting
branch level
7.1 Major head wise receipt scroll for
CBDT. 2
7.2 System should generate scroll
number for each type of tax (major-
head wise). 2
7.3 Daily memo 2
7.5 Facility to generate Error-
Report/Validation Report. 2
7.6 Facility to generate tax collected
major head-wise and period wise
(from date…….to date) 2
7.7 Facility to find out tax collected at the
collecting branch through
Cash/Clearing/Transfer for a
particular period (from date… to
date). 2
7.8 Facility to compare the actual
collection with the budget and submit
a variance report thereon branch-
wise and Zonal-Office wise. 2
8 At Focal/Nodal branch level
for CBDT. 2
for CBEC. 2
8.3 System should generate main scroll
number for each type of tax.(CBDT &
CBEC) 2
8.5 Facility to generate Error-
Report/Validation Report. 2
Form 8
Page 150 of 248
Government Business
8.6 Facility to generate tax collected
major head-wise and period wise,
collecting branch-wise (from
date…….to date) 2
8.7 Facility to find out tax collected at the
various collecting branches through
Cash/Clearing/Transfer for a
particular period (from date… to
date). 2
8.8 System should reconciliation with
the collecting branches. 2
9 Sales Tax
9.1 Central/Local sales tax collection 2
9.2 Sales Tax daily consolidation
summary scroll 2
9.3 Sales tax receipt scroll 2
9.4 Monthly Turnover statement 2
9.5 Calculation of turn over commission 2
9.6 Quarterly letter from link branch to
RBI 2
9.7 Date wise monthly summary scroll 2
9.8 Daily memo focal point monthly
reports 2
9.9 Focal point head wise consolidation 2
9.10 Sales tax remittance by electronic
way to concerned PAD, RBI. 2
10 Sub treasury
10.1 The system should be able to handle
the State Govt sub treasury business 2
10.2 System should be able to capture
the challan details as per format of
Govt. 2
10.3 System should be able to capture
the Payment details like name,
cheque no, date, issuing authority. 2
10.4 System should generate Scroll No. 2
10.5 System should generate receipt
scroll for the day as per the format
specified by Govt. 2
10.6 System should generate payment
scroll for the day in the format
specified by Govt. 2
10.7 System should open GL Head for
sub-treasury business. 2
10.8 System should transfer total
receipts and total payment to
Agency Link Branch at the end of the
day electronically. 2
10.9 The system should be able to collect
the amount through cash/ transfer/
clearing. 2
10.10 System should upload/download
data in ASCII format from/to sub-
treasury branch/agency link branch. 2
Form 8
Page 151 of 248
Government Business
10.11 System should maintain records of
daily receipts and payments in the
system. 2
10.12 System to accept the cheque series
given by the sub-treasury authorities
and update the stock of cheque
book. 2
10.13 System to give warning messages in
the event of stock of cheque books
has reach the re-order quantity
level / below minimum quantity. 2
10.14 System should generate date wise
monthly statement on monthly basis
and should transmit the same to
agency link branch and sub-treasury
for reconciliation. 2
10.15 System should generate daily
transaction of receipts and payments
in the passbooks. 2
generate consolidated summary of
the receipts collected party wise,
head wise and payment by treasury
officials. 2
11 Departmentalize Ministries
Account
11.1 The system should be able to handle
the central Govt. ministry account
business of receiving and paying on
behalf of ministry of finance, Deptt.
Of (Revenue expenditure). 2
11.2 The system should be able to collect
the amount through cash/ transfer/
clearing. 2
11.3 The system should immediately
remitt to the government account as
soon as the receipt realizes. 2
11.4 The system should also adhere to
the online collection to this account. 2
11.5 System should support government
accounts such as Ministry of Finance
department of revenue
(expenditure). 2
generate consolidated summary of
the receipts collected party wise,
head wise and payment by DDO
wise. 2
11.7 The system should automatically
able to calculate the commission
charges to be recovered/to be paid
to other Banks. 2
11.8 The system should be able to remit
all proceeds at the end of the day to
nodal branch. 2
Form 8
Page 152 of 248
Government Business
11.9 The system should upload/download
the data transmitted/received by the
designated branch. 2
11.10 System to specify limits and drawing
powers for such accounts and track
exposures in such accounts. 2
11.11 System to link the limits to underline
letter of credit. 2
11.12 System to waive or charge interest
commission (paramateterised) and
changes to a particular account or all
such accounts. 2
generate ASCII files in prescribed
format of government account wise
for daily transaction done. 2
consolidate and transmit fund,
challan data, payment details to link
cell branch. 2
11.15 System should generate net figures
that is to be sent to or receipt from
CAS/RBI sending them e-advice to
either debit or credit our account. 2
11.16 System to accept the cheque series
given by the government authorities
and update the stock of cheque
book. 2
11.17 System to give warning messages in
the event of stock of cheque books
has reach the re order quantity
level / below minimum quantity. 2
11.18 System should generate date wise
monthly statement on monthly basis
and should transmit the same to
CAS/RBI and Ministry of Finance for
reconciliation. 2
11.19 System should be able to generate
flow of information to Ministry of
Finance Govt. of India, New Delhi. 2
12 PPF Accounts
12.1 system should define different A/C
types i.e. HUF, Individual to open
PPF accounts. 2
12.2 All details of accounts should appear
on one screen. 2
12.3 system should verify that he is not
an existing P.P.F. account holder. 2
12.4 system should open account by
Cash/Transfer/Clearing. 2
12.5 system should open account by
transfer from other branch of our
bank and from other bank. 2
Form 8
Page 153 of 248
Government Business
12.6 system should auto generate
vouchers for all activities i.e.
Opening of account closing of a/c
etc. 2
12.7 Facility to modify interest rate with
effective date should be available in
the system as per Govt. notification. 2
12.8 system should generate Daily
Reconciliation Statement. 2
12.9 system should accept nomination
facility. 2
12.10 system should provide yearly
Interest at the end of financial year
i.e. March every year and auto
generation of vouchers. 2
12.11 system should provide balancing
reports for a selected range dates
etc. 2
12.12 system should calculate eligible
Loan amount and mark lien on the
PPF. Account i.e. as per the
eligibility criteria i.e. he is eligible for
taking Loan after 3 years and eligible
amount is 25% of 1st years balance
outstanding. (To be Parameterized)
2
12.13 system should provide year-wise
outstanding balances of the account. 2
12.14 system should generate monthly
statement for government
Department and for Nodal Branch. 2
12.15 system should maintain Agency
record of eligible Agents. 2
12.16 system should Calculate Agency
commission maintain record and
provide information for a select
range dates etc. and generate
vouchers at branch level. 2
12.17 system should not accept amount
over Rs.70, 000/- in a year.
(Minimum Rs.500/-. (To be
parameterized) 2
12.18 system should generate yearly
commission certificate. 2
12.19 Provision for deduction of TDS from
the agent commission. 2
12.20 system should claim Agency
commission from Nodal Branch. 2
12.21 system should generate following
Reports at the level of Collecting and
Paying Branches.
12.22 A) Daily Reconciliation Statement 2
12.23 B) Daily Memo of collection and
Payments. 2
12.24 C) Monthly Statement of
Collection and Payments. 2
Form 8
Page 154 of 248
Government Business
12.25 D) Monthly jotting of PPF
accounts. 2
12.26 System should provide for extension
of PPF accounts beyond 15 years. 2
12.27 system should generate following
reports/forms.
Form “A” is application form 2
Form “B” deposit slip 2
Form “C” withdrawal form 2
Form “D” is loan application 2
Form “E” Nomination form 2
Form “F” cancellation/variation of
nomination 2
Form ”G” withdrawal by
nominee/Legal hairs 2
12.28 system should permit partial
withdrawal after expiry of 5 years. 2
12.29 Eligible amount will limit to 50% of
the balance at the credit of the end
of 4th year immediately proceeding
year in which the amount is
withdrawn or at the end of the
proceeding year which ever is lower.
2
12.30 system should permit nomination for
one or more persons. 2
12.31 system should provide for repayment
of PPF amount to nominee as per
rule defined in the system 2
12.32 The system should be able to print
passbook. 2
13 Procedure at NODAL BRANCH
13.1 system should maintain following
Records,
13.2 a) Branch-wise Register 2
13.3 b) To generate Daily
collection/payment memo. 2
13.4 c) To generate information for
the month end as per format-I. 2
13.5 d) To maintain Register for Daily
collection/payment. 2
13.6 e) To generate above reports
month-wise range of dates. 2
13.7 f) To generate statement of
collection/payment State-wise. 2
13.8 g) To generate Half-yearly,
yearly statement of 2
13.9 collection/payments.
System should calculate Turnover
Commission on quarterly basis and
generate report for claiming amount
from RBI. (@ 11.80 pause per 100/-)
To check generation of report for
different rate of commission. (To be
parameterized)
2
Form 8
Page 155 of 248
Government Business
13.10 system should calculate
remuneration from RBI and to
generate related reports. 2
13.11 system should maintain Master
Record of Agents. 2
14 SENIOR CITIZEN SAVING
SCHEME’ 2004
14.1 The system should support the
Senior Citizen Small Savings
Scheme 2004. 2
maintain a list of Small Savings
Agents and track the details against
each agent. 2
capture the details of the customers
as required by the bank. 2
maintaining following parameters. 2
14.5 Tenure of the scheme i.e. 5 years,
which can be extended by 3 more
years. 2
14.6 Interest rate – 9% should be
parameterized and payable quarterly
on 31st March/ 30th June/ 30th
September/ 31st December.
2
14.7 Tax aspect interest is taxable. 2
14.8 Minimum investments in multiples of
1000 in cash/ cheque/ DD in favor of
depositors bank. 2
14.9 Maximum investment limit Ra.15.00
lakes (Principle + Interest) single or
multiple per account of the depositor.
2
14.10 Minimum eligible age criteria i.e. 60
years or 55 years if depositor retires
under Special Voluntary Scheme. 2
14.11 System should define penalty rules
in the system. 2
14.12 Facility of premature withdrawals –
availability with the penalty as per
rule. 2
14.13 Transferability feature – available. 2
14.14 Tradability – not available. 2
14.15 Nomination facility with details of
nominee. 2
14.16 Mode of holding – either single or
jointly with spouse only. 2
14.17 System should be able to maintain
the commission paid to agents. 2
calculate commission automatically. 2
Form 8
Page 156 of 248
Government Business
14.19 System should be capable of making
payment of commission under at
source commission payment system
to the agent. 2
14.20 System should validate the
parameters set at the time of
opening account, transaction to be
made and closure of account / or
premature closure. 2
14.21 System should be able to print the
deposit receipt advice generate the
passbook as per the prescribed
format. 2
14.22 System should maintain the list of
SCSS –2004 designated branches
for transferability of accounts as per
the request of depositor. 2
14.23 System should maintain list of
branches linked to particular nodal
branch. 2
14.24 System should be able to link all
nodal branches to link cell Napery. 2
14.25 System should be able to remit the
subscription deposit clear amount of
balance to the link cell Napery
through nodal branches on daily
basis. 2
14.26 System should validate the
remittance on daily basis otherwise
delayed remittance would attract
penalty at coupon rate as per the
guidelines automatically. 2
14.27 System should be able to report to
link cell Napery for the transaction
either directly or through nodal
branches. 2
14.28 System should be able to
consolidate report of state wise and
branch wise SCSS – 2004
transaction on daily basis to CAS 2
14.29 Nagpur and settle funds directly with
Napery.
monthly statement to enable the link
cell to submit the same to principal
account officer department of
economic affairs, ministry of finance,
Government of India, New Delhi and
to Department of Government and
bank accounts RBI, Mumbai in the
first week of the following month.
2
14.31 System should be able to integrate
with clearing module for local
cheques/ DD deposited. 2
track of particular transaction with
the help of unique reference number. 2
Form 8
Page 157 of 248
Government Business
the supplementary of all transactions
done on particular day of the branch. 2
14.34 System should upload the ASCII
files received from non-CBS
branches at the nodal / link branches
for consolidation. 2
reconciliation between the branches
and nodal / link branches and vice
versa. 2
14.36 System should not pay the
cumulative interest or stop further
interest calculation if the interest
amount is not withdrawn. 2
14.37 On maturity of the deposit system
should calculate interest at prevailing
saving bank rate and should
generate the notice or advice to the
depositor informing for withdrawal of
deposit or extension of period for
further 3 years.
2
15 PENSION ACCOUNTS
15.1 system should define different types
of pension accounts i.e. State
Government, Central Government
etc. and other statutory bodies. 2
15.2 system should define categories and
types under Main pension Accounts
i.e., under Central Government –
Defense, Railway, Civil etc., 2
15.3 system should open pension
account in single name only. – No
joint account will be opened. 2
15.4 System should set applicable DA in
case of accounts opened under
different ministry, state Govt/State
Govt. 2
15.5 system should accept data from
government organization in soft copy
and upload the same into the
system. 2
15.6 system should update pensioners
list on incremental basis in the event
of new inclusion/deletion in the event
of death. 2
15.7 system should reduce the family
pension after seven yearly as per
rules of the Govt. 2
15.8 System should start family pension
AFTER expiry of the pensioner. 2
15.9 System should set parameters for
payment of Family pension to Un-
married daughters/Minor sons. 2
Form 8
Page 158 of 248
Government Business
15.10 system should capture details of the
individual pension account holder
i.e., name, PPO No., Basic Pension,
dearness pension, dearness relief,
Interim Relief, commutation amount
etc.,
2
15.11 system should define the different
calculation methods for different
types of pension payments. 2
15.12 system should automatically
calculate and post pension
payments payable to different
pension accounts taking into account
salary structure, DA etc., 2
15.13 system should scan and generate
reports of signature and
photographs. 2
pension payment scroll and
summary for different types of
pensions category-wise/pension
issuing authority-wise. 2
15.15 System should bifurcate P.P.O. wise
state pension on Govt. defined ratio
between the state Govt. 2
15.16 system should generate a
consolidated summary for all types
of pensions. 2
15.17 system should send the pension
scroll and summary to Link / Nodal
branches type-wise, category-wise,
pension issuing authority wise. 2
15.18 system should restore
commutation amount of pension
after 15 years from date of
retirement/date of commutation
(parameterized). 2
15.19 system should generate
consolidated summary of all types of
pensions at Nodal, Link branch. 2
15.20 system should auto reconcile
pension payments with branches,
Link and Nodal branches. 2
15.21 system should automatically and
manually transfer accounts to
different branches. 2
15.22 system should give warning about
non-submission of life certificate in
the month of November every year. 2
15.23 system system sanction loan
facilities to Pension holders and
marking of lien in Saving account
and auto recovery of loan. 2
Form 8
Page 159 of 248
Government Business
15.24 System should generate pension
statement with details such as last
months outstanding, pension paid,
claimed reimbursement, and total
outstanding balance at the of the
month.
2
15.25 system should calculate DA /arrears
of DA on the basis of basic and other
allowance. 2
15.26 System should consolidate the
scroll ministry-wise received from the
paying branches and generation of
summary report in prescribed format.
2
15.27 Transfer of non-civil ministry scroll to
SBI/RBI and civil ministry scroll,
summary report to nodal branch with
A,B,C,D,E,F (ASCII) formats decided
by Govt. 2
15.29 1) consolidation of the pension scroll 2
15.30 2) Generation of daily Govt. Debit
Scroll & transmit to Link cell. 2
15.31 3) Consolidation of A,B,C,D,E,F
(ASCII) formats and transmit to
CPAO, New Delhi. 2
16 RELIEF BONDS/SAVING BONDS
16.1 System should define different
categories of relief bonds upon
interest rates, tenor, schemes,
calculation of interest etc., 2
16.2 Details of the Relief Bonds Scheme
wise
Which is eg. -
9% Relief Bonds 1999 2
8.5% Relief Bonds 2001 2
8% Relief Bonds 2
7% Relief Bonds 2002 2
6.5% Relief Bonds 2003 (Non
Taxable) 2
(It is abolished in this financial year
2004-05)
8% Relief Bonds 2003 (Taxable) 2
16.3 System should check maturity date
of RBI Bonds automatically picks up
the same forms the table as per the
category of bond selected. 2
16.4 System should identify whether
interest is cumulative/ Non-
cumulative for the particular category
of the Bond. 2
16.5 System should calculate the interest
on due dates as per the Bond
Scheme and post the same. 2
Form 8
Page 160 of 248
Government Business
16.6 System should define categories of
Relief Bonds, which are exempted
from the tax liability. (E.g. 7% Relief
Bonds exempted from Wealth Tax) 2
16.7 System should identify the collection
made through Broker / Direct. 2
16.8 Capable to maintain master list of
Authorized Brokers. 2
16.9 System should globally define
brokerage and calculate the same. 2
16.10 System should generate due date
letter to customer of different type of
Bonds. 2
16.11 System should facilitate repayment
of bonds. 2
16.12 System should permit closure of a
bond account on maturity. 2
16.13 System should stop calculating
interest post maturity. However
these should be an option to accrue /
pay interest and display the same
until the bonds are not encased. 2
16.14 System should calculate (as
defined in the charges / commission
module) and store commission
amounts to be received by the
Branches for maintenance and
servicing of Government accounts.
Ask the vendor whether this feature
is supported by the system and if
“Yes,” ask him to show the
parameter for the same.
2
16.15 system should be capable of printing
a consolidated report of all
collections made during the day,
category-wise at branch, Nodal/Link
branch and the parent branch. 2
16.16 System should Generate following
reports/formats in acceptable format.
16.17 Certificate of holding – Form X and

Form Y. 2
16.18 Certificate of Investment 2
16.19 Register of Bond Issues/transferred/
repaid. 2
16.20 Register of nominees. 2
16.21 Acknowledgement of nomination
made and canceled repayments
made. 2
16.22 Commission earned / Brokerage
paid. 2
Form 8
Page 161 of 248
Government Business
submission of statement to RBI –
Byculla (Mamba) in every month by
7th day of each month. Branch has
to send every month the following
annexure.
16.24 Part A – Bond Ledger Accounts

opened during the month 2
16.25 Part B – Transferred from other
branches / banks (In flow) 2
16.26 Part C – Transferred to other
branches / Banks (Out flow) 2
16.27 Part D – Repayment 2
16.28
16.29 System should check whether Bonds
are overdue for payment.
16.30 System should generate ASCII file
in RBI Suggested format for
Summary of Bonds received on
Monthly Basis/daily basis, Bond type
wise. 2
16.31 System should generate Annexure-
IV report as per RBI suggested
format on daily basis, bond type
wise. 2
17 CURRENCY CHEST
17.1 system should have a module to
cater to currency chest 2
17.2 Maintenance, branch vault cash
maintenance and head office
currency maintenance [Notes/Coins]
in base currency/any other currency 2
17.3 cash denomination option,
movement of cash from safe to Head
cashier, Head cashier-to-cashier,
Cashier to head cashier and cashier
to cashier should be available?
2
17.4 manual overriding of denomination
check with authorization should be
available 2
17.5 System should display closing cash
balance in various safe like safe-1,
safe-2 denomination wise 2
17.6 At any point of time manager should
be able to view the cash position in
each terminal 2
17.7 parameter for branch cash retention
limit should be available 2
Form 8
Page 162 of 248
Government Business
17.8 System should reckon the cash
holding limits of each of the CBS
branches and comparing the same
with closing cash balance to arrive at
excess holding limits, which
information should be directly
transmitted to Fund management
Dept, HO/ZO for better management
of CRR/call money, Tracking this
branch-wise, bank as a
whole/currency chest wise/Zone-
wise
2
17.9 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
17.10 system should display the details of
the cash order/surplus form upon
entry of the reference number,
amount, date etc. 2
17.11 System should prompt for
authorization of the details,
displayed for the cash order/surplus
form at the currency chest. 2
17.12 upon authorization of cash order
surplus form at the currency chest,
the system should be able to pass
the appropriate accounting entries in
the respective books of accounts 2
17.13 What will be the process of
appropriate accounting entries with
example required [At currency chest
level] 2
17.14 system should print a cash
order/surplus denomination-wise 2
17.15 After authorization of cash
order/surplus form at currency chest,
system should pass only the
appropriate accounting entries of
total value [amount] or also
add/deduct the denomination-wise
note pieces in the balance of
currency chest details
[denomination-wise]
2
Form 8
Page 163 of 248
Government Business
17.16 If there is transaction between
currency chest and those branches
which are connected with CBS, and
there is provision for automatic
adding / deducting the
denomination-wise note pieces in
the balance of currency chest details
[denomination-wise] system should
up load the details of note pieces
and value for deposit/withdrawal of
other branches cash, which are not
connected with the CBS
2
17.17 If automatic addition/deduction of
note pieces and value is not happen
[occur] in the balance of currency
chest details [denomination-wise],
then up loading of closing balance,
denomination-wise on certain date
should be supported and after that
provision for feeding the details of
deposit/withdrawal as per TE_2 [RBI
statement] and provision for feeding
the details of deposit/withdrawal as
per TE_2 prepared for cross tally
should be supported
2
17.18 system should accept currencies
under different categories
[parameterisable] issuable / non
issuable/mutilated notes 2
17.19 System should define various
currency chest and link branches to
particular currency chest 2
17.20 System should link currency chest
at a link branch 2
17.21 System should up load the details of
deposit/withdrawal denomination-
wise at link branch level for
consolidation purpose for those
branches which are not connected
with CBS
2
17.22 system should automatically update
the cash position at the link- branch
denomination-wise with the amount
received from/remitted to the
currency chest which are linked with
CBS
2
generate covering letter [schedule]
for the currency deposited/
withdrawn [credit/debit] at link
branch to RBI in the format as
desired by the bank
2
generate link branch statement to be
send to RBI with covering letter 2
Form 8
Page 164 of 248
Government Business
RBI accounts for the bank based
upon the currency position at the link
branch 2
17.26 system should automatically pass
the appropriate accounting entries in
the respective books of accounts at
link branch 2
17.27 system should add/deduct the
remittances received from RBI
/remitted to RBI at currency chest
level 2
17.28 System should service currency
chest remittances for other banks 2
17.29 System should maintain account
and track withdrawals & deposit
made by other banks to the currency
chest 2
17.30 system should be able to
maintain/print the record of in
flow/out flow of cash to RBI
denomination-wise 2
17.31 system shouldautomatically update
the currency position at the head
office level 2
17.32 system should calculate and store
interest on a daily bases for cash
held at currency chest based on the
rate specified for the day 2
17.33 system should at least generate
reports as on a particular date/range
of dates for the following branches,
currency chest, link office, central
cash department and head office 2
17.34 system should generate report on
detailed listing of the notes /coins
entered in the system currency-wise 2
detailed listing of notes category
wise 2
17.36 system should generate report
summary of currencies category-
wise 2
17.37 system should generate report of
total out-flow of cash summary
branch-wise 2
17.38 system should generate detailed
report on the out flow of currencies
denomination-wise 2
total in-flow of cash summary
branch-wise 2
report on the in-flow of the
currencies denomination-wise 2
Form 8
Page 165 of 248
Government Business
17.41 system should generate report of in-
flow of the cash, currency chest-wise
and denomination-wise at a
particular date/range of dates 2
out-flow of the cash currency chest
wise and denomination-wise at a
particular date / range of dates 2
report on borrowings done from RBI 2
report on cash deposited to RBI
[non-issuable/mutilated] 2
17.45 system should generate report
summary of borrowings/deposits
from RBI 2
total cash position of the bank
currency-wise/ category-wise and
denomination-wise 2
listing of excess cash branch –wise 2
17.48 system should generate TE 2 form
submitted by the various currency
chest to RBI and Link office 2
17.49 system should generate Link-
statement, submitted by link office to
RBI 2
interest earned on funds, parked
with RBI for Central Bank of India 2
17.51 system should generate detailed and
consolidated position and
transaction listing denomination-wise
for transaction done by other bank
with the currency chest 2
17.52 system should generate stock of
soiled/mutilated notes denomination-
wise 2
statement of exchange of
soiled/mutilated notes 2
17.54 system should be able to calculate
amount recoverable from branches
on account of chest services
provided 2
17.55 system should calculate amount
recoverable from RBI /other banks
towards maintenance cost of the
chest /any other transaction cost 2
17.56 system should give advance alert on
fitness certificate, due date of chest 2
17.57 system should give advance alert for
annual position certificate as on 1st
April every year to be send to RBI 2
Form 8
Page 166 of 248
Government Business
17.58 system should give advance alert
for annual indent for cash from RBI
should reach at link office as or
before 15nth February and
consolidated indent should reach at
RBI on or before 20ath February
every year
2
17.59 system should give advance alert
for annual balance certificate as on
31st May every year to be send to
RBI
2
17.60 system should give advance alert for
annual balance certificate as on
30ath June every year to be send to
RBI 2
17.61 One new head in nominal Half value
paid [in the case of acceptance of
mutilated notes]should be supported 2
17.62 In addition to expenses incurred in
maintenance of currency chest,
other misc. Expenses one additional
new head in SL Expenses incurred
in currency transfer; [transportation
and escort party (police) expenses]
which is recoverable from RBI
should be supported
2
17.63 When branch is connected with CBS
but currency chest is not connected
with CBS . In branch system should
have a module to print cash order
/surplus form and System should
automatically pass the appropriate
accounting entries, what will be
process of sending and receiving the
cash [accounting] to those currency
chest which are not connected with
CBS by those branches which are
connected with CBS
2
17.64 When currency chest is connected
with CBS but link office is not
connected with CBS what will be
process of accounting and sending
the M F and statements to link office 2
17.65 System should generate ASCII files
in the desired format for all
transaction don by the various
currency chest at the link office
[central cash department] 2
17.66 System should upload ASCII files
for currency chest not connected to
the CBS for consolidation purpose 2
Form 8
Page 167 of 248
Government Business
17.67 System should generate report of
cash borrowed from/dispatched to
the currency chest by the link
office /RBI cash denomination and
currency-wise 2
18 FOR SMALL COIN DEPOT
18.1 All the procedure as defined for
currency chest maintenance for
deposit/withdrawal /accounting
/maintenance of
balance/consolidation of balances
for the branches and currency chest
connected with CBS and NON CBS
branches and currency chest should
be separately available for small coin
depot
2
18.2 system should maintain and
generate Form T A _51 statement for
sending to RBI for small coin depot
at small coin depot level 2
18.3 System should be available at link
ofice level for currency chest
maintenance
/accounting/consolidation of
balances for the CBS small coin
depot and NON CBS small coin
depot
2
18.4 system should generate the
covering letter to be send to RBI with
link office statement for small coin
depot separately 2
the balance position of small coin
depot at link office level 2
TOTAL 734
Form 8
Page 168 of 248
Government Business
Comments
1 SERVICBRANCH/CLEARING
1.1 System should interface with the
existing software package at our
bank’s service branches. 2
1.2 System should link various
branches falling under a particular a
Service Branch/Clearing Processing
Center (CPC)? 2
1.3 System should : -
1.3.1 1) Maintain clearing functions of
CBS & Non-CBS branches at the
central/distributed location viz.
CPC/Service Branch/QCS. 2
1.3.2 2) Capture all relevant details as per
the sorting for instrument processing
as-
#Cheque, 2
#Demand draft, 2
#Pay order, 2
#Warrants etc. 2
#Multicity Cheques 2
For CBS & Non- CBS Branches
1.3.3 3) to interact RTGS system for fund
settlement. 2
1.4 System should maintain clearing
types and assigning it to the
particular Clearing center as bellow:
1.4.1 -1) Inward clearing 2
1.4.2 2) Outward clearing 2
1.4.3 3) Up country outstation/OBC clg. 2
1.4.4 4) National Clearing 2
1.4.5 5) Home Clearing 2
1.4.6 6) High value clg. 2
1.4.7 7) Inter Bank clg –applicable to Non-
RTGS Centers 2
1.4.8 8)MICR, Non MICR Clg 2
1.4.9 9) EFT 2
1.4.10 10)ECS clg. 2
1.4.11 11) Cheque Trancation facility. 2
1.4.12 12) Quick collection service clg. 2
1.5 With Minimum details as follows:
*Clearing Name 2
*Number of days to effect
Auto/Manually credit for outward 2
*Number of days within Inward to be
return 2
*Rate of clearing House charges 2
*Minimum amount/ Limit accepted
for particular clearing. 2
1.6 System should -:
Form 8
Page 169 of 248
Service Branch Clearing
1.6.1 1) Define Clearing Time Zone and
number of days to effect credit for
each time zone. 2
1.6.2 2) Credit the customer’s account
automatically upon crossing the
number of days specified under each
time zone, the event of releasing of
un-cleared effect should be user
configurable e.g. as a part of day-
begin, Day- end, time period etc.
2
1.6.3 3) Hold the release of unclear effects
for a particular instrument in
particular time zone 2
1.6.4 System should define all clearing
House charges. At least the
following charges need to be
defined: -
# Cheque processing charges 2
# Penalty charges after cut-off time. 2
1.7 System should define the
charges/commission table with rates
for multiple slab with the facility to
change a fixed commission
component for each slab along with
the variable rate (as a percentage of
the cheque value) for
collection/rejection of instruments,
system should at least capture the
following details:
# Number of days for clearing 2

# Slab 2
# Fixed Rate 2
# Variable Rate 2
1.8 System should identify the cheque
status, the various stages could be: -
# Under clearing 2
# Not sent for clearing (outward) 2
# Return by the drawee / drawer
bank 2
# Cleared 2
# Cheque of RBI with payment –
advice e.g. I.T.Refund 2
# Returned to the customer 2
# Under stop payment (inward) 2
# Not yet presented 2
1.9.1 1) Maintain the tables of all
participating banks and their relevant
branches for clearing type purposes.
2
1.9.2 2) System should automatically pick
up the number of days required for
clearing based upon the bank and
branch code / name 2
Form 8
Page 170 of 248
1.1 System should generate ASCII file
of the details of instruments
presented in clearing in a specified
format? 2
1.11 System should interface with
cheque power Encoder with
Image/Reader/sorter for straight
through processing (Straight through
processing. refers to automatically
debiting the respective accounts for
inward clearing at a central /
distributed location)
2
1.12 System should display the total un-
cleared amount in the account at the
time of transaction posting and
transaction authorization also to
display the details of the cheques
pending for clearing in an account
while transaction
posting/authorization with the help of
HOT-KEYS
2
1.13 System should
1.13.1 1) Upload information / download
information from the core banking
solution to other system through
direct interfaces / electronic medium,
2
1.13.2 2) Parameterize the number of times
an instrument can be presented for
clearing and track the instruments
presented in clearing and display
appropriate warning / error
messages in the event the particular
instrument has reached the
parameterized value
2
1.14 System should support postponing
a particular clearing forcefully under
unexpected circumstances and the
system should be able to mandetorly
capture the reason for such
postponement.
2
1.15.1 1) Support instruments payable
AT PAR. 2
1.15.2 2) Generate a collection
schedule for cheques payable at par.
2
1.15.3 3) Automatically reconcile
payable at par cheques received in
clearing. 2
1.15.4 4) Validate the inward AT PAR
clearing data with master Data
available centrally and generate
returns with valid Return Reasons. 2
Form 8
Page 171 of 248
1.16 System should consolidate
balances in all net clearing accounts
at defined time interval for bank’s
overall clearing position ( e.g. intra
day , end of day etc.) 2
2 INWARD CLEARING
2.1 At CPC/Service branch System
should : -
2.1.1 1) Sort out Inward Clearing Cheques
received from Clearing house /RBI 2
for CBS & NON-CBS
branches. 2
2.1.2 2) Support Straight through
processing with the data posted by
RBI / clearing houses on the web
sites or data received via electronic
media 2
2.1.3 3) Generate MF (Manifold) advices
to be forwarded to branches along
with instruments 2
2.2 System should capture images at
least following details of Inward clg
cheques-
#presenting bank and branch MICR
code
#account no 2
#Transaction code 2
#Instrument no 2
#Drawee branch MICR code 2
#Amount 2
#Date of Instrument 2
#Beneficiaries name etc. 2
2.3.1 1) Identify entry as below-
i) Listed but not received
and 2
ii) Received but not listed. 2
2.3.2 2) Generate corresponding
accounting entries automatically 2
2.3.3 3) Generate RBI forms “A” & “ B”
incase of listed but not received and
received but not listed for receivable
& payable Amount. 2
2.4 System should Interface with
cheque readers to-
2.4.1 1) Generate Bank wise Reports
for Clearing Difference & Claim
Letters 2
Form 8
Page 172 of 248
2.4.2 2) Write – off the Clearing
Difference entries pertain to
particular Period for particular
Service Branch at HO level and
transfer the entries to specified
account as a consolidated effect or
as individual entries as specified in
the Case.
2
2.4.3 3) Generate Pay orders for Valid
Claims received by Other Banks
after reconciling the pending
Clearing Suspense Payable Entry. 2
2.5.1 1) Generate a report as on a
particular date / range of dates for
the total amounts receivable /
payable under each time zone for
the branches as well as RBI. 2
2.5.2 2) System should display and
print all instruments at the branch
which have been uploaded at the
service branch for inward clearing
along with the details of the
instruments
2
2.5.3 3) System should display balances
as a shadow balance for instruments
uploaded at the service branch for
inward clearing and move the
balances to clear balances once the
details have been authorized by the
branches and it should also
authorize individual / all entries
together as desired by the bank
2
2.5.4 4) In case of Inward Clearing the
system should be able to store the
cheues not having sufficient balance
in the account or instruments
rejected separately and should have
a menu based option for the branch
head to clear / pass these
instruments as per his delegated
powers
2
3 OUTWARD CLEARING
3.1 System should :-
3.1.1 1) Support Outward Clearing 2
3.1.2 2) Capture minimum details of
outward clearing cheques such as:-
# Date of instrument 2
# Instrument number 2
#Type of transactions 2
#Bank & Branch clearing code
number 2
# Amount etc. 2
Form 8
Page 173 of 248
3.1.3 3) Generate an Outward Clearing
Memos giving consolidated details of
all cheques sent to the City
Processing Center/ Service Branch. 2
3.2 In case of Outward Clearing System
should : -
3.2.1 i) Automatically balance the total
value of cheques deposited by the
customer through one credit slip,
otherwise display an error message
with unique customer I D Number 2
3.2.2 ii) Consolidate the clearing credits of
particular customer having different
types of accounts with unique
customer I D Number 2
3.2.3 iii) Automatically update account on
inward/outward clearing & cheques
returns 2
3.2.4 iv) Change the credit date with
Appropriate authority on basis of -
# Input date wise 2
# Bank & Branch wise 2
# Region wise 2
# Credit date wise 2
3.3 System at service branch level
should: -
3.3.1 1) Enter number of instruments
collected for outward clearing along
with consolidated amounts by the
branch on a particular date and to
compare the same at the time of
individual instrument entry made by
the branches.
2
3.3.2 2) Display appropriate warning
messages in the event the control
total entered at the branch does not
match with the totals after the
individual instrument entries is
completed at service branch/ CPC.
2
3.4 System at service branch level
should: -
3.4.1 1) Maintain and store BATCH
TICKET NUMBER. (Cheques a BR.
are clubbed in batches of 200
cheques each batch is given a
unique BATCH TICKET NUMBER)
2
3.4.2 2) Group all BATCH TICKET
NUMBER for a particular day under
a particular BLOCK TICKET
NUMBER and print a report listing
the individual batch ticket numbers
along with the total instruments and
amounts and a cumulative total of all
instruments and amounts under a
batch number
2
Form 8
Page 174 of 248
3.4.3 3) Query based on BATCH
TICKET NUMBER and OUTWARD
MEMO NUMBER 2
3.5.1 1) Generate a branch – wise
Outward memo with cumulative
totals. 2
3.5.2 2) Maintain the net figures Zonewise
(total instruments presented for
clearing) outward – total inward
clearing at the service branches for
comparing the same with the RBI net
figures
2
3.5.3 3) Support netting of branches i.e.
(total instruments presented for
clearing) outward – total inward
clearing received = including
( + / -) adjustments and returns . 2
3.5.4 4) System should generate advices
for non-CBS branches. 2
3.6.1 1) Print a detailed and
consolidated report at the service
branch for all outward-clearing
cheques branch-wise. 2
3.6.2 2) Generate branch wise
/consolidated flat files for outward
clearing in the format as prescribed
by RBI. 2
3.6.3 4) Merge the flat files received by
the service branch for non-core
banking branches for consolidation,
reconciliation and reporting
purposes. 2
3.6.4 5) Charge discount charges on
purchase of an instrument earlier
sent for collection, credited to the
party through manual intervention,
also system should reverse the
purchasing of cheque on realization
of the same
2
4 HOME CLEARING
4.1.1 1) Handle local clearing cheques. 2
4.1.2 2) Support Home Clearing (cheques
drawn on Central Bank branches) for
all branches not connected to the
core banking solution, 2
Form 8
Page 175 of 248
4.1.3 3) Print a report of all the
transactions (debit/credit) effected
through home clearing (i.e.
transactions from other branches on
a particular and transactions by a
particular branch on other branches)
based upon user definable
frequency e.g. on authorization of
the transaction, day-end etc.
2
5 HIGH VALUE CLEARING
5.1 System should identify: -
5.1.1 1) High value clearing. 2
5.1.2 2) Metropolitan area clearing
(e.g. fort clearing in Mumbai. It is
also referred to as “Same Day
Clearing”) 2
5.1.3 3) Generate flat files for both High
Value clearing and Metropolitan area
clearing in the desired format as
prescribed by RBI 2
5.1.4 4) Consolidate the flat files at the
service branch Bank – wise
and generate a schedule of all
cheques collected under high value /
metropolitan area clearing, bank –
wise with details of each instrument
under a particular bank.
2
5.1.5 5) Consolidation of the various flat
files generated at the branches. 2
5.1.6 6) Generate a separate
consolidated flat file in the desired
format as prescribed by RBI at the
service branch 2
5.1.7 7) Generate a summary of all
transactions bank – wise for
cheques collected under high value /
metropolitan area clearing. 2
5.2 System should generate and
consolidate flat files in the prescribed
format for INTER BANK CLEARING
(unqualified cheques i.e. cheques
drawn in favor of “Central Bank”) for
Non- RTGS area.
2
6 NATIONALCLEARING (NCC)
6.1.1 1) Support NATIONALCLEARING
(NCC) 2
6.1.2 1) Print a schedule for National
Clearing Cheques (NCC) at the
Service Branches/CPC for cheques
collected by the branches drawn on
any NCC centers designated by RBI
including Delhi, Mumbai, Chennai,
and Kolkatta.
2
Form 8
Page 176 of 248
6.1.2 2) Print the Schedule branch-
wise with cheques clubbed NCC
center-wise for tallying purposes at
the Service Branches/CPC. 2
6.1.3 3) Allow the user to key in the
data /upload the same using any
electronic medium at the Service
branch/CPC for National Clearing
Cheques (NCC) collected by
branches, which are outside the
Core Banking Solution (CBS)
2
6.1.4 4) Generate a consolidated
report for all National Clearing
Cheques collected (Center –wise
with details of all instruments) by all
the branches, manually
keyed/electronically uploaded linked
to a particular Service Branch/CPC
2
6.2.1 1) Generate automatically a unique
National Clearing code number for
each consolidated lot. 2
6.2.2 2) Generate automatically an CR.
advice for the branches, for realized
cheques sent on National Clearing to
various centers along with the
national clearing code number 2
6.3.1 1) Automatically credit the respective
customer accounts upon realization
of the cheques based upon user
definable criterion e.g. the national
clearing code number +date
+amount+ account number etc.
2
6.3.2 2) Generate a report of all
realization entries branch-wise at the
service branch as well as at the
individual branches (as define). 2
7 CHEQUE TRUNCATION
7.1.1 1) Interface with the Cheque
Truncation System as required by
the statutory authorities for
automated data capture or upload
/download of files as required, 2
7.1.2 2) Apply Charges for Truncation
based Clearing 2
7.1.3 3) Compare signatures on
cheques with the ones linked to an
account 2
7.1.4 4) Generate reports as on a
particular date /range of dates for
cheques presented though the
truncation system along with day-
wise consolidated totals. 2
Form 8
Page 177 of 248
7.15 The scanned image and the
signature of the customer should be
visible on the same screen for easy
comparison 2
8 CLEARING RETURNS
8.1.1 1) Mark a clearing as a Return
Clearing zone wise. 2
8.1.2 2) Parameterize cheque return
charges for both Inward & Outward
returns (e.g./ as per reason of return,
flat rate, percentage, slab rate,
minimum/maximum charge limit etc.) 2
8.1.3 3) Mark return cheques with valid
reasons & print return memos in
prescribed formats (e.g. Fund
insufficient, Stop payments etc.) 2
Maintain cheque RETURN
REGISTER such as return date,
bank-branch, reason, etc. and
generate reports accordingly. 2
8.1.4 4) Generate a cheque return advice
(outward return memo) electronically
or otherwise for the customer
indicating cheque number, the
amount of cheque, return charges
debited (for the customer purpose)
2
8.1.5 5) Represent the cheques returned
in clearing for technical reasons like
Endorsement irregular present
again. 2
8.1.6 6) Check inward clearing returns
data whether returns are actually
presented by bank or not 2
8.2.1 1) Display and print all rejected
instruments separately uploaded by
the service branches at the branch
along with the reasons for rejection. 2
8.2.2 2) Support recording / passing of
rejected instruments through
appropriate authorization 2
9 DIVIDENT/INTEREST WARRANTS
ETC.
9.1 System should support: - at par
payment of dividend warrants,
interest warrants, refund orders
under direct assignments and under
agency arrangements
/correspondent banking
2
9.2 System should: -
9.2.1 1} Have the facility for payment of
dividend warrants / interest warrants,
refund orders etc. for customers 2
Form 8
Page 178 of 248
9.2.2 2} Upload the master details of
warrants issued, provided by
customer through any electronic
medium or manually entered in the
system and maintain the stock
details.
2
9.2.3 3} Identify each customer though a
unique customer ID 2
9.2.4 4} Validate each debit in the
customers account against master-
list 2
9.2.5 5} Reject stale, post dated and
stopped warrants 2
9.2.6 6) Capture and store the signature of
the authorized personnel for each
customer account. There should be
no limit on the number of signatures
that can be captured and stored 2
9.2.7 7) Support Revalidation of stale
warrants. 2
9.2.8 8) Capture details of re-validation of
stale warrants in the event warrants
have been re- validated 2
9.3 System should Support batch entry
for bulk deposit postdated cheques
(WARRANTS etc.) (PDC) etc; and to
define a time limit and amount for
posting of post dated cheques
(WARRANTS etc.) account – wise
2
9.3.1 1) Ability of the system to identify
warrants, whose payment
instructions are not issued but
received for payment 2
9.3.2 2) Ability of the system to Pass
forcefully certain warrants even
though it has identified the warrant
as Return (parametererized) 2
10 EFT/ECS (ELECTRONIC FUND
TRANSFER/ELECTRONIC
CLEARING SYSTEM)
10.1.1 1) Interface with Electronic Fund
Transfer (EFT) software provided by
RBI and 2
Interface with the Electronic Clearing
Service (ECS) software for
instrument returns and validations
provided by RBI 2
10.2 System should upload & download
data in the desired format and print
reports as desired (e.g. branch –
wise, zone – wise etc.) for Electronic
Clearing Service and EFT Service
received from RBI / clearing houses.
2
Form 8
Page 179 of 248
10.3 System should Provide income –
expenditure report based on actual
float that was available, Expenses
incurred towards MICR / ECS,
Courier Charges against the income
from service Charges and notional
income at prevailing Call Money
lending rates
2
11 RECONCILIATION
11.1 System should Track the movement
of instruments from Branch to
Service Branch and Reconciliation &
Control Method to ensure that all
instruments physically received at
Service Branch, by generating MF
(manifold advices) both at service
branch and branch level
2
11.2.1 1) Generate service branch
Adjustment account entries age wise
for reconciliation. 2
11.2.2 2) Generate Service Branch
Adjustment Account Debit Entry
pertaining to branches by following
principals of Mirror Accounting (1-4). 2
11.2.3 3) Create ASCII File for
reconciliation at IBR (INTER-
BRANCH RECONCILIATION
DEPARTMENT) 2
11.3 System should Support and keep
track of transaction for borrowing /
lending funds to other banks and
maintain details for due dates for
settlelements and over dues. 2
11.4.1 1) Send messages to the Fund
providing branch when clearing is
Adverse and generate messages
when funds are Surplus. 2
11.4.2 2) Track fund outflow from
particular accounts specifically
towards the other Financial
Institutions / Financial Service
Providers 2
11.5 System should display pending
Receipts from Bank with Details of
Each Transaction 2
11.6 System should Reconcile the
transactions passed by bank &
passed at Clearing House &query on
branch reconciliation number? 2
11.7 System should generate Reports
as below: -
11.7.1 1) Consolidated statement Bank -
wise of amounts "Due by them" as
per user defined format 2
Form 8
Page 180 of 248
11.7.2 2) Daily status of net amounts "due
to " or "due by" clearing house 2
11.7.3 3) All statements as per RBI format
for all types of clearing 2
11.7.4 4) Bank - wise listing of cheques for
outward listing 2
11.7.5 5) Cheques returned unpaid
(outward) - all cheques that were
sent out as part of outward clearing,
but have been returned unpaid 2
11.7.6 6) Cheques returned unpaid (inward)
- all cheques that were received as
part of inward clearing, but have
been returned unpaid 2
11.7.7 7) Consolidation of various RBI
clearing settlements accounts
maintained by the service branches
on a periodic basis (as
parameterized) for overall fund
positions
2
11.8 System should Support entry and
upload of NON _ CORE BANKING
BRANCHES data at the NODAL
/FOCAL branches for consolidation,
aggregation, reporting and MIS
purposes for all types of clearing
handled by the Bank, also whether
system Supports individual
/consolidated printing of entries for
all type of clearings for both CORE
BANKING and NON-CORE
BANKING BRANCHES.
2
12 Draft Payment
12.1 1) System should interface DD
Payment issued by Non-CBS
branches. 2
12.2 2) Able to upload officers
signature with index number and
also option to add/delete/suspend
etc. and display specimen signature
during payment by index number. 2
12.3 3) DD payment module (Advice
& Ex-advice cases) with check
system like stop/stale/cancelled/paid
draft. 2
12.4 4) DD paid in absence of advice
and to generate report for this in
letter form with details of draft
addressed to branch for
confirmation. 2
12.5 5) DD Advice posted but DD
cancelled – Credit advice to be
generated for branch for reversal
entry pass. 2
Form 8
Page 181 of 248
12.6 6) Payment of duplicate draft
issued on back date with different
alpha numeric (advice posted)
number. 2
12.7 7) DD lost, forged, stop payment
warning. 2
12.8 8) DD with serial number and /or
alpha numeric number mismatched:
flexibility to pay at certain level of
authorization. 2
13 Reports: Draft Payment
13.1 1) Ex-advice paid DD register
branch wise containing date, Sl No,
alphaneumeric No. of DD etc. 2
13.2 2) Advice paid but DD not
reached. 2
TOTAL 364
Form 8
Page 182 of 248
Comments
1 Remmitance
1.1 SECURITY
1.1.1 System should record stock receipt
& issue details
DDs/Pos/Chequebooks/FD
Receipts/MTs
2
1.1.2 System should check for duplicate
cheque numbers at the time of stock
entry of cheque books in the system.
2
1.1.3 System should maintain safety
levels of cheque books.
2
1.2 REMITTANCE/ DD
1.2.1 System should prompt for PAN No. if
DD is purchased with cash above X
amount.
2
1.2.2 System should generate unique
branch wise running serial number
(User configurable) for every DD
which gets initialized on a
parameterisable basis.
2
1.2.3 System should parameterise the
DD limit, DD validity period,
commission amount and other
charges applied from time to time.
2
1.2.4 System should have facility to
parameterize waiver of / Discount
the charges with appropriate
authorisation by the defined
authority.
2
1.2.5 System should be capable of
automatically printing the draft once
the transaction is authorized by the
bank official on continuous
stationary? Option should be
available for printing it manually also.
If problems comes in DD printing, is
there any option of printing a DD
again.
Form 8
Page 183 of 248
Remittance
1.2.6 Capability of maintaining and
monitoring the stock of drafts on a
centralised basis from where the
stock can be allocated to different
branches and provision to trigger
message for replenishment of stock
when reaches minimum buffer level.
2
1.2.7 Provision of printing phone no of
issuing branch.
2
checking whether the DD is in the
stock before issuance and printing
2
generating advices in electronic and
print forms to communicate the
paying branch for DD amount of
Rs. X /= and above. Is there an
option to communicate the advice to
all non-cbs branches by email.
2
1.2.10 CapSystem should upload bank
draft details from non CBS branches
into the CBS system. This capability
shall be of two ways i.e. inward and
outward.
2
1.2.11 System should support restriction on
issue of DD numberwise,
amountwise for different categories
per month / per year
2
1.2.12 System should support capturing of
specimen signatures with index
numbers of the authorised officers of
the bank in a specimen signature
album on-line which can be updated
from time to time.
2
1.2.13 System should display the specimen
signature of the signatory of the
draft, when his index number is
mentioned.
2
1.2.14 System should perform day-end
check for DDs authorized but not
printed
2
1.2.15 System should define instrument
validity period parameterisable
2
1.2.16 System should support bulk
issuance of drafts through a batch
upload? 2
Form 8
Page 184 of 248
Remittance
1.2.17 System should support demand draft
issue requests through Internet/other
modes with appropriate
authentication i.e. through secret
PIN code.
2
1.2.18 System should support for inclusion
of other mandatory charges like the
cost of courier, etc along with the
commission, in respect of drafts
directly sent to the customer from the
centralised location / branch?
2
1.2.19 System should display details at a
single query of all the remittances
both inward and outward of any
single customer.(To know customer
profitability)
2
1.2.20 System should support remote
printing of statements / DD's I.e DD
entered in mumbai but printing for
the same to be done in Delhi
2
1.3 ISSUANCE OF DUPLICATE DD
1.3.1 System should display status of DD

based on DD number, DD amount,
issue date, issuing branch, and track
the paid / stale / Lost DD .
2
1.3.2 System should permit revalidation of
DD 2
1.3.3 At the instance of duplicate DD
issued, syatem should emboss
duplicate DD with some
parametrizable caution like
“Dupliacte DD issued in lieu of DD
serial no-------- printed
no---------------- dated-----------” .
2
1.3.4 System should accept the indemnity
details (e.g. purpose of indemnity,
date of draft, draft serial No. And
printed no., amount of DD, drawee
branch, reference no. Etc.) And
generate a unique reference no. for
the same. The system should check
whether the draft has already been
encashed or not at the time of entry
of indemnity details.
2
1.4 STOP PAYMENT/CANCELLATION
Form 8
Page 185 of 248
Remittance
1.4.1 System should display the details of
the draft upon entering the draft
number to be stopped and upon
verification of the same by the
officer, it can mark the draft as
stopped ?
2
1.4.2 System should facilitate cancellation
of the DD issued. And charge for
cancellation accordingly.
2
1.4.3 For cancellation of DD, system
should provide for different heads to
be debited/ credited as
parameterized by the bank. Eg. For
cancellation of DD > 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
Form 8
Page 186 of 248
Remittance
1.5.4 System should facilitate issuance
multiple DDs against one single
credit or one DD against multiple
credits. 2
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
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
Form 8
Page 187 of 248
Remittance
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
cheques with Postage,
1.9.2 Commission, full detailsExchange, 2
other charges Max/Min.should be in
1.9.3 Auto generated schedules, for
the system. 2
1.9.4 banks/branchwise.
Facility for modification/deletion of 2
bills.
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
charge overdue interest. reminder / 2
fate enquiry of cheques / received, to
1.9.8 Facility
Banks /toBranches
store bank address
and customers. 2
book/directory of other bank
branches published by RBI whether
1.9.9 System should be
there is branch able to generate
of bank which thea
report
bills is of
to all
be instruments grouped for
sent for collection.
upcountry clearing with at least the
1.9.9.1 following
*Presentation
details 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
centre for upcountry clearing
1.10.2 2) Generate
cheques a special
collected collection
by branches, 2
schedule
which arefor all other
outside the cheques
Core Banking
1.11 ROB/POB
received byAccounts
Solution (CBS) the collection centre for
upcountry
1.11.1 System should clearing
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
Form 8
Page 188 of 248
Remittance
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
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
Page 189 of 248
Remittance
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
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
Form 8
Page 190 of 248
Teller Transactions
1.11 System should print the end of day
teller log./ Date wise /Teller wise 2
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 :
Form 8
Page 191 of 248
Teller Transactions
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
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 transactions. 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 offline 2
transaction processing
2.7 System should have “Store” and
“Forward” mechanism to record off – 2
line transactions (for business
continuity during loss of
connectivity / breakdowns)
Form 8
Page 192 of 248
Teller Transactions
2.8 System should map all nodal / focal 2
branches to the link branch (i.e. the
branch where the main account is
System should maintain off - line
2.9 held)
limits for branches and enforce the
same in the event of off - line mode. 2
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 respective
account heads shouls be updated 2
and discripiancies / erors if any
should be dispalyed
2.11 Maintaining a record and printed. At
for signatures 2
the time of
changed upload to for
/ cancelled theacore
particular
banking
account the system should validate
2.12 System
the datashould
with theallow the data
master user in
(Bank)
the
to define the different
core banking solution 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)
e.g. only for stop payments, issue of
2.17 System
chequesshould
numbersmaintain
etc. rate tables,
conversion rates, cross currency
rates etc. at a global level for
different currencies as designate by
the bank 2
Form 8
Page 193 of 248
Teller Transactions
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
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
Form 8
Page 194 of 248
Teller Transactions
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
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
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
Page 195 of 248
Teller Transactions
Comments
1 Lockers
1.1 System should provide standardized 2
document –processing checklist as
1.2 System
defined inshould capture customer
the document
details
management module. customer ID in
upon entering
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 if 2
any
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
Form 8
Page 196 of 248
Lockers
1.18 Parameter to fix grace days for
payment of rent. Flexible Parameter. 2
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
Form 8
Page 197 of 248
Lockers
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
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
Page 198 of 248
Lockers
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 transaction. 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
Form 8
Page 199 of 248
Interest, Commission and Charges
1.13 System should define add – on rates
(+ / -) at the account level upon
appropriate authorization 2
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
Page 200 of 248
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
along with the adjusted amounts.
2
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
Form 8
Page 201 of 248
2.4.4 Ø Statement generation fee 2
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 accounts 2
2.4.14 Ø 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 etc. 2
2.9 System should define add – on
charges rates (+ / -) charges at
group level/Customer level/account
level upon appropriate authorization 2
Form 8
Page 202 of 248
2.10 System should accrue charges /
commission and apply after a
parameterisable time period 2
2.11 System should generate the
separate report for each type of
charge / commission applied 2
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
Form 8
Page 203 of 248
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
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
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
Form 8
Page 204 of 248
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
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
Page 205 of 248
Comments
1 Issue of Cheque Books
1.1 System should specify the
accounts / products for issue of
cheque books for defined number of 2
1.2 cheque
System leaves
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 system. 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
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
Form 8
Page 206 of 248
Cheque Book and SI
1.16 System should view the status / fate
of a cheque leaf /range of cheques /
cheque books for a particular
account 2
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 instruction 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
Form 8
Page 207 of 248
Cheque Book and SI
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
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
Form 8
Page 208 of 248
Cheque Book and SI
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
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
letters at user definable time
intervals (paramerisable) e.g. after 2
retries generate a warning letter 2
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
Form 8
Page 209 of 248
Cheque Book and SI
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
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 Instructions 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 authorization 2
Form 8
Page 210 of 248
Cheque Book and SI
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
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 / entries 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
Form 8
Page 211 of 248
Cheque Book and SI
TOTAL 192
Form 8
Page 212 of 248
Cheque Book and SI
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
Page 213 of 248
General Banking
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
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
Page 214 of 248
General Banking
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 account 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
Page 215 of 248
General Banking
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 system. 2
Form 8
Page 216 of 248
General Banking
11.3 Passbook is to be generated for
entire deposit amount, instead of
one receipt for each unit. 2
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 default charges.
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
Form 8
Page 217 of 248
General Banking
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
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
Form 8
Page 218 of 248
General Banking
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
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 outstanding.
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
rollover as per the terms of standing
instructions (e.g. Interest & Principal,
interest only, interest and part of
principal, principal only, etc.) 2
Form 8
Page 219 of 248
General Banking
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
calculating and displaying the
maturity amount along with
deductible TDS amount if any as
defined in the TDS module 2
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 outstanding.
2
Capture the following
renewals/settlement instructions and
renew/settle Deposit Account as per
instruction automatically on maturity
date.
2
Form 8
Page 220 of 248
General Banking
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 applicable 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
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 dating. 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
Form 8
Page 221 of 248
General Banking
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
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
Form 8
Page 222 of 248
General Banking
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
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
Page 223 of 248
General Banking
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
Form 8
Page 224 of 248
Cash Management
3.12 System should support initiation,
verification and authorization of all
payment activities from any location
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
Form 8
Page 225 of 248
Cash Management
8.2 System should have capability of
generating event based alerts from
any of the transaction processing
systems 2
9 Infrastructure 2
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 integration tools 2
TOTAL 126
Form 8
Page 226 of 248
Cash Management
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
Form 8
Page 227 of 248
Inspection
2.27 Submission of various returns - satisfacory/Not 2
satisfactory
2.28 Customer service - satisfactory / not satisfactory 2
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.
Form 8
Page 228 of 248
Inspection
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
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
Form 8
Page 229 of 248
Inspection
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
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 with 2
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
Page 230 of 248
Inspection
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
Page 231 of 248
AML
3.3 2
The AML system should provide a list
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 2
The AML system should enable the
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 2
The AML system should provide for
completely customizable Mandatory
Fields Template allowing the user
complete flexibility in case any
changes / additions are required in
mandatory fields.
3.6 2
After setting the Fields for each
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 2
The Mandatory Fields Missing Report
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 2
The AML system should provide a
Link 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.
Form 8
Page 232 of 248
AML
3.9 2
When a user’s name is entered in the
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.
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 2
The user should also be able to
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 2
A search made on a customer’s
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 2
Once these relationships are found,
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 2
The AML system should enable the
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
computation of customer's expected
behavior based on his CIF details and
risk profiling
reassessment of customer risk,
reclassification and recreation of
customer behavioral profile
5 Transaction Monitoring
Form 8
Page 233 of 248
AML
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
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

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.
Form 8
Page 234 of 248
AML
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.
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
Form 8
Page 235 of 248
AML
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
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:
Form 8
Page 236 of 248
AML
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.
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
Form 8
Page 237 of 248
AML
7.6 2
The AML system should provide for a

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 2
Any folder in the Case Manager
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
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
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.
Form 8
Page 238 of 248
AML
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
11.1 2
Default Benchmarks –The AML
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 2
Visual Benchmarking – The AML

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 2
Specific Benchmarking feature in 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
Form 8
Page 239 of 248
AML
12.1 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 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.
12.4 2
The parameters that should be

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 2
Using the customer peer review graph
the user should be able to make
comparison between two or more
customers on any of the above-
mentioned parameters.
12.6 2
The AML system should provide for an
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.
Form 8
Page 240 of 248
AML
12.7 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 2
The user should also be in a position
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 2
The user should also have the option
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 2
The above graph should enable the
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.
12.12 2
The user should be able to view the
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 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 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.
Form 8
Page 241 of 248
AML
12.16 2
fired on the all instruments across the
users to focus on the instruments
whose alert weightage are high. Alert
weightage on instruments should be
is fired.
12.17 2
fired on the all products across the
users to focus on the products whose
alert weightage are high. Alert
weightage on products should be
is fired.
12.18 2
The AML system should provide for
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 2
The user should be able to view any
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.
12.2 2
The Customers Flip Table should
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 2
The Product Flip Table should allow
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.
Form 8
Page 242 of 248
AML
12.23 2
The AML system should have a
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
14.1 2
The AML system should have

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 2
The AML systems should maintain
comprehensive Audit Trails detailing
every user activity. Audit Trail reports
should be generated and may be
viewed on-screen and/or printed.
15 Help
Form 8
Page 243 of 248
AML
15.1 2
Complete Online context sensitive
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
Page 244 of 248
AML
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. both 2
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
6.4 Storing Documents
Form 8
Page 245 of 248
Document Imaging
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
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.
Form 8
Page 246 of 248
Document Imaging
6.7.1.4 A comprehensive security system must allow the system 2
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 and 2
text to preserve confidentiality
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.
Form 8
Page 247 of 248
Document Imaging
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 documents 2
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
Page 248 of 248
Document Imaging

Form 08 - Functional RFP

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Form 08 - Functional RFP

Загружено:

Авторское право:

Доступные форматы

Centralised Banking Project RFP

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

Functional RFP - Scoring Sheet

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

9 Some Other Examples of Incorrect Responses

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

3.1 System should record basic Master Data for 2

5.9 System should be able to define various 2

5.12 Should handle unlimited number of allowances 2

5.14 System should compute the Provident 2

5.19 System should support passing of accounting 2

9.8 System should support preparation of lists of 2

10.3 System should provide managers the 2

18.2 System should have Rules and Officer Service 2

20.2 System should maintain details of the 2

25.1 System should maintain details of staff 2

The system should capture data

1.1.8 The system should have the facility to 2

1.1.12 System should have “Maker” 2

1.1.15 System should store the unique 2

1.1.16 System should update the Internet 2

1.1.21 System should send intimation, 2

Ø Those transactions that require

1.3 Account Services

1.4.9 The system should allow a user to 2

1.5.5 The system should have the facility to 2

1.6.19 The system should identify each 2

1.8 Utility Bill Payment

1.9 Personalised Account Information

1.10 Customer Service & Information

1.11 Credit / Debit card Transactions

1.12 Demat Services

1.13 Trade Finance

1.14.7 System should link the transactions 2

1.15 Tax Collection Services - on - line

1.16 Collection Services

1.16.9 System should link the transactions 2

2.1.11 System should store the unique 2

2.1.12 System should update the Phone 2

2.1.16 System should announce a greeting 2

Ø Those transactions that require

2.3 Account Services

2.4.12 The system should be able to generate 2

2.5 Customer Service & Information

2.6 Trade Finance

Form 8 Page 76 of 248

3.1 Liquidity Risk Management:

Form 8 Page 79 of 248

2.1 System should generate a unique

1.23.1 A) Price sensitivity

16.17 Certificate of holding – Form X and

16.24 Part A – Bond Ledger Accounts

# Number of days for clearing 2

1.3.1 System should display status of DD

1.4.4.1 a) Pay cash to the customer over

1.5.1 System should automatically display

1.14.2.1 1. Agewise/ amount wise o/s

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

4.8 Overdrawing above limits 2

2.6 Support to accept names defined by 2

5.2 The system should support automated 2

5.5 The system should be able to known 2

5.6 The system should support 2

5.10 The AML system should provide for 2