Benefits may terminate or be missing from the interface file for several reasons:

• Job termination, unpaid leave, short work break, or employee waiver/life event (e.g., marriage, dependent gains coverage).
• Dependent aged out (26+), though adult dependents are not currently configured to age out in CHRS.
• Delayed entry of benefit changes when using the multiple permitting event code workaround (review via Health Benefits; note Election Date is when processed in Ben Admin).
• Workaround timing issues, as daily enrollments can overwrite Ben Admin/Base Benefit tables. Review with Ben Admin and Base Benefit Audit queries.
• Interface date earlier than the Health Benefits Election Date.
• Interface selection criteria not met (e.g., missing gender, out-of-state address).

If an employee’s Payroll Status changes, their benefits may be waived or terminated. In some cases, a Suspended status can also result in cancelled benefits in CHRS.

• Review BAS events and changes: Benefits > Manage Automated Enrollment > Employee Event Details (see Cheat Sheet).
• Check overall enrollments: Benefits > Review Employee Benefits > CSU Benefits Summary.
• Review detailed enrollments: Base Benefit tables (Health, Disability, Life/AD&D, Spending Accounts).
• Did the employee voluntarily waive benefits while on leave, short work break, or due to a life event? Confirm via Employee Event Details.

Some benefits terminate based on Benefits Employee Status. If the status is Leave of Absence, Terminated, Retired, or Deceased, benefits may be waived or terminated. Employees may also voluntarily waive benefits during unpaid leave, short work breaks, or life events. Review BAS events in Benefits > Manage Automated Enrollment > Employee Event Details (see Cheat Sheet).

Depending on the situation, additional questions may need to be asked:

• Did the employee lose eligibility due to ACA?
• Did the employee end another CSU job?
• Did the employee’s Benefits Primary Job change? (Benefits > Maintain Primary Jobs > Maintain Flags)
• Did the employee waive benefits while on unpaid leave, short work break, or a life event? (Benefits > Manage Automated Enrollment > Review Processing Results > Employee Event Details)
• Did the employee’s work location or address change to outside a geographic eligibility area? (Contact Information & Work Location pages; review Geographic Location Elig Table)
• Did Elig Fld 1–5 values change for the employee’s Benefits Primary Job? (Job Data > Benefits Program Participation)

Depending on the situation, additional questions may need to be asked:

• Did the dependent age out (26 for a qualified child)? (Benefits > Employee/Dependent Info > Update Dependent/Beneficiary) — note: adult dependents are not currently set to age out in CHRS.
• Was this a conversion issue from HR9.0 (dependent missing or dropped in HR9.0 to CHRS)? Compare HR9.0, campus conversion DB, and CHRS.
• Is the dependent disabled but not flagged as disabled for the time period? (Update Dependent/Beneficiary)
• Did the dependent’s relationship change (e.g., spouse → ex-spouse, domestic partner → ex-domestic partner)? (Update Dependent/Beneficiary)
• Did Elig Fld 1–5 values change for the employee’s Benefits Primary Job? (Job Data > Benefits Program Participation)

Review Job Data and check the action/action-reason combinations used for termination and hire rows. Benefits may have ended incorrectly due to how these rows were entered or because of gaps in CSU business processes. If so, coordinate with CMS-Benefits and Systemwide HR (SWHR) to determine if CHRS configuration or business process changes are needed.

For employees transferring between CSU locations, also review Employee Event Detail > Plan Type to confirm Ben Admin changes (see the Employee BAS Event Details Cheat Sheet for guidance).

Flagged BAS events often result from retroactive changes in CHRS (e.g., late hires, rehires, transfers, terminations), Job Data corrections, selective processing by Benefits Officers, or daily BAS events generated before prior events are resolved.

To investigate:

• Go to Benefits > Manage Automated Enrollment > Events > Update Event Status or Review Processing Results > Employee Event Detail to check for flagged BAS events.
• Review flags:
  • Out of Sequence → Events must be reprocessed in the correct order (see Reprocessing Cheat Sheets).
  • Address Eligibility Changed → Check Modify a Person for home state/zip changes and Job Data for work location changes. Moves may affect eligibility for regional plans.
  • Job Eligibility Changed → In Job Data, review fields such as Benefits Employee Status, Location, Empl_Class, Employee Type, FTE, Union Code, Pay Group, and Elig Flds 1–9.
  • Multi Job Indicator Changed → Review the same Job Data fields across all active jobs.

Processing BAS events out of order can incorrectly terminate benefits. Delivered PeopleSoft does not show the exact order of past manual processing, though you can use Ben Admin and Base Benefit Audit table queries (via the CSU Benefits Administrator Tile or Query Viewer) for partial insight. For audit table use, see the CHRS Benefits Audit Table User Guide.

The best solution is to reprocess BAS events in the correct order:

1. By Event Date – Process from oldest to newest (e.g., 1/1/2022 before 2/1/2022).
   Check Event Date in: Benefits > Manage Automated Enrollment > Events > Update Event Status or the Event Status Update button in On Demand Event Maintenance.
2. By Event Priority – For events on the same date, process in order from lowest to highest priority (e.g., 35 → 45 → 200 → 375).
   Check Event Priority in the same pages above.
3. By Event ID – For events with the same date and priority, process in ascending Event ID order (e.g., 1 → 2 → 3).
   Check Event ID in the same pages above.

There are numerous delivered and CSU-custom eBenefits, Ben Admin, and Base Benefit configuration pages. If you suspect a CHRS Benefits configuration issue, submit a ServiceNow ticket for CMS-Benefits to review.