Part of the Outgrowing your finance systems series.
A group finance function does not break all at once. It breaks in a sequence, and the sequence is almost always the same. The danger is that each stage looks like a temporary pressure rather than a structural limit - until the limit becomes undeniable and the cost of catching up is far higher than the cost of acting earlier would have been.
How do you tell a busy month from a structural limit?
A busy month resolves itself; a structural limit repeats and compounds. The clearest test is whether the pressure is isolated to a single cause - an acquisition, a one-off restatement, a systems outage - or whether it recurs across every close regardless of external events. When the team is consistently at capacity before anything unusual happens, you have crossed from capacity management into a structural problem. The distinction matters because busy months justify short-term measures; structural limits justify investment.
What breaks first: the close calendar?
The close calendar is almost always the first signal. What was a ten-day close becomes twelve, then fourteen, and the drift happens gradually enough that it is rationalised at each step. Quarter-end takes longer than month-end by a margin that widens each year. The mechanism is not mystery: as the group adds entities, currencies, or reporting lines, the volume of data moving through the close grows faster than the team's capacity to process it. At some point the calendar is no longer a target - it is a negotiation. When the finance leadership team spends as much time defending the close timetable as running it, the calendar has become a symptom rather than a schedule.
Why do intercompany and eliminations absorb so much review time?
Intercompany reconciliation and consolidation eliminations consume disproportionate review time because they are the point where group complexity is most visible. Every new entity, every intra-group trading relationship, every intercompany loan or shared-service recharge adds to the matrix of balances that must agree before a consolidated position can be signed off. As groups grow through acquisition or organic expansion, this matrix grows combinatorially - not linearly. A team that could handle reconciliation at review speed for a smaller group finds itself doing detective work at every close, tracing mismatches that exist because reporting timetables, currencies, or accounting policies are not yet aligned. The time absorbed here is not wasted; it is doing real work. But it is work that has crowded out higher-value analysis, and that trade-off is a signal.
When do reporting requests start to exceed what the function can deliver?
A finance function has structurally outgrown its capacity when it cannot answer a reasonable board question inside a single board cycle. This is a sharper test than it sounds. Boards ask questions that require data to be cut differently from the standard pack - by geography, by product line, by legal entity, by acquired versus organic growth. If answering those questions requires a material allocation of analyst time that competes with the next close, the function is operating without headroom. The consequence is not just delayed answers; it is that the board learns to stop asking, and the finance function loses its seat in the room where decisions are made.
What does key-person dependency tell you about structural strain?
Key-person dependency is a late-stage signal, but it is one of the most diagnostic. When a process - whether the consolidation, the intercompany sign-off, or the management accounts commentary - cannot run without a specific individual, that process has no structural integrity. It is a person, not a system. In a growing group, this matters more each year: the individuals in question are typically the most senior and most expensive members of the finance team, and their time is being used as a substitute for process design. The risk is compounded because these individuals often do not surface the fragility - they absorb it quietly, working the hours required to keep the function moving. Which leads directly to the final signal.
How does overtime become a silent subsidy to the business case?
Overtime that is structurally necessary - not occasional, not project-related, but recurring every close - is the finance function funding its own capacity gap from the personal time of its people. It does not appear on a cost line. It does not appear in the board pack. But it is real, it has a limit, and when the individuals who are carrying it leave or burn out, the gap becomes visible and acute rather than slow and manageable. Group CFOs who have inherited a team in this state typically describe two surprises: how long it had been going on, and how quickly things deteriorated once the load-bearing individuals left.
Why is this a trajectory problem, not an incident?
Each stage in this sequence looks, in isolation, like something that can be managed. The close runs a day longer - acceptable. Intercompany takes more review time - the team is thorough. A board question takes two weeks to answer - it was a complex request. One controller is indispensable - she is very good. The overtime is high - it is a busy period. The reason this is a trajectory problem is that none of these observations is wrong; they are just incomplete. The pattern across all of them, tracked over time, is the diagnosis. By the time the strain is undeniable, the close calendar has drifted significantly, the team has lost its best people, and the board has reduced its expectations of finance. Catching that trajectory early - before it becomes an incident - is the work of a Maturity Matrix assessment: rating the finance function as it actually operates today, not as it was designed to operate, and costing the gap in pounds rather than in abstract risk.
Common questions
What is the first thing to break when a group outgrows its finance function?
The close calendar is typically the first structural signal. What was a ten-day close stretches to twelve or fourteen days, and the drift is rationalised at each step as a temporary pressure rather than a structural limit. When the timetable becomes a negotiation rather than a target, the function has reached a structural constraint.
How does intercompany reconciliation become a bottleneck in a growing group?
As a group adds entities and intra-group relationships, the matrix of intercompany balances grows combinatorially - not linearly. The finance team shifts from reviewing reconciliations to investigating mismatches, and that detective work crowds out higher-value analysis. The time absorbed is doing real work, but it signals that the function's capacity is being consumed by complexity rather than insight.
What does key-person dependency signal about a finance function's maturity?
Key-person dependency means a process has no structural integrity - it is a person, not a system. In a growing group, senior individuals absorb the load quietly, often working significant additional hours to keep the function moving. When those individuals leave, the gap becomes acute rather than gradual, and the function's fragility is suddenly visible.
When should a CFO treat overtime as a structural warning rather than a cyclical pressure?
Overtime becomes a structural warning when it recurs at every close regardless of one-off causes. At that point, the finance team is effectively funding the function's capacity gap from personal time. It does not appear on a cost line, but it has a limit - and when the individuals carrying it leave, the impact is immediate and material.
Why is a finance function's structural strain diagnosed late?
Each stage of strain - a longer close, slower intercompany reconciliation, delayed board answers, key-person dependency - looks manageable in isolation. The pattern across all of them, tracked over time, is the real diagnosis. By the time the strain is undeniable, the function has typically lost headroom, people, and board confidence simultaneously.