Because attendance is captured on the floor and payroll is run in an office, 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 is.
Disputes then get settled from memory, because the clock data and the payslip were never on the same record.
Rosters carry shift patterns, and check-in and check-out produce the attendance record directly. Regularisation is a request with an approver and a reason rather than an edit somebody makes quietly.
Overtime and shift premiums are computed from the roster and the clock, so the payroll run reads what actually happened.
It is not a workforce scheduling optimiser and it will not build the roster for you. It holds the roster you build and enforces it consistently.
And 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.
Multi-site operations sit on one personnel record with one reporting line, so an employee moving between sites keeps their history rather than being created again.
Statutory compliance and payslips come from the same record, and every change to salary keeps its previous value with a date and an actor.
Yes, computed from the roster and the clock, without re-keying.
Yes, per site and per team, with premiums attached.
Through the API. The record and the arithmetic stay in Nest.
Half an hour on your own numbers is usually enough to say whether Nest is the right place to start.