A system of record was built to store and report data that has already been validated. When it’s held to the standard of a system of execution, the gap shows up as spreadsheets, messages and manual double-checking. The failure is rarely the product’s.
What’s the difference between a system of record and a system of execution?
A system of record holds what has already been decided and confirmed. A system of execution would decide in real time, with the exception of the moment — and that’s what the operation does on the outside, manually, because the ERP was never designed for that part.
Why does the gap only appear months after go-live?
Because the pilot tests the expected path, not the exception. The exception only appears when the operation’s real volume forces it into being — and by then the project has already been declared complete.
Whose responsibility is it when that gap appears?
Not the ERP vendor’s, nor the implementer’s: neither promised to cover unanticipated exceptions. It belongs to whoever decides what to do with the knowledge the operation already produced to handle it — and today has nowhere to record that.
Does switching systems solve it?
It doesn’t close the gap — it reappears in the new system, under a different spreadsheet name. What closes it is structuring the knowledge that already exists about the exception, before deciding which system will host it.
No ERP will advertise this, because admitting the gap doesn’t sell licences. Whoever structures the exception has no such conflict — it’s the whole business.