Anna Totterdell
Projects Director
Your board pack arrives seven days after month end. It is formatted professionally. The numbers are laid out clearly. The charts trend in directions that invite discussion. The commentary is written with the confidence of someone who knows the business well.
And at least three people in the room know the numbers are not quite right.
They know because they have their own versions - pulled from different systems, at different times, using different assumptions. They know because last month's pack was corrected quietly after the meeting when someone spotted a discrepancy. They know because the person who assembled the report told them privately that she had to make a judgement call about a figure she could not reconcile.
But nobody says anything. Because the alternative - admitting that the business does not have a single, trustworthy set of numbers - is a conversation nobody wants to have.
How the fiction gets written
The process of producing a board report in most mid-market businesses is not a data exercise. It is a narrative construction exercise.
It begins with extraction - the daily tell-tale of missing data and systems integration. Someone, usually in finance, exports data from the ERP, the CRM, and whatever other systems contribute to the numbers. These exports arrive in different formats, with different definitions, covering slightly different time periods.
Then comes reconciliation. The exported data does not agree. Revenue in the CRM does not match revenue in the ERP, which does not match revenue in the finance platform. The differences are caused by timing, scope, categorisation, or simply different data entry practices. Someone spends hours - sometimes days - making the numbers align.
The alignment is not scientific. It involves judgement. Which source is more likely to be correct? Which figure should be adjusted? Where can a rounding difference be absorbed? These decisions are made by a competent person using their best assessment, but they are decisions - not calculations. The output is a version of the truth, not the truth itself.
Then comes assembly. The reconciled numbers are placed into a template. Commentary is written to explain variances. Charts are formatted. The pack is reviewed by the finance director, who may adjust a figure or rephrase a commentary before it goes out.
By the time the board sees the pack, the data has been extracted, reconciled, adjusted, formatted, and narrated. It looks authoritative. It is not. It is a constructed account based on disconnected data, subjective reconciliation, and a timeline so long that the information is already stale.
Why everyone tolerates it
The board tolerates it because the alternative - demanding real-time, fully reconciled, trustworthy data - feels like an unreasonable ask. It would require investment, change, and an admission that the current process is not fit for purpose.
The finance team tolerates it because they are doing the best they can with the systems they have. They know the report is imperfect. They also know that nobody has given them the tools or the integration to make it better.
The leadership team tolerates it because the report has always been produced this way. It is a known quantity. The imperfections are familiar. The quarterly rhythm of assembly, correction, and acceptance has become normalised.
And so the fiction continues. Not because anyone is dishonest, but because the systems and processes that produce the report are incapable of producing anything better. The fiction is structural, not intentional. But it is fiction nonetheless.
What it costs
The direct cost is the time spent assembling the report - typically two to five days of finance team capacity per month, depending on the business. That is time spent on reconciliation, not analysis. On assembly, not insight.
The indirect cost is worse. Decisions made on data that is seven days old and partially reconciled are, by definition, less reliable than decisions made on current, trustworthy data. The board discusses strategy based on numbers that may have already shifted. Investments are approved based on margins that were estimated, not measured. Risks are assessed using figures that were constructed from the best available data, not the actual data.
And there is a subtler cost: the erosion of trust. When leadership suspects the numbers are not fully reliable - even if they never say it - they stop treating the data as authoritative and start relying on instinct. The report becomes a formality. The real decisions happen in hallway conversations and one-to-one meetings, informed by experience rather than evidence.
What real reporting looks like
Real reporting is not a document produced once a month by a person in finance. It is a live, connected view of the business that updates automatically from the systems that run the operation.
Revenue is not extracted and reconciled. It is calculated from a single, consistent data source that the CRM, ERP, and finance platform all contribute to - with aligned definitions, automated flows, and real-time updates.
Variances are not discovered during the close. They are flagged as they occur through business automation - an alert when a figure deviates from expectation, a notification when a reconciliation fails. The investigation happens in the moment, not three weeks later.
The board pack is not assembled. It is generated - from the same live data that leadership accesses every day. The meeting is about what to do with the information, not whether the information is correct.
This is not aspirational. It is achievable. It requires the kind of IT and process strategy that treats connected systems, structured data, and an integration layer as foundations - so the numbers agree by design, not by manual effort.
The conversation nobody wants to have
If your board report takes more than a day to produce, the data has been manually reconciled, and anyone in the room has a different version of the numbers, your reporting is not reliable. It is a best-effort narrative constructed from disconnected sources.
That is an uncomfortable thing to say in a board meeting. But it is a far less uncomfortable thing to say than: "we made a significant investment decision based on data that turned out to be wrong because nobody caught the reconciliation error until the following month."
The fiction is comfortable. The consequences are not.
