t24 290 Expanded Due Diligence Questions 30 Mar 2018 Ver 1 03

T24 Due Diligence Questions Expanded 30 Mar 2018 135 1
SAMMAN-LIVINGSTON IT CONSULTING (www.sam-v-it.com)
T24
EXPANDED
Due Diligence
Check
List
Summary
T24 is a full banking system for core information and products that is sold by Temenos, SA of
Geneva Switzerland. The T24 system is a complete banking system when all of the product
modules are added to the core component. The system can do all retail and corporate banking.
It can also manage securities and investments. Can also do trade finance, FX, MM, Swaps,
Derivatives, Syndications, All-in-One Accounts, and a host of other types of banking products.
The list here is not exhaustive. T24 does not do trust banking however. It is also not suitable for
very specialized FX trading work. However, it is a completely integrated system, and when set up
and configured properly it will function almost flawlessly and is very easy to configure for
functions and work processes not part of the product as it is sold.
The system however requires a considerable degree of banking knowledge to set up for an
individual client, and this document will outline the pros and cons of T24 and where many
clients get “into trouble” with a T24 implementation because of questions they fail to ask or to
consider before they purchase the system.
© Copyright, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018 by Samman-Livingston IT Consulting – All Rights Reserved – Reprint
or redistribution of this document is not allowed without written permission.
QUESTIONS TO ASK BEFORE BUYING T24 (there are 99 questions that follow in this document)
First (10) – getting the groundwork laid – basic things to consider and to ASK—and to get CLEAR
answers to from Temenos and from your own project team
1. What is your budget? A typical T24 system with minimum modules can easily cost $1 million
US or more—typical installations run in price up to $20 million USD or more. This cost may be
controlled however, but if you are a bank with a small budget, T24 may not be for you.
Anticipate a minimum of $1 million US dollars for the core and common modules (loans,
deposits, limits, etc.), and then a cost in the range of $2000 US dollars per day for skilled T24
consultants to do the setup, design, and implementation work.
2. What is you banking arrangement?—number of offices, branches, etc. ? What sort of
configuration of locations (branches) do you intend to support?—do you want Internet or
browser based access to the system? Do you want to have a fast system? (T24 is not always
“fast” depending on how it is set up and configured/customized). Do you plan to run the system
in one physical location? Do you plan to expand the number of modules in T24 in the future?
Are you planning to add considerable customizations to the system? Do you plan to run T24 in
the “cloud”?
3. Are you prepared to configure and set up the system with your own consultants and staff or
do you intend to rely on Temenos to do the initial setup and support (configuration and
parameterization)? Temenos is rarely ever able to do the full set up by themselves, or if they do
then the quality of their work is quite often low.
4. What are you replacing? Which banking system? Have you prepared a full set of business
requirements (and technical requirements) BEFORE you consider and evaluate T24? If you are
replacing an old, legacy system you should be sure to note exactly what your system does and
does NOT do before you evaluate T24. A common mistake many buyers of T24 make is that they
do not know what they have or what they need to compare against T24 capabilities and
functionality. They are often forced to rely on Temenos sales staff who are not necessarily
interested in evaluating your needs on a “low” level. Sell is the name of the game with
Temenos. Remember that. Know what you have and what you want in a full list of requirements
in a RFP before you go to Temenos. Be picky. Do not accept answers from Temenos without
them giving you proof and if needed live proof with a T24 demo via a competent subject matter
expert or technician. Get outside consultation if needed (not from Temenos) to do your T24
evaluation.
5. Are you trying to expand your business capabilities in any respect? If so make sure that you
have a full map of what new services or products you intend to offer. There are many products
that are only partially capable of being processed on T24. There are certain types of loans and
syndications that you need to examine if you’re in this line of business. Also if you are very
specialized you need to have the full product specifications in hand when you evaluate T24. A
T24 trained and experienced product specialist consultant (again, not from Temenos) would be
advisable to help you with your evaluation and due diligence process.
6. What are your sizing and speed/performance needs? How many transactions per
minute/hour do you process daily/monthly/yearly, etc. (estimate this in advance before you
consider purchasing T24)? Are you looking for a system that gives you speed and good all-
around performance under a heavy user load? Note that the more people on T24 at one time
the slower the system can be. Also, if you do not maintain the T24 system and keep file
(database) sizes as small as possible, then there can be speed and performance issues. Under
normal maintenance and for example a 50 user load, the T24 system is fast (meaning almost no
“wait” time for a transaction to take place). However, COB times are reduced by the amount of
data stored (not archived that is) in the system database. Also, customizations can slow system
performance considerably. You need to set benchmark retrieval and processing times when you
evaluate T24. Otherwise, you could be facing 4-8 hr COB (Close of Business processing) times or
more! COB speed is a common problem with a flawed T24 set up. You need to consider this fact
when you evaluate the system. Also arrange for a visit to an existing T24 client site (and one not
arranged by Temenos—do this yourself) and see exactly what the performance benchmarks
(timings) are and if the COB takes a short or long time period to run—also check for “crashes”
and “fatal error” problems that the client has encountered, what they were, and why they
happened (if they know).
7. If you are considering setting up Internet access (browser based access) to T24, remember
one thing. This system has a poor track record of browser based access and performance (it’s
typically slower on browser access). Again, ask for a demonstration somewhere. Also if you are
planning a large installation (more than 100 concurrent users), then you have to check what the
general performance is on the browser system opposed to the GUI system opposed to the
Classic (character-based) system. If you are accessing T24 from any remote location to a central
server and you do not have adequate bandwidth on your telecom lines, you will face major
performance and “speed” problems with T24. Ask about this before you buy it!! Likewise, other
versions of T24 such as the standard GUI one or the Classic one can be slow also if you are
accessing via a telecomm connection to a remote central server in a foreign country (not in your
own country that is). GUI and Classic are not used anymore, but there are concerns now with
T24 in the “cloud” and on the internet. There have been major changes to the way T24 works
and is delivered since about 2010. Get the full story on the current Java release (they call it) of
T24. Also decide which database you are going to use (Oracle, DB2, SQL, etc.).
8. What sort of project are you planning to conduct? This goes back to the questions about
product and design, but if you are going to have a major rebuild of your core banking system
(accounting, CIF, G/L, limits, loans, deposits, F/X, trade finance, etc.), then you need to consider
if you have the skills in-house to do a proper and complete T24 core design. More on this
question later, but you need to understand you own legacy (current system) design and what
you would have to do in order to at least “copy” it to T24. T24 is strong on core, but it is weak
on the same if you do not know how to design a core set of parameter table values in order to
have the products, limits, G/L, reports, and CIF all coordinated properly. It is possible to build
the core of T24 in a way that is not consistent across these areas which will result in major
problems with reporting and with G/L entries later on. Seek a consultant on core banking to
assist you with your own needs with T24. This is the most important area to consider when
buying T24. Can you do a proper core configuration and/or design? Typically Temenos cannot.
This takes skill! Find someone who can. And the T24 “model bank” is not reliable. Its design is
somewhat “cobbled” together and erratic (or inconsistent with low quality control in its design).
Remember that the model bank as Temenos calls it may not be for you! See #10 for more on
this statement.
9. Are you planning to do specialized products in securities, trade finance, treasury, derivatives,
loans, deposits, or mortgages? Work out what your complexities are there before looking at
T24. It has reasonably good capabilities in all of these areas except securities processing which
is extremely difficult to set up if you don’t know how to design and parameterize this module on
the T24 system. Securities processing is a "system in a system" (so to speak) on T24 and is not
one that many except the most skilled T24 consultants can set up properly.
10. Are you being asked to buy and use "as is" the T24 “model bank”? ANSWER—don’t because
it is not a good design in the model bank they offer. Banks who take the “model bank” and think
they can run it successfully “out of the box” are always sadly disappointed. Ask yourself if you
are prepared to configure (and design from “scratch”) the T24 system yourself. This requires skill
too. Be prepared to ask yourself if you can find a good T24 core designer who is not employed
by Temenos to assist you.
What are you willing to go through regarding development and implementation time??
11. T24 is not a “fast” system to set up. Temenos will say they can do it in 3 – 6 months. THAT IS
NOT TRUE!! Any respectable T24 consultant (an honest one) will tell you that it takes up to 2
years to set up and properly and thoroughly test a fully configured T24 system for a LARGE (full
service) bank. What are your time frames? BE realistic with yourself!
12. Are you prepared to deal with T24 consultants whose reputation is not always that of
“quality?” Do you know what sort of issues you face and whether you are willing to have
outsourced work done to set up your system (or consultants brought on-shore who are
probably not familiar with either your country’s banking laws, banking needs, or language)?
Oftentimes Temenos consultants are not "long" in experience nor are they “high” on skill. A
typical Temenos junior consultant has less than three years of T24 experience. This is NOT
enough for working on complex installations. It may be all right for “cut and paste” type model
bank “builds,” but if you want a truly customized T24 system for your bank, then you must be
prepared to hire non-Temenos consultants to help you. Are you willing to go this route or are
you going to rely totally on Temenos to get you through the set up process?
13. What sort of interfaces do you require to T24, if any? This is a separate discussion, but you
should know before you buy. T24 can be interfaced to almost anything, but it is not a “ready-
made” process. You will require technical expertise in this area.
14. Are you doing complex regulatory, IFRS, and MIS reporting? T24 does not have a strong
reporting tool in the core. Enquiries in T24 are likewise not easy to build. Are you prepared to
purchase a third party reporting tool? Evaluate your reporting needs (regulatory reporting in
particular and MIS) beforehand. Get a full list of all of your reports into the RFP. Present them to
Temenos to see what they say. Typically T24 alone is not good for any complex reporting. You'll
need add-on systems, SQL, or a database "outside" of jBase (the T24 “native” database) that is
easier to work with.
15. What sort of limit (credit/risk) management do you currently have? T24 has an excellent
global and “simple” limit management module (you can do either, but you should not do both
together); but again it must be carefully set up and designed after a solid core (Category design
as it is called in T24) is set up. Evaluate your limit and credit management needs. This takes an
expert on T24 in this area to assist you by the way. Few Temenos consultants really understand
the capabilities of the Limit (and Collateral) modules in T24 or how to set up these modules
together to work correctly—especially for nostro limit management and limit/collateral
reporting.
16. Are you looking at training your own staff to do post-live support on T24? You should.
Temenos is very expensive for post-live support. Most banks have at least one (1) full-time
Temenos-trained, T24 staff consultant for routine in-house business and technical needs.
17. Are you being promised functionality that will have to be developed by Temenos in the
future? Again, do not accept “future release” availability for any function not already in T24. Are
you prepared to wait for such development or even worse PAY for it yourself as a
customization? If you have a large amount of customization, T24 is still a possibility for you, but
know the potential costs you may face.
18. The greatest mistake that most T24 customers make is that they “can do it (set it up/design
it) mostly by themselves. ” True and false? (Answer is False) But the point to make here is to ask
this question—"Does my company believe it can actually manage a full T24 implementation
successfully by itself?” Project managers for T24 are everywhere, but few are really all that
competent. Note that even Temenos admits that world-wide there are only about 1000 people
who know how to set up a T24 system correctly (if that many—I only know of about 50 or less
whom I’d trust). And of that number even fewer really know how to manage (from a true PM
point of view) a T24 project. Think what your needs are for project management. Ask this
question of yourself first, not of Temenos. They will provide “project managers,” but you may
not like what you get from Temenos to be honest.
19. Are you willing to evaluate at least two (2) competitor systems to T24? You should evaluate
at least two others. Then make your own comparison. Many customers take T24 because
Temenos promises initially a VERY LOW price for the license and for the yearly maintenance fee.
Don’t be fooled. The idea is to sign you up. They do not take the configuration work seriously
after you’re a T24 customer. Then you’ll see the prices you are charged escalate every time you
want something "extra" done. Get the truth! Get the prices from other banking system vendors
too. Then when you get their lowest price, you can multiply it by a factor of at least 3x to get
your “true” estimated implementation cost. Caveat—you can put in T24 for a small sum if you
know how to. Don’t think that this system is going to run you over $2-3 million at most if you
know how to manage the vendor and how to manage a project. They go together.
20. Are you a bank that is located in a remote location (E. Europe, Africa, Middle East, Asia,
etc.)? Then you should consider that Temenos is not really able to support you adequately in all
of the “more remote” locations. There are "other vendors" who say they can support you on
T24 in remote locations too (these are "Temenos partners" usually) but they are only “selling”
to you also. Non-Temenos vendors (that is, Temenos “partners”) have limitations too in their
overall competency. Check the track record of other banks in your locale who may have
purchased T24 and see what they tell you about "other vendors" and consulting firms that they
may have used who say they can support your project and implementation needs in more
remote locations.
The nature of the project, questions to ask in this respect. . .
21. OK, you’re going to buy a T24 banking system. Now what? First off, what does your bank
know about effective and GOOD project management and team/skills structure? If you can’t
answer this question with specific details, then you need to ask yourself if you are prepared to
hire either a Temenos or a non-Temenos project management team. That does not mean some
"big name" consulting firm (such as Accenture, Ernst & Young) or whomever. They are not much
better in project management than many smaller vendors. You must manage the project
yourself—and with your staff/consultants. Are you prepared to do that? This is a big question to
ask yourself, not to ask Temenos or some other vendor who offers T24 support services.
22. Is your I. T. staff really capable of getting involved with a T24 project? They will need much
training in advance on T24. Then they will need to be able to support T24 in the future. Evaluate
this aspect of your support capabilities before buying T24.
23. Are you a bank with good enough project experience (other or previous projects) that has
given your staff some ability to run a project independently? Many banks say they have such
staff, but in reality they only have staff who can do the basics of project management. How
aggressive is your project management staff? And then how many projects have they
implemented successfully and on-time and on budget? This is important. Project management
is just as much of an issue with having a good T24 implementation as the design, configuration,
and testing.
24. The components you will need in addition to project management are documentation,
training, and audit. Do you have such capabilities to add to the project management team?
Temenos does not do any of these tasks by the way. You will need them for a successful T24
implementation. Then you will need a team to come in and do a final evaluation and
certification after your project is finished and you are ready to “go live. ” Again, a final
evaluation and certification team should be from a non-Temenos, 3rd party who is experienced
in T24 builds and quality analysis.
Products “are products,” but are they what you really want in T24?
25. There are product innovations in banking almost every day, certainly if not that then every
year. What are your products? What are their work flows? What are the local customs and
practices that may be different from the way these products work in other parts of the world? If
you have what you consider to be non-standard products or products that are complicated in
work flow, then you need to have these products listed in your RFP along with their
complexities. Some products span modules in T24. This is a difficult if not impossible work flow
to automate (although Temenos has a tool called PW or Process Workflow that can handle such
complicated cross-module workflows and workflows that need to be tightly controlled and
standardized). Trade finance settlements converting automatically into loans is one good
example of what T24 CANNOT do. Know these things before you get involved with purchasing
T24.
26. Are you planning to add fields to the T24 standard database? Get the T24 data dictionary
and evaluate it thoroughly for each product before you buy T24.
27. Are you planning to do specific processes that will involve a CRM system? T24 does not
always work well with CRM (although T24 now comes with an integrated CRM of its own).
Investigate your CRM needs before you buy.
28. Are you planning to do Islamic banking products? T24 can do some but not all. And while
Temenos claim to have a T24 “Islamic” banking system, none of their Islamic banking customers
are happy with what they have received so far in this area. Islamic banking is not fully discussed
in this document however. If you require more information in this respect, then a separate list of
questions must be provided to Temenos. T24 generally speaking is NOT a “true” Islamic banking
system. It has been customized in a few locations around the world to do such products, but
Islamic products are not standard anywhere. There is an Islamic accounting standard available,
but it depends on the country you are in to determine if this standard is acceptable to you.
Islamic banking is complicated, and it would be highly advisable that you “dig deeper” into what
T24 can do in this respect with someone who is highly knowledge of Islamic banking and who
also knows T24.
29. Are you planning to do exotic type products such as “structured deposits”? T24 will not do
these. Again, the same is true for Islamic banking (where structuring is commonplace). T24 will
do some Islamic products, but it is NOT truly an Islamic banking system despite what Temenos
may tell you. The main reason for this is that you cannot have a General Ledger in T24 that is
purely Islamic if you have non-Islamic banking products too. You would need two separate
General Ledgers in that case which T24 does not have and cannot do.
30. Are you planning to do complex FX products? T24 is not the system for you.
31. Are you planning to do complex structured trade finance? T24 is limited there too.
32. Have you considered your form (advice) and statement needs? T24 does not have a strong
word processing or form generation capability. More on this in a separate set of questions if
needed. Not included here except this one comment about forms and statements.
33. Do you require data warehousing? T24 is NOT a data warehouse.
34. Do you require complex MIS reporting, funds transfer pricing, service transfer pricing,
profitability reporting, budget management, purchasing order management, etc. ? T24 is not
capable of any of these in and of itself. Outside systems to do that would be required.
35. Do you require a system that can be expanded easily in the future to accommodate new or
innovative products? T24 is fairly flexible here, but if you are thinking about products that are
going to be linked to market pricing (mark-to-market), various conditions present any financial
market that will affect product returns (profit/interest/rates of return), products that may be
subject to other terms/conditions, then you need to take a closer look at the respective
modules(s) in T24 that will process such products. If you require expansion simply by adding
another T24 product module, this is fairly straight-forward and simple however. But many T24
customers find later on that such product modules do not fit their core design so easily. The
point is that the best T24 implementation is one that is done all “at once” where the core
parameters are designed in one instance to accommodate a full spectrum of product codes
across all modules. More on this question if you want, but a separate discussion from this
general “99 questions” list as presented to you here would be required to go into this subject in
greater depth.
36. Are you doing off-shore products where you are likely to involve various product restrictions
from one country or jurisdiction to another? A good example is off-shore deposits that are not
to be linked to a customer’s on-shore accounts directly. Sometimes banks in the US deal with
USD accounts say for Brazilian customers where that money cannot be shown as being
deposited in the US itself. The place of deposit is a branch in the Cayman Islands. But the point
is that these funds have to be linked in T24 in such a way that shows them as sub-accounts (off-
shore) of a main account (US on-shore). T24 does not do true sub-accounts (in the General
Ledger that is) either (compare T24 to the Flexcube banking system which can). There are also
complexities in managing on- and off-shore accounts especially when dealing with tax
jurisdictions, domicile, and residency. T24 is capable of some product linking where there are
accounts that are not necessarily in one country but in another for tax purposes. This requires
further investigation if you plan to use T24 for on- and off-shore banking
transactions/branches/outlets.
37. Are you doing multi-bank or multi-company configurations? T24 can support this, but you
need to do a separate investigation into this area if you are involved in such operations.
38. Are your products set up in such a way that you require a complex limit structure to be set
up in T24? More on this one is required in a separate discussion if your answer is YES.
39. Are you a bank in a country such as Holland, Belgium, Luxembourg, etc. where reporting
requirements are complex (on products and/or risk & exposure)? A separate set of questions is
also required here if the answer is YES.
40. Are you a bank where you are offering a range of competitive loans and deposits that are
subject to strict regulatory reporting and compliance? Some countries (such as Scotland) have
government-backed loans, mortgages, etc. that require an extra level and detailed degree of
reporting and tracking/management. Also, some countries have govt-backed loans and other
funds offered via various channels that require special processing. If your bank is involved in
extensive govt-backed funding for any loan products, then a separate assessment of T24
suitability for you is needed.
Configuration of the T24 system and what you should ask. . .
41. The configuration of T24? What is that? It’s in a plain and simple word DESIGN. And if you
do not know what design of a banking system means, then you need to find out!! You ask
Temenos what it is. . . then you ask these questions next. . .
42. What do I need to do first to get a design for T24 in place? (The answer is not use the
“model bank” in T24.)
43. What do I need to do next to get a design for T24 validated? Note: T24 has a limit of
approximately 50,000 codes for products (category codes) that run in so called ranges. You need
to have your full accounting and product list evaluated to see if T24 can accommodate your
bank’s product and accounting size.
44. Ask to see the Categories component of T24. This is a question. Then ask if it meets your
needs. The point is that many banks find that T24 is not “big enough” in the number of products
available for them. Also note that generally speaking T24 product modules are limited to about
200 fields, no more! Temenos will say they can expand this, but the way they do it is by making
extendable fields in jBase. This overloads the system if you get too many of them and slows
down processing and COB times.
45. Ask to see a limits module set up—specifically ask to see a full global limits module set up
for revolving and non-revolving limits. If you don’t understand what this is, then a separate set
of questions in addition to the ones here is required.
46. Ask to see what the account driven functions are in T24 opposed to the transaction driven
ones. Note that T24 is a transaction driven system in design; not an account action or based
driven system. More discussion is necessary for a fuller explanation of this question if you have
issues with this sort of design in T24.
47. Ask to see what a G/L (General Ledger) looks like in T24. G/L is complicated to set up in T24.
It takes extreme knowledge of every core component and value in T24 to do so well. If you want
more on G/L set up in T24, then there is another set of questions besides the ones here that
you need to ask (you must make that list in advance about your General Ledger needs and
present it to Temenos).
48. Ask to see what CIF (customer info file) in T24 contains. This module also may or may not
meet your bank’s requirements.
49. Ask to see what is required to set up a full set of MIS reports in T24 using their MIS module.
They have one. It’s not suitable for everyone, but look at it anyway.
50. Ask to see what the impact is if you run out of Category codes. This is a “hidden” problem in
T24 that few lay (non-technical) people understand. (The answer is you can’t add any new
products in the future if you run out of Category codes [for products]).
Questions that most people FAIL to ask (and why T24 projects typically fail or why T24 is under-
or over-evaluated against its competitors). . .
51. How many T24 implementations were decommissioned in the last year? Why?
52. What is T24’s ranking as a “top selling” banking system in 2008? 2009? 2010? 2011? 2012,
2013, 2014, 2015, 2016, 2017, etc. ? Who’s 2nd and 3rd? Who’s #1 in 2015/2016/2017?
53. How many T24 projects were launched in the last year where the bank canceled the T24
contract with Temenos before project completion?
54. Why do T24 projects typically fail? Ask Temenos how many banks now signed up are not yet
“live” with T24. Then ask what “happened” to cause that failure to go live. (Tip: The “answer”
will always be that the client didn’t supply the necessary product and configuration/business
requirements. This may or may not be true. Dig deeper if you get this answer or any other
answer that sounds suspicious.)
55. What will you do if you find out later (for whatever reasons) that T24 is not the system you
need (after you’ve signed the contract with Temenos)?
56. What will you do if you engage Temenos and buy T24 and then realize that you must back
out of the project? What is your fallback strategy?
57. If you sign a contract with Temenos (or any other T24 consulting firm) to do a full “turn-key”
implementation, what are you really getting? Put this question to them directly!! Get clear
answers!
58. If you are a “new” bank to the banking system market, then are you willing to consult with
people and banks with “prior” experience using Temenos and T24 to arrive at your own decision
to purchase T24?
59. What led you to consider T24 in the first place? Be honest. This question is important to
answer for you to complete this questionnaire honestly!!
60. Who told you that T24 was the #1 banking system in the world??? It has been, may be now,
but may not be in the future—note this question and get as much information as you can.
Technology. . .is it here to stay, here to change, or hearsay. . .
61. T24 loves a Sun Solaris system, RISC machine, AIX, etc. But here’s the “’rub”—T24 server
platforms get hammered and hammered fast. Most banks during the 1st year of T24 use find
that they are undersized for the vast amount of data that T24 “puts out. ” OK, here’s the
question: WHAT IS YOUR budget for hardware? A typical T24 installation requires a lot of
hardware. QUESTION: Ask Temenos for the architecture document for your bank’s sizing and
product/data needs. You may be surprised at the cost of the hardware you need to purchase to
install T24 for your size and needs!!
62. T24 is basically an old UNIX based design. While UNIX is not “stone-age” yet, it’s got quirks
and peculiarities about it. If you are going to get involved in customization of T24, then you’ll
need to know that their database which is jBase is an old PICK database (binary) that is very
difficult to work with—especially with reporting. This document does not cover jBase however.
But to give you the simple description jBase is Temenos’ proprietary database that T24 uses that
is (a) NOT relational (that is, there are no ERDs in it; jBase is a hierarchical or extendable
database in design) and (b) jBase is called an extendable or hierarchical database because of the
way it is designed which is via internal “hard coding,” or source code level programming, that
you cannot see and cannot control or change yourself (although you may hear Temenos tell you
incorrectly that it is a relational database which is true only if it is interfaced to Oracle, DB2, or
SQL or some outside database that is truly a relational DB, which gets into a very complicated
T24 database design and set up at that point (and slows the system down considerably)—more
on this subject is available if requested). This design also causes problems if you want to build a
data warehouse. More questions on this subject are available (not in this document, but on
request) if you want more details. Locate and contact a jBase/T24 consultant if you want to dig
deeper here.
63. Who is skilled in jBase in your bank? There are two configuration levels in T24. One is in the
parameterization tables. The other is in jBase if required. Working directly on jBase coding
yourself can be very “tricky” too. You can wreck the T24 system if you don’t know what you are
doing.
64. Do you plan to have a data warehouse in Oracle, Sybase, DB2, SQL, Terradata, etc? Then you
need to seriously consider that T24 does not have DB (database) ERDs, schemas or instances for
such DB’s. More questions on this will be supplied if you require.
65. Do you plan to support “thin client” technology if you deploy a browser-based T24 system?
T24 does not fully support thin client in the way that Finacle or Flexcube do. The browser
technology that T24 uses is based on a “wrapper” around the basic T24 design that simply
makes it “visible” on the Internet. It’s not truly Java based as more up-to-date systems (such as
Finacle or Flexcube) are (note that since R13 T24 claims to be Java based; see the Notes section
at the end of this document for more information on that subject); nor does T24 allow the
speed and reliability over the Internet that more recently designed browser-based banking
systems do. A separate set of questions are available here if you want to explore this area
further as related to T24.
66. Do you plan to deploy Finantix or Siebel or MS Dynamics CRM or some other CRM system in
conjunction with T24 (or take Temenos’ own integrated T24 CRM system)? It’s a questionable
area regarding performance when T24 is interfaced to any CRM system. Seek additional advice
and see where a successful CRM with T24 has been implemented and how it was designed and
“done. ”
67. Do you plan to interface T24 to any other systems? This requires major development of APIs
to T24. T24 is likewise a system that does not “like” outside data sources via so called “interface
programs,” which slow down T24 performance considerably. A large number of interfaces to
T24 will result in delayed COB processing too if you are not careful. Also examine this aspect of
the T24 product if you are considering purchasing T24.
68. It is always a major problem with T24 when a number of interfaces to reprocess data or to
do extended program routines are involved. For example, take Islamic banking. You calculate
profit, loss, or “break even. ” These are always programs written around the core of T24. And
the result is that they work if programmed correctly, but they do not always help with system
processing (especially COB) speed. T24 has a core program (source code) that you cannot
change (in Unix and jBase). You can add programs to the Standard Selection module of T24, but
that’s all. And the more you add for customized processing, the slower T24 gets. Ask yourself,
then, how much customization do you plan to do? What sort of customization? How much
customization? And for which products? Then get some non-Temenos advice about the risks of
doing so and how to proceed safely and reliably.
69. If there is one thing that makes the T24 system work right it’s consistency!! Ask yourself how
many “project design and testing phases” you plan to have. Again, core T24 needs to be built
with the future in mind if you plan to build T24 in phases for your bank (that means tight quality
control and consistency in the design so you do not deviate from what the Core can handle—
and if it can handle additional products/modules to be added in the future).
70. Last but not least, a comment or two on technology to close out here-- If you are a relatively
“new” bank (less than 3 years in business) are you a “mature” enough company to deal with
Temenos which has been savvy in the IT banking world since 1993??? If you are not a “player” in
this world, then the advice here is not to “go it alone. ” Temenos is not successful for nothing!!
They get clients (and lose them) because they are smart!! Are you smart? Ask yourself this
question?? Be honest?
Last twenty-nine questions. . . short and to the point. . .
71. These are short and simple from here to #99—have you ever dealt with Temenos before? If
not read on. . .
72. Do you know what their reputation is?
73. Do you know what their typical installation results in (usually not 100% successful)?
74. Do you know if you’re getting “VALUE” for your money spent (with Temenos and with T24)?
75. Do you know that T24 banking analysts and consultants are not always as good as they say
they are?
76. Do you know that the money you can spend on a T24 project (or any banking system for
that) can be money wasted if you don’t manage the project well?
77. Do you know that no real, world-wide standards exist in banking systems and their
design/performance (a totally unregulated area of banking and software)?
78. Do you know that you will face operational risk if not closure if your banking system fails?
79. Do you know that over the last twenty plus years Temenos has been sued in court in various
EU countries over and over for botched implementations?
80. Do you know that recourse on a bad implementation with Temenos does not exist after you
sign the business requirements documents and submit them to Temenos???
81. Do you know that you are the final and sole determiner of your “bank’s destiny” if you buy
T24/implement the same?
82. Do you know that most “recognized” (as stable) banking software and technology is on
average 20+ years old—or more?
83. Do you know that when you sign an agreement with a banking system software vendor that
getting out of it contractually takes a minimum of 1 year to decommission the system not to
mention high penalty costs for voiding the contract?
84. Do you know that Temenos gives a “maintenance password” that they control whereby if
you DO NOT pay your yearly maintenance agreement fees they can automatically shut down
your entire bank (by disabling T24 via a “time bomb” embedded in it?)
85. Do you know that T24 is the most decommissioned banking system in the world today?
86. Do you know that the owners of Temenos are originally accountants not bankers?
87. Do you know that if you become a client of Temenos that you are subject to 3 year upgrade
agreements to continue T24 support on your version of T24??? OR, be de-supported! A big one
to remember here.
88. Do you know that if you do not upgrade T24 every (roughly) three years that you will be
charged additional maintenance fees should you continue to use the system (or be de-
supported all together if you do not pay these additional fees)?
89. Do you know that Temenos is not going to support you on major in-house customizations if
you do not fully document the technical design of those changes and submit them to their IT
support center in Chennai, India? This can be very time consuming and expensive to do, to
document your entire set of T24 customizations.
90. Do you know that Temenos has been the target of forcible buy-out and takeover actions by
several competing banking software firms over the last few years (since 2010). Misys was the
last to try this back around 2012 or thereabouts, but the UK govt blocked the merger of these
two companies—however rumor has been for years that T24 is for sale to the “right buyer”
(whatever that means)?
91. Do you know that T24 is likely to be “rationalized” as a banking system should some
competitor buy it out? Do you know what “rationalized” means? Check on the Internet for that
definition. It means “free” for the most part—becomes shareware or “open” software for
anyone to use and to develop/re-develop/customize.
92. Do you know that T24 is at least 30 year old programming technology (dressed up to look
modern)? It originally came out of Citibank in London about 1983. It was originally designed as
a wealth management system.
93. Do you know that the employee turnover rate per year at Temenos is over 50% (if not
more!)?
94. Do you know that most Temenos staff at the management level do NOT know how to work
on or configure T24?
95. Do you know that most Temenos configuration and source code maintenance staff are in
India where the quality control of each Temenos release is somewhere around “zero”?
96. Do you know that T24 was completely botched on the R5 release (2005) so that they could
get it to “market”? (A lot of that has been cleaned up since then, but R10 was also another
botched release—and releases R11 through R15 have had issues with performance—stable and
reliable new releases in Temenos T24 are not the norm).
97. Do you know that as a client/customer of Temenos/T24 you are subject to support that will
be “questioned” if you cannot prove T24 source code errors?
98. Do you know that as a Swiss corporation EU laws (or US or elsewhere) do not always apply
should you have a contractual dispute with Temenos? They are now incorporated in the Dutch
Antilles as Temenos Holding Co. You’d better check your legal rights there too.
99. Last but not least, be realistic. Ask yourself this one, last question--- Who are Temenos? Are
they a company that I want my bank to do business with? Put their track record to the test!! Ask
yourself this final one question—WHERE WILL I BE IF TEMENOS IS GONE??? That’s the one I’d
ask. I’ve worked off and on for them before. Since 1997. I know the nature of how they are!
Contracts and prices
100. What does the vendor really provide you with when you get into the “details” of the
contract? Does it look like fairly standard, straight-forward contract language or is there a “devil
in the details” you don’t see at first?
Beware of “Penalties” clauses for one—here’s an example:
Source code escrow

101. Ask how this is managed. There must be a source code escrow arrangement and
agreement in place with the exact specifications of when and how access to this code would
take place. Typically access comes when the company that owns the codes goes out of business
or when there is a catastrophic event that renders the company incapable of doing business.
Maintenance of system and software
102. How much does it cost per year!!!??? This is the big question to ask! And what do you get
for that money? Note that the “real profit” on banking software comes from the maintenance
fee each year. And if you are getting very little from that cost other than “vague promises” of
doing “this and that” “if this and that happens” then you had better be 100% clear about what
you are paying for in this maintenance fee:
103. What does the vendor do in this respect?

104. Do you receive software upgrades free of charge?
105. How often do they offer such upgrades?
106. Does the vendor offer new functionality in the software when it is developed without
charge to existing customers?
107. Is the maintenance contract clear and specific about what the definition of “maintenance”
is and where the client is responsible for certain maintenance and the vendor is not? Here’s an
example of what Temenos gives in respect to T24 maintenance:
This means in short that if you “change” or “tamper with” the T24 system you are not going to
receive free maintenance service if something goes wrong. Also if the client terminates the
agreement with Temenos then the maintenance fees are still due “until the end of the period”
(or year typically). This is not something that people truly understand until Temenos claims that
the client has altered something in the T24 system against the original specifications of the
software agreement and license. Note however that many clients alter T24 on their own accord
and outside of the software agreement and do so at the risk of having their entire contract and
license with Temenos terminated. Be careful and make sure you fully understand where the
metes and bounds of maintenance in the T24 world are.
Defects in software
108. The question to ask in this respect is what is a “defect” - note that T24 is full of defects
many of which are not known and not removed before the yearly release or upgrade comes out.
These are known by numbers such as R17, R18, and so forth. Many times there are major
changes to the fundamental design of the T24 product from year to year that require that to use
that particular release you must invest in considerable changes to your existing hardware and
software infrastructure at high cost and at major risk. Be sure that you have the term “defect”
clearly understood and how that defect if you discover it will be corrected by the vendor,
Temenos.
Note again the language they at Temenos use about warranties where you WILL NOT always see
the word “Defect”--
Defects in any T24 release are typically not publicized if Temenos can prevent it. Also, defects
while they may be subtle or minor in appearance at first may indicate deeper issues within the
overall software design. Such defects usually are not identified early on due to no testing or
weak testing of the software by the vendor prior to release. Also, the vendor often releases
software from year to year that may or may not be compatible with certain older technology. Be
sure you understand all such compatibility concerns that you may have in order to have it
written into the software agreement regarding what a T24 software defect is and how it will be
corrected.
Help desk
109. The first question you ask the vendor about help desk support is where is it? That means is
it a live person on the phone, an internet site, or something where you put in a request and wait
for a response. Help desk support with most banking software vendors is reasonably good, but
you have to be careful about what you tell them about your problem or question. Everything
you say is logged, and as they say in the police vernacular “can be used against you.” Make sure
that you get a clear understanding of what help desk support the vendor offers and just how
they “class” your information (level 1, 2, 3, etc). A help desk is great but it’s not the only way to
solve a problem. The best way is to have staff well trained enough to solve it themselves and if
they cannot then you go to the vendor. Specific help desk support questions you should ask are:
110. How many years of experience does your typical help desk employee have?
111. How many escalations does a typical help desk question require before it is resolved?
112. How many help desk questions are never resolved?
113. How many times has the help desk given a client the WRONG answer?
You may not get your answers to these questions 100% but it is best to ask them. And be careful
to write down the answers you receive. Note that all meetings about anything you do with the
vendor whether engaged or not should be carefully “minuted” and those minutes saved in a
file. That information may be very useful if “things change” in the future. Read the help desk
terms from a contract yourself:
Pricing
114. Here’s the real question. Pricing in the banking software world is never the same and is
never presented in an honest fashion. That may sound strange at first, but NO software,
especially banking software, is priced the same way to every prospective client. The vendor sells
“based on what the market will bear,” which is not good for you as a customer. This is how
Temenos priced one project where in the end the bank never really got exactly what it needed.
The implementation took years, and it was not successful in the end, not 100% at least and had
much post-live support to correct issues. Here’s what it cost them initially. How much more they
paid later is unknown:
And for that sum of money they received the following modules in T24--
I can say that there were several REQUIRED modules (such as DR and BILLS for Letters of Credit)
that were not part of this licensing scheme. They missed those. Why? No one knew what was
required. And the consulting firm managing the project didn’t know either. This is a perfect
example of where proper due diligence by the bank would have prevented the vendor and its
implementation partner from “taking advantage” of the bank. Modules required that are not
implemented at the beginning of a project are more difficult and way more expensive to add on
to the system later. I can bear eyewitness to that fact.
POINT- Do your due diligence, and if you don’t know how then get someone competent enough
with T24 who can.
Recission
115. This is where you can really get into trouble later if things go wrong. What are the terms of
recission in a Temenos software and implementation contract? Well here they are:
Now here is where the term “defects” appears, and the definition of a defect is as follows (per
Temenos):
Determining a true “defect” that would qualify for the bank to end its agreement and contract
with Temenos is nearly impossible to do. Also, the vendor would never admit to such a defect in
its software, and in order to cover up some defect will have SIX (6) ATTEMPTS to remedy the so
called “defect.” Beware of this tactic. Many customers who have purchased T24 have been left
in the position of having no legal recourse of action to recover their losses (financial and
otherwise) from Temenos in court as a result of defective software. Also, note that finding a
venue to file a legal claim against Temenos is just as questionable and difficult to do because
while posing as a Swiss company they are not fully Swiss. They are incorporated in the Dutch
Antilles. Figure that one out. And ask them WHY they are so incorporated and to what
advantage that is to them and not to you, the customer.
Warranty
116. The line to read here carefully and slowly is - “CLIENT operating on a Main Release of the
Software System older than two (2) prior Main Releases or any modification to the Software
System performed by xxx or xxx without Temenos’ written consent. . .”
So they do not warranty their product unless you are within the last two releases - and those
come every year. So you buy T24 and then you’re required to upgrade every three or four years.
That’s what causes trouble for many because if you do not do that you are out of warranty - and
then you are basically out of support. Ask specific questions about this matter and be clear on
what exactly you have to buy to remain within warranty. This is basically a way to simply force
you to pay more money from time to time to upgrade which is in most cases not necessary to
do. A software system once live and stabilized is put at risk to upgrade it so frequently. And
despite what the vendor may say you are not going to close the bank if the system is not
upgraded. Often banks use software systems for up to ten (10) years without any major
upgrades and get by just fine with the patches that come from time to time. Temenos makes a
lot of clients upgrade unknowing of what they really gain from it other than having continued
maintenance and warranty support which in most cases is never required and if it is can usually
be remedied in house by fixes applied there without the need of vendor support.
Property Rights
117. The question to ask here is who owns the T24 system if you make customizations to the
extent that the system is really “no longer T24?” Temenos has had this fight with numerous
clients in the past, the most famous case being the Dunfermline Building Society in Scotland in
2007. That project and bank collapsed by the way in early 2009. Over $65,000,000 USD was
spent on customizing T24 for a building society there all to be essentially never used. DBS
collapsed in the 2009 financial upheaval that ended a lot of banks and trading firms. But the
argument was that DBS had so customized T24 for their own needs that it wasn’t T24 rather it
was DBS’s system for bespoke operations related to all building society products and operations
in the UK. The intent was to resell the product DBS had developed to other building societies in
the UK. Basically in the end Temenos pulled out of that project because of property rights
disputes with DBS. Don’t get yourself into the same situation. Temenos does not sell the source
code to T24 anymore. Once some twenty years ago they did occasionally, but now even the old
compiler has been removed from the product. You cannot compile code in T24 yourself without
it. The area of property rights with T24 is somewhat murky. You can read for yourself from a T24
contract--
Fees and expenses

118. Here the question is what happens if you DO NOT PAY ON TIME? Read this section in a
contract regarding payment--
What they do NOT tell you is that inside of the T24 system there is a “time bomb” that will “go
off” and disable the system if payment (the yearly maintenance payment) is not made by a
certain due date. You will begin to receive system warning messages about payment being due
after a certain time when the license is near expiration. After the expiration date the license
automatically terminates and disables the system. Be sure that you are clear about this aspect
of T24 system control by the vendor and what happens when the “time bomb” triggers and T24
is no longer operational in your bank. This has happened before!!
Mode of payment and where
119. Ask how the payments are expected, when expected, and paid where. The issue with the
payment is usually the VAT that may be demanded by some country where the payment is
either made or collected. Investigate that closely? Temenos will not permit any tax deductions
from payments or surcharges to be added by a local government either. This matter is often
encountered in African and Asian countries. Also it’s an issue in the UK itself where a client bank
may be located. VAT is always an issue with payments to Temenos.
Payment terms
120. These are always spelled out in the service contract and license but ask about them in
detail and be sure you understand the methods they use in structuring payments and when
they are due (and what happens if they are late).
Overdue payments - what happens?
121. Ask the big question here. And that is what if there are disputed payments due? Typically
disputes arise over unfinished work that has been contracted, failure to perform on the part of
vendor staff or sub-contractors, payments claimed that are not substantiated by time sheets
(which you MUST keep and keep them up to date every day!), payments that have been claimed
due to penalties imposed (this is another area of dispute usually), and payments that are
suddenly increased without clear explanation (per diem, travel, lodging, project due date
overrun, etc.)
Taxes and Charges
122. What are the taxes and VAT charges in your country? In the vendor’s country? In the
country of any sub-contractors? This is important to know because high VAT claims and income
tax deductions can become a nightmare to manage with non-local staff.
Liability
123. This one is as below - but beware of language such as: “any modifications to the Software
System not made by Temenos, or any failure by xxx to implement xxx will VOID obligations. . .”
Again Temenos is consistently concerned with the client making changes to the T24 system. This
is for a reason. Clients do it all of the time when they gain access to rogue T24 source code or
when consultants have unauthorized access to the T24 source code. While there is allegedly no
such source code outside of Temenos’ control that is not true. The source code to T24 was
“hijacked” years ago and has been available via “underground connections” for years. Having
the source code to T24 gives you immense power over the product if you know the program
and how to work it and manipulate it. And there have been many instances where rogue
programmers (“hackers”) have modified T24 actually to work better or in a manner that is more
suitable to the client’s country practices. But again the aspect of anything related to T24 is
“don’t get caught” modifying it. Then all liability ceases. Again you are left without any legal
recourse should problems arise.
Death or Injury
124. This topic is essentially under liability but here are the usual terms in the event of death or
injury--
Make sure this is clear to all parties however, and ask what is the procedure for repatriating the
deceased if there is such a need that arises while the project is underway. It is rare for this to
happen, but there have been instances where staff and contractors from outside of the local
jurisdiction (i.e. foreign staff) have been robbed and assaulted while on a project. This
happened in Slovakia once. Also, there have been attempts on staff to steal laptops, jewelry,
cash, and other items in the hotels where they stay. Cover the way these events are to be
handled in your due diligence questions. Death is rare. But be sure how a death will be dealt
with should you have to take charge of the person’s remains and repatriate them or do
whatever must be done according to local law or the family’s wishes.
Solicitation of employees to leave the vendor
125. This can cause major trouble. Ask the vendor what the terms are here–this is an example
from a Temenos contract about this question--
Governing Law
126. Ask what the jurisdiction is for legal remedy should it become necessary. Oftentimes
foreign vendors may be sued only as stipulated in the contract for the legal jurisdiction that is
stated there. Question this if you are not sure what is involved with say a court in some location
you are not in or where there would be an arbitration entity that would be involved at first. The
losses you may suffer if you do not specify this matter regarding governing law can be grounds
for your lawsuit being dismissed. Contract law has some odd aspects sometimes, and the
software companies certainly have lawyers who have carefully worked out the manner in which
a legal dispute would most likely go so that the outcome would be in their favor. Here is one
example--
Jurisdiction
127. Similar to governing law but make sure you specify where the court is that would preside
over the case.
Amendments
128. Straightforward, but question how amendments to contracts and agreements are made.
129. Who has the authority to approve them?
130. Must they be mutually consented to? Don’t think that it’s unilateral with amendments or
that the client can simply do so without the vendor’s approval. Oftentimes amendments lead to
massive cost increases and extensions of the project schedule. Sometimes the amendments can
negate work already done. Make sure you get your scope of work (SOW) finalized to everyone’s
written approval before you enter into a contract with the vendor. Not doing so is the best way
to have a failed project later on.
Severability
131. Clarify this in no uncertain terms. A dispute could lead to a challenge to the validity of the
entire contract, not just specific parts of it. A classic example of this would be a project in a
location where a war breaks out. Then what? Are you still expected to pay or does force
majeure take over? I’ve seen projects where the country involved (such as Libya in 2010 and
2011) completely fell into chaos and collapsed economically, militarily, and politically. And then
nothing could be done to complete the contract with the bank there. In fact there was no bank
there. It was a “greenfield bank” and didn’t have anything but a charter. So the government
ceased to exist and the project never received any funding to pay the vendor. The vendor
received nothing. And whether severability or force majeure applied it didn’t matter. If you think
that you are doing a project in a location with a high “war risk” make sure that you have a
contingency plan in place to move the project elsewhere or specify what severability entails
regarding certain aspects of a contract suddenly becoming “illegal” (in Libyan in 2010 Kaddafi
tried to levy a “terrorist tax” on the project which he did to supply his outlaw friends with cash--
this was disputed 100% and the bank was forced to collect this tax or not do business--while
this is an extreme example this is the sort of thing that while “severable” in some jurisdictions
was not severable in Libya since it was the law there--eventually the whole contract was
canceled - force majeure being the reason).
Non Assignment
132. Typically this is not permitted unless there is a sale or transfer of the bank during the time
of the project. If there is some concern that the bank is in some negotiation with another entity
to take over ownership then the matter should be discussed and mentioned in the contract so
that a smooth transition of the T24 system and project will take place. This is a concern
primarily in the United States where a bank may be forced by the government to sell due to
insolvency.
Counterparts
133. This is standard - no real questions here other than what is the vendor’s definition of
“counterparts.” Clarify that in writing.
Confidentiality
134. Nothing special to question about this other than how long is the confidential agreement
in effect? - in years or months or other conditions of expiration?
Definition of Terms and References

135. Standard in the preface of all contracts - make sure you have this spelled out clearly and
question any terms that seem “new” or “odd” to you. Language can be a two-edged sword in a
contract. Protect yourself accordingly.
Example--
More definitions - beware of some of these from a legal point of view and question the vendor
before agreeing to ANY of these definitions if you are not sure what they mean or if they seem
to be “one sided” and not necessarily in the best interest of protecting your rights--especially
regarding DEFECTS or PROJECT COMPLETION definitions:
Vendor Deliverables
136. Here’s where the real fun begins, and I’m going to dwell on this subject for the next few
pages just to make sure I haven’t left anything out--
A deliverable has any number of meanings--can be code, parameters configuration, hardware
setup, peripheral software configuration, documents, training, support, etc. It’s infinite.
A deliverable to be accepted by the client must be DEFINED clearly by the client to the vendor,
namely Temenos in the case of the T24 system. No clear definition of what a deliverable is can
lead to gaps in design and development that you will have to fix yourself at your own expense
later.
OK, listen to me now - carefully - I’m going to tell you how to get “wool from an egg” on
deliverables as the Russians say:
137. Have you done your business requirements and developed a document that describes
everything you do in the bank? - and that is not to the lowest level necessarily, but nevertheless
gives a high-level view of your products, work flows, current systems, accounting, credit and
limits, risk management, documents and forms, interfaces, reports, and training. This is not a
complete list by any means but it is a place to start. And surprisingly enough many banks do not
have such documents, or they do not have SOPs or Standard Operating Procedures which they
should keep up to date for regulatory and audit purposes. Don’t even think about negotiating
with a banking system and software vendor without such information. If you do you are at their
mercy for them essentially to have an excuse to do more or less NOTHING on the project but
what they want to do. They will give you a pre-configured system and simply walk away from
what you really need them to build to do your work as you do it now and hopefully will do it
better in the future with a new system.
138. The best question to ask the vendor about deliverables is to what extent are they willing to
change the configuration of their system to meet your needs? They will tell you that they will
configure the system based on a set of business “specifications” requirements that you give
them that are derived from workshops they will conduct with your staff. But here’s the catch.
Most staff don’t know how to write or to create business requirements in a meaningful manner
that are of real use to a software vendor. They will simply say “I want this and I want that” and
the vendor will simply make some notes, produce some documents, and say “here they are,
now sign off on them.”
That’s not an efficient nor effective way to do this sort of work. The best way is that you hire
someone who knows how to gather this information and write it so that the vendor does not
“shortcut” on this crucial aspect of your system design and configuration.
139. The best business requirements are gathered by speaking to and documenting the
different areas of business operations that have historically been engaged in the use of
automated systems. They typically understand how on line and off line operations and work
flows interact, and the people in these areas frequently can point out quickly where an
automated system cannot do the work at all or can only do it partially. This is more important to
gathering business requirements at first because it gives you the whole picture of the
automated systems rather quickly and identifies immediate areas of weakness or no capability
at all. Work that is done 100% off line may not be automated for a reason. You need to
investigate that and then compare that work to the work done on line either totally or partially
and identify the “gap” between to the two work flows and why it exists. The question to ask
here is whether you have such information already documented in the form of SOPs and
training manuals or whether this knowledge resides only with certain people in certain areas
who have this information “in their head.” If that is the case then you need to reassess how
your organization retains “corporate knowledge” and engage someone to begin a thorough
documentation of your entire company. When a new system is being considered and decided
upon is the perfect time to do this. Also, it will give you better control over the vendor and the
system implementation so that you can readily explain and SHOW to the vendor how you want
the new system configured and designed. Also, such documents can be attached to the software
and work specifications in the contract as a basis of making up a scope of work (SOW). Do you
also know that such documents when attached to a contract for software and software services
“nail down” the gaps that may come along that need further clarification or that can be clarified
in ADVANCE which is the ideal scenario?
140. Do you know that the requirements part of your project will be the basis for your test
scripts that will be used later to validate the “build” of the T24 system to certify it as fully
compliant with your requirements and specifications and to demonstrate that the system is
capable of going live and into full production? Without these requirements you are not going to
be able to demonstrate that the system works properly nor will you be able to have a basis by
which to raise any issues regarding defects or misconfigurations of parameters if they arise.
With the test scripts which are based on the business requirements you essentially have an
“insurance policy” against anything that goes wrong with the system either in test or production
later, and you can give solid evidence based on the test/requirement information against any
problems that show up on the system. If you have a system that is operating with some “bugs”
or some “mistakes” you can identify them quickly if the requirements and test scripts are
thorough enough in what the expected results should be or should have been. A troubleshooter
can then get on the system and investigate more accurately without having to “guess” so much
what is causing the problem whatever it is.
Test scripts are typically worked out based on business rules and scenarios where when the test
script is input it will follow a certain number of steps and pass a certain number of “milestones
or phases” that will show step by step what the system is doing. All of the information the
system returns is documented and attached to the test script and then is validated and verified
by someone on the business team. The test scripts should NEVER be validated or verified by
anyone on the test team because fraud and manipulation of the data can take place.
Thus, MAKE SURE that the test team is not able to access anything either before or after the test
script is input and that they have no access to anything in the system itself whether data, code,
or parameters. Many times testing on systems, especially T24, has been FAKED by the vendor or
the business user to speed up the roll out process and to make sure that they are not held
accountable for anything that has not be set up correctly in the system. TESTING FRAUD is
widespread. Ask that question of the vendor or the testing sub-contractor about how they are
going to prevent any fraud in testing from taking place!
Testing certification, WHICH is the following that you must do and must ask the vendor
regarding--
141. Who will make the final determination that the system (T24 in this case) is ready to go into
production?
142. What is the level of testing success (that is the number of Level 1 defects, level 2, 3 etc).
Note that in the test plan the number of Level 1 defects that are permissible before going live or
into production or that are NOT allowed must be set in clear numbers. Some banks sometimes
are so eager to “go live” that they will accept a system as “ready” at a 60% level 2 or bug level
“pass rate.” Level 1 should never be accepted—ever! This is ridiculous and completely
unacceptable to the business users. You will be “bug fixing” on a live system for years if this is
how low a “bar” you set on bugs or software defects. A system is only fully ready for production
use when the rate is more like 5-10% defective (at level 2 or 3) and these are defects that are
not necessarily going to affect accounting, business operations, reliability of the system or the
level of support that is going to be required (defects of a nature that relates to lack of reports,
screens, work flows, or documents—such defects that have work arounds in other words for the
meantime). The idea with testing is to of course look for and to identify ALL defects. And
frequently “backwards tests” should be written that have the goal of DELIBERATELY FAILING. You
test with the logic running both ways: expected successes and expected failures.
When the tests and retests or “regression testing” is complete then you run other tests that are
designed to “break the system.” These can be security tests, system failure tests, load tests,
disaster scenarios where part of the system is destroyed or disabled, tests that simulate possible
user fraud and hacking, tests that look for “limits” in the mathematical calculations the system
can perform (number of max decimal points for example), and the use of the system by having
rules that “highly restrict” work flow input or that do not “highly restrict” input. Note that the
T24 system can be set up to put “rules on everything” so that users cannot make mistakes. This
is known in the vernacular as “idiot proofing” the system. Some clients demand this, but doing
this sort of work is time consuming and further complicates the system and the testing. AVOID
THIS SORT OF THINKING AND PRACTICE if you can. Train the users in the proper use of the
system and have checkpoints where managers or approvers review users work before releasing
it into the live database.
Don’t let the vendor tell you how the testing should be done either. Ask the vendor who
typically does testing and who they are partners with for testing services. Note too that testing
can increase the cost of the project by 20-30%. Testing services provided by outside vendors are
very expensive. Remember that. And don’t let the vendor tell you that testing can be done in
house for no cost. Maybe, maybe not. Depends on your in house staff’s knowledge of testing
theory, strategy, and execution. Don’t let the vendor “steer you” into doing inadequate testing
because if you do that, you are letting the vendor “off of the hook” later for mistakes they may
have made and that they will deny that they did. Thorough testing is more work for the vendor
because the more bugs or defects you find the longer the vendor is stuck before getting final
payment which occurs at the go live milestone (typically 1/4 - 1/3 of the total income a vendor
earns from a project is payable at the end).
Client's Obligations (general and specific) - namely Backups - details on these and other Topics
143. The client provides the work space, equipment such as PCs and servers, some staff, the
telephones, internet, and furniture. Typically the vendor does NOT provide anything related to
the “project area” or the physical location where the project will be done. After the system
configuration and build is underway however the client is fully responsible for backups which
are done daily and at the same time each day within an hour or so. The vendor may try to short
cut on backups because it is time consuming. However the build should be backed up for two
reasons (a) safety if the system crashes and must be restored and (b) creating a “delta” whereby
if necessary in the future changes in earlier versions of the build may be examined. The vendor
will not like you keeping a “delta” of the build, but ASK THE VENDOR how this matter is handled.
The other obligations of the client may be to provide housing/lodging, transportation, and
meals for the vendor’s on site project staff. Be careful here because sometimes vendor staff
make unreasonable, if not outrageous, demands in this respect. Housing or lodging should be
adequate, convenient, and clean. Nothing more. The request for four or five star housing or
lodging should be rejected, even for senior staff. Also, transportation costs should be examined
closely so that staff from the vendor are not flying home every weekend or taking business or
first class seating. Also, local transportation is to and from the work place and not to lunch,
night time entertainment, weekend sightseeing, or generally taking taxis and cabs and other
privately hired cars all over town for other reasons (shopping, going to other client sites, etc).
Transportation and housing/lodging/meal costs are the highest of any on a project on a
recurring basis. Know what is expected, typical, and needs to be provided in all of these areas. If
a vendor’s staff member requests family to join them, the usual answer is a resounding NO. If a
vendor’s staff member requests maid service, cooks, special catering, outside arrangements for
special food, etc then the answer is also NO. Some vendor staff have even on occasion in my
nearly thirty years of experience requested that the client provide parties and entertainment
from time to time. Again, the answer is no. I even once saw where a big American bank
provided a project “kick off” dinner in San Francisco, CA in March, 2012 that cost the project’s
budget over $20,000 for one night at a fancy bar and restaurant at the Embarcadero. That
project with high transportation costs, four star hotels being used, and business class airfare for
some not to mention a catered lunch and breakfast at the bank every day for the project team
cost so much money that in 12 weeks time from its launch the project was canceled because
the entire yearly budget had been spent--and most of it spent on nonsense expenses, not the
project being done. Be careful with what you provide. You do not have to provide “nights at the
opera.” Forget it.
Place of Performance
144. Place of performance is typically the client’s own business premises. But that is open to
definition with some vendors who will allow staff to work everywhere and anywhere they want
to work except on the client’s premises. This is what you do--and what questions you ask?
145. Will there be any off-site or off-shore work and what is it? How is it managed? How is it
billed? How is the billing verified and how can it be audited?
146. What staff will not always be on site and why? What is the reason for “working away” from
the primary place of performance?
147. What is the rule about “working from home” even if that home is the “lodging” in the
location of place of performance?
148. What does the vendor do when there are issues with the place of performance (i.e. too
small, inadequate equipment, lines to internet too slow, poor lighting, poor heating/cooling, too
remote and hard to get to by usual public transportation, does not have the necessary meal
facilities nearby, does not have a sufficiently safe environment in the general area (i.e. located in
a building that is in the middle of some slum or high crime area), and what does the vendor do
in the event that staff for unknown reasons are suddenly not able to work at the primary place
of performance due to passport/visa reasons, issues with the police, being arrested while at the
place of performance (yes, this has happened before--typically from frequenting night clubs and
adult entertainment establishments where they got into trouble).
149. The question then to ask is what if the “key staff” suddenly cannot work at the primary
place of performance then what is the remedy? Be sure that the vendor puts this in writing.
Non Performing Employees/Contractors
150. The problem with non-performing employees and contractors is widespread in the T24
project world. The problem is that staff are assigned to projects and only do a certain job and
are not trained to do much more. The vendor will give you certifications, certificates, diplomas,
CVs, resumes, degrees, and a ton of other stuff that will try to convince you that their staff are
suitable and qualified, but in the end you’ll be more than surprised to find out that you’ve been
defrauded in a very carefully orchestrated confidence game that Temenos has run on you. But
how can you avoid this trap? What can you do to stop vendor staff from coming in and wrecking
your bank and botching the entire project and wasting your time and money? Here’s the
rundown and the exact set of questions you should ask long before any of these people show
up at your front door:
151. How many projects have they done--and what did they do on them? Look for words such
as this bank and that bank and this country and that country and did this on this
implementation and so on and so forth. What you’ll find is a hollow answer for each question
you ask. Half of the people if not more that Temenos will send you have less than three years
with the company. Also frequently their resumes and CVs have been “doctored” or altered
where someone in the HR department at Temenos has made the CVs of the staff offered “look
right.”
152 - 157. Interview these people individually before you agree to accept them. Don’t trust or
rely on what Temenos or some vendor or sub-contractor says about them. Check them and
interview them as if they were going to be your full-time staff. Check and follow up on
information on their CVs. Run reference checks. Then run full background checks. Look for CV
omissions. These sorts of changes tell the most. Find out from previous managers on
implementations elsewhere if they know these people. What did they do at their bank? What
did they not do? Check with other team members who may have knowledge about them. They
worked with these people supposedly. What do they say about their colleagues? Then most of
all look carefully at their CVs. Look at the names of the banks where they have done projects
before. Where are those banks? What sort of reputation do they have? The point is that
Temenos is notorious to staff their projects with people who know little more than a
programming language and do NOT KNOW how to write original programs themselves or do
T24 configuration that conforms to business and functional requirements. All they can do is to
bring up the command line, look at a program, and show you or tell you what’s in it. In short
they cannot “translate” that code into business language so that you actually know what it does
in the real world. That takes experience to do, and few Temenos staff have that level of skill.
158. Then ask them to “get on” and log on to the T24 system and show you around. Ask some
ad hoc questions. See what they do and if they can answer your questions. In the end, if nothing
else does, this test will usually expose the frauds and con artists.
Then see how well they speak English or the native language the project is in. Again, this will
reveal a lot about the ability of the vendor staff to “understand instructions.” Many cannot.
They conduct the project in their own native tongue, and frequently the “instructions and
requirements” are “lost in translation.” You get the idea. Don’t take the word of Temenos alone.
That’s what they want you to do. And if you get a bad staff member from the vendor, get rid of
them fast. Don’t be afraid to. It’s your bank, project, and money. Lose it and it’s gone. Believe
me. You’ll never get any of it back in cash or kind.
Project Phases and Services

159. The questions about how the project phases and services are instituted and organized are
basically to learn what the methodology of the vendor is. With Temenos they will give you a
methodology that has been designed to work in essentially two phases with a third phase
perhaps if there is a need based on regression testing. These phases are essentially “build” and
“test.” Basically you will get a project plan from Temenos that looks like this more or less
depending on the modules you buy:
Note - This plan would run for about two years.
T24 Implementation - ACCESSBANK
Project Initiation
Signature of Contract
Services Agreed
Systems Integrator/Programme Manager & Project Team Appointed
Kickoff Meeting
Introduction to Temenos Implementation Methodology - Handover of Templates
T24 Model Bank Implementation
Project Governance
Environment Support
Implementation Main Pre-requisites
Initial Architecture Workshop with recommendations
Architecture document definition
Systems Administrator for Bank Appointed and in place - Bank Activity
Security Administrator for Bank Appointed and in place - Bank Activity
Database Administrator for Bank Appointed and in place - Bank Activity
Software change management system in place - Bank Activity
Hardware purchased and ready - Bank Activity
Network ready - Bank Activity
Application Server, Messaging Server, Web Server software installed - Bank Activity
Infrastructure ready for implementation - Bank Activity
Initial Environment Setup
Set up Initial Test Environment
Book Technical Consultant
Carry out installation activities
Carry out basic checks post setup
Technical Training - Standard for Implementation Team
Technical Training - Standard for Implementation Team
Confirm location of training
Book trainer with least likely VISA issues if appropriate
Apply for VISA
Agree Agenda with both parties
Carry out training
Technical Training Complete
Business Training - Standard for Implementation Team
Confirm training resource
Agree Agenda
Confirm trainees from ABA
Prepare Facilities
T24 Introduction Training
Model Bank TAABs training
Obtain post training feedback
Business Introductory Training Complete
Business Requirements & TAABS Completion
Meetings with PMO to identify resources
PMO to confirm availability of resources
Propose outline schedule for workshops
Agree schedule of workshops
Confirm resources & arrange travel/accommodation
Management Consultancy
Business Reviews for TAABS Completion (Reference Processes)
Model Bank TAABS Review Oversight
Process Walkthrough / Product Definition
Review / Agree Processes, Products, Services
Technical Parameter Requirements
Define Technical Parameters
Test Scripts Produced By Bank (Using Temenos TIM Test Scripts) following Business Requirements Sign Off
Temenos Support Integration Test Scripts Preparation
Business Reviews for TAABS Completion complete
Test Script Production Complete - Bank Activity
Model Bank Reporting & Interfaces
Identify rsource for Central Reporting Analysis & Definition
Carry out Analysis of AZ Reporting Requirements
Schedule workshop with Finance on Reg reporting
Carry out workshop with Finance & document outputs
Produce Requirements Document
Obtain level of inputs required for interface creation
Model Bank Interface Configuration / Reporting
Interfaces Swift/3rd Party - TBA
Local Development
Packaging & Delivery
All Interfaces & Local Developments packaged and delivered on site
Installation of Interfaces & Reporting
Install and Unit Test of all Interfaces & Reporting (UAT, Dev, Training, Prod)
Environment Parameterisation
Parameterisation & Testing of Environment
Customisation Build
Environment Received and ready for installation on site
Delivery & Installation of Parameterised Environment
Identify resource to define the Arabization
Additional Onsite Parameterisation of Environment
Internal Test of Parameterised Environment
Parameterised Environment Available for Testing
Preliminary Testing of Parameterised Environment (No Dev)
Obtain definition of outputs from this phase
Bank parameterised environment Testing Support
Testing of Parameterised Environment Complete
Model Bank Reporting & Interfaces Delivery Complete
Pre-Testing Training (Project Team & Testers)
Confirm Location of training
Confirm whether super user training can consolidate with train the trainer
Identify super users that will carry out the UAT
Business Training
Technical Training
Integration Testing
Temenos Support During Integration Testing
UAT (Bank Activity)
Produce Test Strategy
Temenos Support During UAT Execution
UAT Issue Resolution - Cycle 1
UAT Issue Resolution - Cycle 2
Functional Pre Go Live Audit
Technical Pre Go Live Audit
Sign off UAT - Bank Activity
Business Training
Identify Trainer
Super User Business Training - for Bank Train the Trainer
Branch Training - Bank Activity
Go Live
Go Live Preparation
Preliminary & LIVE RUN
Go Live - Bank Activity
Post Live Support
Project Close
Project Closure
Post Live Support
Post Live Support
You actually can’t tell a lot from a project plan other than the scheduled work to be done. What
you can tell however is the depth of the work and the timeline to do it. That’s the issue with any
banking system implementation--the time to do it--but with the phases of the project if you
know how to work them out you can set up a better control mechanism that will give you a
consistent view of the progress of the project IF YOU WILL not let the vendor tamper with the
base line of the original project plan and move things around on a daily basis if there is slippage
in the project or things begin to GO WRONG. The first phase of the project (and in the project
plan) should consequently set down the BASE LINE (that is the expected due dates of everything
at 100% completion) and LOCK IT. Do not let the vendor play around with the project plan and
start lying with what goes into it regarding daily updates. The deviation of the project from the
original plan and baseline should be watched carefully and the vendor should NOT be allowed
to control the project plan, the project phases, the project tracking, or anything else. You should
set up you own PMO (Project Management Office) and control all of this information yourself.
The vendor reports to you, the client, not the other way around. But the vendor will attempt to
control the project and to take over everything involved so that the truth is suppressed and the
project becomes the sole universe of the vendor where essentially “lawlessness will abound.”
You stop that yourself as the client early on during the first phase of the project.
So what you do as the client is to make sure that you implement safeguards and
counterbalances to keep the vendor under control and to keep the vendor from manipulating
the project with lies and bad information in order to make the project look like everything is
“OK” when in fact it is NOT.
Business Requirements Analysis (who does it - to what level of detail)
160. - 161. This is where most projects get off of the tracks from the 1 st day. Due diligence rule
#1 is that you do NOT go out and buy a business solution of any sort, especially a core banking
system such as T24, without first doing your OWN business requirements before you ever go to
the market. The business requirements are the basis for your due diligence. How can you shop
or buy without knowing exactly what you need? But you’d be surprised to know how many
banks do exactly that. They go to the market with nothing about what they need and buy the
first system that “looks good.” And Temenos knows that. And they bank on you doing that. And
when you show up at their front door they will lure you in and tell you anything you want to
hear if it results in you giving them your money. So remember that buying without knowing is
about as smart as driving a car without a road map. You may wind up anywhere, but I can
assure you that you will not wind up where you thought you would.
162. Requirements cover many areas, and they should be written with as much detail as you can
put. You don’t have to document the last level of code in the system, but you need to have
enough information for each requirement so that you can determine whether a vendor’s system
can do the same on line. Vendor’s say they can do everything, but the classic requirement to
see what T24 can do is the ever evasive “real time Nostro account limits.” T24 cannot do this
and never could. I won’t go into the reasons why, but in the Limits module real time Nostro
account limits are impossible to do. That requirement should always be presented to Temenos
to see whether they lie or not about their system NOT being able to do this. The other
requirement is whether T24 can do structured trade finance. It cannot. I won’t go into what all
is involved in structuring, but basically it is collateralizing letter of credit limits for import LCs
with letter of credit payments from export LCs. Sounds simple but it is not. The other question is
to ask about user security profiles based on daily trading limits for FX traders. They will tell you
that they have daily limits for each FX trader but get up a little closer and see how they do it.
The problem is that system users cannot really be bank customers. T24 only tracks limits on
customers, not on users or bank employees. This question and requirement comes up all of the
time.
163. Ask whether T24 has a truly relational database with TAFJ or whatever (jBase, TAFC,
Univers, the original name for those three). It does not. It’s a hierarchical or extendable
database which is over fifty years old in design (1960s).
164. And the questions for business requirements and functional requirements (functional = can
the system do it?) go on and on. I can’t list all of them here, but if you really do the
requirements so that you see the “real concerns” about the requirement (such as limits per day
for FX traders or other traders set up in the Securities module) then you’ll get to the truth
before you are told a pack of lies about “yeah, we can do that and do this” and so forth where
the information you are receiving is coming from someone who does not know what they are
talking about.
165. Then be sure to ask the really BIG question about how the general ledger works in T24. It
doesn’t have a separate database for T24 information. It’s a “virtual GL” which means that it is a
report produced during the COB or Close of Business run. It cannot be amended and you cannot
see it during business hours and know what specifically is or will be posted to it. This is a
discussion that gets more complex, and I’ll add a separate section on general ledger and how it
works in T24 at the end of this document in Appendix A.
The point is that if you do not have clear and specific enough business requirements AND do
not MAKE THEM A PART OF YOUR CONTRACT AND SOFTWARE AGREEMENT WITH TEMENOS
you will be the one who gets taken advantage of in the end, not the vendor. And once the
contract is signed, that’s it. They will NOT renegotiate it, nor will they cancel it. You are stuck
with them at that point “for better or for worse.” So be careful. Control your environment. Do
not let them do that to you, the bank.
Software Development
166. These programs list in the table further down below are typical of customized software
development in T24—and most of these were developed for a building society in Scotland that
failed in 2009 - millions of dollars (around $64 million over some five years) were spent
developing these customizations to T24 - in the end the bank was flat broke. Some blamed
Temenos; some blamed the recession of 2008-2009. We’ll never know, but this project “died”
and never went live. The building society was sold for 1 GBP--so what’s the lesson to be learned
here with software development in T24: KNOW WHAT YOU ARE GETTING INTO.
This client was lured into the old scam that Temenos runs where they were going to turn T24
into a building society application this time (they’ve tried to make it into a microbank
application, an Islamic bank application, an Americanized version, etc. etc. none of which
amounted to much but a different flavor of the same old junk) and sell it to all of the building
societies in the UK. That was a lofty idea, and one client was sucked into this idea with the
understanding at first that they would own this T24 for building societies application and could
then resell it as their own property if they would pay for developing it. All right, greed knows no
boundaries and once this project was underway it was soon reality that it was too big, the
technology was too diverse and incompatible, and that it would take 100s of thousands of man
hours to do IF IT COULD BE DONE.
Also later in this project (a few years into it) Temenos reneged on their original agreement and
refused to let the client own and resell the T24 for BS's which was called Temenos Building
Society or TBS for short. Another “Temenos success story.”
Software development in conjunction with these people??? You have to be kidding. Read the
history of this messy chapter in the annals of Temenos lore. They may not say much about it
today since it was about ten years ago, but the Dunfermline Building Society is one of the
nastier chapters in Temenos’ project history. Dunfermline failed in 2009. Over $64 million USD
was wasted in the end on T24 developnent there. Nearly 1400 little programs were written to
make T24 work for a UK building society--some of the programs are shown below to show how
“out of hand” and out of scope and out of original size and intention this project got.
_______________________________________________________
E.TBS.UNPAID.DD.BR
E.TBS.UNPAID.DD.BR
This routine will display all Direct Debits which are un-paid, by Branch
*
SUBROUTINE E.TBS.UNPAID.DD.BR(TMNS.STRING)
********************************************************************************
This routine will display all Direct Debits which are un-paid, by Branch
*
*
********************************************************************************
First Release : 30th Sep 2004
Developed for : DBS - Dunfermline Building Society
Developed by : Javaid Ahmed Butt
*
********************************************************************************
*
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_ENQUIRY.COMMON
$INSERT I_F.DD.RETURN
$INSERT I_F.DD.ITEM
$INSERT I_F.DD.REASON.CODES
$INSERT I_F.DE.ADDRESS
$INSERT I_F.ACCOUNT
*
Insert File for report dates
$INSERT I_DD.DATE.CHECK
*
GOSUB INITIALIZE
GOSUB PROCESS
*
RETURN
*
********
PROCESS:
********
*
* Selection for Direct Debit
*
QRY.STR = "SSELECT ":FN.DD.RET
QRY.STR := " WITH CREATE.DATE GE ":M.FR.DT
QRY.STR := " AND CREATE.DATE LE ":M.TO.DT
QRY.STR := " AND RET.REASON NE ''"
CALL EB.READLIST(QRY.STR,LIST.IDS,"",TOT.REC,ERR1)
*
IF NOT(TOT.REC) THEN RETURN
FOR I = 1 TO TOT.REC
M.DD.ID = LIST.IDS<I>
READ R.DD.RET FROM F.DD.RET, M.DD.ID THEN
M.CNT = DCOUNT(R.DD.RET<DD.RET.CLAIM.CONTENT>,VM)
M.ITEM.ID = R.DD.RET<DD.RET.DD.ITEM.ID>
READ R.ITEM.REC FROM F.DD.ITEM, M.ITEM.ID THEN
M.BID.NO = R.ITEM.REC<DD.ITEM.ACCOUNT.NO>
M.DAO = R.ITEM.REC<DD.ITEM.ACCOUNT.OFFICER>
M.AMOUNT = R.ITEM.REC<DD.ITEM.AMOUNT>
END
CALL DBR('ACCOUNT':FM:AC.CUSTOMER,M.BID.NO,M.CUSTOMER)
M.DE.ID = ID.COMPANY:'.C-':M.CUSTOMER:'.PRINT.1'
READ R.DE.REC FROM F.DE.ADDR, M.DE.ID THEN
M.NAME = R.DE.REC<DE.ADD.NAME.1>
M.ADDR = R.DE.REC<DE.ADD.STREET.ADDRESS>
M.TOWN = R.DE.REC<DE.ADD.TOWN.COUNTY>
M.PC = R.DE.REC<DE.ADD.POST.CODE>
END
M.COMB.STR = ''
FOR J = 1 TO M.CNT
M.COMB.STR := R.DD.RET<DD.RET.CLAIM.CONTENT,J>
NEXT J
M.AC.TYP.CD = M.COMB.STR[15,1]
READ R.REASON.REC FROM F.DD.REASON,M.REASON.ID THEN
LOCATE M.AC.TYP.CD IN R.REASON.REC<DD.RC.REASON.CODE,1> SETTING R.POS THEN
M.REASON = R.REASON.REC<DD.RC.ENRICH,R.POS>
END ELSE
M.REASON = 'CODE IS INVALID OR NOT DEFINED ':M.AC.TYP.CD
END
END
GOSUB BUILD.STRING
END
NEXT I
*
RETURN
*
*************
BUILD.STRING:
*************
*
M.LAYOUT = ""
*
M.LAYOUT = M.BID.NO ;1
M.LAYOUT := '*':M.NAME ;2
M.LAYOUT := '*':M.ADDR ;3
M.LAYOUT := '*':M.TOWN ;4
M.LAYOUT := '*':M.PC ;5
M.LAYOUT := '*':M.AMOUNT ;6
M.LAYOUT := '*':M.REASON ;7
M.LAYOUT := '*':M.DAO ;8
*
TMNS.STRING<-1> = M.LAYOUT
*
RETURN
*
***********
INITIALIZE:
***********
*
FN.DD.RET = "F.DD.RETURN"
F.DD.RET = ""
CALL OPF(FN.DD.RET,F.DD.RET)
*
FN.DD.ITEM = "F.DD.ITEM"
F.DD.ITEM = ""
CALL OPF(FN.DD.ITEM,F.DD.ITEM)
*
FN.DD.REASON = "F.DD.REASON.CODES"
F.DD.REASON = ""
CALL OPF(FN.DD.REASON,F.DD.REASON)
M.REASON.ID = 'BACS'
*
FN.DE.ADDR = "F.DE.ADDRESS"
F.DE.ADDR = ""
CALL OPF(FN.DE.ADDR,F.DE.ADDR)
*
RETURN
*
*
END
_______________________________________________________
E.TBS.USER.DEPT
E.TBS.USER.DEPT
This routine will receive the DAO of a transaction, account, contract etc. and will compare this to the department of the user - will return 1 if
they match, 0 if they don't. Used to select only those transactions, contracts etc, which should be visable to a user.
SUBROUTINE E.TBS.USER.DEPT(OWN.DEPT, REC.DEPT)
This routine will receive the DAO of a transaction, account,

contract etc. and will compare this to the departmert of the
user - will return 1 if they match, 0 if they dont.
*
Used to select only those transactions, contracts etc, which
should be visable to a user.
*
Written by JBW 08-10-05
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_F.USER
OWN.DEPT = 0
IF R.USER<EB.USE.DEPARTMENT.CODE> = REC.DEPT THEN OWN.DEPT = 1
RETURN
END
_______________________________________________________
E.TBS.USER.EVENT
E.TBS.USER.EVENT
Conversion routine to produce all records from USER and from TBS.PROCESS.EVENT
SUBROUTINE E.TBS.USER.EVENT(TMNS.STRING)
**************************************************************
NAME: E.TBS.USER.EVENT
for T24/jbase use: JAVED BUTT (TEMENOS) DATE: 27-OCT-2005
*
DESCRIPTION:
Conversion routine to produce all records from USER and from
TBS.PROCESS.EVENT
*
TECHNICAL DESCRIPTION:
*
CHANGE REQUEST / DEVELOPMENT REF:
*
CALLED BY:
*
CALLS:
*
*
CHANGE HISTORY:
**************************************************************
*
$INSERT I_COMMON
$INSERT I_EQUATE
*
GOSUB INITIALISE
GOSUB PROCESS.ACCOUNTS
*
RETURN
!====================================================
INITIALISE:
!==========
FN.USER = "F.USER"
CALL TBS.OPF(FN.USER, F.USER)
*
FN.TPE = "F.TBS.PROCESS.EVENT"
CALL TBS.OPF(FN.TPE, F.TPE)
*
TMNS.STRING = ''
*
RETURN ; END OF INITIALISE
!====================================================
PROCESS.ACCOUNTS:
!================
*
QRY.USR = "SSELECT ":FN.USER
CALL EB.READLIST(QRY.USR,USR.ID.LIST,'',USR.TOT.REC,'')
*
QRY.TPE = "SSELECT ":FN.TPE
CALL EB.READLIST(QRY.TPE,TPE.ID.LIST,'',TPE.TOT.REC,'')
*
TMNS.STRING = TPE.ID.LIST ; All profiles from TBS.PROCESS.EVENT
TMNS.STRING<-1> = USR.ID.LIST ; All User IDs
*
RETURN
!====================================================
*
END
_______________________________________________________
E.TOTAL.LOCKED.AMOUNT
E.TOTAL.LOCKED.AMOUNT
Routine to calculate the total locked amount on an account due to arrestment, sequestration or disputes
SUBROUTINE E.TOTAL.LOCKED.AMOUNT(OUT.DATA,FROM.DATE,LOCKED.AMOUNT)
SUBROUTINE E.TOTAL.LOCKED.AMOUNT(OUT.DATA,LOCKED.KEYS)
Routine to calculate the total locked amount on an account due to arrestment, sequestration or disputes
Developed by Ritesh Srivastava/May 18,2004
S20051214 - Calculation of locked amount is changed from AC.LOCKED.EVENTS to ACCOUNT
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_F.AC.LOCKED.EVENTS ; *S20051214
S20051214 - S
V.FROM.DATE.CNT = DCOUNT(LOCKED.AMOUNT,@VM)
IF FROM.DATE<1,V.FROM.DATE.CNT> LE TODAY THEN

OUT.DATA = LOCKED.AMOUNT<1,V.FROM.DATE.CNT>
END
S20051214 - E
RETURN
END
_______________________________________________________
E.USER.ID
E.USER.ID
SUBROUTINE E.USER.ID(TRUEFALSE,INUSER)
*
$INSERT I_COMMON
$INSERT I_EQUATE
IF OPERATOR = INUSER THEN TRUEFALSE = 1 ELSE TRUEFALSE = 0
RETURN
END
_______________________________________________________
E.WP.CONV.LINK.CARDS
E.WP.CONV.LINK.CARDS
Account information in WEALTH.POSITION should include related LINK CARDS
SUBROUTINE E.WP.CONV.LINK.CARDS
*=================================================
*
Code Ref No : 01101
Written by : Prajwal
Company : Temenos
DATE: : 26-Jun-2006
*
*----------------------
Business Description:
*----------------------
Account information in WEALTH.POSITION should include related LINK CARDS.
*
*-----------------------
Technical Description:
*-----------------------
*
CARD.ISSUE.ACCOUNT record is read for the displayed Account in WP.
If LINK Card/s exist for the Account, then 'YES' is returned.
*
*--------------------------------
Change request /Development ref:
*--------------------------------
*
*------------
CALLED BY:
*------------
ENQUIRY - WP.INVESTMENT
*--------
CALLS:
*--------
*
*----------------
Change History:
*----------------
*
*=================================================
$INSERT I_EQUATE
$INSERT I_COMMON
GOSUB OPEN.FILE
GOSUB CONV.PROCESS
RETURN
OPEN.FILE:
*=========
FN.CARD.ISSUE.ACCOUNT = 'F.CARD.ISSUE.ACCOUNT'
CALL OPF(FN.CARD.ISSUE.ACCOUNT, F.CARD.ISSUE.ACCOUNT)
R.CIA = '' ; ER = ''
RETURN
*
CONV.PROCESS:
*============
CALL F.READ(FN.CARD.ISSUE.ACCOUNT, O.DATA, R.CIA, F.CARD.ISSUE.ACCOUNT, ER)
O.DATA = ''
IF R.CIA THEN O.DATA = 'YES'
RETURN
*
END
_______________________________________________________
EB.PHANTOM.WRAPPER
EB.PHANTOM.WRAPPER
This process will be used as the RUN.ROUTINE for EB.PHANTOM the actual process which is run will be contained in the RUN.VALUE
SUBROUTINE EB.PHANTOM.WRAPPER
**************************************************************
*
Code Ref No :
Written by :
Company : Temenos (London, UK)
Date :
*
*----------------------
Business Description:
*----------------------
*
This process will be used as the RUN.ROUTINE for EB.PHANTOM
the actual process which is run will be contained in the
RUN.VALUE field
*
*-----------------------
Technical Description:
*-----------------------
*
*---------------------------------
Change request /Development Ref:
*---------------------------------
*
*
*-----------
CALLED BY:
*-----------
*
*
*-------
CALLS:
*-------
*
*----------------
Change History:
*----------------
*======================================================
04-Aug-2006 - By Tennyson Kpohraror ; TTK20060804
1. Remove redundant definitions of variable INTERACTIVE
2. Enable the option of running this phantom to process a specific file
defined in the EB.PHANTOM record
3. Make the prompts clearer/more meaningful
*
*======================================================
*
*
******************************************************************************************
*
*INSERTS
$INSERT I_COMMON
$INSERT I_EQUATE
*
$INSERT I_F.SPF
$INSERT I_SCREEN.VARIABLES
*
$INSERT I_F.EB.PHANTOM
************************************************************************
*
*
GOSUB INITIALISE
GOSUB INITIALISE.PHANTOM
GOSUB PROCESS.RECORDS:
*
RETURN.CALL = 0
*
*
************************************************************************
INITIALISE:
*
V$OUTPUT.LOG = 0
C$STO.ONLINE.FLAG = 1
TTK20060804 S
RTN.TO.CALL = ''
FILE.TO.PROCESS = ''
TTK20060804 E
RETURN
************************************************************************
*
PROCESS.RECORDS:
LOOP
*
GOSUB CHECK.SHUTDOWN
*
UNTIL RETURN.CALL
*
TTK20060804 S
BEGIN CASE
CASE RTN.TO.CALL AND FILE.TO.PROCESS AND YFILE.OPEN
FILEID = FILE.TO.PROCESS
READ YFILE.REC FROM F.DIR.TO.SEL,FILEID ELSE YFILE.REC = ''
IF YFILE.REC THEN
CALL @RTN.TO.CALL(DIR.TO.SEL,FILEID)
GOSUB MOVE.FILE
END
CASE RTN.TO.CALL
TTK20060804 E
CMD = 'SSELECT ':DIR.TO.SEL
EXECUTE CMD
LOOP
READNEXT FILEID ELSE FILEID = ''
WHILE FILEID
CALL @RTN.TO.CALL(DIR.TO.SEL,FILEID)
GOSUB MOVE.FILE
REPEAT
END CASE ; TTK20060804
*
GOSUB NOW.TO.SLEEP
*
REPEAT
*
GOSUB PRINT.TIME.S
C$STO.ONLINE.FLAG = 0
PRINT ' PROCESSING FINISHED - LOGGING OUT'
*
RETURN
*
************************************************************************
*
INITIALISE.PHANTOM:
ID.PHANTOM = ID.NEW
*
ERROR.TEXT = S.BELL:@(19,23):S.CLEAR.EOL:@(19,23)
*
F.FILE.CONTROL = ''
OPEN '','F.FILE.CONTROL' TO F.FILE.CONTROL ELSE NULL
*
*
Read EB.PHANTOM (with a view to checking the RUN status)
*
FN.EB.PHANTOM = "F.EB.PHANTOM"
F.EB.PHANTOM = ""
Y.EB.PHANTOM = ''
LAST.TIME.PROCESSED = 0
SLEEP.TIME = ''
SLEEP.MINUTES = ''
SLEEP.SECONDS = ''
V$OUTPUT.LOG = 0
*
CALL OPF(FN.EB.PHANTOM,F.EB.PHANTOM)
READ Y.EB.PHANTOM FROM F.EB.PHANTOM, ID.PHANTOM THEN
*
Set variables from the file record
*
SLEEP.TIME = Y.EB.PHANTOM<TD.SLEEP.SECS>
SLEEP.MINUTES = INT(SLEEP.TIME/60)
SLEEP.SECONDS = MOD(SLEEP.TIME,60)
*
TTK20060804 S
LOCATE 'RTN.TO.CALL' IN Y.EB.PHANTOM<TD.RUN.PARAM,1> SETTING POS1 THEN
RTN.TO.CALL = Y.EB.PHANTOM<TD.RUN.VALUE,POS1>
END
LOCATE 'FILE.TO.PROCESS' IN Y.EB.PHANTOM<TD.RUN.PARAM,1> SETTING POS1 THEN
FILE.TO.PROCESS = Y.EB.PHANTOM<TD.RUN.VALUE,POS1>
END
TTK20060804 E
IF NOT(RTN.TO.CALL) THEN ; TTK20060804
RTN.TO.CALL = Y.EB.PHANTOM<TD.RUN.VALUE,1> ; TTK20060804
END ; TTK20060804
DIR.TO.SEL = Y.EB.PHANTOM<TD.GLOBUS.IN.FILE>
DIR.TO.COPY = Y.EB.PHANTOM<TD.GLOBUS.OUT.FILE>
*
TTK20060804 S
YFILE.OPEN = ''
OPEN DIR.TO.SEL TO F.DIR.TO.SEL THEN
YFILE.OPEN = 1
END
TTK20060804 E
*
Set up a flag to establish the EB.PHANTOM status, i.e. to see if 'ACTIVE'
*
IF Y.EB.PHANTOM<TD.RUN.MODE> = 'INTERACTIVE' THEN
INTERACTIVE = 1
END ELSE
INTERACTIVE = 0
END
Setup field debug to determine whether to display messages

*
IF INTERACTIVE THEN
*
FOR I = 4 TO 19
PRINT @(0,I):S.CLEAR.EOL
NEXT I
*
END
*
PRINT ; TTK20060804
PRINT 'EB.PHANTOM.WRAPPER, ROUTINE - ':RTN.TO.CALL:' - STARTING PROCESSING'
*
END
*
Included for testing purposes

*
IF INTERACTIVE THEN
V$OUTPUT.LOG = 1
END
*
*
IF V$OUTPUT.LOG = 1 THEN
PRINT 'SLEEP TIME = ' :SLEEP.TIME
END
*
GOSUB PRINT.TIME.S
PRINT 'PHANTOM ' :ID.PHANTOM :' STARTED'
*
RETURN
************************************************************************
NOW.TO.SLEEP:
*
IF V$OUTPUT.LOG THEN
PRINT 'GOING TO SLEEP'
END
*
IF INTERACTIVE THEN
PRINT 'DO YOU WISH TO WAIT YES/NO (<cr> = YES)': ; TTK20060804
INPUT REPLY
*
IF REPLY AND REPLY[1,1] # 'Y' THEN ; TTK20060804
RETURN
END
*
END
*
SLEEP SLEEP.TIME
*
RETURN
************************************************************************
CHECK.SHUTDOWN:
Check for system shutdown.
*
IF V$OUTPUT.LOG THEN
PRINT 'CHECKING SHUTDOWN'
END
RETURN.CALL = 0
*
IF INTERACTIVE THEN
PRINT 'DO YOU WISH TO STOP YES/NO (<cr> = YES) ': ; TTK20060804
INPUT REPLY
*
IF REPLY AND REPLY[1,1] = 'N' THEN
RETURN
END ELSE
RETURN.CALL = 1
END
*
END ELSE
*
READ Y.EB.PHANTOM FROM F.EB.PHANTOM, ID.PHANTOM THEN
*
IF Y.EB.PHANTOM<TD.PHANT.STOP.REQ> = 'STOP' THEN
RETURN.CALL = 1 ; Shutdown
GOSUB PRINT.TIME.S
PRINT ' EB.PHANTOM.WRAPPER - SHUT DOWN'
Y.EB.PHANTOM<TD.STATUS> = "CLOSED"
END ELSE
IF Y.EB.PHANTOM<TD.STATUS> <> "ACTIVE" THEN
Y.EB.PHANTOM<TD.STATUS> = "ACTIVE"
Y.EB.PHANTOM<TD.RECORD.STATUS> = "RUNNING"
END ELSE
Y.EB.PHANTOM<TD.RECORD.STATUS> = 'RUNNING (LAST READ) - ':TIMEDATE()
END
END
WRITE Y.EB.PHANTOM TO F.EB.PHANTOM, ID.PHANTOM
END
*
END
*
RETURN
************************************************************************
MOVE.FILE:
*
IF DIR.TO.COPY THEN
DATESTAMP = TIMEDATE()
CONVERT ' ' TO '_' IN DATESTAMP
CMD = 'COPY FROM ':DIR.TO.SEL:' TO ':DIR.TO.COPY:' ':FILEID:',':FILEID:'.':DATESTAMP:' DELETING'
EXECUTE CMD
END
*
RETURN
*
************************************************************************
PRINT.TIME.S:
*
TIME.STAMP = TIMEDATE()
X1 = OCONV(DATE(),"D-")
PRINT X1 :' - ' :TIME.STAMP[1,2] :':':TIME.STAMP[4,2]:
RETURN
************************************************************************
THE.FINAL.END:
END
_______________________________________________________
List of T24 Custom Programs CONV.INS.CONTRACT.FIELDS4243 E.DBS.STMT.CONCAT

CONV.INS.CUST.PRODUCT E.DBS.TELLER.AMT
AMEXIN.PROG
CONV.INS.PRODUCT E.DBS.TP.CHQ.WD
BAT.CLEAR.REPLINE.LOCK
CONV.TBS.AC.PRODUCT.ENRI E.DBS.TXN.LEVELS
BAT.DBS.DD.REG.REQ.PAYMENT
CONV.TBS.DOC.TRACKING E.GET.ALL.MAT.PARTS
BAT.DBS.DD.REG.REQ.PAYMENT.LOAD
CONV.USER.TO.ORACLE E.GET.CHARGE.IDS
BAT.DBS.DD.REG.REQ.PAYMENT.SELECT
CONVERT.BANK.WIZARD.CODES E.GET.CR.INT.RATE
BAT.INS.DEL.QUOTE
CONVERT.CASHBACK.DESCRIPTION E.GET.DEFAULT.NOMINAL
BAT.INS.DEL.QUOTE.LOAD
CONVERT.DOC.TRACKING E.GET.LOWEST.CONT.SEQ
BAT.INS.DEL.QUOTE.SELECT
CORRECT.TBS.PRODUCT.EVENT E.GET.TBS.MULTI.TELLER.TXNS
BAT.INS.PREM.COLLECTION
CREATE.TBS.NOTICE.WITHDRAWAL E.GET.VALID.DDI
BAT.INS.PREM.COLLECTION.LOAD
CROSSVAL.INS.RANGE E.MG.PMT.AMT
BAT.INS.PREM.COLLECTION.SELECT
DBS.AC.TIER E.MG.REDEEMED.PORT
BAT.INS.PROCESS.MATURITY
DBS.AGRESSO.ONLINE E.MT.SIGNATURE.REQD
BAT.INS.PROCESS.MATURITY.LOAD
DBS.ARR.TXN.FILE E.NO.OF.LEVELS
BAT.INS.PROCESS.MATURITY.SELECT
DBS.BUILD.STMT.ENTRY E.NO.OF.LEVELS.MG
BAT.INS.PROCESS.RENEWAL
DBS.CAISPLUS.MG E.PRINT.MASK.DBS
BAT.INS.PROCESS.RENEWAL.LOAD
DBS.CLEAR.TXN.FILES E.PRINT.MULTI.TELLER
BAT.INS.PROCESS.RENEWAL.SELECT
DBS.CONV.XML E.PRINT.TAX.FORMS
BAT.MT.LIVE.TO.HIS
DBS.CUST.INTERFACE E.QTRLY.ISA.RETURN
BAT.MT.LIVE.TO.HIS.LOAD
DBS.DCMIFL.INWARD.CUST E.SCV.MV.COUNT
BAT.MT.LIVE.TO.HIS.SELECT
DBS.DCMIFL.NON.CAIS.FEED E.SCV.REC.COUNT
BAT.SEND.LETTERS.TO.PRINT
DBS.DE.CORRS.ADD E.STMT.ENTRY.DRCR
BAT.STO.PPI.PAY
DBS.E.AGRESSO.LINK E.TBS.AC.CHANGE.DATA
BAT.STO.PPI.PAY.LOAD
DBS.E.CONV.TO.XML E.TBS.AC.INTEREST.DATA
BAT.STO.PPI.PAY.SELECT
DBS.GENERIC.INTERFACE E.TBS.ACCT.RESTRICTIONS
BAT.STORE.COB.DATE
DBS.GET.INT.RATE E.TBS.AEGON.ARR.AC.SUM
BAT.TBS.AC.SUBS
DBS.GIT.AGRESSO.EXTRACT E.TBS.AEGON.P11D
BAT.TBS.AC.SUBS.LOAD
DBS.I.GET.PHONE.NO E.TBS.BRANCH.PRODUCTS
BAT.TBS.AC.SUBS.SELECT
DBS.IMPORT.STMT.ENTRY E.TBS.BUILD.ARREARS.TXNS
BAT.TBS.ACC.DIRECT
DBS.ISA.ANNUAL.RETURN E.TBS.BUILD.CONS.FORMS.LIST
BAT.TBS.ACC.DIRECT.LOAD
DBS.ISA.RETURN.AND.CLAIM14 E.TBS.BUILD.MG
BAT.TBS.ACC.DIRECT.SELECT
DBS.LINK.DATA E.TBS.BUILD.MG.REDEM.ILLU
BAT.TBS.AUTO.WRITEOFF
DBS.LINK.DATA.EOD E.TBS.BUILD.SCV
BAT.TBS.CHANGE.TAX.STATUS
DBS.MIGRATION.FLAG E.TBS.BUILD.SEL.MG.LIST
BAT.TBS.CHANGE.TAX.STATUS.LOAD
DBS.MVMT.AGR E.TBS.BUILD.TXN.FILE
BAT.TBS.CHANGE.TAX.STATUS.SELECT
DBS.MVMT.EOD E.TBS.BUILD.WEALTH.POSITION
BAT.TBS.CLEAR.BROKER.SUBS
DBS.MVMT.EOD.LOAD E.TBS.CALC.NEW.OUTSBAL
BAT.TBS.COPY.DD.PROCESS.LIST
DBS.MVMT.EOD.POST E.TBS.CALC.UNCOM.INT
BAT.TBS.COPY.EOD.LIST
DBS.MVMT.EOD.SELECT E.TBS.CHECK.PREV.PAYMENTS.MADE
BAT.TBS.DD.ADJUSTMENTS.EOD
DBS.MVMT.PARAM.FIELD.DEFINITIONS E.TBS.CHECK.REPAY.AMT
BAT.TBS.DD.ADJUSTMENTS.EOD.LOAD
DBS.N.RE.STAT.LINE.MVMT E.TBS.COMM.ARR
BAT.TBS.DD.ADJUSTMENTS.EOD.PRE
DBS.S17.RETURNS E.TBS.CONV.HOUSE.NO
BAT.TBS.DD.ADJUSTMENTS.EOD.SELECT
DBS.TNS.EXTRACT E.TBS.CONV.INT.RATES
BAT.TBS.EXTRACT.ARR.TXNS
DBS.TNS.EXTRACT.FIELD.DEFINITIONS E.TBS.CONV.MG.DATA
BAT.TBS.FINAL.LETTER
DBS.TNS.PROCESS.EOD E.TBS.CONV.MV
BAT.TBS.FINAL.LETTER.LOAD
DBS.TNS.PROCESS.EXTRACT E.TBS.CONV.MV.LOCREF
BAT.TBS.FINAL.LETTER.POST
DBS.TURN.AGR E.TBS.CONV.NEXT.PAY
BAT.TBS.FINAL.LETTER.SELECT
DBS.VERIFY.STMT.ENTRY E.TBS.CONV.PEN.EXP.DATE
BAT.TBS.LOCKED.EVENT
DEF.TBS.COM.CHG.CODE E.TBS.CONV.PORT.AMT
BAT.TBS.LOCKED.EVENT.LOAD
DEFAULT.TBS.ALL.APPLICATION E.TBS.CONV.REDEM.PEN.AMT
BAT.TBS.LOCKED.EVENT.SELECT
DELETE.TBS.UNAU.RECORDS E.TBS.CONV.REV.MG.PAY
BAT.TBS.MG.APPL.NEWRATE.2
E.ANNUAL.ISA.STATS E.TBS.CU.CHANGE.DATA
BAT.TBS.MG.APPL.NEWRATE.2.LOAD
E.BRANCH.NOMS E.TBS.DISP.PENALTY
BAT.TBS.MG.APPL.NEWRATE.2.SELECT
E.BUILD.MG.PAYMENTS E.TBS.FILTER.LAST.HIS.REC
BAT.TBS.MG.CONFIRMATION
E.BUILD.PRINT.MULTI.TELLER E.TBS.FIND.DD
BAT.TBS.MG.PREFPAY.PAYMENT
E.BUILD.SS.FIELDS E.TBS.FIXED.RATE.MAT
BAT.TBS.MG.PREFPAY.PAYMENT.LOAD
E.BUILD.TB.DEAL.SLIP.DATA E.TBS.FORMAT.ID
BAT.TBS.MG.PREFPAY.PAYMENT.SELECT
E.BUILD.TBS.MAT.LIST.SEL E.TBS.GET.AC.INT.ALL
BAT.TBS.MG.RETN.PREP
E.BUILD.TBS.TILL.CLOSE.DATA E.TBS.GET.ALL.AEGON.CUST
BAT.TBS.MG.RETN.PREP.LOAD
E.BUILD.TBS.TILL.OPEN.DATA E.TBS.GET.CUS.AC
BAT.TBS.MG.RETN.PREP.SELECT
E.CASH.CHQ.AMT E.TBS.GET.CUS.DETAILS
BAT.TBS.MG.SWITCH.PRODUCT
E.CHECK.AGENCY E.TBS.GET.ERC
BAT.TBS.MG.SWITCH.PRODUCT.LOAD
E.CONSN.AMT.TOTAL E.TBS.GET.FIRST.VALUE
BAT.TBS.MG.SWITCH.PRODUCT.SELECT
E.CONV.DATA E.TBS.GET.INSPREM
BAT.TBS.NON.RETEN.LETTER
E.CONV.TBS.GET.OUTSBAL E.TBS.GET.MATMONTHS
BAT.TBS.PROD.EVENT
E.CONV.TBS.MG.MONTH.PAY E.TBS.GET.MG
BAT.TBS.PROD.EVENT.LOAD
E.CONV.TBS.SPL.FMT E.TBS.GET.MG.ID
BAT.TBS.PROD.EVENT.SELECT
E.CONVERT.IN.WORDS E.TBS.GET.MGPAYDETS
BAT.TBS.PRODUCE.REDEM.LIST
E.DBS.AEGON.TRANSACTIONS E.TBS.GET.NOTE
BAT.TBS.PRODUCT.LETTER.2
E.DBS.BACS.DIRECT.CR.IN E.TBS.GET.PORTPEREND
BAT.TBS.PRODUCT.LETTER.2.LOAD
E.DBS.BEN.IN.KIND.P11D E.TBS.GET.PROD.TERM.PAY.DATES
BAT.TBS.PRODUCT.LETTER.2.SELECT
E.DBS.CALC.ADV.PMT E.TBS.GET.PRODUCT.PAY.DATE
BAT.TBS.PRODUCT.LETTER.3
E.DBS.CALC.REDM.BAL E.TBS.GET.REDEM.AMT
BAT.TBS.PRODUCT.LETTER.3.LOAD
E.DBS.CHQ.MAT.BOND E.TBS.GET.RETENTION.DETAILS
BAT.TBS.PRODUCT.LETTER.3.SELECT
E.DBS.CLOSURE.DATE E.TBS.GET.STMT.DATES
BAT.TBS.REDEM.LETTERS
E.DBS.DISP.NOM.TXN E.TBS.GET.SVRREVERT
BAT.TBS.SUBS.LETTER
E.DBS.EARLY.CLOSE E.TBS.GET.TEL.1
BAT.TBS.SUBS.LETTER.LOAD
E.DBS.EARLY.CLOSE.MG E.TBS.GET.TEL.2
BAT.TBS.SUBS.LETTER.SELECT
E.DBS.EARLY.WD.FIX.TERM E.TBS.GET.TEL.3
BAT.TBS.TRACKING.CHARGES
E.DBS.ESTMD.ACCR E.TBS.GET.TEL.4
BAT.TBS.TRACKING.CHARGES.LOAD
E.DBS.ESTMD.DLY.MG.ACCR E.TBS.HAS.MG.PROD
BAT.TBS.TRACKING.CHARGES.SELECT
E.DBS.HIGH.TO.SCT.GLD E.TBS.HCSL.CUSTOMER
BAT.TBS.TRACKING.OVD
E.DBS.HIGH.TURNOVER E.TBS.INS.PRM.COL
BAT.TBS.TRACKING.OVD.LOAD
E.DBS.INT.FREQ E.TBS.INT.STMT.SEL
BAT.TBS.TRACKING.OVD.SELECT
E.DBS.INV.BAL E.TBS.LARGE.WD
BAT.TBS.TRACKING.PENDING
E.DBS.INV.TRANS E.TBS.LIBOR.ANALYSIS
BAT.TBS.TRACKING.PENDING.LOAD
E.DBS.JOINT.CUST E.TBS.MEMBER.SINCE
BAT.TBS.TRACKING.PENDING.SELECT
E.DBS.LARGE.CASH.TRUST.TXN E.TBS.MG.BUILD.NAT.REDEM
BAT.TBS.UPD.ISA.STATUS
E.DBS.LARGE.CASH.TXN E.TBS.MG.BUILD.REDEM.LET
BAT.TBS.UPD.SUBS
E.DBS.LARGE.DEP.DORM.AC E.TBS.MG.ERC.55
BUILD.MG.DEEDCARE
E.DBS.LINK.DATA E.TBS.MG.FORMAT.CCY
BUILD.MV.RELS
E.DBS.LRG.TXN.MG.AC E.TBS.MG.GET.3M.SVR
BUILD.STANDARD.DL
E.DBS.MAT.ANALYSIS.AC E.TBS.MG.GET.DISC
CALC.INS.APP.AGE
E.DBS.MAT.ANALYSIS.MG E.TBS.MG.GET.EVENT.DATE
CALC.INS.CHARGE
E.DBS.MAT.DET.FT E.TBS.MG.GET.NEW.MAT.DATE
CALC.INS.COMB.DISC
E.DBS.MAT.DETAILS E.TBS.MG.GET.OUTSTANDING.BAL
CALC.INS.PREM.TAX
E.DBS.MAT.RETENTIONS E.TBS.MG.GET.REDEM.CHG
CALC.TBS.BONUS.INT
E.DBS.MG.IN.ADV E.TBS.MG.GET.TOT.ADVANCE
CALC.TBS.CHARGE
E.DBS.MG.OUTS.BAL E.TBS.MG.INS.DETAIL
CALC.TBS.INTEREST
E.DBS.PASSBOOK.ADDRESS E.TBS.MG.INT.BUILD.NAT.REDEM
CHECK.TBS.NOTICE.WDL
E.DBS.POP.FILE E.TBS.MG.INT.RCVD
CONV.ACCOUNT.DBS.BUILD23
E.DBS.RATE.CHANGE E.TBS.MG.IS.NATURAL.REDEMPTION
CONV.DD.PROCESS.LIST.TBS.G14.1
E.DBS.REDEM.TOT.ADJ E.TBS.MG.LETTER.DATA
E.TBS.MG.NOFILE.DATA I_F.DBS.AC.TIER I_F.TBS.BACS.DD.RETURNS

E.TBS.MG.REDM.DATE I_F.DBS.ARR.TXN.FILE I_F.TBS.BANK.WIZARD.CODES
E.TBS.MT.BAT.TXNS I_F.DBS.CUST.INTERFACE I_F.TBS.BRANCH.BANKING
E.TBS.NOTICE.DATE I_F.DBS.GENERIC.INTERFACE I_F.TBS.CARD.ISSUE
E.TBS.PRINT.TIME I_F.DBS.LINK.DATA I_F.TBS.CARD.REQUEST
E.TBS.PROPERTY.ADDRESS I_F.DBS.MVMT.AGR I_F.TBS.CASHBACK.DETAILS
E.TBS.REPAY.PEN.INT I_F.DBS.MVMT.PARAM I_F.TBS.CHEQUE.BATCH
E.TBS.STAFF.SAL.SUB I_F.DBS.TNS.EXTRACT I_F.TBS.CHEQUE.CONCAT
E.TBS.STMT.COMMRSL I_F.DBS.TURN.AGR I_F.TBS.CHEQUE.DRAWEE
E.TBS.STMT.ENQ.BY.CONCAT I_F.GIT.CONVERSION I_F.TBS.CHEQUE.ISSUE
E.TBS.SUS.REJ I_F.GIT.FORMATTED.OUT I_F.TBS.CHEQUE.LOG
E.TBS.TDT.PROP.DETS I_F.GIT.FORMATTING.OUT I_F.TBS.CHEQUE.REGISTER
E.TBS.TILL.CHQ.AMT I_F.GIT.IN.KEYLIST I_F.TBS.CHEQUE.REQUEST
E.TBS.TOTAL.REDEM.AMT I_F.GIT.INTERFACE.IN I_F.TBS.CHEQUE.TYPE
E.TBS.TRF.AMT I_F.GIT.INTERFACE.OUT I_F.TBS.CONTRACTS.SUMMARY
E.TBS.UNPAID.CHG.IDS I_F.GIT.MAPPED.IN I_F.TBS.CU.CHANGE
E.TBS.UNPAID.DD I_F.GIT.MAPPED.OUT I_F.TBS.CU.CHG
E.TBS.UNPAID.DD.BR I_F.GIT.MAPPING.IN I_F.TBS.DATE.CHANGE.TAX.STATUS
E.TBS.USER.DEPT I_F.GIT.MAPPING.OUT I_F.TBS.DD.ADJUSTMENTS
E.TBS.USER.EVENT I_F.GIT.OUTPUT I_F.TBS.DDI.AUDDIS.XREF
E.TOTAL.LOCKED.AMOUNT I_F.GIT.OUTPUT.RECS I_F.TBS.DOC.STORED
E.USER.ID I_F.GIT.PROCESS.IN.DETAILS I_F.TBS.DOC.TRACK.EVENTS
E.WP.CONV.LINK.CARDS I_F.GIT.PROCESSING.DETAILS I_F.TBS.DOC.TRACKING
EB.PHANTOM.WRAPPER I_F.GIT.TABLE.UPDATE I_F.TBS.ENQUIRY.FULL.RECORD
EB.SORT.ARRAY I_F.GIT.TRANSPORT I_F.TBS.GL.PARAM
ENQ.BUILD.TDT.HIS I_F.GIT.TRANSPORT.FILE I_F.TBS.HIGHERLEND.CHARGE
FIND.LOCREF.POS I_F.GIT.TRANSPORT.FTP I_F.TBS.HL.STMT.FMT
FT.BACS.WRAPPER.EOD I_F.GIT.TRANSPORT.GENERIC I_F.TBS.IRS.UPLOAD.DET
GENENQ I_F.GIT.TRANSPORT.MQ I_F.TBS.LETTER.FORMAT
GET.INS.CUST.CLAIMS.DETAILS I_F.GIT.TRANSPORT.PRINTER I_F.TBS.MG.MATURITY.LIST
GET.INS.FIELDS I_F.GIT.TRANSPORT.RCP I_F.TBS.MG.PRODUCT
GET.INS.LATEST.RATE I_F.GIT.TRANSPORT.SOCKET I_F.TBS.MG.PRODUCT.CLASS
GET.INS.NCD.RATING I_F.GIT.XML.SCHEMA I_F.TBS.MG.STATEMENT
GET.INS.NEXT.PMT.DATE I_F.INS.ACCOUNT I_F.TBS.MG.STMT.HANDOFF
GET.INS.PC.GROUP I_F.INS.ADDNL.COVER I_F.TBS.MG.SUBSIDY
GET.INS.PC.RATING I_F.INS.ADDNL.COVER.TYPE I_F.TBS.MG.VALUATION
GET.INS.PROD.LIST I_F.INS.AREA I_F.TBS.MULTI.TELLER
GET.INS.REFERRAL.GROUP I_F.INS.CANCELLATION.REASON I_F.TBS.MULTI.TELLER.TXNS
GET.INS.VALUE.NO I_F.INS.CLAIM.TYPE I_F.TBS.NOTICE.WITHDRAWAL
GET.TBS.LATEST.RATE.ID I_F.INS.COMBINED.DISCOUNT I_F.TBS.OCCUPATION.TYPES
GET.TBS.NEXT.DATE I_F.INS.CONSTRUCTION.TYPE I_F.TBS.OVERRIDE.GROUP
GET.TBS.OVERRIDES I_F.INS.CONTRACT I_F.TBS.PASSBOOK.CONTROL
GIT.CONVERSION I_F.INS.CONTRACT.SQU I_F.TBS.POLICY.COMMISSION
GIT.CONVERT.DATA I_F.INS.COVER.TYPE I_F.TBS.POLICY.CUSTOMER
GIT.FORMATTED.OUT I_F.INS.CUST.CLAIMS.HIST I_F.TBS.POLICY.DETAILS
GIT.FORMATTING I_F.INS.CUST.PRODUCT I_F.TBS.POLICY.PARAMS
GIT.FORMATTING.OUT I_F.INS.ENDORSEMENT I_F.TBS.PRINT.MSK
GIT.IN.KEYLIST I_F.INS.EOD.LIST I_F.TBS.PROCESS.EVENT
GIT.INTERFACE.IN I_F.INS.EXCESS.AMOUNT I_F.TBS.PROD.SWITCH.DETAILS
GIT.INTERFACE.IN.RUN I_F.INS.GROUP.DISCOUNT I_F.TBS.PRODUCT.EVENT
GIT.INTERFACE.OUT I_F.INS.HOUSEHOLDER.STATUS I_F.TBS.PRODUCT.MATURITY
GIT.INTERFACE.OUT.RUN I_F.INS.IMP.ASPECTS I_F.TBS.REDEMPTION
GIT.MAPPED.IN I_F.INS.INSURANCE.TYPE I_F.TBS.REDEMPTION.SURVEY
GIT.MAPPED.OUT I_F.INS.INTR.ALARM I_F.TBS.RELATION.PROPERTIES
GIT.MAPPING.IN I_F.INS.LATE.BOOKING.DISCOUNT I_F.TBS.RETENTION
GIT.MAPPING.OUT I_F.INS.OBJECTIVES I_F.TBS.RETENTION.OPTION
GIT.OFS.DIRECT.UPDATE I_F.INS.OCCUPANCY I_F.TBS.ROLE
GIT.OUTPUT I_F.INS.OCCUPATION I_F.TBS.RUN.APPLICATION
GIT.OUTPUT.RECS I_F.INS.PARAMETER I_F.TBS.SIGNATORY
GIT.PASSWORD.ENDE I_F.INS.PAYMENT.DETAILS I_F.TBS.STANDARD.TEXT
GIT.PROCESS.BATCH.OUT.RUN I_F.INS.PERSONAL.ITEMS I_F.TBS.STMT.PARAM
GIT.PROCESS.FORMATTING.OUT I_F.INS.POST.CODE I_F.TBS.STMT.PRINT
GIT.PROCESS.IN.DETAILS I_F.INS.PRODUCT I_F.TBS.STMT.TXN.TYPE
GIT.PROCESS.MAPPING.IN I_F.INS.PROPERTY.TYPE I_F.TBS.TELLER.PARAMETER
GIT.PROCESS.MAPPING.OUT I_F.INS.PROVIDER I_F.TBS.TELLER.PASSBOOK
GIT.PROCESS.OFS.CONVERTER I_F.INS.RATE.APPLICANT.AGE I_F.TBS.TELLER.PRINTING
GIT.PROCESS.OUTPUT.OUT I_F.INS.RATE.AREA.DURATION I_F.TBS.TILL.BANKING
GIT.PROCESS.QUICK.OUT I_F.INS.RATE.BUILD.DATE I_F.TBS.TILL.BANKING.ID
GIT.PROCESS.TABLE.UPDATE I_F.INS.RATE.CONSTRUCTION.TYPE I_F.TBS.USER.CONCAT
GIT.PROCESS.THROUGH.OUT I_F.INS.RATE.ENDORSEMENT I_F.TBS.USER.PROFILE
GIT.PROCESS.WRITE.MSG I_F.INS.RATE.EXCESS I_F.TBS.WEALTH.POSITION
GIT.PROCESS.XML.IN I_F.INS.RATE.FAMILY I_F.TBS.WEALTH.POSITION.XREF
GIT.PROCESS.XML.OUT I_F.INS.RATE.HOUSEHOLDER.STATUS I_F.TBS.XML
GIT.PROCESSING.DETAILS I_F.INS.RATE.INCREASED.COVER I_FINPLAN.COMMON
GIT.TABLE.UPDATE I_F.INS.RATE.INFLATION I_GIT.COMMON
GIT.TRANSPORT I_F.INS.RATE.INTR.ALARM I_INS.ACCOUNTING
GIT.TRANSPORT.FILE I_F.INS.RATE.LENGTH.RES I_INS.CALC.PREMIUM
GIT.TRANSPORT.FTP I_F.INS.RATE.MPPI I_INS.COMMON
GIT.TRANSPORT.GENERIC I_F.INS.RATE.NCD I_INS.FILES
GIT.TRANSPORT.MQ I_F.INS.RATE.OCCUPANCY I_INS.INITIALISE
GIT.TRANSPORT.PRINTER I_F.INS.RATE.OCCUPANTS I_INS.INSERTS
GIT.TRANSPORT.RCP I_F.INS.RATE.OCCUPATION I_INS.VARIABLES
GIT.TRANSPORT.RUN I_F.INS.RATE.PC.GROUP I_TBS.ACC.DIRECT.COMMON
GIT.TRANSPORT.SOCKET I_F.INS.RATE.PERSONAL.ITEMS I_TBS.ACSTMT.COMMON
GIT.UPD.PRO.IN.DETS I_F.INS.RATE.PROPERTY.TYPE I_TBS.BACS.INWARD.VAL.COMMON
GIT.UPD.PROCESS.DETAILS I_F.INS.RATE.ROOMS I_TBS.BATCH.ONLINE.COMMON
GIT.XML.SCHEMA I_F.INS.RATE.SECURITY.TYPE I_TBS.COMMON
I_BANK.WIZARD I_F.INS.RATE.SMOKE.ALM I_TBS.CU.CHANGE.COMMON
I_BAT.DBS.DD.REG.REQ.PAYMENT.COMMON I_F.INS.RATE.SUM.INSURED I_TBS.DATA.ENQUIRY.COMMON
I_BAT.INS.DEL.QUOTE.COMMON I_F.INS.RATINGS.TYPE I_TBS.DD.ADJ.COMMON
I_BAT.INS.PREM.COLLECTION.COMMON I_F.INS.REFERRAL.GROUP I_TBS.DOC.TRACKING.COMMON
I_BAT.MT.LIVE.TO.HIS.COMMON I_F.INS.REFERRAL.TYPE I_TBS.MG.COMMON
I_BAT.TBS.AC.SUBS.COMMON I_F.INS.SECURITY.TYPE I_TBS.MG.EOD.RATE.CHNG.COMMON
I_BAT.TBS.CHANGE.TAX.STATUS.COMMON I_F.INS.SMOKE.ALARM I_TBS.MG.EOD.RATE.LETTER.COMMON
I_BAT.TBS.FINAL.LETTER.COMMON I_F.INS.TYPE.LEVEL I_TBS.MGSTMT.COMMON
I_BAT.TBS.LOCKED.EVENT.COMMON I_F.TBS.AB.RN.CONTROL I_TBS.PRINT.STMT
I_BAT.TBS.MG.APPL.NEWRATE.COMMON I_F.TBS.AC.CHANGE I_TBS.PURGE.POLICY.COMMON
I_BAT.TBS.MG.PREFPAY.PAYMENT.COMMON I_F.TBS.AC.EVENT.LIST I_TBS.STMT.PRN.COMMON
I_BAT.TBS.MG.RETN.PREP.COMMON I_F.TBS.AC.PARAMETER I_TBS.SUBS.LETTER.COMMON
I_BAT.TBS.MG.SWITCH.PRODUCT.COMMON I_F.TBS.AC.PRODUCT I_TBS.TAX.ADV.COMMON
I_BAT.TBS.PROD.EVENT.COMMON I_F.TBS.AC.SUBSCRIPTION I_TBS.TAX.RC.COMMON
I_BAT.TBS.PRODUCT.LETTER.2.COMMON I_F.TBS.ACCOUNT.PASSBOOK I_TBS.TNS.REFRESH.COMMON
I_BAT.TBS.PRODUCT.LETTER.3.COMMON I_F.TBS.ACCT.STATEMENT I.DEEDCARE.INS
I_BROWSER.TAGS I_F.TBS.AGENCY.BATCHING I.GET.USER.ADL
I_DBS.MVMT.EOD.COMMON I_F.TBS.APPLICATION.DEFAULT I.INS.COVER.TYPE
I_DD.DATE.CHECK I_F.TBS.BACS.CONSTANTS I.INS.GET.ENDOW.POLICY
I.LAST.PBOOK.DETAIL O.TBS.BANK.WIZARD.VAL TBS.DD.ADJUSTMENTS

I.TBS.AC.CLOSURE.CHARGE O.TBS.CONF.VAL.DATE TBS.DD.CUSTOMER.CHANGE
I.TBS.AC.CREDIT.FREQ POPULATE.FILE TBS.DD.OUTFORMAT
I.TBS.AC.DEBIT.FREQ POST.TBS.DD.ADJUSTMENTS.EOD TBS.DD.OUTFORMAT1
I.TBS.AC.PROD.RATES STIN.PROG TBS.DD.SAVEDLIST
I.TBS.AC.TAX.STATUS T.MREAD TBS.DDI.AUDDIS.XREF
I.TBS.CALC.INT.PENALTY T.READ TBS.DDI.AUDDIS.XREF.FIELD.DEF
I.TBS.CHARGE.GT.AC.BAL TBS.AC.CHANGE TBS.DDI.AUDDIS.XREF.HIST
I.TBS.DDI.MGPAYMENT TBS.AC.CUSTOMER.CHANGE TBS.DDI.CONCAT
I.TBS.EXT.BNK.DETS TBS.AC.EVENT.LIST TBS.DEACTIVE.USER.PROFILE
I.TBS.GET.CUST.NAME TBS.AC.INWARD.FILE TBS.DECEASED.CUST
I.TBS.GET.MT.RCT.AMOUNT TBS.AC.PARAMETER TBS.DEFAULT.BRANCH
I.TBS.GET.PRD.TRF.TO TBS.AC.PRODUCT TBS.DEFAULT.MGSETTLE.DETS
I.TBS.GET.TDT.FIELD TBS.AC.SUBSCRIPTION TBS.DEFAULT.TODAY
I.TBS.GET.TRUST.CHILD TBS.AC.TAX.FOR.PERIOD TBS.DICT.XML.TRANSFORM
I.TBS.HL.MG.INS.PAYM TBS.ACCOUNT.PASSBOOK TBS.DL.ACCOUNT
I.TBS.INS.VAL.COVER TBS.ACCOUNTING.ROUTINE TBS.DL.BLANK
I.TBS.MAT.ACCOUNTS TBS.ACCOUNTING.ROUTINE.AUTH TBS.DL.CORE
I.TBS.MG.CUST.REPAY.AMT TBS.ACCT.INT.TAX TBS.DL.CORE2
I.TBS.MG.INS.REPAY.AMT TBS.ACCT.STATEMENT TBS.DL.DAO
I.TBS.MG.INS.TYPE.AMT TBS.ACP.FIELD.DEFS TBS.DL.DD
I.TBS.POA.CUSTOMER TBS.ACSTMT TBS.DL.EVENTTRACK
I.TBS.PROD.MAT.INSTR TBS.ACSTMT.DETAILS TBS.DL.FINSERVTRACK
I.TBS.TILL.B.VAL TBS.ACSTMT.LOAD TBS.DL.INSPROD
I.TOT.CUST.REPAY TBS.ACSTMT.ONLINE TBS.DL.MORTGAGE
I.XML.CASHBACK TBS.ACSTMT.POST TBS.DL.TELLER
I.XML.HLC.DETAILS TBS.ACSTMT.SELECT TBS.DM.ACCOUNT
I.XML.HLC.REBATE TBS.AEGON.CALC.SUBSIDY TBS.DOC.ENQUIRY.OUTPUTS
I.XML.INS.PI.DETAILS TBS.AGENCY.BATCHING TBS.DOC.RAISE.EVENT
I.XML.INS.PREM.DETAILS TBS.AGENCY.BATCHING.FIELD.DEFINITIONS TBS.DOC.STORED
I.XML.STANDARD.TEXT TBS.ALLOCATE.UNIQUE.ID TBS.DOC.TRACK.CHARGE
I.XML.SWITCH.PROD.TO TBS.ANNUAL.TAX TBS.DOC.TRACK.EVENTS
I.XML.VAL.DETAILS TBS.APPLICATION.DEFAULT TBS.DOC.TRACK.EVENTS.CHK.FLDS
INS.ACCOUNT TBS.BACS.ACCOUNT.VAL TBS.DOC.TRACK.EVENTS.CROSSVAL
INS.ADDNL.COVER TBS.BACS.COMMON.LOAD TBS.DOC.TRACKING
INS.ADDNL.COVER.TYPE TBS.BACS.CONSTANTS TBS.DOC.TRACKING.CROSSVAL
INS.AREA TBS.BACS.CONSTANTS.CHECK.FIELDS TBS.DOC.TRACKING.CUST.XREF
INS.CANCELLATION.REASON TBS.BACS.CONSTANTS.CROSSVAL TBS.DOC.TRACKING.EOD
INS.CLAIM.TYPE TBS.BACS.CONSTANTS.FIELD.DEF TBS.DOC.TRCK.CU.CHANGE
INS.COMBINED.DISCOUNT TBS.BACS.DD.RETURNS TBS.DYN2OFS
INS.CONSTRUCTION.TYPE TBS.BACS.INWARD.FILE TBS.E.AC.INT.TAX
INS.CONTRACT TBS.BACS.INWARD.VAL TBS.E.ACCOUNT.STATEMENT
INS.CONTRACT.SQU TBS.BACS.LOAD.RTN TBS.E.AEGON.FEE
INS.COVER.TYPE TBS.BACS.SUSP.REASON.LOAD TBS.E.AGR.DETAILS
INS.CUST.CLAIMS.HIST TBS.BACS.VAL.ACCT.7 TBS.E.AGRESSO.LINK
INS.CUST.PRODUCT TBS.BACS.VAL.TXN.CODE TBS.E.BRKR.STMT
INS.ENDORSEMENT TBS.BANK.DATE TBS.E.BRKR.STMT.XML
INS.EOD.ERROR.HANDLING TBS.BANK.WIZARD.CODES TBS.E.BUILD.AC.TAX
INS.EOD.LIST TBS.BRANCH.BANKING TBS.E.BUILD.CUSACC.CNT
INS.EXCESS.AMOUNT TBS.BRANCH.TELLER TBS.E.BUILD.FORMAT.ID
INS.GROUP.DISCOUNT TBS.BRKR.STMT.RUN TBS.E.BUILD.INT.RECORD
INS.HOUSEHOLDER.STATUS TBS.BRKR.STMT.XML.HDR TBS.E.CCHG.ACLIST
INS.IMP.ASPECTS TBS.BW.FIELD.DEFINITIONS TBS.E.CONV.TO.XML
INS.INSURANCE.TYPE TBS.BWE TBS.E.DOC.CUS.DETAILS
INS.INTR.ALARM TBS.CALC.INTEREST TBS.E.GET.ARREARS
INS.LATE.BOOKING.DISCOUNT TBS.CALC.MNTH.YR TBS.E.GET.FULL.RECORD
INS.NOTIFY.FXC.CUST.CREATION TBS.CARD.IMAGE10 TBS.E.GET.INS.MONTHLY.PREM
INS.OBJECTIVES TBS.CARD.IMAGE12 TBS.E.GET.INS.PREMIUM
INS.OCCUPANCY TBS.CARD.IMAGE13 TBS.E.GET.INT.RATE.12M
INS.OCCUPATION TBS.CARD.IMAGE14 TBS.E.GET.MONTHLY.LD.PAY
INS.PARAMETER TBS.CARD.IMAGE15 TBS.E.GET.NOTIFY.TEXT
INS.PAYMENT.DETAILS TBS.CARD.IMAGE30 TBS.E.HL.STMT.OUTPUT
INS.PERSONAL.ITEMS TBS.CARD.IMAGE32 TBS.E.REVERSE.ENTRY
INS.POST.CODE TBS.CARD.IMAGE33 TBS.E.WP.CCH
INS.PROCESS.ENQUIRY TBS.CARD.ISSUE TBS.ENQ.CDD.MONTHS
INS.PRODUCT TBS.CARD.REQUEST TBS.ENQ.CUS.DATA
INS.PROPERTY.TYPE TBS.CASHBACK.DETAILS TBS.ENQUIRY.FULL.RECORD
INS.PROVIDER TBS.CASHBACK.DETAILS.CHK.FLDS TBS.EOD.CU.CHANGE
INS.RATE.APPLICANT.AGE TBS.CASHBACK.DETAILS.FIELD.DEF TBS.EOD.CU.CHANGE.LOAD
INS.RATE.AREA.DURATION TBS.CHANGE.SIZE TBS.EOD.CU.CHANGE.ONLINE
INS.RATE.BUILD.DATE TBS.CHECK.REL.PROPERTIES TBS.EOD.CU.CHANGE.SELECT
INS.RATE.CONSTRUCTION.TYPE TBS.CHEQUE.BATCH TBS.EOD.ERROR.HANDLING
INS.RATE.ENDORSEMENT TBS.CHEQUE.BATCH.RUN TBS.EOD.FILE.TIDY.UP
INS.RATE.EXCESS TBS.CHEQUE.CONCAT TBS.EOD.PHANTOM.START
INS.RATE.FAMILY TBS.CHEQUE.DRAWEE TBS.EOD.PHANTOM.STOP
INS.RATE.HOUSEHOLDER.STATUS TBS.CHEQUE.ISSUE TBS.EOD.RE.STAT.PRINT
INS.RATE.INCREASED.COVER TBS.CHEQUE.LOG TBS.FINPLAN
INS.RATE.INFLATION TBS.CHEQUE.REGISTER TBS.FINPLAN.LOAD
INS.RATE.INTR.ALARM TBS.CHEQUE.REQUEST TBS.FINPLAN.ONLINE
INS.RATE.LENGTH.RES TBS.CHG.ID TBS.FINPLAN.POST
INS.RATE.MPPI TBS.CHK.CHEQUE.REQUEST TBS.FINPLAN.SELECT
INS.RATE.NCD TBS.CHK.DIGIT TBS.FORMAT.ENQ.DATA
INS.RATE.OCCUPANCY TBS.CLEARFILE.LIST TBS.FT.BACS.OUT.MAPPING
INS.RATE.OCCUPANTS TBS.CLOSESTMT TBS.FT.BC.ROUTING
INS.RATE.OCCUPATION TBS.CLOSESTMT.DETAILS TBS.GEN.AUDDIS.FILE
INS.RATE.PC.GROUP TBS.CLOSESTMT.LOAD TBS.GET.AC.BALANCES
INS.RATE.PERSONAL.ITEMS TBS.CLOSESTMT.SELECT TBS.GET.AC.DETAILS
INS.RATE.PROPERTY.TYPE TBS.CNV.PROPER.CASE TBS.GET.AC.STMT.DETAILS
INS.RATE.ROOMS TBS.COB.MONITOR TBS.GET.AC.TAX.DETAILS
INS.RATE.SECURITY.TYPE TBS.COMPILE TBS.GET.BANKING.DETAILS
INS.RATE.SMOKE.ALM TBS.CONT.SUM.FIELD.DEF TBS.GET.BUILD.INSPREM
INS.RATE.SUM.INSURED TBS.CONTRACTS.SUMMARY TBS.GET.CCY.LIST
INS.RATINGS.TYPE TBS.CONVERSION.ROUTINE TBS.GET.CHEQUE.NO
INS.REFERRAL.GROUP TBS.CONVERSION.ROUTINE.1026 TBS.GET.CONT.INSPREM
INS.REFERRAL.TYPE TBS.CR.GBREF TBS.GET.CORR.CUS.TITLES
INS.SECURITY.TYPE TBS.CRED.SAVING.ACCT TBS.GET.CORR.CUSTS
INS.SMOKE.ALARM TBS.CREDIT.DATE.CHK TBS.GET.CORRESPONDENCE.CUS
INS.TRANSLATE.ERROR.MESSAGE TBS.CU.CHANGE TBS.GET.CORRESPONDENCE.CUSTOMERS
INS.TYPE.LEVEL TBS.CU.CHANGE.UPDATE TBS.GET.CUST.ADD.INFO
IO.ANALYSIS TBS.CU.CHG TBS.GET.CUST.ADDRESS
KEYDATAIN.PROG TBS.CU.CHG.FIELD.DEF TBS.GET.DDI.LIST
LOAD.INS.DATA TBS.CUS.DET.EXTRACT TBS.GET.INT.ONLY.PRIN
LOAD.INS.MPPI.CLAIMS TBS.CUSTOMER.CONTRACTS TBS.GET.JOINT.CUS.NAMES
MBNAIN.PROG TBS.DATE.CHANGE.TAX.STATUS TBS.GET.LR.POS
MPSIN.PROG TBS.DATE.FIRST.SUB TBS.GET.MATURING.PROD
MPSOUT.PROG TBS.DAY.FQU TBS.GET.MEMBER.ACCOUNTS
TBS.GET.MG.DETAILS TBS.PBOOK.DETAILS TBS.WORKLIST.TASK

TBS.GET.MPPI.INSPREM TBS.PL.MOVE.TO.AL TBS.XLDT
TBS.GET.PRODUCT.DETAILS TBS.PMSK.CHECK.FIELDS TBS.XML
TBS.GET.TPE.NEW.ACCOUNT TBS.POLICY.COMMISSION TBS.XML.GET.BOW.DESC
TBS.GET.TRAV.INSPREM TBS.POLICY.COMMISSION.AUTH TBS.XML.GET.INT.RATE
TBS.GET.USER.OFFICE TBS.POLICY.COMMISSION.CROSSVAL TBS.XML.GET.TAX.DESCRIPTION
TBS.GIT.AEGON.EXTRACT TBS.POLICY.COMMISSION.FIELD.DEFS TBS.XML.ITEM
TBS.GIT.CALC.GROSS.CUS TBS.POLICY.COMMISSION.FIELDVAL TBS.XML.MGSTMT
TBS.GIT.CALC.PAY.AEGON TBS.POLICY.COMMISSION.REV TBS.XML.MGSTMT.LOAD
TBS.GIT.CONV.DATE TBS.POLICY.CUSTOMER TBS.XML.MGSTMT.POST
TBS.GIT.FMT.AMT TBS.POLICY.DETAILS TBS.XML.MGSTMT.SELECT
TBS.GIT.FOOT.TOT TBS.POLICY.DETAILS.FIELD.DEFS TBS.XML.RESSTMT
TBS.GIT.FOOT.TOT.PAY TBS.POLICY.PARAMS TBS.XML.RESSTMT.LOAD
TBS.GIT.FOOT.TOT.RECS TBS.POLICY.PARAMS.FIELD.DEFS TBS.XML.RESSTMT.POST
TBS.GIT.FOOT.TOT.SUB TBS.POLICY.PARAMS.FIELDVAL TBS.XML.RESSTMT.SELECT
TBS.GIT.HEAD.CLEAR TBS.PRE.GIT.EOD TEST.CALLJ
TBS.GIT.MG.ACCOUNT TBS.PREF.MG.PAY.AMT TFCIN.PROG
TBS.GIT.OUT.INTF.EOD TBS.PREF.MG.TERM TPSIN.PROG
TBS.GIT.OUT.TOTAL.RTN TBS.PRINT.MSK TPSOUT.PROG
TBS.GIT.PRE.CALC.SUBSIDY TBS.PRINT.STMT.LOAD UPD.INS.PAYMENT.DETAILS
TBS.GL.PARAM TBS.PRINT.STMT.ONLINE UPDATE.TBS.ACCOUNT.FILES
TBS.GL.PARAM.FIELD.DEF TBS.PRINT.STMT.SELECT UPDATE.TBS.APPLICATION.DEFAULT
TBS.HIGHERLEND.CHARGE TBS.PROCESS.ENQUIRY UPDATE.TBS.BANK.WIZARD
TBS.HIGHERLEND.CHARGE.CHK.FLDS TBS.PROCESS.EVENT UPDATE.TBS.CHARGE.REQUEST
TBS.HIGHERLEND.CHARGE.CROSSVAL TBS.PROD.SWITCH.DETAILS UPDATE.TBS.CUSTOMER.CONTRACTS
TBS.HIGHERLEND.CHARGE.FIELD.DEF TBS.PRODUCT.EVENT V.AC.MT.PAYEE.NAME
TBS.HL.STMT.FMT TBS.PURGE.POLICY.COMM V.ACPM.VALIDATE.DBS
TBS.HL.STMT.FMT.CHECK.FIELDS TBS.PURGE.POLICY.COMM.LOAD V.ANOTHER.MORT.MAND
TBS.HL.STMT.FMT.CROSSVAL TBS.PURGE.POLICY.COMM.SELECT V.CHECK.SOLICITOR
TBS.HL.STMT.FMT.FIELD.DEFINITIONS TBS.RAISE.CATALOG.EVENT V.CHECK.TBS.ACCOUNT
TBS.HL.STMT.SS.LOAD TBS.RAISE.EVENT V.CHECK.TBS.CAPITAL.DATE
TBS.I.GET.CUS.AGE TBS.RANGE.CLEAR V.CHECK.TBS.PRODUCT.TRANSFER
TBS.I.GET.PHONE.NO TBS.RE.STAT.PRINT V.CHK.REC.DEF.CUS
TBS.IDESK.STE.CNT TBS.READ V.DBS.DC.SUPP.CONTRACT
TBS.IN2ACC TBS.REDEMPTION.SURVEY V.DBS.DD.REQ.AUTH
TBS.IND.CHK.REC TBS.RELATION.PROPERTIES V.DBS.DEF.NUM.SIGNS
TBS.INS.CON.FEE TBS.REPAY.TYPE.ENRI V.DBS.DEF.VAL.INP
TBS.INS.CUSTOMER.CHANGE TBS.RETENTION V.DBS.MG.AUTH.REV
TBS.IRS.UPLOAD.DET TBS.RETENTION.OPTION V.DBS.NREDEM.OVERRIDE
TBS.IRS.UPLOAD.PH TBS.RETENTION.OPTION.AFTER.AUTH.WRITE V.DBS.VAL.MG.LOC.REF
TBS.ISA.POST.RESTRICT TBS.RETENTION.OPTION.CROSSVAL V.DD.DDI.CHECK.REC.RTN
TBS.LAST.AC.ENTRIES TBS.RETENTION.OPTION.FIELD.DEFINITIONS V.DEF.TBS.CAPITAL.DATE
TBS.LETTER.FORMAT TBS.REVERSE.BONUS.INT V.DEF.TBS.PROCESSING.DATE
TBS.LINKSTMT TBS.ROLE V.DEFAULT.TODAY
TBS.LINKSTMT.DETAILS TBS.ROLE.FIELD.DEF V.GEN.TBS.CARD.ISSUE.NO
TBS.LINKSTMT.LOAD TBS.RUN.APPLICATION V.INP.INS.PEND.EVENT
TBS.LINKSTMT.POST TBS.SIGNATORY V.INP.SOLICITOR
TBS.LINKSTMT.SELECT TBS.STANDARD.TEXT V.INS.AUTH.ROUTINE
TBS.LOCAL.PRINT TBS.STANDARD.TEXT.CHK.FLDS V.INS.INP.ROUTINE
TBS.MATREAD TBS.STANDARD.TEXT.FIELD.DEF V.MG.ACSTMT.UPDATE
TBS.MG.BASIC.INT.DESC TBS.STMT.PARAM V.MG.ARRS.PRIN.INC
TBS.MG.BUILD.MGSTMT TBS.STMT.PRINT V.OFSMG
TBS.MG.BUILD.MGSTMT.LOAD TBS.STMT.PRINT.RUN V.PRINT.MASK.DBS
TBS.MG.BUILD.MGSTMT.POST TBS.STMT.PRN V.RETAIN.ADD.MAND
TBS.MG.BUILD.MGSTMT.SELECT TBS.STMT.PRN.LOAD V.TBS.AC.AMEND.FORM.AUTH
TBS.MG.CALCULATE.INTEREST TBS.STMT.PRN.POST V.TBS.AC.APPLIC.FORM
TBS.MG.CALCULATE.PENALTIES TBS.STMT.PRN.SELECT V.TBS.AC.AUTH
TBS.MG.CALCULATE.PENALTY.DAYS TBS.STMT.TXN.TYPE V.TBS.AC.CHG.RQ.AUTH
TBS.MG.CHECK.CONNECTED.CONTRACTS TBS.STO.BC.ROUTING V.TBS.AC.CLS.AUTH
TBS.MG.CHECK.CURRENT.CONTRACTS TBS.STO.CUSTOMER.CHANGE V.TBS.AC.CNG.AUTH
TBS.MG.CUSTOMER.CHANGE TBS.STO.FAILURE.CHG V.TBS.AC.CU.CHANGE
TBS.MG.DEF.TERM.PRIORITY TBS.STO.INT.TAX V.TBS.AC.DATE.CHK
TBS.MG.DEFINE.SOURCE TBS.STO.PPI.PAY.SELECT V.TBS.AC.INP
TBS.MG.EOD.RATE.CHANGE.LETTER TBS.STT.FIELD.DEFINITIONS V.TBS.AC.IPM.AUTH
TBS.MG.EOD.RATE.CHANGE.LETTER.LOAD TBS.TAX.ADV V.TBS.AC.LCK.AUTH
TBS.MG.EOD.RATE.CHANGE.LETTER.SELECT TBS.TAX.ADV.LOAD V.TBS.AC.SWITCH.CLOSE
TBS.MG.EOD.RATE.LETTER.POST TBS.TAX.ADV.POST V.TBS.AC.UPDATE
TBS.MG.GET.MONTHLY.PAYMENT TBS.TAX.ADV.SELECT V.TBS.ACC.CA.UPDATE
TBS.MG.GET.OUTSTANDING.BALANCE TBS.TAX.RECALC V.TBS.ACCOUNT.VAL
TBS.MG.MATURITY.LIST TBS.TDTE.REDEMPTION V.TBS.ACCTGC.DEF
TBS.MG.NEW.INT.AEGON.SUBS TBS.TELLER.ENQ.GET.ACCTS V.TBS.ACCTGC.ID
TBS.MG.NEW.INT.RATE TBS.TELLER.PARAMETER V.TBS.ACL.AUTH
TBS.MG.NEW.INT.REPAY.AMT TBS.TELLER.PASSBOOK V.TBS.AGC.DEF
TBS.MG.PROD.DESC TBS.TELLER.PASSBOOK.PRINT V.TBS.AGENCY.BATCHING.AUTH
TBS.MG.PRODUCT TBS.TELLER.PRINTING V.TBS.ALE.AUTH
TBS.MG.PRODUCT.CHECK.FIELDS TBS.TEMP.ACCT.RESET V.TBS.ALE.INP
TBS.MG.PRODUCT.CLASS.FIELD.DEF TBS.TILL.BANKING V.TBS.AUTH.CREATE.DD.ADJ
TBS.MG.PRODUCT.CLASS.X TBS.TILL.BANKING.ID V.TBS.BACS.CUTOFF.VAL
TBS.MG.PRODUCT.CROSSVAL TBS.TNS.FILE.UPDATE V.TBS.BI.STO.AMT
TBS.MG.PRODUCT.FIELD.DEFINITIONS TBS.TNS.REFRESH V.TBS.BORROWER.DOWNDATE
TBS.MG.STATEMENT TBS.TNS.REFRESH.LOAD V.TBS.BORROWER.UPDATE
TBS.MG.STMT TBS.TNS.REFRESH.SELECT V.TBS.BROKER.CHK.REC
TBS.MG.STMT.HANDOFF TBS.TNS.REFRESH.SELECT.FULL V.TBS.BROKER.VERSION
TBS.MG.STMT.LOAD TBS.TNS.REFRESH.SELECT.PART V.TBS.CA.UPDATE
TBS.MG.STMT.SELECT TBS.TOT.MG.ERC.HLSTM V.TBS.CALC.BROKER.FEES
TBS.MG.SUBS.CROSSVAL TBS.TOT.MG.PAYMENT V.TBS.CARD.ISS.AUTH
TBS.MG.SUBSIDY TBS.TOT.MG.PREF.PAYMENT V.TBS.CARD.ISS.INP
TBS.MG.SUBSIDY.FIELD.DEFINITIONS TBS.TRANS.FLD.NAME V.TBS.CHECK.JOINT.CUS
TBS.MG.TOT.NEW.INT.REPAY.AMT TBS.TRANS.OVE.ERR.MSG V.TBS.CHECK.TAX.FORM
TBS.MG.VALIDATE.CHG.FIELDS TBS.TRANSLATE.ERROR.MESSAGE V.TBS.CLEAR.FLDS
TBS.MG.VALUATION TBS.UNIQUE.LETTER.ID V.TBS.CREATE.BROWSER.PREFERENCES
TBS.MG.VALUATION.FIELD.DEFINITIONS TBS.UP.FIELD.DEFINITIONS V.TBS.CREATE.LETTERS
TBS.MGSTMT.ONLINE TBS.UPD.CHEQUE.REQUEST V.TBS.CU.AMEND.FORM.AUTH
TBS.MT.AGENCY.BATCHING.CROSSVAL TBS.UPD.SORT.CODE.INFO V.TBS.CU.AUTH
TBS.MULTI.TELLER TBS.UPDATE.CONTACT.LOG V.TBS.CU.INP
TBS.MULTI.TELLER.TXNS TBS.USER.CONCAT V.TBS.CU.NULL.LRF
TBS.MULTIVALUE.FILTER TBS.USER.PROFILE V.TBS.CU.UPDATE.NAME
TBS.NOTICE.WITHDRAWAL TBS.V.DEFAULT.VALUE.DATE V.TBS.CURR.SUBS
TBS.NOTICE.WITHDRAWAL.CANCEL TBS.V.INIT.IDESK V.TBS.DC.INP
TBS.OCCUPATION.TYPES TBS.V.MG.PAYMENT V.TBS.DD.AFTER.UNAU
TBS.OCCUPATION.TYPES.FIELD.DEF TBS.V.STO.DEF.CUST V.TBS.DD.AUTH
TBS.OFS.IN.RTN TBS.VAL.BACS.ACCT V.TBS.DD.AUTH.RTN
TBS.OFS.LR.NAME2NO TBS.VALIDATE.DDI V.TBS.DD.BANK.WIZARD
TBS.OPF TBS.VV.FT.OC V.TBS.DD.CNG.AUTH
TBS.OVERRIDE.GROUP TBS.WEALTH.POSITION V.TBS.DD.COMMON.CHECK.REC.RTN
TBS.PASSBOOK.CONTROL TBS.WEALTH.POSITION.XREF V.TBS.DD.CROSS.VAL
V.TBS.DD.DDI.ACCT.DFLT V.TBS.ISA.ELIGIBLE.ACC V.TBS.PASSBOOK.FULL

V.TBS.DD.DIRECTION V.TBS.ISA.NI.NUMBER V.TBS.PLFT.DEFLT
V.TBS.DD.INP V.TBS.ISA.XFER.AUTH V.TBS.RECIPIENT.FREQU
V.TBS.DD.RETURN.AUTH V.TBS.JOINT.CUS.DATE V.TBS.RED.REQ.FEE
V.TBS.DDI.AUTH.RTN V.TBS.MG.CATEG.DEF V.TBS.STO.AMEND.FORM.AUTH
V.TBS.DEATH.STATUS V.TBS.MG.CHECK.MAT.DATE V.TBS.STO.AUTH
V.TBS.DECIDE.DD.PARAM V.TBS.MG.CNG.AUTH V.TBS.STO.BANK.WIZARD
V.TBS.DEF.AC.CORR.CUST V.TBS.MG.CONSN.ADD V.TBS.STO.BEN.ACCT.NO
V.TBS.DEF.CHARGE.CCY V.TBS.MG.CONSN.CANCEL V.TBS.STO.CNG.AUTH
V.TBS.DEF.CUST.FROM.ACCT V.TBS.MG.DWP.AUT.RTN V.TBS.STO.DEF
V.TBS.DEF.DAO V.TBS.MG.DWP.CHK.FLDS V.TBS.TACP.CHECK.ISA
V.TBS.DEF.DATE V.TBS.MG.DWP.CHK.REC V.TBS.TACP.CHECK.NON.ISA
V.TBS.DEF.TIME V.TBS.MG.ID.CHK V.TBS.TDT.DEF.PROP
V.TBS.DEFAULT.TILL.TRANSFER V.TBS.MG.INP V.TBS.TDT.END.INP
V.TBS.DFLT.DDI.REFERENCE V.TBS.MG.MINPAY.PENALTY V.TBS.TDT.ISA.EFF.DATE
V.TBS.DFLT.REPAY.AMT V.TBS.MG.MPPI.AUTH.RTN V.TBS.TDT.LREF.DEF
V.TBS.DISP.ERR V.TBS.MG.MPPI.CHK.FLDS V.TBS.TDT.MG.DEF
V.TBS.DTC.CNG.AUTH V.TBS.MG.NEW.TERM V.TBS.TDT.MG.PEN
V.TBS.ERR.NOM.DR.BAL V.TBS.MG.NULL.LRF V.TBS.TPE.DEFAULT
V.TBS.FIN.INST.ADDRESS V.TBS.MG.PAY.CONFIRMATION V.TBS.TPE.MAND.OFF
V.TBS.FT.AC.AUTH V.TBS.MG.PAY.DATE.DEFAULTS V.TBS.UPD.ISA.STATUS
V.TBS.FT.ACCT.INP V.TBS.MG.PAY.DUPLICATE V.TBS.UPD.POST.REST
V.TBS.FT.ACL.AUTH V.TBS.MG.PAY.INPUT V.TBS.UPDATE.AC.LOCKS
V.TBS.FT.AUT.LETTER V.TBS.MG.PAY.PENALTY V.TBS.UPDATE.AUDDIS.XREF
V.TBS.FT.AUTH V.TBS.MG.PAY.UPD.PAY.ACCOUNT V.TBS.UPDATE.MG
V.TBS.FT.BANK.WIZARD V.TBS.MG.PEN.AUTH V.TBS.UPDATE.USER.PROFILE
V.TBS.FT.DEF.BENACC V.TBS.MG.PREFPAY.XVAL V.TBS.USER.AUTH.RTN
V.TBS.FT.DEFA.RECIPIENT.DT V.TBS.MG.REDEM.LIST V.TBS.USER.CHK.FLDS
V.TBS.FT.GET.MG.ID V.TBS.MG.RETENTION V.TBS.VAL.FREQUENCY
V.TBS.FT.INP V.TBS.MG.VAL.CONSN V.TBS.VAL.PROD
V.TBS.FT.ISA.AUTH V.TBS.MG.VAL.CONTRACT V.TRO.AUTH.RTN
V.TBS.FT.MG.PAYMENT V.TBS.MG.VAL.PREFPAY V.TRO.PGA
V.TBS.FT.NOM.DEF V.TBS.MGPAY.CHK.NONREDEM V.TT.IDSET
V.TBS.FT.REASON.AUTH V.TBS.MGPAY.NONREDEM.ERR V.UPDATE.USER.PROFILE.RUN
V.TBS.FT.RECIPIENT.DT V.TBS.MGPAY.TERM.PRIORITY.DEF VAL.INS.BANK.WIZARD
V.TBS.FT.RJ.AUTH V.TBS.MGPAY.TERM.PRIORITY.N VAL.INS.DATE
V.TBS.FT.RJ.CHG V.TBS.MGPAY.TERM.PRIORITY.VAL VAL.INS.POST.CODE
V.TBS.FT.RJ.DEF V.TBS.MGPAY.TERM.PRIORITY.Y VAL.INS.PRODUCT.ID
V.TBS.FT.RJ.INP V.TBS.MGSTMT.UPDATE VAL.INS.RANGE
V.TBS.ID.TELLER.RTN V.TBS.MT.AB.AFTER.UNAU VAL.TBS.TELLER.PASSWORD
V.TBS.INS.CNG.AUTH V.TBS.MT.ISA.AUTH VAL.TBS.UNBANKED.CHEQUES
V.TBS.INVESTOR.DOWNDATE V.TBS.NOMINATED.ACCT.VAL
V.TBS.INVESTOR.UPDATE V.TBS.NW.CLOSURE.AUTH
V.TBS.ISA.AC.AUTH V.TBS.OVERRIDE.MSG
Testing
167. This is an area where I’ll get involved a little more in detail now. Testing is a separate
discipline from software design and development, so I will not turn this due diligence booklet
into a testing manual. However I will point out some things that you need to know about testing
as it relates to T24 and give you some pointers and warnings in this respect.
Ask about testing before you sign up and get involved in a contract to implement T24. T24 is
HARD TO TEST. Remember that. Why? Well here are some more questions to ask?
a. Get a list of non Temenos vendors who test T24 - do a test requirements document first
however (this is similar to a business requirements document - a sample of one is shown
below which is a proposal that was submitted to a client in response to a set of T24
testing requirements--the price for testing was over $300,000 USD)
Temenos-Cognizant Proposal
For
Libyan Qatari Bank (LQB)
T24 Testing
Version 1.4
19th August 2010
Cognizant Technology Solutions Overseas Corporation (Dubai Branch)
Office No. 901 | 9th Floor | Al Thuraya Tower No.2 | P.O.Box 500378
Dubai Internet City | Dubai | U.A.E.
Tel: +9714-4347607 | Fax: +9714-4290325
www.cognizant.com
(A Fortune 1000 Company)
Table of contents
1 Executive Summary 3
1.1 Proposal Background 3
1.2 Cognizant Solution 3
1.3 Value Proposition 3
1.4 Commercials 4
2 Our Understanding 5
2.1 In Scope 5
2.2 Out of Scope 7
3 Cognizant Solution 8
3.1 Phase 1 8
3.2 Phase 2 9
3.2.1 Run MVC – System Testing 9
3.2.2 Interface Integration Testing 10
3.2.3 User Acceptance Testing (UAT) 11
3.3 Indicative Schedule 12
4 Commercials 13
4.1 Terms and Conditions 13
5 Response to ‘Requirements from Bidders’ 14
5.1 Company Profile 14
5.2 Registered Address 15
5.3 Roles and Responsibilities 16
5.3.1 Cognizant roles and responsibilities 16
5.3.2 Expected roles and responsibilities from Client 17
5.4 T24 Test Methodology 18
5.5 Defect Management 18
5.6 Governance and Communication 19
5.7 Prerequisites 20
5.8 Testing Tools 21
6 Project Management Approach 22
6.1 Project Management 22
6.2 Change Management Procedure 22
7 Assumptions and Dependencies 24
7.1 Assumptions 24
7.2 Dependencies 24
8 Case Studies 26
8.1 Cases Study – I 26
8.2 Case Study -II 26
9 Annexure 28
9.1 About Cognizant 28
9.2 Cognizant BFS Competency 28
9.3 Cognizant Centre of Excellence for T24 30
9.4 Cognizant Testing Offerings 30
9.5 Cognizant T24 Testing Methodology 32
9.5.1 Test Analysis 32
9.5.2 Test Design 33
9.5.3 Test Script Development 34
9.5.4 Test Execution 35
9.5.5 System Integration Testing 36
9.5.6 User Acceptance Testing 37
9.6 Cognizant as SI 38
9.7 Value adds from partnerships 39
9.7.1 Cognizant TEMENOS Partnership 39
9.7.2 Cognizant Validata Partnership 39
9.8 Cognizant Managed Verification Centre 39
Executive Summary
Proposal Background
A new bank, Libyan Qatari Bank (LQB), is being launched in the Middle East. As part of the launch process, the bank wishes to implement T24,
R10 model bank as its core banking system. The core banking system is supplied by TEMENOS.
The bank, a pure “Greenfield” operation, is proposed to function as a universal bank with retail, SME, corporate, treasury and investment
services and a branch and ATM network covering all of the major urban centres.
LQB is interested in outsourcing the testing (system testing, interface testing and UAT) of this implementation. The assignment would involve the
execution of detailed system and interface test scripts as defined in scope on the scoped environments.
This proposal is submitted under the assumption that upon the successful outcome of the bid Temenos will be the prime contractor to LQB and
Cognizant will be its sub-contractor for the proposed scope and services.
Cognizant Solution
Cognizant has participated in large core banking testing programs with other customers, and has a clear understanding of the complexities and
challenges, and has evolved a well-documented set of lessons learnt from its previous engagements.
Cognizant’s strong understanding of the core banking domain has enabled development of tools, frameworks and accelerators that improve
productivity and reliability. Domain experts have built functionally decomposed test scenarios for various core banking modules, which can be
used to build test cases.
In addition, Cognizant’s own Centre of Excellence for T24 accompanied by partnership with TEMENOS and Validata will ensure a timely delivery
to meet LQB objectives.
Cognizant will undertake a two phased approach in line with the requirements:
· Phase 1: Update the existing T24 test factory to add Islamic Banking and bespoke test cases
· Phase 2: Execution of offshore system testing, onsite integration testing and onsite UAT
Cognizant proposes to use Validata as the testing tool for the scoped engagement.
Details of the solution are provided in subsequent sections of the document.
Value Proposition
Cognizant’s brings the following value adds to this engagement:
Cognizant has participated in Large Core Banking Testing Programs with other customers, and has a clear understanding of the complexities and
challenges, and has evolved a well-documented set of “Lessons Learnt” from its previous engagements
Cognizant has prior experience in managing similar, large programs and can put together a robust Governance Structure to manage the
engagement; coupled with mature, metrics based Delivery Model to ensure success
Cognizant’s strong understanding of the core banking domain has led to the development of tools, frameworks and accelerators that improve
productivity and reliability.
As a result of its partnership with TEMENOS and VALIDATA, Cognizant possesses strong T24 competencies which will enable Cognizant to
understand the nuances of this engagement
Our dedicated centre of Excellence around Automation Testing can be leveraged to provide comprehensive testing services to support the
testing program
Cognizant has in place well-established project management activities for independent testing projects. These activities are driven by the overall
CMMi Level 5 guidelines and are consistent across the organization
Commercials
The total value of the entire testing engagement services will be USD $ 440,000 (USD $ Four Hundred and Forty Thousand only).
Cognizant will carry out the proposal on a Fixed Bid basis, and the value is derived based on the agreed scope at this point in time. In case there
are any modifications to the scope, the estimations will be revisited, which might lead to change in the commercials.
Our Understanding
TEMENOS would like Cognizant to conduct and manage system testing, integration testing and UAT for T24 R10 model bank with minimal
customizations (less than 10% of overall functionalities) for LQB.
Additionally, TEMENOS also requires a testing methodology/framework to successfully execute their implementation of T24 R10 model bank.
In Scope
Following is a list of modules in the scope of the engagement
Function
T24 Module
Account Interest and Charges
AC
Cheque management
CM
Collateral
CO
Customer
CU
Data capture
DC
Delivery
DE
Funds Transfer
FT
Limits
LI
Management Information
MI
Miscellaneous deals
MD
Multi Company and Extended Multi Company
Document Management
DM
Nostro Reconciliations
Position Management
PM
Process Workflow
PW
Reporting
RE
Security Management System
SA
System tables
T
CORPORATE
Bills
BL
Letters of Credit and Documentary Collections
LC & ST
Loans & Deposits
LD
Past Due Processing
PD
Trade Finance
--
Securities
SC
Securities Administration
SA
Securities Corporate Actions
SC
Securities Trading
SC
RETAIL
Direct Debits
DD
Teller
TT
TREASURY
Forex
FX
Money Market
MM
Local Clearing
Utilities (Enq, Versions, Menu, Comp. Screens)
Application Accounting
ATM Transactions
Branch automation
T24 IT operations/ Batches, Close of Business
Backup recovery
T24 Browser
Bloomberg Interface
Arrangement Architecture
AML Watch
Temenos Products
Temenos ARC
Temenos T24 Islamic Banking
Tasks in phase I
Analyse gaps between model bank T24 application and the business requirements document
Add and modify as per following to the existing T24 test factory:
Add test cases for Islamic Banking
Modify the existing test cases as per customizations understood during analysis
Tasks in phase II
Conduct the following testing:
Automated offshore execution of system testing
Manual onsite interface testing
Manual execution of onsite UAT
Interface testing to be carried out with following interfaces in scope:
ATM/POS system (Position)
CMS
Swift
RTGS/ACH/ACP
Reuters /Bloomberg
Defect re-testing and management
Out of Scope
The following activities would be out-of-scope for the Cognizant for the said engagement:
Customizations / code changes to the deployed T24
Build / Release Management
Deployment of T24 or any of the modules
Fixes for defects raised during testing
Non-functional testing including performance testing, security testing, usability testing etc
Support for any of the environments or applications
Onsite environment setup
Anything not mentioned in the “In Scope” Section
Cognizant Solution
To satisfy the TEMENOS testing requirements in LQB, Cognizant proposes a two phased approach for as follows:
Subsequent sections describe in detail each of the above shown phases.

Phase 1
Cognizant proposes to leverage its existing test case suite that caters to model bank functionality of T24 R10 version.
Cognizant would conduct gap analysis of LQB business requirement and baseline test cases which are based on T24 R10 reference processes.
It is estimated that a total of 2700 manual and automation test cases would be required, of which there is a ready to use repository of 2000 test
cases.
This existing test factory is to be modified and updated with test cases for LQB specific business requirement.
New test cases on Islamic modules and bespoke customization would be designed.
Entry Criteria
Signed off BRD from TEMENOS and LQB.
Availability of test environment specification.
Availability of build to Cognizant MVC testing team.
Availability of static test data as required.
Key Tasks
During gap analysis phase, Cognizant team will carry out an analysis of existing test cases to understand if they cover the functionality as per the
signed off BRD. The time required to update & optimize (if required) the test cases will be estimated.
Modification of test repository
Cognizant has an existing test repository of 2000 test cases for coverage of T24 testing for the modules defined in the scope
Once the gaps are identified cognizant proposes to create the test cases for the gaps identified which will be mostly for the customization
carried out. This is estimated to be at 5 to 10 percent of the total test cases, leading to total number of customisation test cases to be around
200.
Additionally, 500 test cases specific to Islamic banking modules will be prepared and automated
Define test strategy for the project.
Receive the environment/infrastructure specification and set up test environment for MVC offshore.
Receive the build from development team and install the build in Cognizant hosted MVC environment offshore.
Create test data in test environment based on the static test data provided to Cognizant
NOTE: Out of the 2700 test cases, 2500 will be automated and rest will be manual
Responsibilities and Deliverables
Activities
Responsibility
Deliverables
Analysis of requirements
Cognizant
Gap report and updated test case repository
Identify gaps and update test cases based on gap report
Cognizant
Creation of the additional test cases
Cognizant
Automation of test cases
Cognizant
Define test strategy for all types of testing
Cognizant
Test environment is prepared for execution offshore.
Cognizant
Providing test data
TEMENOS, LQB
Test data
Infrastructure requirement is documented and shared with Cognizant
TEMENOS
Infrastructure details
T24 Build is shared with Cognizant
TEMENOS
T24 build
Sign off on test repository
TEMENOS, LQB
Exit Criteria
Analysis is complete, gaps identified and test cases are updated as per the report.
Build is deployed and test environment is ready, up and running at both onsite and offshore.
Test data is set up in test environment.
Test data mapping is complete with the automation, wherever applicable.
Signed off test repository
Phase 2
Run MVC – System Testing
Cognizant will carry out the system testing offshore at their T24 Centre of Excellence in Pune, India. A 3-pass approach is usually recommended
for this phase, but due to time constraint, only 1 cycle of system testing will be executed. The activities carried out in this phase are:
Execute all automation scripts for all modules as defined in scope in single cycle
The automation scripts will include Islamic banking modules
The bespoke test case execution will be manual execution
Defect re-test and management
Test report preparation
Entry Criteria
Test environment is ready, up and running.
Test data mapping completed for automation scripts.
Activities
Responsibility
Deliverables
Execute automation test suite and manual test cases (1-cycle)
Cognizant
Test Report and Defect Report
Defect reporting and managing
Cognizant
Prepare Test Report
Cognizant
Retest the defect identified during cycle 1
Cognizant
Exit Criteria
100% execution of automation scripts and bespoke manual test cases(1-cycle)
Test report generated and delivered to TEMENOS.
Interface Integration Testing
The objective of onsite interface testing in SIT is to ensure that T24 is working as expected with other interfacing applications (as scoped above).
The interface test cases would be designed by offshore team. This activity can be during Phase 1 design activity depending upon the availability
of requirements:-
For incoming interfaces, Cognizant would need sample interface files from each environment (these can be simulated if not readily available).
Test cases will then be developed to check that the files are imported as expected into T24 and the expected resultant actions (exchange rate
updates etc.) have occurred and are correctly recorded in T24
For outgoing interfaces, test cases would be developed in order to perform the appropriate functions that would generate interface file entries
(e.g. FT for SWIFT payment). Checks would also be automated to ensure (for both real time and batch) interface files/messages are formatted
and contain the correct information
Cognizant would develop interface test cases and execute at onsite. Cognizant would work very closely with TEMENOS personnel to identify the
requirements and design interface test cases.
The test cases developed to process both incoming and outgoing interfaces and ensure that the T24 environment is behaving as expected will
be manually executed as part of this phase.
This testing will be completely carried out at onsite with TEMENOS being responsible for environment readiness with all interfaces up and
running in the test environment.
Entry Criteria
Environment readiness
T24 test factory updated with relevant test cases for interfaces and integration scenarios
Activities
Responsibility
Deliverables
Onsite Test environment preparation and user access
TEMENOS, LQB
Interface integration environment
Manual test case preparation and execution
Cognizant
Interface test cases, Test Report and Defect Report
Prepare test report
Cognizant
Sign off on defect report
TEMENOS, LQB
-
Exit Criteria
Completed interface integration testing
Defects re-tested
Sign-off from TEMENOS and LQB on interface integration testing exercise
User Acceptance Testing (UAT)
Cognizant would provide end to end test management for the onsite manual UAT phase. Cognizant would work very closely with TEMENOS and
LQB to define UAT strategy, scenarios, execute scenarios and perform defect management.
Cognizant will coordinate all the UAT efforts, ensuring that the tests are structured as per the strategy for life cycle testing, that the tests are
conducted appropriately and that results are recorded.
The end-to-end scenarios will provide users participating in the UAT to ensure they check not just the transactions themselves but also resulting
entries in other parts of the system.
This testing will be completely carried out at onsite with TEMENOS being responsible for environment readiness with all interfaces up and
running in the test environment.
Entry Criteria
Completion and sign off on system testing and interface integration testing
UAT environment readiness
T24 test factory updated with relevant test cases for UAT
Activities
Responsibility
Deliverables
Define UAT Test Strategy
Cognizant
Defect Report
Design business driven test scenarios
Cognizant
Test Execution
Cognizant
Defect Management
Cognizant
Test Report
Cognizant
UAT environment preparation

TEMENOS, LQB
Sign off on UAT
TEMENOS, LQB
Exit Criteria
Completed UAT
Defects re-tested
Sign-off from TEMENOS and LQB on UAT exercise
Indicative Schedule
Below is indicative schedule for the activities for Cognizant testing team. This is based on the scope shared at this point in time.
Changes to the agreed scope might result in changes in the timelines indicated above.
Commercials
Based on the understanding of the scope of the engagement, the total project cost is estimated to be USD # 440,000 (USD $ Four Hundred and
Forty Thousand only).
This will be a fixed cost that will be charged to TEMENOS as per the various milestones mentioned below:
Sr. No.
Milestone
Amount to be paid by TEMENOS (in USD $)
Advance against order confirmation (30%)
$132,000
End of Phase1 Gap Analysis and New Test Case Design 20
$88,000
End of SIT Execution 20
$88,000
End of Interface and UAT Test Design 10
$44,000
End of Interface and UAT Cycle 1 Test Execution 10
$44,000
End of UAT Cycle 2 Test Execution 10
$44,000
TOTAL (US$)
440,000/-
Terms and Conditions
The indicative prices above are based on our understanding of the scope of the program at this point in time. In case there are any changes to
the scope as outlined in our proposal we will work with the client to plan and price the phases as appropriate. This may lead to a change in the
pricing.
Taxes: The pricing indicated above is exclusive of all taxes.
Cognizant shall charge for T&E expenses at actuals to the client
Location: Offshore resources are assumed to be based at Cognizant’s Pune, India Delivery Centre and our prices for offshore personnel include
open office space, PC workstations equipped with standard office automation software and network connectivity to a local LAN. Onshore
resources are assumed to be based at the client site (base location, Dubai) where similar technology, communication infrastructure and office
space exists.
Project Hardware / Software: Project specific hardware / software such as servers and associated software, client licenses for project related
software, service management / performance management tools and special tools are not included in the above prices.
Response to ‘Requirements from Bidders’
Company Profile
Cognizant was founded in 1994 as an IT development and maintenance services arm of The Dun & Bradstreet Corporation. The company was
spun-off as an independent organization two years later. For the last 16 years since inception, Cognizant has worked closely with large
organizations to help them build stronger, more efficient, and more agile businesses. By leveraging highly flexible business processes, a
seamless global delivery network and deep domain expertise, Cognizant delivers a better “return on outsourcing.” Cognizant was one of the
first “India-centric” IT services companies to organize around key industry verticals and horizontals. This enables Cognizant to establish
extremely close partnerships that foster continuous operational improvements and better bottom-line results for clients.
A brief company history in chronological order has been provided below:
Year
Event
1994
Started as the technology arm of The Dun & Bradstreet Corporation
1996
Began adding third-party clients and servicing the best across industry segments
1998
First IT company leveraging India to be listed on the NASDAQ
2002
First company to be assessed enterprise-wide against mature industry-process certifications, such as P-CMM level 5, BS 7799, SEI-CMMi Level 5
2004
Acknowledged as a leading provider of IT services by industry analysts such as Gartner, Forrester, AMR and IDC; and added to the prestigious
NASDAQ 100 Index
2006
Became the fastest global IT services company to reach a $1 billion run-rate (under 12 years); Added to S&P 500 Index.
2008
Entered Fortune 1000; established global systems-integration relationship with T-Systems; formally inaugurated near shore delivery centres in
Argentina and Hungary; exceeded $2.8 million revenue mark
2009
Joined Fortune's "Most Admired Companies" list; named to BusinessWeek 50 list of the top-performing U.S. companies for third consecutive
year; named to Forbes "25 Fastest Growing Technology Companies In America" list for sixth straight year
2010
Selected for Fortune’s “Most Admired Companies” list for the second year in a row; placed in Top 5 for IT services
A significant driver of our growth in recent years has been the diversification of our geographic markets. In particular, we gained traction in our
efforts to build our client base in EMEA, where major corporations have increasingly come to recognize the benefits of global sourcing. The
expansion of our offerings into areas such as Business Process Outsourcing (BPO), Knowledge Process Outsourcing (KPO) and IT Infrastructure
Management also contributed to our strong performance.
Below is a snapshot of our financial performance and growth over the past few years:
Category
2007
2008
2009
2010
Net Revenue (USD millions)
$2,135
$2,816
$3,278
$4,100 (Guidance)
Revenue Growth (YoY)
32%
16%
25% (Guidance)
Net Income (USD millions)
$ 350
$ 430
$ 535
Number of Employees
55,397
61,697
78,420
85,500 (As of Q1 2010)
Q1 2010 Highlights
Revenue for the first quarter of 2010 rose to $959.7 million, (43% of which is from the banking and financial services & insurance industry), up
28.7% from the year-ago quarter and 6.3% sequentially as of March 31, 2010.
GAAP net income was $151.5 million, or $0.49 per diluted share, compared to $113.1 million, or $0.38 per diluted share, in the first quarter of
2009.
GAAP operating margin for the quarter was 19.1%.
Against the backdrop of an improving macroeconomic environment, our first quarter results confirm that our strategy of reinvestment continues
to provide the platform for industry-leading growth.
For further details on our financial credentials, please refer to our corporate website http://investors.cognizant.com/
Currently Cognizant has unique blend of onsite/offshore resources of over 85,500 (As of Q1 2010) passionate professionals.
Registered Address
Cognizant Technology Solutions,
World Headquarters
500 Frank W.Burr Blvd.
Teaneck, NJ 07666
Ph: +1 201 801 0233, Fax: +1 201 801 0243, Toll-free: +1 888 937 3277
Cognizant Technology Solutions (Dubai Branch)
United Arab Emirates
Office Number 901
Al Thuraya Tower No 02
Ninth Floor, Dubai Internet City, Dubai
United Arab Emirates P.O. Box 500378
Ph: +9714 4347608, Fax: +9714 4290325
Roles and Responsibilities
Cognizant roles and responsibilities
The roles and responsibilities of the various resources involved in both the above types of testing models are as follows:
Role
Responsibilities
Test Manager
Reviewing and finalizing Test strategy and plan (with scope, resources, milestones, offshore roles, planning, delivery commitments, acceptance
criteria etc.)
Provide direction to the onsite and offshore team
Program Level reporting on Cognizant activities to TEMENOS and Cognizant senior management
Single point of management contact to TEMENOS
Detailed planning, monitoring, and escalation point for all Cognizant onsite and offshore areas of responsibility
Administering and managing delivery
Issue resolution and crisis management, change control and status reporting
Business Analyst
Understanding of the application landscape & interfaces through the following:
Walkthrough of functional requirements
Interfaces walkthrough
Understand T24 customizations based on the Gap Analysis report
Creation of business scenarios for functional & interface testing & prioritize the same
Conduct trainings
Test lead
Scope confirmation and collection of the functional specification documents and requirements
Resource management and team allocation
Ensure that the testing environment has been set up
Ensure that pending issues, if any, are resolved at the earliest
Preparation of RTM, if applicable
Scheduling for testing cycle
Writing and maintaining the test plan and project plan
Finalize the scope, impact, and delivery of the testing with development leads
Communicate with the development lead regarding configuration, releases and defects
Review all requirements, and prepare testing strategy
Weekly / Daily status updating the testing and defect data
Participate in regular status meetings and teleconferences
Arrange KT and training sessions for the team
Release auditing and documentation
Ensure the successful delivery of the applications under testing and provide production validation
Reviewing and managing all testing deliverables of onsite/offshore team
Reporting and maintaining all project metrics
Test execution
Tester
Understand requirement documents
Writing and updating test cases
Test cases execution
Logging the defects and maintaining the Defect Life Cycle
Status reporting to Team lead
Execute regression Test cycle
Expected roles and responsibilities from Client
Role
Responsibility
Test Manager
Handle issues related to contract, proposal, and resources
Ensure that pending issues, if any, are resolved at the earliest
Participate in meetings and teleconferences
Review the overall project scope and deliverables with Cognizant Test Manager
Test Lead
Interact with the Application Development Teams for issues/defects resolution
Ensure that pending issues/defects, if any, are resolved at the earliest
Ensure the smooth delivery of testing lifecycle deliverables

Participate in status meetings on regular basis
Review and sign off artefacts at specified intervals
SME
Train the team with high level domain specific knowledge, application, and test processes
Arrange for interviews and discussions with key personnel
Participate in daily and weekly status calls
Provide the necessary understanding of the system and tasks to be accomplished
Act as primary contact(s) for resolution of any issues and queries raised by Cognizant during knowledge transition and execution phase
Be a coordinator with other vendors (if any)
Provide review and required approvals
Facilitate sign-off for deliverables
Review the artifacts produced
T24 Test Methodology
Cognizant follows a structured approach for T24 testing. Given below is a snapshot for the same.
The details of testing in this approach are covered in the annexure.

Defect Management
Cognizant during the test execution phase will adhere to the process for defect identification and constant retesting for the fixed defects.
Cognizant pursues a quantitative process for the measurement and tracking of all processes using metrics. Hence Cognizant has evolved a
Defect Metrics Management Process that allows the project to measure and take corrective actions during the course of the project.
The defect metrics are evaluated against the project-level benchmarks. Measures for the Defect metrics are regularly collected and collated
using an in-house-developed or third-party Defect and Test Management tool such Test Director or PVCS Tracker. These metrics are analyzed on
variety of parameters and opportunities for improvement are identified. Defects will be monitored on a daily basis during testing and review
process throughout the SDLC. The steps below detail out the process Cognizant proposes for defect resolution.
Each defect, as it is discovered, will be recorded in identified defect tracker test management tool. This repository will be accessed by both the
onsite and offshore testing team, and by the development team(TEMENOS)
Each and every defect is assigned to a developer(TEMENOS)
Once the development team is satisfied that the defect has been fixed, a note is made that the module(s) / component(s) affected by the defect
are ready for re-testing
Once this note is made, all the test cases impacted by the defect or the related component(s) will be executed to ensure that the defect has
been rectified
Defect Prevention Meetings will be conducted at regular intervals between the testing team and development team to discuss test execution
and defect analysis
This is followed by Regression testing to ensure that the actions taken to rectify the defect have not produced any knock-on effects. Suitable
analysis will be performed and appropriate tests will be re-run
Only when re-test has been successfully completed with no critical failures, testing will be signed-off. Testing lead will then deliver the
application to onsite for integration testing
Governance and Communication
Cognizant has proven experience in handling similar engagements in the past. Keeping the customers informed about the health of the
engagement plays a vital role in overall delivery. The following channels of communications have proven worthwhile transparency:
Suggested status reporting / review frequencies with TEMENOS and LQB
Application level, portfolio level, program level detailed metrics reported on a monthly basis
Performance Dashboard – snap shot view of the project metrics to measure the projects health
Internal (Cognizant) reviews / checkpoints
Weekly status reporting/meetings between Cognizant onsite and offshore teams
Monthly account level operational performance review conducted by the domain BU delivery head
Monthly account level performance scorecard with the rating is calculated based on the metrics planning, metrics reporting and process
compliance parameters.
Following diagram depicts a general model for communication. The communication model will be finalized based on further discussions with
TEMENOS and LQB.
Prerequisites
Documentation and training requirements
TEMENOS will be required to provide any training, which will help the test resources to understand the requirements and which will also enable
them to formulate test scenarios and plans. TEMENOS is also expected to provide clarifications on application logic, business requirements,
functionality, test environments and interfaces.
TEMENOS will also be required to provide the following documents:
Business Requirement documents
Functional Specification documents
Interface Requirement documents
User Manuals
Process Flows
Infrastructure/Logistics
Cognizant will need the following infrastructure support from TEMENOS:
Provide all the necessary software licenses to the Cognizant offshore team
Work with Cognizant infrastructure team to extend the existing connectivity to the members of the new project team. Setup users in for VPN
access
Provide necessary physical infrastructure like laptops, workstations, telephones, tools & software to Cognizant’s onsite team
Testing Tools
Cognizant resources are familiar with the following set of tools, and any of them can be used for the testing phase, depending on the
requirement and client’s preferences.
Serial Number
Testing Stage
Tools
1
System Testing
Validata, Load Runner, WinRunner, QTP, , Test Director
Silk Performer, Silk Test International, Silk Test, Silk Central Manager
Webload ,OpenSTA, TestLink, Bugzilla, Selenium,QMS
2
System Integration Testing
Validata , Load Runner, WinRunner, QTP, , Test Director
Silk Performer, Silk Test International, Silk Test, Silk Central Manager
Webload ,OpenSTA, TestLink, Bugzilla, Selenium
,QMS
Cognizant proposes to use Validata as the testing tool for the scoped engagement.
Project Management Approach
Project Management
Cognizant team will monitor project schedule with special emphasis on delivery milestones, dependencies, risks and issues on weekly status
meeting and communicate project performance, vendor performance to all stakeholders.
Scope Monitoring
Schedule Monitoring Against Delivery Milestones
Cost Monitoring Budgeted Vs Actual Cost
Quality Monitoring DAG, stringent quality norms
Risk Monitoring Lookout for new risks, control the identified risks
Change Management Procedure
Any change in the scoped functionality will be incorporated through following change management procedure.
Requests for a change is received through a formal Change Request (CR) document
Initial impact analysis is performed by the onsite project manager/co-ordinator to assess
Impact of the change on existing requirements
Risk involved in making the changes
Modifications required in design, architecture, source code, test cases and other project documentation
Evaluation of the cost, schedule, resource loading etc
Based on analysis, the change control board approves/rejects the change
Detailed analysis of the change is performed by the Project Manager along with the Project Team
The traceability matrix is referred to ensure complete coverage
Change Control Log, Project Plan and Traceability Matrix are updated to reflect the change
Change is then implemented by modifying the necessary software configuration items (source code/documents)
Change is released after proper review and testing of the configuration items
Assumptions and Dependencies
Assumptions
Following are the assumptions made for this engagement:-
The implementation is model bank implementation with less than 10% customization.
Client would provide infrastructure requirement including hardware and software requirement for environment set up.
Client will take appropriate measures as deemed necessary to ensure application/build availability without any disruption.
Client will appoint suitable persons as points of contact as envisaged in the Project Organization/agreed organization structure to ensure that all
inputs such as responses to questionnaire from Cognizant are available in time; as any delay may affect project schedule.
Deliverables forwarded by Cognizant team to Client for review and approval will be assumed reviewed and approved if no response is received
within a reasonable timeframe (1-2 business days) so as to meet project deadlines and deliverables.
For any data masking needs, it is assumed that Client will mask the data that will be accessed by Cognizant team.
Client will identify the authority responsible for signing off deliverables for each project phase.
Client will arrange for basic infrastructure support for Cognizant Personnel working in their premises, including hardware, software, email
access, secure ID's, and access to relevant test environments (UAT and Onsite Interface Testing).
UAT environment would be hosted at onsite at Dubai and will be managed by Client
Client would make functional resources available for review and sign off of UAT scenarios.
Any change in scope found during various phases may cause revision of the present pricing estimate.
The timelines & efforts are based on 100% environment availability during offshore & onsite working hours
Client will ensure that Cognizant Testing team is provided with an integrated environment which has related applications and 3rd party
interfaces integrated with each other for end-to-end functional flow testing
Client will provide necessary documentation that will be required for test case preparation/modification and execution
Any invalid defects arising out of invalidity of the test cases should not be evaluated against the Cognizant Testing team since the team will be
working on pre-designed test cases assuming the implementation as model bank implementation.
Dependencies
Client will ensure that the team will get all the necessary support from providers of Third Party applications / products
Client will be providing baseline documents including business requirement documents, functional specifications, interface requirement
documents, user manuals, process flows
Wherever necessary, Client will provide clarifications on application logic, business requirements, functionality, test environments, interfaces
Client will review UAT test scripts prepared by test outsourcing team and request enhancements, if appropriate
Client Program Manager / Project Coordinator would need to be assigned before project kick-off for this engagement
Client will identify the authority responsible for signing off deliverables for each project phase
Client Subject Matter Experts (both from line of business as well as technical personnel including system administrators, database administrators
or network administrators etc.) must be available during the project for speedy resolution of issues and queries at all times including the
weekends during which testing may be carried out. A quick turn-around time for issue and query resolution will be critical for the timely
completion of the project
Client will provide timely application builds to complete testing activities as scheduled. Delay in providing the correct builds will impact final
delivery.
Case Studies
Cases Study – I
Bank Overview
The Bank is a leading European financial services provider that offers a broad range of products and services to individuals, businesses and
institutions.
Business Needs
The Bank had two T24 Implementations in two separate geographies in 2009 and was in process of implementing T24 in a third location. They
was looking for a complete roadmap to testing managed services with improved processes, methodologies, status reporting and enhanced
project team collaboration.
Solution
The solution was provided in the following phases
Scoping & Gap Analysis
Onboarding and setting up of MVC at Cognizant location
Optimization & Design of Test Cases in Validata
Mapping of Test Cases with Test Data in Validata
Execution of Test Cases in Validata.
Benefits
Following were the benefits of using the Validata based Managed Verifcation Centre.
Measurement of testing activities with the help of defined metrics and reports
Clear analysis of requirement coverage, execution status, defect status and other management reports
Effective Utilization of time and resources to reduce the turn-around time
Hybrid approach and functional testing approach to identify defects at early stages and reduce the test cycle time
T24 functional experts to optimize and create test cases
Availability of reusable set of test cases from Validata
Case Study -II
Bank Overview
The Bank is a Riyadh based joint stock company that is one of the most reputed financial solutions providers in Saudi Arabia. It provides
Consumer, Corporate and Investment Banking products and services .It also offers practical solutions to commercial customer requirements in
conformity with Sharia rules.
Business Needs
An entirely new bank set up along with end to end implementation of the T24 system to cater to their banking needs in diverse business areas
The system was required to meet the following two purposes:
Extraction of a customer’s credit information from the Central Bank to decide the customer’s credit worthiness for a new loan.
Updating the customer’s new credit information in the Central Bank’s system once the loan is disbursed
Solution
The solution was provided in the following phases
Gap analysis was performed and products were developed to meet the gap analysis requirements.
The Bank wanted to have specific products for Commodity Trading Term Deposits and Lending as per Islamic Banking.
The following three products were developed to meet Bank requirements:
MURABAHA for Commodities
WAQALA for Term Deposits
TAWAROOQ for Lending
Testing
System Integration Testing was performed to ensure that the system is defect free
User Acceptance Testing support was provided ensure that the system meets mutually agreed upon requirements.
Post-production support
Cognizant has handled all the post production issues arising in the system
Benefits
Following were the benefits to the Bank.
The entire core banking solution that met all of the bank’s needs was implemented within a time span of less than 24 months.
The ‘Credit Scoring’ solution was integrated with the bank’s core banking system lending a support to their rapidly growing consumer lending
business
The bank was able to comply with the country’s regulatory requirements pertaining to consumer lending
An integrated Bank set up was available to Bank with specific Islamic Banking Products.
Annexure
About Cognizant
Cognizant (NASDAQ: CTSH) is a leading provider of information technology, consulting and business process outsourcing services,
headquartered in . Cognizant’s mission is “To dedicate our business process and innovation know-how, our deep industry expertise and
worldwide resources to working together with Banks to make their businesses stronger”. True to its mission statement Cognizant has been
providing customers a truly differentiated global service offering which is centric to the customers’ domain.
Cognizant was founded with a global mindset. With its headquarters in the and rapidly expanding delivery footprint, extending from and ,
and , Cognizant has the geographic presence and optimal resource mix across onsite, offshore and near-shore locations to meet the needs of
global Banking and Financial services Banks. Its “born global” heritage is viewed as a significant market advantage as customers consider
globalization as a key element to their success. As of 31st June 2010, it has more than 50 global delivery centres and 85,500 employees.
A member of the NASDAQ-100 Index and S&P 500 Index, Cognizant is a Forbes Global 2000 company and a member of the Fortune 1000 and is
ranked among the top information technology companies in Business Week’s Hot Growth and Top 50 Performers listings.
Cognizant has wide experience in defining, setting up and implementing managed testing services for Banks in the financial services domain.
These managed services teams range from mid-size teams (approx 50 testers + leads) up to large-size teams (approx 350+). Testing Practice has
3200+ associates in Banking and financial services spread across various areas. Cognizant is providing independent testing services to 180+
customers across industry segments out of which 40+ customers are in the Banking and Financial services segment.
Cognizant BFS Competency
Cognizant’s Banking & Financial Services (BFS) practice provides industry leading, proven solutions to globally diversified banks, custodians,
regional banks, asset managers and utilities supporting their business and technology infrastructure. The practice offers domain consulting
services in all facets of financial services, from Banking to Capital Markets and integrated Business Process Outsourcing services that focus on
consumer lending, capital markets and retail banking in addition to horizontal services such as data management, analytics and accounting. The
BFS practice is organized around nine key sub-verticals as shown below:
These focused segments within the BFS space, bring in significant domain experience and knowledge of business processes and technology
issues to project execution teams.
Key highlights of Cognizant BFS vertical are:
Largest Industry Practice within Cognizant
Financial Services revenues contribute to around 43% of Cognizant revenues
Over 22,000 associates serving over 100 leading Banking and Financial Institutions
Clients include 9 out of top 15 North American financial institutions; 4 out of top 5 UK financial institutions; 9 of top 15 European Banks
10+ customers served across multiple geographies
Our successfully delivery track record has brought helped ensured customer loyalty 95% repeat revenues
Chosen as Temenos Global System Integration Partner, Signed partnership with Dorado, Loan Origination and Servicing product vendor.
Significant investments in Domain, Technology and Program Management
Cognizant Business Consulting (CBC) – BFS group
With a dedicated team of industry experts and business analysts, CBC-BFS monitors regulations and trends in the BFS industry and creates
solution offerings to give our clients a sustainable competitive advantage by helping them anticipate and respond proactively to such
developments.
CBC-BFS group works closely with delivery teams at every stage of the project lifecycle.
Through this pool of functional experts CBC- BFS offers Consulting services, Business Analysis services, Industry Research services and COTS
products expertise.
Cognizant Centre of Excellence for T24
Cognizant, a leading provider of information technology, consulting and business process outsourcing services has signed a global strategic
partnership with Temenos.
Temenos, the global provider of integrated core banking systems, has signed a global strategic partnership with Cognizant, a leading provider of
information technology, consulting and business process outsourcing services, to significantly enhance its service and delivery capabilities for
Temenos T24 (T24).
As part of the partnership agreement, Cognizant is investing in training quality associates to deliver T24 implementations over a three-year
period. It has established a global Centre of Excellence by working together with Temenos. Financial institutions worldwide will benefit from this
best-of-breed partnership as the joint partnership goes to market. This partnership will mark a significant change in the approach of working
with global systems integrators to deliver T24.
Cognizant is actively engaged on a number of Temenos T24 implementations and will also work with Temenos’ Complementary Solutions
Partners to provide solutions to banks where required.
Cognizant is confident that this strategic partnership will reap considerable rewards as bank spending trends more and more towards core
systems. It is making significant investments in the relationship with Temenos and believes this partnership will add to the breadth and depth of
its capabilities in banking and financial services technology and operations, and its proven, domain led delivery experience, further offering cost-
effective solutions and a compelling proposition to the joint customers.
Cognizant’s consultants will be fully trained on implementing T24 Model Bank, will apply the Temenos Implementation Methodology to all
projects and will be able to avail themselves of Temenos Application Management services for localizations and bespoke requirements. Apart
from core development, the consultants will get into all other aspects of the implementation like Program Management, Requirement
Gathering, Interface design and testing, development testing, data migration, SIT, UAT and end-user trainings. Also, cognizant will be actively
involved in responding to RFP’s.
Cognizant Testing Offerings
Cognizant has a strong testing practice, consisting of 3,200-plus professionals who have the skills to perform system testing and system
integration testing and also provide support for user acceptance testing of banking applications. We provide coverage of the entire test cycle,
including patch testing, regression testing, functional/non-functional testing, load testing and more. Our test automation assets and family of
reusable/pre built assets help us reduce testing cycle times—ensuring that banks Temenos implementations are more productive. Cognizant
offer a variety of flexible testing delivery models, from test execution, to providing a managed test center (MTC) with either bank-owned
infrastructure or a public/private cloud-based infrastructure.
Cognizant provides a full end-to-end (e2e) testing capability to ensure the quality of TEMENOS T24 implementations. The main testing elements
for T24 Implementation and Upgrade can be grouped as following:
Core Testing:
Ready to use T24 Test Packs, library of test cases for T24 modules
Functional testing and regression testing
System Integration testing
Performance testing and
Defect management
Non-Core Testing:
Data Migration testing
Interface testing
Release/Module level testing
Delivery Model
Cognizant presents a bouquet of delivery model options – that enable Cognizant to customize its solution for client testing requirements.
Test Execution Only
Clients manage overall testing delivery and create all testing artifacts. The Cognizant team is responsible only for executing test cases provided
by the client, logging defects, and providing necessary reporting.
Partial Project Ownership
The client’s team creates the test plan and manages the overall testing delivery. Cognizant executes the full set of testing activities defined
within the client test plan under the client’s direct management.
Complete Project Ownership
Cognizant assumes full responsibility for all software testing activities. Cognizant manages delivery with guidance & oversight from the client
testing/SQA leadership.
Managed Test Centre
Cognizant handles end-to-end testing responsibilities across multiple applications/systems within a client organization.
Cognizant’s unique T24 Managed Test Center offering can be operated through any of the models as below:
Public cloud-based setup: This will be operated like a Shared service center. MTCs of client T24 test setup will be archived, maintained and
executed on a need basis. Cognizant will own the hosting and setup of this T24 test environment.
Private cloud based setup: Dedicated space setup for a specific client MTC where the T24 test setup will be maintained, archived and executed
based on the client’s regression testing requirements. Cognizant will be responsible for hosting and setup of this T24 test environment.
Private /Shared Physical Setup: Cognizant will create physical infrastructure of MTC in its own premise with the entire hardware & software
configuration required for test environment. This model can be leveraged as a shared or dedicated setup based on the client need.
Bank owned setup: Standard & recommended MTC model where Cognizant team will leverage the client’s environment via VPN or Citrix
connectivity. Client hosts and maintains the necessary infrastructure of test environment and Cognizant teams run the testing activities on the
same.
Cognizant T24 Testing Methodology
Test Analysis
The onsite team participates in the project-kick off activities and understands the project definition, project deliverables and the overall project
plan. The Cognizant and TEMENOS teams review the business requirements and the functional specifications to ensure that the requirements
are testable and unambiguous.
Entry Criteria
Signed Scope document
Tasks
At a high level the tasks to be performed in this phase are to:
Identify the test Requirements through Requirements Gathering
Define the scope of testing for modules and customization line items that have to be tested
Phases of testing such as SIT, UAT data migration testing
Timelines for closure of each phase
Identify and evaluate tool required for testing
Understand the application and business processes.
Study requirements and based on the project scope, draw out a functionality matrix (the matrix explains the complexity and business priority of
a feature that needs to be tested).
Gather inputs on the test configurations for AUT.
Study supporting documents available.
Based on the type of testing to be done—functionality, performance or security—formulate the test strategy and estimate efforts
Obtain customer go-ahead for efforts estimates and get requirements understanding issues clarified.
Planning for the testing phase includes scheduling and planning the module testing activities, manpower planning for the testing team, resource
planning for the testing resources, identification of tools, etc.
Deliverables
Test Analysis document defining the scope with respect to
Module Testing
Data migration
Interface testing
Defect Management
User Acceptance Testing (UAT)
Test Plan / Test Strategy Document
Validations
Task
Responsibility
Validate Test Analysis Document against scope definition document.
Cognizant
Verify coverage of critical path execution
TEMENOS, Cognizant
Verify inclusion of SLAs as agreed with the bank
TEMENOS, Cognizant
Verify schedule and timelines
TEMENOS
Exit Criteria
Review and Bank sign off on Test Analysis document
Agree on the with all parties involved
Identified testing tool
Responsibilities
Task
Cognizant
TEMENOS
Bank
Creation of test analysis document
Define scope of testing
Agreement
Validation of Test analysis document
Review and signoff on Test analysis document
Test Design
During the test design phase, the test team will prepare the overall testing strategy based on the testing timelines and schedule decided in
analysis phase. This strategy document will have details like test approach, test deliverables, staffing and test phases with entry / exit criteria
and Test Stop / Suspension / Resumption criteria
Entry Criteria
Signed off interface definition document
Signed off architecture
Signed off project plan

Tasks
Preparation of overall test plan for the identified testing scope including the following:
Testing under simulated work conditions (against stubs)
Testing for fail safe and secure operations
Covering all sub-project and subordinate activity testing
Integrated testing strategy
Select and identify critical test paths based on the design
The test plan should also contain the following details: approach to be taken, test strategy, test items, entry/exit criteria, environment, roles and
responsibilities of team members, process to be adopted.
List the various automation areas and performance areas and simultaneously set up the test bed and necessary infrastructure.
Resource planning
Work out execution timelines.
Prepare a risk assessment and mitigation plan with risks categorized as high/medium/low.
Deliverables
Traceability Document
Validations
Task
Responsibility
Verification and review of the test strategy document
TEMENOS
Test Plan Preparation: Exit Criteria
Signed off test plan document from TEMENOS and bank
Test Plan Preparation: Responsibilities
Task
Cognizant
TEMENOS
Bank
Creation of test strategy document
Provide information on critical paths, timelines and functionality for T24 modules
Review and signoff on Test strategy document
Test Script Development
The functionality and design of the module are studied and all the possible input interfaces and data files are identified. The module leader then
identifies the modules/units that would be ready and could be used for the creation and verification of data during testing. As far as possible all
input data is created using already developed software components. Data creation programs/scripts are created only if absolutely necessary.
This ensures that the integration issues between various modules get addressed as the system is being built.
Entry Criteria
Design document of the module
Requirements & Functional Specifications of the module
Construction phase plans and actual status
Tasks
Develop and document unit test plans for all components
Create test-bed for unit testing
Perform the unit tests as per the unit test plans and fix any bugs identified during the unit testing
Keep track of issues, weekly status, and progress
Create functional and integration test cases
Understand the module's design and functionality by going through the design document and the functional specifications.
Identify the list of modules interfacing with the given module.
Identify critical functions and areas in the module that need attention during testing.
Define the scope of the module test. Identify the features that will be tested and those that will not be tested in this module. Identify when and
how these features will be tested.
Identify which tested modules could be used directly during the test.
Identify drivers and/or stubs that may need to be built. Assign the activity for building and testing these to the construction team.
Define procedures for aspects like: checking of inter-module interfaces, performance testing, security features testing, multi-user, checking
results, etc.
Determine the resource requirements for initial executions and subsequent repetition of the module tests. Consider hardware, system software,
test tools and test environment including set-up data requirements. Also consider manpower requirements to execute the tests.
Define the checkpoints where the output results will be verified.
Prepare a schedule for the module test execution.
Write test cases with dependencies, pre and post conditions, sequence of execution, expected results and any other details for execution.
Initiate the scripting for automation-identified cases.
Deliverables
Test cases, Test Scripts, test data and test logs

Validations
Task
Responsibility
Validate and review test cases before releasing
Cognizant
Exit Criteria
Completion of the test on specific modules
Responsibilities
Task
Cognizant
TEMENOS
Bank
Creation of test cases
Test Execution
The objective of this phase is to test the system to check whether it satisfies the required functionality as described in the user requirements.
Module Testing
Entry Criteria
Completion of draft user manual and detailed design
Unit tested interfaces (with stubs)
Unit tested core product tested for customizations
Test Plan for the modified modules
Tasks
Execute the tests.
Log errors observed in the Test Incident Log.
Analyze test incidents logged, to determine the nature of the errors and take the appropriate actions as indicated below:
The error is in the system design, specification or code, raise a System Change Request for the change.
The error is due to a wrong test condition, wrong sequence of test conditions or erroneous test data. Raise a System Change Request to make
the necessary change to the System Test Plan and rerun the related tests.
The error is due to an incorrect set-up environment. Re-setup the environment and run all the affected tests.
The error is due to problems in the drivers and the stubs. Fill a System Change Request to request change to the appropriate driver, stub.
At the end of each round prepare a test completion summary report detailing:
Tests which could not be covered, with reasons
The effort, time and resources used during the test
The number of errors by classification,
Problems faced if any while performing the tests
Any limitations of the system.
Deliverables
Module Test Result
Tested System (with stubs)
Validations
The module test results are validated against the Modules Test plan.
Exit Criteria
Review of Module Test Result
Resolutions of all the errors during module testing.
Responsibilities
Task
Cognizant
TEMENOS
Bank
Creation of Module Test plan
Execution of Module Test plan
Provide unit tested T24 application
Interface bug fixes
Core T24 bug fixes
In this stage, the system integration test environment will be prepared and documented along with expected results. Before starting the system
integration testing the stubs should be replaced with actual interfaces of bank. The test cases will be structured in such to verify the system
behaviour while interacting with various systems.
Entry Criteria
System integration testing environment readiness.
Module Testing has been completed and signoff
System Integration Test plans has been approved

Tasks
Set up the test environment. Execute the tests.
Log errors observed in the Test Incident Log.
Analyze test incidents logged, to determine the nature of the errors and take the appropriate actions as indicated below:
The error is in the interface design, specification or code, raise a System Change Request for the change.
The error is due to a wrong test condition, wrong sequence of test conditions or erroneous test data. Raise a System Change Request to make
the necessary change to the System Test Plan and rerun the related tests.
The error is due to an incorrect set-up environment. Re-setup the environment and run all the affected tests.
There are inconsistencies in the documents used during the test and the interface commands in the system. Raise a System Change Request to
change the corresponding manual.
At the end of each round prepare a test completion summary report detailing:
Tests which could not be covered, with reasons
The effort, time and resources used during the test
The number of errors by classification,
Problems faced if any while performing the tests
Any limitations of the system.
Deliverables
System integration Test Result
Tested Integrated System
Validations
The System Integration test results will be validated against the System integration test plan
Data validation
Exit Criteria
Review of System integration Test Result
Resolutions of all the errors during system integration testing.
Responsibilities
Task
Cognizant
TEMENOS
Bank
Creation of SIT cases
Execution of SIT cases
SIT environment creation
Resolution of errors raised in interfaces during SIT
Resolution of errors raised in core T24 during SIT
SIT Signoff
User Acceptance Testing
The User Acceptance Testing will be carried out by the business users of the bank on the UAT environment setup by the bank operation team.
Cognizant will be responsible for setting up of test mirror image of the UAT system. This mirror will be used by Cognizant team to fix any defects
raised during UAT cycle.
Entry Criteria
Setup of the UAT Test environment.
Identification of business users
User manual readiness
Completion of application Training for business Users
Tasks
Co-ordinate User Acceptance Testing to be undertaken by the customer user along with the other vendors involved ensuring that the Integrated
System is "functionally" functional
Organize walkthroughs to customer and seek approval; make appropriate changes, where deemed necessary
Resolve any issues raised during UAT phase and escalate
Obtain sign-offs
Deliverables
System ready to go Live
Exit Criteria
Sign-off from customer for UAT
Responsibilities
Task
Cognizant
TEMENOS
Bank
Execute User Acceptance Test Plans
Co-ordinate with bank during UAT

Resolve issues in interface coding raised during UAT
Resolve issues in core T24 raised during UAT
Data Migration issues, if any
UAT Signoff
Cognizant as SI
Cognizant is a pure-play services company with a world class system integration arm. To complement our services focus, we leverage our SI
expertise to add more value to the client’s business. The extra value that we bring to the engagement is through very premier set of
partnerships with technology, domain and enterprise-level products’ market leaders. A snapshot of our partnerships is shown below.
Cognizant’s service offerings, leveraging the partnerships stated above, are given below:
Technology Strategy Consulting
Software Application Services
Application Development
Application Maintenance
Enterprise Application Integration
Reengineering & Migration
Testing Solutions
Infrastructure Management
Business and Knowledge Process Outsourcing Activities
Enterprise Software Package Implementation
Data Warehousing and Business Intelligence.
Value adds from partnerships
Cognizant TEMENOS Partnership
As mentioned above, Cognizant has established a Centre of Excellence for T24 which will ensure:
Creation of critical mass of TEMENOS consultants
Enhancement of service and delivery capabilities for T24 core banking product
A significant change in approach of working with global systems integrators to deliver T24.
Cost-effective solutions
Convincing propositions to joint customers
Cognizant Validata Partnership
Due to Validata’s tools, test repository and experience in T-24 testing, Cognizant has decided to partner with them. The objective of building this
offering is to bring a unique solution to Temenos testing which is not available with competition. Cognizant’s proven testing methodology, retail
banking domain expertise, execution capabilities combined with Validata’s Software Asset Suite (SAS) product will ensure:
Reduced testing cycle time for T24 implementations
Effective and better quality assurance
Unique testing service built on respective strengths of partners
Cognizant Managed Verification Centre
The Managed Verification Centre (MVC) provides solution to Banks with testing requirement around Multi-country rollout, reference build on
one country, New rollouts for new geographies, Regression testing due to business impact caused by other transformational activities,
Regression testing for Upgrade activities like T24 version upgrade, OS upgrade etc.
T24, as a product, is highly configurable and comes with a model bank approach (standard features+ gaps). Due to the nature of product, the
front-end functionality of the application is fully customizable. This forces the need of a unique testing solution that provides quick time to
market, optimum test coverage, reusability and easy maintenance of its test suites. With the partnership with Validata - a T24 test automation
tool, a has been evolved & implemented.
A provides repetitive, reusable, consistent, comprehensive, and competitive testing solution for T24 testing needs by hosting & maintaining the
test environments. The uniqueness of the model comes with the various options & combinations offered to the Banks for:
Operating Model:–
Cognizant Hosted: Public Cloud based Setup (Operated like a Shared service center. Cognizant will own the hosting and setup of this T24 test
environment.), Private Cloud based Setup (Dedicated space setup for a specific Bank MVC Cognizant will be responsible for hosting and setup of
this T24 test environment), Private/Shared Physical Setup (Cognizant will create physical infrastructure of MVC in its own premise with the
entire hardware & software configuration required for test environment.)OR
Bank Hosted Traditional Setup (Standard & traditional MVC model where Cognizant team will everage the Bank’s environment via VPN or Citrix
connectivity)
Delivery Model –
Phase 1 of On-boarding, Phase 2 of Automation Baseline and Subsequent Run of automation suite.
b. After you get an idea of what the scope is of the testing required, the complexity, and
the time needed to do it, then you make a decision to what extent you need to test in
order to get the “bugs” (defects) down to whatever level you deem acceptable. Here’s a
typical standard on defects in testing and what the level is before going “live” or into a
production environment.
In this test plan, the following areas are included:
o Goals and objectives that describe what is most important about the project and the tests
needed for it
o Scope describes what will be and what will not be tested under this plan
o The test schedule is presented, based on stated assumptions, with principal risks and
contingencies
o The test deliverables section indicates what deliverables testing has to produce and
contains a matrix that should be extracted and routinely updated as the items to be
produced are generated. The section also contains a sub-section on other development
team members’ responsibilities—extract this matrix and use it also to guide who does
what
o Test methodology is a progression of stages and quality levels to be expected as the
project matures, as well as the typical cycle of testing
o Criteria for acceptance into testing defines what Testing’s expectations are to accept a
build for testing
o Test Director and Test Director (applications by Mecury) database standards are listed so
that developers, project managers, and others understand the basic standards of how
and where we track test cases and bugs. Parties external to testing will use Test Director
and will read the Test Director reports.
Here’s a sample testing plan work flow--
Test Completeness
Testing will be considered complete when the following conditions have been met:
Standard Conditions:
 When Harrah’s Entertainment, Inc. agree that testing is complete, the app is stable, and
agree that the application meets functional requirements
 Script execution of all test cases in all areas have passed
 Automated test cases in all areas have passed
 All priority 1 and 2 bugs have been resolved and closed
 Each test area has been signed off as completed by the test lead.
 50% of all resolved severity 1 and 2 bugs have been successfully re-regressed as final
validation
 Ad hoc testing in all areas has been completed (this is essentially the functional testing
simulating the user view and use of the PDB system)
c. If there is anything more you need to know about testing then you need to contact us by email
(rlivingstonjr@sam-v-it.com) with specific questions – there are way too many topics for a simple
line entry in this document, but we will be glad to help you with other information you may want or
need about how to select a good testing vendor and what sort of testing you need - it may be
easier and simpler than you thought and the whole T24 system may not necessarily need to be
“tested to the bottom” to get a clear view of whether it’s ready to use or not in the end
Bug Fixes, Change Requests, Retesting

The fixes and change requests must be orderly, and if you want to know how the vendor
handles these areas, then make sure you get the questions on a list in your due diligence
questions and find out exactly what the story is with these subjects regarding fixes and
retesting. Change requests typically are managed only after the UAT testing has been
completed. Change requests made during testing are considered either out of scope or to be
dealt with at some future new release stage. Ask the vendor how change requests are listed and
kept for future changes. Ordinarily change requests are suspended during testing and are simply
made a priority for a future upgrade to the software. Step at a time here is the rule. If you do
not work in a logical manner during development your testing you will never be finished. Phases
are the way to manage this sort of thing when it comes to changes requested during the
development and testing cycle of any software, T24 especially.
Bug Reporting & Triage Conditions:
 Bug find rate indicates a decreasing trend prior to zero bug rate (no new severity 1/2/3 bugs
found).
 Bug find rate remains at 0 new bugs found (severity 1/2/3) despite a constant test effort
across 3 or more days.
 Bug severity distribution has changed to a steady decrease in severity 1 and 2 bugs
discovered.
 No ‘Must Fix’ bugs remaining prior despite sustained testing.
Criteria for Acceptance into Testing
For a build/upgrade to be accepted for testing, the following items must be met:
 Unit Testing: Each unit (SP [or stored procedure]) has to be tested by the engineering
team before being released for further system/regression testing.
 Existing Bugs Fixed: Developers must resolve all previously discovered bugs marked for
fix. If there are too many unfixed bugs, which should have been fixed, then testing may
reject the build.
 Release Document: Must be issued for every new build (of Harrah’s in-house software). It
will include the build number, all changes, and new features from the previous build. In a
component release, it should indicate which areas are ready for testing, and which areas
are not.
 Instructions: All necessary setup instructions and scripts should be provided.
 Elements List: A list of all components (objects) in the current release with a version
number.
Data Migration - !!!!!! and Data Cleanup Prior to Migration

168. As with testing the area of data migration is complex and beyond the scope of this
document to engage in a full blown discussion, but ask these questions:
169. What tools does T24 have to do data migration?
170. How reliable is it?
171. How do you map data from one system to another where there is not the same field value,
length, type, etc?
172. Do you have a program or application to move data from one system to another where
there is an audit trail? Do you have an error log? What do you do with data that cannot be
migrated?
173. After data is migrated, how to you validate that it was migrated correctly--that is to the
right fields, databases, tables, etc.
174. What is you typical time line to do a data migration (week, month, more?)
175. What sort of fall back or rollback procedure to you have if the data migration fails or does
not meet standards?
176. What is the success rate on data migrations for the 1st round, 2nd round, 3rd round?
177. How many migrations do you typically conduct (1 test, 2 tests, more - live, backup, smoke
test, what is your migration methodology in other words?)
Ask a question about data clean up too--
178. What does clean up mean to the vendor and client?

179. Who does the clean up?
180. What are the typical standards used?
181. How much is the cleanup a major time factor in data migration (I’ve seen it take 3-6
months to do a clean up). Ask how long a clean up usually takes.
182. Do you clean up data that is older than a certain date (10, 20 years or more) - or simply
archive it?
183. What archiving does the T24 system have for data that is no longer needed but needs to be
retained?
184. Ask about T24 data warehousing. This is another topic that I will not delve into here, but
ask the question?
185. What systems with T24 or in T24 do data warehousing? Get the full picture of how T24 and
data warehousing typically work to meet Basel I, II, III standards.
User Acceptance Tests
186. These simply need to be verified as to their purpose, value, and usefulness to do what they
are intended to do – that is, to find out if the T24 system is configured to your standards and
business processes - here are some sample T24 test scripts - note that these are basic ones (not
with the full input of day, cycle, etc.)
Run Number Module Function Objective Description Product Reference Test Condition Reference Expected Result Actual
Result Pass/Fail Defect Id Executed By Executed On
1.1.1 Customer Customer Creation Create a partnership type customer Create a New Business Customer with 'Partnership' as customer type and Relationship as 'Director'. The
customer does not have any adverse info on any of the checks and the customer is eligible for FSCS and Free Banking [such as a product category code, name, menu item, etc] [such as Day 1, Week
1, Month 1, System Restore, etc - any condition where you are in some part of a cycle with T24 where yuu are inputting new tests under different system conditions or accrual cycles] System
should allow the user to create a New Business Customer with 'Partnership' as customer type and Relationship as 'Director' with FSCS eligibility. System should not escalate the application for
Manager reference as there is no adverse info in any of the checks
1.1.2 Customer Customer Modification Modification of customer Change the Gender of the Customer for 'Partnership' Customer Type System
should not allow the user to change the legal document type of the Customer for 'Partnership' Customer Type
1.1.3 Customer Customer Modification Modification of customer Change the Customer Mnemonic of the Customer for 'Partnership' Customer Type System
should allow the user to change the Customer Mnemonic of the Customer for 'Partnership' Customer Type
1.1.4 Customer Customer Modification Modification of customer Change the Telephone No of the Customer for 'Partnership' Customer Type System
should allow the user to change the Telephone No of the Customer for 'Partnership' Customer Type
1.1.5 Accounts Account Creation Create a XXXX bank clubs and societies account XXXXBank Club & Societies Account creation in GBP currency where the customer
age is equal to 18 and the Interest Rate type is 'Fixed'. The customer is provided with Cheque Facility and Internet Banking facility System
should allow the user to create the XXXXBank Club & Societies Account where the customer should be provided with Cheque and Internet Banking Facility (account should be opened only after AML check)
1.1.6 Accounts Account Creation AML check while creating Instant access account Request of AML and Credit Check by clicking on the button 'Confirm Account
Opening' The system should trigger a request for AML check and Credit Limit Check and the response received should get displayed in a new screen.
1.1.7 Accounts Account Creation Printing of Welcome Letter Printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the
account deal is committed. The system should print a Customer Welcome Letter (EOS) when AOS button is pushed after opening the Account.
1.1.8 Accounts Account modification Modify interest capitalisation frequency Modify the capitalization frequency to Yearly for an Active XXXXBank Club &
Societies Account System should not allow the user to modify the capitalization frequency to Yearly for an Active XXXXBank Club & Societies Account
1.1.9 Account Transactions Cash Deposit Perform cash deposit in XXXX bank clubs and societies account Cash deposit into an "Active" XXXX Bank Clubs and Societies Account at Branch
Counter in Local currency when Customer passes the ID and V User should be able to deposit the cash into the customers' XXXX bank Clubs and
Societies account successfully
1.1.10 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX bank clubs and societies account Cash withdrawal from an "active" XXXX Bank Young savers account with w
withdraw vouchers in local currency and the amount is less than GBP1200 User should be able to withdraw the cash from the customers' XXXX bank Clubs
and Societies account successfully
1.1.11 Account Transactions Cheque Issuance Auto replenishment of full cheque issuance Auto-Replenishment of full cheque cancerous for a new Clubs and societies
account holder at branch counter in base currency System should allow the user to print the Auto replenishment full cheque book for the customer
1.1.12 Fund Transfer Fund Transfer-Inter Account Initiate a Fund Transfer for account type XXXX Bank Clubs and Societies Account performing a Fund Transfer
for the 'XXXXBank Club & Societies Account' with Debit currency as 'GBP' and Credit currency as 'USD' with the Account Balance 'Equal to Debit amount' and the Exchange rate as 'Customer Level-Fixed'
with the value date as Current Date' and the charges waived Fund Transfer should happen for the XXXX bank Current accounts .
The amount is debited from the customer account and credited to the Beneficiary account
1.1.13 Fund Transfer Fund Transfer-Inter Account Collection of Fund transfer charges Charges to be collected in the Fund Transfer for the XXXX Club and societies account
No charges should be charged for the Fund Transfer
1.1.14 Account Transactions Cheque Issuance Cheque Issuance in a Dormant Account Full cheque issuance for existing Clubs and Societies "Dormant" account holder
at branch center in base currency System should allow the user to print the full cheque book in a sequential order only after resetting the Dormant
status to Active status
1.2.1 Customer Customer Creation Create a sole trader type customer Create a New Business Customer with 'Sole Trader' as customer type and Relationship as 'Nominated
Person'. The House Database check returns adverse info. The customer is eligible for Free Banking but not eligible for FSCS System should allow
the user to create a New Business Customer with 'Sole Trader' as customer type and Relationship as 'Nominated Person' with Free Banking facility. System should escalate the application for Manager
reference due to adverse info on House Database Check
1.2.2 Customer Customer Modification Modification of customer Change the DOB of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
System should allow the user to change the DOB of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
1.2.3 Customer Customer Modification Modification of customer Change the Marital Status of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
System should allow the user to change the Marital Status of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
1.2.4 Customer Customer Modification Modification of customer Change the No of Employees of the Customer for 'Sole Trader' Customer Type where the ID & V process
Passes System should allow the user to Change the No of Employees of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
1.2.5 Accounts Account Creation To create a XXXX International Business Account XXXX International Business Account creation in EUR currency where the customer
age is greater than 18 and the amount deposited is equal to the minimum balance amount. The Interest Rate Type is 'Floating'. The customer is provided with Cheque Facility and Internet Banking
facility System should allow the user to create the XXXX International Business Account in EUR currency with 'Floating' Interest Type where the customer has both
Cheque Facility and Internet Banking facility (account should be opened only after AML check)
1.2.8 Accounts Account modification Modify Statement frequency Modify the Statement Frequency to 'Yearly' for XXXX International Business Account in EUR currency
without any Charges debited from the customer account System should not allow the user to modify the Statement Frequency without debiting any charges from the
customer account
1.2.9 Account Transactions Cash Deposit Perform cash deposit in XXXX International Business Account cash deposit in foreign Currency account(EUR) in Account currency at branch
counter when the customer passes ID and V System should allow the user to make deposit the amount in EUR currency,into the customer account
1.2.10 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX International Business Account Cash withdrawal from a foreign currency account(EUR) in account
currency when the customer passes the ID and V and The amount exceeds GBP1200 System should allow the Head teller to withdraw the amount as all the criteria
met.
1.2.11 Account Transactions Cheque Issuance Perform a cheque issuance in a Foreign currency account Full cheque issuance for a new Foreign currency account(EUR) holder at branch
counter in base currency System should allow the user to print the full cheque book for the customer's foreign currency account
1.2.12 Account Transactions Cheque Deposit Perform a cheque deposit in a Foreign currency account "Active" Foreign currency account(EUR) cheque deposit into another "active"
XXXX bank Current account in local currency at branch counter System should allow the user to deposit the amount into the account and the
system should pass the proper entries into the Accounting package
1.2.13 Accounts Account modification Changing account status to Credit blocked Change the account status to 'Credit Block' for XXXX International Business
Account in EUR currency System should allow the user to change the account status to 'Credit Block' for XXXX International Business Account in EUR currency
1.3.1 Customer Customer Creation Create a sole trader type customer Create an Existing Business Customer with 'Sole Trader' as customer type and Relationship as 'Authorized
Signatory'. The customer does not have any adverse info on any of the checks including KYC Check System should allow the user to create an Existing Business Customer
with 'Sole Trader' as customer type and Relationship as 'Authorized Signatory' with FSCS eligibility. System should not escalate the application for Manager reference as there are no adverse info in
any of the checks Customer 100672 created
1.3.2 Customer Customer Modification Modification of customer Change the Name of the Customer for 'Sole Trader' Customer Type where the ID & V process gets failed
System should not allow the user to change the Name of the Customer for 'Sole Trader' Customer Type where the ID & V process gets failed Changed customer name from
"Sole trader" to "Sole trader modified"
1.3.3 Customer Customer Modification Modification of customer Change the Gender of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
System should allow the user to change the Mnemonic of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes Changed customer Mnemonic
from ST1 to ST121
1.3.4 Customer Customer Modification Modification of customer Change the Address of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
System should allow the user to change the Address of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes Changed customer address
from "234fdsgdg" to "123,Testing House "
1.3.5 Accounts Account Creation To create a XXXX International Business Account XXXX International Business Account creation in USD currency where the customer
age is equal to 18 and the amount deposited is greater than minimum balance amount. The Interest Rate Type is 'Periodic'. The customer is provided with Internet Banking facility
System should allow the user to create the XXXX International Business Account in USD currency with 'Periodic' Interest Rate where the customer is provided with Internet Banking
facility (account should be opened only after AML check)
1.3.8 Accounts Account modification Modify capitalisation frequency Modify the Capitalization Frequency to 'Monthly' for XXXX International Business Account in USD currency
System should allow the user to modify the Capitalization Frequency to 'Monthly' for XXXX International Business Account in USD currency
1.3.9 Account Transactions Cash Deposit Perform cash deposit in XXXX International Business Account (USD) Cash deposit in foreign Currency account(USD) in Account currency at
branch counter when the customer passes ID and V System should allow the user to make deposit In to the customer's USD account
1.3.10 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX International Business Account (USD) Cash withdrawal from a foreign currency account(USD) in account
currency when the customer passes the ID and V with withdrawal vouchers System should allow the teller to withdraw the amount as all the criteria met.
1.3.11 Account Transactions Cheque Issuance Perform a cheque issuance in a Foreign currency account Stand alone full cheque issuance for a new Foreign currency account(USD) holder
at branch counter in base currency System should allow the user to print the Stand alone full cheque book for the customer's Foreign currency(USD)
account
1.3.12 Account Transactions Cheque Issuance Perform a cheque issuance in a Foreign currency account walk in type cheque issuance for an new Foreign currency account(USD) holder at
branch counter in base currency System should allow the user to print the walk in type cheques for the new customer's foreign currency account(USD)
1.3.13 Account Transactions Cheque Issuance Perform a cheque issuance in a Foreign currency account Auto-Replenishment of Full type cheque issuance for an existing Foreign
currency account(USD) holder at branch counter in base currency System should allow the user to print the full cheques for the new customer's
foreign currency account(USD)
1.3.14 Account Transactions Cheque Deposit Perform a cheque deposit in a Foreign currency account To verify Depositing a back dated(less than 6 months) GBP cheque into Foreign
Currency account(USD) System should allow the user to make the deposit into the customer's USD account
1.4.1 Customer Customer Creation To create a Retail customer - Sole type Creation of a Retail Customer - Sole with all valid details entered.
System should allow to create a sole customer with all valid details entered.
1.4.2 Customer Customer Creation To create a Retail customer - Sole type request for AML check by clicking on 'Do AML' button in the customer screen.聽
request for Credit Check for the customer by clicking on 'Check Credit Limits' button. The system should trigger a request for AML check and Credit Limit Check and
the response received should get displayed in a new screen.
1.4.3 Accounts Account Creation To create an Instant Access Account for a Retail customer - sole type creation of Instant Access Account for a Sole Customer with Internet
Banking facility but no cheque book. 1. System should allow to create an Instant Access Account for a Sole Customer with Internet Banking facility but no
cheque book.
1.4.4 Accounts Account Creation To create an Instant Access Account for a Retail customer - sole type printing of Customer Welcome Letter (EOS) with valid customer data
along with population date when the account deal is committed. 2. The system should print a Customer Welcome Letter (EOS) when AOS button is
pushed after opening the Account.
1.4.5 Accounts Account Creation To create an Instant Access Account for a Retail customer - sole type request of Credit Check by clicking on the button 'Confirm Account
Opening' 3. The system should trigger a request for AML check and Credit Limit Check and the response received should get displayed in a new screen.
1.4.6 Account Transactions Cash Deposit Cash deposit in a XXXX bank Instant access account deposit Cash into an "Active" XXXX Bank Instant access Account at Branch
Counter in Local currency when Customer passes the ID and V User should be able to deposit the cash into the customers' XXXX bank Instant
access account successfully
1.4.7 Account Transactions Cash Withdrawal Cash withdrawal in a XXXX bank Instant access account withdraw Cash from an "active" XXXX Bank instant access account in local
currency at branch counter when the available balance is equal to transaction amount User should be able to withdraw the cash from the customers' XXXX bank Instant
a access account successfully
1.4.8 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using BACS The retail customer transfers a local currency greater than GBP 10000, Same Day through Generic payments
using Fund Transfer facility when the ID and V passes.
Both the accounts are active in status, No transaction charges applicable but the transaction required an authorization System should allow the user to select the beneficiary,amount to be
transferred and other verifications and send it to interface BACS. Further action will be taken care by BACS.
1.4.9 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using BACS To verify whether the existing UK Beneficiary is populated with the account setup details
System should populate existing UK Beneficiary details 聽
1. Beneficiary Name
2. Beneficiary A/c Number
3. Beneficiary Bank
4. Beneficiary Sort Code
1.4.10 Fund Transfer Fund Transfer-Inter Account Initiate a Inter account Fund Transfer in an instant access account Transfer the Fund for the 'Instant Access' accounts with the Debit and
Credit currency as 'LCY' and the Account Balance 'Equal to Debit amount' with the value date as 'Current date' with the waived charges 1. Fund
Transfer should happen for the Instant Access accounts
2. The amount is debited from the customer account and credited to the XXXX bank account
1.4.11 Fund Transfer Fund Transfer-Inter Account Charges collection for Fund transfer charges is collected in the Fund Transfer for the Instant Access accounts
1. No charges should be charged for the Fund Transfer
1.5.1 Customer Customer Creation Create a customer Sole Creation of a Retail Customer - Sole with some valid details entered. System
should allow to create a sole customer only if all valid details entered when the AML response is 'Refer'.
1.5.2 Customer Customer Creation Create a customer Sole request for AML check by clicking on 'Do AML' button in the customer screen.聽
1.5.3 Accounts Account Creation Create a XXXX Bank Current account Creation of XXXX Bank Current Account in GBP currency for Retail Customer - Joint with Statement
Frequency set as monthly along with Cheque Book and Internet Banking facility. 1. System should allow to create a XXXX Bank Current Account in GBP currency
for Retail Customer - Joint Statement Frequency set as monthly along with Cheque Book and Internet Banking facility.
1.5.4 Accounts Account Creation Create a XXXX Bank Current account printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the
account deal is committed. 2. The system should print a Customer Welcome Letter (EOS) when AOS button is pushed after opening the Account.
1.5.5 Accounts Account Creation Create a XXXX Bank Current account request of Credit Check by clicking on the button 'Confirm Account Opening' 3. The
system should trigger a request for AML check and Credit Limit Check and the response received should get displayed in a new screen.
1.5.12 Accounts IBAN Verification IBAN Verification To verify if the user is able to verify the generated IBAN for the created XXXX Bank Current Account which is manually
fed into the system System should generate the IBAN on successful creation of the account. The IBAN should be of 22 digits with country code as GB followed by
the check number generated through a check digit logic which is derived from the account number. The check number should be followed by the BIC and then the SORT code followed by the account number
Sort code incorrect in IBAN number. It is displayed as 000000
1.5.6 Account Transactions Customer Modification Amend Customer details amendment of surname for Retail Customer - Sole System
should allow to amend surname for a Retail Customer - Sole.
1.5.9 Account Transactions Cash Deposit Deposit cash into account t Cash deposit into an "Active" XXXX Bank Current Account at Branch Counter in Local currency when Customer
passes the ID and V User should be able to deposit the cash into the customers' XXXX bank Current account successfully
1.5.10 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using CHAPS a Business customer transfers a currency > GBP 10000 through Generic Payments
using Fund Transfer facility when user passes ID and V.
Both accounts are active and No charges applicable. System should allow the user to complete the transaction using the CHAPS interface.
1.5.11 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using CHAPS To verify whether the Beneficiary - UK Beneficiary (Utilities Company) is
created with the Account Set up with details:
Beneficiary Name
Beneficiary A/c Number
Beneficiary Bank
Beneficiary Sort Code
Reference A/c Number System should add the UK Beneficiary (Utilities Company) with the Beneficiary details:
1. Beneficiary Name should be available
2. Beneficiary A/c Number should be available
3. Beneficiary Bank should be available
4. Beneficiary Sort Code should be available
5. Reference A/c Number should be available
1.6.1 Customer Customer Creation Create a Customer -Sole Creation of a Retail Customer - Sole with all valid details entered. System
should allow to create a sole customer with all valid details entered. The customer was created successfully
1.6.2 Customer Customer Creation Create a Customer -Sole request for AML check by clicking on 'Do AML' button in the customer screen.
1.6.3 Accounts Account Creation Create a FCY account(EUR) Creation of XXXX Bank FCY Account in EUR currency for Retail Customer - Sole with Cheque Book but no
Internet Banking facility. 1. System should allow to create a XXXX Bank FCY Account in EUR currency for Retail Customer - Sole. Account 10001536 was
successfully created.
1.6.4 Accounts Account Creation Create a FCY account(EUR) printing of Customer Welcome Letter (AOS) with valid customer data along with population date when the
1.6.5 Accounts Account Creation Create a FCY account(EUR) request of Credit Check by clicking on the button 'Confirm Account Opening' 3. The
1.6.13 Accounts IBAN Verification IBAN Verification To verify if the user is able to verify the generated IBAN for the created XXXX Bank Foreign Currency accounts which
is manually fed into the system System should generate the IBAN on successful creation of the account. The IBAN should be of 22 digits with country
code as GB followed by the check number generated through a check digit logic which is derived from the account number. The check number should be followed by the BIC and then the SORT code followed
by the account number Sort code incorrect in IBAN number. It is displayed as 000000
1.6.6 Account Transactions Cash Deposit Deposit cash into account cash deposit in foreign Currency account(EUR) in Account currency at branch counter when the customer
passes ID and V System should allow the user to make the deposit into the customer's EUR account Amount 773.85 deposited
successfully
1.6.7 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter withdrawal from a foreign currency account(EUR) in account currency when the customer passes the ID and V
and The amount exceeds GBP1200 System should allow the Head teller to withdraw the amount as all the criteria met. Amount 1300 withdrawal was
successful
1.6.8 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter withdrawal from a foreign currency account(EUR) in account currency when the customer passes the ID and V
and The withdrawal makes the available balance go beyond the minimum required balance System should not allow the teller to withdraw the amount as the withdrawal
makes the available balance go beyond required minimum balance.
1.6.9 Account Transactions Cheque issuance Issue full cheque to the account full cheque issuance for a new Foreign currency account(EUR) holder at branch counter in base currency
System should allow the user to print the full cheque book for new foreign currency account holder
1.6.10 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using SWIFT the retail customer holding a foreign currency account( EUR) transfers the
amount(over equivalent to GBP 2500) to another Foreign currency account (USD) through Generic Payments using Fund Transfer facility when user passes ID and V.
Both the accounts are active charges are as applicable System should allow the user to complete the transaction using the SWIFT interface to send messages and
further to take the transaction to the authorizer
1.6.11 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using Faster Payments a business customer can transfer a foreign currency which is between GBP 1000
and GBP10000, through Generic Payments using Fund Transfer facility when user passes ID and V.
Both the accounts are active,no charges and the transaction is future dated. System should allow the user to take the request from the customer to perform
the transaction on particular day using Faster Payments Interface as the transaction is future dated.
1.6.12 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using Faster Payments To verify whether the International Beneficiary is created with the Account Set
up with details:
Beneficiary Name
Beneficiary IBAN ( Bank A/c Number)
Beneficiary Bank
Beneficiary Bank Swift Code System should add the International Beneficiary with the Beneficiary details:
1. Beneficiary Name
2. Beneficiary IBAN (Intl Bank A/c Number)
3. Beneficiary Bank
4. Beneficiary Bank Swift Code
1.7.1 Customer Customer Creation Create a Customer -Sole Creation of a Retail Customer - Sole with all valid details entered. System
should allow to create a sole customer with all valid details entered.
1.7.2 Customer Customer Creation Create a Customer -Sole request for AML check by clicking on 'Do AML' button in the customer screen.
1.7.3 Accounts Account Creation Create FCY account(USD) Creation of XXXX Bank FCY Account in USD currency for Retail Customer - Sole with all valid details.
1. System should allow to create a XXXX Bank FCY Account in USD currency for Retail Customer - Sole.
2. The system should print a Customer Welcome Letter (EOS) when AOS button is pushed after opening the Account.
3. The system should trigger a request for AML check and Credit Limit Check and the response received should get displayed in a new screen.
1.7.4 Account Transactions Customer Modification Amend Customer details Amendment of Date of Birth for Retail Customer - Sole
System should allow to amend the Delivery Channels for a Retail Customer - Sole
1.7.5 Account Transactions Cash Deposit Deposit cash into account cash deposit in foreign Currency account(USD) in Account currency at branch counter when the customer
passes ID and V System should allow the user to make the deposit into the customer's USD account
1.7.6 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using SEPA the retail customer holding a foreign currency account( USD) transfers the amount(up to equivalent to GBP
2500) EURO ZONE/Intl to another Foreign currency account (EUR) through Generic Payments using Fund Transfer facility when user passes ID and V.
Both the accounts are active charges are as applicable.and the transaction is a future dated. System should allow the user to use SEPA Interface to complete the transaction
successfully.
1.7.7 Fund Transfer Fund Transfer-Generic PaymentsInitiate a Fund Transfer Using SEPA To verify whether the Euro Zone Beneficiary is created with the Account Set up with details:聽
Beneficiary Name
Beneficiary IBAN (Intl Bank A/c Number)
Beneficiary Bank
Beneficiary Bank Swift Code System should add the Euro Zone Beneficiary with the Beneficiary details 聽
1. Beneficiary Name
2. Beneficiary IBAN (Intl Bank A/c Number)
3. Beneficiary Bank
4. Beneficiary Bank Swift Code
1.7.8 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter withdrawal from a foreign currency account(USD) in account currency when the customer passes the ID and V
with withdrawal vouchers System should allow the teller to withdraw the amount as all the criteria met.
1.7.9 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter withdrawal from a foreign currency account(USD) in account currency when the customer passes the ID and V
with withdrawal vouchers where withdrawal makes the account balance goes beyond the minimum limit System should not allow the teller to withdraw the amount as the
balance goes beyond the minimum balance.
1.7.10 Account Transactions Cheque issuance Issue Stand alone full cheque to the account Stand alone full cheque issuance for a new Foreign currency account(USD) holder
at branch counter in base currency System should allow the user to print the full cheque book for a new foreign currency account holder
1.7.11 Account Transactions Cheque issuance Issue a walk in type Cheque to the account walk in type cheque issuance for an new Foreign currency account(USD) holder at
branch counter in base currency System should allow the user to print the full cheque book for a new foreign currency account holder
1.8.1 Customer Customer Creation Create a customer -Under 16 Creation of a Retail Customer - Under 16 with all valid details. System
should allow to create a Retail Customer - Under 16 with all valid details.
1.8.2 Customer Customer Creation Create a customer -Under 17 request for AML check by clicking on 'Do AML' button in the customer screen.
1.8.3 Accounts Account Creation Create a Young Savers account Young Savers Account creation for a Retail Customer - Under 16 with Internet Banking facility but no
cheque book. 1. System should allow to create a Young Savers Account for Retail Customer - Under 16 with Internet Banking facility but no cheque book.
1.8.4 Accounts Account Creation Create a Young Savers account printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the
1.8.5 Accounts Account Creation Create a Young Savers account request of Credit Check by clicking on the button 'Confirm Account Opening' 3 The
1.8.6 Account Transactions Customer Modification Amend Customer details amendment of Marital Status for Retail Customer - Under 16
System should not allow to amend or input the Marital Status for Retail Customer - Under 16
1.8.7 Account Transactions Cash Deposit Deposit cash into account the Cash deposit into an "Active" XXXX Bank Young Savers Account at Branch Counter in Local currency when
Customer passes the ID and V User should be able to deposit the cash into the customers' XXXX bank Young savers account successfully
1.8.8 Fund Transfer Fund Transfer-Inter Account Initiate a Fund Transfer for account type Young Savers Account the Fund Transfer is allowed for the 'Young Savers Account' with the
Debit and Credit currency as 'LCY' and the Account Balance 'Greater than Debit Amount' and Debit account status as 'Credit Blocked' with the value date as 'Current date' and charges should be present
1. Fund Transfer should happen for the Young Savers accounts
2. The amount is debited from the customer account and credited to the Beneficiary account
1.8.9 Fund Transfer Fund Transfer-Inter Account Collection of Fund transfer charges the charges are collected in the Fund Transfer for the Young Savers accounts 1. Charges
should be applicable
1.5.13 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter Cash withdrawal from Customer's "Active" XXXX bank Current Account in Local currency in store using cash
withdrawal vouchers. System should allow the Teller to withdraw the amount from customer's XXXX Bank Current account by accepting withdraw vouchers and give the
receipt to the customer
1.5.14 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter Cash withdrawal from Customer's "Active" XXXX bank Current Account in Local currency From any ATM.
System should allow the customer to withdraw the amount from customer's XXXX Bank Current account after successful authentication and give the receipt to the customer
1.8.10 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter cash withdrawal from an "active" XXXX Bank Young savers account with withdraw vouchers in local currency
and the amount is less than GBP1200 User should be able to withdraw the cash into the customers' XXXX bank Young Savers account successfully
1.8.11 Account Transactions Cash Withdrawal Withdraw Cash From Branch counter local currency withdrawal from ATM for the active account XXXX bank Instant access account
System should not allow the customer to withdraw the amount from ATM as ATM facility is not available for Young savers account.
1.9.1 Customer Customer Creation Create Customer -Joint Creation of a Retail Customer - Joint with all valid details. System
should allow to create a Retail Customer - Joint with all valid details.
1.9.2 Customer Customer Creation Create Customer -Joint request for AML check by clicking on 'Do AML' button in the customer screen.聽
check request for Credit Check for the customer by clicking on 'Check Credit Limits' button. The system should trigger a request for AML check and Credit Limit Check and
1.9.3 Accounts Account Creation Create a XXXX bank Cash Account Creation of XXXX Bank Cash Account for Retail Customer - Under 16 in GBP currency with customer age
greater than min required, with Internet Banking and no cheque book. System should allow to create a XXXX Bank Savings Account for Retail Customer -
Under 16. Created Individual Customer
1.9.4 Accounts Account Creation Create a XXXX bank Cash Account printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the
account deal is committed.
request of Credit Check by clicking on the button 'Confirm Account Opening' 2. The system should print a Customer Welcome Letter (EOS) when AOS button is
1.9.5 Accounts Account modification Account Amendment Amendment of Statement Frequency for a XXXX Bank Cash Account to Monthly System
should not allow to amend the Statement Frequency to Monthly for XXXX Bank Cash account as it has only yearly statement frequency Statement preferences can
be modified
1.9.6 Accounts Account modification Account Amendment Amendment of Statement Frequency for a XXXX Bank Cash Account to Yearly System
should allow to amend the Statement Frequency to Yearly Statement preferences can be modified
1.9.7 Account Transactions Cash Deposit Cash Deposit Deposit Cash into an "Active" XXXX Bank Cash Account at Branch Counter in Local currency when Customer failed the ID
and V System should not allow the user to make a deposit as customer failed to give the proper ID and V
1.9.8 Account Transactions Cash Deposit Cash Deposit To verify the Cash deposit into an "Active" XXXX Bank Cash Account at Branch Counter in Local currency when Customer
passes the ID and V System should allow the user to make a deposit in to the XXXX Bank Cash Account customer as he passes the ID and V Successfully
deposited Credited 100000
1.9.9 Account Transactions Cash Withdrawal Cash Withdrawal Cash withdrawal from Customer's "Active" XXXX bank Cash Account in Local currency in store using cash withdrawal
vouchers. System should allow the user to withdraw amount from the XXXX Cash account Withdrawal of 500
1.9.10 Fund Transfer Fund Transfer-Inter Accounts Initiate a Fund Transfer to check the day limit Fund Transfer is allowed 'beyond the Daily set limit' for the 'XXXX bank Cash
accounts' with the Debit and Credit currency as 'LCY' and the Account Balance 'Equal to Debit amount' with the value date as 'Future Date' with waived charges 1.
Confirmation from the customer should be done before Transferring the fund as the amount exceeds the daily limit.聽
2. Fund Transfer should happen for the XXXX Bank Cash accounts
3. The amount is debited from the customer account and credited to the Beneficiary account Account transfer was successful
1.9.11 Fund Transfer Fund Transfer-Inter Accounts Collection of Fund transfer charges The charges is collected in the Fund Transfer for the XXXX Bank Cash account 1. No
charges should be charged for the Fund Transfer Charges has been waived
1.9.12 Fund Transfer Fund Transfer-Inter Accounts Initiate a Fund Transfer into credit blocked account The Fund Transfer is allowed for the 'XXXX Bank Cash accounts' with the Credit
account status as 'Credit Blocked' and Debit and Credit currency as 'LCY' and the Account Balance 'Greater than Debit amount' with the value date as 'Future date' with the charges allowed
Fund Transfer should not happen for the Credit Blocked accounts Account 10005469 - Post No Credits
1.9.13 Fund Transfer Fund Transfer-Generic PaymentsInitiate a same day Fund Transfer The retail customer transfers a local currency GBP 1000, Same Day through Generic payments using Fund
Transfer facility when the ID and V Fails.
Both the accounts are active in status, No transaction charges applicable but the transaction required an authorization System should not allow the user to start any transaction as the
customer failed to give the proper ID and V
1.9.14 Fund Transfer Fund Transfer-Generic PaymentsInitiate a same day Fund Transfer The retail customer transfers a local currency greater than GBP 10000, Same Day through Generic payments
using Fund Transfer facility when the ID and V passes.
Both the accounts are active in status, No transaction charges applicable but the transaction required an authorization System should not allow the user to continue the transaction as the
Interface has been set up limit for transfer up to GBP 10000 and the actual transaction amount is exceeding
1.6.14 Account Transactions Cheque Issuance Cheque Issuance for a new customer stand alone walk in type cheque issuance for a new Foreign currency account(EUR) holder at branch counter
in base currency System should allow the user to print the full cheque book for a new foreign currency account holder
1.6.15 Account Transactions Cheque Issuance Cheque Issuance for a new customer stand alone full cheque issuance for a new Foreign currency account(EUR) holder at branch counter in base
currency System should allow the user to print the full cheque book for a new foreign currency account holder
1.6.16 Account Transactions Cheque Issuance Cheque Issuance for a existing customer Auto-Replenishment of Full type cheque issuance for an existing Foreign
currency account(EUR) holder at branch counter in base currency System should allow the user to print the full cheque book for a new foreign
currency account holder
1.6.17 Account Transactions Cheque deposit Foreign Currency Cheque deposit "active" Foreign currency (EUR) cheque deposit into another "active" Foreign currency (USD) account in
USD at branch counter System should allow the user to deposit the amount into the account and the system should pass the proper entries into the Accounting
package
1.6.18 Account Transactions Cheque deposit Foreign Currency Cheque deposit "active" Foreign currency (EUR) cheque deposit into another "active" Foreign currency account(EUR) in
base currency at branch counter System should allow the user to deposit the amount into the account and the system should pass the proper entries into
the Accounting package
1.5.15 Account Transactions Cheque deposit Foreign Currency Cheque deposit Local Currency Cheque deposit of XXXX bank current account into another "active" XXXX bank Current
Account at branch counter. System should allow the teller to credit the Customer's XXXX Bank account wit h the Deposit cheque amount.
1.7.12 Account Transactions Cheque deposit Foreign Currency Cheque deposit Foreign Currency Cheque deposit of XXXX bank current account into another "active" Foreign currency (USD)
Account at branch counter. System should allow the teller to credit the Customer's XXXX Bank account wit h the Deposit cheque amount.
1.7.13 Account Transactions Cheque deposit Foreign Currency Cheque deposit Local Currency Cheque deposit of XXXX bank current account into another "dormant" XXXX bank Current
Account at branch counter. System should not allow the teller to credit the Customer's XXXX Bank account as the account status is dormant.
1.7.14 Account Transactions Cheque deposit Future dated Foreign Currency Cheque deposit Local Currency future dated Cheque deposit of XXXX bank current account into
another "active" XXXX bank Current Account at branch counter. System should not allow the teller to credit the Customer's XXXX Bank account
as the cheque is future dated.
1.16.1 Fixed Deposits Creating a fixed Deposit To create a Fixed Term Savings Account 1 Check whether the system is able to create Fixed Term Savings Account 1 for a
duration of 6 months in GBP currency with interest rate as 2% System should allow to create a Fixed Term Savings Account 1 for a duration of
6 months in GBP currency with interest rate as 2% Fixed Term Savings Account 1 created
1.17.1 Fixed Deposits Creating a fixed Deposit To create a Fixed Term Savings Account 2 Check whether system is able to create the Fixed Term Savings Account 2 for a
duration of 1 Year in GBP currency with interest rate as 2.25% System should allow to create a Fixed Term Savings Account 2 for a duration of
1 Year in GBP currency with interest rate as 2.25% Fixed Term Savings Account 2 created
1.18.1 Fixed Deposits Creating a fixed Deposit To create a Fixed Term Savings Account 3 Check whether the system is able to create the Fixed Term Savings Account 3 for
a duration of 3 Years (5 Months) in GBP currency with interest rate as 3% System should allow to create a Fixed Term Savings Account 3 for a duration of
3 Year (5 Months) in GBP currency with interest rate as 3% Fixed Term Savings Account 3 created
1.18.2 Fixed Deposits Creating a fixed Deposit To create a Fixed Term Savings Account 3.1 Check whether the Fixed Term Savings Account 3.1 for a duration of 3 Years (4
Months) in GBP currency with interest rate as 3% System should allow to create a Fixed Term Savings Account 3.1 for a duration of 3 Year (4 Months) in GBP
currency with interest rate as 3% Fixed Term Savings Account 3.1 created
1.19.1 Fixed Deposits Creating a fixed Deposit To create a Fixed Term Savings Account 4 Check whether the Fixed Term Savings Account 4 for a duration of 5 Years (3
Months) in GBP currency with interest rate as 4% System should allow to create a Fixed Term Savings Account 4 for a duration of 5 Year (3 Months) in GBP
currency with interest rate as 4% Fixed Term Savings Account 4 created
1.19.2 Fixed Deposits Creating a fixed Deposit To create a Fixed Term Savings Account 4.1 Check whether the Fixed Term Savings Account 4.1 for a duration of 5 Years (5
Months) in GBP currency with interest rate as 4% System should allow to create a Fixed Term Savings Account 4 for a duration of 5 Year (5 Months) in GBP
currency with interest rate as 4% Fixed Term Savings Account 4.1 created
1.20.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Client Premium Deposit Account with tier 1 Interest rate Check whether the system
allows to create XXXX Client Premium Deposit Account where the customer age is greater than 16 with 'Fixed' Interest rate type. The amount deposited is less than GBP25k with Tier 1 Interest rate. The
customer is provided with Internet Banking Facility. The product has a monthly Capitalization Frequency and monthly Account Statement Frequency with the maturity date after 6 months
System should allow the user to create the XXXX Client Premium Deposit Account with Tier 1 Interest Rate where the customer has a monthly Capitalization Frequency and monthly Account
Statement Frequency with the maturity date as 6 months. Unable to mark the Interest Capitalization as 'Yes'
allows to create XXXX Client Premium Deposit Account where the customer age is greater than 16 with 'Fixed' Interest rate type. The amount deposited is less than GBP50k with Tier 2 Interest rate. The
customer is provided with Internet Banking Facility. The product has a monthly Capitalization Frequency and monthly Account Statement Frequency with the maturity date after 3months
System should allow the user to create the XXXX Client Premium Deposit Account with Tier 2 Interest Rate where the customer is provided with Internet Banking Facility. Customer should
have a monthly Capitalization Frequency and monthly Account Statement Frequency Unable to mark the Interest Capitalization as 'Yes'
allows to create XXXX Client Premium Deposit Account where the customer age is greater than 16 with 'Fixed' Interest rate type. The amount deposited is less than GBP100k with Tier 3 Interest rate.
The customer is provided with Internet Banking Facility. The monthly Account Statement Frequency with the maturity date after 3 months System
should allow the user to create the XXXX Client Premium Deposit Account with Tier 3 Interest Rate where the customer is provided with Internet Banking Facility. The customer should have a monthly
Account Statement Frequency XXXX Client Premium Deposit Account created
allows to create XXXX Client Premium Deposit Account where the customer age is greater than 16 with 'Fixed' Interest rate type. The amount deposited is less than GBP250k with Tier 4 Interest rate.
The customer is provided with Internet Banking Facility. The monthly Account Statement Frequency with the maturity date after 1 month. System
should allow the user to create the XXXX Client Premium Deposit Account with Tier 4 Interest Rate where the customer is provided with Internet Banking Facility. The customer should have monthly
allows to create XXXX Client Premium Deposit Account where the customer age is greater than 16 with 'Fixed' Interest rate type. The amount deposited is less than GBP1M with Tier 5 Interest rate. The
customer is provided with Internet Banking Facility. monthly Account Statement Frequency with the maturity date after 6 months System should allow
the user to create the XXXX Client Premium Deposit Account with Tier 5 Interest Rate where the customer is provided with Internet Banking Facility. The customer should have a monthly Account
Statement Frequency XXXX Client Premium Deposit Account created
allows to create XXXX Client Premium Deposit Account where the customer age is greater than 16 with 'Fixed' Interest rate type. The amount deposited is greater than GBP1M with Tier 6 Interest rate.
The customer is provided with Internet Banking Facility. The monthly Account Statement Frequency with the maturity date after 1 Year System
should allow the user to create the XXXX Client Premium Deposit Account with Tier 6 Interest Rate where the customer is provided with Internet Banking Facility. The customer should have a monthly
1.26.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Treasury/Money Market Deposits Account with the Fixed Interest Rate type Check whether the system
allows to create XXXX Bank Treasury/Money Market Deposits Account where the customer age is greater than 18 with 'Fixed' Interest rate type. The amount deposited is greater than 25000. The customer
does not opt for Internet Banking Facility. The product has a monthly Capitalization Frequency and monthly Account Statement Frequency with the maturity date after 3 months
System should allow the user to create the XXXX Bank Treasury/Money Market Deposits Account with 'Fixed' Interest Rate type. The customer should not have the Internet Banking Facility.
The customer should have a monthly Capitalization Frequency and monthly Account Statement Frequency
1.27.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Treasury/Money Market Deposits Account with the Notice Interest Rate type Check whether the system
allows to create XXXX Bank Treasury/Money Market Deposits Account creation where the customer age is greater than 18 with 'Notice' Interest rate type. The amount deposited is greater than 25000. The
customer is provided with Internet Banking Facility. The product has a monthly Capitalization Frequency and monthly Account Statement Frequency with the maturity date after 3 months
System should allow the user to create the XXXX Bank Treasury/Money Market Deposits Account with 'Notice' Interest Rate Type where the customer is provided with Internet banking
Facility. The customer should have a monthly Capitalization Frequency and monthly Account Statement Frequency
1.28.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Treasury/Money Market Deposits Account with the Call Interest Rate type Check whether the system
allows to create XXXX Bank Treasury/Money Market Deposits Account creation where the customer age is greater than 18 with 'Call' Interest rate type. The amount deposited is greater than 25000. The
customer does not opt for Internet Banking Facility. The product has a monthly Capitalization Frequency and monthly Account Statement Frequency with the maturity date after 3 months
System should allow the user to create the XXXX Bank Treasury/Money Market Deposits Account with 'Call' Interest Rate Type. The customer should not have the Internet Banking Facility.
The customer should have a monthly Capitalization Frequency and monthly Account Statement Frequency
1.29.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Fixed Term Business Account with 3 maturity Check whether the system allows to create XXXX Bank Fixed Term
Business Account - 3M where the customer age is greater than 18 with 'Fixed' Interest rate type. The amount deposited is equal to 5000 with 0.45 Interest rate. The customer does not opt for Internet
Banking Facility. The product has a monthly Capitalization Frequency and Account Statement Frequency generated at maturity with the maturity date after 3 months System
should allow the user to create the XXXX Bank Fixed Term Business Account - 3M with Fixed Interest type. The customer should not have the Internet Banking Facility. The customer should have a monthly
Capitalization Frequency and Account Statement Frequency generated at maturity
1.30.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Fixed Term Business Account with 6 months maturity Check whether the system
allows to create XXXX Bank Fixed Term Business Account - 6M where the customer age is greater than 18 with 'Fixed' Interest rate type. The amount deposited is greater than 5000 with 0.45 Interest
rate. The customer is provided with Internet Banking Facility. The Capitalization of Interest is calculated at maturity and Account Statement Frequency generated at the end of every 6th month
System should allow the user to create the XXXX Bank Fixed Term Business Account - 6M with Fixed Interest type where the customer is provided with Internet Banking
Facility. The Capitalization of Interest should be calculated at maturity and the Account Statement Frequency should be generated at the end of every 6th month
1.31.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Fixed Term Business Account with 1 year maturity Check whether the system
allows to create XXXX Bank Fixed Term Business Account - 1Y creation where the customer age is greater than 18 with 'Fixed' Interest rate type. The amount deposited is greater than 5000 with 0.55
Interest rate. The customer is provided with Internet Banking Facility. The product has a yearly Capitalization Frequency and Account Statement Frequency generated at the end of every 6th month
System should allow the user to create the XXXX Bank Fixed Term Business Account - 1Y with Fixed Interest type where the customer is provided with Internet Banking
Facility. The Capitalization Frequency should be Yearly and the Account Statement Frequency should be generated at the end of every 6th month
1.32.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Fixed Term Business Account with 2 year maturity Check whether the system
allows to create XXXX Bank Fixed Term Business Account - 2Y creation where the customer age is greater than 18 with 'Fixed' Interest rate type. The amount deposited is greater than 5000 with 1.15
Interest rate. The customer does not opt for Internet Banking Facility. The Capitalization of Interest is calculated at maturity and Account Statement Frequency generated at the end of every 6th
month System should allow the user to create the XXXX Bank Fixed Term Business Account - 2Y with Fixed Interest type. The customer should not have the Internet
Banking Facility. The Capitalization of Interest should be calculated at maturity and the Account Statement Frequency should be generated at the end of every 6th month
1.33.1 Fixed Deposits Creating a fixed Deposit To create a XXXX Bank Fixed Term Business Account with 3 year maturity XXXX Bank Fixed Term
Business Account - 3Y creation where the customer age is greater than 18 with 'Fixed' Interest rate type. The amount deposited is greater than 5000 with 1.25 Interest rate. The customer is provided
with Internet Banking Facility. The product has a yearly Capitalization Frequency and Account Statement Frequency generated at the end of every 6th month System
should allow the user to create the XXXX Bank Fixed Term Business Account - 3Y with Fixed Interest type where the customer is provided with Internet Banking Facility. The Capitalization Frequency
should be Yearly and the Account Statement Frequency should be generated at the end of every 6th month
1.34.1 Fixed Deposits Deposit Account Creation To create a XXXX Client Premium Deposit Account with customer age less than 16 Check whether the system
allows to create a XXXX Client Premium Deposit Account creation with customer age less than 16 System should not allow the user to create the XXXX Client Premium
Deposit Account with customer age less than 16
1.10.1 Customer Customer Creation Create a limited company type customer Create an Existing Business Customer with 'Limited Company' as customer type
and Relationship as 'Business Owner'. The customer does not have any adverse info on any of the checks and the customer is eligible for FSCS and Free Banking System
should allow the user to create an Existing Business Customer with 'Limited Company' as customer type and Relationship as 'Business Owner' with FSCS eligibility. System should not escalate the
application for Manager reference as there are no adverse info in any of the checks
1.10.2 Customer Customer Modification Modification of customer Change the DOB of the Customer for 'Limited Company' Customer Type System
should not allow the user to change the DOB of the Customer for 'Limited Company' Customer Type
1.10.3 Customer Customer Modification Modification of customer Change the Company Reg No of the Customer for 'Limited Company' Customer Type System
should allow the user to change the Company Reg No of the Customer for 'Limited Company' Customer Type
1.10.4 Accounts Creating a Business Account To create a XXXXBank Business Instant Access Account XXXXBank Business Instant Access Account creation in GBP currency where the
customer age is greater than 18. The Interest Rate Type is 'Fixed' and the minimum balance is less than GBP100k with Tier 1 Interest Rate. The customer is provided with Internet Banking facility and
the tax is applicable on the accrued interest System should allow the user to create the XXXXBank Business Instant Access Account in GBP currency with
Tier 1 Interest Rate where the customer is provided with Internet Facility
1.10.5 Accounts Creating a Business Account AML check while creating XXXXBank Business Instant Access Account Request of AML and Credit Check by clicking on the button 'Confirm
Account Opening' The system should trigger a request for AML check and Credit Limit Check and the response received should get displayed in a new screen.
1.10.6 Accounts Creating a Business Account Printing of Welcome Letter Printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the
1.10.15 Accounts IBAN Verification IBAN Verification To verify if the user is able to verify the generated IBAN for the created XXXX Bank Instant Access
System should generate the IBAN on successful creation of the account. The IBAN should be of 22 digits with country code as GB followed by the check number generated through a check
digit logic which is derived from the account number. The check number should be followed by the BIC and then the SORT code followed by the account number Sort code incorrect in IBAN
number. It is displayed as 000000
1.10.7 Accounts Modifying a Business Account Modify account status Modify the account status to 'All Blocked' for XXXXBank Business Instant Access Account with Tier 1 Interest Rate
System should allow the user to change the account status to 'All Blocked' for XXXXBank Business Instant Access Account with Tier 1 Interest Rate
1.10.8 Accounts Closing a Business Account To close a XXXXBank Business Instant Access Account Close the XXXXBank Business Instant Access Account with Tier 1 Interest Rate
with Credit Balance where the Credit Account is in Both Credit & Debit Blocked status System should not allow the user to close the XXXXBank Business Instant Access
Account with Tier 1 Interest Rate with Credit Balance where the Credit Account is in Both Credit & Debit Blocked status
1.10.9 Accounts Modifying a Business Account Modify account status Modify the account status to 'All Active' for XXXXBank Business Instant Access Account with Tier 1 Interest Rate
System should allow the user to change the account status to 'All Active' for XXXXBank Business Instant Access Account with Tier 1 Interest Rate
1.10.10 Account Transactions Cash Deposit Perform cash deposit in XXXX Business Instant access (GBP) Local currency cash deposit into An "active" XXXX Business Instant access
account at branch counter when the customer passes the ID and V System should allow the user to make deposit into the Business Instant access
account.
1.10.11 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX Business Instant access (GBP) Local currency cash withdrawal from An "active" XXXX Business Instant access
account at branch counter when the customer passes the ID and V System should allow the user to withdraw from the business instant access
account.
1.10.12 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX Business Instant access (GBP) Local currency cash withdrawal from An "active" XXXX Business Instant access
account over the Telephone when the customer passes the ID and V System should allow the user to accept the request for withdrawal over the
telephone and to take further action.
1.10.13 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX Business Instant access (GBP) Local currency cash( <1200) withdrawal from An "active" XXXX Business Instant
access account at ATM System should not allow the customer to withdraw as ATM facility is not available for this ac count type.
1.10.14 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX Business Instant access (GBP) Foreign currency cash withdrawal from An "active" XXXX Business Instant access
account at branch counter when the customer passes the ID and V System should allow the user to withdraw Foreign currency as multi currency
transaction is not allowed for XXXX Business instant access account
1.11.1 Customer Customer Creation Create a community type customer Create an Existing Business Customer with 'Community' as customer type and Relationship as 'Business
Owner'. The customer does not have any adverse info on any of the checks and the customer is eligible for FSCS but without Free Banking facility System
should allow the user to create an Existing Business Customer with 'Community as customer type and Relationship as 'Authorized Signatory' with FSCS eligibility. System should not escalate the
application for Manager reference as there are no adverse info in any of the checks Created Community customer
1.11.2 Customer Customer Modification Modification of customer Change the Name of the Customer for 'Sole Trader' Customer Type where the ID & V process gets failed
System should not allow the user to change the Name of the Customer for 'Sole Trader' Customer Type where the ID & V process gets failed Full name: Community
changed to Sole Trader1
Short name: Comm changed to Sole Trader
1.11.3 Customer Customer Modification Modification of customer Change the Gender of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
System should allow the user to change the Gender of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes Changed from C12354 to
C123546
1.11.4 Customer Customer Modification Modification of customer Change the Address of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes
System should allow the user to change the Address of the Customer for 'Sole Trader' Customer Type where the ID & V process Passes Changed from 123 barrier
point to 123Testing House
customer age is greater than 18. The Interest Rate Type is 'Fixed' and the minimum balance is greater than GBP100k but less than GBP250k with Tier 2 Interest Rate. The customer is provided with
Internet Banking facility and the tax is applicable on the accrued interest System should allow the user to create the XXXXBank Business Instant Access
Account in GBP currency with Tier 2 Interest Rate where the customer is provided with Internet Banking Facility Business Instant Access Account is created
1.11.7 Accounts Creating a Business Account Printing of Welcome Letter Printing of Customer Welcome Letter (AOS) with valid customer data along with population date when the
1.11.8 Accounts Modifying a Business Account Modify account status Modify the Statement Frequency to 'Yearly' for XXXXBank Business Instant Access Account with Tier 2 Interest Rate
System should allow the user to modify the Statement Frequency to 'Yearly' and should debit the relevant charges from the customer account Statement preferences can
be modified
1.11.9 Accounts Account Closure Closing of XXXX bank business Instant access account Close the XXXXBank Business Instant Access Account with Tier 2 Interest Rate
with Debit Balance where the Credit Account is in Active status System should allow the user to close the XXXXBank Business Instant Access
Account with Tier 2 Interest Rate with Debit Balance where the Credit Account is in Active status Need to close the Account after checking the Accrual
1.11.10 Accounts Interest Accrual Interest Accrual of XXXX bank business Instant access account Interest gets accrued on the second day for the deposited amount for the
XXXXBank Business Instant Access Account with Tier 2 Interest Rate System should accrue the interest on the second day for the deposited amount
for the XXXXBank Business Instant Access Account with Tier 2 Interest Rate Deposited 5000 to the account.聽
ACCRUAL CR AMT: 0.03
Condition Group: 18
1.12.1 Customer Customer Creation Create a community type customer Create an Existing Business Customer with 'Community' as customer type and Relationship as 'Business
Owner'. The customer does not have any adverse info on any of the checks and the customer is eligible for FSCS but without Free Banking facility System
should allow the user to create an Existing Business Customer with 'Community' as customer type and Relationship as 'Business Owner' with FSCS eligibility but without Free Banking facility. System
should not escalate the application for Manager reference as there are no adverse info in any of the checks Business Owner relationship is not available
1.12.2 Customer Customer Modification Modification of customer Change the Marital Status of the Customer for 'Community' Customer Type System
should not allow the user to change the Marital Status of the Customer for 'Community' Customer Type Marital status cannot be modified for the Business Customer
1.12.3 Customer Customer Modification Modification of customer Change the Name of the Customer for 'Community' Customer Type System
should allow the user to change the Name of the Customer for 'Community' Customer Type Customer name is changed for the Business customer
1.12.4 Customer Customer Modification Modification of customer Change the Legal ID of the Customer for 'Community' Customer Type System
should allow the user to change the Legal ID of the Customer for 'Community' Customer Type Legal ID is changed for the Business Customer
1.12.5 Customer Customer Modification Modification of customer Change the Marketing Preferences of the Customer for 'Community' Customer Type System
should allow the user to change the Marketing Preferences of the Customer for 'Community' Customer Type Marketing preferences can be modified
customer age is greater than 18. The Interest Rate Type is 'Fixed' and the minimum balance is less than GBP1M with Tier 3 Interest Rate. The customer opt for Internet Banking facility and the tax is
applicable on the accrued interest System should allow the user to create the XXXXBank Business Instant Access Account in GBP currency with Tier 3
Interest Rate where the customer does opt for Internet Facility XXXXBank Business Instant Access Account created
1.13.1 Customer Customer Creation Create a partnership type customer Create an Existing Business Customer with 'Partnership' as customer type and Relationship as 'Authorized
Signatory'. The House Database check returns adverse info. The customer is eligible for Free Banking but not eligible for FSCS System should allow
the user to create an Existing Business Customer with 'Partnership' as customer type and Relationship as 'Authorized Signatory' with Free Banking facility. System should escalate the application for
Manager reference due to adverse info on House Database Check Business customer with Partnership type and Authorized Signatory relationship created
1.13.2 Customer Customer Modification Modification of customer Change the Estimated Turnover of the Customer for 'Partnership' Customer Type System
should allow the user to change the Estimated Turnover of the Customer for 'Partnership' Customer Type Estimated Turnover screens missing in the Corporate customer opening screen
1.13.3 Customer Customer Modification Modification of customer Change the Statement Preferences of the Customer for 'Partnership' Customer Type
System should allow the user to change the Statement Preferences of the Customer for 'Partnership' Customer Type Statement preferences can be modified
customer age is equal to 18. The Interest Rate Type is 'Fixed' and the minimum balance is greater than GBP1M with Tier 4 Interest Rate. The customer does opt for Internet Banking facility and the tax
is applicable on the accrued interest System should allow the user to create the XXXXBank Business Instant Access Account in GBP currency with Tier 4
Interest Rate where the customer does opt for Internet Facility XXXXBank Business Instant Access Account can be created
1.14.1 Customer Customer Creation Create a limited company type customer Create a New Business Customer with 'Limited Company' as customer type and
Relationship as 'Director'. The Optima Database check returns adverse info. The customer is eligible for Free Banking but not eligible for FSCS System
should allow the user to create a New Business Customer with 'Limited Company' as customer type and Relationship as 'Director' with Free Banking facility. System should escalate the application for
Manager reference due to adverse info on Optima Database Check Business Customer with Limited Company type and with Director relationship is created
1.14.2 Customer Customer Modification Modification of customer Change the Email ID of the Customer for 'Limited Company' Customer Type System
should allow the user to change the Email ID of the Customer for 'Limited Company' Customer Type Email ID is getting modified
1.14.3 Customer Customer Modification Modification of customer Change the Date of Incorporation of the Customer for 'Limited Company' Customer Type
System should allow the user to change the Date of Incorporation of the Customer for 'Limited Company' Customer Type Date of Incorporation is
getting modified
1.14.4 Accounts Creating a Business Account To create a XXXXBank Business Account XXXXBank Business Account creation in GBP currency where the customer age is
equal to 18. The Interest Rate Type is 'Fixed' with 10% Interest Rate for debits. The customer is provided with both OD and Internet Banking facility and has a monthly Capitalization and Statement
Frequency. The customer is provided with Cheque facility with the Cheque Leaf option as 12 System should allow the user to create the XXXXBank Business Account creation
in GBP currency. System should provide the customer with both Internet Banking Facility and Cheque Facility with 12 Leaf option. System should provide the customer with OD facility where the customer
should be charged a Fixed Interest rate of 10% for all Debits with monthly capitalization frequency and Statement frequency Account creation, interest rate setting & interest capitalisation
setting are successful. System prompts error message when setting up the statement
1.14.5 Accounts Creating a Business Account AML check while creating XXXXBank Business Account Request of AML and Credit Check by clicking on the button 'Confirm Account
1.14.7 Account Transactions Cash Deposit Perform cash deposit in XXXX Business Instant access (GBP) Local currency cash deposit into An "active" XXXX Business Instant access
account at branch counter when the customer passes the ID and V System should allow the user to make deposit into the XXXX Business Instant
access account
1.14.8 Account Transactions Cash Withdrawal Perform cash withdrawal in XXXX International Business Account Local currency cash withdrawal from An "active" XXXX Business Instant
access account at branch counter when the customer passes the ID and V System should allow the user to withdraw from the XXXX Business Instant access
account
1.15.1 Customer Customer Creation Create a limited company type customer To verify if the user is able to create an Existing Business Customer with
'Limited Company' as customer type and Relationship as 'Nominated Person'. The AML check returns adverse info. The customer is eligible for both Free Banking facility and FSCS
System should allow the user to create an Existing Business Customer with 'Limited Company' as customer type and Relationship as 'Nominated' with Free Banking facility. System should
escalate the application for Manager reference due to adverse info on AML Check No Nominated relationship type
1.15.2 Customer Customer Modification Modification of customer To verify if the user is able to change the Additional Customer Details of the Customer for 'Limited
Company' Customer Type System should allow the user to change the Additional Customer Details of the Customer for 'Limited Company' Customer Type Additional
Customer Details can be modified
1.15.3 Accounts Creating a Business Account To create a XXXXBank Business Account XXXXBank Business Account creation in GBP currency where the customer age is
greater than 18. The Interest Rate Type is 'Floating' with 10% Interest Rate for debits. The customer is provided with both OD and Internet Banking facility and has a monthly Capitalization and
Statement Frequency. The customer is provided with Cheque facility with the Cheque Leaf option as 24 System should allow the user to create the XXXXBank Business Account
creation in GBP currency. System should provide the customer with both Internet Banking Facility and Cheque Facility with 24 Leaf option. System should provide the customer with OD facility where the
customer should be charged a Floating Interest rate for all Debits with monthly capitalization frequency and Statement frequency Account creation, interest rate setting & interest capitalisation
setting are successful.
1.15.4 Accounts Creating a Business Account AML check while creating XXXXBank Business Account Request of AML and Credit Check by clicking on the button 'Confirm Account
1.15.6 Accounts Account Opening Calculation of interest Interest gets accrued for the XXXXBank Business Account System
should not accrue the interest for the XXXXBank Business Account
1.15.7 Accounts Account Closure Closing of XXXX bank Business account Close a XXXXBank Business Account account which is in 'Active' status
System should allow the user to close a XXXXBank Business Account account which is in 'Active' status
1.54.1 Customer Customer Creation Create a New Business customer Create a New Business Customer without the Individual Customer Creation Process
System should not allow the user to create a New Business Customer without the Individual Customer Creation Process
1.55.1 Customer Customer Creation Create a Existing Business customer Create an Existing Business Customer without the KYC Check where the relationship is 'Authorized
Signatory' System should not allow the user to create an Existing Business Customer without the KYC Check where the relationship is 'Authorized Signatory'
1.56.1 Customer Customer Creation Create a Existing Business customer Create an Existing Business Customer where the ID & V Process gets failed System
should not allow the user to create an Existing Business Customer where the ID & V Process gets failed
1.57.1 Customer Customer Creation Create a Existing Business customer Create an Existing Business Customer without Manager Reference where the AML Check returns Adverse Info
System should not allow the user to create an Existing Business Customer without Manager Reference where the AML Check returns Adverse Info
1.58.1 Customer Customer Creation Create a Sole Trader type customer Create an Existing Business Customer with 'Sole Trader' as customer Type without House Database Check
System should not allow the user to create an Existing Business Customer with 'Sole Trader' as customer Type without House Database Check
1.59.1 Customer Customer Creation Create a partnership type customer Create an Existing Business Customer with 'Partnership' as customer Type without House Database Check
System should not allow the user to create an Existing Business Customer with 'Partnership' as customer Type without House Database Check
1.60.1 Customer Customer Creation Create a partnership type customer Create an Existing Business Customer with 'Partnership' as customer type without Manager Reference where
the House Database Check returns Adverse Info System should not allow the user to create an Existing Business Customer with 'Partnership' as customer
type without Manager Reference where the House Database Check returns Adverse Info
1.61.1 Customer Customer Creation Create a Community type customer To verify if the user is able to create an Existing Business Customer with 'Community' as customer type
where the customer is offered 'Free Banking' facility System should not allow the user to create an Existing Business Customer with 'Community' as customer
type where the customer is offered 'Free Banking' facility
1.62.1 Customer Customer Creation Create a Limited Company type customer Create an Existing Business Customer with 'Limited Company' as customer type
without Manager Reference where the Optima Database Check returns Adverse Info System should not allow the user to create an Existing Business Customer with
'Limited Company' as customer type without Manager Reference where the Optima Database Check returns Adverse Info
1.63.1 Account transactions Banker's Draft Issuance of Banker's draft to Instant account holder To check Issuance of Banker's Draft in FCY Currency from an Instant Access
Account with insufficient funds and the draft amount more than the max level setup with secondary Authorisation System should not allow to issue the draft as the Account does not
have sufficient funds.
1.64.1 Account transactions Banker's Draft Issuance of Banker's draft to Cash Account holder To check Issuance of Banker's Draft in GBP from a XXXX Bank Cash Account with
sufficient funds but with the draft amount more than the max level setup with single level authorisation. System should not allow to issue the draft with single authorisation
as the amount exceeds the max amount permitted.
1.65.1 Account transactions Banker's Draft Issuance of Banker's draft to Instant account holder To check Issuance of Banker's Draft in FCY Currency from an Instant Access
Account with Sufficient funds and the draft amount equal to min level setup with Single level Authorisation System should not allow the user to issue Banker's Draft as the
facility is not allowed.
1.66.1 Account transactions Banker's Draft Issuance of Banker's draft to Young savers account holder To check Issuance of Banker's Draft in LCY Currency from a Young Savers Account
with Sufficient funds and the draft amount between min and max level level setup with Single level Authorisation System should not allow the user to issue Banker's Draft as the
1.67.1 Account transactions Banker's Draft Issuance of Banker's draft to Cash Account holder To check Issuance of Banker's Draft in FCY Currency from a XXXX Bank Cash
Account with Sufficient funds and the draft amount equal to max level setup with Single level Authorisation System should allow to issue the draft with single level
authorisation.
1.68.1 Account transactions Banker's Draft Issuance of Banker's draft to XXXX Bank FCY account holder To check Issuance of Banker's Draft in GBP from a XXXX Bank FCY Account with
Sufficient funds and the draft amount more than the max level setup with Secondary Authorisation System should not allow the user to issue Banker's Draft as the
1.69.1 Account transactions Banker's Draft Issuance of Banker's draft to Current account To check Issuance of Banker's Draft in FCY Currency from a XXXX Bank Current
Account with Sufficient funds and the draft amount equal to min level setup with Single level Authorisation System should allow to issue the draft with single level
authorisation.
1.70.1 Account transactions Banker's Draft Issuance of Banker's draft to Current account To check Issuance of Banker's Draft in LCY Currency from a XXXX Bank Current
Account with Insufficient funds and the draft amount between min and max level level setup with Single level Authorisation System should not
allow to issue the draft as there is insufficient balance in the account
1.71.1 Account transactions Banker's Draft Issuance of Banker's draft to XXXX Bank Clubs and Societies account holder To check Issuance of
Banker's Draft in FCY Currency from a XXXXBank Club & Societies Account with Sufficient funds and the draft amount equal to max level setup with Single level Authorisation System
should allow to issue the draft with single level authorisation.
1.72.1 Account transactions Banker's Draft Issuance of Banker's draft to XXXX bank International Business account holder To check Issuance of
Banker's Draft in GBP from a XXXX International Business Account with Sufficient funds and the draft amount more than the max level setup with Secondary Authorisation System
should not allow to issue the draft for XXXX International Business account as Banker's Draft is not allowed
1.73.1 Account transactions Banker's Draft Issuance of Banker's draft to Business Instant access account holder To check Issuance of Banker's Draft in FCY Currency from a XXXX Bank
Business Instant Access Account with Sufficient funds and the draft amount equal to min level setup with Single level Authorisation System
should not allow to issue the draft for Business Instant account as Banker's draft facility is not allowed
1.74.1 Account transactions Banker's Draft Issuance of Banker's draft to XXXX Bank Business Account holder To check Issuance of Banker's Draft in LCY Currency from a XXXX Bank
Business Account with Insufficient funds and the draft amount between min and max level level setup with Single level Authorisation System
should allow to issue the draft with single level authorisation.
1.75.1 Customer FSCS Customer FSCS Customer eligible Customer opening version should have the two flag options of Yes and No Customer
screen should have Yes and No flag options
1.75.2 Customer FSCS Customer FSCS Customer eligible The flag in the customer record is default automatically to 'FSCS Eligible' during the customer opening
process System should default automatically to the flag the customer to 'Eligible' during customer opening process
1.75.3 Customer FSCS Customer FSCS Customer not eligible Corresponding reason should be mentioned if the customer is not eligible System
should not allow to mark the FSCS as Y when the sector level FSCS is N. also should ask for valid reason for the not eligible customer
1.75.4 Customer FSCS Customer FSCS maximum compensation amount Record should be maintained to store a maximum compensation amount for a customer as GBP 50000
System should not allow to mark the FSCS as N when the sector level FSCS is Y
1.75.5 Customer FSCS Customer FSCS eligible compensation amount SCV displays Eligible Compensation Amount which needs to be calculated based on the deposits held by the
customer (singly or jointly) System should allow the SCV to display Eligible Compensation Amount which needs to be calculated based on the deposits held by the customer
(singly or jointly)
1.75.6 Customer FSCS Customer Report Enquiry Enquire if the the required report in the above format containing all the required data can be produced on demand from
T24. Report should contain all required data
1.75.7 Customer CAF CAF Printing Customer and Account opening screens should have a button option for the CSR to initiate printing of CAF. Customer
and Account opening screens should have a button option for the CSR to initiate printing of CAF.
1.38.1 Customer Customer Creation create a customer -Joint Creation of a Retail Customer - single with all valid details. System
1.38.2 Customer Customer Creation create a customer -Joint request for AML check by clicking on 'Do AML' button in the customer screen.聽
1.39.1 Customer Customer Creation create a customer -Joint Creation of a Retail Customer - Joint with all valid details. System
1.39.2 Customer Customer Creation create a customer -Joint request for AML check by clicking on 'Do AML' button in the customer screen.聽
1.40.1 Accounts Account Creation Create an account for Cash account XXXX Bank Retail Cash Account creation in EUR currency and with Cheque Book and Internet Banking
facility.
2. printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the account deal is committed.
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the XXXX Bank Retail Cash Account in
EUR currency and with Cheque Book and Internet Banking facility.
1.41.1 Accounts Account Creation Create an account for FCY account XXXX Bank FCY Account creation with Min Balance as 1900 for Retail Customer - Joint with monthly
statement frequency and with valid Joint Holder ID but No Joint Relation Code.聽
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create XXXX Bank FCY Account with balance
not meeting the min balance criteria and with monthly statement frequency and with valid Joint Holder ID but No Joint Relation Code
1.42.1 Accounts Account Creation Create an account for FCY account 1.XXXX Bank FCY Account creation with Statement frequency set as EOY with Internet Banking facility.聽
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the XXXX Bank FCY Account with
Statement frequency set as EOY with Internet Banking flag set to Yes
1.43.1 Accounts Account Creation Create an account for Current account -Joint 1. XXXX Bank Retail current account creation When OD is not allowed for a
retail customer -Joint with valid joint holder ID and valid relation code.
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should allow the user to create the XXXX Bank Current Account with OD
set as NO with valid Joint Holder ID and valid relation code.
1.44.1 Accounts Account Creation Create an account for Instant account creation-Under 16 1. Instant Access Account creation for Retail Customer - Under 16.聽
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the Instant Access Account for
Customer - Under 16 as it does not meet the minimum age criteria System allows the user to create Instant access account to a customer under 16
1.45.1 Accounts Account Creation Create an account for Younger savers account creation-Single age >16 1. Young Savers Account creation when the customer age is greater than
maximum permissible age of 16 years.
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the Young Savers Account for a
customer with age more than 16 years
1.45.2 Accounts IBAN Verification IBAN Verification To verify if the user is able to verify the generated IBAN for the created XXXX Bank Young Savers Account which is
manually fed into the system System should generate the IBAN on successful creation of the account. The IBAN should be of 22 digits with country code as GB followed by
the check number generated through a check digit logic which is derived from the account number. The check number should be followed by the BIC and then the SORT code followed by the account number
22 digit num is generated with sort code as 000000
1.46.1 Accounts Account Creation Create an account for ISA- fixed under 50 1. ISA - Fixed Under 50 Account creation with USD as currency and with valid
Joint Holder ID but Invalid Joint Relation Code.
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the ISA - Fixed Under 50 Account
with USD as currency with valid Joint Holder ID but Invalid Joint Relation Code System only allows with GBP
1.47.1 Accounts Account Creation Create an account for ISA- fixed under 50 1. ISA - Fixed Under 50 Account creation with initial Balance exceeding 5000
GBP.
2.printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the account deal is committed.
3.request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create ISA - Fixed Under 50 Account if the
initial balance goes above the maximum balance.
1.48.1 Accounts Account Creation Create an account for ISA- fixed under 50 1. ISA Account - Variable Under 50 creation when the age is greater than
maximum and with Invalid Joint Holder ID but valid Joint Relation Code.
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the ISA Account - Variable Under 50
when the age is greater than maximum with Invalid Joint Holder ID but valid Joint Relation Code. Cannot create ISA account
149.1 Accounts Account Creation Create an account for ISA-Veriable Over 50 1. ISA Account - Variable Over 50 creation with No Internet Banking Facility.
2.printing of Customer Welcome Letter (EOS) with valid customer data along with population date when the account deal is committed.
3. request of Credit Check by clicking on the button 'Confirm Account Opening' System should not allow the user to create the ISA Account - Variable Over 50
when Internet banking is not allowed. Customer is underage
1.50.1 Accounts Account Creation Create an customer for ISA fixed over 50 Creation of an ISA Fixed over 50 Account for Retail Customer - Joint in GBP
currency with Internet Banking but no Cheque Book. System should allow to create an ISA Fixed Over 50 account in GBP currency for Retail Customer - Joint
with Internet Banking and no cheque book. System does not allow to open the ISA account
1.50.2 Accounts Account Creation Create an customer for ISA fixed over 50 printing of Customer Welcome Letter (EOS) with valid customer data along with
population date when the account deal is committed.
request of Credit Check by clicking on the button 'Confirm Account Opening' The system should print a Customer Welcome Letter (EOS) when AOS button is
1.51.1 Accounts Account Creation Create an customer for ISA fixed over 50 Creation of an ISA Variable Under 50 Account for Sole Customer in GBP currency
with Internet Banking but no Cheque Book. 1. System should allow to create an ISA Fixed Under 50 account in GBP currency for Retail Customer - Sole
with Internet Banking and no cheque book.
1.52.1 Accounts Account Creation Create an customer for ISA variable over 50 Creation of an ISA Variable over 50 Account for Retail Customer - Joint in GBP
currency with Internet Banking but no Cheque Book. 1. System should allow to create an ISA Variable over 50 account in GBP currency for Retail Customer -
Joint with Internet Banking and no cheque book.
1.53.1 Accounts Account Creation Create an customer for Joint XXXX Bank Cash Account Creation of a XXXX Bank Cash Account for Retail Customer - Joint in GBP
currency with Internet Banking and no cheque book. 1. System should allow to create an XXXX bank cash account in GBP currency for Retail Customer - Joint
with Internet Banking and no cheque book.
1.53.2 Accounts Account Creation Create an customer for Joint XXXX Bank Cash Account printing of Customer Welcome Letter (EOS) with valid customer data along with
1.76.1 Customer Customer validations Customer requesting to add a new address Capture the customer address on the customer screen to cover 3 year period
System should allow the user to capture the customer address to cover 3 year road No address validation done on the customer level
1.76.2 Customer Customer validations Customer requesting to add a new address Add the number of customer addresses more than 3 times to cover 3 year period
System should allow the user to customer addresses more than 3 times to cover 3 year period and should mark the application as 'Refer' No address validation done
on the customer level
1.76.3 Customer Customer validations Customer requesting to add a new address Display the captured address on the customer screen Previous
address should be replaced by the newly entered customer address No address validation done on the customer level
1.76.4 Customer Customer validations Customer requesting to add a new address Residential details to be associated with a specific address
Residential details should be linked with a specific address for the information can be populated next to the relevant details on the CAF No address validation done
1.76.5 Customer Customer validations Customer requesting to add a new address Input the specific date/month/year value of Residence Since xxx
Proper duration for the customer residence should be entered in date/month/year No address validation done on the customer level
1.76.6 Customer Customer validations Customer requesting to add a new address Proceed with the application only if the address is more than 3 years
Customer should proceed with the application only if the address is more than 3 years No address validation done on the customer level
1.76.7 Customer Customer validations Customer requesting to add a new address Add another address to proceed with the application if the customer address is
less than 3 years Customer should add address without proceeding if the customer is less than 3 years No address validation done
1.76.8 Customer Customer validations Customer requesting to add a new address Start date of employment in the customer application is mandatory only if the
customer is employed Start date of employment should be mandatory in the customer application if the customer is employed
1.76.9 Customer Customer validations Customer requesting to add a new address Select employment status as 'Unenmployed' Employment
details should not be mandate The Employment status is marked as Unemployed the rest of the employment details is not a mandate fields anymore
1.76.10 Customer Customer validations Change of Paperless Statement Flag field The default value for the Paperless Statement flag is set as Yes
System should set the default flag of Paperless Statement as Yes Paperless statement is shown as Yes by default
1.76.11 Customer Customer validations Change of Paperless Statement Flag field Generate the statement for the customer when the Paperless Statement Flag is
set to 'Yes' System should generate the paper statement for the customer when the Paperless Statement Flag is set as 'Yes' Customer is created with
the paperless statement as Yes
1.76.12 Customer Customer validations Change of Paperless Statement Flag field To verify if the user is able to change the Paperless Statement Flag to 'No'
System should allow the user to change the Paperless Statement Flag to 'No' Paperless statement is able to change the flag as NO
1.76.13 Customer Customer validations Change of Paperless Statement Flag field To verify if the system generates the statement for the customer after setting
the Paperless Statement Flag to 'No' System should not generate the paper statement for the customer after setting the Paperless Statement Flag to 'No'
No paper statement is generated after making the flag as No
1.76.14 Customer Customer validations Printing AOS for a new Customer AOS flag option is present in both the individual and corporate customer screens
Both Individual and Corporate customers should have the AOS flag option AOS flag not available
1.76.15 Customer Customer validations Printing AOS for a new Customer Print AOS automatically when a customer opens an account in any account opening screen
AOS should be printed automatically when a customer opens an account in any account opening screen AOS flag not available
1.76.16 Customer Customer validations Printing AOS for a new Customer Check the flag in the customer after opening the account whether the AOS printed option is Y or Null
System should check the flag in the customer whether the AOS printed is Y or NULL after opening the account AOS flag not available
1.76.17 Customer Customer validations Printing AOS for a new Customer In the customer level, if the AOS printed flag is marked as Y then print AOS System
should print AOS if the flag in the customer is marked as Y AOS flag not available
1.76.18 Customer Customer validations Printing AOS for an existing Customer In the customer level, if the AOS printed flag is marked as Null then print AOS
System should print AOS and automatically should mark the flag in the customer level as Y AOS flag not available
1.76.19 Customer Customer validations Printing AOS for an existing Customer After printing the AOS check whether the AOS printed flag in modified
automatically as Y System should print AOS and automatically should mark the flag in the customer level as Y AOS flag not available
1.76.20 Customer Customer validations Printing AOS for a Joint Customer after opening a new account Check whether there is an option to reprint the AOS There
should be an option to reprint the AOS AOS flag not available
1.76.21 Customer Customer validations Printing AOS for a Joint Customer after opening a new account To verify if the user is able to reprint the AOS after creating another account
for the same customer 1. System should reprint the AOS and the form should be of the same format with exact details as mentioned at the time of opening the
account.聽
2. System should display the Bind ID correctly AOS flag not available
1.76.22 Customer Customer validations Printing AOS for a Joint Customer after opening a new account Check whether the details of the cards issued to any of the accounts for the
selected customer is included in the AOS The printed AOS should include the issued card details to the accounts for the selected customer AOS flag not
available
1.76.23 Customer Customer validations Printing AOS for a Joint Customer after opening a new account Check whether the details of the Cheque books issued to any of the accounts for
the selected customer is included in the AOS The printed AOS should include the issued cheque book details to the accounts for the selected customer
AOS flag not available
1.76.24 Customer Customer validations Printing AOS for a Joint Customer after opening a new account Check whether the limit details related to any of the accounts for the selected
customer is included in the AOS The printed AOS should include limits related to the accounts for the selected customer AOS flag not available
1.76.25 Customer Customer validations Printing AOS for a Joint Customer after opening a new account Check whether the accounts details for the selected customer is included in the
AOS The printed AOS should include the account details for the selected customer AOS flag not available
1.77.1 Customer Customer validations Charge Review Date To verify a new field Charge Review Date is available in the Customer opening screen Charge
Review field Date should be available in the Customer opening screen Charge Review Date field is available
1.77.2 Customer Customer validations Charge Scan To verify a new mandatory field Charge Scan is available with the Yes or No option in the Customer opening screen
Charge Scan field should be available in the Customer opening screen Charge scan field is available
1.77.3 Customer Customer validations Charge Diary Note To verify a new field mandatory Charge Diary Note is available with the Yes or No option in the Customer opening
screen Charge Diary Note should be available in the Customer opening screen Charge Diary Note is available
1.77.4 Customer Customer Creation Charge Review Date Creation of Retail Customer - Sole Trader getting auto populated with a date of 12 months from the customer opening
date and with a frequency of 12 months for future dates. Customer should be created with the with a date of 12 months from the customer opening date and with a
frequency of 12 months for future dates. Date not auto populated in Charge Review Date field
1.77.5 Customer Customer validations Charge Diary Note Generate a Report for Account Officer to take action on the Charge Diary Note action date which should be initially
input as 9 months from date of customer opening and subsequently with monthly frequency for reminders Report should be generated for Account Officer to take action on the
Charge Diary Note action date which should be initially input as 9 months from date of customer opening and subsequently with monthly frequency for reminders Flag option missing in the
Charge Diary Note field
1.77.6 Account Transactions Cheque deposit Local currency Cheque deposit Local Currency Cheque deposit of non XXXX bank current account into another "active" XXXX bank Current
Account at branch counter. System should allow to deposit non XXXX account cheque int into a XXXX Current account of the customer System throws an error
message not allowing to commit the transactions
Roll-out, Go Live & Post Support

Basic questions to ask here are:
187. What support do you give for roll-out?
188. What are the roll-back or “back out” plans if the roll out gets into trouble?
189. How many days post-live or post roll-out support do you give at no charge?
190. How many on-site post roll-out staff are assigned (on premises)?
191. What are some of the typical problems and issues found in post-roll out? What sort of
turnaround time is typical to fix these problems?
Change Process and Rules Related

192. Change process needs to be tracked and a permanent record made of every change after
the build system is “unfrozen.” Again change requests are not allowed while T24 is in the build
phase (causes “scope creep”). After it moves to test phase, depending on the change, the
change process may begin but only after the “bugs” or “defects” are all removed and the system
moves into what is known as a “zero defect” stage. At that point which is when the testing
concludes and is approved then the change request process may begin 100% and start with a
set of changes that will be the basis for the change request process from that point on (tracking
numbers and dates/reasons/justifications assigned to the changes, etc. begin).
Documents for the change request that are usually required typically show:
 The change requested
 Why it is requested
 What the change will impact other than the change itself in the system (changes to work
flow, general ledger, SOPs, etc.)
 What the change will cost and how much estimated work time is involved
 Who initiated the change and who validated its need and approved it
 Who has been assigned the work
 When will it be tested
 Test results
 Ready for live cutover
 When the cutover has been made and the change was put on the live system
193. Ask about the change process so that you don’t find yourself where people are making
undocumented changes to the system. Question the vendor about who controls this process.
And then make sure that you have someone enforcing changes on the system and that audit is
involved with any changes made (audit sets standards and controls for everything on the
system--this is another separate discussion about how audit is involved with T24
implementation--this is NOT covered in this document as this is not part of due diligence other
than you can ask if audit logs are kept on the T24 system which they are--if you need further
information on the subject of audit and T24 operation please email us). The big question is what
is the change methodology you either have in your business already or that the vendor uses or
suggests.
194. Ask too about audit logs on T24 and how they work and if they meet your business and
audit requirements?
Statement of Work (SOW), viz the example below:
195. Stage 1 «Preparation»
• Clarify the scope and format of the work to be performed - ask about the SOW in
the due diligence process and how it is drawn up and agreed upon - IF YOU DO NOT GET
A WORK ITEM IN THE SOW IT IS OUT OF SCOPE - IT WILL COST YOU EXTRA TO ADD IT
LATER MOST LIKELY
• Harmonization of analyzed parameters and format of reports submitted by the
project team - THIS MEANS THAT YOU WILL HAVE TO GET YOUR FULL LIST OF REPORTS
TOGETHER FOR SUBMISSION TO TEMENOS BEFORE THE WORK BEGINS - THE IDEA IS TO
FIND OUT BEFORE YOU START THE PROJECT IF THE WORK FOR THE REPORTS YOU WANT
IS POSSIBLE ON T24 - The parameters are in the enquiry and/or report modules in the
T24 system - do not ask for report parameters later or if they can or cannot be built at a
later date - reporting requirements MUST BE KNOWN WAY IN ADVANCE so that you
know the gaps in the reporting parameters of T24 if there are any that impact your
decision to use T24
• Familiarization with the legal statutes and the contract to address the major risk
of the bank - THIS MEANS FIND OUT IF THINGS GO WRONG WHAT YOU REMEDY IS IN
THE COURTS OR IN RESPECT TO ENDING THE CONTRACT WITH TEMENOS - STATUTES
REGARDING CONTRACTS VARY FROM COUNTRY TO COUNTY OF COURSE
• Assist project management in the organization of the project work and working
groups - WORK THAT BELONGS TO THE VENDOR EXCLUSIVELY NEEDS TO BE CLEARLY
IDENTIFIED BEFOREHAND IN THE CONTRACT - LIKEWISE THE SAME IS TRUE FOR THE
BANK - DO NOT LEAVE “GREY AREAS” OR LEAVE ANYTHING TO GUESSING LATER - THE
WORK WON’T BE DONE, YOU CAN BE SURE OF THAT OR YOU WILL PAY EXTRA TO THE
VENDOR OR SOMEONE ELSE TO DO IT
• Assist in organizing training for working team on T24 and holding them to
improve internal activity - GET THE TRAINING SORTED OUT EARLY ON - SOME TRAINING
NEEDS TO TAKE PLACE BEFORE THE PROJECT BEGINS - FIND OUT WHAT THAT IS, HOW IT
WILL IMPACT YOUR PROJECT’S SUCCESS AND WHO NEEDS TO GO TO THIS TRAINING
Stage 2 «Development of a Project Blueprint»

• Agree on a list of the analyzed business processes (that is which ones you need to
re-engineer or examine for work flow and process improvement) and inventory the
requirements of the bank and get them written down into a business requirements
document that you will use as part of your due diligence and pre-sales process of
examination of the T24 system and the vendor itself, Temenos
• Collection and analysis of the data requested in all business processes in order to
assess compliance with the Bank Risk Assessment.
• Survey of business processes (AS-IS) model.
• Conduct a comparative analysis of global best practices in business processes
• Help in development of Conceptual design (TO-BE) model of business processes.
• Assistance in writing of the conceptual model in all directions (loans, deposits,
risks, etc.).
• Help to create master data for further project work
• Help in description of business processes and all levels of authorization and limits
Stage 3 «Implementation and testing of the system»

• Analysis of current state and readiness to conduct performance testing CBS (Core
Banking System).
• Risk assessment and approval of findings with bank management
• Evaluation methods and plans for performance testing T24.
• Develop recommendations for improving embedded CBS.
• Develop recommendations to minimize operational risks in the interaction with
your CBS in terms of supporting the system and its subsequent refinement
• Help project team in carrying out the procedure UAT (Testing System) and Quality
Assurance (Assessment of the quality of implementation) to improve system
performance and risk mitigation in industrial use
Stage 4 «Post-implementation»
• Analysis of the results of the system and its efficiency
• Develop recommendations to improve the system and improve problem areas
based on international practices and processes
OUT of Scope Work (OSOW)

196. This is the usual place where a project will get into trouble and possibly fail if OSOW is not
managed closely and carefully. You will have to ask the vendor these questions to get a good
grip on this matter about Out of Scope Work and how to deal with it when it comes up as a
problem or possibly “fatal error” factor to your project:
197. How does the vendor deal with OSOW?
198. Does the vendor charge extra for including work that was not originally in scope? And, at
what extra rate?
199. What does the client have to do in order to control this sort of problem when all of a
sudden users begin to demand that work not originally planned be added to the project?
200. Does a change in SOW mean that you must start the project over? (Sometimes it does
believe it or not.)
201. Does the timeline of the project change drastically with a change in the SOW? To what
extent?
202. Where does the vendor have to step in and make it clear that changes in the SOW after the
project has begun greatly diminish the project’s initial change of success?
203. Does the client have to make sure that people do not use a change in SOW as a covert
means to “sink” the project? Saboteurs lurk everywhere with new projects. Many times the “old
guard” doesn’t want the project at all and certainly don’t want it to succeed if they cannot stop
it before it begins.
204. What does a project have to do in order to deal with OSOW in such a way that it eventually
becomes a “phase” in the project?
NOTE again - Scope of work changes frequently arise also from from users who suddenly do not
want to see the project succeed. There could be all sorts of reasons for this, but typically “there
are snipers in the trees” on all projects with people who view the project as (a) a threat to their
job and/or power (b) extra, uncompensated work, or (c ) simply something that will upset their
cozy set up in the bank and force them to take on added work load and responsibilities or have
to be Retrained which is often a big issue with some people who think they “know it all.”
Standard Functionality in T24 (What Does That Mean?)
Be sure to ask these questions in respect to Standard Functionality--
205. What is it?
206. Do I have to use it?
207. Do I pay for it even if I don’t use it?
208. Give me a list of standard functionality in your system.
209. Can I simply make changes to standard functionality free of charge if it is not
suitable for my bank?
210. What will I get in a system where the standard functionality is not re-configurable
(will I have to change how I do business and my internal business processes)?
211. Does standard functionality change at all from release to release?
212. If it does what does that mean to my existing configuration later?
Be careful with this term, standard functionality, because frequently it is “deep code” in
a core banking system that cannot be changed for many reasons.
Project Plan (Who Writes and Maintains It? - How is Project Slippage or “Scope Creep”
Controlled?)
213. While this seems simple enough to explain and understand, many vendors come in
with “fast track” project plans that are designed to get to the “roll out” phase as quickly
as possible. Fixed cost projects always use such “fast track” plans--so ask these questions
about the project plan, who wrote it, what sort of plan it is, and who is the one who
updates it from day to day:
214. Is your plan fast track and based on the fact that the project is “fixed cost”?
215. What sort of details are missing in a fast track plan?
216. What faith must I put in believing that the fast track plan is actually achievable by
the final date it has?
217. Who would think that a fixed cost project has a fixed project plan? Does that mean
you are leaving out things? If so what are they?
218. Do you ever assume that the system cannot be installed according to the same plan
over and over at every client’s site? Explain this to us a bit.
219. What is the best solution for us if this plan will NOT work for us for whatever
reasons?
220. Fixed cost projects are what Temenos loves to sell. They come in and “slap the
system together and turn it on, then give you the keys.” But did you get anything of
quality for your money? Probably not. Be careful to delve into this project plan business
and get the right and TRUE answers for your bank and your project.
Definition of "Project Completion"
This is a clever one they will define according to a lot of mumbo jumbo in the contract
frequently where the exact interpretation of completion is muddled in a morass of legalise that
only some Harvard professor of law could ever understand. So ask these questions:
221. What is the definition per your standards of project completion?
222. How to you MEASURE the standards that determine that?
223. What are the values you use in your completion standards?
224. How do we as the bank know that what these standards say are in fact the truth?
225. How do we audit completion standards and determine if the project is in fact
complete per contractual agreements?
226. Have you ever have a completed project that somehow turns out not to be
complete because of false or altered project reporting, omissions on updates in the
project plan, work that was not in fact done or poorly done and not caught and
corrected in testing, or just outright fraud where the project manager and team falsified
information along the way to “make the project” end on time? Be on the lookup for such
tactics by the vendor on a project, especially a T24 project.
Vendors will lie about nearly anything in a project if that will give them a quick profit or get
them to the handover stage of the project so that they can go work on another project
elsewhere. You are usually not dealing with people on a project with Temenos who have your
bank’s best interests in mind. Remember that.
Acceptance Criteria
This is much the same as the questions regarding the project plan. These are the questions you
need to ask:
227. Who sets the acceptance criteria?
228. How is it measured?
229. What part in the overall QA (quality assurance) process is the acceptance criteria is
included in the test plan and how is QA in fact tracked?
230. If it is not tracked specifically then how do you track it?
231. What sort of QA tools do you use to keep up with acceptance criteria which goes hand-in-
hand with Quality Assurance (QA)?
These questions will put you on the right track to getting some answers from the vendor about
this subject, but you also need to set up your own Project Management Office (PMO) where
tracking of acceptance criteria and QA results is a major part of that office’s duties and
responsibilities.
Flowcharts (Process Work flow - who Validates them?)
232. The whole idea of flowcharts and work flow goes hand in hand with how Temenos will
have you go through their requirements workshops and fill out forms and make adjustments to
their own work flow charts that they will give you for Temenos T24 functions. There are
hundreds of these Temenos work flows, and here are a few below on the next several pages to
give you an idea of how they will have you “change these” to fit your business needs:
Now what you have to remember about working this way is that if you are not “savvy” enough
to understand T24 vs. your own work flows and business processes, Temenos will trick and con
you with these charts and have you waste endless hours filling them out, changing them, and
validating that they are “correct” so that they can shove T24 in more or less as it’s preconfigured
already in the so called “Model Bank” they will give you. And remember it is not a model bank
at all - it’s a “demo bank” which is what it was called and used for 20 years ago when people
were going out and doing sales presentations of T24. Later someone got the big idea to sell it
the “demo bank” as a “model bank,” which is what you want to avoid. It’s not a model of
anything. It’s a collection of discombobulated work flows and products that added all together
wouldn’t even get through a Close of Business run without crashing the system. So beware. This
is ‘lying with graphics” as the line used to go in the class at MIT in Boston. Figure out that
someone has spent a lot of time putting these charts together so that they can get you to sign
off quickly on the T24 business requirements so that they can finish the project in a hurry.
Questions to ask--
233. What is the purpose of going through these charts - what if my own processes are radically
different?--that is different to the point that I need a whole new set of charts and not these that
“come with the T24 system”?
234. What sort of turnaround time do you have to rebuild these processes if we make major
changes?
235. What is the point of using your charts? Can you just use ours in our own documents for the
bank and in our own SOPs? What’s the difference (other than our charts were not drawn for the
T24 system’s design)?
Functional Requirements (vs. Business Requirements)
These require skill to do and the questions accordingly to ask the vendor are these:
236. What are the functional requirements YOU require to configure the T24 system for our
bank? What that means is that with a function requirement vs. a business requirement, the first
is a specification that means HOW does the system, for example, produce a specific
automatically generated form or advice or statement or document opposed to having a
business requirement that simply states the need for the same. Functional requirements are
technical and get into the nitty gritty of how a requirement should work across a system design
and configuration.
T24 may not produce the item you want using the same function (such as using MS Word) as
you have currently or expect. T24 may produce the item in a completely different way using
functionality that is not the same at all and may thus require significant changes to how you
work and how your infrastructure supports how you currently work.
Be sure to get “deep” into the questioning about any functionality with T24 from documents to
SWIFT to wire services to internet connectivity to interfaces to outside systems to anything to
do with reporting. The list of questions here is practically endless, BUT start with a list of your
current functions and functional requirements vs. business requirements as I’ve given examples
of here and start from there.
Technical Specifications (Hardware/Software/Interfaces)
This too is a long and complicated item. The short approach here is to ask these questions:
237. Can we have a sample T24 architecture document for a data center?
238. Can we have a list of all software that is EXTRA to T24 that we need to buy to support T24?
239. Can we have architectural drawings for a typical T24 set up and design for our sizing
needs?
These questions will get you going. However, if you want to know more about T24 architecture
and how to go about getting the RIGHT answers from Temenos for your bank about this subject
we can help you further if you will ask us.
Interfaces (in detail) - message formats required or used
240. These questions are the same as above for architecture and they go together.
Project Ownership
241 - 248. This one is simple:
a. Who owns the “build and configuration”?
b. Who owns the testing?

c. Who owns the documentation?
d. Who owns the training?
e. Who owns the security setup (user profiles)?
f. Who owns the backups and COB (Close of Business run)?
g. Who is responsible for “crashes” and “fatal errors” (system won’t work)?
Project Organization
This is one about project ownership you need to sort out early on - get the roles and
responsibilities assigned by name. MAKE A PROJECT ORGANIZATIONAL CHART AND STICK TO IT.
249. How do you organize your team at Temenos on a project (get clear answers to this and an
org chart with names on it)
250. How do you interact with the bank staff counterparts who are responsible for their
segment of the project either from a business or technical perspective?
Assumptions (both parties, client and vendor)
251. If there are any assumptions get these spelled out and put into writing (such as it is
assumed that the Temenos staff has weekend access to the premises and that the bank is not
responsible for providing meals to the Temenos staff on weekends—off the cuff items such as
these two could be assumptions). Assumptions like this are important. Get it in writing or you
may just be receiving a bill for items you didn’t bargain for. Temenos staff are known for
“pushing the limit” on any extras they can get from you, the bank, if you’re not careful.
Environment (build, test, live)
Spell all of this out in writing. Ask the questions below:
252. How many T24 environments do we need to set up?
253. What level of “sameness” should there be among them (you don’t need to set up a full
testing or production environment for development for example)?
254. What sort of costs are involved with multiple environment set up?
255. What is the size (in square meters or feet) of the physical premises the bank needs for each
(room, whole floor, separate building, etc.)?
Facilities (in general)
Ask questions about desks and telephones/PC for Temenos staff such as:
256. Do Temenos staff get their own desk/equipment/office?
257. Do they have eating and toilet facilities that are separate?
258. Do they have parking?

259. Do they have access to public transportation?
260. Do they have access to outside eating and food vendors nearby?
261. Are there medical facilities on premises at the bank or nearby?
262. What if there are emergencies (accidents, sickness, money issues, etc)?
Operations of the bank and related documentation

263. Do you have your own documentation for processes, SOPs, systems in current use, security
standards and rules, etc.
Reports and Forms (including IFRS)
a. Make a full list of every report in the bank - do you have such a list? That means
IFRS and specialized reporting and reporting that may be for the central bank.
b. The same with forms - have a full list with current examples - find out how
Temenos and T24 system will process and store them - get the whole story here. Make
them show you.
Screen Cosmetics (UI and UIX)
264. Does your bank adhere to any special UI or UIX (screen display on a PC) standard? If so
have this documented and present it to the vendor for comment.
Business Continuity (Disaster Recovery)
265. T24 does not come with a Disaster Recovery system or plan or set up or architecture. Ask
about this. This is a completely separate area of discussion however and not in the Due
Diligence sphere to explore in depth beyond the questions about how does T24 handle this.
Project Documentation (for the client only)
266. Again, ask if you need special or separate project documentation and WHO DOES IT?
Deployment (who does?)
267. Ask if T24 deployment (go live) is done in country or out of country. Temenos has a “cloud”
version of T24. Are you on it? Are you doing a local on-site deployment or a cloud deployment
or a mix? BE SURE TO ASK TEMENOS WHAT THEY ARE SELLING YOU IN THIS RESPECT.
Local Developments and Customizations
268. These are areas that are always murky and confusing when Temenos comes in and starts
claiming that you need these two.
a. Ask what local developments are? This is a strange term to most people, but is
everyday language to Temenos. In short it means adding fields to the system whereby
the system has an internal tool that will generate a new field and let you add it to a
module. This is a field extension. In the JBase or TAFC or TAFJ world it is simple or a “flat”
field the T24 system generates to store data. Typically these fields are added for
information needed in reports or inquires. Also, the field may be incorporated in a
program or a “routine” (stored procedure) added inside of a version (particular screen
display of a part of a module’s database displayed under a tab on a work flow screen or
composite screen as Temenos calls it).
b. Ask what customizations are in respect to their (Temenos’) definition. Frequently
customizations to T24 do NOT mean exactly what you may think. They may “customize”
a screen view or work flow. That is NOT a customization per se. Get the scoop or the real
story behind that term when you hear Temenos staff use it. Note also that customization
and configuration are NOT the same thing. Beware.
COB operations, Reports, Inquiries and Deal Slips
269.
a. Ask how long it takes to run COB or “Close of Business.” This is the “nightmare
world” of T24. COB sometimes can take hours - up to 12 or more I’ve seen - which is
certainly no good for your bank when the system is “down” for that long. T24 is NOT
useable during a COB run. Don’t listen to anyone if they say that it is. And “T24” or non-
stop processing is not the “be all and end all” of solving the COB problem. T24 or round-
the-clock no COB operation is an additional feature that you have to buy with the
product. And Temenos while promoting this as a big advantage to the system hasn’t yet
got it all smoothed out yet. T24 was renamed in 2004 to reflect this new capability, but
to this day people are still running COBs. Ask Temenos why this is the case?
b. COB also produces in some instances 100s of useless end-of-day reports that are
nothing to many customers but clutter and useless data. They slow the COB immensely if
they are not turned off. Ask Temenos about the end-of-day reports and how many are
running each day and why. Note that in “T24 talk” inquiries are reports that are not
hard-coded. Temenos no longer uses the old report modules (there were three or four of
them once) because they have to be compiled and cannot be altered or edited
afterwards. Also the compiler was removed in T24 some ten years ago. They do not want
you writing your own code and compiling it in the T24 system. Ask them about that too.
Deal slips are part of the editor or “Delivery” module in T24. Ask about them too (and
how complicated Delivery is to set up – it’s horrible to use – it’s an old UNIX “vi” editor –
ancient technology). Ask how many there are (forms, slips, statements, advices, etc.).
Ask them how easy they are to set up and edit? They are not.
Products Supported (and Not)

270.
a. Get his question settled regarding interfaces and connectivity to any legacy
systems you have in your bank that need to hook into T24. Will they? What sort of
complexity is involved in building these interfaces?
b. Also find out if you have any other systems in your bank that will be used in
conjunction with T24 such as forms processors and generators, mortgage and loan
systems, reporting systems, etc. Ask if these systems will “connect” to T24 and work as
they should.
System Architecture (Roles and Responsibilities)
271.
a. Ask about the architecture. I’ve mentioned this already earlier in this document,
but before you go out and start building a data center or server farm get the real
answers from Temenos about what you need to build and configure and WHY.
Sizing of Hardware and Data Center
272.
a. Ask for due diligence visits to other T24 “live sites” and see this for yourself.
Don’t just trust the Temenos architect to tell you what you need. T24 is BIG and needs a
lot of hardware and data support. Get the real numbers here on the data sizing for 1 - 5
years. Know in advance when you will be in a “scale” situation and have “run out of
room” on your databases.
Layers (Presentation, Queuing and Messages, Application, and Database)
273.
1. Get Temenos to explain all of these topics in detail to you along with giving you the proper
documentation that explains it completely and in depth. Don’t take their word. Queuing and
messaging in particular are areas you need to investigate “up close.”
Operating System Required for T24 (server software, databases if you are not using TAFC or TAFJ
alone)
274.
a. This is simple enough, but get it in writing what the OS is for T24. MS Server 2008 R2
among others. Get the full picture here of T24 supported OS’s. Ask them which OS’s do NOT
work with T24--and why. Then get answers in detail to the following items--
Implementation Environment and Sizing--
--Master Reference
--Quality Audit and Certification of the Site
--Data Migration
--Functional Testing
--System Integration Testing
--User Acceptance Testing
--Training
--Pre-Live (System Replica for "Cold Run")
Project Schedule (not the Plan but the actual yearly Calendar or Milestones Table)
275.
a. Get this one and ask for a real live calendar, not the project “calendar” of “man days”
but the actual physical calendar for 2019, 2020, etc. with the project shown day by day. Why?
This is so that you have some sense in “real time” how long you are going to be working on the
T24 implementation. Tell Temenos to convert the project plan’s calendar to a calendar “on the
wall.” This may sound silly but it is not. The project plan can be manipulated hence the calendar
can change inside of there (MS Project or something similar). Make a real calendar and “nail it
to the wall” somewhere and fix it where no one can change it (put plastic over it). That’s your
baseline for the project. Then watch and see if they stick to the “real time” you have marked for
the project’s duration there.
Training Offered Off-Site (by the Vendor)
276.
a. This is a simple question but the big question is WHO ARE THE TRAINER(S)? Get this
sorted out early in the project life cycle. Temenos brings in people for training who are
oftentimes not high quality. Be careful with what you agree to here regarding bringing outside
training staff on board. You may have to contract your own trainers if those from Temenos are
sub-standard.
Staff the Client Must Supply and Then That the Vendor Must Supply
277.
a. Again, get this in writing. Oftentimes, Temenos will not supply key staff. Get to the
bottom of this if you think the staffing requirements are odd. Or, if they are “farmed out” to
sub-contractors via other non-Temenos companies (typically referred to as “partners”).
Resource Plan (staffing and who is required by the number of hours or man days)
278.
a. This goes with staffing. Work it out to the “T” and determine you cost factors regarding
staffing. Overruns in cost will occur if you don’t.
Gap Analysis
279.
a. This is what you do at the pre-sales or pre-project stage. The more you know about gaps
the more effective your negotiations will be with Temenos regarding T24 implementation. Gap
analysis is not part of Due Diligence unless you want it to be. This document only mentions gap
analysis, but does not explain how to do it. Further information is available from us at Sam-V-IT
if you want it in this regard.
Release of software you are to receive - means how has it been "cut" for you?
280.
a. Make sure you are not getting some “old release” of T24. That’s all I will say. Get the
release and the details about “what’s in the release” from Temenos before you ever sign a
service and project agreement with them. Otherwise you may be in for a big surprise. Then
work out the General Services Agreement - as noted below with at least the minimum topics
shown below in your agreement:
General Services Agreement - what does it contain?
281.
--Should have info on:
----Expenses for vendor staff
----Employees and sub-contractors--get the employment terms of who is staffing the project
----Suspension of services - what will trigger? notice period? and remedies?
----Employment by the client of employees, contractors, and sub-contractors of the vendor
----Reasonable effort - what is it? Make sure it is defined in the Services Contract you sign
----Intellectual property - what are the definitions and "boundaries" of who owns what?
----Define and determine limitations of liability - what are they?
----Define product liability based on "hidden defects" - do you have such a clause in your
Services Agreement?
----What are the terms and rules governing making software and IP available to 3rd parties?
----What are the terms of notification between primary or principal parties if there is a breach of
confidentiality? What are the actions to be taken?
----Define force majeure - what is it? What are the liabilities and damages in such an event and
how are the remedied?
----Define what per diem rates are for vendor personnel - how much per day - what are the
limitations if any?
----Define the terms of international travel and what is allowed/not allowed - what are the basic
rules for international travel regarding cost of travel, etc.
----Define the nature of the Project Management Office - does the vendor provide this service?
is it the responsibility of the client?
----Define the training and testing aspects of the project - DO THIS FOR ALL ASPECTS OF BOTH
AND THE OWNERSHIP AND COST FOR THE SAME - Are you able to manage such work in-house
or not?
281. Releases each year (R15, R16, R17, R18, etc) - what do they mean? Find out how you will
be affected if you do not upgrade every three years or so
a. I’ve mentioned this subject in other places in this document, but get this clarified and
how soon you will be expected to upgrade your release of T24. Don’t guess at this. You can be
desupported and your warranty voided if you do not follow their terms and conditions on
upgrades. Also, be sure you know what you face if you deliberately decide NOT TO UPGRADE at
the expected time in the future. WHAT WILL YOU LOSE REGARDING SUPPORT AND WARRANTY
in that case? Then get answers to these questions below:
1. Do you know how your bank is at risk with Temenos and T24 after you go live? -
This is a major aspect of your business risk and you need to understand how
Temenos can make unreasonable demands of your organization and basically
hold you ransom for maintenance and license fees
2. Do you know that T24 post-live support is risky, expensive, and unreliable?
3. Do you know that TAMS (Temenos Application Management Services) and other
exclusive agreements regarding the use of non-Temenos approved personnel
can put your bank at risk of breach of contract, termination of contract for
Temenos support, and other matters of a not so favorable nature for your
company, bank, or organization?
This is the end of this document. Thank you.
Notes:
Temenos Application Framework for J (TAFJ) (from R13) - Similar to TAFC, but the Java version.
Database driver - Direct Connect Driver (DCD) is the T24 data abstraction layer that decouples
T24 business logic from the underlying data storage or structure. This project (test project) uses
the DB2 DCD as the database driver for the DB2 database. [COULD BE OTHER COMPLIANT JAVA
DBs TOO BESIDES DB2]
The jBASE Distributed Lock Service (JDLS) lock manager is a component of the DCD that
manages locks across multiple T24 application servers.
T24 Monitor - T24 Monitor is a Java Management Extensions (JMX) and web-based online
monitoring tool for T24. It offers real-time statistics and historical views of a particular T24
system.
Message Queue - An optional middleware infrastructure that allows T24 to use message-driven
communication with the Channels layer. It is essential where high availability or horizontal
scalability in the T24 Application layer are required. This project used WebSphere MQ Server as
the messaging infrastructure. An alternate approach is possible by using WebSphere Application
Server JMS queues.
Database - Can be any database management system that is supported by T24. Examples
include DB2, Oracle, SQL Server, and jBASE/TAFC/TAFJ (the Temenos proprietary database
management systems).
© Copyright, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,2018 by Samman-
Livingston IT Consulting – All Rights Reserved – Reprint or redistribution of this document is not
allowed without written permission.

t24 290 Expanded Due Diligence Questions 30 Mar 2018 Ver 1 03

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

t24 290 Expanded Due Diligence Questions 30 Mar 2018 Ver 1 03

Hochgeladen von

Copyright:

Verfügbare Formate

T24 Due Diligence Questions Expanded 30 Mar 2018 135 1

SAMMAN-LIVINGSTON IT CONSULTING (www.sam-v-it.com)

The nature of the project, questions to ask in this respect. . .

Configuration of the T24 system and what you should ask. . .

Technology. . .is it here to stay, here to change, or hearsay. . .

Last twenty-nine questions. . . short and to the point. . .

Beware of “Penalties” clauses for one—here’s an example:

Source code escrow

103. What does the vendor do in this respect?

Fees and expenses

Definition of Terms and References

Project Phases and Services

T24 Implementation - ACCESSBANK

Systems Integrator/Programme Manager & Project Team Appointed

Introduction to Temenos Implementation Methodology - Handover of Templates

T24 Model Bank Implementation

Implementation Main Pre-requisites

Initial Architecture Workshop with recommendations

Architecture document definition

Systems Administrator for Bank Appointed and in place - Bank Activity

Security Administrator for Bank Appointed and in place - Bank Activity

Database Administrator for Bank Appointed and in place - Bank Activity

Software change management system in place - Bank Activity

Hardware purchased and ready - Bank Activity

Network ready - Bank Activity

Infrastructure ready for implementation - Bank Activity

Initial Environment Setup

Set up Initial Test Environment

Book Technical Consultant

Carry out installation activities

Carry out basic checks post setup

Technical Training - Standard for Implementation Team

Technical Training - Standard for Implementation Team

Confirm location of training

Book trainer with least likely VISA issues if appropriate

Apply for VISA

Agree Agenda with both parties

Carry out training

Technical Training Complete

Business Training - Standard for Implementation Team

Confirm training resource

Confirm trainees from ABA

T24 Introduction Training

Model Bank TAABs training

Obtain post training feedback

Business Introductory Training Complete

Business Requirements & TAABS Completion

Meetings with PMO to identify resources

PMO to confirm availability of resources

Propose outline schedule for workshops

Agree schedule of workshops

Confirm resources & arrange travel/accommodation

Business Reviews for TAABS Completion (Reference Processes)

Model Bank TAABS Review Oversight

Process Walkthrough / Product Definition

Review / Agree Processes, Products, Services

Technical Parameter Requirements

Define Technical Parameters

Temenos Support Integration Test Scripts Preparation

Business Reviews for TAABS Completion complete

Test Script Production Complete - Bank Activity

Model Bank Reporting & Interfaces

Identify rsource for Central Reporting Analysis & Definition

Carry out Analysis of AZ Reporting Requirements