On Wednesday the Federal Reserve raised its policy rate for the first time since 2018, and the projections published alongside the decision imply a series of further increases before December. The Bank of England raised on Thursday, its third consecutive move. Gulf central banks followed within a day, as they always do. The European Central Bank had already accelerated the wind-down of its asset purchases the week before. For anyone holding an unapproved enterprise systems business case, something quietly important happened this week: the discount rate moved. Almost every ERP business case in existence was written in an era when money cost nothing, and the shape of those cases — large costs now, benefits distributed across years two, three and four — is the single most rate-sensitive cash flow profile in corporate finance. This is not an argument for cancelling projects. It is an argument that rising rates change which benefits count, which modules go first, and how you should be paying your vendor.
Three mechanisms, not one
Rate rises act on a systems investment in three separate ways, and most business cases only acknowledge the first. The discount rate rises. Benefits arriving in year three are now worth measurably less than they were in January, while the costs — licences, implementation fees, internal effort — all fall in the first twelve months. A case with a marginal internal rate of return last autumn may not clear the hurdle now, without a single assumption changing. Doing nothing starts paying. For the first time in over a decade, cash left on deposit earns a return that is not a rounding error. The do-nothing option has become a real alternative with a measurable yield, which raises the bar every project has to clear. Working capital becomes expensive. This is the mechanism that works in your favour, and it is systematically under-exploited. Every day of inventory and every day of receivables is financed, and the cost of that financing has just gone up and will go up again. Benefits that release cash are now worth more than they were, in direct proportion to the rate. So the same environment that punishes deferred productivity gains rewards immediate working-capital gains. The correct response is to rebuild the case around the second category.
The arithmetic nobody does
The calculation is embarrassingly simple and almost never appears in an ERP business case. Take your cost of borrowing. Multiply by the value of a day of inventory, or a day of receivables. That is what one day of improvement is worth, annually, forever. A distribution business carrying three months of stock and collecting in seventy days has an enormous amount of money tied up in decisions its systems currently cannot support: which items to stop buying, which customers to stop extending credit to, which purchase orders to cancel rather than receive. If better visibility removes a week of stock cover and five days of collection, the annual saving is the sum of those two figures multiplied by a financing cost that is rising. Nothing in the productivity section of the case will be as large, as verifiable, or as easy to defend to a lender. And unlike a productivity claim, working-capital release shows up in a place finance already watches: the facility utilisation report.
Four classes of benefit, ranked by how well they survive scrutiny
Cash-releasing. Working capital, duplicated software eliminated, licences consolidated, penalties and interest avoided, early-settlement discounts captured. Verifiable in the ledger. Cost-avoiding. Headcount not added as volumes grow, overtime at close, external accountants brought in to finish reconciliations, audit fees reduced by cleaner records. Credible only if a named budget line is reduced or frozen. Risk-reducing. Compliance failures, downtime, fraud losses, penalties. Real and usually the honest reason for the project, but not bankable and best presented as probability-weighted exposure rather than as a benefit line. Capability. Insight, agility, single source of truth, better decisions. These belong in the narrative. Put a number on them and you have told your reader that all your other numbers are also invented. The test worth applying: if a benefit cannot be traced to a line in next year's budget with a named owner who accepts the reduction, it is a reason for doing the project, not a benefit of it. Reasons are legitimate. They are just not cash.
| Benefit type | Evidence to examine |
|---|---|
| Working-capital release | Stock age, collections and the timing of actual cash release. |
| Recurring cost reduction | Budget or resource change that can be realised, not hours alone. |
| Revenue or visibility hypothesis | The causal mechanism, owner and evidence for the claim. |
| Delivery exposure | Spend timing, milestone scope and partial benefits if delivery stops. |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
Phasing is now a financial decision
When money was free, sequencing was a delivery-convenience question. Now it is arithmetic. Deliver the cash-releasing scope first — purchase control, inventory visibility, credit management, collections — and defer the modules whose payoff is qualitative. Pay the integrator against verified milestones rather than a calendar. Prefer a shorter contract at a higher unit price over a long commitment when rates and your own volumes are both uncertain, because optionality has a price and commitment has just become relatively more expensive. One specific recalculation is worth doing this quarter. Vendors offer discounts for multi-year prepayment, and those discounts were compelling when your alternative use of cash earned nothing. Now the comparison is against a rising cost of money: a ten per cent discount for paying three years upfront is a different proposition when your marginal borrowing cost is several points higher than it was in the autumn. Work out the break-even yourself rather than accepting the vendor's framing, and expect the answer to move against prepayment as the year goes on.
Practical Guidance for ERP ROI Assessment
- Rebuild the case around cash-releasing benefits, with working capital first and named owners attached.
- Update the discount rate to your current marginal cost of funds, and show the sensitivity to two more increases.
- Price the do-nothing option properly, including the return on the cash you would not spend.
- Sequence scope by payback speed, not by module logic or vendor convenience.
- Recompute prepayment discounts against your current cost of money before signing a multi-year term.
- Stage vendor payments against verified milestones, and keep a meaningful retention until the first clean close.
- Name the report where each benefit will become visible, and schedule reviews at six, twelve and twenty-four months.
- Separate reasons from benefits explicitly, so the compelled part of the decision is argued honestly.
The Regional Angle
Three features of regional corporate finance make rate rises bite faster here than the commentary suggests. Almost all mid-market borrowing in the Gulf is floating-rate bank facilities priced off a local interbank benchmark and reviewed annually, frequently supported by group or personal guarantees. There is very little fixed-rate term debt to insulate a balance sheet. When the central banks moved this week, the pass-through to your overdraft, trust receipts and working-capital lines was immediate rather than gradual. That has a direct consequence for systems investment, and it is not the obvious one: your ERP project is not competing against an abstract hurdle rate, it is competing for headroom in the same facility that funds inventory and receivables. A programme funded from the working-capital line reduces the stock you can carry. Anyone presenting a business case this year should show the facility impact alongside the return, because that is the number the bank and the shareholder will both ask about. Second, the hurdle rate that matters in a family group is not derived from a bond yield. It is whatever the next trading, dealership or property opportunity is expected to return, and in this region that figure is high, immediate and much easier for an owner to visualise than a systems payback. Arguing on the basis of discounted cash flows against that comparator is a losing strategy. Arguing that the project releases a specific amount of cash currently trapped in slow stock and uncollected receivables — cash that could fund the next opportunity — is the same case translated into the language the decision is actually made in. Third, the shift from perpetual licences to subscriptions has a covenant consequence that rising rates make sharper. Capitalised software sat below the line; subscription fees sit in operating costs and reduce earnings before interest, tax, depreciation and amortisation. Regional facilities are commonly governed by leverage and interest-cover covenants tested annually against exactly that measure. It is entirely possible to make an economically identical purchase, move it from capital to operating expenditure, and reduce your covenant headroom at the precise moment the interest-cover test is getting harder because rates have risen. Model the covenant effect before choosing the commercial model, and if the move is material, talk to your relationship bank before signing rather than at the next review.
The objection worth taking seriously
The strongest objection is that discounted cash flow applied to an ERP project is false precision, and that a quarter-point move in policy rates changes nothing about a decision whose real driver is that the incumbent system is unsupported, the auditor is unhappy, and the books take five weeks to close. These projects are compelled far more often than they are chosen. The business case is usually written after the decision, to satisfy a process, and adjusting its discount rate is an exercise in refining a number that was reverse-engineered in the first place. The uncertainty in the benefit estimates dwarfs any plausible change in the cost of capital. That is largely true, and worth admitting rather than arguing with. Most enterprise system replacements are necessities wearing investment clothing. But the discipline is not for the go or no-go decision. It is for the hundred discretionary decisions inside a compelled project: how much scope, which modules first, how much customisation, how many entities in wave one, how long a contract, how much to prepay. Rates change the right answer to several of those, and a project team that has never done the working-capital arithmetic will sequence by module dependency and discover in year two that the cash-releasing scope was scheduled last. And the do-nothing option cutting both ways is genuinely new: deferral now has a measurable carrying cost as well as a measurable yield, so waiting a year has become a priced choice rather than a free one. That is a more useful conversation than the one about whether the internal rate of return is nineteen or twenty-three per cent.
Common Questions
Should we delay our ERP programme because of rates?
Rarely. Re-sequence it so the cash-releasing scope lands first, shorten the commitment, and stage the payments. Delay is only correct if the benefits are genuinely all qualitative.
What discount rate should we use?
Your current marginal cost of funds, not last year's, with a sensitivity showing two further increases. If you are cash-funded, use the deposit rate you are giving up.
How do we make working-capital benefits credible?
Baseline days of inventory and days of receivables by category and customer now, before the project starts, and agree the measurement method with finance in writing. Unbaselined improvements are unprovable.
What should we expect over the next twelve months?
Expect several more increases — the Federal Reserve's own projections point to a policy rate near two per cent by year end, and regional benchmarks will track it closely. Expect vendors to push multi-year prepayment harder as their cost of capital rises too, and to become more flexible on term length if you ask. Expect finance functions to start demanding working-capital lines in every case. Expect re-phasing rather than cancellation as the dominant response, which is the right response. And expect covenant conversations with relationship banks to become routine by the autumn, particularly for groups carrying inventory bought at last year's inflated prices with this year's more expensive money.
ERP ROI Assessment — we rebuild your business case around cash that can be released, re-sequence the scope by payback speed, and show the facility and covenant impact before you sign anything.