UKG payroll reconciliation, location by location
Every cycle, hours and dollars are reconciled from each source system to UKG Pro, by location and pay code, before your team approves the load.
Hours and dollars reconciled from each source to UKG Pro, by location and code.
Three comparisons: source to load, load to UKG Pro, cycle to cycle.
Results on the approval screen before anyone releases a load.
Reconciliation is the control payroll leaders trust most and have the least time for. On UKG Pro it usually means exporting a register, pulling source totals into a spreadsheet, and chasing the differences across locations, often after payroll has already calculated.
PCLnXAI runs reconciliation as part of every cycle, before approval. Source totals, the lines about to post, and what UKG Pro holds are compared by location, pay group, and code, and every difference is classified as match, warn, or block, with its cause.
Three points of comparison
A complete reconciliation answers three questions, not one:
- Source to load. Did every line that left the source system become a pending pay item, or a held line with a reason?
- Load to UKG Pro. Does UKG Pro hold exactly what was approved, after import and after calculation?
- Cycle to cycle. Do the totals make sense against comparable prior cycles, by location?
Match, warn, or block
Each difference is classified, so your team looks only at what needs a person. A match goes through. A warning is a movement inside agreed tolerance that is worth a glance. A block is a difference that would change someone's pay, and it stops that pay group's load until it is resolved or a lead approves it with a written reason.
Tolerances are set per location and pay group. A distribution center with seasonal overtime is held to a different expectation than a corporate office.
When the totals do not tie
The difference is traced to lines, not left as a number. Typical findings: an employee whose pay group in UKG Pro differs from the source, a code that maps to an earning with no hours, a file for the following week, or a manual change made in UKG Pro after load. Each is reported with the employees and source lines involved.
For background on the practice itself, see what payroll reconciliation is and reconciling payroll across locations.
- 1Intake
- 2Validation
- 3Reconciliation
- 4Exceptions
- 5Approval
- 6Close
How PCLnXAI handles UKG reconciliation
We agree the comparison points and tolerances with your team during discovery, then run reconciliation automatically on every cycle. Results appear on the approval screen, so the person releasing a load sees the full reconciliation picture first.
Frequently asked questions
Is reconciliation done before or after UKG Pro calculates?
Both. Source-to-load reconciliation runs before approval. A second comparison runs after import and calculation to confirm UKG Pro holds what was approved.
Can we reconcile by location even if UKG Pro groups by pay group?
Yes. Reconciliation runs at the level your team manages, usually location within pay group, and rolls up from there.
What happens when a block is found?
That pay group's load waits. Your team resolves the difference or a lead approves it with a written reason, which is kept in the cycle record.
Does this need a data warehouse?
No. Reconciliation runs inside the pipeline, in your environment, using the files and UKG Pro data the cycle already uses.