Issue

When pay codes with include "Super" flag set as No are processed in the special pay, pay code FESUPE is populated in the special pay.

Business Scenario

1. A company pays overtime and meal allowance to employees as part of a special pay.
2. Certain employees have employee additional Super (FESUPE) set to be deducted by value. This is set in employee deductions menu.
3. Some employees are paid overtime and meal while others are only paid meal allowances. When pay is processed for these employees the FESUPE pay code is also added to the current pay.
4. Payroll personnel does a pay verify so that PAYE and XXXXX calculations are accurately calculated for those employees who are paid overtime.
5. Now if employee is paid EMEAL of $50 only and FESUPE is set as $150, the net pay for this employee becomes -$100.
6. Current workaround given is to put this deduction on hold before making special pay, however due to the number of employees, this will cause issues if payroll personnel forgets to mark as active after processing the special pay.
7. FESUPE added to the pay is not removed from "Mass Pay Code Processing". 

1. All deductions setup on menu 324, should flow into the normal pay only.
2. Paying allowances with "Include Super" as "No" should not accommodate for FESUPE deduction. This should be treated as a fixed deduction.

Steps to Replicate

1. There is a pay code as EMEAL which has the following characteristic: [Refer to Figure 1.1]
   1. Classification: Non – Taxable Allowance
   2. Includes Super – NO
2. Add the following deductions to an employee:
   1. FESUPE
   2. FDD
3. Create Special Pay for that employee E069 using menu: 334-1
4. Using menu: Edit  Manual Pay 334-2:
   1. Add “EMEAL” to the employee
   2. Hours\Quantity = 1
   3. Save
5. Open menu: 332-3: [Refer to Figure 1.2] 

1. Click on save
2. The screen adds “FESUPE” to this employee.

[Refer to Figure 1.1]

[Refer to Figure 1.2]

Hi Alvis, 

I have verified the case in 9.2.4, issue remains the same.

The following scenario breaks in Link Payroll.

1. Create a paycode as "EALLO" [Refer to Figure 1.1]
   1. Classification: Non – Taxable Allowance
   2. Includes Super – NO
2. Add the following deductions to an employee:
   1. FESUPE - $100.00 every pay.
   2. FDD - $20.00
3. Create Manual Pay for that employee E013 using menu: 334-1
4. Using menu: Edit  Manual Pay 334-2:
   1. Add “EALLO” to the employee
   2. Hours\Quantity = 1
   3. Save
5. Open menu: 332-3: [Refer to Figure 1.2] 
6. Click on save
7. The screen adds “FESUPE” to this employee.

• FESUPE is the excess FNPF deduction. FNPF is not enabled on EALLO.
• No other deduction paycode was added.

• Database - LINKSOFT
• Server - QA1

Hi Rashna,

The workaround is to edit the deduction entry and mark it as hold, then process special pay, then un-hold deductions.

We have agreed to make the following changes in version 9.4:

1. There are 4 types of pay, Normal, Special, Termination, Non-pay week. Each of these has several decisions that are currently not configurable.

The following decisions will be applicable for each pay type:

1. Include Timesheet entries
2. Include Standard Pay
3. Include Allowances from allowance screen
4. Include Deductions from deduction screen
5. Include Benefits from benefit screen
6. Include Leave Transactions - Taken
7. Include Leave Transactions - Sold
8. Include final pay entries. creates leave balance payout, leave accrual payout, marks the employee as terminated after pay update.
9. Create Normal Hours with zero quantity
10. Include ESS time entries
11. Include Achievement payments
12. Include "Auto Reduct Hours for Contract Expiry"
13. Include shift allowances
14. include leave loading
15. Include "Missing Time Entry Paycode". Changes pay method from "Direct" to "Cash" when employees have missing time on payday. Exceptions for an employee's having "Missing Time Paycode" which overrides the rule. Reverts payment method to "Direct" after pay update.
16. Include customizations
17. Calculate Super - Compulsory
18. Calculate Super - Excess
19. Calculate Tax
20. Send Deductions over threshold alert
21. Send super not deducted alert
22. Send verification checks alert
23. Close pay: update next pay details
24. Send pay update alert to all employees
25. Process leave accruals/rollover
26. Automatically terminate an employee on contract expiry and send contract expired alert

Regards
Alvis

Development has agreed to perform the following changes in version 9.4:

1. Create a Transaction Rule menu
2. Add "Payroll ~> PayrunType" as a Transaction Rule
3. Add a list of Payrun Types
4. Add a sub-grid to define rules

Proceed with Design and build in version 9.4

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

1. Created new menu for "FR061 - Transaction Rules" URL: /Framework/TransactionRule.aspx
2. Created maintenance tables "LT_SYS_TransactionCode, LT_SYS_TransactionCodeDetail, LT_SYS_TransactionCodeDetailRule"
3. Created Select, insert and update procedures for above tables
4. Created Transaction Code build script for Payrun type.
5. Changed back-office "Create Pay and Create Manual Pay" screen for "Payrun type" lookup to view from "LT_SYS_TransactionCode -> PAY.PayrunType"
6. Changed "Pay create process" to use pay run type rules defined in 4. above.
7. Changed "Pay update process" to use pay run type rules defined in 4. above.

Assigned to Sanjay to create maintenance form in ESS for TransactionRule.

System Test completed.

The following were tested:

1. New configuration menu in the Web framework, tested the edit of the record.
2. Tested each configuration rule for Payroll Processing -> Payrun Types

System test completed.

Verified the following:

1. Enabled Leave Loading Flag "Include Leave Loading"
2. Configured an employee to receive leave loading
3. Created Leave transaction
4. Created pay and verified leave loading entries - pass

Regards
Alvis

Hi Alvis, 

This case has been successfully tested.

Documentation on the case has been updated.

• ESS-- Administration -- Configuration

Test Environment

• Version 9400 Beta 2
• Database - LINKSOFT on QA1
• Application on QA1
• OS - Windows 7

Test Plan

System Test completed.

The following were tested:

1. New configuration menu in the Web framework, tested the edit of the record.
2. Tested each configuration rule for Payroll Processing -> Payrun Types

Thanks

Rashna

Hi Rashna,

We have put in more details in the configuration description. Please review and update documentation.

regards
Alvis

System test completed.

Verified the "Payroll Processing -> Payrun Type" configuration description has been changed to include more details.

Test Environment

• Version 9400 Beta 3
• Database - LINKSOFT on QA1. Demo Database.
• Application on QA1
• OS - Windows 7.