The product workflow
How Attendify works,
from check-in to payroll export
Keep check-in evidence, schedule calculations, exceptions and recorded decisions connected. People remain responsible for reviewing genuine work and authorizing payroll.
- 01
A worker records a check-in or checkout with selfie and location evidence.
- 02
The server checks a received capture before accepting attendance.
- 03
Schedules, paired events and applied corrections produce daily hours.
- 04
Missing punches and other exceptions stay visible for investigation.
- 05
Record correction reasons; use the approval queue when enabled.
- 06
Review export exclusions and reconcile hours with the payroll receiver.
Capture evidence at the point of attendance
Workers set up the app once with a company code, their employee ID and a PIN. After that the phone is remembered and every check-in is PIN-free: a liveness selfie and a GPS fix at the site. Optional face verification is on Growth and enabled per workspace. A selfie or liveness result alone is not proof of enrolled identity.
Mobile attendance app for field workers →Validate received attendance
The server checks authorization and applicable requirements before accepting a capture. It calculates geofence distance from submitted coordinates when required. Device checks can block or flag fake GPS apps, emulators and rooted phones, and the server flags impossible travel and reused selfies. It is still a decision about supplied evidence, not a guarantee that a modified device cannot provide misleading inputs.
GPS geofencing attendance system →Account for delayed and rejected captures
Personal devices can queue captures while offline. The dashboard sees accepted events after synchronization, not records still on disconnected phones. A capture the server refuses stays in a rejected-records list on the phone for 30 days, so a supervisor can follow up and correct genuine attendance.
Offline attendance app for sites with no signal →Calculate the day with its schedule
The daily engine pairs events, attributes overnight shifts, applies configured breaks and overtime, and layers applied corrections over the original evidence. Missing punches remain exceptions. Configured paid-time arithmetic is an attendance input, not a universal payroll-law decision.
Automatic timesheets from every clock-in →Record corrections and decisions
A permitted administrator supplies a correction and reason. The company can require a permissioned approval decision before application. This does not impose an independent second person, multi-level payroll approval or a finalized-period lock.
Missed punch corrections and attendance regularization →Prepare hours and reconcile the receiver
The reviewed-hours export shares the Timesheets engine and excludes blocking days. Named ERP layouts need payroll IDs and receiving-system mapping. Keep exclusions and receiver results alongside the file. The REST API is a separate raw-event data product.
Export reviewed attendance to payroll →Choose a shared device only when the conditions fit
The site kiosk identifies eligible enrolled workers through an online 1:N flow. It is on Growth and enabled per workspace, with notice, calibration and fallback requirements. It is not an offline option.
Face recognition kiosk on a shared tablet →Continue the workflow
Bring your actual attendance workflow.
Starter and Growth are self-serve — start a 7-day free trial, no credit card required. For Enterprise, or to talk through worker/site counts and payroll fit first, reach out directly.