Requests & Overtime

This guide covers fixing a missing or incorrect day, how attendance gets finalized, and how overtime is tracked and approved.

Purpose

Punches don't always tell the whole story — a forgotten clock-out, a day worked without clocking in at all, a system hiccup. This answers: "How does a day's record get corrected, and who signs off on it?"

Attendance Requests

An employee (or their manager, on their behalf) can submit a request to add a missing day or correct an existing one — proposing the date, shift, work type, clock-in and clock-out times, worked hours, and a description explaining the change. Requests can also be submitted in bulk, covering a range of days at once.

Once submitted, a request sits pending until it's approved or rejected. Approving applies the proposed changes to the actual attendance record; rejecting a brand-new day removes it entirely, while rejecting a correction to an existing day simply leaves the original data in place.

Validation

Attendance validates itself automatically as long as the day's worked hours stay under a company-configured cutoff (9 hours by default). A day that goes over that cutoff needs a manual check from HR or a manager before it's considered final — a safeguard against unusually long, potentially miscounted days slipping through unreviewed.

An already-validated day can be un-validated if it needs a second look, and a validated day with a pending correction request automatically drops back to unvalidated until that request is resolved.

Overtime

Hours worked beyond a shift's minimum count as overtime. Depending on configuration:

• Overtime can be capped at a maximum per day.
• Overtime can require manual approval, or approve itself automatically once it reaches a configured minimum.

Every employee also has a running monthly Hour Account — a tally of hours worked, hours still pending approval, and approved overtime for the month, excluding any days covered by approved leave.

What Each User Sees

Action	Employee	Reporting Manager	HR Administrator
Submit a correction request for themselves	✅	✅	✅
Submit one on behalf of their team	—	✅	✅
Approve or reject a request	—	✅ (their team)	✅
Validate / un-validate attendance	—	✅ (their team)	✅
Approve overtime	—	✅ (their team)	✅
View the monthly Hour Account	✅ (their own)	✅ (their team)	✅

How Visibility Is Decided

1. Ownership. Everyone can request corrections to, and see the Hour Account for, their own attendance.
2. The reporting line. A reporting manager can submit requests on behalf of their team, and approve, validate, and reject on their behalf.
3. Permissions. Company-wide access requires the relevant permission.

Customization Options

• The auto-validation cutoff — how many hours a day can have before it needs manual review — is configurable.
• Overtime rules — the daily cap, the minimum overtime needed before auto-approval kicks in, and whether auto-approval is on at all — are all configurable.

Good to Know

• Bulk requests skip anything already pending. If a day in the selected range already has a request in progress, it's left alone rather than double-submitted.
• Overtime that's auto-approved is still tracked the same way as manually approved overtime — it shows up in the Hour Account and feeds payroll the same way.
• A validated day isn't necessarily a "perfect" day — it just means either it fell under the review threshold, or someone has checked and confirmed it.

Every hour, checked and counted.