Reporting and Finance

Centralized Operations: A Key to Improved Financial Performance

A finance-focused look at consolidating back-office work into shared services centers: where costs can fall, where they can rise, and why results are never guaranteed.

On this page
  1. The financial argument in one paragraph
  2. What gets consolidated
  3. Where costs can fall
  4. Where costs can rise
  5. A simple illustration
  6. Cost is not the only financial effect
  7. Questions a finance team should ask
  8. When a different model may fit better

The financial argument in one paragraph

Many organizations perform the same back-office work in several places: each business unit has its own people processing invoices, running payroll, handling purchasing paperwork or answering HR questions. Moving that work into one or a few shared services centers is a common way to try to improve financial performance. The theory is straightforward. Fewer, larger teams working to common methods may do the work for less, with fewer errors, and with better information about what the work costs. The practice is less certain, and this article looks at both sides.

What gets consolidated

Typical candidates are transactional, repeatable activities:

  • accounts payable and accounts receivable
  • payroll and basic HR administration
  • procurement administration
  • expense processing
  • general ledger maintenance and reconciliations
  • IT help desk and similar support

These are chosen because they follow rules, occur in volume and do not depend heavily on local judgement. Activities that need close contact with local customers or conditions are generally poorer candidates.

Where costs can fall

Scale and workload smoothing. When ten small teams each keep spare capacity for busy periods, the organization holds ten buffers. One larger team can often cover peaks with a smaller total buffer, because not every peak coincides.

Standard processes. Doing a task one way, rather than ten, tends to reduce rework and training effort. It also makes automation more practical, since a tool built once can serve everyone. Process standardization is often where most of the efficiency comes from rather than the relocation of staff itself.

Fewer duplicated systems. Several departments may each license and maintain their own software. Consolidating onto one platform can lower licensing and support effort, though migration is a project with its own cost and risk.

Better purchasing position. Combined volume can sometimes support better terms with suppliers. This is one reason people discuss centralized procurement, although the effect varies widely between categories and markets.

Clearer cost visibility. A shared services center has a defined cost base, which makes it possible to see what a transaction actually costs. Some organizations then use chargeback and showback to make that cost visible to the units that use the service.

Where costs can rise

Honest financial analysis must include the other side of the ledger.

One-off costs. Redesigning processes, migrating data, training staff, paying for new technology and, in some cases, severance or relocation can all be substantial. These costs arrive early, while benefits arrive later and may be smaller than forecast.

Coordination overhead. A new layer of managers, service agreements, governance forums and reporting can offset part of the saving. Local units may also hire their own “shadow” staff to chase the shared center, which quietly returns cost to where it started.

Quality and service problems. If a central team is distant from the business, errors can rise: invoices coded to the wrong unit, queries answered slowly, exceptions mishandled. Fixing these takes time and sometimes extra staff.

Loss of local knowledge. People who knew why a particular supplier was paid on unusual terms may no longer be in the process. The cost of that lost knowledge is real but hard to put in a spreadsheet.

Concentration risk. Placing a large share of transactions in one team creates a single point of failure. An outage, a staffing shortage or a control failure can have a wider impact than it would in a distributed setup.

Transfer pricing and allocation disputes. Deciding how shared costs are divided among units can create friction, and the allocation method can change how each unit’s results look without changing the total cost.

A simple illustration

The numbers below are invented to show the logic, not to suggest typical results. Suppose four business units each employ 5 people on payables, 20 in total. After consolidation, the shared center needs 16 people to do the same work, because of workload smoothing and standard processes. Suppose it also needs 2 extra people for coordination and service management, so 18 in total.

That is a reduction of 2 positions out of 20, or 10 percent. If one-off project costs are equal to roughly a year of the salary of those 20 people, and the saving is only 10 percent of the annual cost, it would take around ten years to recover them at that rate. With a different assumption, such as a 25 percent reduction, the payback would be about four years. The point is how sensitive the answer is to assumptions. Anyone building a real business case should test several scenarios and involve their finance team.

Cost is not the only financial effect

Financial performance is wider than cost. Shared services may also affect:

  • Working capital, if invoices are paid and collected more consistently.
  • Control and error rates, if segregation of duties and approvals are applied uniformly.
  • Management information, since consistent coding makes it easier to compare units and to use performance metrics fairly.
  • Flexibility, which can fall if the center is slow to change or can rise if it can absorb growth without hiring in every unit.

These benefits are real possibilities, but each depends on execution.

Questions a finance team should ask

  1. Which activities are genuinely standardizable, and which are not?
  2. What is the current cost of each, measured consistently? Without a performance baseline, later claims of savings cannot be checked.
  3. What are the full one-off costs, including management time?
  4. What service levels will the center commit to, and what happens if it misses them?
  5. How will costs be allocated, and will units have any say?
  6. What would it take to reverse the decision if results disappoint?

When a different model may fit better

Smaller organizations may not have enough volume for consolidation to pay off, because the overhead of a formal center can exceed the saving. Organizations with very different business lines, regulatory settings or customer expectations may find a hybrid operating model more suitable, keeping some functions local while sharing others. Outsourcing is another option, with its own trade-offs.

Centralizing back-office operations can improve financial performance in some organizations and disappoint in others. Treat any forecast as an estimate, check assumptions regularly, and seek advice from qualified finance professionals for decisions specific to your organization.

The complete guide to reporting and finance

The Benefits of Centralized Business Intelligence
Read the guide

Keep exploring

Guides from other topics

All topics →