RPA programs head to the mainstream in financial services
By FF Newsroom · 29 January 2019

Yet only 20% of organisations are confident they can measure their successful roll-out and 70% claimed it was hard to get productivity data in the first place
Financial services companies exploring Robotics Process Automation (RPA) are finding it difficult to establish ROI because traditional measures often do not justify the deployment cost. This is according to research conducted across 50 North American mid to large-scale financial services organisations by ActiveOps, a leading provider of digital operations management solutions.
RPA is autonomous software programmed to follow rule-based tasks just as a human would. The difference is that robotic decision making and outcomes are predictable, consistent, and 100 per cent accurate.
Julian Harper, CEO, North America, ActiveOps, stated: “There are mature RPA programs in complex operations where the business case for RPA spending is important and our survey confirms that even though roughly 45% of financial services organisations have large robotics programs, only about 20% of them feel they are confident in their ability to access significant performance metrics to measure their program’s success.”
Key findings include:
- 45% of financial services organisations questioned are running 10 or more robots in their operation.
- When asked how they measured the productivity of robotics, unsurprisingly perhaps, 90% of those who responded stated that it was based on FTE hours saved.
- 48% of the sample stated that they saw variances into robotics performance, while 10% saw none.
- A staggering 70% of the sample stated that is was not easy to get productivity data on their robots.
- Measure the start time verses stop time of a back office process before and after an RPA roll-out and compare and contrast
- Measure the length of time a human spends on a tax verses how quickly a robot does the same thing
- Measure output accuracy before and after a deployment – it should be 100% post roll-out
- Check and measure compliance before and after a deployment – it should be 100% after the roll-out