Oracle PeopleSoft licensing is uniquely complex because it uses not one but four distinct licensing models. Named User, Employee-based, Campus FTE, and Module Entitlements are often applied simultaneously within the same organisation. Misunderstanding which metric applies to which module is the root cause of the compliance gaps Oracle discovers in 50 to 70% of PeopleSoft audits. This guide provides the complete framework: four licensing models with worked cost examples, suite-by-suite metric mapping, licence calculation methodology, non-production requirements, audit risk areas, support and cloud migration considerations, and the governance disciplines that prevent six-figure compliance gaps.
Unlike Oracle's technology products (Database, WebLogic) which use Processor or Named User Plus metrics, PeopleSoft applications use application-specific licensing models that vary by functional module. The same PeopleSoft deployment may require Named User licences for Financials staff, Employee-based licences for HCM modules, and Student FTE licences for Campus Solutions, all governed by different counting rules, different cost structures, and different compliance triggers. Understanding which model applies to which module is the foundation of PeopleSoft licence compliance. For Oracle database licensing fundamentals that underpin every PeopleSoft deployment, see Oracle Licence Metrics & Definitions.
| Licensing Model | What It Counts | Applies To | Typical Cost Range | Key Compliance Risk |
|---|---|---|---|---|
| Named User | Each individual person (or non-human device/integration) with access to the system. | Financials, Supply Chain, Project Costing, Grants, Asset Management, Treasury. | $100 to $500 per user per module. | Access drift. Users gain access to modules beyond their licence scope through role changes. |
| Employee-based | Total workforce size. All employees, and often contractors, regardless of whether they access the system. | HCM (Core HR, Payroll, Benefits, Time & Labour, Absence Management, Talent Management). | $50 to $250 per employee per module. | Headcount growth. M&A, contractor expansion, or seasonal workforce spikes exceed licensed count. |
| Campus FTE | Full-Time Equivalent student population (combining full-time and part-time enrolments). | Campus Solutions (Student Records, Enrolment, Financial Aid, Admissions, Academic Advising). | $20 to $100 per student FTE. | Enrolment fluctuations. Year-over-year changes require annual licence true-up. |
| Module Entitlement | Rights to use specific functional modules or add-on components within a suite. | All PeopleSoft suites. Modules must be explicitly licensed in the ordering document. | Varies by module. | Feature creep. Enabling unlicensed modules or add-on components without purchasing entitlements. |
PeopleSoft licensing applies to all environments: production, test, development, training, staging, and disaster recovery. Oracle does not provide free non-production licensing for PeopleSoft applications. Every environment running PeopleSoft must be covered by appropriate licences for the users and employees who access it. This is one of the most commonly overlooked compliance areas. Organisations build development and test environments assuming they are exempt, only to discover during audit that Oracle requires full licensing coverage for every running instance. The only exception is Oracle's Application Testing Suite licence, which provides limited non-production rights under specific conditions. Verify your ordering document carefully.
Named User licensing applies to PeopleSoft modules used by a defined group of staff, typically finance, procurement, supply chain, and project management personnel who log into the system directly. Each individual person with system access must have their own licence. There is no concurrent user pooling, no sharing of credentials, and no device-based alternative. Every named individual counts.
| Module | Typical User Population | Licensing Requirement | Common Compliance Issue |
|---|---|---|---|
| General Ledger | Finance team, controllers, FP&A. | 1 Named User licence per individual with access. | Budget managers granted GL read access without licence allocation. |
| Accounts Payable / Receivable | AP/AR clerks, invoice approvers. | 1 Named User licence per individual. | Managers added as approvers without being counted as licensed users. |
| Purchasing / Procurement | Buyers, requisitioners, approvers. | 1 Named User licence per individual. | Self-service requisitioners across the organisation expand user count far beyond the procurement team. |
| Inventory Management | Warehouse staff, inventory controllers. | 1 Named User licence per individual. | Barcode scanners and mobile devices used by warehouse staff may count as users. |
| Project Costing & Billing | Project accountants, billing specialists. | 1 Named User licence per individual. | Project managers granted costing access without separate licence. |
| Asset Management | Fixed asset managers, property controllers. | 1 Named User licence per individual. | IT asset tracking users added without licence allocation. |
| Treasury & Cash Management | Treasury staff, cash managers. | 1 Named User licence per individual. | Small user base but high compliance sensitivity due to financial controls. |
The most common Named User compliance gap in PeopleSoft occurs when organisations deploy self-service procurement. A purchasing module initially licensed for 30 procurement professionals is opened to 500+ employees across the business for self-service requisitions. Every employee who submits a purchase requisition, even once per year, requires a Named User licence for the procurement module. At $200 to $400 per user, this can create a $100K to $200K compliance gap overnight. The defence: model the self-service user population before deployment, or negotiate an employee-based metric for self-service procurement access.
Employee-based licensing applies to PeopleSoft Human Capital Management and related workforce modules. Unlike Named User licensing, the employee metric counts the total workforce size, every employee, and often every contractor and contingent worker, regardless of whether they ever log into the system. The logic: HCM modules store data about every employee (payroll records, benefits enrolments, absence records), so the licensing covers the entire workforce.
| HCM Module | Metric Basis | Who Is Counted | Key Compliance Consideration |
|---|---|---|---|
| Core HR (Workforce Administration) | All employees. | Every active employee in the HR database: full-time, part-time, temporary, and often contractors. | M&A activity adds acquired company employees to the count immediately. |
| Payroll | All paid employees. | Everyone receiving a paycheck through PeopleSoft, including seasonal, part-time, and contractors on payroll. | Seasonal workforce peaks (holiday temp staff, harvest workers) trigger peak-count licensing. |
| Benefits Administration | Benefits-eligible employees. | All employees eligible for benefits enrolment, whether or not they have elected benefits. | Contract language may define eligibility broadly to include all employees. |
| Time & Labour | Time entry population. | All employees who enter time, have hours tracked, or are subject to attendance management. | Expanding time tracking to previously exempt populations (salaried staff) increases the count. |
| Absence Management | All employees with leave records. | Employees whose PTO, sick leave, or other absences are managed in PeopleSoft. | Typically covers the full employee population. |
| Talent Management | Performance-managed employees. | All employees subject to performance reviews, goal setting, or succession planning. | Rolling out performance management company-wide expands the metric to full headcount. |
A 12,000-employee enterprise runs PeopleSoft HCM with Core HR, Payroll, Benefits, and Time & Labour. Licensed position: 10,000 employees (the count when the licence was purchased 5 years ago). Current position: 12,000 employees after two acquisitions. Compliance gap: 2,000 employees x 4 modules x $150/employee average = $1,200,000 in unlicensed usage. Plus 22% annual support on the required additional licences = $264,000/year ongoing. Oracle's audit team will compare the employee count in the PeopleSoft HR database against the licensed quantity. There is no ambiguity in this metric. The defence: implement annual employee count true-ups aligned to licence agreements, with M&A due diligence procedures that assess PeopleSoft licensing impact before closing.
Universities and colleges using PeopleSoft Campus Solutions face a unique licensing model based on student Full-Time Equivalent (FTE) counts rather than users or employees. This metric reflects the reality that virtually all students interact with the system (for registration, enrolment, grades, financial aid) and scales licensing costs with institutional size.
| Campus Metric | Who Is Counted | Calculation Method | Compliance Consideration |
|---|---|---|---|
| Student FTE | All enrolled students (full-time + part-time equivalents). | Total credit hours enrolled divided by full-time credit load. Example: 15,000 students at average 0.8 FTE = 12,000 FTE. | Enrolment fluctuations require annual true-up. Peak semester count may be the contractual measurement point. |
| Administrative staff | Faculty and staff with system access. | Named User count for registrars, advisors, financial aid officers. | May be covered by a campus enterprise licence or require separate Named User licences. |
| Applicants | Prospective students using admissions portal. | May count if admissions module has a separate metric or if applicants are granted system access. | High-volume application periods can spike applicant access numbers. |
| Alumni / Continuing Ed | Alumni using services or continuing education students. | Typically separate module entitlement with its own metric. | Alumni and continuing education modules often require standalone licensing. |
PeopleSoft is not a single application. It is a platform of dozens of functional modules grouped into suites. Oracle sells modules in bundles (sometimes called "packets") where purchasing a suite includes a set of core modules. However, many modules are standalone add-ons that require separate licensing, and the boundary between what is included in a bundle and what requires additional purchase is frequently misunderstood.
| Suite | Typically Bundled (Included) | Typically Standalone (Separate Licence) | Compliance Risk |
|---|---|---|---|
| Financials (FSCM) | General Ledger, Accounts Payable, Accounts Receivable, Billing. | Expenses, Treasury, Strategic Sourcing, Supplier Contract Management. | Enabling Expenses module without verifying it is included in the bundle. |
| Supply Chain (SCM) | Purchasing, Inventory, Receiving. | Advanced Planning, Manufacturing, eSupplier, Supplier Portal. | Opening Supplier Portal to vendors without licensing the portal module. |
| HCM | Core HR, Benefits, Base Compensation. | Recruiting, Learning Management, Talent Acquisition, Workforce Analytics. | Deploying Recruiting or Learning modules assuming they are part of core HCM. |
| Campus Solutions | Student Records, Enrolment, Academic Advising. | Housing, Alumni Relations, Contributor Relations, Continuing Education. | Activating Housing or Alumni modules without separate entitlement. |
| CRM | Support, Helpdesk (base). | Sales, Marketing, Field Service. | Expanding CRM beyond helpdesk into sales functionality. |
Before enabling any PeopleSoft module in any environment: (1) verify the module is explicitly listed in your Oracle ordering document, (2) confirm whether it is included in a bundle or requires separate licensing, (3) identify the applicable licensing metric (Named User, Employee, or Campus FTE), and (4) ensure the required licence quantity is purchased and allocated. Enabling a module without completing these four steps is the second most common PeopleSoft audit finding. Oracle's audit methodology compares enabled modules against the ordering document. Any module that is active but not listed creates compliance exposure.
| Step | Action | Detail |
|---|---|---|
| 1 | Inventory all deployed modules | Document every PeopleSoft module that is installed and active across all environments: production, test, development, training, DR. Include modules that may have been activated by administrators for testing or evaluation. The module inventory is the foundation of your licence position. |
| 2 | Map each module to its licensing metric | For each deployed module, identify whether it uses Named User, Employee-based, Campus FTE, or another application-specific metric. Cross-reference against Oracle's PeopleSoft price list and your ordering document. Some modules may have changed metric types across PeopleSoft versions. |
| 3 | Count Named Users per module | For user-based modules: extract the complete list of user accounts with access to each module from PeopleSoft Security. Include every active user ID: human users, service accounts, integration accounts, and batch processing accounts. Remove genuinely deactivated accounts. Every remaining account with access = one Named User licence required. |
| 4 | Count employees for HCM modules | For employee-based modules: extract the total active employee count from PeopleSoft HR. Include full-time, part-time, temporary, seasonal, and contractor records as defined by your Oracle contract. Compare against the licensed employee quantity. Account for M&A activity that may have added employees since the licence was purchased. |
| 5 | Calculate Campus FTE (if applicable) | For Campus Solutions: calculate the current student FTE using your institution's methodology (total credit hours divided by full-time credit load). Verify which semester or annual measurement point your Oracle contract specifies. Account for enrolment growth trends. |
| 6 | Verify module entitlements against ordering document | Compare the list of deployed modules against the modules explicitly listed in your Oracle ordering document. Every deployed module must appear in the ordering document with a corresponding licence quantity and metric. Flag any module that is active but not listed. This is a compliance gap. |
| 7 | Account for non-production environments | Verify that non-production environments (dev, test, staging, training) are covered by your licence entitlements. Oracle requires full licensing for all running PeopleSoft instances. If non-production access is broader than production (e.g. all developers have access), the non-production user count may exceed the production count. |
| Audit Finding | How It Occurs | Typical Cost Impact | Prevention Strategy |
|---|---|---|---|
| Unlicensed modules enabled | Add-on modules (Recruiting, Expenses, Learning) activated without verifying entitlement in ordering document. | $200K to $2M+ (module licence + support). | Implement change management requiring ordering document verification before any module activation. |
| Named User under-count | Self-service expansion, role changes, or integration accounts not counted as licensed users. | $100K to $500K (incremental user licences). | Quarterly user access reviews. Include integration accounts in licence counts. |
| Employee metric shortfall | Workforce growth through hiring, acquisitions, or contractor expansion exceeds licensed employee count. | $500K to $3M+ (incremental employee licences across multiple HCM modules). | Annual employee count true-up. M&A due diligence includes PeopleSoft licensing assessment. |
| Non-production licensing gap | Dev/test/training environments running PeopleSoft without proper licence coverage. | $200K to $1M+ (full licensing of non-prod users/employees). | Include non-production in licence inventory. Negotiate non-production terms at contract renewal. |
| Database technology stack | Oracle Database EE and database options (Partitioning, Diagnostics Pack) used by PeopleSoft without separate licensing. | $500K to $5M+ (database technology licensing is separate from PeopleSoft application licensing). | Map PeopleSoft database technology stack and licence DB EE, options, and middleware independently. See Oracle Database Licensing. |
PeopleSoft application licensing covers only the PeopleSoft application software. The Oracle technology stack that PeopleSoft runs on, including Oracle Database Enterprise Edition, WebLogic Server, Tuxedo, and any database options (Partitioning, Diagnostics Pack, Tuning Pack), must be licensed separately under Oracle's standard technology licensing rules (Processor or Named User Plus metrics). This is the most expensive audit finding in PeopleSoft environments. Organisations assume PeopleSoft licensing covers the database, when in fact the database and middleware are entirely separate licence obligations. A PeopleSoft deployment on a 16-processor database server creates $760,000 in Oracle DB EE licensing alone, before any application licences are counted. See Oracle Licence Metrics & Definitions and Oracle Partitioning Policy.
| Support Consideration | Current Position | Strategic Implication |
|---|---|---|
| Premier Support availability | Oracle continues PeopleSoft Premier Support with no published end date. PeopleTools updates continue (PeopleTools 8.61+). | No forced migration timeline. Organisations can plan PeopleSoft longevity. |
| Annual support cost | 22% of net licence fee, paid annually. Support uplift of 3 to 8% per year if not contractually capped. | Cumulative support costs often exceed the original licence investment within 5 to 6 years. See Oracle Support Costs 2026. |
| Oracle's cloud push | Oracle actively promotes migration to Oracle HCM Cloud, ERP Cloud, and Student Cloud as replacements for PeopleSoft. | Oracle may use ULA renewals, audit pressure, or support pricing to incentivise cloud migration. Evaluate independently. See Oracle Sales Tactics 2026. |
| Third-party support alternative | Providers like Rimini Street offer PeopleSoft support at 50 to 60% less than Oracle, with no forced upgrades. | Viable for organisations committed to long-term PeopleSoft with no plans to implement new Oracle features. See Third-Party Support Comparison 2026. Note: Rimini Street agreed to wind down PeopleSoft support by 2028 as part of the Oracle vs Rimini Street settlement. |
| OCI hosting incentives | Oracle offers incentives to host PeopleSoft on OCI (Oracle Cloud Infrastructure), including support credits and migration assistance. | Evaluate OCI economics independently. Incentives may lock you into OCI commitments that increase total cost. See Oracle OCI Cost Optimization. |
| Strategic Option | When It Makes Sense | Licensing Implication | Cost Impact |
|---|---|---|---|
| Maintain and optimise | PeopleSoft meets business needs. No compelling reason to migrate. Strong internal support capability. | Focus on licence compliance, support cost optimisation, and shelfware elimination. | 10 to 30% support cost reduction through optimisation. |
| Migrate to Oracle Cloud | Oracle Cloud HCM/ERP functionality meets requirements. Organisation is ready for cloud operating model. | PeopleSoft licences may be credited toward cloud subscription under negotiated terms (not guaranteed). | Typically 2 to 3x PeopleSoft annual support cost. Negotiate credits carefully. See Contract Negotiation Service. |
| Migrate to non-Oracle alternative | Reducing Oracle dependency. Workday, SAP SuccessFactors, or other platforms better fit future needs. | PeopleSoft licences become shelfware. Terminate support to eliminate annual cost. Verify contract obligations. | Eliminates Oracle support cost entirely. Reinvest in new platform. |
| Move to third-party support | Committed to PeopleSoft long-term. No need for Oracle's new features or patches. Want 50%+ cost reduction. | Retain PeopleSoft perpetual licences. Switch support provider. Oracle may audit within 12 to 24 months. | 50 to 60% annual support cost reduction. See Third-Party Support Advisory. |
| Discipline | Frequency | What to Do |
|---|---|---|
| Named User access reviews | Quarterly. | Extract user lists from PeopleSoft Security for every module. Compare active users against licensed quantities. Deactivate dormant accounts. Flag users with access to modules beyond their licensed scope. |
| Employee count true-up | Annually. | Compare current total active employee count (including all worker types per contract definition) against HCM licensed quantities. Account for organic growth, M&A, and contractor population changes. Purchase additional licences before the gap triggers audit exposure. |
| Module entitlement audit | Annually. | Compare enabled PeopleSoft modules across all environments against the ordering document. Disable any module that is active but not explicitly licensed. This is the single most preventable PeopleSoft audit finding. |
| Non-production licence verification | Annually. | Verify that development, test, staging, and training environments are covered by licence entitlements. Restrict non-production access to licensed users only. Document the non-production licence position. |
| Technology stack licence review | Annually. | Separately assess Oracle Database, WebLogic, Tuxedo, and database option licensing for PeopleSoft infrastructure. Technology licensing is independent of application licensing and is frequently the largest compliance gap. See Conducting Internal Oracle Licence Audits. |
| Integration and service account inventory | Quarterly. | Maintain a register of all non-human accounts (integration interfaces, batch processes, middleware connections) that access PeopleSoft. These accounts may count as Named Users depending on Oracle's interpretation and your contract terms. |
PeopleSoft uses four distinct licensing models simultaneously: Named User (for Financials, Supply Chain, and project-based modules, where each individual with access needs a licence), Employee-based (for HCM modules, where total workforce size determines licence count regardless of system access), Campus FTE (for Campus Solutions, where student full-time equivalent population is the metric), and Module Entitlements (where specific modules must be explicitly listed in the ordering document). The applicable model depends on the functional module, and a single PeopleSoft deployment often uses two or three models concurrently. This makes PeopleSoft uniquely complex compared to other Oracle application platforms.
No. This is the most expensive misconception in PeopleSoft licensing. PeopleSoft application licences cover only the PeopleSoft application software. The Oracle technology stack (Oracle Database Enterprise Edition, WebLogic Server, Tuxedo, and any database options like Partitioning or Diagnostics Pack) must be licensed separately under Oracle's standard technology licensing rules. This creates a separate compliance layer that often exceeds the PeopleSoft application licensing cost. A PeopleSoft deployment running on a 16-processor Oracle DB server requires $760,000 in database licensing alone, before any application licences are counted. See Oracle Database Licensing.
Yes. Oracle requires full licensing for all PeopleSoft environments, including development, test, staging, training, and disaster recovery. There is no automatic non-production exemption for PeopleSoft applications. Every user accessing a non-production environment must be covered by appropriate licences. Some Oracle contracts include specific non-production provisions (such as Oracle's Application Testing Suite licence), but these must be explicitly negotiated and documented in the ordering document. This is one of the most commonly overlooked compliance areas and a frequent audit finding.
Employee-based licensing counts the total workforce, all employees, and typically contractors and contingent workers, regardless of whether they log into PeopleSoft. The logic is that HCM modules (Core HR, Payroll, Benefits, Time & Labour) maintain records for every worker, so the licence obligation covers the entire population. If your organisation has 10,000 employees and 2,000 contractors, the licensed quantity must cover 12,000 workers (depending on contract definitions). Employee count must be trued-up annually to account for growth, M&A, and contractor population changes. Oracle's audit team compares the employee count in the PeopleSoft HR database against the licensed quantity directly.
No. Oracle continues to provide Premier Support for PeopleSoft with no published end date. PeopleTools continues to receive updates (PeopleTools 8.61+), and Oracle has stated that PeopleSoft will be supported as long as there is customer demand. However, Oracle actively promotes migration to Oracle Cloud HCM and ERP Cloud, and may use audit pressure, support pricing, or ULA renewal discussions to incentivise migration. The decision to maintain PeopleSoft or migrate should be based on your organisation's independent analysis, not Oracle's sales strategy. See Oracle Sales Tactics 2026 for how Oracle uses pricing and audit levers to drive cloud adoption.
Yes. Several strategies can reduce annual support costs by 20 to 60%. Eliminate shelfware (modules you are paying support on but not using) for immediate savings. Negotiate support uplift caps (0 to 3% annually) at contract renewal. Consider third-party support providers for 50 to 60% cost reduction if you do not require Oracle's new features or patches. Note that Rimini Street agreed to wind down PeopleSoft support by 2028 as part of the Oracle vs Rimini Street settlement, so evaluate alternative providers. If migrating away from PeopleSoft, terminate support on modules no longer in use. However, verify Oracle's repricing rules in your contract before partial termination, as Oracle may reprice remaining modules at higher rates. See Oracle Support Costs 2026.
Whether you need a PeopleSoft compliance assessment, help modelling the four licensing metrics across your environment, audit defence support, or strategic advice on PeopleSoft support optimisation and cloud migration, our Oracle licensing specialists deliver vendor-neutral expertise to reduce risk and eliminate overspend.
Oracle Advisory ServicesIndependent PeopleSoft compliance assessment, metric modelling, audit defence, and support cost optimisation. Fixed-fee engagements. No vendor conflicts.