ERP Licensing Models Explained 2026 | Per-User, Perpetual & More

For a complete overview of all ERP costs, see our complete ERP cost guide.

ERP Licensing Models Overview

ERP licensing has undergone a structural shift over the past decade. Perpetual on-premise licences — where you paid a large upfront fee and owned the software indefinitely — were the industry standard through the 2000s. Today, subscription-based models dominate the cloud ERP market, and most new ERP deployments are priced on a recurring basis.

The model you choose has significant long-term financial implications. Two ERP systems with similar per-user price points can diverge dramatically in 5-year total cost of ownership depending on whether pricing is per named user or consumption-based, whether upgrades are included, and whether you have the option to own the licence outright. The licensing model choice can affect your 5-year TCO by 30–50% compared to an alternative that carries the same annual sticker price.

For IT decision-makers, understanding the structural differences between licensing models is essential before entering vendor negotiations. A vendor will rarely volunteer that a different licensing structure would better suit your situation — that is your analysis to do.

The five primary ERP licensing models in 2026 are: per-user subscription, consumption-based, perpetual licence, open-source, and custom enterprise agreement. Each has a distinct cost structure, scalability profile, and set of trade-offs that suit different types of organisations.

The 5 ERP Licensing Models

1. Per-User Subscription

How it works: You pay a monthly or annual fee for each user who requires access to the system. Most vendors offering per-user pricing differentiate user types at different price points. A "full user" or "professional user" has unrestricted access to all licensed modules and typically costs $70–$250/user/month. A "limited user," "team member," or "read-only user" has restricted access — typically read-only reporting, approvals, or access to a single module — and costs 30–60% less than a full user. Named user licences are assigned to specific individuals; if someone leaves, the licence must be reassigned or released.

Vendors using this model: Oracle NetSuite, Microsoft Dynamics 365, Sage Intacct, SAP S/4HANA Public Cloud, SAP Business One Cloud, Epicor Kinetic (Cloud), Workday, IFS Cloud, Infor CloudSuite, Unit4, SYSPRO Cloud, FinancialForce (Certinia), Deltek, Priority ERP (Cloud)

For current per-user pricing across these vendors, see our cloud ERP per-user pricing guide.

Best suited for: Organisations with relatively stable, predictable user counts; companies that prefer OpEx over CapEx; businesses that want to eliminate infrastructure management overhead.

Watch out for: User count creep. As organisations grow and integrate more processes into the ERP, user count often increases faster than anticipated. Model your Year 3 and Year 5 user count when assessing 5-year TCO — a 30% user growth rate can materially change your cost outlook.

2. Consumption / Resource-Based

How it works: Rather than charging per named user, consumption-based pricing charges based on business transaction volume, total revenue processed, or compute resources consumed. Acumatica — the primary proponent of this model among mainstream mid-market ERP vendors — charges based on a "resource" tier that encompasses transaction volume, storage, and processing capacity. All licensed users are included within the resource tier at no additional per-user charge.

Vendors using this model: Acumatica (primary market proponent), some SAP S/4HANA RISE with SAP configurations (compute-based elements)

Best suited for: Fast-growing organisations where user count is increasing quickly; businesses with high user-to-transaction ratios (e.g., many occasional users relative to transaction volume); distribution or field service companies where broad employee access is operationally valuable.

Watch out for: Transaction volume growth. If your business processes significantly more orders, invoices, or inventory movements than when you established your resource tier, you may trigger a tier upgrade mid-contract. Model transaction growth alongside user growth when assessing Acumatica's TCO.

3. Perpetual Licence

How it works: You pay a one-time upfront fee for a permanent software licence — you own the right to use that version of the software indefinitely. The upfront fee can be substantial: $1,000–$5,000 per user for mid-market systems, and $10,000–$50,000+ per user for enterprise platforms. In addition to the licence fee, vendors charge an annual maintenance fee — typically 18–22% of the original licence cost — which covers access to software updates, patches, and vendor support. If you stop paying maintenance, you retain the right to use the software but lose access to updates and support.

Vendors using this model: SAP Business One (on-premise), Epicor Kinetic (on-premise), SYSPRO (on-premise), Global Shop Solutions, QAD (on-premise), Priority ERP (on-premise), Infor (on-premise products), Microsoft Dynamics GP (legacy)

Best suited for: Organisations with strong internal IT capabilities; companies with CapEx budget flexibility; large deployments where per-user subscription costs would accumulate significantly over a 7–10 year horizon; businesses in industries where data sovereignty or offline operation requirements limit cloud adoption.

Watch out for: Upgrade cycles. Perpetual licence holders are responsible for funding major version upgrades, which for complex implementations can approach 25–50% of the original implementation cost. Before choosing perpetual, understand the vendor's upgrade cadence and the likely cost of staying current over your planned system life.

4. Open-Source

How it works: The source code is freely available and can be downloaded, deployed, and modified without paying a software licence fee. The economic model instead captures costs through hosting, implementation services, customisation development, and optional vendor support or enterprise edition subscriptions. Most commercial open-source ERP vendors offer a "community edition" (free, self-supported) alongside a paid "enterprise edition" that adds proprietary modules, vendor support, and managed cloud hosting.

Vendors using this model: Odoo (Community Edition free; Enterprise Edition $24.90–$44.90/user/month), ERPNext / Frappe (Community free; managed cloud hosting available)

Best suited for: Tech-savvy organisations with developer capability in-house; companies with highly specific process requirements that benefit from source-level customisation; businesses with strong cost pressure and willingness to invest in implementation over licence fees; organisations in regions where Odoo or ERPNext partner ecosystems are well-established.

Watch out for: The true cost of "free." An Odoo Community implementation that requires significant customisation, a self-managed cloud server, and internal developer maintenance can cost as much or more than a mid-range SaaS ERP within 3 years. Model the full implementation and operating cost, not just the licence cost, before concluding that open-source is cheaper.

5. Custom Enterprise Agreements

How it works: For very large deployments — typically 1,000+ users or very high enterprise software spend — vendors negotiate bespoke contracts that cover all modules, all users, and often implementation services in a single bundled agreement. These deals are highly customised and typically involve significant negotiation over multi-year terms, volume discounts, price escalation caps, and rights to future products. SAP's RISE with SAP offering and Oracle's Universal Licence Agreement (ULA) are examples of enterprise-level constructs that replace standard per-user pricing.

Vendors using this model: SAP (Enterprise Licence Agreements, RISE with SAP), Oracle (Universal Licence Agreement, cloud subscriptions), Workday (enterprise subscription agreements), Infor (enterprise subscription constructs), Microsoft (Enterprise Agreement with Dynamics 365)

Best suited for: Large enterprises with complex, multi-entity deployments; organisations standardising on a single platform across multiple business units; companies with the procurement sophistication to negotiate effectively with large vendors.

Watch out for: Consumption vs. entitlement mismatch. Enterprise agreements often grant access to capabilities that the organisation never implements. Ensure the agreement is sized to what you will actually deploy — paying for SAP modules you will not implement in the contract term is a common and avoidable waste.

Licensing Model Comparison Table

Which Vendors Use Which Model?

The table below maps the 25 most widely evaluated ERP vendors to their primary and secondary licensing models, along with indicative per-user pricing ranges. Pricing reflects publicly available or market-standard rates as of 2026; actual pricing is subject to negotiation.

How to Choose the Right Licensing Model

No single licensing model is right for every organisation. Use this decision framework to identify which model aligns with your situation:

Company growth rate. If your user count is growing rapidly — 20%+ per year — a consumption-based or open-source model limits your licensing cost exposure as headcount increases. Per-user subscription costs scale directly with growth; model the user count at Year 3 and Year 5 to understand the full exposure.

User count stability. Mature organisations with a stable user base have the most to gain from perpetual licensing over a long horizon. If you expect to run the same ERP for 8–10 years with a stable 200-user base, the perpetual licence can be significantly cheaper than a decade of subscription payments.

Cash flow preference (CapEx vs OpEx). Perpetual licences are capital expenditures. Subscriptions are operating expenditures. Your CFO's preference — and your company's ability to depreciate a large software asset — matters. Most growing companies prefer OpEx predictability; capital-constrained organisations often prefer to spread costs over time. This is an accounting and treasury decision as much as a technology one.

Internal IT capability. Perpetual on-premise licences and open-source deployments require internal IT teams with the capability to manage infrastructure, apply patches, and plan upgrade cycles. If your IT function is lean or outsourced, cloud SaaS subscriptions that shift infrastructure management to the vendor are almost always preferable — the management burden on cloud providers is a significant hidden value that offsets some of the subscription cost premium.

Contract length comfort. Enterprise agreements lock you into 3–5 year commitments with significant exit penalties. Per-user subscriptions are typically annual contracts with more flexibility. Open-source has the highest flexibility — no vendor lock-in on the licence itself, though switching ERP platforms remains an expensive and disruptive undertaking regardless of licensing model.

For a comprehensive view of how licensing model choice flows into total 5-year cost, see our ERP TCO calculator guide.

How to Negotiate ERP Licensing

ERP licensing costs are rarely fixed. The list price is a starting point for negotiation, not a final offer. Six tactics that consistently deliver results:

1. Negotiate multi-year pricing before signing. Vendors will almost always offer a meaningful discount — typically 10–20% — in exchange for a 2–3 year commitment made at the outset. Never sign a 1-year contract at list price if you intend to keep the system long-term. Lock in the multi-year rate before go-live.

2. Cap annual price increases contractually. Most standard SaaS ERP contracts include provisions allowing the vendor to increase pricing at renewal by a percentage linked to CPI or by a fixed rate (commonly 5–8%). Negotiate a hard cap — 3–5% maximum — and get it written into the contract, not just referenced in a side letter. This single clause can save $50K–$200K over a 5-year term.

3. Negotiate your user type mix aggressively. Limited users, team members, and read-only licences typically cost 30–60% less than full users. Before finalising your user count, map every user to the minimum access level they genuinely require. A finance department with 5 people entering transactions and 10 people reading reports does not need 15 full licences — it needs 5 full and 10 limited.

4. Ask about concurrent user vs named user licensing. Not all vendors offer concurrent (floating) licensing, but those that do allow a pool of licences to be shared across a larger user population — ideal for organisations where users access the system at different times across time zones. If your workforce is distributed, concurrent licensing can reduce licence count requirements by 20–40%.

5. Bundle implementation with licensing for leverage. If the vendor's implementation arm is competing for your services work, use the combined value of the software deal and the services engagement as leverage. Vendors are more willing to discount software to protect a large services win. Even if you ultimately use a third-party implementer, let the vendor know you are evaluating their implementation team — it changes the commercial dynamic.

6. Get competitive quotes from at least three vendors. Nothing accelerates vendor flexibility like a credible competing offer. Run a structured selection process with at least three vendors through final commercial proposal stage before accepting any pricing. Vendors know when they are in a real competitive process versus a rubber-stamp evaluation, and they price accordingly.

Frequently Asked Questions

What is the most common ERP licensing model?

Per-user subscription is the most common ERP licensing model for new implementations in 2026. The shift from perpetual on-premise licensing to SaaS subscription has accelerated significantly since 2018, driven by cloud adoption, vendor preference for recurring revenue, and buyer preference for OpEx predictability. Most major ERP vendors — including NetSuite, Dynamics 365, SAP S/4HANA Public Cloud, Sage Intacct, and Workday — are either exclusively or primarily subscription-based. Perpetual licensing remains available for on-premise deployments from vendors including SAP Business One, Epicor, SYSPRO, and Global Shop Solutions, but the vendor community is gradually shifting these customers toward subscription as well.

Is perpetual or subscription ERP licensing cheaper?

Perpetual licensing is typically cheaper over a 7–10 year horizon for organisations with stable user counts and strong internal IT capabilities. The crossover point — where total perpetual costs (upfront licence + annual maintenance + infrastructure) exceed total subscription costs — typically falls between Year 5 and Year 7 for mid-market deployments. Under Year 5, subscription is almost always cheaper due to the much lower upfront capital requirement. Beyond Year 7, perpetual has a structural cost advantage because annual maintenance fees (18–22% of a fully amortised licence) are significantly lower than recurring subscription rates. The comparison changes materially when a major version upgrade is required under perpetual — upgrade costs can reset the break-even point.

Can I switch ERP licensing models later?

Switching between licensing models for the same product is sometimes possible but rarely straightforward. Transitioning from a perpetual SAP Business One on-premise licence to SAP Business One Cloud, for example, involves a commercial renegotiation and a system migration — it is not a simple administrative change. Switching ERP platforms entirely to access a different licensing model is possible but should be treated as a full ERP replacement project with commensurate cost and disruption. The practical reality is that ERP licensing model selection is a long-term decision. Model your requirements over a 5–10 year horizon before committing.

What is a named user vs concurrent user license?

A named user licence is assigned to a specific individual — that person's access is tied to the licence, and if they are on leave or no longer with the company, the licence cannot simultaneously be used by someone else. A concurrent (or floating) user licence grants access to any user up to the licensed limit at any one time — if you have 20 concurrent licences and 50 named users, up to 20 can be logged in simultaneously. Concurrent licensing is more cost-efficient for organisations where users access the system in distinct time windows (e.g., a global team across time zones, or a warehouse operation with shift-based staffing). Not all ERP vendors offer concurrent licensing — it is more common in on-premise and legacy platforms.

How do ERP licensing costs change at renewal?

At contract renewal, most SaaS ERP vendors apply the contractual price increase provision — typically 3–8% annually, or a CPI-linked adjustment. In practice, vendors also use renewal as an opportunity to restructure pricing: introducing new user type categories, moving functionality previously included in the base to premium tiers, or requiring additional module purchases to maintain existing workflows. Organisations that are deeply embedded in a platform have limited leverage at renewal because switching costs are high. The most effective way to manage renewal cost risk is to negotiate price increase caps and renewal terms at the initial contract signature — not at renewal, when your negotiating position is weakest.

---

For vendor-specific pricing benchmarks and a full comparison of ERP system costs, return to our complete ERP cost guide.