Evaluating standalone treasury management systems vs. ERP treasury offerings

When evaluating technology enhancement opportunities, the first step companies usually take is to assess the full range of capabilities of the technology they already own. Typically they turn to their Enterprise Resource Planning (ERP) software as these providers are more actively promoting their treasury management capabilities and clients have already made significant investments integrating the technology and building knowledgeable resources of the product. There are benefits to be achieved from this approach, but also limitations.

The potential benefits include seamless integration with existing functionality with regards to the general ledger, accounts payable and receivable, and cash reconciliation. Additionally, connectivity with third parties – such as market data providers and banks – is often already in place and thus available for treasury’s needs. It would create one source of static data, payment instructions and general ledger accounts thus reducing time and risk of maintenance to keep master data congruent as well as any mappings to translate data between internal systems. Furthermore, most users will have existing knowledge of the application and its reporting tools.

While there are many facets to consider when evaluating your ERP treasury capabilities, there are two primary ones we see driving the majority of decisions. First is the limitation in functionality available in an ERP system as compared with a specialised Treasury Workstation. Most ERP systems contain basic treasury capabilities, and some have even made strides in expanding their instrument coverage to more structured products, however they are often not as robust as traditional treasury workstation systems. Examples of functionality gaps include the ability to model and account for complex intercompany loan structures, structure derivatives, and certain investment products. Functionality gaps force firms to manage certain products and processes offline thereby losing the benefit of having one fully integrated application. In addition to functionality gaps, many users do not find the ERP Treasury modules intuitive to use and the reporting suite and its flexibility is limited without significant customisation. Again, this could force the user to build and manage reporting offline and thus minimise the benefit of having a centralised treasury management solution.

This leads us to the second primary item driving the ultimate decision: cost. The cost to implement the treasury functionality in an ERP application is typically substantially more than a standalone treasury workstation. The implementation costs are typically three to four times as much. There may also be additional software licensing costs incurred to accommodate the full suite of functionality required – including cash positioning management, forecasting and bank fee analysis, and bank administration management. These potential licensing costs need to be factored into the overall analysis as well as ensure these additional modules are fully integrated into the existing modules being utilised.

Although our view is that leveraging your ERP to manage the entire scope of treasury functionality is not ideal in many situations, we have seen certain scenarios work well. One scenario is when your capability needs are aligned with the strengths of your current ERP provider. This typically translates to a more vanilla portfolio of financial products with a priority focus on cash management and payments. In this situation, we have seen clients be successful in leveraging the ERP to fulfill their holistic treasury needs.

Another scenario we have seen be successful, and the most common in our experience, is a hybrid approach. In this approach, the client will again leverage the strengths of the ERP tool, but also leverage a standalone treasury workstation. This is referred to as the “best in breed” approach where you select multiple products providing industry-leading functionality in specific areas and integrate them to provide a complete solution. An example of this division of responsibility is performing payments, cash reconciliation and cash accounting in the ERP, while the remaining functionality – such as deal management and the associated accounting, cash positioning and forecasting – is performed in the standalone treasury workstation. We have seen various permutations of this model, but it is most often utilised when the ERP application is already being leveraged and a new standalone treasury workstation is being brought in to fill gaps not provided by the ERP. This scenario requires bi-directional integration between the two systems. An example of such integration would entail accounting entries and potentially instrument settlements where payments are required to be fed from the treasury workstation to the ERP and anticipated accounts payable and receivable flows provided from the ERP to the treasury workstation to facilitate forecasting.

To the extent the number of applications can be limited to only a couple, the “best in breed” approach can be very successful in providing a solution to fully meet all your needs. Situations where this approach is less successful are ones when there are numerous applications with each fulfilling only a fragment of the requirements. When numerous tools are involved in the process, a large amount of time and effort is required to integrate data between the applications, and any analysis requiring a comprehensive view of your data can be very arduous, not to mention involve a significant timing lag.

While there can be benefits to leveraging ERP applications for some or all of your treasury management needs, a comprehensive analysis of the costs and benefits should be performed to ensure the ultimate solution will fully meet your current and future needs.

1645 views

Related reading