This job aid shows Benefits Officers how to:
- Download CSU Payroll Deduction Audit Report
- Create a spreadsheet for working through issues
- Resolve CSU Payroll Deduction Audit Report issues
Background
- Each month, after the monthly LCD tape is loaded to CHRS, you must run the CSU Payroll Deduction Audit Report.
- Resolve all issues within the first two weeks of each month.
- The sooner you run and resolve issues on this report, the cleaner your next SCO Interface, Delta Dental Interface and PeopleSoft benefits data.
- Corrections by the State Controller's Office (SCO) may take more than a month to resolve and subsequently drop off from the CSU Payroll Deduction Audit Report.
Download CSU Payroll Deduction Audit Dashboard
Use these procedures to run the CSU Payroll Deduction Audt Dashboard
Log in to Amazon QuickSight
You can log in to Amazon QuickSight if you have Amazon QuickSight Reader or Author security roles assigned in PeopleSoft. If you need access to QuickSight, contact your campus CHRS security administrator. After you obtain access, you will be able to log in with Single Sign-On.
Step 1: Navigate to CHRS Reporting Home.

Step 2: Click the CHRS Reporting link.

- You are directed to the CHRS Reporting website.
- If the link does not work, contact the BI/DO team at [email protected].
Open the Dashboard
Step 1: Click the Dashboards navigation option.

Step 2: On the Dashboards page, click the Payroll Deduction Audit tile.

The dashboard opens to the PeopleSoft Benefits Data vs. PIMS Payro... page.
Step 3: Export PeopleSoft Benefits Data vs. PIMS Payro... to Excel.
- Click the three dots in the top right of the page.
- Click Export to Excel.

Step 4: Open each of the other three tabs and export each page to Excel.
Keep your Benefits Excel files on a secured shared location so that other Benefits Officers can work on them.
Create a spreadsheet for audit issues
This method for organizing the spreadsheet has been used by campuses successfully.
Step 1. Save the PeopleSoft Benefits Data vs. PIMS Payroll download on a shared location. Rename this file to include the report month. Example: Payroll Deduction Audit May 2025.
Step 2: Rename the worksheet tab Working List.
Step 3: Create the following worksheets:
- New Enrollments
- Termination
- PIMS Deds not in PS
Step 4: Open each of the other downloads and copy all the data from each file into the appropriate tab of the
All worksheets
You will create a single Excel spreadsheet that contains all worksheets. On all worksheets, do the following:
- Add a Notes/Comments column.
- Resize the columns to see everything clearly.
Working List
- Initially, this worksheet contains all the data on the PeopleSoft Benefits Data vs. PIMS Payro download. However, you will remove rows from this worksheet to create the following worksheets:
- LWOP
- FERPS
- Inactive Ben Prog
- VSP Premier - Plan Type 14
- After you remove the rows for these worksheets, Working List contains remaining employees that are not placed on other worksheets. You can then start working directly on this worksheet.
What to do on this worksheet:
- Review and resolve Plan Type 60 and 61 (HCRA/DCRA) first.
- Review and resolve Plan Type 10, Medical issues second.
- Mismatched Deduction Code between PS and PIMS – this is a common error on the Working List worksheet. Check to see what medical benefit plan the employee is enrolled in in PeopleSoft and compare it to the medical plan in CalPERS. Also, review the employee’s applicable HBD-12 form. If the plan differs in CalPERS and the employee’s HBD-12 form from PeopleSoft, correct the employee’s medical benefit plan in PeopleSoft by reprocessing the applicable enrollment BAS event and reprocessing all BAS events from that point forward through the current BAS event. Note, the solution may also mean that a new effective-dated BAS event may need to be added to complete the correct enrollment.
New Enrollments
This worksheet contains all the data that you downloaded from New Benefits Enrollment tab from QuickSight. The Recent new hires and newly benefit-eligible employees who have been enrolled into benefits and the column Error message is ‘New Election as of: ##/##/####’. Use this listing in your new hire audits to verify correct.
Benefit Terminations
This worksheet contains all the data that you downloaded from the Terminated Benefit Enrollments tab from QuickSight. Recent benefit plan terminations (also includes waive (voluntary cancel) where the employee was previously enrolled) and Values message is ‘Election Termination Date: ##/##/####’. Use this listing in your benefit plan termination audits to verify correct.
PIMS Ded w/no PS Bens
- This worksheet contains all the data that you downloaded from PIMS Deductions with no PeopleSoft tab from QuickSight.
- Employees who are enrolled in certain benefit plans per the PIMS system, but not per the PeopleSoft system. Select the column G Cvg Type equal to Employer-Paid and Employee-Paid. Review and take the appropriate action to clear this message. One of these systems is correct. Determine which one.
- Compare employees against prior CSU Payroll Audit Deduction Report to see if employee is on the report.
- Always check the B003 Compendium Report and the Benefits 360 Dashboard to see if shared employee with another CSU campus, and always check the Override Benefits Eligibility Excel document to see if the employee has overwritten benefits eligibility.
LWOP
To create this worksheet:
- Create a new worksheet tab, named LWOP.
- Move employees from the Working List where the Value message is ‘Leave without Pay.’
What to do on this worksheet:
- Compare employees against prior CSU Payroll Audit Deduction Report to see if employee is on the report.
- Employees who show a status as Leave of Absence in PeopleSoft (not paid Leave of Absence) and column K (in 9.0) column O (in CHRS) on the report says, ‘Leave without Pay.’.
- Verify that employees on the LWOP worksheet are on leave without pay, and that they have been offered the direct pay option to maintain their benefit coverage, and if they have not been offered that option, offer that option to the employee.
- Note on the worksheet the date and communication medium used to offer the employee the direct pay option.
- Employees are responsible for paying both the employee cost and employer cost of the benefits while on direct pay coverage.
- If the employee is on a long-term disability, make sure to fill out and submit the long-term disability claim form to The Standard. Note on the worksheet when you fill out and submit the long-term disability worksheet to The Standard, in addition to placing this form into the employee’s file.
FERPS
To create this worksheet:
- Create a new worksheet tab, named FERPS
- Move employees from the Working List where the Message is ‘FERP - No Ded past 12 months.’
What to do on this worksheet:
- Employees with issues/errors related to FERP Vision enrollment.
- Compare employees against prior CSU Payroll Audit Deduction Report to see if employee is on the report.
- Employees are eligible for FERP Vision for a total of 5 years. Sign into PeopleSoft and go to Benefits > Interface with Providers > CSU FERP Vision Deduction to see FERP employees who are Active, on a Work Break and Terminated. The FERP Elig End Date appears, along with the last time the FERP premium was paid, processed via the SCO interface. Note that for FERP premiums paid via the benefits SCO MISC Form, the FERP Premium Paid date on the CSU FERP Vision Deduction page in PeopleSoft is not updated, so be sure to manually track employees with manually paid annual premiums.
- FYI Only – The FERP Annual Premium Process: Go to the CSU FERP Vision Deduction page (Benefits > Interface with Providers) each semester and then review and select to Pay Spring appointments in February to make effective dated 3/1 and review and select to pay Fall appointments in September for 10/1 effective date. This is a coordinated exercise that should occur between Faculty Affairs, Payroll and Benefits to identify the active FERP appointments. The annual FERP Vision Deduction is transmitted to the SCO via the SCO Interface. Do not check mark the Work Break or Terminated appointments.
- Before February 15 of each calendar year, Benefits must go to CSU FERP Vision Deduction page in PeopleSoft and select to pay Spring FERP appointments on this page, and before September 15 of each calendar year, Benefits must go to CSU FERP Vision Deduction page in PeopleSoft and select to pay Fall FERP appointments on this page. Note that you cannot submit and transmit a FERP deduction until the FERP deduction is in PIMS (Payroll keys the appointment in Job Data and then creates a PPT and keys the appointment into PIMS).
Inactive Ben Prog
To create this worksheet:
- Create a new worksheet tab named Inactive Ben Prog
- Move employees from the Working List where the Benefit Program column equals RET, TER, and NOB benefit programs.
What to do on this worksheet:
- This is a list of employees in the RET, TER and NOB benefit programs who show as enrolled or terminated (Coverage Elect = E or T) in benefit plans in PeopleSoft but have a coverage or deduction discrepancy between PIMS and PeopleSoft.
- For the most part, the employees on this worksheet are recently terminated or retired employees who have benefit plans active until the first of the following month, and the majority of the employees listed have no issues. If the terminated employee’s Benefits are active until a future date (i.e., the first of the following month), you can ignore the employee on this particular worksheet.
- If an employee is on the Inactive Ben Prog worksheet with terminated benefits for an old effective date, check to see in PeopleSoft when the termination row was created in the CSU SCO Interface Inquiry page (reference the Election Date on the CSU SCO Interface Inquiry page). If the Election Date and the submission date is prior to the 15th of the previous month, check the employee’s deduction in PIMS to see if it was terminated. If Vision, Life, LTD and Dental (if you are a campus that transmits dental enrollments to the SCO in lieu of submitting Form 692) was not terminated in PIMS, resubmit the original SCO Interface termination transaction(s) for each applicable plan type for the employee on the SCO Interface Inquiry page. Note that if the original benefit plan termination transaction was sent to the SCO before the campus Payroll department keyed the termination transaction into PIMS, the employee’s deduction will still be active in PIMS. If you find that a benefit plan enrollment or termination transaction for an old date was never submitted to the SCO, then you will need to fill out and submit the applicable SCO form (MISC, 692 or 674).
- For most classifications, an NOB benefit program employee can be enrolled in HCRA/DCRA and that is correct. NOB benefit program no longer means not benefit eligible. It means that an employee is not eligible for mandatory benefits and core benefits except for HCRA/DCRA. It is rare that an NOB employee is enrolled in HCRA/DCRA, but it can happen and is generally valid.
- Compare employees against prior CSU Payroll Audit Deduction Report to see if employee is on the report.
- Review each employee and verify that the benefit program and current benefit plan enrollment is correct.
- It is common to find retired or terminated employees in this section of the report who are still enrolled in benefit plans due to the original RET or TER BAS event date being disconnected. To resolve, make sure the disconnected TER or RET BAS event is voided, and then reprocess the employee’s replacement RET and TER BAS events, then verify that all benefit plans have terminated for the employee.
VSP Premier - Plan Type 14
To create this worksheet:
- Create a new worksheet tab named VSP Premier - Plan Type 14
- Move employees from the Working List where the benefit plan (Cov Typ is 14, and Plan is VSP) and when the error message is Mismatch Deduction Code.
What to do on this worksheet:
- This is a list of employees who are enrolled in the VSP Premier plan. This is not a list for you to review for errors. It is an FYI listing, butt it can be helpful for troubleshooting VSP issues.
- If an employee says that they ‘lost’ their VSP Premier coverage, sign into PeopleSoft and confirm that they are enrolled in VSP Basic, and then sign into PIMS and confirm that the VSP Basic and the VSP Premier deductions are in place.
- Each month, compare the new VSP Premier worksheet against last month’s VSP Premier worksheet to identify 1) employees who are no longer on the list, and 2) newly added employees. Then review those identified employees to ensure that they have the correct enrollment in PeopleSoft and deduction codes in PIMS. Doing this verification is a proactive approach to avoid getting a phone call from the employee that they do not have or have lost their VSP Premier vision coverage. If the employee is not enrolled in basic vision and is qualified for vision and was enrolled in VSP Premier, the employee and their dependents (if applicable) will lose their VSP Premier enrollment. Make sure to enroll the employee and the applicable dependents into basic vision and contact VSP as soon as possible to alert them that the employee is enrolled in basic vision if this situation occurs.
Tools
To resolve these issues, you might need to use one or more of the following tools:
- Prior CSU Payroll Deduction Audit Report
- PeopleSoft System
- PIMS System
- B003 Compendium Report
- Benefits 360 Dashboard
- Override Benefits Eligibility Excel document
- CalPERS system
Resolve Issues with Error Messages
Resolve the issues that are indicated in the Messages column of the downloaded spreadsheets.
-
Error Message: Cvg Elected; No Dedctns Taken = Employee shows enrolled in PS, but there’s no deduction on current paycheck/PIMS.
-
Action: Confirm enrollment status (Coverage Elect = Elect) is valid and correct in PeopleSoft for that plan type.
- If enrollment status is correct for Dental in PeopleSoft and a deduction is due, locate the original SCO Form 692, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to re-establish the deduction in PIMS.
- For Vision, Life and LTD plan types, this error occurs when the SCO Interface is sent to SCO before the employee is entered by Payroll into PIMS. In other words, this issue can be a timing issue. If enrollment status is correct in PeopleSoft and a deduction is due, go to the CSU SCO Interface Inquiry page, and see if the plan type enrollments transmitted to the SCO via the SCO Interface. If they show that they did, checkmark the Resubmit button. The Plan type enrollments will be included on the next SCO Interface. Verify that they are after the next SCO interface runs. If they are not resubmitted, or if the Resubmit button is greyed out, submit SCO MISC Form.
- For Health, if enrollment status is correct in PeopleSoft and a deduction is due submit SCO STD Form 674. Also verify the correct enrollment exists in CalPERS.
- For HCRA/DCRA and for Flex Cash, if enrollment status is correct in PeopleSoft and a deduction is due locate the original enrollment form, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to re-establish the deduction in PIMS if a deduction is due.
- If the HCRA/DCRA OE enrollment reported on the HCRA/DCRA Enrollment spreadsheet is incorrect, use SCO STD Form 674 to communicate the correction.
- If there’s no deduction due to a termination of employment or no benefits-eligibility and the enrollment status is correct, this is an expected error message due to the end of benefits and the coverage end date. No action is required.
- Save the forms to the HR Benefits Shared Drive in the applicable form folder in Benefits Enrollments so the Health Benefits officer can sign and submit the forms to the SCO using ConnectHR. Also, print out a copy of each form and place it in your follow-up folder.
- Review your follow-up folder every two weeks to see if the SCO has processed the requested change/correction. Do not shred your follow-up folder copy of the form until you have verified that the SCO has processed the requested change/correction.
- Use the following link to access the SCO Payroll Procedures Manual for additional SCO STD Form 674 instructions if needed. https://www.sco.ca.gov/ppsd_ppm.html
- Note: this error message can also occur when employees are shared with other campuses and the deductions are from the campus whose payroll is processed first by the SCO (the SCO does not care nor track the campus is that is the employee’s PeopleSoft Benefit Primary Job). Check the B03 Compendium report and the Benefits 360 Employee View Dashboard to see if this is a shared employee and to also confirm that the coverage and deduction status is correct and in order. If the coverage and deduction status is not correct, take the appropriate action to resolve the issue.
-
Action: Confirm enrollment status (Coverage Elect = Elect) is valid and correct in PeopleSoft for that plan type.
-
Error Message: Mismatch Employer-Paid Deduction = PS Rate vs PIMS Rate doesn’t match.
- Action: Confirm if the Cvg Cd in PeopleSoft matches the premium being paid by the SCO. If the enrollment is correct in PeopleSoft, for Dental locate the original SCO Form 692, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to re-establish the deduction in PIMS.
- For Vision, Life and LTD plan types, if enrollment status is correct in PeopleSoft and a deduction is due submit SCO MISC Form.
- For Health, if enrollment status is correct in PeopleSoft and a deduction is due submit SCO STD Form 674. Also verify the correct enrollment exists in CalPERS.
- For HCRA/DCRA and for Flex Cash, if enrollment status is correct in PeopleSoft and a deduction is due locate the original enrollment form, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to re-establish the deduction in PIMS to re-establish the deduction in PIMS if a deduction is due.
- If the HCRA/DCRA OE enrollment reported on the HCRA/DCRA Enrollment spreadsheet is incorrect, use SCO STD Form 674 to communicate the correction.
- If there’s no deduction due to a termination of employment or not benefits-eligible and the enrollment status is correct, no action is required.
- Save the forms to the HR Benefits Shared Drive in the applicable form folder in Benefits Enrollments so the Health Benefits officer can sign and submit the forms to the SCO using ConnectHR. Also, print out a copy of each form and place it in your follow-up folder.
- Review your follow-up folder every two weeks to see if the SCO has processed the requested change/correction. Do not shred your follow up folder copy of the form until you have verified that the SCO has processed the requested change/correction.
- Use the following link to access the SCO Payroll Procedures Manual for additional SCO STD Form 674 instructions. https://www.sco.ca.gov/ppsd_ppm.html
- Note: this error message can also occur when employees are shared with other campuses and the deductions are from the campus whose payroll is processed first by the SCO (the SCO does not care nor track the campus is that is the employee’s PeopleSoft Benefit Primary Job). Check the B03 Compendium report and the Benefits 360 Employee View Dashboard to see if this is a shared employee and to also confirm that the coverage and deduction status is correct and in order. If the coverage and deduction status is not correct, take the appropriate action to resolve the issue.
-
Error Message: Empl Dedctn; Cvg Not Elected = Employee has an active deduction on their paycheck, but the benefit is terminated in PeopleSoft. Note: This error message also generates the Emplr Dedctn; Cvg Not Elected message. Once you resolve the employee deduction issue, the employer deduction error message is resolved and drops off the report.
- Action: Employee may be ineligible for the benefit due to a job change in PS (i.e., reduced time due to time base change).
- Confirm and submit SCO Form Dental 692 to cancel dental deduction if ineligible.
- For Vision, Life and LTD plan types, submit SCO MISC Form to cancel the deduction.
- For Health, if enrollment status is correct in PeopleSoft submit SCO STD Form 674 to cancel the deduction. Also verify the correct enrollment exists in CalPERS.
- For HCRA/DCRA and for Flex Cash, if enrollment status is correct in PeopleSoft, make a copy of the original form generated to cancel the deduction, write “INQUIRY” at the top of the form, and then submit the form to SCO to cancel the deduction in PIMS.
- If the HCRA/DCRA OE enrollment reported on the HCRA/DCRA Enrollment spreadsheet is incorrect, use SCO STD Form 674 to communicate the cancellation.
- If there’s no deduction due to a termination of employment or not benefits-eligible and the enrollment status is correct, no action is required.
- Save the forms to the HR Benefits Shared Drive in the applicable form folder in Benefits Enrollments so the Health Benefits officer can sign and submit the forms to the SCO using ConnectHR. Also, print out a copy of each form and place it in your follow-up folder.
- Review your follow-up folder every two weeks to see if the SCO has processed the requested change/correction. Do not shred your follow up folder copy of the form until you have verified that the SCO has processed the requested change/correction.
- Use the following link to access the SCO Payroll Procedures Manual for additional SCO STD Form 674 instructions. https://www.sco.ca.gov/ppsd_ppm.html
- Note: this error message can also occur when employees are shared with other campuses and the deductions are from the campus whose payroll is processed first by the SCO (the SCO does not care nor track the campus is that is the employee’s PeopleSoft Benefit Primary Job). Check the B03 Compendium report and the Benefits 360 Employee View Dashboard to see if this is a shared employee and to also confirm that the coverage and deduction status is correct and in order. If the coverage and deduction status is not correct, take the appropriate action to resolve the issue.
- Void the TER or RET BAS event in PeopleSoft if the employee was eligible and erroneously cancelled due to job information update (i.e., appointment extensions keyed late, uncleared flags in PeopleSoft (be sure to reprocess and clear all flags on employees if any exist!), rescinded termination of employment or retirement).
-
Error Message: Mismatched Deduction Code = between PeopleSoft and PIMS medical plan for an active employee. Note: This error message also generates the Mismatch Employer-Paid Deduction message. Once you resolve the employee deduction issue, the employer deduction error message is resolved and drops off the report.
- Action: Check PeopleSoft to see if there was a deletion or addition of a dependent. Also review the employee’s medical plan enrollment in CalPERS.
- For Health (medical), if enrollment status is correct in PeopleSoft and a deduction adjustment is due, submit SCO STD Form 674.
- Save the forms to the HR Benefits Shared Drive in the applicable form folder in Benefits Enrollments so the Health Benefits officer can sign and submit the forms to the SCO using ConnectHR. Also, print out a copy of each form and place it in your follow up folder.
- Review your follow up folder every two weeks to see if the SCO has processed the requested change/correction. Do not shred your follow up folder copy of the form copy until you have verified that the SCO has processed the requested change/correction.
- Use the following link to access the SCO Payroll Procedures Manual for additional SCO STD Form 674 instructions. https://www.sco.ca.gov/ppsd_ppm.html
- Note: this error message can also occur when employees are shared with other campuses and the deductions are from the campus whose payroll is processed first by the SCO (the SCO does not care nor track the campus is that is the employee’s PeopleSoft Benefit Primary Job). Check the B03 Compendium report and the Benefits 360 Employee View Dashboard to see if this is a shared employee and to also confirm that the coverage and deduction status is correct and in order. If the coverage and deduction status is not correct, take the appropriate action to resolve the issue.
-
Error Message: Mismatched Deduction Code = between PS and PIMS dental, Flex Cash, HCRA/DCRA, life and/or LTD plan for an active employee. Note: This error message also generates the Mismatch Employer-Paid Deduction message for dental, life and/or LTD plan. Once the employer deduction error message is resolved it drops off the report.
-
Action: Look at original enrollment forms, see if there were changes. For HCRA/DCRA, check the enrollment excel spreadsheet for OE events and the SCO HCRA/DCRA for non-OE events.
- If enrollment status is correct for Dental in PeopleSoft and a deduction/adjustment is due, locate the original SCO Form 692, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to adjust/re-establish the deduction in PIMS.
- For Vision, Life and LTD plan types, if enrollment status is correct in PeopleSoft and a deduction/adjustment is due submit SCO MISC Form.
- For HCRA/DCRA and for Flex Cash, if enrollment status is correct in PeopleSoft and a deduction/adjustment is due locate the original enrollment form, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to adjust/re-establish the deduction in PIMS.
- If the HCRA/DCRA OE enrollment reported on the HCRA/DCRA Enrollment spreadsheet is incorrect, create the HCRA/DCRA Enrollment form to communicate the correction (write “INQUIRY” at the top of the form), and then submit the form to SCO to adjust/re-establish the deduction in PIMS.
- Save the forms to the HR Benefits Shared Drive in the applicable form folder in Benefits Enrollments so the Health Benefits officer can sign and submit the forms to the SCO using ConnectHR. Also, print out a copy of each form and place it in your follow up folder.
- Review your follow up folder every two weeks to see if the SCO has processed the requested change/correction. Do not shred your follow up folder copy of the form copy until you have verified that the SCO has processed the requested change/correction.
- Use the following link to access the SCO Payroll Procedures Manual for additional SCO STD Form 674 instructions. https://www.sco.ca.gov/ppsd_ppm.html
- Note: this error message can also occur when employees are shared with other campuses and the deductions are from the campus whose payroll is processed first by the SCO (the SCO does not care nor track the campus is that is the employee’s PeopleSoft Benefit Primary Job). Check the B03 Compendium report and the Benefits 360 Employee View Dashboard to see if this is a shared employee and to also confirm that the coverage and deduction status is correct and in order. If the coverage and deduction status is not correct, take the appropriate action to resolve the issue.
-
Action: Look at original enrollment forms, see if there were changes. For HCRA/DCRA, check the enrollment excel spreadsheet for OE events and the SCO HCRA/DCRA for non-OE events.
-
Error Message: Mismatch deduction code = Employee shows enrolled in benefits in PeopleSoft but is in the NOB, TER or RET Benefit Program
- Action: Confirm the employee’s employment status and benefits eligibility status and reprocess the employee’s BAS event, clearing all flagged events. After reprocessing the employee’s BAS events, verify that PeopleSoft has assigned the correct Benefit Program for each BAS event. Also, go to the Job Data > Benefits Program Participation page for a Benefit Record 0 job and confirm that the correct Benefit Programs and related effective dates appear for the employee.
- If you have already re-processed the employee’s BAS events and an incorrect Benefit Program and related effective date still appear on the Job Data > Benefits Program Participation page for Benefit Record 0, you can delete the incorrect Benefits Program and related effective date on the Benefits Program Participation page (you must be in correction mode).
- Action: If there’s no deduction due to a termination of employment or no benefits-eligibility and the enrollment status is correct, this is an expected error message due to the end of benefits and the coverage end date. No action is required.
- For most classifications, an NOB benefit program employee can be enrolled in HCRA/DCRA and that is correct. NOB benefit program no longer means not benefit eligible. It means that an employee is not eligible for mandatory benefits and core benefits except for HCRA/DCRA. It is rare that an NOB employee is enrolled in HCRA/DCRA, but it can happen and is generally valid.
-
Error Message: PIMS Deductions w No PS Ben Rcd
-
Action: Review the employee’s Benefits deductions in the CSU Benefits Summary page. Go to Benefits > Manage Automated Enrollment > Events > Update Event Status page. If there are flagged BAS events for the employee, reprocess the employee’s BAS events via the On Demand Event Maintenance page using the applicable reprocessing instructions. Return to the CSU Benefits Summary page to confirm the employee’s PeopleSoft benefits enrollments. Determine why the employee is not eligible for the deduction. Common reasons for this type of error message are:
- change in time base,
- reclassification or change of classification,
- any benefit deduction enrollment that was never terminated in PIMS,
- an incorrect deduction code set up in PIMS.
- Make sure that PeopleSoft and CalPERS are in sync for the employee’s medical plan enrollment status.
- Rerun the CSU Payroll Deduction Audit Report, and if the employee remains on the report, check to see if the employee is on the CIRS A17 report (CIRS = Campus Information Retrieval System). The A17 report identifies employees who are ineligible for benefits but are receiving benefits.
-
Action: Submit the applicable form to the SCO for correction. See below for examples.
-
Example 1: Employee is enrolled in HCRA, Plan Type 60, in PeopleSoft, and that is the correct plan, but PIMS reports that the employee is enrolled in DCRA, Plan Type 61. After confirming the correct plan type the employee should be enrolled in, locate the original HCRA/DCRA Enrollment Form, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to correct the deduction in PIMS.
- If the above example occurs, contact the employee ASAP, advise of the situation and how you are working with SCO to resolve the issue. The reason for alerting the employee is that the employee would be denied HCRA reimbursement for this example if he/she submits a HCRA claim while PIMS maintains the incorrect DCRA enrollment.
- Example 2: Employee is enrolled in LifeCS and Vision in PeopleSoft, but neither plan type enrollments have interfaced via the SCO interface. Reprocess the employee’s BAS events and see if the plan type enrollments are transmitted via the next SCO Interface. If the plan type enrollments are not transmitted via the next SCO Interface, use SCO MISC Form to enroll the employee into the two plan types/benefit plans. The SCO will retroactively collect the employer-paid cost for the impacted benefits.
- Example 3: You reprocessed an employee’s BAS events, and reprocessing results in the employee enrolled into a life benefit plan EFFDT 9/1/23 and is then terminated from CSU employment EFFDT 1/19/24. 1) Check to see if the life benefit plan enrollment and the life benefit plan termination is interfaced to SCO on the next SCO interface, and 2) the SCO should reimburse your campus the employer-paid benefit cost that was overcharged. If the SCO employer paid benefit cost reimbursement does not happen automatically, submit a SCO MISC Form for the employer paid benefit cost reimbursement.
- Example 4: Employee was no longer enrolled in a medical plan in PeopleSoft and CalPERS, but the medical deduction is still occurring in PIMS. Submit SCO STD Form 674 to end an employee’s PIMS benefit enrollment and deduction for Medical.
-
Example 1: Employee is enrolled in HCRA, Plan Type 60, in PeopleSoft, and that is the correct plan, but PIMS reports that the employee is enrolled in DCRA, Plan Type 61. After confirming the correct plan type the employee should be enrolled in, locate the original HCRA/DCRA Enrollment Form, make a copy of the original form, write “INQUIRY” at the top of the form, and then submit the form to SCO to correct the deduction in PIMS.
- Save the forms to the HR Benefits Shared Drive in the applicable form folder in Benefits Enrollments so the Health Benefits officer can sign and submit the forms to the SCO using ConnectHR. Also, print out a copy of each form and place it in your follow up folder.
- Review your follow up folder every two weeks to see if the SCO has processed the requested change/correction. Do not shred your follow up folder copy of the form copy until you have verified that the SCO has processed the requested change/correction.
- Use the following link to access the SCO Payroll Procedures Manual for additional SCO STD Form 674 instructions. https://www.sco.ca.gov/ppsd_ppm.html
-
Action: Review the employee’s Benefits deductions in the CSU Benefits Summary page. Go to Benefits > Manage Automated Enrollment > Events > Update Event Status page. If there are flagged BAS events for the employee, reprocess the employee’s BAS events via the On Demand Event Maintenance page using the applicable reprocessing instructions. Return to the CSU Benefits Summary page to confirm the employee’s PeopleSoft benefits enrollments. Determine why the employee is not eligible for the deduction. Common reasons for this type of error message are:
0 Comments
Add your comment