Community
The banking industry has become a buyer's market, where corporate treasurers carefully select their bank relationship partners and demand more added-value services. Should banks stay on separate product lines or offering packaged solutions in order to meet customer needs?
One of the frequent topics debated in transaction banking (and, in particular, in supply chain finance) today relates as to whether banks can remain profitable once they start selling integrated packages rather than separate (a.k.a. ‘vertical’) product lines (e.g. cash management, trade finance, open accounting, etc). The greatest fear suffered by banks is that they might start losing revenue and cannibalise product lines.
The approach I always recommend is to learn from the successful practices of the ones that have had similar experience in the past. There’s no need for banks to ‘reinvent the wheel’ if they can learn best practices from others, even if these come from completely different industry sectors. One valuable source of good practices is from the IT industry in the physical supply chain. This is a sector in constant evolution - a buyer’s market heavily exposed to customer demands and standards compliance. Not so dissimilar from the banking world, after all. I found the paradigm of IT extremely helpful to illustrate how banks can take inspiration from software vendors when deciding how to best deploy a business plan strategy to build and install electronic platforms (e-platforms) for global transaction services. To answer corporate banking product managers as to whether profit is lost when abandoning vertical product lines, I refer to my preferred area of corporate IT: the supply chain marketplace of enterprise systems.
During the late 70’s, supply chain management application software vendors had to decide whether they would stay with a portfolio of separate software applications product lines (e.g. production planning and execution, warehouse management, logistics, parts purchasing, inventory control, product distribution, order tracking, etc) or merge them into an integrated multi-module software system. The latter option was chosen, which eventually opened up the era of the materials requirement planning (MRP) systems. MRP, in turn, evolved in the late 80’s into enterprise resource planning (ERP) systems. Players like SAP, Oracle, JD Edwards, Baan, and Peoplesoft, expanded the footprint of the MRP and moved from co-ordination of manufacturing processes to the integration of enterprise-wide backend financial applications and human resources processes (e.g. finance, accounting, accounts payables (A/P), accounts receivables (A/R), HR, etc) to provide a complete solution to a company for managing their inventory, cash and people resources.
The decision criteria used to opt for MRP first and, subsequently, for ERP weighted the risks of operating in a competitive market and offering a piecemeal of separate software ‘verticals’. These risks entailed:
ERP vendors also learned that they might have lost some revenue by blurring the lines between rewarding vertical product lines, but gained in profitability because they were able to attach lucrative (and more scalable) added-value services to the selling of the ERP ‘product’: post implementation maintenance, system integration, consulting, and training. The enterprise software vendors also evolved their supply chain management products into the ERP because they had to follow their corporate clients who were also evolving: modern organised companies started to integrate their various internal functions. The manufacturing sector, particularly automotive, was the first to experience this trend thanks to the influence of Japanese ‘just-in-time’ and ‘total quality management’ practices which revolutionised the work organisation structures still centred around the predicaments of Taylor and Ford (i.e. mass production, segregated duties, quality at the end of the line, and ‘any colour the customer wants, as long as it’s black’).
In summary, the lessons learned from the ERP vendors are:
Turning back to banks (i.e., the financial chain) and to the focus theme of this article regarding staying on separate product lines or offering packaged solutions, an overview of the major business imperatives pressuring the banking industry can help:
If there’s only one thing we should take from the ERP ‘lessons’ is that the key heart of an ERP lays in its ability to improve the performance of the internal (physical chain) business processes of a company. The magic word is ‘processes’.
This for banks (i.e., financial chain) means that:
This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.
Alexander Boehm Chief Executive Officer at PayRate42
02 September
Azimkhon Askarov Co-partner at CONCRYT
Edvards Margevics Co-partner at CONCRYT
30 August
Ellen Roberson Global Marketing Advisor, Risk, Fraud & Compliance at SAS
Welcome to Finextra. We use cookies to help us to deliver our services. You may change your preferences at our Cookie Centre.
Please read our Privacy Policy.