Timesheets

Overtime is calculated per 7-day week within the pay period using a 40-hour threshold. Hours exceeding 40 in any given week count as overtime regardless of the pay-period length, and each timesheet shows a regular vs. overtime split.

Timesheets move through pending, submitted, regional-pending (when two-level approval is on), approved, and rejected. A rejected timesheet returns to editable so the employee can correct and resubmit, and an employee can recall a submitted-but-not-yet-approved timesheet back to pending to fix it themselves.

They can submit a correction request from the approved timesheet. It notifies the approving manager (or, if that manager has left, users with approve authority) with the employee's reason, and the manager makes the change through the normal manager-edit flow.

Timesheets export as CSV: an employee self-service download of their own sheet, a manager/admin export filtered by status, date range, and department, and scheduled SFTP push/pull for integrations. Turning approved hours into pay — dollar calculations, paystubs, PDF pay reports, and provider sync (ADP, Workday, Gusto, and others) — is handled by the separate Payroll Processing and Payroll Connect apps.

Four pay-period types are supported — weekly, biweekly, semi-monthly, and monthly — set once per business. The default is biweekly, and the setting controls how each period's start and end dates (and therefore each auto-generated timesheet) are computed.

When an admin turns it on, each submitted timesheet is scored on a 100-point model: a flawless sheet scores 100 and points are deducted per anomaly — missing punches, edited entries, schedule deviation, overtime, and suspicious IP. Sheets scoring at or above the threshold (95% by default, configurable 1–100) with no blocking anomaly are approved automatically; everything else is flagged to a manager. Three anomaly types — suspicious IP, outside-window punches, and unreviewed attendance — always block auto-approval and route to a human no matter how high the score.

You can define premium types in five categories — shift differential, acting pay, hazard, call-back, and custom — each calculated as a percentage, a flat rate, or a rate override, and applied automatically when a timesheet is submitted. Stacking is priority-based: rules resolve in priority order, and once an exclusive premium applies, only premiums explicitly marked stackable are added on top. Rules can be date-effective (start/end windows) so a premium turns on or off on a given date.

Yes. The AI Timekeeping assistant answers employee questions about hours, overtime, and timesheet status, and lets an authorized approver approve or reject a submitted timesheet from chat. The write actions dispatch through the normal approval controller and show a confirmation preview before any change is made, and they are gated by the same 'approve timesheets' permission — a manager without approval authority only gets the read-only answers.

Time & Attendance is where hours are captured — clock-in/out (including from a shared kiosk or biometric device), breaks, and missing-punch corrections. Timesheets consumes those attendance records into per-pay-period sheets, then layers on the approval workflow, overtime and premium calculation, auto-approval scoring, and CSV/SFTP export. Neither app turns hours into dollars — that is the separate Payroll Processing and Payroll Connect apps.