Overview
This job aid shows Campus Benefits Officers (CBOs) what to process for employee transfers and short-term rehires.
Reference
Use the following Job Aids to process employee benefits using On-Demand Event Maintenance:
Background
- A transfer means that no break in service occurs for the employee, for example, the employee terminates from campus A on a Friday, and starts at campus B on a Monday.
- A rehire less means that the employee is being rehired at a CSU campus and that there's been a break in service.
- The break in service can be less than 30 days, or greater than 30 days.
- A weekend between appointment start and end dates does not constitute a break in service.
- Transfers between campuses and short term (less than 30 days) rehires can cause disruption to employee benefits.
- Employees can lose benefits.
- Employees treated as new-hires.
- Transfers can occur between campuses that are different versions of PeopleSoft. Only PeopleSoft 9.2 campuses are in CHRS.
- CHRS has action/action reason codes specifically to handle these situations.
- These action/action reason codes trigger specific BAS Events that you need to process manually.
The following flowchart shows the processes for transferring an employee from one CHRS campus to another CHRS campus. Ideally, the event is coordinated between campuses.
What you need to do
- If you are a Benefits Officer at the old campus, there is nothing that you need to do. Do NOT delete or process the MSC event: The CSUBAS nightly process deletes the MSC event automatically.
- If you are a Benefits Officer at the new campus, process the REH BAS event in On-Demand Event Maintenance. Do not treat the employee as a new hire. The employee keeps their current benefits and they are only eligible to change their medical benefit plan if there was a home or work location change that made them ineligible for their previous medical plan.
The following flowchart shows the processes for transferring an employee from a 9.0 campus to CHRS campus. Ideally, the event is coordinated between campuses.
What you need to do
- If you are a Benefits Officer at the old campus, there is nothing that you need to do. Do NOT delete or process the TER BAS event: The CSUBAS nightly process finalizes the TER event automatically.
- If you are a Benefits Officer at the new campus, use the T92 BAS event in On-Demand Event Maintenance to enroll the employee into the same benefits they had at the old campus. Do not treat the employee as a new hire. The employee keeps their current benefits and they are only eligible to change their medical benefit plan if there was a home or work location change that made them ineligible for their previous medical plan.
The following flowchart shows the processes for transferring an employee from a CHRS campus to a 9.0 campus. Ideally, the event is coordinated between campuses.
What you need to do
- If you are the Benefits Officer at the old campus, you need to terminate the employee's benefits enrollments and finalize the T90 BAS Event in On-Demand Maintenance.
- If you are the Benefits officer at the new campus, you need to Start benefit enrollments on v9.0. Obtain the employee's benefits information from terminating campus. Do not treat the employee as a new hire. The employee keeps their current benefits and they are only eligible to change their medical benefit plan if there was a home or work location change that made them ineligible for their previous medical plan.
The following flowchart shows the processes for rehiring an employee within 30 days of being terminated from a 9.2 campus.
What you need to do
- Adjust benefits only if eligibility changes. The employee is not treated as a new hire regarding benefit changes.
- You need to determine whether the employee has a TER BAS event prior to the REH BAS event and then determine whether the prior TER event terminated the employee's benefits.
- If the the TER BAS event terminated the employee's benefits, you can void the TER BAS Event, which reinstates their prior benefits.
- If the employee had no prior benefits that were terminated, you do not need to void the TER BAS event.
- The employee keeps their current benefits and they are only eligible to change their medical benefit plan if there was a home or work location change that made them ineligible for their previous medical plan.
- Use the REH BAS Event to change the employee's medical benefits if applicable and finalize the REH BAS Event in On-Demand Event Maintenance.
The following flowchart shows the processes for rehiring an employee after 30 days of being terminated from a 9.2 campus.
What you need to do
- Treat the employeeas a new hire regarding benefit changes.
- Use HIR/>30 when the employee doesn't have an EMPLID and EMPL_REC_NBR for the campus in v9.2.
- Use REH/>30 when the employee does have an EMPL_REC_NBR for the campus in v9.2.
- CSUBAS finalizes HIR and NEW event (if your campus is full eBenefits)
- If your campus is view-only: You create and finalize the HBE to enter core benefit elections.
- If your campus is full ESS: create the NEW BAS event, move it to a Prepared Process Status, then advise the employee to log into eBenefits to choose benefit elections.
- At a Full ESS campus, you need to audit the enrollment and then finalize the event in Update Event Status.
End of Article
0 Comments
Add your comment