Skip to content
All blog
Finance Operations Growth

Explaining your numbers to someone who was not there

Chong 7 min read

Most owner-run businesses are legible to exactly one person.

The owner knows why that customer gets those terms, what the recurring adjustment on the payout is, why last March looks odd, and which of the three suppliers is the one that actually delivers. None of it is written down, because none of it needed to be while the person holding it was in the room every day.

Then somebody outside asks. And what they need is not your explanation. It is figures that survive without it.

Four audiences, one requirement

Your accountant wants the underlying transactions, not your interpretation of them, because their job is to form an independent view. Every question they ask that you answer from memory is a control they cannot rely on.

A bank assessing a facility is testing whether your reported numbers are the real ones. They will sample. What they learn from a business that produces the substantiation quickly is different from what they learn from one that takes a week, and that difference is priced.

A buyer or investor in diligence is looking specifically for the gap between what the summary says and what the records support. Every unexplained item widens it. Diligence findings do not usually kill deals; they adjust price and add conditions.

A new senior hire is the audience people forget. A finance manager joining a business whose numbers only make sense with the founder's commentary cannot take work off the founder, which was the entire reason for the hire.

Four different purposes, one shared requirement: figures that stand up when the person who produced them is not there to narrate.

Where it usually falls down

Aggregates that cannot be opened. "Platform charges: RM14,200" invites the question "made up of what", and the honest answer is that the detail was discarded on import. This is the most common single failure, and it is unrecoverable after the fact.

Adjustments without reasons. A stock correction, a credit note, a write-off. The amount is recorded, the reason is not, and the person who knew has moved on.

Timing that nobody can reconstruct. Revenue recorded when the payout arrived rather than when the sale happened, so months are shifted in ways that are internally consistent and impossible to explain to somebody comparing against a different basis.

Numbers assembled outside the system. The management pack that lives in a spreadsheet, built monthly by one person from several exports, with adjustments applied along the way. It may be entirely correct, and it cannot be verified by anyone else, which for these audiences amounts to the same thing as being wrong.

What actually convinces

Not polish. Three things.

Specificity on demand. Someone points at a line and you open what it is made of, then open one of those, and reach a real document. This does more for credibility than any presentation, because it cannot be faked and it is instantly obvious whether it is there.

Consistency of basis. The same revenue definition in your management accounts, your statutory accounts and the deck you sent. Different bases are defensible; different bases nobody flagged look like something else.

Visible exceptions. Counterintuitively, showing that you have unmatched items being worked through builds more confidence than a perfectly balanced set of books. Everybody experienced knows some transactions do not match cleanly. A business that shows its exception queue is demonstrating a control. One that shows none is either exceptional or absorbing them somewhere.

The month-end that answers questions

There is a difference between a close that produces numbers and one that produces defensible numbers, and it is mostly about where reconciliation happens.

If revenue, fees and settlements are reconciled inside the system as transactions occur, then the management accounts are a view of records that are already substantiated. Anyone can drill in. The close is a review.

If the numbers are assembled at month-end from exports, the output may be identical, but nothing behind it can be interrogated by anyone except the person who built it. That is fine until that person is on leave during a diligence process.

The traceability principle underneath this is simple: reconciliation that happens inside the records leaves evidence; reconciliation that happens in a spreadsheet leaves a spreadsheet.

Getting there before you need to

Do the five-minute test. Pick a transaction from last year and follow it end to end. Whatever slows you down is what will slow down anyone external.

Write down the reasons, not just the amounts. A one-line note on an adjustment costs seconds now and is irreplaceable later.

Stop aggregating on import. Fees, cash, settlements — captured at transaction level, summarised for presentation only.

Move the management pack inside the system. If the monthly numbers are assembled in a spreadsheet from exports, that is the single biggest thing standing between you and figures somebody else can verify.

Assume the audience arrives without warning. Financing conversations, disputes and diligence all start on somebody else's timetable.

The same gap shows up earlier than a diligence request — most months, when the figures tie out and nobody in the room can quite say why they moved: the gap between a report and a reason.

Common questions

Is this only relevant if I am raising money or selling?

No. The most frequent audience is a new hire, and the second most frequent is your own accountant. Both are trying to do work that depends on your records explaining themselves. Financing and diligence are the versions with a deadline attached.

My accountant already handles all this. Is that enough?

Your accountant works from what you give them. If that is exports and explanations, then the substantiation lives with you, and the question of whether it holds up has only been deferred rather than answered.

How much detail is too much?

Detail is not the problem; unstructured detail is. Records that reference each other stay navigable however deep they go, whereas a folder of documents nobody can connect to transactions is noise regardless of how complete it is.

What if a past period genuinely cannot be explained?

Say so plainly, describe what changed, and show that current periods are different. Experienced reviewers are used to businesses that improved their record-keeping at some point. What damages credibility is discovering a gap that was presented as though it were not there.

Legible without you

The measure worth aiming at is not whether your numbers are right. It is whether somebody else can establish that they are right, without you.

That is the same property whether the person asking is a bank, a buyer, an auditor or the finance manager you hired last month to take the work off your desk. Build it for the last of those, and the others are already handled.


See what you could build

Start a free trial and describe what your business needs in plain language — SmartB Studio builds the module for you.

Start free trial
Get started

No credit card · Cancel anytime · Your data stays yours