The books are in order. The reports are on time. There is even a financial model.
Then the leadership team sits down to decide whether to keep funding a business unit – or the business itself. And nobody can say what that unit earns, or whether the business is making money at its core.
Not because anyone in the finance team did anything wrong. Revenue is recognised on one logic in the accounts and another in the model. Inventory hasn't been touched since year-end. Costs are recorded accurately, just not in a structure that tells one unit from another.
So the meeting ends the way these meetings often end. Someone takes it away to look into. A spreadsheet gets rebuilt by hand. The decision waits two weeks.
The numbers exist, yet the leadership team still can't act on them.
It is optimised for the tax authority – a compliant, accurate record that satisfies statutory reporting. And here is the uncomfortable part: you are already paying for it, and it is already the source of truth everything else is built on. It is simply not structured for the questions leadership has to answer.
When reporting isn't structured for decisions, the people accountable can't fully rely on it. Not because the numbers are wrong, but because they aren't assembled in a way that makes a decision clear.
So everyone builds their own version. Finance produces one. The business unit produces another. The board asks for a third. Several layers of the organisation spend their time spinning numbers that already exist – and a clear picture still doesn't emerge.
The waste doesn't only show up in the cost of the finance function. The more expensive part is time.
A decision that waits two weeks is a decision made two weeks late. In a funding round or a negotiation, that delay can cost the deal.
Unclear numbers rarely stop a decision. They change what it rests on.
Purchases are approved because they seem reasonable, headcount added because growth is expected. Each choice is defensible on its own, made with whatever was visible locally.
The result is local optimisation – dozens of sensible decisions with no shared direction between them. And two years later, they are sitting on the balance sheet.
At this point, the usual answer is a system. A new ERP. A BI layer. AI-driven reporting.
Any of them can be right. But the conversation moves to which tool is best before anyone has asked what problem is being solved.
So it is worth stepping back: what is the finance function for?
The answer isn't reporting. The finance function exists to enable decisions – and decisions dictate how limited resources get directed. Cash. People. Time. Increasingly, AI agents too.
Which changes the design question. It is not what should we measure. It is what decisions does this company have to make, and what would it take to answer them in the room.
Built properly, this is unspectacular. One revenue recognition logic, used in both the accounts and the model. A chart of accounts that can show a business unit on its own. A monthly close with a rhythm used for management, not only compliance. A gap between the accounting system and the forecast model small enough that one export crosses it. A balance sheet reviewed monthly, because that is where earlier decisions accumulate long before they reach cash.
None of this requires new software. It requires the structure to be designed rather than inherited – and the tools that come afterwards are then worth what they cost.
The moments when this is needed most are the moments when there is no time to build it. A funding round. A change of ownership. A board that has to decide rather than discuss.
When the moment comes, you don't want to be assembling the picture. You want to be reading it – and deciding.
If you are working with a company that is scaling, raising, or integrating an acquisition, there is one question worth asking: When a real decision is on the table, do the numbers answer it – or does someone have to go and rebuild them first?