CHRS Knowledge Base

Benefits for transfers and rehires

Updated on

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.
Transfer between two 9.2 campuses

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.

process flow showing transfer between 9.2 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.
Transfer from 9.0 campus to 9.2 campus

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.

process flow showing transfer between 9.2 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  deletes the TER event automatically.
  • If you are a Benefits Officer at the new campus, process the T90 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.
Transfer from 9.2 campus to 9.0 campus

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.

Process flow showing a transfer from a CHRS campus to a 9.0 campus

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 Event Processing.
  • 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.
Rehire less than 30 days from CSU, termination on 9.2

The following flowchart shows the processes for rehiring an employee within 30 days of being terminated from a 9.2 campus.

Process flow showing rehire < 30 days from CSU termination on 9.2

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.
  • After CSUBAS creates the REH BAS Event, you can finalize it from On-Demand Event Maintenance.
Rehire more than 30 days from CSU, termination on 9.2

The following flowchart shows the processes for rehiring an employee after 30 days of being terminated from a 9.2 campus.

Process flow showing rehire > 30 days from CSU termination on 9.2

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)
  • You finalize HBE or if your campus is view-only.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Previous Article Void Expired NT ESS BAS Events
Next Article Prepare Employee for ACA Benefits