Implementing campuses have an array of tasks to complete. Campuses should refer to the TL Setup Checklist for Implementing Campuses for details.   

The TL auto-enrollment process is configurable by campuses and should be reviewed by the campus. Starter queries and enrollment configurations have been provided by CMS, but they can be edited or inactivated as part of campus configuration.

The CO delivers baseline templates in CHRS, but campuses have the ability to create their own templates, as needed.

The only employees that require a work schedule are those enrolled in absence management or using Time & Labor rules which refer to the assigned work schedule (e.g. auto-assignment of ADO).

Yes.  Campuses can build and maintain their own TL Rule Programs. 

The fields in this region are used to specify the information displayed alongside the employee's name and job title on the Time and Labor Self Service pages.

• All timesheet transactions must be reviewed and approved to ensure accurate payment and balances.
• For managers, the approval tile displays a count of approvals pending action.

Navigation: Manager Self Service > Time Mgmt > Approve Time & Exceptions > Payable Time

Time Admin is automatically triggered to run as time entries are submitted on the timesheet and the time is available for approval immediately afterwards.  Time Admin will not be scheduled to run via batch.  Campuses can run Time Admin, as needed.

Navigation: Menu > Time and Labor > Process Time > Request Time Admin

• All compensatory time are maintained in Time & Labor and not Absence Management in CHRS. This includes all compensatory time: CTO, ADO, Holiday CTO, Holiday Credit, and HG5/HG6.
• Employees must be enrolled in comp time plan(s).
  • Navigation: Menu > Time & Labor > Enroll Time Reporters > Comp Plan Enrollment
• Report all compensatory time adjustments using the timesheet.
• ADO is automatically generated by the system based on employees’ work schedule. ADO is maintain by days, not by hours.

Campus users are to use the Exceptions page to review and resolve exceptions.

Navigation: Manager Self Service > Time Mgmt > Approve Time & Exceptions > Exceptions

All absence eligible employees – those enrolled in absence management in Job Data – or those enrolled in a Time & Labor ADO plan must be assigned to a work schedule.  All schedule assignments must align with the employees’ FTE (e.g. a part-time .50 FTE employee must be assigned to a corresponding .50 FTE schedule.)  Any employees who are not explicitly assigned a schedule will default to the Standard M-F 40 Hours schedule.

Navigation: Menu > Time and Labor > Enroll Time Reporters > Assign Work Schedule

The TL auto enrollment process is used to automatically set up and update Time Reporter Data for employees. Campuses are responsible for their own setup. Review the starter queries and enrollment configurations delivered by CMS and update, if necessary, to meet campus specific needs.

Navigation: Menu > Time & Labor > Enroll Time Reporters > Process Auto Enrollments

Once the employee submits the time a timeadmin process for that employee is automatically run and Payable time is created. Goes to the designated approver (based on the approval options) for approval.

Hourly employees, including student workers, should enter their hours daily.

The Rule CSUT008 will be delivered in baseline and will automatically set blank TRC rows as "REG".

The hours will not count towards accruals.  

Yes, enter on the timesheet.  If a correction to accruals is required, perform the late time entry business process to set a retro trigger.  

No, the adjust paid time process is only needed if payable time needs to be adjusted.  Make changes to the timesheet directly. 

Anything entered on the timesheet will require approval as per the campus-defined approval process.  ADO created via rules will not require approval.

CTO Time is approved in the Approvals tile.  If the time is not showing up in the tile, review the Workgroup as it could be misconfigured before opening a ServiceNow ticket. 

They are done directly on the timesheet using the appropriate adjustment TRC.

Job Aids: 

• Employee Enter Additional Days (ADO/ADOT)
• Employee Enter Compensatory Time (CTO)

The timesheet should be used to correct all prior period entries.  The hours worked on the timesheet should reflect the hours reported to the SCO.  The adjust paid time process should only be used if there is a change in the pay that cannot be reflected by correcting the timesheet.

Time & Labor entries come in  via the TL_PAYABLE_TIME record. The campus then has to run the CSU TL Earnings Distribution process (CSUTL09A.SQR) for that data to get populated into the CSU_TL_ERN_DIST record. From there, Pay Check Create program (CSULCD20.SQR) picks up the Combo Code from the CSU_TL_ERN_DIST record. For Additional Pay, that gets entered on the Additional Pay page into the ADDL_PAY_DATA record, which should also get picked up in the Pay Check Create program (CSULCD20.SQR).

Transactions are routed to the employee’s reports-to position. This routing logic does not account for leave status or other employment statuses. To avoid approval interruptions, it is recommended to proactively set up delegation before any planned leave.

However, for Time and Labor (TL) approvals, the recommended setup is to use Dynamic Groups instead of the reports-to hierarchy.

No, the "Save for Later"  functionality is not enabled on Timesheets.

Campus controls the security on what they can see and what they can not see. Row level security for the user is tied to the T&L access tied using a dynamic group that campuses maintain.

 No, the manager will not receive an email when time is entered on the timesheet.  

 No, the manager will not receive an email when time is entered on the timesheet.  

No. 

The manager will see a number on the approvals tile indicating the number of pending approvals. 

No, the employee will not see any notifications on their fluid tiles.

All time entries and approvals for the cycle must be complete before the 5^th business day.  Central CHRS will close the cycle for all campuses on the 5^th day each month. New to CHRS, the PIP interface process includes the ability to exclude specific employees from the PIP file.

Navigation: Menu > Time & Labor > CSU Time & Labor > CSU PIP

Job Aid: Run Payroll Input Process (PIP) Audit Report

Yes.

Job Aid: Run Payroll Input Process (PIP) Audit Report

In CHRS, campuses will have the ability to remove rows from the PIP file through the front end.  If an update to the PIP file is required, then the best practice is to do it through the front end, rather than modifying the file itself.

​Yes, each PIP Process creates a PDF, a CSV and a text file.

When payable time values are generated from reported time values, a rule is run (CSUC111) which rounds the payable time as per SCO rules. The rounding occurs for each individual date (DUR - Date Under Report), and not a sum of hours worked in the period.

Rounding will not occur on reported time (either elapsed or punch), but will round on payable time.  The rounding will occur for each payable time entry; on a daily basis, not on a sum of hours.

​No, the data is displayed on a separate page in CHRS. 

Navigation: Menu > Time and Labor > CSU Time & Labor > CSU Run MPC Process

Job Aid: Run Master Payroll Certification (MPC) Reports

Review the Run Master Payroll Certification (MPC) Reports Job Aid for more information.

The main difference between the two is freshness of data.  CHRS Reporting QuickSight will be a day old, while the multi-report will be live.  From a CMS perspective, it is preferred that campuses use CHRS Reporting QuickSight as it is optimized for reporting purposes.  That said, the campus should use the tool which matches their business process.

The table you will need is CSU_WS_BAL_VW.

TL_COMPLEAV_TBL and TL_COMP_DAY_BAL.

The Comp Time TRCs have been incorporated in to the Absence MultiReports (GRP 186)

No audits will be provided as the "Save for Later" functionality is not enabled on Timesheets.

Yes. 

Yes, the list of delivered queries is available in the CHRS Knowledgebase, in a document titled TL CHRS Delivered Queries.