Closing the Time-Theft Gap
How GPS-verified timekeeping recovered $87,000 in inflated payroll — after a PIN pad quietly leaked it for 14 months.
The Situation
A security company with 95 guards discovered during an internal audit that actual clock-in times at sites were systematically earlier than the shift start, and clock-out times were later than shift end — by an average of 22 minutes per shift per guard. The timekeeping system used PIN-pad entry that could be triggered by anyone at the site.
A combination of buddy punching, early arrivals logged as billable, and late departures added to payroll without supervisor verification had inflated payroll by an estimated $87,000 over 14 months. The discrepancy was discovered through a random payroll audit cross-referenced against GPS vehicle logs.
What Went Wrong
- PIN-pad timekeeping with no GPS verification — anyone could clock in for anyone.
- Buddy punching enabled by a system that couldn't verify physical presence at the post.
- 22-minute average daily inflation per guard across 95 guards over 14 months.
- No automated cross-reference between clock-in times and verified guard location.
- Supervisors approving timesheets without independent verification capability.
Payroll Problem → Impact
| Payroll Problem | Impact |
|---|---|
| Buddy punching system-wide | Undetectable without GPS |
| 22 min average daily inflation | $87,000 over 14 months |
| 95 guards affected | Full workforce exposure |
| Partial recovery only | Most overpayment unrecoverable |
| Ongoing annual exposure | $74,000 if unaddressed |
The Business Impact
$87,000 in payroll overpayment was identified across 14 months. Recovery was partial due to employment law constraints — the company implemented GPS verification immediately but could not recoup the majority of overpaid wages. Payroll accuracy became a board-level discussion.
The InstaNotified Solution
InstaNotified requires GPS-verified clock-in at the post location before a shift is recorded. A guard cannot clock in from anywhere other than the assigned site, and clock-out requires the same verification. Payroll is generated from verified location data, not manual entry or PIN submission.
The Results
After switching to InstaNotified, GPS verification is required for every clock-in and clock-out, $87K in annual payroll leakage was recovered, buddy punching became structurally impossible with zero workarounds, and 100% of payroll is now backed by verified location data.
If your clock-ins aren't GPS-verified, you likely have this leak right now.
See how InstaNotified ties every clock-in and clock-out to the exact post location — so payroll runs on verified data, not a PIN pad.