There is a useful way to think about an ERP system that most businesses never try. Ask not what the software cost to buy. Ask whether, right now, it is an asset or a liability. The answer can change without the software changing at all, because the classification depends on what the system does for you relative to what it costs you.
An asset is something that produces more value than it consumes. A liability is something that consumes more value than it produces. Your ERP crossed that line at some point. The question is whether you noticed, and what you did in the months between the warning signs and the event that finally made it obvious.
In this guide
The five triggers
In 13 years of advisory work I have seen the asset to liability flip arrive through five doors, almost always in this order of frequency:
- Vendor support ends. The product reaches end of life, and the renewal letter arrives with either no option or a premium price. The system is now on life support, and every future problem is yours to own.
- A failed audit or compliance review. The auditor asks for evidence of control that the system cannot provide. The finding sits on the risk register and the insurance renewal asks about it.
- A major outage. The old server fails, the restore takes four days instead of four hours, and the business loses orders it can never recover. Availability was always the risk. Now it has a date attached.
- The key person leaves. The only person who understood the configuration hands in notice. The business suddenly owns a system it cannot operate, and the replacement costs a premium to unpick.
- A security breach. The unpatched vulnerability is exploited. The system that processed every order is now the reason the business is on a regulator's radar. There is no faster way to flip the classification.
Notice what all five have in common. None of them is caused by the software doing something new. Each is caused by the business's relationship with the software changing: the vendor walked away, the auditor looked closer, the clock ran out, the person left, the attacker found the door.
The warnings that arrive first
The five triggers do not fire without notice. Each one sends warnings for months beforehand, and the warnings are the same shape every time:
- Maintenance climbs. The support invoice goes up faster than inflation, or the vendor starts steering every conversation toward a migration.
- Support gets slower. Tickets take longer, answers get vaguer, and the fixes arrive as workarounds rather than patches.
- Workarounds multiply. The spreadsheet layer grows, and the phrase "that is just how it works here" appears in meetings.
- Documentation goes stale. The config notes stop matching the live system, and nobody is updating them because nobody fully remembers what changed.
- The key user count shrinks. From three people to two to one, and the one is already planning their exit.
Each warning is a decision point. The mistake is to treat them as noise. A single warning is easy to ignore; two or three together are the system telling you the classification is about to change.
A service business called me in a panic. Their ERP had failed during the year end, and the finance director had spent ten days reconstructing figures from backups and spreadsheets. As we worked backwards through the timeline, the warnings were all there: support tickets unanswered for weeks, a maintenance bill up 22 percent, a superuser who had left the year before with no handover. The board had approved a replacement business case twice and let it lapse both times because the system kept working. It stopped working, eventually, on the worst possible week. The recovery project cost roughly twice what the earlier business case had budgeted.
Cost versus value: doing the sums honestly
The classification of asset or liability is a simple sum, and the accountancy profession does it all the time. The Institute of Chartered Accountants in England and Wales teaches its members that an asset's value is its future economic benefit, not its past purchase price. Your ERP's value is the future benefit it will deliver: the orders it can process, the reports it can produce, the growth it can absorb.
Do that sum honestly and the answer is often uncomfortable. The old system's future benefit is capped by what it can no longer do: no new integrations, no new currencies, no new reporting. Meanwhile the costs keep rising and the risk of a triggering event compounds each quarter. The Office for National Statistics business data shows how much of UK growth comes from firms that keep investing through change. Staying on a capped system is the one investment decision that guarantees no return.
If you want the full financial picture before making the call, the real cost of running software you have outgrown walks through the TCO model line by line.
After the flip: recovery is possible, and more expensive
Here is the good news: a liability can become an asset again. Businesses do it every year, by replacing the system, and the new platform typically delivers more value than the old one ever did. Here is the honest part: the recovery is always more expensive than acting on the warnings would have been, because you are now buying time, expertise and goodwill under pressure.
Three rules if you are already on the wrong side of the line:
- Buy the bridge, deliberately. If extended support exists, take it for a fixed term with a written end date. It is insurance, not a strategy.
- Protect the knowledge. Whatever it costs to retain the person who understands the system, it costs less than losing them. Document everything they know before they leave.
- Start the replacement now. The longer the system stays in liability territory, the more triggers can fire while you are still planning. The timing question is answered properly in how long your business can afford to wait on a system change.
Frequently asked questions
When does an ERP system become a liability?
An ERP becomes a liability when its running cost and risk exceed the value it delivers. The usual triggers are end of vendor support, a failed audit, a major outage, the departure of the only person who understands it, or a security breach.
What are the warning signs before an ERP turns into a liability?
The warnings arrive months before the event: maintenance fees climbing, support tickets going unanswered, workarounds multiplying, documentation going stale, and the key user count shrinking to one. Each warning is a chance to act before the trigger fires.
How should a business treat ERP risk on its books?
Treat it as a risk register item, not just a fixed asset. Score likelihood and impact across security, availability, knowledge and compliance, and review the scores each quarter. The register is what auditors and the board will ask to see.
Can a business recover after its ERP has become a liability?
Yes, but the recovery is more expensive than acting on the warnings would have been. The options are the same: extend support as a bridge, fix the specific failure, or replace the system. The difference is that the decision is now being made under pressure.
The honest summary: your ERP will flip from asset to liability at some point, whether you watch for it or not. The only question is whether you act on the warnings, or discover the change the way every business I have ever advised would rather not.
