Bula Team,

We connected via Teams with ATH HR and rectified the following in their Azure Database.

Ran the following reports:

Leave Balances (summary) Report 

1. Double AAL limes are reflected as leave balances were zeroed out and allocated again in the same leave year. 
2. Accrual amounts are also doubled.

Leave Liability Analysis - Detail

1. Cannot understand how the figures are reflected as Taken and Accruals, both figures show in negative.

Both reports are throwing incorrect data from an employee.

Next Steps:

Analyse the data with the development team. 

Sitla.

This issue was replicated in Edge Demo - 

1. https://linktechnologies.com.au/DEMO-LinkSOFT-EDGE 
2. Company 1006
3. EmP ID -LTE00001

Mismatch in Data in both reports. The above scenarios were replicated in the Demo.

Sitla.

Hi Sanjay

Below steps were taken to replicate the issue.

1. Leave Code AAL was removed from employee LTE00001 by passing out the adjustment to reduce the balance to zero.
2. Under the Current Leave Allocation Menu, the leave was marked void.
3. Reallocated the same Leave code AAL with a balance brought forward of 80 hours.
4. Created payrun 539 and 540 to bring in accruals for test results.
5. Ran Report-"Leave Balance (Summary)", Double Lines for AAL appear with incorrect accruals as well.

Let me know if we need to discuss this further.
Sitla.

Teams Discussion - Sitla and Sanjay

1. Leave Summary Report for employee: LTE00001 isw picking up two AAL. Seems like the VOID entry is also picking up
2. This issue was resolved in the Leave Liability Report

Can we have the same logic applied to the following reports:

1. Leave Balances (summary) Report
2. Leave Liability Analysis - Summary
3. Leave Liability Analysis - Detail
   

Hi Sanjay,

Ran all three reports with the following parameters

Date From: 01.1.2025
Date To: 31.8.2025
Company 1006

The result shows double the value of the leave balance. Therefore, all need to have the same logic as discussed in comment 3.

Sitla.

1. The change will be available in version: 15.70

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

1. Changed the following reports to exclude Employee Leave that has been VOID

1. Leave Balances (summary) Report
2. Leave Liability Analysis - Summary
3. Leave Liability Analysis - Detail

3. Affected Areas:

1. Leave reports in 2. above

4. The issue was caused by:

1. Handle VOID leave on Employee Leave Allocation

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

Hi Sanjay,

I reran the reports for the employee mentioned in Comment 3, and the results are as per below.

1. The current allocation screen has
   1. 10.6667 Days in AAL
   2. 10 Days in ASL
   3. 3 Days in L13128 (Berreavement)
2. Reports Reflect

   Reports	Balance
   	AAL	SL	L13128
   1. Leave Balances (summary) Report	0	40	0
   2. Leave Liability Analysis - Summary	0	40	0
   3. Leave Liability Analysis - Detail	0	40	0
   4. Leave Liability Report -	2.5 - (-0.83+3.33)	40	0

3. Failed 
   

Hi Sitla, the reason your results are different is that the dates you used do not align with the Leave Start/End date.

Your leave Allocation Date for AAL is: 01/07/2025 to 30/06/2026, therefore, If you run the report within this range, the results will match.

This is how the report was initially designed.  If you need  this changed, we will need a set of  rules with test case.

For this case, the change was to exclude VOID leave codes in the report numbers.

Next step: Verify this report by checking the Report using Leave Start and END dates and confirming that VOID leave is not picking up.

Hi Sanjay,

All balances are accurate after running the reports as designed.

Case Passed.
Sitla