This page (revision-8) was last changed on 26-Nov-2021 10:22 by mhodgins

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
8 26-Nov-2021 10:22 1 KB mhodgins to previous
7 26-Nov-2021 10:22 1 KB jmyers to previous | to last
6 26-Nov-2021 10:22 1 KB jmyers to previous | to last
5 26-Nov-2021 10:22 1 KB jmyers to previous | to last
4 26-Nov-2021 10:22 1 KB jmyers to previous | to last
3 26-Nov-2021 10:22 1 KB jmyers to previous | to last
2 26-Nov-2021 10:22 1 KB jmyers to previous | to last
1 26-Nov-2021 10:22 1 KB jmyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 4 changed one line
There may be times where employees who have been terminated will require Sundry payments to be made. In order for this to happen pay headers will need to be created. We do not want to have to select the specific employees to pay nor do we want to have to create the batch in IBPE and manually add the employees into the pay header. UPCPAY has been modified to allow this to happen automatically.
There may be times where employees who have been terminated will require Sundry payments to be made. In order for this to happen, pay headers will need to be created. We do not want to have to select the specific employees to pay nor do we want to have to create the batch in [IPBE] and manually add the employees into the pay header. For this reason, [UPCPAY] has been modified to allow automatic Sundry payments to terminated employees.\\
At line 6 changed one line
In order for UPCPAY to handle this an element must be created that will contain the pay components that require payment.
In order for UPCPAY to handle this, an element must be created that will contain the pay components that require payment.\\
At line 8 changed 6 lines
In this example an element called TERM_SUNDRIES has been created which contains PC2011. Any additional Pay Components that could be paid to a terminated employee would need to be listed here as well.\\ \\
[PAYING TERMINATED EMPLOYEE SUNDRIES_01.PNG]\\ \\
The employee’s record in IPSN (Sundry) must either be a one time or must encompass the date that the UPCPAY program is run for.\\ \\
UPCPAY will be run as follows:\\ \\
[PAYING TERMINATED EMPLOYEE SUNDRIES_01.PNG]\\ \\
The Incl Prior Terminations would be set to <<Yes>>. The Terminated Sundry would be set to the element that contains the pay components used to define when terminated employees to select. The status under Report Filters MUST be set to Terminated employees otherwise all employees will be picked up.
In this example, an element called TERM_SUNDRIES has been created which contains PC2011. Any additional pay components that could be paid to a terminated employee would need to be listed here as well.\\ \\
At line 10 added one line
The employee’s record on the Maintain Sundry [IPSN] form must either be set to a One Time frequency, or must encompass the date that the UPCPAY program is run for.\\ \\
At line 12 added 9 lines
For the UPCPAY run:
*The Incl Prior Terminations field will be set to <<Yes>>.
*The Terminated Sundry field will be set to the element that contains the pay components used to define which terminated employees to select.
*Under Report Filters, the Status field MUST be set to 'Terminated', otherwise all employees will be picked up.
----
![Notes|Edit:Internal.PAYING TERMINATED EMPLOYEE SUNDRIES]
[{InsertPage page='Internal.PAYING TERMINATED EMPLOYEE SUNDRIES' default='Click to create a new notes page'}]