Skip to main content

Employee balance not appearing as expected after adding a new floating entitlement code

Employees balances incorrect after application of new Floating Entitlement Codes.

J
Written by James Pardy
Updated over 4 months ago

If an employee’s balance isn’t displaying as expected after assigning a Floating Entitlement Code, it’s usually because the wrong code has been attached.

This article explains how to fix the issue.


Why this happens

The most common cause is an invalid floating entitlement code attached to the employee’s balance.


Remove the invalid floating entitlement code

  1. Go to CoreTime.

  2. Click Pers. Data > Person Maintenance.

  3. Select Current Balances.

  4. Click on the balance that isn’t showing as expected.

  5. Remove the Floating Entitlement Code.

  6. Click Save.


Decide how to correct the balance

What you do next depends on whether any new balances have been activated since the last Balance Period End.

If no new balances have been activated:

You can roll back and re-run the balance period.

  1. Go to CoreTime > System Parameters > Balances > Calendars.

  2. Untick the last Balance Period End checkbox.

  3. Click Save.

  4. Re-run the Balance Period End process.

⚠️Important: Rolling back the balance period will remove any new balances activated after the last period end.


If new balances have been activated:

Do not roll back the period. Instead, adjust the employee’s balance manually.


Check position-based entitlement settings (if applicable)

If your Floating Entitlement is based on Position History, check that the relevant parameters are enabled.

To check this in Back Office:

  1. Go to CoreTime.

  2. Select System Params > Balances.

  3. Click Parameters.

  4. Search for the relevant Annual Leave Balance.

  5. Click Advance Parameters.

  6. Make sure the following options are enabled:

    • Populate Position History details

    • Calculate Entitlement Based on Position History


Once complete, the employee’s balance should display correctly.

Did this answer your question?