UKG Pro

UKG Pro pay cycles that follow your pay calendar

When a pay period closes in UKG Pro, the next cycle opens for that pay group, with its expected files, deadlines, and checks ready.

By Dan Agarwal, founder·Updated

Cycles open when UKG Pro closes the prior period, per pay group.

Files placed in the cycle their data covers.

One status view across every pay group.

A UKG Pro tenant with many pay groups runs many calendars at once. Weekly groups close while biweekly ones are mid-period, holiday weeks shift pay dates, and each group has its own file deadlines. Keeping track of which cycle each file belongs to is often a manual job done by memory and spreadsheet.

PCLnXAI reads the pay calendar from UKG Pro. When a period is closed, the next collecting cycle opens for that pay group automatically, files are placed in the cycle they belong to, and each cycle has a clear status from open to closed.

A cycle's life, read from the UKG Pro calendar
Period closes in UKG Pro
Collecting
Expected files arrive and are validated
Ready for review
Reconciliation available
Approved and loaded
Closed
Cycle record complete
The calendar stays in UKG Pro. The pipeline follows it, so a holiday pay date change is followed automatically.

One calendar per pay group

Each pay group follows its own period dates and pay date as defined in UKG Pro. The system does not keep a separate calendar that can drift. If UKG Pro changes a pay date for a holiday, the cycle follows it.

Files placed in the right cycle

Files are matched to a cycle by the period their data covers, not only by file name or arrival date. A file that belongs to the following week is held for that week rather than loaded early. Files with no clear pay group are placed by rule and flagged.

Cycle status your team can see

  • Collecting. Expected files are arriving and being validated.
  • Ready for review. Inputs are complete or exceptions are known; reconciliation is available.
  • Approved and loaded. The load posted and was confirmed against UKG Pro.
  • Closed. UKG Pro closed the period; the cycle record is complete.

Safe by default

Automation that follows the UKG Pro calendar can be switched per environment. Test tenants often carry frozen or stale calendars, so cycle opening can follow production while test loads stay under manual control.

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 pay cycles

During discovery we map every pay group, its frequency, its file deadlines, and its exceptions to the normal calendar. The pipeline then runs each pay group on its own cycle, and your team sees one status view across all of them.

Frequently asked questions

Does the system change our UKG Pro pay calendar?

No. It reads the calendar from UKG Pro and follows it. Calendar setup stays with your team in UKG Pro.

Can weekly and biweekly groups run at the same time?

Yes. Each pay group runs on its own cycle. See weekly and biweekly payroll.

What happens to a file that arrives for the wrong cycle?

It is placed in the cycle its data belongs to, or held with a reason if that is unclear.

Can we still open or close a cycle by hand?

Yes. Manual control remains available, and every manual action is recorded.

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.