Reconstructing a write-off decision two years later

These figures are modelled, not measured. They come from an internal planning exercise built on realistic Malaysian inputs for a business of this shape. No real customer is described here, and nothing below is a quotation from anyone. Treat this as a worked scenario for sizing an argument, not as evidence of what happened to somebody else.

A mid-sized distribution business writes off a RM180,000 trade receivable in its FY2024 accounts. The write-off itself is a single journal entry: debit bad debt expense, credit trade receivables, approved, posted, done. Two years later, a new auditor reviewing the comparative figures asks a reasonable question: what was the basis for writing this off, and why this amount rather than a partial provision?

The reconstruction, step by step

The finance manager who approved the write-off has since left the company. Nobody currently on the team was directly involved in the original decision. What follows is what it actually takes to answer the auditor's question from a standing start.

Step one: find who was involved. HR records confirm the approving manager's tenure, but nobody left has direct knowledge of this specific customer or transaction. The next best source is whoever handled collections at the time — also since departed, though a colleague vaguely recalls "some issue with that account."

Step two: search for supporting correspondence. Email retention policies mean anything older than eighteen months has been archived or purged. A partial email thread surfaces, referencing a dispute over delivered goods, but without the earlier messages that explain what the dispute was actually about.

Step three: reconstruct from indirect evidence. The customer's account history shows a series of disputed invoices and a final payment that came in well below the outstanding balance. From this, a plausible story can be built: the customer disputed part of the goods received, a partial settlement was negotiated, and the remainder was written off. Plausible — but nobody can confirm this is actually what happened, because the person who made the decision isn't there to confirm it.

Step four: present a best-effort explanation, with a caveat. The final answer given to the auditor is honest about its own uncertainty: "based on available records, this appears to relate to a disputed delivery, though the original decision-maker is no longer with the business and we cannot confirm the specific rationale with certainty."

What this costs, beyond the hours

The direct cost is measurable: several days of searching, cross-referencing and drafting an explanation that, in the end, is still a reconstruction rather than a confirmed account. The indirect cost is less visible and arguably worse — an auditor receiving a hedged, uncertain explanation for a judgement call naturally scrutinises it more closely than a documented, confident one, which can extend testing into other areas as confidence in the overall control environment is quietly recalibrated.

What would have prevented this

A single sentence, written at the time the write-off was approved, describing the basis for the decision — "customer disputed delivery quality on invoice #4471, negotiated settlement at 40% of balance, remainder written off as uncollectable following three collection attempts" — would have resolved the auditor's question in under a minute, two years later, regardless of who was still employed by the business.

This is the argument this cluster has made from several directions, applied here to its most expensive setting: the moment a judgement call meets an external party whose job is specifically to question it — see why audit season keeps taking longer than the numbers justify.

The conclusion this scenario doesn't fully support on its own

It would be neat to conclude that this single write-off's reconstruction cost more than a decision log would have cost across several years. The arithmetic doesn't quite get there on one case — the real argument is cumulative: a business that reconstructs judgement calls this way routinely, across many write-offs, provisions and exceptions over years, spends far more in aggregate than the trivial cost of writing the reason down once, at the time, every time.

Common questions

What made this write-off hard to explain two years later?

The people directly involved in the original decision had left the business, supporting emails had been purged under standard retention policies, and no note was ever attached to the write-off explaining the basis for the amount. The explanation had to be pieced together from indirect evidence rather than confirmed directly.

What would have prevented the reconstruction effort?

A single sentence recorded at the time the write-off was approved, describing the basis for the decision and the amount. This would have answered the auditor's question directly, regardless of staff turnover, and taken a fraction of the time the reconstruction eventually required.

Is the cost of poor documentation always this dramatic?

Not on any single transaction — this is a modelled illustration of the mechanism, not a claim that every write-off costs days to reconstruct. The real cost is cumulative, showing up across many judgement calls made the same way over years, where the aggregate reconstruction burden becomes substantial even if any individual case seems minor.

Does a hedged, reconstructed explanation actually matter to an auditor?

Yes — an explanation an auditor recognises as a best-effort reconstruction, rather than a confirmed account, tends to invite closer scrutiny and can extend testing into related areas, since it signals something about the overall reliability of the business's documentation practices, not just the one transaction in question.

Related: why audit season keeps taking longer than the numbers justify · key-person risk in finance · a decision log is cheaper than the mistake it prevents