[PR] How to correct timecards when you need liabilities to calculate

Created by Crystal Ann Harvey, Modified on Fri, 29 Aug at 9:16 AM by Crystal Ann Harvey

What do I do if I posted time incorrectly and I need to move labor and burden?

NOTE: Print Payroll Register before you begin making changes.

 

If the Pay Period the Phase was posted in is Closed:

1.  Create two new sequences in PR Pay Period Control in the current pay period.  Example sequence 2 and 3. 

2.  In sequence 2 post the negative timecards lines with the wrong phase using the original date.  

    2a.  In PR Employee Sequence Control, process the employee.

    2b.  Check the earnings, deductions and liabilities matching with the original payroll register, only negative.

    2c. Pay with a manual check number below your normal check range. Example check number 100 

3.  In sequence 3 post the positive timecards lines with the correct phase using the original date.

    3a. In PR Employee Sequence Control, process the employee.

    3b. Check the earnings, deductions and liabilities matching with the original payroll register.

    3c. Pay with a manual check number below your normal check range. Example check number 101

You can check the PR Payroll Register report to make sure that sequence 2 and sequence 3 net to zero.

If the Pay Period the Phase was posted in is Open:

1. Create new Timecard Batch in Pay Period

2.  File > Add Timecards and enter criteria to bring the timecards back in.

3.  Change the originally posted Phase Code to the correct Phase.

4.  Process, Validate and Post the Batch

5.  In Payroll Process, Process Employees with Changes

6.  Check the earnings, deductions and liabilities. Make sure they match the original payroll register.

7.  Run PR Ledger Update, Validate and Post

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article