Derrimon Trading Company’s 2025 net loss of $2.42 billion, against $1.22 billion the year before, has a traceable origin: a 2022 decision to move its accounting and inventory systems from Retail Express to Microsoft Dynamics Business Central.

That decision, on its own, was ordinary. Growing companies outgrow their software all the time.

What turned it into a multi-year financial crisis was what came next: a 2023 cyberattack that forced the company to go live on the new system before the migration was stable, followed by roughly two years in which management reportedly could not fully trust what the system was telling it about inventory valuation and unit costs.

The consequences arrived late but landed hard. When the numbers finally got sorted out, Derrimon wrote down more than $3 billion in inventory in 2025 alone.

Its auditors could not sign off on time, forcing a Jamaica Stock Exchange trading suspension that lasted through most of June 2026 while outside specialists, some consulted overseas, worked through what the company’s own chairman described as flying blind.

Six months into 2026, the losses were still widening, with the company reporting $486.7 million loss for the half-year, up 2 per cent from the prior year.

For other Caribbean mid-cap operators eyeing their own systems overhaul, the specifics matter less than the sequence. A software migration is not primarily a technology project. It is a controls project that happens to involve technology, and the controls failure shows up on the balance sheet, not the server room.

Three lessons sit inside the Derrimon timeline that any regional business owner planning a similar move should take seriously before signing a vendor contract.

First, a forced or rushed go-live, whatever the trigger, whether a cyberattack, a contract deadline, or a board that wants results by year-end, tends to skip the reconciliation work that catches configuration errors early. Those errors compound quietly.

A wrong unit-of-measure setting or a misconfigured costing method does not announce itself in month one; it distorts margins gradually until an inventory count or an audit forces the discrepancy into the open, by which point it may represent years of unreliable reporting.

Second, parallel running matters more than vendors like to admit. Keeping the old system and the new one operating side by side for a full reporting cycle is expensive and slows the project down, which is exactly why it gets cut when budgets tighten. It is also the single clearest way to catch the kind of data integrity problem that eventually cost Derrimon its trading status.

Third, a business’s exposure to a systems failure scales with its leverage. Derrimon was already carrying a gearing ratio the Jamaica Gleaner reported at 76 per cent when the ERP problems surfaced, and a subsequent breach of banking covenants followed without a formal waiver in place.

A company with less debt has more room to absorb a bad quarter of unreliable numbers while it sorts out the underlying system. A highly leveraged one does not get that cushion; lenders and auditors both start asking harder questions the moment the reporting looks shaky.

None of this means Caribbean mid-caps should avoid modernising their finance systems. Legacy platforms carry their own risks, and Derrimon’s original move to a more capable ERP was a reasonable strategic call.

The lesson is about sequencing and discipline: budget for a real transition period, resist go-live deadlines driven by anything other than data readiness, and treat the finance system’s reliability as a board-level risk item, not an IT ticket.

The cost of getting that wrong is not measured in downtime. It is measured, as Derrimon’s shareholders now know, in billions.