1. Created Employee
   

   Emp Code	Start Date
   GAL001	01/01/2021
   GAL002	01/01/2021
   GAL003	01/07/2021

   
   
2. Grade Setup
   

   Row	Leave	Privilege	Minimum Service (yrs)	Employment Start Between
   1	Annual Leave [AL1]	120	0	01/01/2000 - 31/12/2100
   2	Annual Leave [AL2]	150	1	01/01/2000 - 31/12/2100
   3	Annual Leave [AL3]	180	2	01/01/2000 - 31/12/2100

1. URL: https://linktechnologies.com.au/DEMO-LinkSOFT-EDGE
2. Company: 1003
3. Version: 15.51.250130.GA

Regards
Vineshwar Prasad

Problem Statement:

1. For all three employees, AL1 was not allocated on the first pay. Note that "Min Service Year" is zero, therefore, this should have been allocated on the first pay.
2. For Employee GAL003, the following issues were identified:
   1. Pay # 1, 31/01/2022 - AL1 was allocated. This is incorrect as it should have been allocated in the first pay for the employee
   2. Pay # 7 on 31/07/2022, AL2 was not allocated. This is the 1st anniversary

Sitla Note: In version 14, Grade Leave was correctly allocated to the employee on the anniversary, i,e, Problem 2.2 was not an issue in V14

Next Step: Sitla to get Mind Pearl DB which is V14 for us to investigate the issue.

Hi Sanjay,

Tested with the below setup to see Rollover:

1. Company ID: 1002
2. Employee ID: GL0015

Table 3 - Grade Setup - Leave Annual 10

Table4: Tested Resuts

1. The change will be available in version: 15.60 and 15.51.250215

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

1. Corrected Leave Allocation for "Grade Based Entitlements" when Grade Leave is set to rollover at Anniversary.

3. Affected Areas:

1. Period Close and Period End Process in Payroll

4. The issue was caused by:

1. Anniversary based leave in Grade Entitlements we no rolling over correctly when the Rollover method was set to "Anniversary"

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

PART B - Development Reference (Place descriptor for objects changed):

1. The change will be available in version: 15.60 and 15.51.250215

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

1. Corrected the issue by allocating "Grade Entitlements" when the Employee "Service Years" exceeds the configured value. i.e. in the example above, the Grade leave will be allocated when September is Closed, instead of August Close

3. Affected Areas:

1. Grade Leave Allocation

4. The issue was caused by:

1. Change in allocation parameters

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

1. The change will be available in versions: 15.60 and 15.51.250220

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

1. Changed Accrual calculations to the following Formula: Accrual = "Leave Days" * (Number of days in Pay)/Number of days in Leave Year)
   1. This calculation ensures that employees leave is allocated based on Pay Days instead of Months Worked.  Both methods add up to the correct total, however, the new method is also accurate month by month.
   2. This calculation also accounts for the extra day in a Leap Years
2. You can Approve a pay without submitting. If you have access, the system will automatically submit
3. Changed the order of Leave "Allocation History Details" so that the Order is: DATE, Brought Forward, Allocation, Accrual
4. Changed Order of Leave Allocation History so we see the leave in Order of LEAVE CODE, then "FOR Year"
5. Removed "Totals" from "Allocation History Details" as we cannot add Multiple Leave Types together

3. Affected Areas:

1. Leave Accruals
2. Leave Allocation
3. Pay Close
4. Month Rollover
5. Year Rollover

4. The issue was caused by:

1. Improvement and corrections to Pay Allocation and Accruals

5. Other Relevant Notes: 

1. Changes applied to DEMO and "Clients Training Environments" on LINKAD

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