A pay cycle is the interval at which the university pays employees.
Our pay cycles are either Biweekly or Monthly.
A pay cycle change is triggered when a workforce administration action results in a change to the frequency that an employee is paid.
No, the Pay Group field can not be entered by campus users.
The Pay Group is assigned to an employee by a UCPC nightly process based on various job data attributes. If the FLSA status is manually overwritten, a Case with UCPC must be initiated requesting the Pay Group be overwritten.
In most cases, the Pay Group is evaluated and reassigned (as needed) via the UCPC nightly process. However, if the FLSA status is manually overwritten, a Case with UCPC must be initiated requesting the Pay Group be overwritten.
Yes. The primary trigger for pay cycle changes is an FLSA change. Generally* exempt employees are paid Monthly, and non-exempt employees are paid Biweekly.
*Readers titled employees are FLSA exempt but are paid Biweekly.
No. The Pay Group field is not editable for campus users to change even if the desired Pay Group entry is known.
To change an employee’s Pay Group, you must submit a Job Action Update request form to UCPC via a Case asking for a Pay Group override and provide the desired Pay Group value.
Only UCPC can change the Pay Group field value in UCPath.
The department transactional user who is initiating workforce administration actions that result in pay cycle changes is responsible for managing pay cycle changes.
The transactional user must dutifully anticipate possible pay cycle changes by assessing if key triggering fields like the FLSA status change due to their WFA entry.
A pay cycle change impacts multiple stakeholders including:
- the employee who might not be paid
- technical campus teams who are interfacing pay-impacting data from our campus to UCPC (Timekeeping and Parking)
- transactional department users who must help resolve pay issues
- the campus Payroll office who may need to request off-cycle pay remedies for the employee.