Inside the service
Attendance in any company starts with two questions: who punched, and where. This service answers both at the moment of the punch, not afterwards. The app checks the employee's device and location, the system matches the location against the drawn boundary of the branch and records every refusal with its reason, and the accepted punch enters the shift calculation. Out of it come minutes of lateness, early departure and absence that the report and payroll read together. What falls along the way, a refused attempt or a forgotten punch, reaches management in a form it can act on: approve it, correct it, or review the site boundary.
01
Punch location per employee
By default an employee punches at their own branch. Your company can allow any saved branch, a set of branches you pick, or anywhere at all, and each employee can have a setting of their own that overrides the company's. The boundary of each site is drawn on the map as a rectangle, a polygon or a circle, and at punch time the system matches the phone's coordinates against it. A check-in outside the boundary is refused with a message naming the nearest allowed site and your distance from it, and the refusal is recorded for management. A check-out is never blocked, because an employee must be able to end the day, so it is recorded and the employee's sheet shows it fell outside the boundary. If a site has no boundary drawn, nobody is refused over an incomplete setup.
02
A punch that is hard to fake
Before every punch the app checks the device. It refuses a fake location and its known apps, a device with modified privileges, an emulator, and any approximate location in place of the precise one, and it holds the punch while a connection cable is plugged in or developer options are on. It compares the satellite location with the network location and refuses when the gap exceeds 2,000 metres and three times the sum of their accuracy margins. The system then checks the app's integrity through Google Play, and asks for the fingerprint or face check when your company has turned it on, using a one-time challenge that expires after 5 minutes. Every tampering attempt is recorded for management with its reason.
03
One phone and fingerprint devices
Each employee has one approved phone, bound at first sign-in. If they open their account from another phone, sign-in is blocked and a dialog offers two choices, confirm or cancel, and confirming sends a device change request to management. Your company chooses whether attendance can be recorded from the phone only, from a fingerprint device only, or from both, and each employee can override the choice. For ZKTeco devices the system generates a private key for each device that goes into the receiving address you set on the device, and keeps a log of every connection that was refused. A device number is linked to an employee automatically by matching the national ID, while a name match only suggests a link until someone confirms it, and raw punches are stored so they apply retroactively once a number is linked.
04
From the shift to the minute
Each employee has a shift with a fixed time or flexible hours, and some employees have more than one shift a day, such as a morning and an evening shift, or a shift that crosses midnight. Each shift has its own lateness allowance, early-departure allowance and rest days, and your company's public holidays enter the calculation so a holiday is never counted as an absence. On a fixed-time shift, check-in is not accepted before it starts unless your company sets a window in minutes. Overtime is counted after the shift ends, always, and before it starts only if your company turns that on. An employee who has not punched out by midnight Riyadh time is counted as having a forgotten punch, and a shift that crosses midnight gets three hours after it ends.
05
After the punch: correction, alerts and payroll
Refused attempts are kept in a log that only management sees on the web, with the street and district, the distance and a map link. The employee sees the reason for the refusal at the moment of the attempt, and the app keeps no log of it. Someone with the permission can approve an attempt as a punch or correct a day, and every edit is recorded with its value before and after and the name of whoever made it. A day inside a payroll run already released cannot be edited directly. An employee who forgot to punch files a request by choosing one of the days that carry a flag. Management receives alerts for silent absence and for repeated location refusals, plus a morning digest. In payroll, minutes of lateness, early departure, absence and forgotten punches appear as separate lines with their own formula, and the basic salary is left untouched.