My Links
Home
Contact
RSS 2.0 Feed
Login
Archives
September, 2011 (1)
August, 2011 (2)
July, 2011 (2)
March, 2011 (1)
November, 2010 (1)
October, 2010 (9)
September, 2010 (8)
August, 2010 (2)
June, 2010 (2)
February, 2010 (1)
January, 2010 (1)
October, 2009 (3)
September, 2009 (2)
August, 2009 (5)
June, 2009 (1)
April, 2009 (3)
March, 2009 (4)
February, 2009 (3)
Post Categories
Cash Forecasting (rss)
Cash Positioning (rss)
Decentralized Cash Management (rss)
Features & Functionality (rss)
General (rss)
GL Integration (rss)
Hedge Fund Implementation (rss)
Integration (rss)
Multi-Currency Support (rss)
Payments (rss)
SWIFT (rss)
Training (rss)
Treasury System Adoption (rss)
Treasury Workstation Reporting (rss)

Wednesday, July 27, 2011

Configuring Centralized & Decentralized Cash Management in TS CMO - Part 2

Todays post continues that series of posts that describes the ability of TS CMO to support multiple centralized and decentralized cash management and positioning needs of enterprise organizations. Today we will look at a case of decentralized cash management. (Please read the first post the describes a centralized scenario as well)

Decentralized Cash Management - Consider an organization head quartered in the US with operations in US and Canada, the US organization managing the treasury (cash and investments) for the US and the Canadian subsidiary managing their cash.

A decentralized cash management scenario is described below - the organization receives BAI files from banks and proprietary investment updates in the US and Bank proprietary files for cash and investments in canada. Cash management and Investments are decentralized and taken care of by treasury users in respective locations. Also note that two backend GL systems that TS CMO synchronizes with are part of this setup as well. You can read more about the GL integration capabilities of TS CMO here and here.
Screen Shot 2011-07-27 at 2.00.37 PM.png

To accommodate this need 2 Treasury Operations Entities are configured - Canada and US and respective users or roles and accounts or account groups are assigned. Now users in the respective organizations can perform their day to day forecasting, reconciliation, positioning, reporting and other functions w.r.t the specific set of accounts. As noted previously, not all accounts need to be used position and they can be classified as such.


A third Treasury Operational Entity called North America is created with access to all accounts and is assigned to a specific set of senior management users who would need access to data across the enterprise- Note that users using this entity will use it for view only access as the cash management functions are performed within the US or Canada entities created earlier. This configuration is described below.


Screen Shot 2011-07-27 at 2.05.28 PM.png

It is important to note here that we went from centralized positioning (described in the previous post) to decentralized positioning purely via end user configuration. It is also important to note that in the event that a new user or set of users need to perform a cash management function, all an administrator has to do is to assign that user or the role of the user to the appropriate tag using a web browser.
We will look at the same feature set in even more complex scenarios in the next couple posts. Thank you for reading.

posted @ Wednesday, July 27, 2011 2:40 PM | Feedback (0)


Powered by: