Time & Attendance

Records can be created from the web, a Time Clock Kiosk, a biometric time clock device (IDCube), the REST API, CSV/Excel import, or a manager-reviewed missing-punch request. Every record stores its punch source for audit.

A manager pairs a kiosk to a location, generating a passcode. Employees connect with that code and identify themselves by Employee ID plus a personal PIN (with optional photo capture). Rate limiting locks out after 5 failed attempts for 5 minutes to block brute-forcing.

They can file a missing-punch request from the Time & Attendance app with the correct clock-in/out times, any breaks, and a reason. It is sent to their manager for review and must fall within the retroactive window (default 7 days, following the timesheet lockout setting). Requests are never auto-approved, and the AI agent can only direct users to the form — it cannot log time on their behalf.

Yes. Every clock event syncs into the corresponding timesheet in real time, including break records. Hours feed overtime, double-time, daily-overtime, and premium-pay calculations, and approved timesheets can be pushed to payroll via Payroll Connect.

Time & Attendance records discrete clock events — each clock-in/out is a record with an on-time, late, or missed status, a punch source, and location/device verification. Timesheets aggregate those events into pay-period hours for review and approval. Every clock event (including breaks) syncs into the matching timesheet in real time, where the hours roll up into overtime, double-time, and premium-pay totals. In short: attendance answers "when did they punch and was it valid?"; timesheets answer "how many payable hours this period, ready to approve?"

When an employee clocks in, the system auto-creates each break type your business has marked as required — for example a 30-minute unpaid Meal Break and a 15-minute paid Rest Break. Paid break time stays in payable hours; unpaid break time is subtracted. If an employee ends a required break short of its configured duration, the record is flagged for manager approval, and any break still in progress is auto-completed when they clock out.

Yes. Each punch can capture GPS coordinates, IP address, and a device fingerprint. Per-location geofencing flags a clock-in taken outside the site's allowed radius; IP validation runs in passive, warning, or strict mode (with IP-based geolocation as a fallback when GPS is unavailable); and unrecognized devices are flagged. Any punch that fails a check is routed to the manager's review queue instead of being silently accepted, and optional photo verification at clock-in and clock-out adds an identity check.

Yes. Time & Attendance integrates with IDCube biometric and badge-based time clock devices. An admin configures the IDCube connection once as a system integration; punches from the device sync in with a "time_clock" punch source and flow through the same verification, timesheet, and manager-review pipeline as web and kiosk punches.

It is an optional autonomous agent that watches clock activity and surfaces issues for a human to approve — it never acts silently. Its capabilities (each toggled independently) include clock/anomaly monitoring, tardiness alerts, approaching-overtime warnings, and no-show detection. Detected items land in an approval queue where a manager confirms or dismisses each one.