Payroll that starts at the gate, not in a spreadsheet
HR and payroll automation joins the physical record of who actually worked to the system that pays them. We take attendance from hardware already on your site — a camera at the gate, a tablet at the workshop door, a tag on a plant item — and feed it into leave, overtime, allowances and the monthly pay run with statutory deductions already applied. Every payslip line traces back to a timestamped event.
Where payroll actually breaks
In most operations we assess, the payroll engine itself is sound. What fails is everything upstream: a register signed in a book at the gate, overtime chits handed in late, a WhatsApp message about who worked night shift, and a clerk re-typing all of it in the last days of the month. Each handover invites a keying error or a disputed shift, and none leaves evidence you can check six months later.
Attendance captured by hardware you already own
We do not open with a quote for biometric terminals. Most sites already have a camera on the pedestrian gate, a smartphone in every supervisor's pocket and a tablet on the floor, and any of those can become a clock-in point. Facial recognition on an existing camera records arrival with no queue at a reader, a geofenced phone check-in suits drivers who never pass a gate, and Bluetooth tags suit contractors moving between yards.
Zimbabwean payroll rules encoded once
The rules that make local payroll tedious rarely change but must never be wrong: PAYE under the Final Deduction System, NSSA contributions for both the pension and workers' compensation schemes, the statutory training and standards levies, and the grading and minimum wage structure set by your industry's National Employment Council. We encode these against your real grades and shift patterns, then run them over months you have already paid so you can compare line by line before go-live.
Multi-currency runs and mixed payment methods
Paying part of a wage bill in United States dollars and part in local currency, at a rate that moves, is the commonest source of payroll disputes we see. The system holds the contractual currency, the split rule and the rate used for that run, and prints all three on the payslip so the calculation explains itself. Output leaves as a bank transfer file, a mobile money batch, or a signed cash schedule for daily-rated labour.
Working with the payroll engine you already run
If your finance team trusts an established payroll package or a well-maintained spreadsheet, replacing it is rarely the cheapest route. In most engagements we automate the front half — capture, validation, approval, statutory calculation — and hand the finished input to your existing system in its own import format, so month-end does not change.
What it covers
No buddy clocking
Attendance is tied to a face or a device at a known place and time, so one employee cannot sign in for another.
Exceptions, not registers
Supervisors stop approving whole registers and approve only what looks wrong: a missing clock-out, an unusually long shift, an unexplained absence.
Leave and contract dates watched
Leave accrues off the same record that drives pay, and fixed-term expiries, probation ends and certificate renewals are raised before they lapse, not after.
Statutory pack ready to file
Each run produces the schedules your finance team needs for ZIMRA, NSSA and employment council submissions in the format they already file.
Built for bad power and thin links
Clock-in points buffer locally through a power cut or a dropped connection and synchronise when it returns. A gate does not stop working because the internet did.
How it works
Site assessment
In week zero we walk the operation — gates, workshops, shift changeovers, the payroll office — and document the cameras, tablets and HR and payroll systems you already have, finding where month-end jams.
Integration
Over weeks one to three we connect the clock-in points, the employee record and the payroll engine, then run them in observation mode alongside your existing register so you can compare the two before trusting it.
Payroll rules and guardrails
In week four we encode grades, shift and overtime rules, allowances, leave accrual and deductions, then test them against months you have already paid. Nothing goes live until a test run reconciles to a pay run you recognise.
Go live and optimise
From week five the system carries capture, approval, calculation and the payment file. We review weekly at first, tightening exception rules and tuning recognition at the gate as your site's real patterns emerge.
Questions buyers ask
Do we have to replace our current payroll software?
No. In most engagements the existing engine stays and we automate everything feeding into it, handing over a validated import file each period. We would only propose replacing it if it were genuinely the constraint, and would show you why at assessment.
How long does a first system take?
Typically four to six weeks from site assessment to go live for one site. Groups usually run the first site to completion, then roll the tested configuration out to the rest.
Is facial recognition at the gate lawful, and must employees agree?
Biometric attendance is personal data and should be treated as such: employees informed, the purpose stated, and retention agreed in writing, usually through a policy update and your works or employment council process. Data stays in your environment or a dedicated tenant, and we will not deploy a system your HR and legal advisers have not approved.
Our sites lose power and connectivity. Will attendance be lost?
Clock-in points keep working offline and buffer events locally, synchronising when power and the link return. If a gap does occur, the system flags it for a supervisor rather than quietly closing it.
Can it handle different employment council agreements across divisions?
Daily-rated, seasonal and contractor hours are captured on the same clock-in points as permanent staff, with their own rate rules and payment schedule, so site headcount is one number.
Book a platform briefing
Fifteen minutes with an engineer, not a sales pitch. Tell us how your month-end runs today and we will say which parts we would automate first and what it would take on your sites. Email sales@eigenstatesystems.com or message us on WhatsApp on +263 77 636 6999.