Treasury Strategy & Transformation
Published  10 MIN READ
Please note: this article is over 12 years old. If you feel this article is inaccurate or contains errors get in touch here . Many thanks, TMI

Making the Tough Choices

by Karin Amacher, Treasury Director, Cash Management and Oliver Wolfensberger, Global Head of Treasury Operations, Rio Tinto

Following the acquisition of Alcan in 2007, treasury needed to re-evaluate and integrate its processes and organisation in order to achieve its strategic and operational objectives. At that time, we had five treasury centres, but we recognised the potential to rationalise these centres, and streamline processes more effectively across the group.

Although the new group had a large and in some ways disparate treasury organisation, it was possible to identify and leverage the most efficient processes from within the Alcan and Rio Tinto legacy businesses. We also needed to rationalise our treasury team, whilst ensuring that there was sufficient scope for managing project work as well as daily activities.

Meeting the challenges

While some decisions were straightforward, there were inevitably some more challenging aspects of the treasury re-organisation. In some cases, there were activities undertaken by treasury that we recognised would be better managed by other business functions. In others, there were tasks undertaken elsewhere in the organisation, or distributed across business units, that needed to be centralised in treasury to enable us to perform our role effectively.

Challenge 1: Shared payments responsibility

While payments and collections are an essential function of treasury, we recognised that treasury had too broad a remit in these areas. Not only was treasury responsible for treasury payments, but we also performed a large number of vendor payments. This created a variety of challenges. Firstly, we had insufficient resources to conduct this activity, and manual payment processes increased the risk of error and fraud. Furthermore, it was difficult to verify approval requirements at business unit level. There was also a potential conflict between the activities of treasury and our shared service centres (SSCs) that have primary responsibility for vendor payments. Invoices were not captured in the ERP and were not subject to the SSCs’ approval requirements. Reconciliation was inconsistent, and it was difficult to identify who had processed the payment in the event of follow up enquiries.