UKG to Viewpoint Vista: Payroll and HR Data Integration
SelectView Data Solutions integrates workforce systems with Trimble Viewpoint Vista. The UKG to Viewpoint Vista integration one of the most requested and one of the easiest to get wrong, because both systems can legitimately claim to own employee data. This guide covers the ownership decision, how data should flow, and what causes these integrations to drift.
The decision that comes before any technical work
Decide which system gets the initial employee information input, and enforce it. If UKG integration and Vista both believe they own employee records, you will spend the following year reconciling names, statuses and rates instead of getting value from either system.
Our usual recommendation for contractors: UKG owns employee and HR data including benefits, onboarding and certifications. Vista owns payroll processing, job costed labor and everything that touches job cost. Each field flows one direction only.
What flows, and which way
Data
Owner
Direction
Note
Employee demographics
UKG
UKG to Vista
New hires and changes originate in UKG
Employment status
UKG
UKG to Vista
Terminations must reach payroll promptly
Pay rates
Depends
Decide explicitly
Union rates often belong in Vista Craft and Class
Time and attendance
UKG or field system
Into Vista
Must arrive coded to job, phase and cost type
Job costed labor
Vista
Stays in Vista
This is why payroll runs in Vista
Benefits and deductions
UKG
UKG to Vista
Deduction codes must be mapped explicitly
Certifications and compliance
UKG
Reference into Vista
Drives eligibility for classifications
The pay rate exception
Pay rates are the one field where the obvious answer is often wrong. In a union or prevailing wage environment, rates are driven by Craft and Class in Vista rather than by an individual employee record, because the rate follows the classification of work performed rather than the person. Pushing employee level rates from UKG into that structure will break certified payroll. If you have both union and non-union employees, the practical answer is usually that UKG owns rates for salaried and non-union staff, and Vista owns rates driven by classification.
Time capture and job costing
The value of running payroll in Vista is that labor cost lands in job cost at the right level of detail. That only works if time arrives coded to job, phase and cost type. Time captured without cost coding creates a reconciliation problem rather than solving one, because someone has to allocate it afterward.
The time entry system will be capturing time on the job phase and cost type. However, payroll processing may lose the detail that you need for job costing. This is a primary consideration for integrating with any outsourced payroll system.
Compliance considerations
UKG holds certifications, Vista drives classification-based pay — and the two intersect at eligibility. When a certification lapses, the worker may no longer qualify for the classification at which they are being paid. Neither system catches this on its own. Don’t assume an integration will; build the check into reporting instead.
What breaks these integrations
No agreed system of record, which produces permanent reconciliation work.
Deduction and earnings codes assumed to match because the names look similar.
Terminations that reach HR but not payroll, so someone stays on the payroll run.
Silent failures. A nightly job stops and nobody notices until payroll does not balance.
Company mismatch in multi company Vista installs, so records land in the wrong legal entity.
How to implement it
Agree ownership per field, in writing.
Map earnings, deduction and liability codes explicitly. Do not rely on matching names or freeform text.
Build against a copy of Vista, never production.
Reconcile a full payroll cycle before go-live: employee counts, gross pay, and job costed labor against job cost.
Instrument the integration with failure alerting and a visible last successful run.
Review the mapping quarterly, because new codes get added in both systems.
Frequently Asked Questions
Can UKG integrate with Viewpoint Vista?
Yes. The common pattern is UKG owning employee and HR data while Vista owns payroll processing and job costed labor, with each field flowing one direction only.
Which system should own employee records?
Usually UKG for demographics, status, benefits and certifications, and Vista for payroll processing and anything touching job cost. What matters most is that the decision is explicit.
What about pay rates?
In union or prevailing wage environments, rates are driven by Craft and Class in Vista because the rate follows the classification of work, not the person. Pushing employee level rates into that structure will break certified payroll.
How does time reach job cost?
Time must arrive coded to job, phase and cost type. Time captured without cost coding creates a reconciliation problem rather than solving one.
What breaks UKG to Vista integrations?
No agreed system of record, unmapped earnings and deduction codes, terminations that do not reach payroll, silent job failures, and company mismatches in multi company installs.
How long does the integration take?
Longer than a reporting integration, because the work is in code mapping and exception handling rather than the connection. Reconciling a full payroll cycle before go-live is essential.