UKG Pro

Payroll requests and cases, tied to the cycle they affect

A correction request is only useful if it reaches the right pay group before cutoff. Requests are tied to the cycle, routed, and recorded with it.

By Dan Agarwal, founder·Updated

Each request matched to the employee's pay group and open cycle.

Routed to the analyst who owns that pay group.

Requests that change pay join the same queue as held lines.

Location managers send payroll requests constantly: missed punches, rate changes, final pay, corrections. Whether they arrive through a case tool or email, payroll often spends real time working out which pay group and which period each request belongs to, and requests filed against the wrong period are refiled or missed.

PCLnXAI brings payroll cases into the cycle. Each request is matched to the employee's pay group and the collecting cycle, routed to the analyst who owns that pay group, and kept with the cycle record, alongside the exceptions from the pipeline itself.

A location request, start to finish
Location request
Case tool or email
Matched to pay group
From UKG Pro
Placed in open cycle
Analyst decides
Recorded with the cycle
Requests stop being refiled against closed periods, because each one is placed in the cycle it affects.

Where requests go wrong

  • The form does not ask for pay group or pay period, so payroll has to work it out.
  • Requests filed against a closed period are refiled or duplicated.
  • Attachments are downloaded repeatedly by different people.
  • Catch-all request types hide work that has no clear owner.

Requests as part of the cycle

Each request is placed in the open cycle for the employee's pay group, triaged by type, and routed to an owner. Requests that change pay become exceptions in the same queue as held lines and reconciliation blocks, so the approver sees everything that affects the load. See exception management.

Working with your existing case tool

Existing cases can be brought in from the tool your locations use today, so the history is kept and nobody has to change how they submit requests on day one.

Where this sits in the payroll cycle
Source systems
  1. 1Intake
  2. 2Validation
  3. 3Reconciliation
  4. 4Exceptions
  5. 5Approval
  6. 6Close
UKG Pro
Source systems feed six stages in your environment. Nothing reaches UKG Pro until a person approves the load.

How PCLnXAI handles payroll requests

We review your request types and volumes during discovery, then configure triage and routing by pay group. Location access uses your single sign-on.

Frequently asked questions

Do location managers have to use a new tool?

Not on day one. Existing cases can be imported, and any change to how locations submit requests is your decision.

How is the right cycle chosen for a request?

From the employee's pay group in UKG Pro and the open cycle for that pay group.

Who owns catch-all requests?

Your team decides; typically the pay group's analyst.

Are requests part of the audit trail?

Yes. Requests, their resolution, and any resulting pay change are recorded with the cycle.

See it on your own UKG Pro payroll.

We map how your payroll actually runs, then prove the system on your own data across live pay cycles, with your team approving every load.