Undo Payroll

Not every payroll job needs to be undone and re-run when the Distribute and Pay Payroll job failed. Sometimes the problem can be remedied by running separate jobs after PYPADP. For instance, if only the GL Posting portion of the Distribute and Pay Payroll process failed but everything else looks correct, the issue can be resolved by undoing the GL and then reposting to the GL.  The following sections discuss several common scenarios in which Payroll may fail and the steps needed to remedy the issue.

Important Note: Payroll setup is unique for every client site. Therefore, the reason for a payroll process to fail can be unique for every client. The steps outlined in the next sections are to be viewed as general guidelines. PowerSchool recommends contacting BusinessPlus Support for any questions regarding a failed payroll, so that the client-specific setup can be reviewed, and a recommendation may be given on how to proceed.

Employee Paid History Has Both WP and DP Records

1. Confirm Employee Paid History (PYUPPH) has both WP and DP records.
2. Determine the issue that caused the program to not process all records as Distributed Paid (DP).
3. Run PYUTUX, the Undo job for both Payroll and GL. Enter the PYPADP job number in the "Job Number to be purged" field. PYUTUX automatically clears the subledger table for the pay period, if transactions exist.
4. Undo BK by running BKUTPU. Select CHK (Checks) as the Transaction Type to purge. Use the selection criteria to enter the failed PYPADP job number.
5. Recompute employee accumulators (PYUTRA).
6. Correct the issue that caused the payroll to fail, run Force Calc and Prelist to confirm there are no errors.
7. Re-run PYPADP.

BK Failed

To check how many records were updated in BK, open the BK Update Check/Deposit Info (BKUPCD) page, search by the PYPADP job number to retrieve EF and PY records associated with this payroll. The total number of records must match the number of records found in Employee Paid History (PYUPPH) for the same pay period. If the numbers do not match, there was an issue posting to BK.

Duplicate Check Numbers

If BK failed because the program found duplicate check numbers during the PYPADP process, resulting in some records already inserted into the BK database, while other are missing:

1. Correct the duplicate check number issue.
2. Purge BK by running BKUTPU. Select CHK (Checks) as the Transaction Type to purge. Use the selection criteria to enter the PYPADP job number.
3. Run PYUTRFNE or PYUTRFOR to reprint checks.

Printer Paper Jam

It is not uncommon for paper to get jammed in a printer, resulting in only a portion of the checks to be printed. In that case, the update to BK did not fail, just the printing portion. No updates to the BK are needed. After the paper jam is cleared, a Quick Reprint (PYUTQR) can be run to print the remainder of the checks. The PYUTQR job prints from the spool file, so no updates to the BK database are made.

GL Failed

Check the Employee history, BK, Subledger, EO stubs to determine if only the GL failed. If so, follow these steps:

1. Undo GL by running GLUTSUUN. Enter the job number of the failed PYPADP job. GLUTSUUN automatically clears the subledger table for the pay period, if transactions exist.
2. Run PYPARN to repost to GL. Common code PYFG/PY560C is referenced during this process.

EFT File Was Not Created

1. Determine no other issues occurred during the payroll run.
2. Run the EFT Tape and Report (PYREPAEF) process to recreate the EFT file. The file is saved to the admin/data directory on the App server.

Nothing Posted to the Subledger

1. Determine the issue that caused the program to not post to the Subledger.
2. Run PYUTUX, the Undo job for both Payroll and GL. Enter the PYPADP job number in the "Job Number to be purged" field.
3. Undo BK by running BKUTPU. Select CHK (Checks) as the Transaction Type to purge. Use the selection criteria to enter the failed PYPADP job number.
4. Recompute employee accumulators (PYUTRA).
5. Correct the issue, run Force Calc and Prelist to confirm there are no errors.
6. Re-run PYPADP.

Payroll Failed

Whether payroll fails on just one person or several persons:

1. Run PYUTUX, the Undo job for both Payroll and GL. Enter the PYPADP job number in the "Job Number to be purged" field. PYUTUX automatically clears the subledger table for the pay period, if transactions exist.
2. Undo BK by running BKUTPU. Select CHK (Checks) as the Transaction Type to purge. Use the selection criteria to enter the failed PYPADP job number.
3. Correct the data that caused the payroll to fail.
4. Run Force Calc (PYPAFC) and Prelist (PYREEL) to confirm there are no errors.
5. Rerun PYPADP.