UKG Pro pay data import, automated and approved
Every earning, hour, and adjustment that reaches UKG Pro arrives checked, mapped, traceable to its source line, and approved by your team.
Every source file validated and mapped before it becomes a pending pay item.
Each pay item traced back to its source file and line.
A wrong file can be backed out precisely; a revised one changes only its changed lines.
Most UKG Pro payroll teams spend more of each cycle preparing imports than processing payroll. Files arrive from time systems, operations systems, commission tools, and location spreadsheets, each in its own layout. Someone reshapes them into an import template, checks the employee numbers, fixes the codes, uploads, and then checks again after Bring in Time Imports to make sure what landed is what was sent.
That work is skilled, repetitive, and easy to get slightly wrong. PCLnXAI automates it as one governed step in the pre-payroll pipeline: files are read as they arrive, validated against your rules and your UKG Pro configuration, and turned into pending pay items that wait for your team's approval before anything posts.
Where UKG Pro imports usually go wrong
The import itself is rarely the problem. The problems sit in the data that feeds it, and they repeat every cycle until someone writes them down.
- Employee not in the pay group. A line for an employee who transferred, termed, or sits in another pay group is accepted by the file but never reaches the right payroll, and quietly disappears from the totals.
- Codes that drift. A source system adds a new pay type, or a location renames one, and lines map to the wrong earning code or are rejected.
- The same line twice. A resent or revised file is imported on top of the original, and nothing in the payroll system records which file each item came from.
- Rates and hours that do not belong together. Rate-based codes arrive with flat amounts, or hours arrive for a code that should carry dollars.
- No way to take a file back. When a file turns out to be wrong after import, finding and removing exactly its items is slow manual work.
What an automated UKG Pro import does differently
The system knows which files to expect for each pay group and cycle, and when. Each file is validated on arrival: employees are resolved against UKG Pro, pay group membership is confirmed, codes are mapped using rules your team already applies, and lines that cannot be placed are held with a plain-language reason instead of being dropped.
Every line that will post is recorded against its source file and line number before it is sent. That record is what makes the rest possible: a resent file is recognized and only its changed lines are proposed, a wrong file can be backed out precisely, and a source-to-load report shows what the automation changed between the feed and the load.
Posting through UKG Pro's own interfaces
Items are posted through UKG Pro's supported APIs as pending pay items, the same objects your team would create by import. There is no screen automation and no scripted keystrokes, so a UKG Pro release does not break the connection.
Posting happens only after approval. Your payroll team sees the full picture for the pay group, including held lines and reconciliation results, and decides. The load is then read back from UKG Pro to confirm that what landed matches what was approved.
What your team keeps
Your UKG Pro configuration, earning codes, and payroll process stay exactly as they are. The rules your analysts already apply by eye become written rules the pipeline runs on every file, and the judgment calls stay with the people who own them.
- 1Intake
- 2Validation
- 3Reconciliation
- 4Exceptions
- 5Approval
- 6Close
How PCLnXAI handles UKG Pro imports
We map how each pay group's files arrive today, file by file, then adapt a proven import pipeline to those files and your UKG Pro setup. It runs in your environment, rehearses against your UKG Pro test tenant first, and posts to production only on your team's approval.
Frequently asked questions
Does this replace UKG Pro's import tools?
No. The system prepares and posts the same pending pay items an import would create, through UKG Pro's supported interfaces. Your payroll process, including Bring in Time Imports and payroll calculation, stays in UKG Pro.
What happens to lines that cannot be imported?
They are held, not dropped. Each held line carries a reason, such as an employee who is not in the pay group or a code with no mapping, so your team can resolve it before the cycle closes.
Can a file be removed after it has been posted?
Yes, as long as payroll has not yet taken the items. Because every posted item is recorded against its source file, the system can back out exactly that file's items and confirm the removal.
Does anything post without approval?
No. Every load waits for your payroll team's approval. Nothing reaches UKG Pro production until a person has reviewed the pay group and approved it.