UKG payroll exceptions, resolved before payday
Exceptions are not the failure. Unrouted exceptions are. Each one arrives in a queue with its reason, an owner, and a record of how it was resolved.
Every exception for a cycle in one queue, tied to the pay group and lines.
Routed to the person with the context to decide.
Undecided lines block sign-off; overrides need a written reason.
In a multi-location UKG Pro payroll, exceptions arrive from everywhere: held import lines, reconciliation differences, variance flags, late files, and requests from locations. They are usually tracked in email threads and spreadsheets, and resolved by whoever sees them first.
PCLnXAI puts every exception for a cycle into one queue, tied to the pay group and the lines involved. Each carries a plain-language reason, a suggested owner, and the evidence, and nothing in that pay group loads until the blocking ones are resolved.
- Held import lines
- Reconciliation blocks
- Variance flags
- Late or missing files
- Location requests
- Resolved before the load
- Held to next cycle with a reason
- Override with written reason
Types of exceptions in a UKG Pro cycle
- Held lines. Import lines that could not be placed: unknown employee, wrong pay group, unmapped code.
- Reconciliation blocks. Differences between source and load that would change pay.
- Variance flags. Movements beyond tolerance that need a reason.
- Missing inputs. Expected files that are late or absent.
- Terminated employees. Pay for leavers, routed to their own queue rather than approved with routine lines.
- Location requests. Corrections and questions from managers, tied to the cycle they affect.
Routing and resolution
Routine, well-understood exceptions follow rules your team has agreed. Everything else goes to the person with the context to judge it, usually the pay group's analyst. Each resolution, whether a fix, a hold to next cycle, or an approved override, is recorded with who decided and why.
Undecided lines block sign-off. A lead may override only with a written reason, which is kept in the cycle record. Our working model for payroll exception handling describes the practice in more depth.
Fewer exceptions every cycle
Because every exception carries a cause, recurring ones become visible. A location that sends files late, a code that never maps, or a transfer pattern that always lands in the wrong pay group can be fixed at the source, and the queue gets shorter over time.
- 1Intake
- 2Validation
- 3Reconciliation
- 4Exceptions
- 5Approval
- 6Close
How PCLnXAI handles exceptions
The exception queue is part of the approval screen your team uses for every pay group. We configure routing and owners with your team during discovery, then refine them over the first live cycles.
Frequently asked questions
Does this replace our ticketing tool?
Not necessarily. Exceptions are tied to the payroll cycle and its lines. Requests from other tools can be brought into the same queue. See payroll case management.
Can exceptions be auto-approved?
Only where your team has agreed a rule for a well-understood pattern. Everything else is decided by a person, and terminated-employee pay is always routed for review.
What if an exception cannot be resolved before cutoff?
It can be held to the next cycle with a reason, or a lead can approve an override with a written reason. Either way it is recorded.
Is there a record for auditors?
Yes. Every exception, its resolution, and who decided are part of the cycle's audit trail.