The choice of pricing model has become just as strategic as the choice of ERP itself. A 30 to 50% difference in total cost of ownership over five years can hinge not on the features selected, but on how you pay for them. In 2026, four models coexist on the market, each with its own financial logic, hidden advantages and contractual pitfalls.
According to the 2025 Panorama Consulting Group report, nearly 78% of new ERP implementations now opt for a cloud solution. But “cloud” does not mean “SaaS per user”. Behind this umbrella term, several pricing models coexist — and the CFO who signs without distinguishing between them risks discovering the real bill three years later.
The 4 ERP Pricing Models Coexisting in 2026
SaaS per User / Month: The Dominant Model
This is the most widespread model in the mid-market and SMB ERP space. The company pays a monthly or annual subscription per named user, covering hosting, updates and basic support.
Public pricing examples:
- Microsoft Dynamics 365 Business Central: $80/user/month (Essentials) to $110/user/month (Premium), with Team Member licences at $8/month (microsoft.com)
- Odoo Standard: approximately $31/user/month billed annually, with access to all applications (odoo.com)
- Sage Intacct: quote-based pricing, with market estimates placing the cost between $400 and $800/user/year for a basic accounting module (erpresearch.com)
Advantages: predictable monthly budget, no heavy upfront investment, fast deployment (3 to 6 months), scalability both up and down.
Limitations: cost grows linearly with the number of users. Over 7 to 10 years, cumulative subscription costs far exceed the amortised cost of a perpetual licence. And annual price escalation clauses can turn a competitive contract into a financial trap.
Perpetual Licence + Annual Maintenance Contract: The Legacy Model
The company purchases a permanent licence, then pays an annual maintenance contract (typically 18 to 22% of the licence price) to receive updates and support.
This model remains common among traditional vendors serving the mid-to-large enterprise segment: SAP (for residual on-premise deployments), Sage (X3 and 200 product lines), Epicor, and Infor. It was the dominant model before the SaaS wave and still represents a significant share of installed ERP estates worldwide.
Advantages: the licence is a depreciable asset on the balance sheet (intangible fixed asset). After year 5, the annual cost is limited to maintenance. For a company with stable headcount, this is often the cheapest model over 7 years or more.
Limitations: high upfront investment (often £50,000 to £200,000 for 50 users, excluding integration). The company bears responsibility for infrastructure (servers, security, backups) if the ERP is deployed on-premise. Major version upgrades require a full project in their own right, sometimes as costly as a reimplementation.
Consumption-Based / Pay-per-Use Pricing: The Cloud-Native Model
The company pays based on actual consumption: number of transactions processed, storage volume, API calls, compute power used. This model is offered by some cloud-native platforms, notably Oracle Cloud Infrastructure (OCI) for infrastructure layers, and certain SAP BTP (Business Technology Platform) modules.
Advantages: perfect alignment between cost and actual usage. Ideal for businesses with seasonal activity (retail, food & beverage, hospitality) where transaction volumes vary sharply month to month. No overpayment for inactive users.
Limitations: the invoice is unpredictable if consumption is not monitored continuously. An unanticipated activity spike (promotional campaign, intense quarterly close) can double the monthly bill. This model requires FinOps discipline that few SMBs and mid-market companies have mastered today.
Hybrid Model and BYOL (Bring Your Own Licence)
BYOL allows a company holding perpetual on-premise licences to reuse them when migrating to the same vendor’s cloud environment, without purchasing new licences. SAP and Oracle have historically offered this mechanism to accelerate migration of their installed base to the cloud.
Advantages: reduced cloud migration cost by leveraging past investment. A less financially disruptive transition period.
Limitations: this model is fading out. SAP has progressively restricted BYOL terms since 2024, and Oracle is pushing customers towards native cloud commitments (Universal Credits). BYOL is only relevant as a transitional lever, not as a long-term strategy.
Comparative Table: Costs, Risks and Flexibility Over 5 Years
Costed Simulation for 50 Users Over 5 Years
| Cost item | SaaS ($80/user/month) | Perpetual licence | Pay-per-use |
|---|---|---|---|
| Licences / subscription | $240,000 | $100,000 (upfront) | Variable |
| Annual maintenance | Included | $20,000/year = $100,000 | Included |
| Infrastructure | Included | $40,000 (servers + renewal) | Included |
| Integration / deployment | $60,000 | $90,000 | $70,000 |
| System administration | $25,000 ($5,000/year) | $100,000 ($20,000/year) | $15,000 |
| Estimated 5-year total | ~$325,000 | ~$430,000 | ~$250,000–$400,000 |
Costed Simulation for 200 Users Over 5 Years
| Cost item | SaaS ($80/user/month) | Perpetual licence | Pay-per-use |
|---|---|---|---|
| Licences / subscription | $960,000 | $300,000 (upfront) | Variable |
| Annual maintenance | Included | $60,000/year = $300,000 | Included |
| Infrastructure | Included | $80,000 | Included |
| Integration / deployment | $150,000 | $200,000 | $180,000 |
| System administration | $50,000 | $200,000 ($40,000/year) | $30,000 |
| Estimated 5-year total | ~$1,160,000 | ~$1,080,000 | ~$600,000–$1,200,000 |
Crossover point: for 50 users, SaaS remains competitive over 5 years thanks to the absence of infrastructure costs. For 200 users, the perpetual licence becomes advantageous from year 4 onwards, as the SaaS subscription continues growing while the licence is fully amortised. Pay-per-use is the highest-risk model without FinOps monitoring, but potentially the cheapest for organisations that control their consumption.
Note: these simulations use an $80/user/month SaaS rate, representing a mid-market benchmark. Premium ERPs (SAP S/4HANA Cloud, Oracle Fusion) frequently exceed $150/user/month at list price, which accelerates the crossover point in favour of perpetual licensing.
The Real Cost of SaaS: What the Subscription Doesn’t Say
The advertised per-user/month price does not always cover everything needed for production use:
- Additional storage: most contracts include a base quota (5 to 20 GB per user). Beyond that, each additional GB is charged separately, sometimes at high rates.
- API calls: integrations with your CRM, BI tool or e-commerce platform generate API calls. Some vendors charge beyond an included threshold.
- Named vs concurrent users: a named-user contract bills each person with an account, even if they only connect once a month. A concurrent-user model (simultaneous connections) is often 30 to 40% cheaper, but few SaaS vendors still offer it.
- Add-on modules: the base price rarely covers project management, advanced BI or multi-entity consolidation. Each addition increases the bill.
- Test environments: a sandbox environment is sometimes charged separately, even though it is essential for testing version upgrades.
Which Model for Which Organisation Profile?
Fast-Growing SMB (under 100 users): SaaS Wins
For an SMB growing from 30 to 80 users over three years, SaaS offers the necessary flexibility: add licences on demand, no infrastructure provisioning, automatic updates. The long-term premium is offset by the absence of technical risk and speed of deployment.
Recommendation: negotiate a 3-year contract with a locked rate and a progressive volume clause (tiered discounts as user count grows).
Stable Mid-Market Company with an In-House IT Team: Perpetual or Hybrid
A 200 to 500-user organisation with a structured IT team benefits more from a perpetual licence. The upfront investment is amortised over 5 to 7 years, and the company retains control over its upgrade cadence. The hybrid model (perpetual licence + IaaS cloud hosting) combines control with infrastructure outsourcing.
Recommendation: insist on a reversibility clause and a data export commitment in a standard format (CSV, XML, REST API) in your maintenance contract.
Multi-Entity Group with Variable Usage: Consumption-Based
A group with 15 subsidiaries, some of which only use the ERP for the monthly close, overpays on named users. The pay-per-use model, combined with a consumption monitoring tool, aligns cost with the actual usage of each entity.
Recommendation: set up a FinOps dashboard from day one of deployment. Without consumption visibility, this model becomes a financial risk.
Regulated Industries (Data Sovereignty): On-Premise or Private Cloud
Sectors subject to strict data sovereignty requirements (defence, healthcare, public sector) often have no choice: data must remain on a certified private cloud or internal servers. The model then becomes a perpetual licence with dedicated hosting, or a SaaS deployment on a sovereign/compliant cloud from vendors offering dedicated government or regulated-industry environments.
Recommendation: integrate the premium cost of sovereign cloud (30 to 50% above standard public cloud) into your business case from the selection phase.
Contractual Pitfalls to Watch Out For
Annual Price Escalation Clauses
According to data from Vertice, SaaS software price inflation reached 13.2% in early 2026 — nearly five times general inflation. Some ERP contracts include an escalation clause indexed to a benchmark (CPI, RPI or a vendor-specific index) or, worse, a discretionary clause allowing the vendor to raise prices freely at each renewal.
What to negotiate: a contractual escalation cap (3 to 5% maximum per year) or a guaranteed fixed price for the duration of the commitment.
Data Lock-In at Exit (Exit Fees)
The end of an ERP contract is rarely free. Some vendors charge for data extraction, limit available export formats, or impose a 30-day transition period — far too short for a clean migration.
What to negotiate: a detailed reversibility clause covering the export format (SQL dump, REST API, structured flat files), a minimum 6-month transition period, and the absence of exit fees. To explore this topic further, see our complete guide on ERP vendor lock-in.
Named vs Concurrent Users: The Invoice Impact
The distinction between named and concurrent users can represent a 30 to 40% difference on your licence bill. A named user pays for access whether they connect or not. A concurrent user shares a connection pool: only the maximum number of simultaneous connections is billed.
Concrete example: a 200-employee organisation where 120 users access the ERP only occasionally (viewing product records, submitting occasional expense reports) will pay for 200 licences under a named model, but only 60 to 80 licences under a concurrent model. At $80/month per licence, the gap represents $57,600 to $115,200 per year.
Negotiation Checklist: 7 Questions to Ask Before Signing
Before signing an ERP contract, ask your vendor or integrator these seven questions. Any evasive answer is a warning sign.
-
What is the all-in per-user price? Request a detailed quote breaking down the base price, included modules, storage, API calls and test environments. Refuse “starting from” figures.
-
What is the exact escalation clause? Get in writing the annual increase mechanism: reference index, cap, and frequency. If the clause is discretionary, negotiate a cap or change vendor.
-
What is the exit cost? Have the cost of data extraction, guaranteed export format and transition period at contract end formally quoted.
-
Named or concurrent users? If your user population is mixed (power users + occasional users), ask for a split with light or read-only licences at reduced rates.
-
What is charged separately? Explicitly list: sandbox environments, integrations, additional storage, premium support, training, major version upgrades.
-
Is the contract terminable annually? A 3-year commitment with annual termination after year 1 is acceptable. A firm 5-year commitment with no early exit is not.
-
What is the pricing policy if headcount reduces? If you go from 200 to 150 users, can you reduce your licence count at the next renewal, or are you locked into a minimum?
These questions are not formalities. They determine whether your ERP will be a profitable investment or an uncontrollable cost centre. To structure your evaluation, download our ERP evaluation grid covering 30 criteria across 100 points to objectively compare three vendors.
For a complete view of hosting considerations tied to these pricing choices, see also our cloud vs on-premise comparison and our multi-tenant vs single-tenant guide.
