Guide: SpotOn Teamwork
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
 |
|
|---|---|
| Location | ✅ Locations |
| Shift (actual) | ✅ Punches |
| Shift (planned) | ❌ Not Supported |
| Hours | ✅ Hours Worked |
| Salaried workers | ❌ Not Supported — every employee is costed at an hourly rate |
| Employee | ✅ Employees |
| Role | ✅ Roles |
| House Part | ✅ Role grouping or Department |
| Pay rate | ✅ Hourly Rate |
| Labour cost | ✅ Base Cost |
| Employer taxes | 🚸 Applied from the Employer tax rate you set when connecting |
| Pension | ❌ Not Supported |
| Overheads | ❌ Not Supported |
| Holiday | ❌ Not Supported |
| Breaks | ❌ Not Supported |
| Overtime | ❌ Not Supported |
| Employee start / leave date | ❌ Not Supported |
| Borrowed / loaned employees | ❌ Not Supported |
| Exception costs / one-off costs | ❌ Not Supported |
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 20 minutes |
| Data retrieved on each poll | Each file covers the last few business days for all locations; the latest file replaces earlier data for the days it covers |
| Historical data | All data SpotOn Teamwork has sent us since the integration was connected |
How Do I Compare SpotOn Teamwork Data to Data in Tenzo?
Compare against your SpotOn Teamwork labour reporting for the same date range and location. Hours worked and labour cost per employee should reconcile.
One difference matters for how you read hours: a shift's hours are the full clocked span, so any unpaid break an employee took is still included. Hours in Tenzo will therefore read slightly higher than a break-adjusted figure. Breaks, overtime and holiday are not part of the feed, and employer taxes are calculated by Tenzo from the rate you set rather than sent by SpotOn.