Topics Map > PD LEARNING PATH > PY Learning Path
Topics Map > DOCUMENT TYPE > Reference
Topics Map > FUNCTIONAL AREA > Payroll (PY)
PY - Payroll Calculation and Confirmation Processes - On-Cycle
Calculating and finalizing checks in HRS is a Payroll operational function involving manual and automatic processes that are internal to the UW Service Center. HRS - Payroll is a system that determines earnings, deductions, taxes, and net pay for all employees who have pay earnings in the specified pay period. On average, each pay period (2 biweekly and 1 monthly) processes about 40,000 paychecks.
There are several preliminary operational tasks that are conducted by all UW Service Center staff to ensure the correctness of the paychecks which include payline adjustments and error resolutions.
The payroll process consists of preliminary batch jobs (compiled coding) that are 4-5 nights in a payroll processing week. On the final day of the payroll, usually Thursday, there are final calculation, confirmation, and post confirm jobs that are run. The Payroll team utilizes the payroll query checklist to resolve any outstanding errors that arise. Once the final calculation process has completed without any errors, the confirmation process can begin. Confirmation finalizes the calculated paycheck, so employees receive either a direct deposit or paper check. Once the payroll has confirmed, there are a series of post-confirm jobs that are run primarily for reports.
Nearly all of these jobs are executed by a batch processing tool, which include reports that campuses receive on those employees paid and the prenote files for direct deposit data to US Bank.
- This KB is informational only as the processes are largely automated and any manual manipulations are restricted to UW Service Center payroll staff. During the final calc and confirm processes (typically Thursday afternoons), refraining from job data changes reduces the risks of process failures.
Preliminary Operational Tasks
During the payroll week UW Service Center staff will enter in deductions, leave payouts, and other adjustments to the pay periods as well as fix exceptions, omissions, and errors (pay, benefits, leave, time and labor). Below is a typical week of tasks per day.
Monday – Thursday: Payroll staff will check the calculation errors from the previous night’s preliminary process and emails the spreadsheet to Service Center operational staff (HR, BN, etc.). Payroll staff will check the log files for the “orphan” process from the previous night to see if there are any anomalies that need to be fixed (e.g. blank department ID).
Tuesday: The deadline for campuses to submit requests (via WiscIts) to add paylines to the pay period is 4:30 pm. Payroll staff will initiate the HRS mass payline upload but this will only load in active employee data. Terminated employee paylines are manually entered into new paylines by payroll staff by the end of day on Wednesday.
Wednesday: FICA processing is initiated in HRS in the late afternoon after campuses submit their spreadsheets.
Thursday: Several audits are run in the morning before the noon deadline for final calculation and confirm.
Every night for Payroll, there are 3 jobs scheduled for prenote (direct deposit data), retro payments, and work study data.
Preliminary Payroll Processes
There are two different streams of job processes for the biweekly paid and the monthly paid employees. There are similarities but also important differences between the two.
Biweekly Preliminary Payroll
Biweekly job processes that precede the final calculation and confirmation day of processes usually begin on the Sunday night of the payroll week through Wednesday (with the final on Thursday). Key data for biweekly employees is the data from time and labor.
Sunday: The nightly processes load in Absence data into the Time and Labor data before the Payroll jobs start. The first job loads in the data from Time and Labor and creates paysheets. Subsequently, benefits prepay data and deductions load into the paysheets followed by a preliminary payroll calc which calculated the pay check for the employees. Two reports are generated, the payroll edit report and the payroll error message report.
Monday: The first job loads in custom paylines from the campuses onto the paysheets, then there is the time and labor load into paysheets (and creating any new ones_ followed by deductions, then payline adjustments for pay or deductions, and then the preliminary calc and reports as above.
Tuesday: This is a big night of processing as paylines are uploaded from payline requests to the Service Center, overtime, retro, and benefits prepay and retro deductions.
Wednesday: This night mirrors Monday night's create and load paysheets that are not already created, deductions, and a preliminary calc and reports.
Monthly Preliminary Payroll
Monthly job processes that precede the final calc and confirmation day of processes usually begin on a Friday night, skip Saturday night, and continue Sunday through Wednesday nights. Key data for monthly employees is the absence management data.
Friday: The first process creates paysheets for the pay period for active employees. Absence takes and deductions are loaded into the paysheets followed by a payroll preliminary calculation and the reports, payroll edit and payroll errors.
Like the preliminary payroll processes, the final calculation and confirmation is similar for the biweekly and monthly paid employees but there are key differences. Both types are manually monitored and run by the Service Center payroll staff usually at noon on Thursdays. The monthly final calc and confirm payroll week is usually between the two biweekly weeks. Exceptions are in the Payroll Calendar.
The first process loads all employees' time to payroll.The 11 am Time Admin jobs need to finish first. Time and Labor and Absence then check their entries after which Payroll runs the first preliminary calculation. If there are no errors or modifications needed, the payroll team continues the remainder of the process for deductions, earning code swaps, another preliminary calculation and then, if there are no errors, proceeds with the final calculation process and the final confirmation process.
Automated, post confirmation jobs follow the final confirmation.These are primarily reports, some of which are sent to Cypress. Two of the more important post confirm jobs are the earnings extract which populates the Earnings Statement and the Bank Files.
The first process loads all employees' absence takes for the month of the payroll followed by a preliminary calculation. If there are no errors or modifications, then deductions, earning code swap, and another preliminary calc is run. If there are no other errors, then the payroll team proceeds with the final calculation process and the final confirmation process.
Automated post confirm jobs follow the final confirmation. These are primarily reports, some of which are sent to Cypress. Two of the more important post confirm jobs are the earnings extract which populates the Earnings Statement and the Bank Files.