Compensation Syncing Between Bob and Payroll
Compensation updates in Bob only sync to payroll when the effective date aligns with the payroll system’s active pay period. If the timing does not match, the new rate may appear in the employee’s profile but not in payroll.
Two timing rules commonly cause this behavior.
Mid-cycle effective dates do not apply to the current pay period
If a compensation change becomes effective after the start of a pay period, it will not apply to that payroll run.
Example
Pay period: Feb 1 to Feb 15
Compensation change effective date: Feb 10
Since the effective date occurs after the pay period started, the updated rate will not sync to the Feb 1 to Feb 15 payroll. Instead, it will apply to the next pay cycle that begins after the effective date.
Backdated compensation changes do not sync once the system moves into a new active pay period
The payroll system determines eligibility based on the active pay period, which is the pay period that today’s date falls within, not the payroll cycle that is currently being processed.
This means a previous pay period may still be open for processing, but the system already considers it closed for compensation syncing.
Example
Pay period being processed: Jan 1 to Jan 15
Today’s date: Jan 17
Active pay period: Jan 16 to Jan 31
If a compensation change is entered on Jan 17 with an effective date of Jan 10, the system treats this as a backdated change because Jan 10 belongs to a prior pay period. The change will not sync to payroll, even if the Jan 1 to Jan 15 payroll is still being processed.
How to ensure compensation changes sync correctly
To avoid payroll sync issues:
Use an effective date that aligns with the start of the pay period.
Enter compensation updates during the pay period they belong to, not after the system has moved into the next active period.
Avoid using effective dates that fall in prior pay periods.
How to resolve compensation sync issues
The correct solution depends on whether the payroll cycle you are trying to update is still within the system’s active pay period.
In this context, active refers to the pay period that today’s date falls within, not simply a payroll that is still being processed.
Example
Payroll being processed: Jan 1 to Jan 15
Today’s date: Jan 17
Even if the Jan 1 to Jan 15 payroll has not been submitted yet, the system considers it closed for compensation syncing because today’s date falls in the Jan 16 to Jan 31 pay period, which is now the active period.
If the payroll cycle is still within the active pay period
Update the compensation effective date so it aligns with the beginning of that pay period.
The updated rate should then sync to payroll.
If the payroll cycle is no longer the active pay period
Add the missed amount as additional wages in Step 1 of the next payroll cycle to reconcile the difference.
Update the employee’s compensation by creating a new row with an effective date that aligns with the next pay period, so the correct rate syncs going forward.
If the discrepancy is discovered after payroll has already been finalized, an off-cycle payment can be issued to ensure the employee is paid correctly.
Why a Compensation Change in Bob Core Doesn’t Sync to US Payroll
Compensation updates in Bob only sync to payroll when the entry method and effective date align with the payroll system’s active pay period. If the timing does not match, or if the incorrect entry method is used, the new rate may appear in the employee’s profile but will not flow correctly into the payroll module.
Three core factors commonly cause this discrepancy
1. Entry Method: Updating Existing Record vs. Creating New Line
The way a change is entered determines how the sync is triggered:
Creating a New Comp Line (Recommended): This is the required method for standard pay changes. The system uses the new effective date to determine which pay period the rate belongs to.
Updating an Existing Record: If you edit an existing compensation object instead of creating a new row, the system may force an immediate sync of that data. This can cause future-dated rates to "overwrite" the current payroll prematurely, or cause backdated changes to sync incorrectly because the system is not processing it as a new event.
2. Mid-cycle effective dates do not apply to the current pay period
If a compensation change becomes effective after the start of a pay period, it will not apply to that specific payroll run.
Example:
Pay period: Feb 1 to Feb 15
Compensation change effective date: Feb 10
Since the effective date occurs after the pay period started, the updated rate will not sync to the Feb 1 to Feb 15 payroll. Instead, it will apply to the next pay cycle that begins after the effective date.
3. Backdated compensation changes do not sync once the system moves into a new active pay period
The payroll system determines eligibility based on the active pay period, which is the pay period that today’s date falls within, not the payroll cycle that is currently being processed. This means a previous pay period may still be open for processing, but the system already considers it closed for compensation syncing.
Example:
Pay period being processed: Jan 1 to Jan 15
Today’s date: Jan 17
Active pay period: Jan 16 to Jan 31
If a compensation change is entered on Jan 17 with an effective date of Jan 1, the system treats this as a backdated change because Jan 1 belongs to a prior pay period. The change will not sync to payroll, even if the Jan 1 to Jan 15 payroll is still being processed.
How to ensure compensation changes sync correctly
To avoid payroll sync issues:
-Always use the "Add Row" function to create a new compensation line rather than editing an existing one.
-Use an effective date that aligns with the start of the pay period.
-Enter compensation updates during the pay period they belong to, not after the system has moved into the next active period.
-Avoid using effective dates that fall in prior pay periods.
How to resolve compensation sync issues
The correct solution depends on whether the payroll cycle you are trying to update is still within the system’s active pay period (the period today's date falls within).
If the payroll cycle is still within the active pay period:
Update the compensation by adding a new row with an effective date that aligns with the beginning of that pay period. The updated rate should then sync to payroll.
If the payroll cycle is no longer the active pay period:
Manual Reconciliation: Add the missed amount as additional wages or a correction payment in Step 1 of the next payroll cycle to reconcile the difference.
Forward-Facing Correction: Update the employee’s compensation by creating a new row with an effective date that aligns with the start of next (active)pay period, so the correct rate syncs going forward.
Off-cycle Payment: If the discrepancy is discovered after payroll has already been finalized, an off-cycle payment can be issued to ensure the employee is paid correctly.
Note: We are currently having discussions internally about how to loosen the restrictions around when compensation changes can be entered to provide more flexibility for our users.