Pre-payroll validation for UKG Pro
UKG Pro's audit reports check data once it is in payroll. Pre-payroll validation checks it before, while a problem is still a line in a file.
Checks run on every input before import, while a problem is still a line in a file.
Works alongside UKG Pro's own audit reports, which check data already in payroll.
Every held line carries a reason, not just a flag.
UKG Pro gives payroll teams strong tools once data is in the system: pending item review, pre-calculation audit reports, and the register. What those tools cannot see is the data that never arrived, the file that came for the wrong period, or the line that was dropped because the employee sat in another pay group.
Pre-payroll validation covers that gap. PCLnXAI runs your checks on every input as it lands, before import, so the audit reports your team already uses have less to find. Our general pre-payroll validation guide explains the checks; this page covers how they apply on UKG Pro.
- Data already in payroll
- Pending items and pre-calculation audits
- The register after calculation
- Every input before import
- Missing, late, or wrong-period files
- Employees, pay groups, codes, duplicates
- Changes made in UKG Pro after the load
Checks that run before anything reaches UKG Pro
- Expected files. Every source for every pay group is listed in advance, and each is confirmed received, on time, and for the right pay period.
- Employees. Each employee number resolves in UKG Pro, sits in the pay group being processed, and has a status that allows the payment.
- Codes. Every pay code maps to a UKG Pro earning or deduction your configuration accepts, with the right hours, rate, or amount shape.
- Duplicates. No line has already been sent, including across a resent or revised file.
- Plausibility. Hours and amounts fall inside limits you set per location or pay group.
- Control totals. Totals about to post agree with each source system, location by location.
After import: checking UKG Pro against what was sent
Validation does not stop at the upload. After Bring in Time Imports and again after calculation, the system compares what UKG Pro holds with what was approved. A pending item that never reached the payroll, or a manual edit made directly in UKG Pro after the load, is found and recorded rather than discovered by an employee.
Validation with reasons, not just flags
A flag says something changed. A reason says why, and what to do. Every held line carries a plain-language explanation, such as "employee transferred to another pay group on the 12th" or "code has no hours mapping", so your analysts spend their time deciding, not investigating.
- 1Intake
- 2Validation
- 3Reconciliation
- 4Exceptions
- 5Approval
- 6Close
How PCLnXAI handles UKG Pro validation
We capture the checks your team already runs, by eye and by spreadsheet, and turn them into rules applied to every file. Tolerances are set per pay group. Results feed the approval screen your team uses to release each load.
Frequently asked questions
Is this different from UKG Pro's pre-payroll audit reports?
Yes, and it works alongside them. UKG Pro's reports check data already in payroll. Pre-payroll validation checks the inputs before import, including files that are missing or late, which payroll reports cannot see.
Can validation rules differ by pay group?
Yes. Rules and tolerances are set per pay group or location, because what is normal for one is noise or risk for another.
Does it detect manual changes made in UKG Pro?
Yes. After load, the system compares UKG Pro with what was approved, and changes made directly in payroll are recorded for review.
How is AI used here?
Rules do the validating. AI assists by explaining exceptions in plain language and grouping related ones. It never makes a pay decision, and your team approves every load.