What your ERP does not record

Open any ERP and you can answer, in seconds, exactly what happened. This order was placed at this time, for this amount, by this customer. This invoice was approved, by this person, on this date. This journal entry moved this sum from one account to another.

Ask a different question — why was it approved, why that amount, why this customer gets terms nobody else does — and the system goes quiet. Not because the answer doesn't exist. Because it was never structured data to begin with.

The system of record was never designed to hold this

An ERP is a ledger with a user interface. Its job is to record state changes accurately, timestamp them, and let you total them up. That is a genuinely hard problem, and most systems solve it well.

Reasoning is a different kind of thing. It's contextual, conditional, and often only makes sense with history nobody thought to attach to the transaction. Why does this supplier get 60-day terms instead of the usual 30? Because two years ago they carried you through a stock shortage nobody else could cover. That fact lives in whoever remembers it, not in the terms field.

The result is a business that can produce a perfect trial balance and still can't explain half the decisions sitting behind it — see key-person risk in finance for what that looks like when the person holding the reasoning resigns.

Where the gap actually shows up

Three places this bites, none of them dramatic on their own.

A new hire asks why, and the honest answer is "ask David." If David is on leave, in a meeting, or has left the company, the process stalls or gets reinvented badly.

An auditor asks for the rationale behind an exception, and the trail shows the exception was approved, by whom, and when — not why it was reasonable at the time.

A manager reviewing a discount, a write-off or a non-standard term has no way to tell whether it was a considered judgement call or an oversight nobody caught.

None of these show up in a monthly report. They show up the day someone needs the answer and it isn't there.

Why this is easy to miss for years

A business can run this way indefinitely as long as the people who hold the reasoning stay put. Turnover is what exposes it, and turnover is not rare — it's a certainty on a long enough timeline.

The trouble is that the gap is invisible right up until the moment it matters. Every day the reasoning lives in someone's head instead of somewhere searchable is a day the business is one resignation away from having to reconstruct it from scratch, usually under time pressure, usually for something that mattered.

What actually closes it

Not a feature you install. A habit you build, in three parts.

Write the reason next to the decision, not in a separate document nobody will find. A one-line note on why a term was granted, attached to the record itself, survives long after the conversation that produced it is forgotten.

Make audit trails do the job they're capable of. A system that records who approved what, and when, doesn't explain reasoning — but it does mean nobody has to guess whether an exception was ever reviewed at all, which is most of what an auditor is actually checking for. That's the honest ceiling of what software captures here, and it's still worth having — see approval workflows people actually follow.

Treat onboarding as knowledge transfer, not access provisioning. Handing someone a login is not the same as handing them the reasoning behind the processes they're about to inherit — see onboarding a new staff member.

The question worth asking this week

Pick one exception currently running in your business — a non-standard price, a supplier term, a discount structure — and ask whoever approved it to explain why, in writing, in two sentences.

If they can answer instantly and it takes thirty seconds to write down, you've just closed one small gap for free. If they can't quite remember, or the answer only makes sense because they were in the room, you've found exactly the kind of thing this article is about — and it's worth doing before the person who can still answer it moves on.

Common questions

Why doesn't an ERP capture the reasoning behind decisions?

Because an ERP is built to record transactions and state changes accurately, not the contextual judgement behind them. Reasoning is conditional and depends on history that was never entered as structured data, so the system can tell you what was approved and when, but not why it made sense at the time.

How do you know if your business has this gap?

Pick a live exception — a special price, a non-standard supplier term, a write-off — and ask the person who approved it to explain why in writing. If the explanation only makes sense because they remember the context, and nobody else could reproduce it, that reasoning exists nowhere except in their head.

Can software fix this on its own?

Not fully. Audit trails record who did what and when, which is valuable but different from why. AI tools can investigate a data trail quickly, but the reasoning behind a human decision still has to be written down by a person for it to survive that person leaving.

What is the cheapest way to start closing the gap?

Write the reason next to the decision at the moment it's made — a one-line note attached to the record itself, not a separate document. It costs almost nothing when the context is fresh and becomes expensive to reconstruct the moment it isn't.

Related: key-person risk in finance · approval workflows people actually follow · onboarding a new staff member