Clocking, leave and payroll exports that hold up under BCEA and POPIA.
EyesOnTime replaces the spreadsheet-and-hope approach to attendance with a real engine underneath: biometric device support, automatic leave accrual, overtime authorisation, and payroll-ready exports — built for South African employers, not adapted for them.
Built by Bitspace Business Solutions
Biometric-ready
Real biometric terminal integration, not a spreadsheet import.
BCEA-built
Statutory leave accrual, overtime rules and public-holiday pay, modelled in the engine.
POPIA-conscious
Per-tenant encryption on ID, tax and bank fields — not an afterthought.
Mobile-first
An installable phone app for clock-in, no hardware required to start.
From a punch to a payslip, with nothing hand-typed in between.
Every clock-in — from a phone or a biometric terminal — flows straight into one processing engine, so hours, leave and overtime stay in sync automatically.
Clock in
Employees punch in from the EyesOnTime mobile app or a biometric terminal on site — no separate systems to reconcile.
Attendance processes itself
Shifts, lateness, overtime and public-holiday premiums are calculated automatically, with exceptions flagged for a manager to clear, not guess at.
Payroll-ready, on demand
Approved hours export straight to your payroll process — no re-keying timesheets, no end-of-month scramble.
One deep product, not a suite of shallow ones.
EyesOnTime does one job — time and attendance — and does it thoroughly, rather than spreading thin across HR, payroll and recruitment.
Attendance & shifts
Rosters, geofenced mobile clock-in, and a real-time dashboard of who's in, late, or unaccounted for.
Leave management
Statutory accrual, an append-only ledger, and approvals that respect who's allowed to see what.
Overtime authorisation
Pre-approval workflows so overtime pay follows what was actually sanctioned, not just what was punched.
Real-time dashboards
Who's in, who's absent, who's on standby — drill down to the actual record, not just a number.
Payroll export
Approved hours flow out clean, mapped to how your payroll process already expects them.
Device integration
Biometric terminal integration today, with more device support on the way.
Compliance was a design constraint, not a checkbox.
South African labour and privacy law shaped the schema from the first migration, not a policy document added at the end.
Per-tenant encryption
ID numbers, tax numbers and bank details are encrypted per business, not shared across a single database key.
Consent-gated biometrics
Facial capture for clock-in requires explicit recorded consent before it's ever taken.
Automatic retention limits
Biometric images expire on a real schedule by default, enforced by the system — not a manual cleanup task.
BCEA-modelled rules
Overtime, public-holiday premiums and statutory leave follow the Basic Conditions of Employment Act as written.
Facial recognition · Clock-in Coming to EyesOnTime
A face can't be borrowed, lost, or left at home.
Facial recognition ties every clock event to the person actually standing at the terminal — not the card or PIN they were handed. On a large casual or seasonal crew, that's often the difference between attendance data you can trust and one that quietly drifts. No extra device, and no new app account for every worker.
One enrolment, no ongoing credential
A face profile is captured once per employee. No email, password or company phone to issue, reset, or take back when someone leaves.
Runs on the terminal already on site
The same device handling badge and PIN clock-ins today does the recognition — nothing extra to mount at the gate.
A place and a moment, not just a name
Location and a timestamped image ride along with the match automatically, the same way a mobile clock-in works today.
Nothing to hand to the next person
Unlike a card or a PIN, there's no credential one worker can pass to a colleague running late.
Kept on infrastructure you control. Facial recognition is matched and stored per tenant, on EyesOnTime's own servers — never handed to a third-party recognition API — and every enrolment still needs the same recorded, revocable consent as the rest of our biometric handling.
See it running on your own attendance data.
Book a short walkthrough — we'll show you the mobile clock-in, the dashboard, and how a payroll export actually looks.