Every ERP project lands, sooner or later, one question on the CFO’s desk: is this a cost or an investment? The answer determines not only how the project appears in your financial statements, but also your relationship with lenders, your financing capacity, and your taxable income over the next five years. CapEx or OpEx — the decision is made before the contract is signed.
This article structures the thinking every CFO needs to work through before choosing between on-premise and SaaS ERP. It is not a substitute for your tax advisor or external auditor, but it gives you the right questions to ask and the right figures to model.
CapEx vs OpEx: Accounting and Tax Fundamentals
Before running the simulations, let’s establish the accounting foundation. The distinction is not a matter of jargon: it determines how the expenditure appears in your financial statements and how it affects your ratios.
What IAS 38 Says About Capitalising Software
Under IAS 38 (Intangible Assets), acquired or internally developed software can be recognised as an intangible asset on the balance sheet, provided it meets three cumulative criteria: the entity controls the asset, future economic benefits are identifiable, and the cost can be measured reliably.
In practice: if you purchase a perpetual ERP licence, or commission bespoke development, you can capitalise the cost as an intangible asset and amortise it over its expected useful life. The same principle applies under US GAAP (ASC 350-40), where the internal-use software guidance permits capitalisation of development-phase costs once technological feasibility is established.
What you cannot capitalise: a SaaS subscription. A subscription does not transfer control of the underlying asset to the customer. It is a service consumed period by period, recognised as an operating expense. There are no exceptions to this rule, regardless of contract value or duration.
IFRS 16 and SaaS Contracts: What Changed in 2019
The adoption of IFRS 16 in January 2019 introduced an important nuance. The standard requires recognition of a right-of-use asset for any lease contract that conveys the right to control an identified asset.
The question arises with certain multi-year SaaS contracts: if the contract grants exclusive access to a dedicated infrastructure (identified physical servers, strictly isolated data), some auditors may reclassify it as a lease subject to IFRS 16. The company then recognises a right-of-use asset and a corresponding lease liability on the balance sheet — increasing leverage ratios without delivering the tax benefits of capitalised investment.
In practice, the vast majority of SaaS ERP subscriptions (Sage Intacct, Microsoft Dynamics 365, SAP Business Cloud, Unit4, Oracle NetSuite) run on shared infrastructure, which rules out reclassification. But if you sign a dedicated hosting contract with a vendor, have your external auditor validate the accounting treatment before signing.
On-Premise ERP: A CapEx Investment to Amortise
Components of On-Premise CapEx
The initial investment in an on-premise ERP breaks down into several line items, all capitalisable:
- Perpetual licences: the primary cost, calculated per named or concurrent user. For a mid-market company with 150 employees and 80 users, the typical range runs from £50,000 to £150,000 (or equivalent in your currency) depending on the vendor and functional scope.
- Hardware infrastructure: physical or virtual servers, storage, networking. A standard on-premise deployment requires an initial hardware investment of £12,000 to £40,000, depending on redundancy and high-availability requirements.
- Integration and configuration services: the most variable item, typically 60–120% of licence cost depending on process complexity and number of interfaces.
All these items can be capitalised, subject to component-level granularity. Your auditor will advise on what to expense immediately (travel costs, initial training, ancillary fees).
Amortisation Rules: Duration and Method
The amortisation period for an ERP is left to the company’s judgement within the bounds of economic reality and industry practice. In practice, the market converges on 5 to 7 years using the straight-line method.
- Straight-line method: equal amortisation charge over the chosen period. A £300,000 intangible amortised over 5 years generates an annual depreciation charge of £60,000, consistent through to the end of year 5.
- Declining balance method: rarely applied to software. It is primarily used for qualifying tangible assets. For intangible assets, straight-line is the standard accounting and tax method under IFRS.
Key tax point: if you have developed custom modules with an integrator, distinguish in the contract between “development work” (capitalisable) and “configuration and consulting services” (expensable). This distinction can account for 30–50% of the integration budget and has an immediate tax impact.
Balance Sheet and Ratio Impact
Capitalising an ERP as an intangible asset improves certain ratios while weakening others. The CFO needs this complete picture:
- EBITDA preserved: depreciation charges do not affect EBITDA. For companies valued on an EBITDA multiple (M&A transaction planned, private equity discussion underway), this is a concrete advantage.
- Heavier total assets: the intangible increases the asset base, which can dilute return on assets (ROA) if net income does not keep pace.
- Net debt / EBITDA: if the ERP is debt-financed, leverage increases. Lenders typically enforce a net debt / EBITDA covenant of 3–4x. An ERP investment of £400,000 funded by debt can push this ratio over the threshold if EBITDA is tight.
Have this conversation with your bank before launching the project, not during a credit renewal negotiation.
SaaS ERP: An OpEx Charge to Manage
What the SaaS Subscription Actually Covers
A SaaS ERP subscription typically includes: software access, cloud hosting, automatic updates (major and minor releases), and a baseline support tier defined in the SLA.
What it does not systematically include, depending on the contract:
- Additional functional modules (production management, integrated WMS, advanced CRM)
- Connectors to third-party systems (CRM, e-commerce, EDI, government invoicing portals)
- Initial training and ongoing capability-building
- Custom development and bespoke configuration
- Storage beyond a base quota
- Support sessions beyond hours included in the base contract
Before signing a SaaS contract, require a complete breakdown of what is included and price out the additional modules you will need in the first 24 months. The listed price is usually the floor, not the real cost of operation.
SaaS Cost Variability Over Time
The main risk of SaaS OpEx is not the initial price: it is cost drift over time. SaaS ERP subscriptions are indexed on several levers:
- User growth: every new hire increases the invoice. A company growing from 80 to 150 users over three years sees its subscription grow proportionally, unless the contract includes negotiated pricing tiers.
- Annual price reviews: SaaS contracts typically include indexation clauses. Increases of 5–10% per year are common in the sector; some specialised contracts allow up to 15%.
- Consumption-based pricing: some cloud offerings bill per transaction, API call, or archived data volume. This model can be attractive at launch and very expensive at steady state.
P&L Impact: Operating Expense and Tax Treatment
SaaS subscriptions are recognised as operating expenses, reducing pre-tax profit and generating an immediate tax benefit at the applicable corporate tax rate (the standard rate in most OECD countries is 19–25%).
This immediate deductibility is a real advantage for cash-constrained businesses. It contrasts with on-premise ERP, where the tax deduction is spread over the amortisation period (5–7 years).
The flip side: the SaaS subscription flows directly above EBITDA, since it is recognised before depreciation and financial charges. For a company valued on an EBITDA multiple, choosing SaaS can mechanically reduce valuation at identical operating performance.
5-Year Simulation: Which Option Is Actually Cheaper?
Illustrative Example: Industrial Mid-Market Company, 150 Employees
The table below is built on realistic, transparent assumptions. It reflects no specific vendor or project.
Assumptions:
- Industrial mid-market company, 150 employees, 80 ERP users
- On-premise: perpetual licence £100,000 + infrastructure £25,000 + integration £100,000 = initial CapEx £225,000, annual maintenance £17,000, recurring infrastructure cost £12,000/year
- SaaS: starting subscription £1,300/month (£15,600/year), 7% annual price review, additional modules charged at £400/month from year 2
| Year | On-Premise ERP (annual cost) | SaaS ERP (annual cost) |
|---|---|---|
| Year 1 | £254,000 (CapEx + maintenance + infra) | £15,600 |
| Year 2 | £29,000 | £27,100 (revised subscription + modules) |
| Year 3 | £29,000 | £29,000 |
| Year 4 | £29,000 | £31,000 |
| Year 5 | £29,000 | £33,200 |
| 5-year total | £370,000 | £135,900 |
Over five years, SaaS appears considerably cheaper in cumulative cash outflows. But this reading is incomplete.
The Variables That Shift the Decision
Analysis horizon. Extend the simulation to 7 years and factor in the cost of on-premise infrastructure refresh (server replacement approximately £15,000 mid-life), plus continued SaaS price indexation. At a 7% annual increase, the gap narrows significantly by year 7.
Headcount growth. If the company grows from 80 to 150 SaaS users in 5 years, the SaaS invoice grows proportionally, while the on-premise cost remains nearly constant (the licence is already paid).
Discount rate. A rigorous CFO discounts future cash flows at the cost of capital. An 8% discount rate advantages SaaS (payments spread over time), even if the nominal total is comparable over 7 years.
Exit clauses. A SaaS contract with a 3-year commitment and a 30% early termination penalty represents a financial risk to quantify. Build this exit cost into your risk analysis, especially if your company is in a transformation or acquisition phase.
Practical advice: before comparing, require “all-in” pricing for 5 years from each vendor. Licences or subscription, infrastructure, integration, maintenance, additional modules, training costs, and exit costs. A spreadsheet that ignores variable costs in year 3 is a sales pitch, not a financial analysis.
Decision Criteria Beyond Price: Governance, Flexibility, Risk
Data Control and Sovereignty
Your ERP manages your most sensitive data: chart of accounts, product margins, payroll data, customer contracts. With an on-premise ERP, you have physical control over where that data resides.
With SaaS hosted outside your jurisdiction, GDPR (for EU-based entities) and applicable data transfer frameworks govern data handling. Most major vendors maintain regional data centres — but verify actual data location and sub-processing conditions before signing. For companies in defence, regulated industries, or handling sensitive data, public cloud SaaS may create compliance constraints that are difficult to work around.
Vendor Dependency and Lock-In
With a perpetual on-premise licence, you can theoretically continue using the software indefinitely, even if the vendor discontinues support. This is not ideal, but it gives you time to migrate.
With SaaS, if the vendor disappears, raises prices unsustainably, or changes terms unilaterally, your only option is migration. The cost of data portability (extraction, cleansing, re-integration) can reach £25,000 to £100,000 depending on scope complexity. Systematically negotiate a data escrow clause and a contractual right to extract data in an open format in your SaaS contracts.
Scalability and Peak Load Management
If your company is growing fast, anticipating an acquisition, or exploring a capital raise, SaaS offers structural flexibility that on-premise cannot match: add users without a deployment project, elastic compute capacity for month-end close and peak periods, the ability to activate modules for international subsidiaries on demand.
For a company with stable, predictable long-term activity, this flexibility argument carries less weight.
Hybrid Strategies and Negotiation Levers with Vendors
The binary CapEx/OpEx opposition is often superseded by the market. Several hybrid configurations are worth exploring.
Finance lease on infrastructure. Some companies purchase perpetual licences while financing the hardware infrastructure on a finance lease. Infrastructure becomes OpEx; the licence remains CapEx. This spreads initial cash outflows while retaining software ownership.
Government and public financing. Many jurisdictions offer SME digitisation support: national development bank programmes (Bpifrance in France, British Business Bank in the UK, KfW in Germany), regional co-financing schemes, and R&D tax credits for bespoke development. These programmes typically apply to investment projects, which tends to favour on-premise options or implementation costs for SaaS (configuration, integrations, training).
Contractual negotiation. Regardless of the model chosen, systematically negotiate these points before signing:
- An annual price increase cap (3% or 5%), indexed on an agreed reference (CPI, COLA, or a published technology index), written into the contract
- An audit right for consumption-based contracts (transactions, API calls, storage)
- A data portability clause with the export format defined contractually (CSV, XML, normalised JSON)
- An uptime SLA of at least 99.5% with effective financial penalties (not just a credit on the next invoice)
Your strongest negotiating position exists before you sign, not at renewal three years later when your data is in the system and your team is trained. Keep vendors competing through to the last line of the contract.
To go deeper on the full TCO calculation methodology, read our 5-year ERP TCO comparison: SAP, Odoo, Dynamics and Sage and our guide to ERP pricing models in 2026. If you are considering moving an existing on-premise ERP to SaaS, our on-premise to SaaS migration guide covers the 5 pitfalls to avoid and the conditions for a real ROI.
