Operating Model

When it makes sense to move finance operations to a hub model

Centralising transactional finance is not automatically cheaper or better. The decision depends on volume, variability, and how much of your process is genuinely local.

Published
5 February 2026
Reading time
5 min read

The question behind the question

Hub models are usually proposed as a cost decision. In practice, the durable benefits are control and consistency: one way of processing a payable, one reconciliation standard, one escalation path.

Cost follows from that consistency. If the underlying processes remain different in every country, centralising them simply relocates the variation.

What travels well, and what does not

High-volume, rules-based work travels well: accounts payable, accounts receivable, bank reconciliation, master data maintenance, and routine reporting.

Work that depends on local statutory judgement, regulator relationships, or language-sensitive negotiation is better retained locally, statutory filings, payroll interpretation, and tax positions among them.

Sequencing the transition

Document the current process before moving it. Lifting an undocumented process into a hub transfers the risk along with the work.

Move one process and one entity first, run it in parallel for a cycle, then scale. Measure exception rates rather than headcount in the first two quarters, headcount savings that come at the cost of control are not savings.

More reading

Keep reading across the finance function.

Want this applied to your finance function?

A short diagnostic conversation is usually enough to tell you where the real constraint sits.