Choosing the wrong PeopleSoft licensing metric is one of the most expensive decisions an Oracle customer can make, and one of the hardest to reverse. Named User Plus and Processor licensing carry fundamentally different cost structures, compliance obligations, and strategic implications. This independent advisory breaks down both models in detail, explains the four application licensing categories that complicate PeopleSoft further, and provides the analytical framework procurement and ITAM teams need to make the right choice.
PeopleSoft is licensed under Oracle's standard technology and application licensing framework, but with application-specific complexities that make it one of the most nuanced products in Oracle's portfolio. Before diving into the Named User vs Processor comparison, ITAM and procurement teams need to understand the structural elements that underpin all PeopleSoft licensing.
Like all Oracle products, PeopleSoft licences are perpetual. You pay a one-time licence fee to acquire the right to use the software indefinitely, plus an ongoing annual support fee (currently 22% of net licence fee) that entitles you to patches, updates, and technical support. The licence fee is a capital expense. The support fee is a recurring operational expense that compounds over time and typically becomes the dominant cost within four to five years. For a comprehensive overview of Oracle's licensing model, see our Oracle Licensing Guide.
PeopleSoft licences are granted on one of two metrics: Named User Plus (NUP) or Processor. The choice of metric is made at the time of purchase and recorded on the Oracle Ordering Document. Once established, changing metrics mid-contract requires a new commercial agreement with Oracle, which Oracle has no obligation to grant and will typically use as an opportunity to extract additional revenue. This makes the initial metric selection a decision with long-term financial consequences.
Critically, PeopleSoft licensing is not a single, flat structure. The applications are divided into four distinct user categories, each with different definitions, counting rules, and price points. Understanding these categories is essential because the wrong categorisation can result in either massive overspend or compliance exposure.
The single most valuable thing an ITAM team can do before any PeopleSoft licensing decision is to obtain and thoroughly review the actual Oracle Ordering Document(s). The Ordering Document specifies the exact products licensed, the metric (NUP or Processor), the quantities, and the applicable definitions. Oracle's online documentation, price lists, and sales presentations are informational only. The Ordering Document is the legally binding reference. We have seen organisations make six-figure licensing errors because they relied on Oracle's website rather than their contract.
Named User Plus (NUP) is the most common licensing metric for PeopleSoft and is typically the most cost-effective approach for organisations with a well-defined, controllable user population. Under NUP licensing, you purchase a licence for each individual who is authorised to access the PeopleSoft application, regardless of whether they actually use it or how frequently they log in.
The NUP definition is broader than many organisations realise. A Named User is not simply someone with a PeopleSoft login. Under Oracle's counting rules, a Named User includes any individual authorised to use the programs, whether directly (through the PeopleSoft interface) or indirectly (through another application that reads from or writes to PeopleSoft). This indirect access provision is a significant compliance risk. A Salesforce integration that updates PeopleSoft HCM records, a custom portal that queries PeopleSoft data, or a third-party reporting tool that reads PeopleSoft tables can all create Named User obligations.
NUP licences are not concurrent. You cannot purchase 100 licences and rotate them among 500 users based on who is logged in at any given time. Each individual who may access PeopleSoft requires their own licence. However, NUP licences are reassignable: if an employee leaves the organisation, their licence can be reassigned to a replacement. The reassignment must be permanent (not temporary or rotational). Good practice is to document reassignments quarterly.
Oracle imposes minimum Named User Plus requirements tied to the number of processors on which PeopleSoft runs. For Oracle Application programs (which includes PeopleSoft), the standard minimum is 10 Named Users per processor for Enterprise Edition deployments, though this varies by specific product and should always be verified against the Ordering Document. You cannot purchase fewer NUP licences than the minimum, regardless of actual user count.
NUP pricing varies significantly across PeopleSoft modules and user types. List prices range from approximately $200 per Named User for basic self-service modules to $4,000+ per Named User for core HCM and Financials modules. Discounts of 40 to 70% from list price are common for enterprise deals, particularly when negotiated as part of an Unlimited License Agreement (ULA) or large bundled transaction. Annual support at 22% of net licence fee adds a permanent recurring cost.
Processor licensing is an alternative metric that detaches the licence cost from user counts entirely. Instead, you pay based on the processing capacity of the hardware running PeopleSoft, specifically the number of processor cores, adjusted by Oracle's Core Factor Table.
Oracle's Processor licensing uses the Core Factor Table to translate physical processor cores into Oracle Processor licence units. Each processor core type is assigned a factor (e.g., Intel Xeon = 0.5, SPARC T-series = 0.25, IBM POWER = 1.0). The licence requirement is calculated as: Number of Cores x Core Factor = Required Processor Licences. For example, a server with two Intel Xeon processors, each having 16 cores, requires: 32 cores x 0.5 = 16 Processor licences. Processor licensing covers unlimited users.
Processor licensing becomes significantly more complex in virtualised environments. Oracle's standard licensing policy requires that all processors in the physical host be licensed, not just the cores allocated to the virtual machine running PeopleSoft. A PeopleSoft VM allocated 4 cores on a 64-core host may require licensing of all 64 cores, dramatically inflating the licence requirement. VMware, Hyper-V, and other hypervisors are classified as "soft partitioning" and do not limit the licence requirement. Oracle's own virtualisation technology (Oracle VM) supports "hard partitioning," which allows licensing only the cores allocated to the partition. For detailed guidance, see our article on PeopleSoft licensing in cloud and virtual environments.
Processor licence list prices for PeopleSoft modules are substantially higher than NUP prices, typically $20,000 to $100,000 per Processor depending on the module. However, the price per Processor covers unlimited users, so the effective per-user cost decreases as the user population grows. Annual support at 22% applies to Processor licences just as it does to NUP, and the absolute support cost is typically much higher for Processor-licensed deployments.
PeopleSoft's licensing complexity goes beyond the NUP/Processor choice. Under the Named User model, PeopleSoft applications use four distinct user type categories, each with different access rights, counting rules, and price points. Misclassifying users between these categories is one of the most common, and most costly, compliance issues we encounter in PeopleSoft audit defence engagements. For a full breakdown, see our dedicated PeopleSoft licensing guide.
The broadest licence type. Enterprise Users are counted as the total number of employees in the legal entities that use PeopleSoft, not the number of people who actually access the system. If your organisation has 10,000 employees and PeopleSoft HCM manages all of their HR records, you need 10,000 Enterprise User licences regardless of whether those employees ever log in. Enterprise licensing is effectively a headcount metric, making it simple to count but potentially very expensive for large organisations.
A narrower licence type covering individuals who use PeopleSoft for professional or managerial activities. Professional Users generally include HR administrators, finance staff, and managers who perform transactional work within PeopleSoft beyond basic self-service. The precise definition is contract-specific. For organisations familiar with Oracle's EBS user types, the Professional User concept is similar, though the definitions are not identical.
Individuals who access PeopleSoft solely for employee self-service activities: viewing payslips, updating personal information, submitting time cards, enrolling in benefits, or requesting leave. Self-Service Users are the least expensive licence type but carry the most restrictive access rights. A user who performs any activity beyond the defined self-service scope must be upgraded to a Professional or Enterprise User licence.
Some PeopleSoft contracts include product-specific Named User definitions that don't fit neatly into the three categories above. These may include specific module-level user definitions, restricted-access users, or users of standalone PeopleSoft components. Always refer to the Ordering Document for the exact user type definitions applicable to your deployment.
| User Type | Who Is Counted | Typical List Price (per NUP) | Best For |
|---|---|---|---|
| Enterprise | All employees in deploying entities | $95 to $200 | Large organisations where most employees are "in scope" |
| Professional | Managers + staff performing transactions | $300 to $800 | Organisations with a defined group of power users |
| Self-Service | Employees doing self-service only | $40 to $120 | Broad access for ESS functions at low per-user cost |
| Processor | N/A: capacity-based | $20K to $100K per Processor | Deployments with very large or unpredictable user counts |
User type classification is a frequent area of focus during Oracle licence audits. Oracle's LMS or GLAS audit teams will examine how users actually interact with PeopleSoft, not just how they are classified in the licensing records. A user classified as Self-Service who has been granted access to run reports, approve transactions, or perform any function beyond the self-service definition will be reclassified as a Professional or Enterprise User, with the corresponding licence fee differential applied retrospectively. Ensure your user classifications match actual system access, not just intended access.
The choice between Named User Plus and Processor licensing depends on your specific deployment characteristics. Neither is universally better. The optimal choice is determined by the intersection of user population size, infrastructure architecture, growth trajectory, and compliance management capability. For a broader comparison across all Oracle products, see our analysis of Named User Plus vs Processor licensing.
| Factor | Named User Plus | Processor |
|---|---|---|
| Cost driver | Number of individual users | Processing capacity (cores x factor) |
| User limits | Must licence every authorised user | Unlimited users |
| Compliance effort | High: continuous user tracking required | Low: hardware inventory only |
| Virtualisation impact | Minimal (users count regardless of infra) | Severe: soft partitioning inflates counts |
| Growth impact | Linear cost increase per new user | No cost impact until new hardware added |
| Indirect access risk | High: integrations create user obligations | None: all access covered |
| M&A impact | Immediate licence shortfall as headcount increases | No impact unless infrastructure changes |
| Best for | Controlled, stable user populations | Large, dynamic, or unpredictable populations |
The crossover point is the user count at which Processor licensing becomes cheaper than Named User Plus licensing for the same PeopleSoft deployment. Below the crossover, NUP is more economical. Above it, Processor wins. Calculating this point requires precise numbers for your specific situation, but the methodology is straightforward.
Total NUP Cost = Number of Users x NUP Licence Price. Total Processor Cost = Required Processor Licences x Processor Licence Price. Crossover Point = Total Processor Cost / NUP Per-User Price. For example, consider PeopleSoft HCM licensed on a two-socket Intel Xeon server with 16 cores per socket. The Processor requirement is: 32 cores x 0.5 core factor = 16 Processor licences. If the Processor list price is $47,000 per Processor, the total Processor cost is $752,000. If the Enterprise User NUP list price is $120 per user, the crossover point is $752,000 / $120 = approximately 6,267 users. Below 6,267 users, NUP is cheaper. Above 6,267, Processor licensing is cheaper.
In practice, the crossover point for PeopleSoft HCM typically falls between 3,000 and 8,000 Enterprise Users depending on the specific modules deployed, the hardware architecture, the applicable discounts, and whether the deployment is virtualised. For PeopleSoft Financials with Professional User licensing (higher per-user prices), the crossover can be as low as 500 to 1,500 users. Always model the five-year total cost of ownership (licence + support), not just the upfront licence fee. A $200,000 licence cost difference becomes a $420,000 TCO difference over five years. Use our Oracle Licensing Calculator to model scenarios specific to your deployment.
Virtualisation and cloud hosting fundamentally alter the PeopleSoft licensing equation, and almost always in favour of Named User Plus licensing. This is the single most important technical factor in the NUP vs Processor decision.
If PeopleSoft runs on VMware or similar soft-partitioned virtualisation, Processor licensing requires counting all physical cores in the host, not just the cores allocated to the PeopleSoft VM. This inflates the Processor licence requirement by a factor of 2x to 10x depending on your virtualisation density. A PeopleSoft deployment that would require 16 Processor licences on bare metal might require 64 or more on a shared VMware cluster. At $47,000 per Processor, the difference is $2.26 million in additional licence cost. Named User Plus licensing is unaffected by virtualisation architecture.
Running PeopleSoft on public cloud infrastructure introduces additional licensing considerations. On AWS, Oracle's licensing policy counts vCPUs for Processor licensing (2 vCPUs = 1 Oracle Processor for most instance types), which is more favourable than physical-host counting but still adds cost. On Azure, the same vCPU-based counting applies. On Oracle Cloud Infrastructure (OCI), Oracle provides the most favourable licensing terms, including BYOL credits. Regardless of cloud provider, NUP licensing remains insulated from infrastructure complexity. For PeopleSoft specifically, see our guide on licensing PeopleSoft on AWS.
Whether you are currently on NUP or Processor licensing, several strategies can significantly reduce your PeopleSoft licensing costs. For a comprehensive treatment, see our guide to optimising PeopleSoft licensing costs.
For NUP-licensed deployments, the most immediate optimisation is eliminating "ghost users," individuals who retain PeopleSoft access despite no longer needing it. Departed employees whose accounts were never deactivated, contractors whose engagements ended months ago, and users provisioned for a project that has since concluded all inflate your licence count. A systematic cleanup typically reduces the licensable user count by 10 to 20%. Implement a quarterly deprovisioning review and integrate PeopleSoft access management with your HR offboarding process.
Many organisations over-classify users. Professional Users whose actual activity is limited to self-service functions (viewing payslips, updating addresses) should be reclassified to the cheaper Self-Service User type. Conversely, ensure no Self-Service Users have been granted access beyond their licence entitlement. The reclassification exercise requires analysing actual usage patterns against user type definitions and typically identifies 15 to 25% of Professional Users who can be downgraded without any loss of required functionality.
For Processor-licensed deployments, reducing the physical core count directly reduces the licence requirement. Consolidating PeopleSoft onto fewer, more powerful servers, migrating from soft-partitioned virtualisation to Oracle VM (which supports hard partitioning), or moving to cloud instances with the minimum vCPU count that meets performance requirements all reduce the Processor licence base. Each core removed at a 0.5 factor saves one-half of a Processor licence, potentially $10,000 to $25,000 in licence fees plus $2,200 to $5,500 in annual support.
Review every PeopleSoft module against actual usage. Many organisations licensed modules during initial deployment that were never fully implemented or have since been replaced. While you cannot "return" perpetual licences, you can drop support on unused modules, eliminating the 22% annual support fee. Over five years, dropping support on a module with a $500,000 net licence value saves $550,000 in support fees.
If your PeopleSoft deployment is growing rapidly through organic expansion, M&A activity, or cloud migration, an Oracle Unlimited License Agreement (ULA) may provide a cost-effective path to unlimited deployment rights for a fixed period (typically three years). At ULA certification, you lock in perpetual licences for your actual deployment. However, ULAs carry their own risks and complexities; see our ULA exit strategy guide before pursuing this option.
Do not attempt a metric conversion (NUP to Processor or vice versa) without independent commercial advice. Oracle treats metric conversions as new sales opportunities and will typically price the conversion at full list price minus whatever discount they choose to offer, often a worse commercial outcome than the original deal. If a metric conversion is genuinely beneficial, it should be negotiated as part of a larger commercial event (renewal, ULA, or cloud migration deal) where you have maximum leverage. See our Oracle Advisory Services for independent negotiation support.
Many PeopleSoft customers are evaluating a path from on-premise PeopleSoft to Oracle Cloud applications (HCM Cloud, ERP Cloud, or a hybrid coexistence model). The licensing implications of this transition are significant and frequently misunderstood.
Oracle Cloud applications use a fundamentally different licensing model: cloud subscriptions based on Hosted Named Users or Hosted Employees, not perpetual NUP or Processor licences. Your existing PeopleSoft perpetual licences do not convert to Oracle Cloud subscriptions. You will pay for Oracle Cloud subscriptions in addition to (or instead of) your PeopleSoft licences. Oracle offers licence conversion programmes, Oracle Support Rewards and similar mechanisms, that allow you to apply existing on-premise licence support payments as credits toward Oracle Cloud subscriptions.
Alternatively, organisations may move PeopleSoft to cloud infrastructure (OCI, AWS, Azure) without migrating to Oracle Cloud applications. This preserves existing PeopleSoft licences but requires careful attention to how Processor licensing is counted in the cloud environment. NUP licensing travels seamlessly to any cloud. Processor licensing must be recalculated based on the cloud provider's instance sizing. For PeopleSoft specifically, see our guides on running Oracle enterprise applications on Azure and licensing PeopleSoft on AWS.
Organisations considering third-party support for PeopleSoft as part of a cloud migration or cost reduction strategy should evaluate how this affects their ongoing Oracle relationship and future licensing flexibility. Third-party support can reduce annual support costs by 50% or more, but it forecloses access to Oracle patches and updates, a trade-off that must be carefully weighed.
Not unilaterally. A metric change requires a new commercial agreement with Oracle, which Oracle has no obligation to grant. In practice, Oracle will typically accommodate metric conversions, but at a price that reflects a new sale rather than a simple administrative change. The conversion is usually priced at the full Processor list price for the modules being converted, with your existing NUP licence value applied as a partial credit. The net cost is often higher than simply purchasing additional NUP licences. Always model both options before approaching Oracle, and consider timing the conversion to coincide with a larger commercial event.
During an Oracle audit, the LMS or GLAS team will examine PeopleSoft system tables to identify every user ID with active access, analyse role and permission assignments to determine user type classification (Enterprise, Professional, Self-Service), review integration architectures for indirect access that creates additional Named User obligations, and compare the total licensable user count against your contracted entitlement. They will also examine the physical or virtual infrastructure to verify Processor counts. The audit scope covers both production and non-production environments. Inactive user accounts that have not been formally deactivated may still be counted. See our Oracle Audit Response Playbook.
Yes. Oracle's standard licensing requires that development, test, staging, and any other non-production environments running PeopleSoft be licensed, using the same metric and counting rules as production. The only exception is if your contract includes specific non-production use rights. Many organisations undercount non-production environments, creating compliance gaps that are readily identified during audits.
M&A events create immediate licensing exposure for PeopleSoft. Under NUP licensing, this means purchasing additional Named User licences for every new user. Under Enterprise User licensing, the headcount of the combined entity becomes the licensing base, potentially doubling the licence requirement overnight. Under Processor licensing, additional licences are only needed if the infrastructure changes. This is one scenario where Processor licensing provides a clear advantage: absorbing a 5,000-person acquisition has zero licensing impact on a Processor-licensed deployment. For detailed guidance, see our article on managing Oracle licences during M&A and divestitures.
Choosing the wrong metric for their deployment profile and being unable to change it cost-effectively. The second most common mistake is failing to account for indirect access, users of integrated systems who technically "touch" PeopleSoft data without ever logging into the PeopleSoft interface. The third is neglecting to decommission inactive users, resulting in inflated NUP counts that drive unnecessary licence and support costs. All three mistakes are preventable with proper licensing governance and periodic compliance reviews. See our PeopleSoft compliance best practices guide.
For any organisation with PeopleSoft annual support exceeding $200K, independent advisory support delivers measurable value, particularly at contract renewal, during audit defence, or when evaluating migration to Oracle Cloud. An independent advisor provides pricing benchmarks, identifies optimisation opportunities (user cleanup, reclassification, support reduction), and supports commercial negotiations with Oracle. The advisor must have no commercial relationship with Oracle to ensure their recommendations serve your interests. See our Oracle Advisory Services.
Expert playbooks covering Oracle audit defence, PeopleSoft licensing, database licensing, ULA certification, Java compliance, and cost optimisation. Written by former Oracle licensing specialists.
Browse White PapersContact us for a confidential introductory call to discuss your PeopleSoft licensing position, upcoming renewals, and how Redress Compliance can deliver measurable savings. Fixed-fee proposal typically provided within 48 hours.