Looking for a treasury/debt management system capable of handling multi-currency, multi-entity, multi-account and that is easy to amend loan terms. Any suggestions?
Answers
easy is in the eye of the beholder (user)
Any of the major
For multi currency accounts the workstation used feeds from pricing services to track Euro, GBP and other currencies.
workstations also maintain legal entity structures to roll up loans to the apprpriate parent.
Downside - cost to set up, train and implement
That said, what do you mean by "terms". None of the workstations can review / calculate loan covenants as this type of calculation requires reading then converting credit agreement into calculations which can have many exemptions or carve outs depending on the creative of the banker, legal language, etc.
Hi there! Great questions and thoughts from Bruce. The only system I have implemented (besides of course massive
I agree with Bruce: most treasury workstations will be able to record, eventually amend or process debt transactions. The key decision point we've seen at IT2 concerning debt is the flexibility around the capture, the security and the modification of existing trades (without re-capturing / re-processing them).
Depending on what your goals are, advanced debt reporting (including basic covenants calculation, but also position analysis), entity reporting (from trade or
We have had good experience with the TMS from City Financial, now part of Wall Street Systems for loans, loan tracking, and FX including SWIFT confirmations, but have found limitations beyond that. This is WSS' middle market solution with some customization. I think Treasura is WSS' entry level system and they also have a fully customized large corporate system which is very comprehensive We are looking at Kyriba for local implementation of their multi-currency cash management, position and reconcilement modules including direct links to our banks (Kyriba currently links to over 780 banks) and our accounting system and I understand they have a robust loan module, which we haven't evaluated yet. But I agree with Stephane, it's the integration opportunities, elimination of manual data entry points, and input data verification that should be the driver.