Approve the period.
Then it’s locked.
Overtime computes on your rule, not a generic one. Approved PTO lands at base rate. You review the period person by person, sign off, and it freezes, so the number you approved is the number that gets paid.
The hours are already in the system.
Payroll is just sign-off.
If your techs are clocking in here, payroll stops being a rebuild and starts being a review. Overtime is already computed on your rule. PTO is already in. You read the period, approve it, and push it to QuickBooks or Gusto, with the whole list on screen before anything leaves.
Overtime on your rule, not ours
Set your shop's overtime policy once and every period computes against it. No spreadsheet formula to maintain, no list of exceptions you carry in your head.
PTO at base rate, automatically
Approved time off lands in the period as paid hours at base rate. The total you sign off on is the total you pay.
Aligned to your pay period
Weekly, biweekly, semi-monthly, whatever your run is. Hours slot into the right period instead of a calendar month you then have to unpick.
Approve once and it freezes
Sign off and the period locks. Hours cannot move after that, so the number you approved is the number that gets paid and the number that reaches your books.
QuickBooks, Gusto, or CSV
Approved hours go out as QuickBooks Online time activity, a staged Gusto timesheet with the overtime split already applied, or a plain CSV for anything else.
Nothing sends until you have seen it
Every sync opens on a preview: every person, every hour, every destination. You review it, then you send. No silent pushes into your accounting.
Sign off once.
Nobody touches it after.
Included in the flat price. No payroll add-on, no per-tech fee, no third-party timesheet tool to reconcile at the end of the week.