Although PeopleSoft systems like UCPath are advanced and mostly automated, users should monitor transactions to ensure accuracy and impact. This is particularly true when it comes to retroactive transactions and their impact on benefits in UCPath.
UCPath's benefit eligibility processes are designed to look forward. When a retroactive transaction is entered, the system updates the job data, but its automated benefits process may not reevaluate the past. In some cases, this may result in the unintended early termination of employee benefits. Therefore, when a retroactive transaction such as a job change occurs, benefit eligibility is may not be automatically reevaluated and adjusted. This can create a mismatch that affects benefits.
What you can do
When a retroactive change is processed that could affect an employee's benefits, work with your UCLA department HR administrator to monitor the transaction and benefit eligibility. An HR administrator can:
- Identify that the retroactive change affects benefit eligibility.
- Manually review the employee's benefit status for the period of the retroactive change.
- Ensure the correct eligibility is applied and that benefits are correctly reinstated or enrolled, preventing any disruption in coverage.
Reviewing the Benefits Triggers Job Aid may help you promptly and proactively correct an issue. If needed, you can expedite support by creating a UCPath case and contacting CRU and requesting an escalation.
Manual department oversight is a crucial step that prevents system limitations from causing real-world problems. The More You Know!
