Guide: UKG
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
 |
|
|---|---|
| Location | ✅ Business Structure |
| Shift (actual) | ✅ Worked Shifts |
| Shift (planned) | ✅ Scheduled Shifts |
| Hours | ✅ Worked Hours |
| Salaried workers | ✅ Salaried employees, costed from their pay code |
| Employee | ✅ People |
| Role | ✅ Jobs |
| House Part | ✅ Business Structure |
| Overheads | ✅ Calculated from the Overhead Rate you set when connecting |
| Holiday | 🚸 Non-worked pay codes |
| Breaks | ❌ Not Supported |
| Overtime | ❌ Not Supported |
| Pay rate | ❌ Not Supported — UKG sends the cost of a shift rather than an hourly rate |
| Borrowed / loaned employees | ✅ Job and labour transfers |
| Exception costs / one-off costs | ❌ Not Supported |
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 8 hours |
| Data retrieved on each poll | Two weeks back and two weeks forward |
| Historical data | All data since you started using UKG |
How Do I Compare UKG Data to Data in Tenzo?
Compare against your UKG timecard and schedule reporting for the same date range and location. Worked hours, scheduled hours and labour cost per employee should reconcile.
Labour cost comes from UKG's own per-day pay figure with leave taken out, which is why it matches for salaried and hourly staff alike and includes premiums that a plain hours total leaves out. Because the cost arrives as an amount rather than a rate, Tenzo does not show an hourly pay rate per shift. Overheads are not sent by UKG — Tenzo adds them using the Overhead Rate you set, so changing that rate changes reported cost.