Attendance, leave and shifts that payroll can actually trust
eSSL biometric and geofenced web punches, shifts, overtime and leave balances reconciled into one clean set of payroll inputs — with every exception owned by a named manager.
- Punches ingested
- Shifts matched
- Exceptions routed to managers
- Regularisations approved
- Payable days locked
- MISSMissing punch — 2 employees, Plant BVerified
- OTOvertime beyond limit — 1 employeeVerified
- LEAVELeave without balance — 1 employeeVerified
- SHIFTUnassigned shift — night rotationPending
Shifts · Holiday calendar · Overtime rules
- 2 regularization requests passed their SLA and escalated to HR.
- 3 exceptions blocking payable-day lock, all routed to the accountable manager.
- Attendance downloaded from a device, cleaned in Excel, then emailed to payroll.
- Leave balances that differ between the policy document and the system.
- Overtime and shift allowances calculated by hand for each plant or site.
- Nobody can say who approved a regularisation three months later.
- Capture modes
- eSSL biometric (ADMS) · Geofenced web punch
- Reconciliation
- Missing punch · Half day · Weekly off · Holiday
- Overtime
- Overtime rules per policy
- Close
- Locked period with adjustment tracking
- 1Capture
eSSL biometric devices (ADMS push) and geofenced web punch feed the same attendance records.
- 2Reconcile
Missing punches, half-days, weekly offs and holiday calendars are matched against the applicable shift.
- 3Approve exceptions
Every exception is assigned to the reporting manager with an SLA; approvals are recorded as evidence.
- 4Lock the period
Once the period closes, attendance becomes a frozen payroll input — later edits create a tracked adjustment.
Attendance reconciliation — configured for 🇺🇸 United States
The same product, populated with representative data and local identifiers. Never a different product per country.
- Punches ingested
- Shifts matched
- Exceptions routed to managers
- Regularisations approved
- Payable days locked
- MISSMissing punch — 2 employees, Plant BVerified
- OTOvertime beyond limit — 1 employeeVerified
- LEAVELeave without balance — 1 employeeVerified
- SHIFTUnassigned shift — night rotationVerified
Shifts · Holiday calendar · Overtime rules
- 2 regularization requests passed their SLA and escalated to HR.
- 3 exceptions blocking payable-day lock, all routed to the accountable manager.
Shifts, weekly-off patterns, workweeks and holiday calendars per location as configuration, not code.
CL, SL and EL starter set with accrual, carry-forward, encashment and the sandwich rule — approved by the manager, then HR.
A manager sees only their team's requests; anything past its SLA escalates to HR automatically.
Who punched, who regularised, who approved, and when — retained with the payroll period.
Do you work with our existing biometric devices?
If they are eSSL devices that support the ADMS push protocol, yes — punches arrive directly. Other devices are not supported yet; geofenced web punch works for everyone else.
How long does a workforce management rollout take?
It depends on how much history you migrate. A single-country workspace with employee records, attendance policies and one payroll cycle is typically configured in weeks, not quarters — we run it with you as a founding design partner.
Ready to run HR and payroll on one governed platform?
Book a walkthrough. We’ll map your entities, statutory setup and current HR system, and show your team a workspace configured for them.