Capability vs Complexity
Finance infrastructure that works at one stage of a business often does not work at the next. The gap between complexity and capability is where commercial risk accumulates.
What makes a business financially complex?
Business complexity is not simply a function of revenue. Two companies of the same size can require very different finance functions.
A business becomes more financially complex as it adds entities, markets, products, currencies, transaction volume, regulatory requirements, and external capital. The combination of these factors determines the finance capability required, more than the revenue number alone.
| Complexity driver | What changes for finance |
|---|---|
| Entities | Consolidation, intercompany eliminations, and group reporting |
| Markets | Local requirements, tax regimes, and operating complexity |
| Products and channels | Profitability analysis, margin visibility, and performance tracking |
| Currencies | FX management, treasury, and consolidated reporting |
| Transaction volume | Automation, reconciliation at scale, and controls |
| Capital | Cash forecasting, investor reporting, and governance |
| Regulation | Compliance, audit requirements, and controlled processes |
Each driver adds demand to the finance function. When several are present simultaneously, the capability required increases significantly.
What happens when finance does not keep pace?
Most businesses do not suddenly develop a finance problem. The signs appear over time.
Reporting cycles lengthen. More of the finance function moves into spreadsheets outside the accounting system. Different teams arrive at different numbers for the same metric. Forecasting requires increasing manual effort. The finance function spends a growing proportion of its time assembling information rather than interpreting it.
At a certain point, the complexity of the business has moved ahead of the capability supporting it. That is the finance capability gap.
- Reporting
- Information arrives too late or at the wrong level of detail.
- Planning
- Budgets become outdated quickly and forecasts require significant manual work.
- Insight
- Finance can report what happened but struggles to explain why.
- Control
- Processes increasingly depend on individuals, spreadsheets, and workarounds.
- Systems
- The accounting system works, but much of finance happens outside it.
- People
- The team is working harder, but adding headcount does not solve the underlying problem.
Matching capability to complexity
Most businesses do not know where they sit on this map. The gap is rarely obvious from inside the function until something breaks.
A business in the gap zone is carrying more complexity than its finance function can support. The risk is invisible until reporting fails, a forecast misses badly, or a decision is made on incorrect information.
A capacity problem and a capability problem are not the same thing
When finance starts struggling, the immediate response is often to add headcount. That may be the right answer. In many cases the constraint sits elsewhere: people, process, systems, data, governance, or AI.
A company with weak processes does not necessarily need another accountant. A company with unreliable data does not necessarily need a new ERP. And a company with significant manual work does not necessarily need more finance headcount.
The appropriate response depends on where the constraint actually sits. Identifying it is the necessary first step.
The answer may be to strengthen the existing team, hire new capability, improve processes, change systems, outsource specialist work, or automate repeatable activity. In most cases it is some combination of these, sequenced in the right order.
Build for where the business is going
The appropriate finance function is one that can support the complexity of the business today, while being structured to handle what comes next. Size and sophistication are secondary to fit.
That means asking, regularly, what capabilities the business needs now and what it will need in the next 24 months. Then deciding, for each one, whether to build internally, hire, outsource, use fractional support, or automate.