Benefit Board Amounts dropping off Pay Register Fix

Benefit Board Amounts dropping off Pay Register Fix

GOAL: To provide a wholistic overview of why Benefit BRD Amounts might be dropping off the Pay Register, especially around the time a Position has been End Dated. 

ISSUE: 

STAFFING > STAFF MANAGEMENT > EID

**EID has had Position End Dated** 

Note: Entitlement and Group Authorization were then completed before the pay run. 

PAYROLL > PAY PROCESS > SCHEDULE GROUPS > TEACH > PAY RUN

**Pay Run processed** 

REPORTS > PROCESS REPORTS > PAY REGISTER > EID

**Benefit BRD Amounts have dropped off**

ROOT CAUSE: 

When the Position was End Dated, the Primary Group was updated FROM TEACH back TO TSUB – before the Pay Run was completed. 

IMPORTANT NOTE: The issue here is that the Primary Group drives the Benefit configuration, and this change takes immediate effect. 

**If this is completed BEFORE the Pay Run is completed, then Benefits will drop off as TSUB has no Benefits configured – and the Primary Group is no longer TEACH**

STAFFING > STAFF MANAGEMENT > EID > EMPLOYEE INFORMATION > EMPLOYMENT

**Update Primary Employee group back to TEACH until Pay Run is COMPLETE**

Note: This field, although it needs to be updated, should be changed AFTER the pay run to ensure Benefits still deduct from the Final Pay Period. 

PAYROLL > PAY PROCESS > ENTITLEMENT > TEACH > GROUP AUTHORIZATION > TEACH

**Processes Completed** 

PAYROLL > PAY PROCESS > SCHEDULE GROUPS > PAY RUN

**Process Completed**

REPORTS > PROCESS REPORTS > PAY REGISTER > EID

**Benefit BRD Amounts have now returned**

IMPORTANT NOTE: Once this pay is Processed > Confirmed then the user can update the Primary Employee Group back to TSUB as the TEACH position is now closed. 

Best Practice: 

Due to the way HRP is set up and designed to run, having to defer until AFTER the Pay Run to update the Employee Primary Group is the recommended practice to handle this situation to ensure Benefit BRD amounts continue to deduct across the final Pay Run. 

**This has been raised in the past and discussed among the Product committee, however this approach is the “lesser of two evils” as the alternative requires more manual intervention than deferring this one simple field to be updated after the pay run**