UKG Pro payroll adjustments without the rework
A correction should change exactly what was wrong and nothing else. Every adjustment is traced, approved, and recorded.
A revised file changes only its changed lines.
Nothing is removed once payroll has taken it, unless your team chooses.
Every correction recorded with what changed, why, and who approved.
Corrections are where payroll time disappears. A location resends a file, a retro rate arrives late, or an employee's hours were short last cycle. On UKG Pro, fixing it often means finding the original items by hand, deleting or adjusting them, and making sure the replacement does not double-pay anyone.
PCLnXAI knows exactly what each earlier load sent. A revised file is compared with what is already in UKG Pro, and only the changed lines are proposed. A wrong file can be backed out precisely. Adjustments after reconciliation are prepared as their own controlled set.
- Stay in UKG Pro as posted
- Nothing to review
- Old item removed, new item proposed
- Shown side by side for approval
- Proposed for removal
- Refused if payroll already took them
Replacement files: changed lines only
When a corrected file arrives, the system compares it line by line with what was sent from the original. Unchanged lines stay. Changed lines are replaced. Lines that no longer appear are removed. The proposal goes to approval like any other load, and nothing is replaced if payroll has already taken part of it, unless your team chooses how to handle that.
Backing out a file
If a file should not have been loaded, the system lists its items, shows which are still pending and which payroll has taken, and removes the pending ones on approval. The removal is confirmed against UKG Pro and recorded with its reason.
Adjustments after reconciliation
- Underpayments. Short hours or missed earnings from a prior cycle, prepared as a separate adjustment set with the evidence.
- Overpayments. Recovered according to your policy, routed for review.
- Retro pay. Rate changes applied to past periods, calculated by your rules and checked before posting.
- Off-cycle payments. Prepared with the same checks and approval as a regular load.
- 1Intake
- 2Validation
- 3Reconciliation
- 4Exceptions
- 5Approval
- 6Close
How PCLnXAI handles corrections
Every correction follows the same path as a regular load: validated, reconciled, approved, posted, confirmed, recorded. Fewer corrections reach payroll in the first place, because validation runs before import. See reducing payroll rework.
Frequently asked questions
Can a revised file double-pay employees?
No. The system compares it with what was already sent, and proposes only changes. It will not post a revised file on top of the original.
What if payroll has already taken some items?
The system shows which items were taken. It will not remove items already in a payroll unless your team explicitly chooses a partial approach.
Are off-cycle payments supported?
Yes, with the same validation and approval as a regular cycle.
Is every correction recorded?
Yes. What changed, why, and who approved it are kept in the cycle record.