The Bangalore Burden
For twenty years, the decision to move a finance function to Bengaluru was a reflex. The proposition was simple: take routine knowledge work, send it to a city with an inexhaustible supply of English-speaking graduates, pay a fraction of Western wages. No procurement committee had to justify it. No CFO was ever sacked for following the herd.
The herd, however, has bid up the price of the pasture.
The turnover tax
The most punishing cost of the legacy model never appears on an invoice. Annual staff turnover in business process management across India's tier-one cities runs between 30 and 40 per cent, according to Nasscom, and in high-demand cycles it moves faster. For a call centre, that churn is painful but survivable. For a finance function, it is corrosive.
Finance runs on institutional memory. A senior accountant who has managed a client's ledger for two years knows which reconciliation items recur every quarter, what the auditors will ask for, and which month-end sequences deviate from the standard because of a legacy system nobody has replaced. None of that transfers in a handover document. When she leaves, her replacement needs three to six months to reach baseline competence, longer to handle exceptions without escalating. At 30 to 40 per cent attrition, the odds favour a departure within two years. The cycle repeats. Its costs compound.
Wages catching up
India's success has made it expensive. Multinational firms, global capability centres, and the big accountancy networks all chase the same pool of qualified professionals across Mumbai, Bengaluru, and Hyderabad. Salary growth has run at 10 to 12 per cent a year, roughly three times the rate in Western Europe and well above the pace at which outsourcing contracts are renegotiated. A finance director still operating on a rate card agreed several years ago is paying yesterday's price for today's talent market. The labour arbitrage has not reversed, but the margin of safety it once provided has thinned to the point where, in a growing number of engagements, it has disappeared entirely.
The clock problem
India sits at GMT+5:30. For a finance team in London, the working day ends roughly when Bengaluru's begins. For most of offshoring's history, the gap was easy to absorb. Batch processing tolerates delay: send the work east at close of business, receive it in the morning.
What has changed is the work itself. Finance has grown more tightly coupled to real-time operations: shorter reporting cycles, tighter cash visibility windows, forecasting that feeds decisions rather than simply recording them. In that environment, a twelve-hour lag means an error in overnight consolidation propagates into the liquidity position and the management accounts before Bengaluru has started its day. The workarounds (extra management layers, early-morning bridging calls, extended timelines) are expensive remedies for a problem that is, at root, geographic.
A 2022 Deloitte survey of CFOs at European mid-market firms ranked responsiveness of outsourced teams as the second-highest source of dissatisfaction with offshore arrangements, behind only staff turnover. The two problems reinforce each other. A team that is both frequently replaced and twelve hours away will, structurally, always be slower than one that shares your working day.
Why firms stay anyway
Outsourcing decisions, once made, are rarely revisited honestly. The cost of switching (migrating processes, retraining teams, absorbing the transitional dip) is concrete and immediate. The cost of staying is diffuse, cumulative, and easy to discount. Finance leaders renew legacy engagements because switching feels riskier than staying, even when nobody has formally concluded the existing model is still the best option.
A serious total-cost-of-ownership analysis tends to disturb that comfort. The visible costs (invoiced fees, management salaries) are weighed against the risks of change, while the invisible costs (attrition, replacement training, timezone-driven rework, and wage inflation running above contracted rates) stay off the ledger. When those costs are finally assembled, the model that looked cheap in 2005 and defensible in 2015 often looks like something else.
Where the original conditions still hold
Ledgeris operates in Nigeria, so we should be plain about our position. But the argument does not depend on taking our word for it.
Nigeria sits at UTC+1. For a finance team in London, that is a one-hour difference, close enough to share a full working day. The twelve-hour lag that defines the Bengaluru model does not apply, and neither do the workaround costs that come with it.
The professional infrastructure is more developed than most European finance leaders assume. The Institute of Chartered Accountants of Nigeria has over 63,000 members and models its qualification framework on British chartered accountancy institutes. Its credentials carry reciprocal recognition with ICAEW in the UK and CPA Ontario in Canada. Nigeria has more than 53 million people aged 18 to 35, English is the language of business and professional education, and the country's BPO sector is the second largest on the continent.
On cost, the gap with India is substantial. Labour costs across African outsourcing destinations run up to 80 per cent below US and European levels, and Nigeria's labour market has not yet been through the wage escalation cycle that eroded India's original advantage. The savings on offer today are not already being consumed by the increases of the next contract cycle.
Nigeria carries its own risks, and any honest assessment must account for them. Infrastructure remains uneven: power supply, internet reliability, and logistics in certain regions all require workarounds that a Bengaluru operation can take for granted. These are real constraints, concentrated in particular geographies and improving year on year, but they are real. The question facing a finance leader is whether the total cost of a Nigerian engagement, including its frictions, compares favourably against the total cost of the Bengaluru model, including the frictions that two decades of cost escalation have piled onto it.
The arithmetic
The discomfort of transition is real but finite. A well-managed handover, with defined milestones and phased migration, typically reaches full productivity within six months. The accumulated costs of the legacy model accrue every month, with no endpoint in sight.
The default still works. Whether it still works well enough to justify what it costs is the question that a genuine total-cost analysis will force into the open, and one that fewer finance leaders are finding comfortable to leave unasked.
For twenty years, the decision to move a finance function to Bengaluru was a reflex. The proposition was simple: take routine knowledge work, send it to a city with an inexhaustible supply of English-speaking graduates, pay a fraction of Western wages. No procurement committee had to justify it. No CFO was ever sacked for following the herd. The herd, however, has bid up the price of the pasture.