The Leave Liability Report uses transactions to sum up the Leave Hours, which does not match with what is shown on the Leave Allocation screen.

An example from the standard DEMO environment is shown below:

Figure 1 - Leave Allocation Screen

Figure 2 - Leave Liability Report

1. The change will be available in version: 15.70 and 15.60.250322

2. The following changes were made (Include Database object names, Program classes, and any other relevant information):

1. Corrected Anniversary Leave Rollover to correctly adjust Rollover amount to next Year
2. Added validation so Leave Codes cannot be changed once they are used in transactions
3. Improved Narration on Leave Transactions so we can clearly see the Allocations, Entitlements, Brought Forwards and Accruals

3. Affected Areas:

1. Leave Processing

4. The issue was caused by:

1. Changes to Leave Codes after it has been used in pay processing is causing the leave amount to incorrectly reflect in the Leave Liability report

5. Other Relevant Notes: 
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT

Made the following changes in version 15.60.230323

1. Allow Leave Adjustments in prior periods so we can clear old Leave Balances
2. Show "Allocation", "Brought Forward", "Accrual" and "Taken" columns in the "Leave Allocation History Transactions" view. Menu: "Leave Management ~> Leave Allocation" Expand to "Leave Allocation History".

1. The change will be available in version: 15.61 and 15.60.250325

2. The following changes were made (Include Database object names, Program classes, and any other relevant information):

1. Cannot close a PERIOD if there are Pay Teams that have the "Next Pay date" before "Period End Date". This is to prevent Accidental Period Close.
2. We do not allow you to change the "Pay Control" to a closed period. This is the case of Leave Accrual Issues as the period is closed.
3. Grade Leave can be activated in Months instead of Years. to Activate in Months, set "Min Service Years" to N/12, where "N" is the number of months. i.e. 6 months = 6/12 = 0.5.

3. Affected Areas:

1. Leave Allocation, Period Close, Pay Control Update.

4. The issue was caused by:

1. Improvement and Bug Fixes

5. Other Relevant Notes: 
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT

UAT performed by Sanjay and Sitla. The following tests were performed:

1. Process multiple payments with Anniversary and Calendar types over multiple years and verify Accruals, Roll-over, Balance Calculations and verify with Leave Liability Report.
2. Check EDIT function on Leave Codes that have been allocated to employees
3. Check Period Close function where there are "Pay Teams" that have not been completed
4. Check Pay Control update to Closed Period

Testing Environment: LinkSOFT-DEMO-EDGE

A utility has been built to correct Leave Data. Below is the description of this utility. Please contact Link Support if you need details on how to use this utility:

1. Zero VOID Leave:
   1. If a Leave is marked as VOID, the Utility checks to see if the transaction History match the Leave allocation summary.
   2. If there is a mismatch, an entry is passed to "zero" the summary
   3. This results in all VOID Leave having Zero sum
2. Leave Allocation Rebuild:
   1. If there are any leave entries in the incorrect period, the leave entry is moved
   2. The summary value for "Brought Forward" is calculated using history
   3. The summary values for "Accrued" and "Taken" is recalculated and updated

To use this patch, you must be on version 15.61.250331 or later.

Before using this script, please apply to training environment and get USER SIGNOFF

Please NOTE: This script will change Leave allocation amounts and will not send integration entries.

Figure 1 -- Execute Statement --
DECLARE @UserID UNIQUEIDENTIFIER
SELECT @UserID = ID FROM LT_SYS_User_vw WHERE UserName = 'admin'