Break rules
Deduct the scheduled unpaid break automatically, per location. Off by default so nothing changes without you choosing it.
✦ Timesheets
The hours you approve are the hours you pay.
Timesheets assembled from real clock-ins, with breaks deducted and overtime applied by rule. Approve, lock, and the numbers cannot drift afterwards.
Review
Scheduled against worked, side by side.
Every timesheet shows what was scheduled next to what actually happened, and flags the gap. Overtime, short shifts and missed punches surface before the pay run instead of turning up as a payroll query three weeks later.
- Generated automatically from clock-ins for a period and location
- Break auto-deduction using the shift’s scheduled break
- Configurable rounding and overtime thresholds
- Discrepancy flags for missed clock-outs and unscheduled hours
- Approve → lock, so an approved period cannot silently change
EmployeeScheduledWorkedStatus
Jamie StoneShoreditch · 5 shifts
38.0h
37.5h
Matches
Amina OkaforCamden · 4 shifts
32.0h
34.25h
+2.25h OT
Leo ParkShoreditch · 5 shifts
40.0h
36.0h
Missed clock-out
Breaks auto-deducted per location rules · Approve → lock → pay run
Capabilities
Where the arguments used to be.
Rounding
Round to the nearest 5, 10 or 15 minutes — consistently, and visible on the record.
Overtime
Thresholds per location, calculated from actual versus scheduled hours rather than by hand.
Lock periods
Once approved and locked, the period is frozen. Corrections happen as visible adjustments, not edits.
Delegated approval
Team leads approve their own team; finance sees the whole period.
Export
CSV out for an external payroll bureau, or straight into a TaskBit pay run.
Straight into pay
One approval, all the way to the payslip.
A locked timesheet period is the only thing a pay run will read. That single rule removes the whole class of error where the rota said one thing, the clocking box said another, and the payroll spreadsheet said a third.
- Pay runs build from locked periods only
- Hourly and salaried employees in the same run
- Holiday pay and premiums applied by rule
- Payslip PDFs land in each employee’s own app
Amina OkaforTeam lead · Camden
LockedBasic pay · 152.0h @ £12.60£1,915.20
Overtime · 6.0h @ £18.90£113.40
Holiday pay£96.40
PAYE income tax−£248.60
National Insurance (cat. A)−£114.32
Pension (5%)−£106.25
Net pay£1,655.83
Illustrative figures · cumulative PAYE across the tax year
Questions
What people ask about this.
Do I have to use break deduction?
No — it is off by default. Turn it on per location and the shift’s scheduled unpaid break comes off worked hours; leave it off and raw clock-in to clock-out stands.
Can a manager edit a timesheet?
Before approval, yes, and the change is attributed. After lock, the period is frozen and any correction is a visible adjustment rather than a silent edit.
What about salaried staff?
Salaried employees appear in the same period with contracted hours rather than clock-derived ones, so a mixed workforce runs in a single pay run.
Can we export to our existing payroll provider?
Yes. CSV export of approved periods is designed for exactly that — many customers keep their bureau and use TaskBit only to get clean, agreed hours to them.
End the monthly hours argument.
Approve a real timesheet in your own trial organisation this week.
No credit card. Cancel any time. Or book a demo instead.