
Benefits and Pensions Monitor
Step Forward, Back Office

Point Of Demand
Now, how on earth does this relate to financial services? What restauranteurs have done is to consider STP not just from the food production point of view (their ʻback office,ʼ the kitchen), but rather straight from the point of demand – you, the diner. For financial firms to get the best out of their kitchens, they also need to embrace STP from their diners (the traders, or front office). This means that, when selecting technology for the back office, you need to ensure you will also cater for those front office needs. You need to look at the full chain from trade concept on the dealing desk through all the back office functions. There are two, essential, things to consider:
- excellent communication front-toback
- simplicity in execution in the back
Excellent communication is an obvious one. From a system point of view, this means the back office system needs to be easy to interface to other systems. XML messaging, an open interface, and a clear data design all contribute to easy communications between systems. Luckily, interfacing is getting easier as systems providers embrace these facets.
Simplicity in execution is not always recognized as an essential ingredient to the success of a system selection process. What I mean by this is that a back office system needs to be able to process individual units well, without getting hung up on the entire panoply of financial instruments.
Going back to our restaurant, the chef has really become more ʻmiddle office.ʼ He does the final assembly on the plates, pours on the béarnaise sauce just so, and is the quality control for the kitchen operations. Several sous-chefs are responsible for grilling the fish and meat, preparing the vegetables, and boiling the potatoes. A good back office system does not try to be the chef, but rather sticks to the preparation of distinct, individual ingredients. It ensures it can process the units of a complex financial transaction, and does that excellently, without worrying too much about the sum of the parts or how the pieces fit together for the trader – thatʼs the job of the front office system.
Expensive Fallacy
Many people will disagree with that last statement, saying that it is essential that back office systems can understand all aspects of all financial instruments being traded. I think this is an expensive fallacy.
Just take a relatively simple instrument, such as a repo. Repos come in various guises – fixed term, open term, fixed rate, variable rate, indexed rate, cross currency, with call options, with rights of substitution, packaged together as a basket, with a tri-party agent … and more. The repo market is evolving constantly – rather like dinersʼ tastes – and front-office specialist repo systems have to evolve to meet that demand.
To force your back office system to likewise change whenever a new twist on repo trading arises is simply doubling your technology investment cost. Itʼs far better to keep the back office system simple, and leave the business intelligence in the front office system. You can put other controls in place to ensure your trader is not taking excessive risk and understands his true profit and loss on his necessarily complicated trading strategies. But donʼt believe that you have to put the same intelligence and complication into the back office system. Youʼll only be testing your back office systems developers against your front office ones!
Of course, you can avoid this back office/front office system struggle by getting a ʻfront-to-backʼ system for particular parts of your financial operations. This makes sense for some trading products and for some shops, but is not always the optimal solution. Careful consideration has to be given to the benefits of having a single front-to-back system for a business vertical versus the potential overlap in back office processing with other back office systems processing other parts of your trading.
Like creative diners, traders, by nature, are always dreaming up special orders and will have requirements for individual transactions that donʼt fit the menu. Good front office technology will be designed to cope. The back office system needs simply to process the simplified components coming from the front office. Following this approach gives you the most benefit from true STP – seamlessly from the diner, to the kitchen, and back again!
Bon appetit! ■
Malcolm Clark is director, strategist, at Anvil Software.
< previous
|