TLM Impl and Migration Domestic Cash Reconciliation v 1.0

8/10/2019 TLM Impl and Migration Domestic Cash Reconciliation v 1.0

1/13

Domestic Cash TLM Migration 12/30/2014

Domestic Cash TLM Migration

Gorantla [email protected]

TATA CONSULTANCY SE!"CES #age 1 o$ 13
mailto:[email protected]:[email protected]


2/13


Table Of Contents

1. Introduction 3

1.1 Client Profile..3

1.2 Project Profile....3

2. Scope.4

2.1 Technologies/Tools....4

2.2 Business Driers....4

2.3 Ch!llenges..4

3. "econcili!tion process oerie#....$

4. Sche%! & 'B Design.$

$. St!tic D!t! Setup(

). Do%estic C!sh *!tch +ogic I%ple%ent!tion..,

).1 -CD s Do#nlo!d ....,

).2 -CD s -D ..1

).3 -0ception !ndling11

(. D!sho!rd Design..12

. BusinessBenefits / !lue to Custo%er.13

,. Deliverables.13

,.1 "e5uire%ents 6!thering !nd 7n!l8sis..13

,.2 Design ...13

,.3 Deelop%ent9 Configur!tion !nd :nit Testing ...13

,.4 :ser 7ccept!nce Testing .13



3/13

Client is a leading global investment bank with a strong private client base, is one of the

largest in terms of financial assets that are managed.The Clients requirement was to

streamline the reconciliation process within the business and opted for the

SmartStreams product TLM Transaction Lifec!cle Management". The ob#ective wasto eliminate the manual workaround within the reconciliation process and replace the

e$isting legac! applications with TLM.

The initial phase of implementation started with %oland and &apan business. The

opportunit! was to cover the implementation across various locations geographicall!.

The initiative was mainl! focussed on enhancing its Straight Through %rocessing ST%"

capabilities across the entire trade life c!cle. Trade Match Manager TMM", a ma#or

component of the trade processing services was envisioned to be globall! deplo!ed. 't is

a multi(currenc!, multi(legal entit! and enterprise wide solution for real(time trade

matching capabilit! with all counterparties, brokers, customers, clearing corps and

settlement agents.

)omestic cash *econciliation involves Migration of business logic from e$isting legac!

s!stem to TLM +.version. Creating automated reconciliations processes in a more timel!

manner, along with greater visibilit! of the resulting reconciliation items, is a ke! elementto reducing risk. 't was one of the important drivers behind choosing TLM. This pro#ect

primaril! had recons which were to be built from scratch. %ro#ect duration was for one

month. -eed files are received from T'T/ s!stem namel! )ownload ledger", 0C)

+122 ledger 3 451 statement", 06) statement" respectivel!. *econciliation is done

across 0C) +1227 ledger and )ownload ledger, 0C) +1227C" Ledger and 06)

Statement. 0$ception is created for all transactions whose mount doesnt nets down to

8ero and also for all the e$isting singletons.


1. Introduction

This document provides a methodolog! and approach for implementation9 migration

of a t!pical TLM *econ pro#ect and is based on e$perience gained from previous

TLM implementation9migration pro#ects for various leading :lobal 'nvestment;anks. The ob#ective of this offering is to provide a standard process, methodolog!,

framework, and governance for TLM pro#ects so that the benefits of standardi8ation,

reuse, timel! deliveries and


4/13


2. Scope;

The broad scope of work for the implementation would involve=

5. 0nd to end implementation9migration of reconciliations on TLM+. Support for >T, regression and performance testing

?. >ser Training

2.1 Technologies/Tools;

2.2 Business Driers;

2.3 Ch!llenges;


Applications

TLM 2.7,

Smart Schema 4.1

Smart Stuio 2.!

OS " #ni$

%& S'base 1(.).*

+eb Serer " +ebsphere

Thin client +eb Connect

Standardi8ation b! establishing a centrali8ed recon utilit! for all business lines.

*e(0ngineering the e$isting stock recon, to cater to the business requirements

Creating the framework for the building the cash reconciliation

*econciliation cost reduction9optimi8ation, future business growth, enhanced

productivit!

Schema levels 3 @; design as per the ;usiness requirements.

Comple$ *econciliations involving Matching and utomating, updating and

closing of 0$ceptions for the transactions between attributes of three different

Schema levels.


5/13


3. "econcili!tion process oerie#;

'n )omestic Cash reconciliation end(to(end business is implemented encompassing.

0TL services comprising of e$traction, transformation and loading the data

from various source s!stems such that it is TLM readable

The reconciliation framework for Aalidation 3 matching the Transactions

The reporting framework comprising of dashboards

The entire *econciliation %rocess implementation is depicted in -igure ?.5as below=

-igure ?.5

4. Sche%! & 'B Design;

The >niverse, ttributes 3 6b#ects in schema 3 @; are built as per the businessrequirements. 'n Legac! s!stem feed files are generated from Source s!stem namel!

T'T/ )ownload file" 3 0C) +12 Ledger 3 451 Statement". The +12 ledger

from 0C) s!stem is duplicated as +1227 3 +1227C through 0TL. The Legac!

s!stem is as shown below in -igure B.5

TATA CONSULTANCY SE!"CES #age % o$ 13


6/13


niverse 'tem consists of

three levels of schema %; 06) Statement, %; )ownload Ledger, %; 0C) under the

base level of %; )omestic Cash *econciliation %osting as shown in -igure B.+,.The

amount 3 Currenc! attributes are added at base level to enable multi level matching.


7/13


The schema attributes for all the Schema levels as e$plained in the )C7Schema

model.$ls

The @; file is the base for the :0MS engine to read the feed file received from 0TL

la!er. The feed file is processed through 0TL such that it is in TLM readable format.

n 0ntr! in Master @b has to be done for all the @b files generated for each Schema

level 6b#ects. :ems server must be restarted to trace the changes made in the Master

@; file. The :0MS engine will terminate automaticall! if the new @b files generated

are not as per the design.To debug this scenario we need to alter the state of :0MS in

Aerbose mode such that the :0MS log contains more descriptive 3 user friendl!

error messages.

$. St!tic D!t! Setup;

Static data setup include sset *egister, Currenc! loading 3 ;usiness )ata Categor!,

ccount 3 message feed" 'nsertion.

$.2 Currenc8 pdate SST table e$ecuting following command=

update s!st set s!st7string D E (sFSA (cp5 (rp? (dp (ep+ (fpG (dfMM))E where

s!st7nameDEC>**0/C7%*ME

?. The s!stemEs base currenc! is defined in the S!stem Configuration Table s!st"

with a SST7/M0 of E;S07C>**E which is >S) in %; Master Trust

pro#ect".>pdate s!st table to define a base currenc! b! e$ecuting the following

commandH

update s!st set s!st7stringDE>S)E where s!st7nameDE;S07C>**E

B. %lace the asset register file e.g. TLM7C>**0/C.t$t into 9tmp director! for

loading purpose.

1. Start stocks engine e$ecuting following command=

TATA CONSULTANCY SE!"CES #age ' o$ 13

%C-SchemaMoel.$ls$


8/13


tlmstart TLM); currenc!

G. Login to *econ dmin.

. :o to Servers (I Aalidations branch.J. *ight click and select 'nsert.

4. Make an entr! be giving -ilename as 9tmp9 TLM7C>**0/C.t$t, select

currenc! from Servers dropdown and click 6@.

52. 6nce the entr! disappears from Servers (I Aalidation branch, loaded data can be

checked in currand cr!t tables.

55. curr ( This table holds information that defines a currenc!.

5+. crat( 't records the Currenc! e$change rates to the s!stemEs base currenc! >S)"rate.

5?. 'n *econ dmin the loaded currencies and their rate can be checked under

Currencies branch=

$.3 Business D!t! Insertion;

0ach account will be represented b! a cash account.

ll accounts carr! >S) amounts.

The Static )ata like Categories, Lead Sets, Sets and Message -eeds are

configured through one time process. There are two set of accounts to be

created in TLM.

5. )) to ))=

a. +122 K Ledger+1227domcash7"

b. )ownload K Ledger

c. 451 K Statement

+. 06) to +122

a. 06) K Statement

b. +122 K Ledger+1227domcash7C"

TATA CONSULTANCY SE!"CES #age ( o$ 13


9/13


). Do%estic C!sh *!tch +ogic I%ple%ent!tion;

).1 -CD =(2$>7 +edger? s Do#nlo!d =+edger?;

'f there is 5 )ownload record and 5 ))+1227" record irrespective of

amount /ets to ero". )ownload record is moved to %erfect match9istor!. Cat,

Match Subcategor! and download N are copied from download record to )) record.

'f there is atleast 5 )) record but no )ownload records Match Categor! is set to

O>nassignedH. Match Subcategor! is set to O>/@H. )ownload N is set to O(5H.

There is no concept of creating 0$ception eader over here for breaks between ))

record and )ownload record. The following table G.5 will summari8e pass details 3

figure G.5 has Matching logic.

Scope '*S D 6utstanding

%opulation &%M%;9%; )C )ownload

&%M%;9%; )C 0C) %osting where account D +1

:roup ;! Transaction /umber, Corr cc /o

%P* 5 5 )ownload record and 5 )) record

%P* + t least 5 )) record but no )ownload records

T!le ).1


10/13


).2 -CD =(2$>C +edger? s -D =St!te%ent?;

:rouping is done b! Transaction number.

Matches the transactions whose mount nets down to ero 3 send allcorresponding matched Transactions to istor!, >pdates match )ate to s!stem date

and >pdate Match /umber to mingin" as shown in -igure G.+.The %ass details are as

shown in Table G.+.


%opulations &%M%;9 ))+1227domcash7C"

&%M%;906) Statement

:roup ;! Transaction /umber

%P* Man! 06) K Man! ))+1227domcash7C"

T!le ).2

Yes

S), set

6verShort-lag to True in TLM as shown in figure G.?.The pass details are as

mentioned in Table G.?.


%opulations &%M%;9 ))+1227domcash7C"

&%M%;906) file

&%M%;9Common eader

:roup ;! Transaction /umber

%P* Man! 06) K Man! ))+1227domcash7C"

T!le ).3


Net Amount =0,at least 1 EODand 1 DDA(72500)

record

:pd!te !ll records to

istor8/Perfect *!tch.

: d!te *!tch D!te


11/13


nderl!ing transactions amount

nets down to 8ero else the particular e$ception eader values are updated with the new values

and the transactions remain outstanding. This Scenario is same for all the )ownload, 0C)

+1227 Ledger", and 0C) 451" Statement Transactions but, the population 3 grouping

Columns var!. The pass details for )ownload, +1227 Ledger", and 0C) 451" statement

are summari8ed in Table G.B, Table G.1, Table G.G and Match logic is as shown in figure G.B

respectivel!.


%opulations &%M%;9)ownload

&%M%;9Common 0$ception

:roup ;! cct /umber, Match Categor!, Match Subcategor!, Settle )ate, download,

report name

%P* 5 0 does not e$istR Create 0$ception eader

%P* + Transactions e$istR Close 0$ception eader

%P* ? blank" >pdate 0$ception header

T!le ).4




12/13


%opulations &%M%;9+122

&%M%;9Common 0$ception where account D +1

:roup ;! ccount, Match Categor!, Match Subcategor!, Settle )ate, 0C) download




T!le ).$


%opulations &%M%;9451

&%M%;9Common 0$ception

:roup ;! ccount, Match Categor!, Match Subcategor!, Settle )ate




T!le ).)


13/13

Centrali8ed reconciliation tool for all business lines with standardi8ed

reconciliation processes across products and functions supported b! common

reconciliation platform

Scalable and stable recon capable of handling large volumes

0nhance the frequenc! of reconciliation for business needs

0nhanced control and productivit! improvements with considerable cost and risk

reduction.

chieve udit and Compliance requirements

'mproved ;usiness Continuit! %lan

'ncreased ST%9Match *ate with higher automation

;etter9improved M'S reporting for the management

*educed %rocessing Time

eplacement of the e$istin/ le/ac' application 0hich 0as not as

e$ible as TLM for econciliation process ,business reuirements an


. Business Benefits / !lue to Custo%er

,. Delier!les

-ollowing documents would be delivered as per the various implementation stages=

,.1 "e5uire%ents 6!thering !nd 7n!l8sis%ro#ect %lan

-unctional Specifications )ocument

,.2 Design)esign and Mapping documents for 0TL

Configuration )ocuments for TLM

,.3 Deelop%ent9 Configur!tion !nd :nit Testing>nit test resultsS'T %lan

,.4 :ser 7ccept!nce Testing>T sign(off

-inal application code base9 configuration component Suport


TLM Impl and Migration Domestic Cash Reconciliation v 1.0

Documents