A finance team can run smoothly for years — and then, seemingly overnight, leadership stops trusting the numbers.
Finance functions rarely fail because the people in them get worse at their jobs. They fail because the business changes size or shape faster than the structure around them does.
Most people hear "scaling the finance function" and assume it means growing it. It doesn't always. Sometimes the right move is adding capacity. Sometimes it's tightening oversight without adding a single person — or even redesigning the team into a smaller, stronger structure. Either way, it's the same discipline: making sure the structure actually matches what the business needs from it right now.
These aren't Fortune 500 problems. They're common in growing privately held businesses long before anyone thinks they need a CFO.
When Growth Outpaces the Team
A company operating two sister businesses — one in Quebec City, one in Montreal — had a finance team that worked. A controller and an accountant handled the full cycle for both entities. People came and went over the years, as they do, but the team kept functioning.
Then leadership made a decision: three more offices would be added to the group's accounting — two in Ontario, one in BC. The work more than doubled. The team did not.
The BC office in particular didn't onboard cleanly — it came online late and full of mistakes, the kind of rocky start that usually signals a team already past capacity before the new work even stabilizes.
The same two-person structure that had handled two companies was now expected to handle five, across three provinces. Deadlines slipped. The errors showed up most in accounts receivable — duplicate invoices with numbers just slightly off from each other, easy to miss until they'd already been booked twice. Month-end entries grew more complex without becoming more accurate; the story the numbers told stopped holding together. The team still hit its deadlines, but only because people were quietly putting in unpaid overtime to make it happen — a cost that never showed up on any report, but was very real. And once leadership noticed the errors, something harder to fix than any individual mistake happened — they stopped trusting the reports altogether.
The math behind that struggle wasn't simple addition. Five offices didn't mean five times the work of one — it meant a jump in intercompany transactions and monthly management fees that had to be recorded correctly between entities, a lot more coordination between CEOs across Quebec City, Montreal, Toronto, Ottawa, and Vancouver, each with their own priorities and timelines, and a fast-growing set of customer-specific invoicing rules that had to be tracked and applied correctly every cycle. None of that shows up as a line item. All of it shows up as time, and eventually as errors.
The fix wasn't simply hiring more people to do what the original two had been doing. When a new controller took over, he rebuilt the structure itself: a controller, an assistant controller, and two accountants, each accountant responsible for specific regions. The last office to come online was brought properly in line with the rest of the group, and AR was rebuilt from the real invoice backups rather than the duplicated records already in the system. The assistant controller reviewed and trained before anything reached the controller for final sign-off — a second set of eyes, built into the process, on every region, every time. Coordination with the different office CEOs, previously scattered across whoever had time, was consolidated with the controller alone, so there was one clear point of contact instead of five competing conversations.
When Oversight Disappeared
A smaller company, single office, had run for years with a lean structure: a VP Finance and an assistant controller. On paper, things looked fine — the VP Finance reviewed and approved all the finance work, so nothing went out the door unchecked. But tension had been building between the CEO and the VP Finance over the numbers, and eventually the VP Finance's role ended.
To cover the gap, the company brought in a controller. Given some uncertainty about the state of the accounting, HR asked for a copy of the accounting database as a safeguard before the new controller's first day.
That safeguard turned out to matter more than anyone expected. On day one, the assistant controller — who was supposed to spend her final days showing the new controller the ropes — had deleted the database and never showed up. Working from the backup, the new controller spent about a month rebuilding the picture largely through bank reconciliation — working out what had actually happened financially from what the bank records showed, rather than trusting the entries on file. What started as a handover became a full rebuild: the entire previous year had to be redone before an audit could even begin.
Along the way, the controller also discovered that the outgoing assistant controller had failed to act on a CRA payroll garnishment notice — left unresolved, it would have made the company itself liable for the full amount, right up against the deadline.
What made this possible wasn't a single bad decision — it was a structure with too much power concentrated in one place and not enough independent control around it. The VP Finance reviewed and approved everything for years, and his bonus was tied to EBITDA — which meant the person with the most influence over how the numbers looked also had a direct financial interest in them looking good. The assistant controller stayed on for two months after his departure, which meant the underlying problems in the work had already existed before he left — they simply hadn't been found or acknowledged. A missed CRA notice, duplicate entries, a database with no real oversight of who could delete it — none of that requires bad intent to become a crisis. It only requires no one independent looking.
The numbers that came out the other side were more accurate — but by then, the damage to trust was done. The board forced the appointment of a fractional CFO to help rectify the situation and stand behind the numbers to leadership and investors going forward.
By the time the fractional CFO came on board, the controller had already done the hard part — the database was rebuilt, the previous year redone, the numbers back on solid ground. The fractional CFO's role was as much about the board as the numbers themselves: working directly with the audit team to negotiate a delayed timeline and resolve complex reconciliation mismatches. Working alongside the controller, the fractional CFO helped put everything back in place and get the company ready for a reorientation.
Where the company once had a VP Finance and an assistant controller, it now had a single controller working with a part-time fractional CFO — fewer people, but for the first time, someone independent was actually checking the work.
Trust doesn't come back just because the numbers are correct. It comes back when someone independent is visibly involved in making sure they stay that way.
The Pattern Behind Both Stories
Two companies, two different triggers. One scaled on purpose. One got blindsided by an exit nobody planned for. But underneath, the failure looked the same: the work and the risk grew, and the finance organizational structure didn't grow with it.
Neither company had a simple people problem. The first team was capable of running two companies well — it just wasn't built for five. In the second, one person controlled both the numbers and the story around them, with no one independent enough to catch it if something was wrong.
That's the part that's easy to miss. Growth and turnover feel like different problems, so they get different reactions — "let's add capacity" for one, "let's find someone new" for the other. But both are really the same question: as complexity increases, who is reviewing the work — and is anyone actually independent enough to catch it if the numbers are wrong?
Structure isn't one thing. It's roles and reporting lines, who reviews what and at what point, how responsibilities split as work grows, and whether the person entering the numbers is ever the only person checking them. Call it governance, organizational design, or just structure — the underlying discipline is the same: making sure how work actually flows through the finance function keeps pace with what the business has become.
Finance complexity rarely grows in proportion to revenue. Every new entity, every new layer of oversight, creates new relationships between people, systems, approvals, and reporting requirements — which is exactly why governance has to be designed deliberately, not left to grow on its own.
The first two stories are what happens when structure reacts to change. The best version is structure that anticipates it.
Where a Fractional CFO Fits
Looking back, neither company lacked capable people. What they lacked was someone whose full-time job was to step back and ask whether the finance function's governance still matched what the business had become — not doing the accounting, but watching the structure around it.
In a growth-triggered situation, that means catching the mismatch between scope and structure before leadership commits to the next office or market — not redesigning the team after the errors start. In a disruption-triggered one, it means an independent perspective with no stake in how the numbers used to look, focused on verifying, stabilizing, and standing behind them to a board or lenders who need to trust them again.
That's often where a fractional CFO creates the most value — not by taking work away from the finance team, but by making sure the way that work is organized still makes sense.
Signs Your Finance Department Structure Hasn't Kept Up
Some signs point to growth outpacing structure. Others point to oversight that was never really there. Worth watching for either:
- Errors are increasing, not decreasing — especially ones that used to be caught before they reached leadership.
- One person "just handles" a whole area, with no one reviewing their work and no real backup if they leave.
- Leadership is quietly double-checking the numbers themselves — a sure sign trust is already slipping, even before anyone says so out loud.
- Audit prep turns into a fire drill instead of a formality, becoming weeks of digging to explain what happened.
- The team's structure hasn't changed in years, but the business has — more entities, more revenue, more complexity, same people doing it the way they always did.
- Nobody can say who would catch a mistake. If you can't answer that quickly, the answer is probably no one.
Building the Structure Before You Need It
Both companies got their trust back — eventually. One rebuilt the structure after the errors piled up. The other rebuilt it after an exit exposed a year of unreliable numbers. Both stories end well. Neither had to happen the way it did.
The best time to add a review layer isn't after leadership stops trusting the numbers. It's before growth outpaces the team, and before any one person becomes the only one who understands how the numbers were built. That's the work of a controller or a fractional CFO who's paying attention — not waiting for a crisis to justify the structure, but building it because the business's complexity already calls for it. Knowing when to hire a controller, when to add a CFO, or when to simply reorganize the team you already have is rarely obvious from inside the business — which is exactly why it often takes someone independent to see it clearly.
Scaling the finance function was never really about adding headcount. It's about making sure that as the business grows — on purpose or not — someone independent is still checking the work. That's what lets leadership trust the numbers enough to make decisions on them, instead of second-guessing them.
Finance departments don't become unreliable overnight. They drift there when complexity grows faster than structure. The companies that avoid those crises aren't necessarily the ones with the biggest finance teams — they're the ones that recognize when it's time to redesign how the work is organized.