Time & attendance

Where punches come fromCopy Anchor Link

Each punch records its source and device. Punches are never edited: corrections are separate records with a reason, and both stay visible.

Punch correctionsCopy Anchor Link

Employees ask for a correction from the Employee Area (a missed punch, or a wrong one to replace) with a reason. A manager with punches.correct for that employee approves or rejects it. Approving adds the corrected punch and marks the replaced one void: it stays on record (includeVoided=true shows it) but no longer counts. Corrections into a locked pay period are refused. Rebuild timesheets after approving to update their totals.

Kiosk timeclockCopy Anchor Link

Planned The built-in kiosk is designed but not built yet. Until it ships, send punches from a timeclock integration.

1. Go to Settings → Kiosks (kiosk.manage) and choose Add kiosk for a location.
2. Open the pairing URL on the tablet or PC and enter the pairing code.
3. Staff clock in with a badge (barcode or QR), a QR code from their Employee Area, or a personal clock code.

Options:

• Photo on punch (time.kiosk_photo) to discourage buddy punching. Photos are kept for a configurable period and then deleted.
• Job or department selection when someone works in several areas.
• Offline mode: punches are stored on the device and sent when the connection returns, keeping the original times.

Schedule-aware punchingCopy Anchor Link

Planned With Scheduling on (scheduling.schedule_enforcement), the kiosk and API check each punch against the schedule:

Labor rulesCopy Anchor Link

A labor rule set (labor_rules.manage) is assigned to each location or inherited from above:

• rounding (e.g. to 5 minutes)
• paid and unpaid breaks and meal periods, with required timing
• daily and weekly overtime thresholds and multipliers, and holiday pay
• minimum rest between shifts, and maximum consecutive days
• rules for minors (latest end time, maximum hours on school days)
• predictive scheduling: notice periods and premium pay for late changes
• break attestation (time.break_attestation): at clock-out, the employee confirms they took their breaks or explains why not

TimesheetsCopy Anchor Link

Timesheets are built automatically from punches for each pay period and show:

• worked, break, overtime, holiday and premium hours per day
• exceptions: missed punches, missed breaks, early or late punches, unscheduled shifts, overtime
• the comparison with the schedule

ApprovalCopy Anchor Link

1. Manager approval (timesheets.approve), within the manager's reach. Exceptions must be resolved or accepted first.
2. Payroll approval and lock (pay_periods.lock). A locked pay period can't change. Late corrections are carried into the next period as adjustments.

Employees can raise punch correction requests from their Employee Area. The manager approves or rejects them, and every decision is audited.

Time offCopy Anchor Link

time.time_off manages leave types (vacation, sick, personal, unpaid…), accrual rules and balances. Employees request leave in their Employee Area, managers approve it (time_off.approve), and approved time off appears on schedules and timesheets.

Payroll exportCopy Anchor Link

time.payroll_export exports approved, locked hours:

• CSV templates: choose columns, codes and formats to match your payroll provider's import, and save them as named templates.
• Integration: a payroll integration listens for pay_period.locked and fetches the hours through the API.

Hours are broken down by employee, earning code (regular, overtime, holiday, premium), location, department and cost center.

API & eventsCopy Anchor Link

Events: punch.received, punch.corrected, punch.exception Planned, timesheet.approved, timesheet.rejected, pay_period.locked, time_off.requested, time_off.approved, time_off.rejected.