The Lure of Outsourcing in Accounts Receivable and Accounts Payable

The move toward widespread finance and accounting outsourcing (FAO) appears both undeniable and unstoppable. Numerous large corporations have already outsourced significant transactional activities. This activity has taken many forms and included both financial institutions and third parties – and often partnerships between the groups. Yet relatively few banks have accounts receivable outsourcing (ARO) or accounts […]

Author
Bob Meara Date published
April 23, 2007 Categories

The move toward widespread finance and accounting outsourcing (FAO) appears both undeniable and unstoppable. Numerous large corporations have already outsourced significant transactional activities. This activity has taken many forms and included both financial institutions and third parties – and often partnerships between the groups. Yet relatively few banks have accounts receivable outsourcing (ARO) or accounts payable outsourcing (APO) offerings beyond the staple wholesale lockbox and disbursement products. Those that do are glad they do.

Against the backdrop of FAO growth by third parties, along with its favorable client impact, banks would be hard pressed to defend inaction. Clearly nascent and not without challenges, APO and ARO represent strategic levers for cash management banks in the quest for revenue growth. Banks can choose to get involved, securing a more strategic position with clients, or relinquish the opportunity, leaving for themselves an increasingly commoditized payments business at the tail end of their client’s financial supply chain.

Celent encourages such forays into APO and ARO, as some early movers have already done, albeit in measured, incremental ways. A specific example is profiled later in this article. In contrast, full-scale FAO (e.g., outsourcing entire departments) should be left to the likes of Accenture and CapGemini.

A common challenge for banks seeking to field APO and ARO solutions is in developing adequate domain knowledge to get the product right the first time. While this may be a classic product development challenge, the way forward for banks doesn’t have to be overly difficult or risky. That’s because multiple solution providers are ready, willing, and able to engage in partnerships with financial institutions to deliver FAO solutions to the market. It is a win-win.

Celent recently interviewed banks, FAO providers, practitioners, and software venders to distill the opportunity and implications for banks in APO and ARO, offering these observations:

The benefits to financial institutions of extending into APO and ARO are manifest, yet doing so will require some courage because it will not be easy. Demand for such services is growing, and moving solidly into the mid-market. But the opportunity does not resemble the tidal wave of remote deposit capture demand, for example, but more of a gently rising tide. Thoughtful action is warranted.

FAO: The Time Has Come

Finance and accounting outsourcing (FAO) is indeed an idea whose time has come. Increasingly, companies are looking for ways to bolster their bottom lines with cost savings and organizational efficiency gains. Meanwhile, many banks are facing stagnant cash management revenues, with little optimism for a sustainable rebound unless decisive action is taken. Activity is occurring on both the payables and receivables side, but the more significant opportunity may be in accounts payable outsourcing (APO) solutions.

Why now? First consider the client perspective. While companies have been outsourcing bits and pieces of their finance and accounting function for 30 years, multi-process FAO is reaching the rapid growth stage, according to a September 2005 report by the Everest Research Institute. There are several factors:

And, from the financial institution’s perspective, why now? What are the drivers?

Where to Participate

All manner of FAO services are being offered, from specialized processes such as collections or payroll management to complete outsourcing of entire payables or receivables functions. Some of these (e.g., collections) provide no obvious synergies with services financial institutions have historically provided. Other examples are close to where banks already play in the financial supply chain, and movement there can be considered a logical step. For example, Key Bank leveraged its roots in disbursements to move into payroll management and beyond. It is Celent’s view that such ‘incremental’ movement (versus the outsourcing of entire functional areas) represents the best near-term opportunity for financial institutions.

APO and ARO are both viable for incremental extensions of banks’ current services. Of the two areas, receivables offer the most logical place to start. Lockbox has been around for decades and has near saturation adoption. By providing lockbox services, banks have placed themselves well into clients accounts receivable work processes. Few banks, however, have ventured up the receivables side of the supply chain. In contrast, banks have not had a rich history of being connected with clients’ accounts payable – beyond payment origination. Yet comparatively more examples exist of banks successfully launching APO solutions. Why the apparent incongruity? Celent’s view is that it was banks’ relative absence on the payables side that invited innovation by third parties. In essence, banks are now in the position of having to play catch up. In contrast, banks have long since ‘owned’ the wholesale lockbox environment. Figure 1 shows examples of incremental (or specialty) FAO services in a financial supply chain context.

Figure 1: Specialty Versus General FAO Examples

How to Get Started

Three obvious options exist for financial institutions seeking an expanded participation in clients’ financial supply chains: go it alone, partner with a third party, or acquire an existing FAO provider. Several well-known examples are listed in Table 1.

Table 1: Typical FAO Implementation Overview (16 Weeks)

Stage Activity Documentation
Project initiation
(1 to 3 weeks)
Presale technical review.
Requirement gathering
Statement of work (SOW) development.
Master service agreement.
SOW.
Planning
(4 to 5 weeks)
Project plan development.
Detailed work breakout.
Project schedule.
Project plan.
Execution
(4 to 6 weeks)
System definition and design.
Development user
acceptance testing (UAT).
User training.
Workflow and use case design.
Post-test system approval.
Closure
(1 to 2 weeks)
Final project reporting
Transition to live environment
Project summary document.

Source: FAO provider interviews

Arguments can be made for two of the three options. Going it alone, however, would prove difficult unless the initial solution scope was purposefully narrow (e.g., invoice capture) and closely tied to a bank’s core competency (e.g., lockbox). Here’s why:

Exit mobile version