Oracle PeopleSoft Licensing Module Structure: Product Families, Base Modules & Add-ons

PeopleSoft Module Structure Overview

PeopleSoft licensing is organized into major product families, each with a required base module and optional add-on modules. The critical rule: you cannot license an add-on module without first licensing the corresponding base/foundation module. Violating this prerequisite rule is one of the most common audit findings in PeopleSoft environments.

The five PeopleSoft product families are HCM (Human Capital Management), FSCM (Financial Supply Chain Management), Campus Solutions, CRM (Customer Relationship Management), and Interaction Hub. Each family follows the same licensing pattern: identify which modules your organization actually uses, confirm you hold licenses for the base and any add-ons deployed, and measure usage against the appropriate metric (employee count, application users, students, etc.).

The Base Module Prerequisite Rule

Every add-on module requires a corresponding base license. In HCM, PeopleSoft Human Resources (HR Core) is the mandatory foundation; you cannot license Talent Management, Payroll, or Benefits without holding an HR Core license for the same population. In FSCM, Financials (typically entered via General Ledger) is the base; you cannot license Procurement or Project Costing without an underlying Financials license.

This creates a licensing trap: organizations sometimes enable a module in PeopleTools or begin using a feature without acquiring the corresponding license. If Oracle discovers that you have Payroll features enabled but no Payroll module license, the audit conclusion is that you were deploying Payroll unlicensed and owe back payments plus penalties.

Licensing Metrics Per Family

PeopleSoft licensing metrics differ by product family. HCM is licensed by employee count (all employees in the organization, regardless of whether they log into the system). FSCM and CRM are licensed by Application User (AU) — only users who actually access each module require a license. Campus Solutions is licensed per enrolled student per term. Understanding which metric applies to each module is essential because misclassifying your population can result in significant audit exposure.

HCM Module Structure and Licensing

The HCM product family is the most commonly deployed and most frequently audited. HCM licensing is straightforward in structure but complex in execution: you license one employee count across all HCM modules, but each module you use must be licensed separately, and every license depends on HR Core.

HCM Base Module: PeopleSoft Human Resources (HR Core)

HR Core is the mandatory foundation for all HCM modules. It includes core personnel administration, organizational structures, compensation management, and the HR reporting framework. You must hold an HR Core license for every employee in your organization who is represented in your HR system, regardless of whether they ever log into the system themselves.

The employee count for HCM is total employee headcount. If your organization has 10,000 employees, you must license HR Core for 10,000 users, even if only 3,000 are managers who access the system directly. This is a fundamental difference from many other enterprise applications and is a frequent source of audit disputes.

HCM Add-on Modules: Payroll

PeopleSoft Payroll is available in three regional variants: Payroll (North America), Payroll (UK), and Payroll (Global). Each variant includes regional tax rules, deduction types, and reporting requirements. You must license the payroll variant(s) for the regions where you operate. Payroll licensing is one of the highest-risk audit areas because:

• Integration with HR feeds employee data into Payroll automatically, creating the perception that Payroll is "included" in HR
• Payroll is often deployed in phases, and licenses may not be purchased for all regions simultaneously
• Outsourced payroll organizations sometimes access the Payroll module via PeopleSoft without a license, treating it as a service provider access scenario

Payroll licensing covers the same employee population as HR Core. If you license HR Core for 10,000 employees, you can deploy Payroll (North America) for all 10,000 without additional per-user charges, but you must hold the Payroll module license itself.

HCM Add-on Modules: Benefits Administration

Benefits Administration covers benefits enrollment, benefits eligibility determination, and benefits lifecycle management. Benefits is tied to the same employee population as HR Core and requires an HR Core license as a prerequisite. Benefits is commonly deployed alongside Payroll because payroll deductions are sourced from benefits elections.

HCM Add-on Modules: Talent Acquisition Manager, eRecruit

These modules support recruitment workflows, job requisitions, and candidate tracking. Talent Acquisition Manager (TAM) and eRecruit are sometimes confused; eRecruit is the legacy module name, and Talent Acquisition Manager is the current product. They are separate licenses, and organizations upgrading from eRecruit may hold both licenses temporarily or retire the eRecruit license inconsistently, creating audit risk.

Talent Acquisition is licensed differently than other HCM modules. It is typically licensed per recruiter or recruiter role rather than per employee, though some agreements specify per-employee licensing. Confirm your contract language because this is a common audit question.

HCM Add-on Modules: Performance Management

Performance Management covers goal setting, review workflows, rating scales, and performance documentation. PM is licensed on a per-employee basis but is typically deployed for a subset of employees (managers and individual contributors in rated populations). Unlike HR Core, which covers all employees, PM is licensed for the actual user population.

HCM Add-on Modules: Talent Management

Talent Management includes succession planning, retention analytics, and career development workflows. Talent Management is one of the highest-risk modules because:

• Organizations often enable Talent Management features in HR without realizing they are deploying an unlicensed module
• Talent Management is frequently bundled in modern HCM contracts but was not included in legacy agreements
• The distinction between basic HR functionality (which is in HR Core) and advanced talent analytics (which requires Talent Management) is ambiguous in Oracle's definition

This module triggered audit findings in 68% of HCM audits reviewed by Redress Compliance in 2025. If you use Talent Management functionality without an explicit module license, Oracle will claim you owe license fees plus penalties.

HCM Add-on Modules: Absence Management, Time and Labor

Absence Management covers time-off requests, accrual tracking, and absence policies. Time and Labor covers timesheet entry, approval workflows, and time allocation to projects or cost centers. Both are commonly deployed in organizations with hourly or project-based workforces.

Absence and Time and Labor are licensed for the user population that actually uses the module, not the total employee count. If your company has 10,000 employees but only 2,000 hourly workers who use Time and Labor, you license Time and Labor for 2,000 users, not 10,000.

HCM Add-on Modules: Learning Management, Workforce Planning

Learning Management provides learning content delivery, course management, and skill tracking. Workforce Planning covers headcount forecasting, capacity planning, and demand modeling. Both are specialized modules deployed by organizations focused on talent development or workforce optimization.

FSCM Module Structure and Licensing

FSCM (Financial Supply Chain Management) licensing is more complex than HCM because it spans multiple distinct module families: Financials, Supply Chain Management (SCM), and specialized modules like Grants Management. FSCM modules are licensed by Application User, meaning only users who access each module require a license.

FSCM Base Module: Financials (General Ledger)

Financials is the base module for the financial side of FSCM. General Ledger is usually the entry point, but other core financial modules include Accounts Payable, Accounts Receivable, Cash Management, Asset Management, Billing, and Contracts. Each of these is a separate license, but all depend on Financials as the foundation.

Unlike HCM, FSCM modules are licensed by Application User. You count only users who actually access each module. If you have 10,000 employees but only 500 who use General Ledger, you license GL for 500 users, not 10,000. This is a significant difference that allows organizations to right-size their FSCM spending.

FSCM Core Financial Modules

General Ledger is the foundation. Accounts Payable manages vendor invoices, payment processing, and vendor master data. Accounts Receivable handles customer invoices, collections, and customer master data. Cash Management covers bank reconciliation, liquidity forecasting, and cash position reporting. Asset Management (sometimes called Fixed Assets) tracks capitalized assets, depreciation, and asset retirements. Billing is used by service-based organizations for billing recurring charges or project-based services. Contracts manages contract lifecycle, terms, and obligations.

Each module requires a Financials base license and is licensed separately by Application User. Prerequisites are important here: if you deploy Billing without licensing Accounts Receivable, you will have an audit exposure because Billing requires AR infrastructure to function properly.

FSCM Supply Chain Modules

Supply Chain Management modules include Procurement, eProcurement, Inventory, Order Management, Manufacturing, Project Costing, and Grants Management. These are licensed separately from Financials modules and also require licensing the Financials base module.

Procurement covers purchase requisitions, purchase orders, and vendor management. eProcurement is the employee-facing buying portal and requires Procurement as a prerequisite (you cannot license eProcurement without Procurement). Inventory manages warehouse stock, material transactions, and inventory valuation. Order Management covers sales orders, order fulfillment, and shipment tracking.

Manufacturing includes bill of materials, production scheduling, and work order management. Project Costing allocates costs to projects and requires Contracts as a prerequisite (some configurations may also require Procurement). Grants Management is specialized for grants-funded organizations and manages grant compliance, spending limits, and reporting.

FSCM Prerequisite Rules and Integration Risks

FSCM module prerequisites are rigid and enforced in code. The most common prerequisite issues are:

• eProcurement requires Procurement — you cannot deploy eProcurement standalone
• Project Costing requires Contracts in many configurations — verify your specific implementation
• Billing requires Accounts Receivable — cannot deploy Billing without AR
• All SCM modules require Financials as the foundation

When FSCM modules integrate (e.g., Procurement feeding into Accounts Payable), data flows automatically. If you deploy Procurement but do not license it, Oracle's audit tools will detect that Procurement-originated purchase orders are being processed in AP. This creates an "unlicensed usage" claim even if you believed you were only using AP.

Campus Solutions Module Structure

Campus Solutions is PeopleSoft's higher education product suite. Campus licensing is organized around a base module (Campus Community) with add-ons for Student Records, Financial Aid, and other functions. Campus is licensed per enrolled student per term, a metric that resets each academic term.

Campus Base Module: Campus Community

Campus Community is the foundation and must be licensed first. It covers student master data, academic planning, and the core student system infrastructure. All other Campus modules require Campus Community as a prerequisite.

Campus Add-on Modules

Student Records covers enrollment, registration, and academic transcripts. Financial Aid manages federal student aid, grants, loans, and financial aid disbursement. Advisor Center provides advising functionality. Contributor Relations (formerly called Advancement) covers alumni relations and fundraising. Campus also integrates with HCM for administrative staff.

Campus licensing is unique because it resets per term. If you enroll 15,000 students in fall term, you license for 15,000. In spring term, if enrollment drops to 14,500, you adjust your license count. This creates an ongoing compliance obligation to track enrollment and adjust licenses accordingly.

CRM and Interaction Hub Module Structure

PeopleSoft CRM is less commonly deployed than HCM or FSCM because many organizations have adopted Salesforce for customer relationship management. However, organizations with existing CRM implementations must understand CRM licensing, which is per-Application User and includes modules like CRM Foundation, Helpdesk, Sales, Marketing, and FieldService.

CRM Modules and Licensing

CRM Foundation is the base module. Helpdesk covers support ticket management. Sales covers opportunity and deal management. Marketing covers campaigns and lead tracking. FieldService covers field service operations. All are licensed by Application User and each requires a CRM Foundation license as the base.

Interaction Hub (Enterprise Portal)

Interaction Hub, historically called Enterprise Portal, provides web-based access to PeopleSoft functions. It is required for any web-based access and is licensed based on the total user population that requires web access, which may be the sum of all PeopleSoft users across all product families.

Module Compliance Traps and Audit Risks

Oracle's PeopleSoft audits commonly identify the following compliance violations. Understanding each trap allows you to remediate before an audit begins.

Trap 1: Enabled Without Licensed

The most common audit finding occurs when a module is enabled in PeopleTools (via configuration, custom development, or user access) without an actual module license. Oracle's audit tools scan the PeopleTools application through the PIA (PeopleSoft Internet Architecture) to determine which modules have been configured. If you have configured Talent Management, Payroll, or another module but do not hold a license, Oracle claims you were using it unlicensed.

The defense to this claim is difficult: you must prove that the enabled configuration was not actually used, or that you did not knowingly deploy the module. Many organizations cannot make this proof and end up paying for back licenses.

Trap 2: Integration-Driven Unlicensed Usage

When one module feeds data into another module (e.g., Recruitment feeding into HR, or Procurement feeding into AP), data flows automatically and transparently. If you license Recruitment but not Talent Management, and Recruitment data populates Talent Management features, Oracle will argue that you are using Talent Management unlicensed.

This trap occurs across product families too: if HR data integrates with Payroll, and Payroll integrates with Financials, a missing license in any intermediate module creates an audit risk.

Trap 3: Outdated Licensing Records

PeopleSoft implementations span 10, 15, or even 20 years. During that time, modules are enabled, then disabled. Features are used, then abandoned. But licensing records may not reflect these changes. If you held a Talent Management license five years ago and discontinued the implementation three years ago but never officially surrendered the license, you may be paying for unused licenses. Conversely, if you stopped paying for a license but continued using it, you have an audit exposure.

Trap 4: Confusion Between Module Versions

Older agreements may reference modules with legacy names (e.g., eRecruit instead of Talent Acquisition Manager, Enterprise Portal instead of Interaction Hub). A license for "eRecruit" may not be interpreted as covering "Talent Acquisition Manager" even though the products are substantially the same. When Oracle audits, they check if your license SKU matches the module you are using. If the names do not match exactly, they may claim the license does not apply.

Trap 5: Missing Prerequisites at Deployment

When deploying a new module like eProcurement, organizations sometimes launch the module immediately after implementation without first acquiring the Procurement base license. From the moment the module goes live, you are technically using it unlicensed. Retroactive license purchases do not eliminate the back-payment claim for the period of unlicensed use.

Trap 6: Application User Miscounting in FSCM

FSCM modules are licensed by Application User, but "Application User" is strictly defined: a user who logs into the specific module. However, many organizations give broad access to financial modules. If you have 500 finance staff with access to General Ledger, you must license GL for 500 users, even if only 200 actively use it daily. Some organizations undercount their AU population and face significant true-up fees.

Trap 7: Third-Party or Outsourced Access

Outsourced payroll providers, recruitment firms, or service providers sometimes access PeopleSoft modules as part of their service delivery. If they access a PeopleSoft module, they may require a license. Oracle's position is that any named user accessing the system must be licensed, including external users. This can result in unexpected licensing obligations for organizations that did not realize their third-party access required licenses.

Trap 8: No Formal Module Surrender Process

When organizations decide to discontinue a module (e.g., stop using a particular talent management capability), they often simply disable the feature without formally notifying Oracle or updating their licensing. Oracle then continues billing for the module annually. Unlike some Oracle products that have formal "de-install" processes, PeopleSoft module surrender requires an explicit contract amendment and notification to Oracle.

Licensing Strategy: Right-Sizing Your Module Portfolio

The most effective compliance strategy is a complete module portfolio review: understand which modules you actually use, confirm you hold licenses for all deployed modules, and identify unused licenses for surrender.

Step 1: Audit Your Deployed Modules

Use PeopleTools administration tools to generate a list of enabled modules. The Component Registry and PIA Configuration reports will show which modules are configured. Cross-reference this against your Oracle license agreement to identify any gaps between deployed modules and licensed modules.

Step 2: Analyze User Activity Across Modules

Use Oracle's Activity Guide or third-party tools to measure actual user access to each module. For HCM, confirm your employee count against your HRMS population. For FSCM, count Application Users per module. For Campus, verify your enrollment count per term. This analysis reveals which modules are actually used and which are deployed but abandoned.

Step 3: Identify Prerequisite Compliance

Confirm that every add-on module you license has the corresponding base module licensed. For HCM, confirm that every HCM add-on has an HR Core license. For FSCM, confirm that every SCM module has a Financials base license. This audit often reveals that you are paying for add-on licenses without holding the base license, which may be legally non-compliant.

Step 4: Surrender Unused Modules

Negotiate a contract amendment with Oracle to formally surrender any unused modules. Surrendering modules reduces your annual support costs (support is 22% of license fees and increases 8% per year, so every unused module removes growing support costs). The key word here is "unused" — only surrender modules you are confident will not be deployed in the future.

Step 5: Update Licensing for New Modules

When deploying a new module, acquire the license before the module goes live. Do not operate any module unlicensed, even for a trial period. If you enable a new module in development and want to test it without incurring licensing, do so on a dedicated development system that is not counted in your production licensing.

Support Structure by Module

PeopleSoft support costs are tied to module licensing. Oracle charges 22% of net license fees annually for support on all licensed modules. Support increases 8% per year, which compounds significantly over time. If you reduce your module portfolio, you reduce your support costs proportionally.

Third-party support providers offer PeopleSoft support at approximately 50% of Oracle's rate. However, third-party support typically covers only specific modules or implementation issues, not full product support. Understanding your support options allows you to negotiate the right support model for your organization.

Oracle Licensing Agreement Types for PeopleSoft

PeopleSoft licensing is available under several Oracle agreement types. Understand which agreement type applies to your organization because each has different renewal terms and upgrade rights.

• ULA (Unlimited License Agreement): Pay a fixed annual fee for unlimited users across named modules for a multi-year term (typically 3 years). ULAs are ideal for organizations with variable user populations because there is no true-up if users increase.
• PULA (Perpetual Unlimited License Agreement): A one-time perpetual license purchase with ongoing annual support. Provides long-term cost certainty but requires accurate upfront sizing.
• OCS (Oracle Cloud Services): Cloud-hosted PeopleSoft with per-user-per-month pricing. OCS includes infrastructure and support and is ideal for organizations looking for operational simplicity.
• CSI (Customer Support Infrastructure): Perpetual license with support. This is the traditional on-premises licensing model and is suitable for organizations with stable deployments.

Conclusion: Module Compliance as Audit Prevention

PeopleSoft licensing compliance begins with understanding your module structure. Know which product families you use (HCM, FSCM, Campus, CRM, or Interaction Hub), confirm that every deployed module is licensed, verify that every add-on module has the corresponding base module licensed, measure usage against the correct metric (employee count for HCM, Application Users for FSCM, enrolled students for Campus), and formalize any module surrenders through contract amendment.

Organizations that conduct a complete module audit and formalize their licensing position through contract amendment reduce their audit exposure by 60% to 80%. The cost of proactive compliance is lower than the cost of audit remediation, penalties, and legal disputes.

Your next step is to confirm your module licensing against your current deployment. Start with a module inventory (which modules are configured in PeopleTools), cross-reference against your license agreement, and identify any gaps. From there, you can either acquire missing licenses or formally decommission deployed modules and update your licensing accordingly.