Evidence versus explanation in a financial review

Financial review, whether internal or external, tends to focus heavily on evidence: is this figure supported by a document, does this transaction have an invoice behind it, does this balance reconcile to a statement. That's the right focus for confirming figures are real. It's a different exercise from confirming those figures make sense, and the two get conflated more often than they should.

Evidence answers "did this happen." Explanation answers "was this right."

A supported figure has a document trail proving the transaction occurred as recorded. That's evidence, and it's necessary — a business without it has a much bigger problem than this article addresses. But evidence that a transaction occurred says nothing about whether the underlying judgement was sound. An invoice proves a discount was applied. It doesn't prove the discount was the right call.

This distinction matters because a review focused purely on evidence can pass every check and still miss the actual question a stakeholder cares about. The figures are real. Whether they represent good decisions is a separate question the evidence trail was never built to answer.

Why reviews default to evidence over explanation

Because evidence is checkable in a way explanation isn't. A reviewer can confirm a document exists or doesn't, in a binary, low-ambiguity way. Confirming whether a judgement call was reasonable requires understanding context that usually isn't written down anywhere the reviewer can access — so review processes gravitate toward what they can actually check, which is evidence, and quietly under-cover explanation, which they usually can't.

This isn't a flaw in the reviewers. It's a structural consequence of what's actually available to review. If the explanation was never recorded, no amount of reviewer diligence can retrieve it — the gap exists upstream of the review itself.

Where this creates a false sense of assurance

A business that passes every evidence-based review can develop unwarranted confidence that its financial decision-making is sound, when what's actually been confirmed is narrower: the transactions are real and supported. Whether the decisions behind them were good ones is a question the review process never actually tested, because the material needed to test it — the explanation — was never available to test against.

This gap tends to surface at the worst possible moment: when a decision is challenged specifically on its merits, not its authenticity, and the business discovers that passing every prior review provided no protection against that particular question — see what an auditor asks for that your ERP cannot answer.

Closing the gap between the two kinds of review

Explicitly separate the two questions in your own internal reviews. Ask "is this supported" and "was this the right call" as distinct questions, rather than treating a passed evidence check as if it answers both.

Build explanation capture into the same processes that already capture evidence. If an approval workflow requires a supporting document, it can just as easily require a one-line rationale for anything outside standard policy — the two additions cost roughly the same amount of friction, and only one of them is currently standard practice in most businesses.

Recognise that evidence-only assurance has a real limit, and communicate that limit honestly rather than letting a passed review imply more confidence than it should. A review that confirms figures are supported is valuable and specific — it shouldn't be mistaken for a review that confirms the underlying decisions were sound.

Common questions

What's the difference between evidence and explanation in a financial review?

Evidence confirms a transaction actually happened and is properly documented — an invoice, a receipt, a reconciled balance. Explanation confirms the judgement behind the transaction was reasonable — why this amount, why this exception, why this decision. A review can pass entirely on evidence while never actually testing explanation.

Why do financial reviews focus more on evidence than explanation?

Because evidence is checkable in a clear, binary way — a document either exists or it doesn't — while assessing whether a judgement call was reasonable requires context that usually isn't recorded anywhere accessible. Reviews naturally concentrate on what they can actually verify, which structurally favours evidence over explanation.

Can passing every financial review still leave a business exposed?

Yes, if the reviews were evidence-based and the underlying decisions were never actually examined for soundness, only for documentation. A business can have every transaction fully supported and still be unable to defend the judgement behind a significant one, because that judgement was never captured or tested in the first place.

How can a business build explanation checks into its existing review process?

By explicitly separating "is this supported" from "was this the right call" as distinct questions in internal reviews, and by requiring a one-line rationale for exceptions or judgement calls at the same point an approval workflow already requires supporting evidence — adding roughly the same friction to capture a second, currently missing, piece of information.

Related: what an auditor asks for that your erp cannot answer · transactions are not decisions · the audit trail tells you who not why