Record working time, correct exceptions, approve hours, and understand the payroll handoff.

Time & Attendance requires the TIME_ATTENDANCE licence. The attendance page shows My Entries and, for attendance viewers/managers, All Entries. Search, date, status, team and Needs correction filters narrow the server-paginated list.

Permission	Capability
`clock_in_out`	Clock in/out and read your own entries and summary
`view_attendance`	Read attendance lists, summaries and exports
`manage_attendance`	Create, correct, delete and approve entries, including bulk actions
`approve_attendance_period`	Sign off a whole period, separately from individual entry approval
`manage_attendance_config`	Configure attendance policies, locations and biometric devices

The manager view supplies direct-report filters when team scope applies. These permissions are separate: granting a write permission alone does not grant every read endpoint.

Clock in and out

A time entry records one work session. Multiple sessions can share a date. It holds clock times, break minutes, regular/overtime hours, approval state, source, notes and any correction flag.

Clock In creates a present entry. A recent open entry prevents a duplicate with "Already clocked in. Please clock out first."
Clock Out finds the most recent open entry across dates, supporting overnight work. With no open entry the error is "No open clock-in found. Please clock in first."
An entry open more than 24 hours cannot be closed using Clock Out. A manager must correct it. Clock In can set that stale entry aside for review and start a new session; the stale row is not treated as paid worked time.
The entry's calendar date uses the matched work location's timezone, then the company timezone, then the platform fallback of Africa/Nairobi.
Net worked hours are the clock span minus break minutes, floored at zero. The daily calculation considers all sessions on that date together.

Geofencing is strict at clock-in. At clock-out, an outside/missing location is recorded as a [Geofence] note and the entry can close. Such an entry needs human review and cannot qualify for automatic approval. See Work Locations and Biometric Devices.

Corrections and approval

Employees can use Fix this day or Request correction on their own entries, or request a missing day when no entry exists. The request records the proposed complete clock span and reason; it does not immediately change attendance. Self-service requests are limited to the last 90 days. Managers review requests in Corrections, then approval applies the correction through the attendance service. Direct manager edits remain available for older corrections. Review the request's result: an approval and successful application are separate steps.

Create or edit a manual entry when a punch is missing. You can supply clock times or recorded hour totals. The source values are web-clock, mobile, biometric, manual and system; status values are present, absent, late, half-day, on-leave, holiday and rest-day.

Needs correction opens the exception queue. A flagged missed-clock-out entry must have its real times corrected before approval. Individual and bulk approval skip or reject unresolved corrections. Editing an approved entry resets approval; recalculating a day also resets approval when its hour split changes. An approved entry must be edited to reset approval before it can be deleted.

Individual approval and approval of visible entries are distinct from Approve period. Period approval covers the selected date range and scope across pages, reports approved/already-approved/skipped-correction counts, and needs approve_attendance_period.

Automatic approval is opt-in on the overtime rule and defaults off. It only approves completed clocked entries linked to a shift, on an ordinary weekday, with no overtime, correction flag, manual adjustment or geofence note. Both punches must match the schedule within the configured tolerance (default 15 minutes). Other entries stay for manual review.

Overtime policies

These are implemented configuration defaults, not a statement of which employment rules apply to your company.

Setting	Entity default
Normal daily / weekly hours	8 / 45
Weekday / rest-day / holiday multiplier	1.5 / 2 / 2
Rest-day mode	`weekend`
Default individual rest day	Sunday
Working days per week	5
Overtime pay basis	`premium_only`
Automatic hour calculation	On
Weekly caps, standard / night	52 / 60
Fortnight caps, standard / night	116 / 144

Company policy presets can set different values. Review the saved rule rather than assuming the entity defaults are your policy.

With automatic calculation on, ordinary-day sessions share one daily threshold: early sessions fill regular hours and later hours become overtime. All hours on a rest day or holiday are overtime, including hours below the daily threshold. Holidays take priority over rest days.

In weekend mode Saturday and Sunday are rest days. In per_employee mode the employee's configured rest day applies, falling back to the rule's default day. Rest-day overtime is stored in the weekend bucket even when that rest day is Tuesday.

With no active rule, attendance still uses an eight-hour daily threshold and weekend/holiday classification. With an active rule's Auto-calculate off, automatic rebucketing is disabled; recorded splits are preserved. Weekly excess is computed in the period summary, without counting hours already classified as daily overtime twice.

Weekly Hours

The Weekly Hours page compares contracted hours, worked hours, approved/pending hours and a rolling fortnight total. It flags configured weekly/fortnight limits, near-limit hours, past weeks below contract, and corrections. Night-worker settings select the night caps. The page links to the correction queue. These are checks against your configured policy, not a legal-compliance certificate.

Exports

Attendance exports support CSV, Excel and PDF with employee, date, clock times, hours, break, status, source, approval, correction, location and notes. The dialog supports all time, month or custom dates. Approved only and Exclude needs correction default on. Exports format clock times in the company timezone, named in the headers; an unusable timezone falls back to UTC.

Payroll handoff

Payroll consumes approved hours only. Overtime hours are grouped into weekday, rest-day and holiday buckets. An active overtime rule is required to pay overtime; hours can appear without an overtime payment when no rule exists.

The rule determines both the hourly-rate denominator (working days and normal daily hours) and the pay basis: premium_only adds hourly rate ? (multiplier ? 1), while full_rate adds hourly rate ? multiplier. Each is multiplied by the bucket's hours. Approved unpaid leave is a separate payroll input.

Before calculating payroll, resolve corrections, approve the period's hours, and check the saved overtime rule. See the Payroll Workflow Guide.

Time & Attendance