Check List for Requirements Gathering- General & Money Market

Sr No Check List Item Details

1 Language If the users of the particular client are not

well versed with English, then the
requirements gathering might be required
to be done using the local language. If so
there should be an arrangement of an
interpreter.

2 Types of Transactions/Product Different types of transactions

3 No. of outstanding transactions No of outstanding transactions in each

category of transaction/product
Eg. Money Market
1) Call Money 10 Deals Approx on any
given day
2) Fixed Deposits 10 Deals Approx on any
given day
Securities
1) 100 Securities outstanding
2) 10 Repos outstanding Approx

4 Nature of transaction Money market transactions can have

variations with each client.

5 Prepardness of the client for data take on If currently client is using manual records,
then it is important to inform the client that
during implementation phase, the data
should be ready for keying in / Upload.

6 Accounting Policy Prepare a document for Accounting Policy

for all available transaction. In case of
securities the document should cover value
date and trade date concept, portfolios,
various products.
7 Profit Policy Profit policy for various instruments
8 Interest Calc methods / Interest Basis Various interest Basis used by the client
9 Amortization method Straight line or yield based
10 Pricing Yield or price
11
12
13
14
15
16
17
18
Significance

Preferably the interpreter should have basic knowledge of Treasury to

reduce the efforts required to explain the functionality of the product.

Get the list of all the transactions handled by client. Gather information
about each and every transaction in depth even if it looks similar to
some transaction in Kastle.
This information is necessary to know the volumes of data to be
captured during the implementation phase so that the estimation for
data capturing can be done with minimal deviation. While doing so it is
also necessary to check whether any sub transactions are present.
This would also help to devise the strategy for data take on. If data is
not much the users can manually punch in the data else we need to
have upload facility

Normally In case of money market each client may have its own
variation for a similar kind of transaction. Hence, it is important to get
the exact details of each and every transaction.
Sr Check List Item Details
No
1 Hardware availability for treasury Server & Client HDD ,RAM, processor, etc.
implementation.
2 Software availability for treasury Operating system on the server. Kastle
implementation. requires
1) Windows NT Server, Windows 2000
server.
2) For client machines, it can be Windows
XP, or Windows NT client, Windows 98
3) RDBMS - Oralce 9 or higher server
version on the server and client version on
each client machine.

3 LAN Connectivity between the server and the

4 Current mode of handling treasury
operations.
5 Types of Transactions/Product
6 No. of outstanding transactions
7 Transaction volumes
clients.
Manual/excel records or some other
software.
Different types of transactions within the
scope of treasury operations.
No of outstanding transactions in each
category of transaction/product
Average No of deals entered on any given
day.

8 Prepardness of the client for Data take on If client is using manual records, then it is
important to have the latest updated records
in place which can be keyed in Kastle
during implementation phase.
9 Accounting Policy A document for Accounting Policy for all
available transactions at various activities.
Eg. Accounting entries to be generated
during fund settlement and authorization of
an Outright purchase transaction.

10 Profit Policy Profit policy for various instruments. Eg.

11 Portfolios
12 Interest Calc methods / Interest Basis
13 Amortization method
14 Pricing
15 Mode of delivery of securites
16 Whether Master Data information can it
be sent for upload immediately, which will
be done off site
Weighted Average , Random Manual
Marking( Pick & Choose) Etc. (Any One)
Various portfolios in which the investment Is
bifurcated. E.g. Trading , Investment or
Available for Sale , Held till maturitiy etc.
Kastle supports actual/365 and 30/360
Kastle supports straight line method.
Kastle derives the cost from price.
Demat or Physical
1) All the details of outstanding securities
except the outstanding position.
2) Clients/Counterparties/Brokers/Issuers

17 Cut off Date for Data take on Outstanding data would be captured as of
current date.
18 Accounting entries download.
19 Mark to market Policy
20 Financial year start and end date
21 No of Users
The accounting entries generated from
Kastle needs to be passed on to the GL
system. Please specify the name of the GL
system
Is it currently done? If yes, then please send
us the document giving the details of the
same.
As per the Kenyan markets.
No of concurrent kastle users
Client Remarks