Workforce · time and overtime
Overtime goes wrong quietly, because the rule is not the same for every employee.
Five thresholds, each set per employment level, with multipliers that come from statute. Management and line staff don’t share a rule.
Daily, weekly, bi-weekly, semi-monthly and monthly
Per level, so one rule never covers everybody
Named, one format per company

Trusted by the Caribbean’s best-known employers
Airlines, telecoms, utilities, hotels, credit unions and the National Insurance Board itself.

Five thresholds, each set per employment level
Most people skim past this part of Workforce. It’s the reason overtime goes wrong quietly.
Daily
Catches the single long shift a weekly total would never show.
Weekly
The familiar one. For many systems, the only one.
Bi-weekly
For a fortnightly cycle, where a weekly threshold would double-count.
Semi-monthly
For the periods that don’t divide into weeks at all.
Monthly
For salaried arrangements measured across the month.
And each is per level
Management and line staff don’t share a rule, and here they don’t have to.
One overtime threshold for the whole account means one rule for a kitchen porter, a duty manager and a financial controller. In practice it gets set for whichever group complains first. Then it’s quietly wrong for the other two, every period. Nobody notices, because a payslip that’s wrong by a believable amount looks exactly like one that’s right.
Two switches decide what the number means
Whether overtime is calculated from the threshold, or taken as it is listed on the timesheet. And whether regular hours may exceed the threshold during a run.
Between them, they decide whether the system computes overtime or the system records what a supervisor already decided. Both are fair ways to run. If overtime must be authorised in advance, you want the second. If hours are whatever the clock says, you want the first. Pick without knowing which one you’re picking, and your payroll ends up disagreeing with your own supervisors.
Timesheets, and the flag before approval
A review step is there so you see now what you’d otherwise find out later.
- A long-shift threshold flags a day that ran unusually long in the bulk timesheet preview, before anyone approves it
- A separate daily threshold for time off, so leave hours don’t create overtime
- Overtime lands on a pay type you nominate, so it reports and posts as itself
The time-off threshold only looks important once it’s cost you. A week with a public holiday and a full set of worked days can tip over a weekly threshold on hours nobody worked. The overtime that follows is real money, paid on an error nobody can see in the total.
Working with timesheets
- Bulk create and bulk approve
- Edit reasons on a changed punch
- Auto clock-out at the end of a scheduled shift
- Late and unscheduled clock-in alerts
Why edit reasons matter
At audit, a corrected punch that records why it was corrected reads very differently from one that was simply changed. The first is a decision. The second looks like any other alteration.
And auto clock-out fixes the most common data problem in attendance. A wrong punch is rarer than a shift nobody closed.

Eight routes for hours you already collect
Here they are by name, so you can check whether yours is on the list.
Time and attendance systems
- TimeForce
- uAttend
- TimeMoto
Workforce platforms
- Deputy
- TimeClock Plus
Field services
- Aspire
- Landscape Management Network
Generic
- An Excel layout
Or capture directly
Four routes, covered on time clocks and mobile clock-in.
Aspire and Landscape Management Network matter to field-services employers, who usually get told to change systems instead. A landscaping or grounds-maintenance operation running job costing in one of those isn’t going to drop it to get payroll right. And it shouldn’t have to.
A company imports one of these formats, set once against the account. The import shows a preview before it commits. And while the run is still draft or pending approval, you can roll it back once.
Thresholds are configuration. Multipliers are the instrument.
Only one of the two is yours to set.
A threshold is a rule you configure against how your operation works and what your contracts say. A multiplier is law. What overtime is paid at, and when a premium rate applies, is set by the instrument in each territory. It isn’t a setting in this product or any other.
We publish those multipliers per territory, with their sources and the date each was verified. Follow the links and check:
Hours computed here reach the pay run, where each territory’s statutory engine applies its own multipliers, and the pre-run review raises a regular-hours-exceeded warning among its sixteen flags before anyone approves.
Upstream, a schedule can mark an entry as scheduled overtime with its own hours before it’s worked. That’s how you can still tell planned from unplanned overtime once the timesheets exist.
Where it stops
It doesn’t decide whether overtime was authorised
It applies the threshold you set and shows the exception. Whether a given hour should have been worked is a management question, and the product doesn’t pretend to answer it.
Nor does it enforce a statutory maximum. It calculates against the rule you set. If your setup allows more hours than the instrument does, the system will calculate them, and that setup is your responsibility.
What it does guarantee is that the rule is applied consistently, per employment level, and visible before approval. The long-shift flag, the edit reasons and the pre-run warning are all there to have the conversation sooner.
Articles
Further reading
Overtime is where a Caribbean payroll goes wrong quietly
No two territories we support have the same rule.
Read the article ArticleRounding and grace periods, and who they actually favour
Small decisions, applied every day, to everyone.
Read the article ArticleApproving hours before they become money
The last point where a mistake is still cheap.
Read the articleQuestions about time and overtime
Can overtime rules differ between staff groups?
Does the system calculate overtime, or record it?
Which time clocks can we import from?
Can leave hours accidentally create overtime?
Does it stop us breaching a statutory maximum?
What gets checked before approval?
See it on your own data
Bring a period of real hours, and the staff group whose overtime rule is different. We’ll set up both and run them.
- Five thresholds set differently for two employment levels
- Both switches, and what each one changes
- An import from one of the eight routes on your own file
- A long-shift flag raised in the bulk preview
- SOC 2 Type II attested
- AES-256 at rest
- 99.9% uptime
- Built in The Bahamas
Where to go next
Time sits inside Workforce, between the roster and the run. These are the pages around it.
Time and overtime are part of the Workforce module. Statutory overtime multipliers are published per territory with their sources and verification dates; the thresholds described here are configuration. Security: AES-256 at rest via AWS KMS, TLS 1.2 and above in transit, SOC 2 Type II attested against the Security criteria with the report available under NDA, and AWS US multi-AZ as standard with on-premises or Caribbean regional cloud on request, subject to scoping. See also Core HR, Payroll and Talent · the six territories · contact.
