PeopleSoft AWE Approval Patterns | J.H. Randolph & Co.

Architecture reference only. AWE configuration varies by PeopleTools version and implementation. Test all patterns in a non-production environment. Validate against your organization's security architecture before production deployment.

Official sources

Use payroll approval workflows alongside official payroll recordkeeping and employment tax requirements.

🏗️

Overview

AWE and Payroll Approval — Why It Matters for Compliance

›

The PeopleSoft Approval Workflow Engine (AWE) is the delivered framework for routing HR and payroll transactions through approval chains before they take effect. For payroll, AWE governs critical authorization controls that directly affect compliance — compensation changes, direct deposit updates, tax data modifications, and off-cycle payment requests.

A poorly configured AWE implementation is a segregation-of-duties failure. IRS examiners and internal auditors look specifically at whether compensation-affecting transactions could be self-approved, and whether the approval chain produces an immutable audit trail. These patterns address both concerns.

What AWE Controls in Payroll Context

Transaction type	AWE applicable?	Compliance risk if uncontrolled
Compensation / pay rate change	Yes — Job Data AWE	Unauthorized pay increases; self-approval; SOX/audit failure
Direct deposit change	Yes — custom or delivered AWE	Payroll fraud; misdirected funds
W-4 / tax data change	Optional — employee self-service	Usually employee-initiated; IRS lock-in violation if improperly overridden
Off-cycle check request	Yes — custom AWE recommended	Unauthorized disbursements; control failure
Additional pay setup	Yes — additional compensation AWE	Standing pay arrangements without authorization
Termination processing	Yes — Job Data AWE	Premature or unauthorized terminations; final pay timing

⚙️

Architecture

AWE Core Components in PeopleSoft HCM 9.2

›

Key AWE Objects

AWE Object	Purpose	Navigation path
Event Registry	Registers business events (transactions) that can trigger AWE workflows	Enterprise Components > Approvals > Approvals Setup > Event Registry
Process Definition	Defines the approval process for a specific event — stage names, paths, and criteria	Enterprise Components > Approvals > Approvals Setup > Process Definition
Approval Authorization	Maps roles and users to approval authority for each process definition	Enterprise Components > Approvals > Approvals Setup > Approval Authorization
Criteria Definition	Business rule conditions that route transactions to different approval paths	Enterprise Components > Approvals > Approvals Setup > Criteria Definition
Worklist	The queue of pending approvals for each approver	Enterprise Components > Approvals > Pending Approvals
Transaction Monitor	Tracks status and history of all AWE transactions — the audit trail viewer	Enterprise Components > Approvals > Transaction Monitor

AWE Transaction Lifecycle

Initiator submits transaction (e.g., Job Data change) — AWE event is triggered
AWE evaluates criteria definitions to determine routing path
Approval request routed to approver's worklist
Approver reviews and approves, denies, or pushes back
If approved, transaction saves to PeopleSoft tables and becomes effective
All steps are logged in the AWE Transaction Monitor with timestamps and EMPLID of each actor

🔑

Pattern 1

Role Separation — Initiator vs. Approver

Critical›

The most fundamental AWE control: the person who initiates a compensation-affecting transaction must not be the same person who approves it.

Implementation

In the AWE Process Definition, configure the approval stage to require an approver with a different EMPLID than the initiator
Use PeopleSoft row-level security to ensure payroll staff can initiate transactions but do not have the approval role
Managers can initiate transactions for their own direct reports but should not be able to approve transactions they initiated
Configure the Approval Authorization to assign the approval role to a separate group (e.g., HR Compensation) with no overlap with the Payroll Initiator role

Role Matrix

Role	Can initiate?	Can approve?	Notes
Payroll Analyst	Yes	No	Enters data; cannot approve own entries
Payroll Manager	Yes (escalations)	Yes (up to dollar threshold)	Can approve other analysts' entries; cannot approve own
HR Manager	Yes (Job Data)	Yes (within their department)	Cannot approve transactions for employees outside their supervisory org
Compensation Analyst	No (payroll entry)	Yes (pay rate changes above threshold)	Secondary approval for material pay changes
Payroll Director	Yes	Yes (all)	Final approver; cannot be both initiator and sole approver

🚫

Pattern 2

Self-Approval Prevention

Most Common Failure›

The most common AWE audit finding: missing self-approval block. If an employee holds both an initiator role and an approver role, AWE will — by default in some configurations — allow them to approve their own transactions. This is a SOD failure that auditors always test for.

Implementing the Self-Approval Block in AWE

In the AWE Process Definition, set the Self Approval flag to Not Allowed for all payroll-affecting processes
Configure the AWE Criteria to skip to the next available approver when the approver's EMPLID matches the initiator's EMPLID
Test by submitting a transaction as a user who also has the approver role — verify the transaction is routed to a different approver, not back to the same user
Document the test results and retain for audit purposes

Edge Case: When Only One Approver Is Available

If the only available approver is the initiator (e.g., a solo HR manager at a small entity), configure an escalation path to the next level of management rather than allowing self-approval. An unapproved transaction is preferable to a self-approved one from a compliance standpoint.

🔄

Pattern 3

Delegation Controls

›

PeopleSoft AWE supports approval delegation — an approver can delegate their approval authority to another user for a defined period (vacation coverage, leave). Delegation without controls creates a bypass vector for self-approval prevention.

Delegation Design Requirements

Mandatory expiration date: All delegations must have an end date. Open-ended delegations with no expiration are a control failure. Configure AWE to reject delegation records without an end date.
Self-delegation prohibited: A user cannot delegate approval authority to themselves or to a user who would create a self-approval scenario for any pending transactions.
Delegation audit log: Every delegation event must be logged — who delegated, to whom, for what process definitions, and for what date range. Retained in AWE Transaction Monitor.
Notification to delegate: The delegate must receive a system notification when a delegation is created. Undisclosed delegations are a control failure.
Approval authority limitation: Delegates should not receive broader approval authority than the delegating approver. Configure delegation templates to limit scope.

PeopleSoft Delegation Setup Path

Self Service > Manage Delegation > Create Delegation Request. Delegation administration: PeopleTools > Security > Delegation > Delegation Authority Setup.

📝

Pattern 4

Audit Trail Configuration

›

AWE's Transaction Monitor provides an out-of-the-box audit trail for approved/denied transactions. However, the default retention and logging settings may not meet IRS 4-year retention requirements or SOX audit trail completeness standards.

Audit Trail Requirements for Payroll AWE

Enable AWE Transaction Monitor logging for all payroll-affecting process definitions
Configure the AWE Transaction Monitor purge schedule to retain records for a minimum of 4 years (IRS requirement) — default PeopleSoft purge settings may be shorter
Ensure the audit trail captures: EMPLID of initiator, EMPLID of each approver, timestamps of each action, action taken (Approve/Deny/Pushback), and comments entered
For compensation changes, the transaction log should capture both the previous and new values — verify your component interface or transaction setup passes both values to the log
Configure email notifications for all approvals to create a secondary record in corporate email system (additional audit evidence)

Accessing the AWE Audit Trail

Enterprise Components > Approvals > Transaction Monitor. Filter by Process ID, date range, or EMPLID. The Transaction Monitor shows each step, who acted, and the timestamp. For IRS examination purposes, export the relevant Transaction Monitor records to a PDF or spreadsheet and retain with the payroll audit trail documentation.

📱

Pattern 5

Fluid-Ready AWE Design

›

PeopleSoft Fluid UI requires specific AWE configuration to render approval workflows correctly on mobile and responsive layouts. Classic AWE configurations may not render properly in Fluid without updates.

Fluid AWE Configuration Requirements

Enable the Fluid Approvals Framework for applicable process definitions — this uses the delivered EOAWFL application package and Fluid approval pages
Configure the Pending Approvals tile on the Fluid homepage to surface pending payroll approvals — reduces approval latency
Review approval notification templates for mobile-friendly rendering — long comment fields and tables may not render well on small screens
Test approval workflows on mobile devices before go-live — approval buttons must be accessible on iOS and Android without zooming
Fluid delegation uses the same backend as classic but renders through Fluid Manager Self Service — verify delegation pages are accessible in your Fluid tile configuration

Fluid Pending Approvals page. The delivered Fluid Pending Approvals page (EOAWFL_APPROVLS_FL) provides a mobile-optimized view of all pending approvals across all AWE process definitions. Configure this page to appear in the relevant manager role's Fluid homepage so approvals don't stall because managers miss email notifications.

⚠️

Common Failures

AWE Implementation Failures That Create Audit Findings

›

Failure mode	Audit / compliance risk	Remediation
Self-approval not blocked	SOD failure; IRS examiner finding; SOX deficiency	Set Self Approval = Not Allowed; retest all process definitions
AWE bypass via direct table entry (PeopleCode override)	Entire control framework bypassed; undetected changes	Audit PeopleCode for direct table updates; enable Application Engine logging
Delegation with no expiration date	Permanent proxy approval authority; invisible to standard access reviews	Require end date on all delegations; quarterly delegation audit
Approval chain too short (auto-approve on timeout)	No human review if approver doesn't act; transactions pass without authorization	Configure escalation instead of auto-approval; notify manager of stale items
AWE Transaction Monitor retention too short	Cannot reconstruct approval history for IRS exam period	Extend purge schedule to 4+ years; archive older records before purge
Approval comments not required	Approved transactions with no documented rationale; examiner asks why	Configure approval comments as required for payroll-affecting processes
Approver can approve for own department pay increases	Manager approving own team's increases without independent review	Add secondary Compensation approval step for increases above threshold

✅

Testing Checklist

AWE Controls Testing Before Go-Live

›

Self-approval test: Log in as a user with both initiator and approver roles. Submit a Job Data change. Verify the transaction is NOT routed back to the same user for approval.
Role separation test: Submit a pay rate change as a Payroll Analyst. Verify it routes to the configured approver and cannot be approved by the same analyst.
Delegation test: Create a delegation with an end date in the past. Verify the delegation is rejected or the approver cannot act under an expired delegation.
Open-ended delegation test: Attempt to create a delegation with no end date. Verify the system rejects the request or requires an end date.
Transaction Monitor test: Approve a test transaction and verify the audit trail in Transaction Monitor shows initiator EMPLID, approver EMPLID, timestamps, and action taken.
Fluid rendering test: Access the Pending Approvals page on a mobile device. Verify approval buttons are accessible and the approval can be completed on mobile.
Escalation test: Create a test with the approver's out-of-office flag set. Verify the transaction escalates to the next level rather than auto-approving.
Deny and pushback test: Deny a test transaction and verify the initiator receives notification and the reason is captured in the audit trail.

AWE Design Patterns for Payroll Approval