Short answer: PeopleSoft user licensing offers three metrics — Named User Plus (every authorized individual, including self-service), Concurrent User (peak simultaneous sessions), and Application User (legacy contracts). Named User Plus is the default and the costliest because it counts the entire self-service population, which is usually 60-80% of all users.
Key Takeaways
- Named User Plus counts every individual authorized to use PeopleSoft, active or not — including self-service employees, managers, and contractors.
- Self-service users are typically 60-80% of the total named user population in an HCM deployment and are the leading driver of PeopleSoft back-license claims.
- Concurrent User licensing prices at roughly 10x the NUP unit but counts only peak simultaneous sessions, cutting cost 40-70% where population dwarfs concurrency.
- Across PeopleSoft engagements, the initial Oracle audit user claim is typically 3-5x what the customer actually owes once entitlements are applied (Oracle Licensing Experts, 2026).
- Switching from Named User to Concurrent is negotiable at renewal with concurrency evidence — and it removes user-population audit risk entirely.
What is a PeopleSoft Named User Plus?
A Named User Plus (NUP) is an individual authorized by you to use the programs installed on a server, regardless of whether that individual is actively using them at any given time. That definition — "authorized," not "active" — is Oracle's legal safety valve, and it is the single most important sentence in PeopleSoft licensing. If a user account exists, is mapped to a security role, or is provisioned through your identity system to reach PeopleSoft, that person is a Named User for licensing purposes whether they log in daily or never.
This is why PeopleSoft NUP counts surprise customers. An organization that "licensed PeopleSoft for HR" — perhaps 500 HR professionals — often discovers it must license several thousand named users once everyone with authorized access is counted. The PeopleSoft NUP metric also carries a 25 NUP per processor minimum where a processor floor applies, setting a hard cost baseline below which you cannot license. For the full pricing structure behind the metric, see the PeopleSoft Licensing Guide.
Do PeopleSoft self-service users need a license?
Short answer: Yes. Every employee authorized to use PeopleSoft self-service — viewing payslips, submitting expenses, entering time, requesting absence — counts as a Named User, even if they touch the system twice a year.
Self-service is the great PeopleSoft licensing trap. Employee Self-Service and Manager Self-Service functions put PeopleSoft in front of the entire workforce, and every one of those people is authorized to use the application. Managers approving timesheets or expenses via PeopleSoft Fluid count. Contractors and temporary staff with access count. The result is that self-service users routinely represent 60-80% of the total named user population — yet customers who first licensed PeopleSoft in the 1990s and 2000s frequently never counted them.
Oracle's LMS team knows this precisely. When an audit surfaces a self-service population that was never licensed, Oracle issues a back-license claim covering the unlicensed users plus annual support back-assessed across multiple years. Defending it requires evidence: which accounts are genuinely active, which are stale and can be deprovisioned, and whether a Concurrent User metric better fits the usage pattern. This is the moment where right-sizing pays for itself.
Our License Optimization service measures and right-sizes your authorized user population before Oracle's LMS scripts do. See the healthcare case study: $6M of audit risk eliminated.
How does Concurrent User licensing compare to Named User Plus?
Short answer: Concurrent User counts only peak simultaneous sessions, not total population. Its unit price is about 10x the NUP price, so the break-even is simple: if your peak concurrent count times ten is below your total named user count, Concurrent User is cheaper.
Concurrent User (CU) licensing is the defensive counter to self-service overcounting. Instead of paying for 10,000 authorized employees, you pay for the maximum number of simultaneous PeopleSoft sessions — perhaps 400 at payroll peak. Oracle prices CU high (roughly 10x NUP) precisely because it eliminates the overcounting problem, but for large populations with low simultaneity it still wins decisively, typically reducing cost 40-70%.
CU is the natural fit for seasonal and high-population, low-engagement scenarios: distribution centers with seasonal hiring, academic institutions with concentrated registration periods, hospitality groups with seasonal staffing. The decisive advantage beyond cost is risk: once you license to peak concurrency and hold a CU metric, Oracle cannot argue you owe thousands of named users. The audit question narrows to whether you exceed your licensed peak — a far more defensible position.
| Scenario | Authorized users | Peak concurrent | Lower-cost metric | Approx. saving |
|---|---|---|---|---|
| Large HCM + self-service | 5,000 | 300 | Concurrent User | ~70% |
| Seasonal distribution | 8,000 | 400 | Concurrent User | ~70% |
| Small professional module | 400 | 200 | Named User Plus | ~66% |
The math: multiply your peak concurrent count by 10 and compare to your total named user count. Lower number wins. For the migration of metrics at renewal and HCM-specific employee metrics, the PeopleSoft HCM Licensing & Employee Metrics guide goes deeper.
What is the Application User metric and when does it apply?
Application User is an older PeopleSoft metric that appears in legacy agreements, predating much of the current NUP framework. Where it survives, it counts authorized application users under contract-specific definitions that have often drifted through amendments and acquisitions. The risk with Application User contracts is definitional: Oracle and the customer may genuinely disagree on who counts, because the original definition was written years ago for a different deployment.
If you hold an Application User agreement, treat the exact contractual definition as the controlling text — not Oracle's current price list language. We routinely find that grandfathered Application User terms are more favorable than the modern NUP metric, and Oracle will quietly migrate you to NUP at renewal if you let it. Challenge any attempt to "modernize" your metric without a side-by-side cost comparison; the legacy term may be worth defending.
How does Oracle audit PeopleSoft user counts?
Oracle's License Management Services (LMS) audit for PeopleSoft queries the application's own security tables. The scripts read PSOPRDEFN for user definitions, examine role assignments, and cross-reference Oracle Database user audit data to build a comprehensive picture of the authorized population. They are designed to find the gap between what you licensed and who can actually reach the system — and the self-service population is exactly where that gap lives.
You are not obligated to hand Oracle unrestricted access to run those scripts however it wishes. The scope, the data shared, and the interpretation of "authorized" are all defensible ground. Before any PeopleSoft audit, freeze your user data, deprovision genuinely stale accounts under documented policy, and prepare your entitlement evidence. For the full audit playbook — what LMS measures and what you must share — see the Oracle Audit Defense Guide and our Audit Defense service.
How do you right-size PeopleSoft user licensing before renewal?
Right-sizing is the highest-impact lever you fully control. The sequence is consistent across our engagements: audit the authorized user population against actual usage; deprovision departed staff, role-changers, and migrated users under a documented access policy; model Named User Plus cost against Concurrent User cost at your true peak concurrency; and then take that evidence into the renewal to challenge Oracle's support base and, where the math favors it, change the metric.
A reduction from 5,000 to 4,000 documented named users cuts annual support by 20% immediately. A justified shift to Concurrent User can cut it far more. The discipline that makes this stick is documentation — Oracle accepts evidence-based reductions far more readily than assertions. To go further on cutting the resulting support bill, pair this with PeopleSoft Third-Party Support options and our Contract Negotiation service.
PeopleSoft User Licensing FAQ
What is a PeopleSoft Named User Plus?
A PeopleSoft Named User Plus is an individual authorized to use the program, whether or not they are actively using it at any given time. The count includes professional users, managers, contractors, and every employee with self-service access — not just people who log in regularly.
Do PeopleSoft self-service users need a license?
Yes. Any employee authorized to use PeopleSoft self-service — payslips, expenses, time entry, absence requests — counts as a Named User. Self-service users typically make up 60-80% of the total named user population and are the leading source of PeopleSoft back-license claims in an Oracle audit.
Is Concurrent User cheaper than Named User Plus for PeopleSoft?
It depends on the ratio of total users to peak simultaneous sessions. The Concurrent User unit price runs roughly 10x the NUP price, so if peak concurrent count times ten is less than your total named user count, Concurrent User is cheaper — often 40-70% cheaper for large, low-simultaneity self-service populations.
How does Oracle audit PeopleSoft user counts?
Oracle's LMS scripts query the PeopleSoft security tables — PSOPRDEFN and role assignments — and cross-reference database user data to build the authorized user population. A customer who believed it licensed 500 HR users often discovers it must license several thousand once self-service accounts are counted.
Can I switch PeopleSoft from Named User to Concurrent at renewal?
Yes, the metric is negotiable at renewal. Oracle resists it because it reduces future audit revenue, but with evidence of genuine peak concurrency the LMS team will accept the change. Once made, audit risk shifts from user population to whether you exceed your licensed concurrent peak.
Right-size your PeopleSoft user count before Oracle measures it
We identify named user overcounting, model the cheaper metric, and build the evidence to defend it — independent, buyer-side, and built on 600+ engagements.