CL - Longevity Increase

Purpose: Leave schedule updates are system generated from payroll when an employee reaches their CSS longevity milestone. The 'CL' is generated for all pay schedules - Hay (H), Military (3) and 000 with Leave codes that begin with A, B, C, or D.

 
Note:  If an employee's CSS hours are updated with a priority update that puts them over a longevity milestone, a 'CL' will not generate on the next payroll processed.  The agency will need to submit a Personnel Remarks form and the 'CL' will have to be manually processed.       
 
System generated 'CL' change reasons will have an effective date equal to the day the employee reaches their CSS milestone, but does not affect the employee's leave accruals until the following pay period.  The 'CL' change reason generates when an employee's Statewide CSS balance combined with their current payroll CSS hour accruals will be equal to or greater than the CSS longevity milestone.
 
Note: If the employee is in multiple positions, the CL will be generated to all positions active on the employee's record during that pay period.
 
If the date an employee reaches their CSS milestone occurs:
 
  • prior to the current class effective date, the 'CL' will generate with an effective date equal to the current class effective date and a retro date equal to the day the employee reached their CSS milestone.
  • during the same pay period a Payroll MVA (Manual, Void, or Adjustment) is processing and no time sheet is processing, the 'CL' will generate with an effective date equal to the MVA effective date.
  • during the same pay period a Payroll MVA is processing along with a time sheet, the 'CL' will generate with an effective date equal to the first date time is coded on the time sheet.
  • during the same pay period two or more Payroll MVA's are processing, the 'CL' will generate with an effective date equal to the latest MVA effective date regardless of which MVA reached the longevity milestone.
  • during a pay period overtime was worked, the overtime hours will be added to the first day of the week the overtime hours occurred.
 
Example of longevity milestone reached when a MVA and a regular time sheet are processed:
Longevity Milestone:                             10,400.0
Employee CSS before payroll:               10,320.0
Hours needed to reach milestone:                80.0
 
MVA:  Regular 80 hours for prior pay period ending 2/21/10.  CSS hours after MVA = 10,400.0
 
Regular Time Sheet:
Week 1
Sunday - 3/7
Monday - 3/8
Tuesday - 3/9
Wednesday - 3/10
Thursday - 3/11
Friday - 3/12
Saturday - 3/13
 
 
8.0
8.0
8.0
8.0
8.0
 
                       
 
Week 2
Sunday - 3/14
Monday - 3/15
Tuesday - 3/16
Wednesday - 3/17
Thursday - 3/18
Friday - 3/19
Saturday - 3/20
 
 
8.0
8.0
8.0
8.0
8.0
 
CL - Longevity would generate effective Monday, 3/8, of week 1 because that is the first day hours are reported in the current pay period.
 
Example of longevity milestone reached when multiple MVA's are processed:
Longevity Milestone:                             10.400.0
Employee CSS before payroll:               10,360.0
Hours needed for milestone:                        40.0
 
MVA:  Regular 80 hours for prior pay period ending 1/23/10.  CSS hours after MVA = 10440.0.  Effective date on MVA is 3/22/10.
MVA:  Regular 80 hours for prior pay period ending 2/6/10.  CSS hours after MVA = 10520.0.  Effective date on MVA is 3/24/10.
 
CL longevity would generate effective 3/24/10.  Employee reached milestone on MVA for pay period ending 1/23/10, but the 'CL' would generate with the effective date of last MVA processed.
 
Note: If a 'CL' is generated with a prior pay period effective date, it may be necessary for the agency to review the employee's record to ensure accurate vacation accruals occurred and the balance is correct.
 
Example of longevity milestone reached when overtime is worked:
Longevity Milestone:                             20,800.0
Employee CSS before payroll:   20.719.0
Hours needed for milestone:              81.0

When a CSS milestone is reached in a pay period where overtime is worked, the overtime hours will be added to the first day of the week the overtime hours occurred.  Five hours of overtime occurred in week two. The nine hours on Friday, 3/18, are reduced by five hours and moved to Sunday, 3/14, as five OTS. The hours for the week are then added up to determine when the longevity milestone is reached.
 
Week 1
Sunday - 3/7
Monday - 3/8
Tuesday - 3/9
Wednesday - 3/10
Thursday - 3/11
Friday - 3/12
Saturday - 3/13
Hours Worked
 
8.0
8.0
8.0
8.0
8.0
 
CSS Hours by Day
20,719.0
20,727.0
20,735.0
20,743.0
20,751.0
20,759.0
 
                       
 
Week 2
Sunday - 3/14
Monday- 3/15
Tuesday - 3/16
Wednesday - 3/16
Thursday - 3/17
Friday - 3/18
Saturday - 3/19
Hours Worked
 
9.0
9.0
9.0
9.0
9.0
 
Adjusted Hours
OTS - 5.0
9.0
9.0
9.0
9.0
4.0
 
CSS Hours by Day
20,764.0
20,773.0
20,782.0
20,791.0
20,800.0
20,804.0
 
CL - Longevity would generate effective Thursday, 3/17.