HR, Attendance & Payroll
From the punch at the door to the payslip and the tax filing
Attendance you can defend, and a payroll you can explain. Staff clock in by GPS radius, office wifi, a QR that rotates at the counter, a face match or a PIN at a kiosk, and anything odd β a mocked location, a rooted phone, a clock that disagrees, a face that does not match β goes to a review queue with its evidence instead of sliding quietly into the timesheet. From there the period closes, a versioned payroll formula computes the pay, and the insurance and personal income tax filings come off the same approved numbers.
Key Features
Built with
How it works
Trust is the design problem here, not the feature count. Every clock-in carries the signals that could make it a lie β whether the device is the bound one, where the location came from, how far the clock has drifted, how close the face was β and the system's answer to a bad signal is a queue with evidence and a decision on the record, not a silent pass and not a silent block. The same thinking runs through payroll: a run snapshots the template version and every system variable it used, so a payslip queried three months later can be rebuilt exactly as it was computed. Sensitive fields β ID numbers, bank accounts, uploaded documents β are encrypted at rest, and each time one is opened the view is logged.
How it works
How It Works
Set up
the org tree, who approves what, and the clock-in rules each unit has to meet
Run the month
staff clock in and file requests from the app, and anything suspicious waits in the review queue with its photos
Close the timesheet
holidays, approved corrections and overtime settle, and the period locks
Pay and file
the template computes, the run is approved, payslips go out, and the insurance and tax filings come off the same figures