Loading
Between the floor and the office. Attendance is captured where the work is; payroll is run somewhere else; and between them sits a spreadsheet emailed on the 25th.
Every transcription is a chance to be wrong about overtime, and overtime is where the money and the disputes are.
Check-in and check-out produce the attendance record directly. The roster supplies shift patterns and premiums, so overtime is computed rather than declared.
Corrections are regularisation requests with a reason and an approver, not silent edits — which is what keeps the record usable as evidence.
It does not connect to your clocking hardware out of the box. Check-in works from the app or the web; existing terminals integrate through the API.
And it does not file returns. It produces the figures and holds the evidence.
Payroll reads the same records rather than a transcription, so the run is a check rather than a reconstruction. A variance against last period is the useful test, and it works because the inputs are consistent.
And every adjustment keeps its previous value, so an overtime query takes a minute.
Yes, from the roster and the clock.
As a regularisation request with a reason and an approver.
Through the API. The arithmetic stays in Nest.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.